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

Question

Question

Installation Error 1712

asked on February 24, 2017 Show version history

This is a PSA, no answer required.

We recently ran into two situations where a product would not install, throwing a dialog box with nothing more than the message: 1:1712.

This took place at the step labeled, "Committing System Changes".  On OK, the installation is rolled back.  This turns out to be a Windows issue, where a prior installation of the same product failed.  It is not really a Laserfiche problem, although it affects what you are trying to do with Laserfiche.

There is no one remedy for this issue. Typically, you'd look in Add/Remove programs to see if any entry there is listed.  If so, uninstall and try again.  Also, a key in the registry might have to be removed.

One conflict involved the Windows Client. Here we found an entry in Add/Remove Programs for the Black Ice Driver.  Once that was uninstalled, the Win Client installed without issue.

A second conflict involved Workflow.  Running it from the menu (install everything) did not work.  But we were able to install one at a time the Designer, then the Server, then the Subscriber.

For diagnostics, you can run the installation from a command line with logging. Use this syntax:

"Path to installation program" -log "Path to log File"

As in: 

D:\10.2.0.872\en\WindowsClient\Setup.exe" -log "C:\temp\Client Installation Log.txt"

1 0

Replies

replied on February 27, 2017

Found the same issue while trying to install client 10.1 on a machine that had client 9.0 removed (apparently not completely removed). Cleared all entries from registry that had to do with laserfiche and blackice (snapshot was needed). Found out that if we did the installation of the client without snapshot it went fine and then we did the manual silent installation of snapshot and that solved the issue.

 

1 0
replied on March 3, 2017

Hi Gerardo -

We found that the Laserfiche client does not install Black Ice as a separate component, but it looks like other applications do.   That almost certainly caused the conflict.  Using a two step installation for Snapshot is an interesting wrinkle.

 

 

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

Sign in to reply to this post.