/build/static/layout/Breadcrumb_cap_w.png

PaperPort 11 invalid serial number error

Hi folks,

I've been some issue with Paperport 11 SE while installating with Zenwork. When I tried to install with a standard user logged, I always got thoses errors message :

Invalid Serial Number

and

Ereg Error Use - EREG_RUN - mandatory property

After two month speaking with Nuance support, they give me this solution :

Problems:

The following problems can occur when performing an installation as the SYSTEM account, or after the application was installed by the SYSTEM account.

An "Invalid Serial Number" error during installation or when launching the program after installation.

Trial watermarks appear on a PDF file when opening it in PaperPort or PDF Pro.

Application shortcuts do not appear on the Windows Start menu and the application doesn't appear to be properly installed.

A "Visual C++ Runtime" error appears when trying to open the application.

Application does not appear in the "Add/Remove Programs" Control Panel


The following error appears at the start of an MSI log file:
ISMsiServerStartup Failure, Failed to Initialize script support, Error = 0x80070006

Cause:

These problems can occur due to a bug in the InstallShield Scripting Runtime (ISScript). The Windows Installer (MSIEXEC) calls the ISScript component to complete certain parts of the installation. This bug causes these parts to run as the user logged into the system (or not at all if no one is logged in). If the user logged in doesn't have adminstrative rights or no one is logged in, the installation can fail and return one of the issues noted above.

Solution:

The following solution will force all parts of the installation to be performed as the SYSTEM account, allowing the application to be properly installed.

Note: Do NOT use this solution unless the installation was performed using elevated privileges or the SYSTEM account.

1. Click "Start > Run > regedit" to open the Windows Registry Editor.
2. Navigate to the following registry key:

ISScript10
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\{24D495A5-A174-4945-819D-CF294600C500}

ISScript1050
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\{223D861E-5C27-4344-A263-0C046C2BE233}


3. Delete the following value (entry on right) that exists under this key (folder):

"RunAs"

4, Close out of the Windows Registry Editor.
5. Perform the installation again. If the application is partially installed, uninstall it using the "Add/Remove Programs" Control Panel and then run the remover tool before performing the installation.

hope will help !

Cheers !

0 Comments   [ + ] Show comments

Answers (1)

Posted by: anonymous_9363 12 years ago
Red Belt
0
Typical vendor - blame someone else!

Actually, it *is* a problem with the InstallShield runtime but anyone who's been packaging for more than 5 minutes will have encountered the problem and added handling in their package to bypass it. So, it's a bit of a cop-out to expect their customers to fix it when it could be included in the package from the start. Poor show and well done for pointing it out.

BTW, you *should* have posted this in the 'Package Devlopment' forum. A moderator may move it.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

View more:

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ