Unable To Start The Requested Number Of Print Engines Follow

0
Avatar
Legacy Poster

I'm running Bartender 9.4 EU on Windows 2003 Server.   I can open bartender and print a label, I can browse to the BP-WPS default.aspx and select a label and print it that way.  When I try to create a Visual Studio 2010 web service to print labels as soon as the code hits btTaskManager.start(1) I get an error.  The code is below and the message.

 

Using btTaskManager As New Seagull.BarTender.PrintServer.TaskManager()

Try

btTaskManager.Start(1)

Catch ex2 As System.Exception

Throw New System.Exception("Error Starting btTaskManager: " & ex2.Message)

Exit Sub

End Try

 

Error Message says "Error Starting btTaskManager:  Unable to start the requested number of print engines"

 

If I remove the try catch I get an inner exception that list a bunch of possible reasons for it.  None of which makes sense to me since the BP-WPS is working and the web service is running under the same app pool as the BP-WPS and all security settings for the Virtual Directory are identical.  The message seem to indicate that either the sdk isn't registered or bartender isn't registered or there is a security issue.

 

lpursell

 

3 comments

0
Avatar
Legacy Poster
Comment actions Permalink

More info.  I thought that the SDK installed by default with Bartender but it doesn't.  I installed it on the server but I'm still getting the same issue.  My VS 2010 Web Service includes the bartender interop files in the bin folder.  I noticed that the ones installed in the Assembly directory are all dated 3/10/2011 while 2 of the files in the bin directory seagull.interop.dll and seagull.security.interop.dll are dated 5/16/2011.  Could this be what is causing the issue.  If I'd installed an update on my dev pc for bartender sdk but not on the server I cant find the update.

0
Avatar
Legacy Poster
Comment actions Permalink

More info.  I found an update for bartender previously downloaded to one of our files shares.  I ran it on the server and then made sure the SDK was installed.  I re-tested and I still get the same error.  Consequently I tried to use regsvr32 to register the dll in the \assembly folder of the SDK and they won't register.  It says that a entry path is missing.  Take it this means that there is another dll that the dll is dependant upon that is either not there or the version doesn't match.

0
Avatar
Ian Cummings
Moderator
Comment actions Permalink

Please sign in to leave a comment.