Seagull.bartender.print.printengineexception: The Bartender Engine Could Not Be Started 追蹤

0
Avatar
Legacy Poster

I got this error please help.... I was able deploy on development envir but not on my server 2012

 

 

------------------"Seagull.BarTender.Print.PrintEngineException: The BarTender engine could not be started.
Possible reasons are:\r\n\r\n1)
BarTender is not properly installed.\r\n2)
BarTender is not properly registered on the computer (e.g bartend.exe /register).\r\n3)
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.\r\n4) The user account does not have permission to run BarTender. ---> System.UnauthorizedAccessException: Retrieving the COM class factory for component with CLSID {B9425246-4131-11D2-BE48-004005A04EDF} failed due to the following error: 80070005 Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)).\r\n   at Seagull.BarTender.Print.Engine.Start(EngineSettings engineSettings, LicenseKeyManaged license)\r\n   --- End of inner exception stack trace ---\r\n   at Seagull.BarTender.Print.Engine.Start(EngineSettings engineSettings, LicenseKeyManaged license)\r\n   at Seagull.BarTender.Print.Engine.Start()\r\n -------------

 

 

 

Window server 2012 64bit

I did try to reinstall bartender app and activated in automation 10.1 r4

I did try to register bartend.exe

I did check process instances

I did try to impersonate = true

 

 

 

 

Many thanks,

 

Tim

 

 

 

 

 

3 意見

0
Avatar
Legacy Poster
評論操作 永久連結

i am getting the same error.

anybody from seagull that can help?

0
Avatar
Legacy Poster
評論操作 永久連結

Same here...

0
Avatar
Legacy Poster
評論操作 永久連結

I am getting the same error and I was told that Bartender 10.1 SR3 is not compatible with Windows Server 2012 SR2. I updated to 10.1 SR4 and am still getting the error. I am guessing this is a compatibility issue with Windows Server 2012 

登入寫評論。