You are viewing limited content. For full access, please sign in.

Question

Question

Workflow 11 Installation Setup Error Code 2343

Workflow
Updated June 24, 2022
asked on March 23, 2021 • Show version history

We updated our Laserfiche test environment to LF11 this week. We did not have any issues installing Workflow 11 on the server. However, when trying to install Laserfiche Workflow 11 Designer and Admin Console on our Windows 10 desktops, we are receiving an error code 2343. It appears the installer fails on writing system registry value FINDENTRYINREGISTRYCHECK.72A823C6_3707_48BB_9403_D62F3C9D0FDD. The installation will fail and roll back the installation. Has anyone else run into this problem and found a resolution?

5 0

Answer

SELECTED ANSWER
replied on June 23, 2022
1 0

Replies

replied on March 25, 2021

The issue appears to be caused by not having IIS installed. I've confirmed this in testing and have filed Bug 312607 for the time being.

This thread will be updated again once a fix is available. For now, a possible workaround may be to install IIS on the PCs that need the Workflow Designer installed.

6 0
View 6 previous replies
replied on June 8, 2021

Is there a time frame for when a fix for this issue will be released? Having end users install IIS on their machine is not an ideal workaround for most IT departments.

3 0
replied on June 8, 2021

Hi Blake,

An updated release of Workflow is targeted for Q3 of this year in which this installation error will be addressed. In the meantime, another option that's available instead of actually installing IIS is to insert the registry keys on the PC to make the installer think IIS is present. Then after the Workflow Designer is installed, just remove the registry keys.

See the attached text file, which you can then change to a .reg file, to use to insert the needed values.

WF_IIS_reg.txt (2.8 KB)
Download
0 0
replied on June 9, 2021

Is there a reason a fix hasn't been targeted for release sooner? The other workaround you mention is similar to needing to actually install IIS. Most IT departments are not going to want to create those registry keys on end user machines. We have been holding off on installing Laserfiche 11 for clients waiting for a fix on this as well as other issues with other applications.

4 0
replied on June 9, 2021

We've also been holding off on any plans to migrate to LF 11 for this reason as well

1 0
replied on August 19, 2021

I installed part of the IIS feature - in Windows Features, I selected (under Internet Information Services/World Wide Web Services/Application deployment) ASP.NET 4.8 and it self-selected the rest of the components it needed - then installed workflow designer and admin console, then removed the IIS feature.

Certainly not ideal, but for the one person in our organization that edits workflows (me), it is a workable solution.

3 0
replied on October 11, 2021 • Show version history

Just wanted to check in to see when this will be resolved?  It is now Q4 and the 11 package still includes a version of Workflow that requires IIS to install.  

2 0
replied on December 10, 2021

Steve Hoyer, thank you so much for sharing that workaround, much appreciated!!!

0 0
replied on December 22, 2021

Adding this here so it's in both places. If you do the step where you removed IIS after installing workflow, you'll have to re-add the feature to do the uninstall.

Steve 

1 0
replied on April 6, 2022

@████████ any updates? Its been over a year and we are running into this issue.

0 0
replied on February 25, 2022

We just updated to Workflow 11 using the Laserfiche 11 package that was updated this month, and I'm still getting this error.

It's more than a little disappointing that this still hasn't been resolved after such a long time.

4 0
replied on April 6, 2022

Agree. Just installed in April and its still a problem!

0 0
replied on November 13, 2021

Bumping this thread since I just encountered this error when migrating our designers to LF11. Pretty crazy to think this fundamental installation error has remained since March. 

3 0
replied on March 24, 2021

I encountered the same issue, same scenario but have not found a resolution.  Sounds like something Laserfiche Support needs to investigate and research.

2 0
replied on June 22, 2022

Fixed in Workflow 11 update 1

2 0
View 2 previous replies
replied on June 23, 2022

Awesome! When will Workflow 11 Update 1 be released? 

0 0
SELECTED ANSWER
replied on June 23, 2022
1 0
replied on June 23, 2022

I downloaded and installed the updated version of LF11 and Workflow Designer does now open on my workstation. Thanks!

0 0
replied on June 24, 2022

I installed this update and Workflow Designer 11 now works without IIS, but I'm having a problem getting the Workflow Administration Console to run.  I've uninstalled and reinstalled a few time and even installed IIS on my workstation to see if it needed that for the console.  The Workflow Administration Console acts like it is going to start but never does and there is nothing in the Windows Event Logs.

Anybody else having a similar problem?

0 0
replied on June 24, 2022

OK my issue seems to be isolated to my local machine as I was able to install the new WF Designer & WF Administration Console on a co-workers PC and had no problems running either of them.

 

0 0
replied on March 25, 2021

Also same issue, same scenario. Relevant section of Workflow.msi.log appears to be:

Action start 14:27:53: RemoveExistingProducts.
MSI (s) (98:A4) [14:27:53:745]: Doing action: SetARPINSTALLLOCATION
Action ended 14:27:53: RemoveExistingProducts. Return value 1.
MSI (s) (98:A4) [14:27:53:746]: PROPERTY CHANGE: Adding ARPINSTALLLOCATION property. Its value is 'C:\Program Files\Laserfiche\Workflow\'.
Action start 14:27:53: SetARPINSTALLLOCATION.
MSI (s) (98:A4) [14:27:53:746]: Doing action: ChangeDir
Action ended 14:27:53: SetARPINSTALLLOCATION. Return value 1.
MSI (s) (98:A4) [14:27:53:747]: Note: 1: 2343 
Action start 14:27:53: ChangeDir.
DEBUG: Error 2343:  Specified path is empty.
MSI (s) (98:A4) [14:28:19:968]: Product: Laserfiche Workflow (x64) -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2343. The arguments are: , , 

Action ended 14:28:19: ChangeDir. Return value 3.
Action ended 14:28:19: INSTALL. Return value 3.
1 0
replied on December 16, 2021

I have run into the same issue too and we are at the end 2021. Any news from support?

1 0
replied on December 16, 2021
1 0
replied on June 18, 2021

Hey everyone, I too have been having this issue but I did find a workaround.

 

Install Laserfiche 10.4 Workflow Installation - After it has completed, Install LF 11 Workflow Installation.

1 3
replied on July 6, 2021

I reinstalled Workflow Designer and Admin Console 10.4 and then attempted to install LF11 Workflow Designer and Admin Console. I still ran into the error code 2343.

1 0
replied on July 6, 2021

Same

0 0
replied on March 24, 2021

Log files should be generated automatically during install. On the Windows 10 machine where you are unable to install the Workflow Designer and Administration Console, check C:\Users\[username]\AppData\Local\Temp\laserfiche\install\Workflow and review the files there to try and see why the installation may have failed.

If further assistance is needed, please contact your Laserfiche Solution Provider to open a support case. Be sure to provide the install log files.

0 0
replied on July 19, 2021

We are getting this error still in July. Does it still require an IIS installation on the workstation to install the Designer? Installing 10.4 first doesn't seem to help any.

0 0
replied on September 22, 2021

Want to give this a bump.   Neither I nor my VAR are able to install Workflow 11.  Very annoying

0 0
replied on September 30, 2021

Confirming that installing IIS as a prerequisite fixed that issue for us!

I had a fresh OS build (Windows Server 2019) errored out with the same error 2343 when trying to install Workflow 11. I installed IIS on that server, and the installation went through with no problems.

Hope this helps!

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Attachments
Related Posts
Loading ...