Cant Automate Bartender At Runtime
Hi guys,
We are fully licensed for Bartender Automation; Bartender about reports:
Edition: Enterprise Automation (3 Printers)
Version 10.0 SR4
Build 2868
OS: Windows 7 Enterprise [x86], SP1
ActivationStatus: Activated
On running the project in the VS2010 IDE as Release build everything is fine, but on building the final binaries and running them in place inside the project (should work) I am suddenly getting the "bartender engine could not be started".....Retrieving the COM class factory for component with CLSID {B9425246-4131-11D2-BE48-004005A04EDF}. Error.
The only way I can get rid of the error is to "Run As Administrator", something we don't want to do. This seems to be a recent development, perhaps a windows update? As far as I know none of our other software is built with Admin rights and works fine, it seems just my dev machine.
Can anyone suggest a solution to this please?
The Full Error:
Failed to print all the selected items Seagull.BarTender.Print.PrintEngineException: The BarTender engine could not be started. Possible reasons are: 1) BarTender is not properly installed. 2) BarTender is not properly registered on the computer (e.g bartend.exe /register). 3) There are too many process instances of BarTender running. Stop a few bartend.exe instances and try again. Also see SDK Engine.Start method documentation for information about how to allow more BarTender processes to run on your computer by increasing your "non-interactive" shared desktop heap. 4) The user account does not have permission to run BarTender.
---> System.Runtime.InteropServices.COMException (0x800702E4):
Retrieving the COM class factory for component with CLSID {B9425246-4131-11D2-BE48-004005A04EDF}
failed due to the following error: 800702e4.
at Seagull.BarTender.Print.Engine.Start(EngineSettings engineSettings)
-
I take it that if you open BarTender manually on this PC and initiate a print job, you get no error messages complaining that BT cannot find Seagull License Server on the network?
For the Windows user which is running the application (or better said the Windows user which will try to start the BarTender engines), try to give this user full permissions over the following Windows registry keys:
HKEY_CURRENT_USER\Software\Seagull Scientific
and
HKEY_LOCAL_MACHINE\SOFTWARE\Seagull Scientific --> for 32 bit OS
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Seagull Scientific --> for 64 bit OS
0 -
Thanks but sadly that did''t change anything. Added read/write permissions (and to sub-containers) for all those keys (no 64 bit).
BTW I have tried unregistering, uninstalling, and re-installing/re-registering.
0 -
I have also tried the following as it seemed like a good idea:
- deactivate bartender
- uninstall bartender
- delete all reg entries to bartender, seagull, and any file entries
- reinstall bartender
- re-activate bartender.
No change, but I have noticed the following:
On another dev machine that is set up the same (or should be) Bartender 10 SR4 bartend.exe does not prompt when run, but on my machine I get the UAC prompt "Do you want to allow the program to make changes". Our UAC are both set to the 2nd mark on the UAC console. Both are Windows7 SP1, fully updated machines.
0 -
I take it that if you open BarTender manually on this PC and initiate a print job, you get no error messages complaining that BT cannot find Seagull License Server on the network? You would obviously start BarTender while being logged with one of the Windows users you're having problems with when trying to print from the .NET SDK solution.
Furthermore, as a test, you could try raising down UAC settings to a minimum and then give it another go...
0 -
I have confirmed that the problem is in fact a UAC one. Even when I run bartender (the application) as my user (a local admin) I get prompted. Reducing UAC to 0 results in no prompt. I have confirmed that all bartender services are running as localsystem so frankly I am at a loss.
For now though I am running built applications on my machine as Admin to test them, but its not ideal. However, it works when built and rolled out so it doesn't matter that much.
When I have time I think a reinstall of Windows is needed!
0
請登入寫評論。
評論
5 條評論