Permissions Required To Start Engine Follow

0
Avatar
Legacy Poster

We're using 9.4 Automation. We have a web site that calls almost identical code to the Label Print sample application. When testing in Visual Studio, it works fine, we can change the template name, use the substrings, change the target printer, etc. great. But when the web site was deployed to IIS, the engine is not started. The generic message is returned, (app not deployed, too many engines running, not installed properly, etc...) I changed the application Pool Identity to a machine administrator and it works fine again. Which services do we need to give administrator priveleges to the App Pool Identity so we don't have to use an administrator? 

1 comments

0
Avatar
Domingo Rodriguez
Moderator
Comment actions Permalink

You need to guarantee that it has permissions over the BarTender documents folder, over the printers that you intent to use. Also, make sure that the account you're using for the application pool has full rights over the following Windows registry entries:

 

HKEY_CURRENT_USER\Software\Seagull Scientific

 

HKEY_LOCAL_MACHINE\SOFTWARE\Seagull Scientific --> for 32 bit Windows installation

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Seagull Scientific --> for 64 bit Windows installation.

 

 

Will this help?

Please sign in to leave a comment.