Jump to content
Tribmos

Cannot Locate License Server

Recommended Posts

Tribmos

I have a few systems running 9.01 B2561 and they have been going fine for years now. However today one system is reporting error 3405 "BarTender cannot locate the Seagull License Server on the network." It had been working the previous week.

 

Going into Tools -> Licensing setup and running manual tests DO find the server

All running processes that appear to be seagull related are allowed through the firewall (windows)

System is WinXP SP3

 

I'm really not sure where to start as the "test" finds the server, yet it errors on a print/print preview. The other systems are not experiencing this issue.

Share this post


Link to post
Share on other sites
Ian C - BarTender ninja @ Seagull

As a quick test, deactivate the BarTender application and then reactivate again. Does that get BarTender finding License Server again? Be sure to have your PKC handy before deactivating.

Share this post


Link to post
Share on other sites
Peter_E

As a quick test, deactivate the BarTender application and then reactivate again. Does that get BarTender finding License Server again? Be sure to have your PKC handy before deactivating.

 

I registered on this board just to say thank you! Now it works.

Share this post


Link to post
Share on other sites
John Popernack

Hi-

 

I have an issue with BarTender not connecting to the Seagull License Server.

 

I am running Windows Server 2008 R2 Standard and BarTender Enterprise Automation Edition version 9.40 licensed for 3 printers. I downloaded the software from this website and used the trial mode for a period of time and activated it today.

 

I tried deactivating and reactivating BarTender. Also, under Administer..Licensing Setup, I tested the connection and it didn't find it (although, this may not be a proper test, since it's set to automatically find the SLS).

 

Can someone help with this?

 

Thanks

Share this post


Link to post
Share on other sites
Ian C - BarTender ninja @ Seagull

Have you installed and activated License Server on one of your computers in the network? You mention installing the BarTender Trial and activating it, but nothing about the License Server.

 

The License Server software can be downloaded from the below link. It is License Server which you activate on-line as you license. It then provides printer licenses to the BarTender clients.

 

http://www.seagullscientific.com/aspx/seagull-license-server.aspx

 

See the below white paper for more details:

 

http://s3.amazonaws.com/SeagullBarTender/ftp/WhitePapers/WhitePaper_LicensingForBarTendersAutomationEditions_English.pdf

 

The BarTender user manual also covers License Server installation and configuration:

 

http://www.seagullscientific.com/aspx/bartender-software-manuals.aspx

Share this post


Link to post
Share on other sites
John Popernack

Thanks. I didn't know this was required. I'll try it and let you know how it goes.

Share this post


Link to post
Share on other sites
John Popernack

I see that it recommends installing the SLS before installing BarTender. Should I uninstall BarTender first, or just procede.

Share this post


Link to post
Share on other sites
Ian C - BarTender ninja @ Seagull

It's recommended as an activated BarTender won't find License Server until that is also installed and activated, but really it doesn't matter if printing down time of 10 minutes is not an issue. Leave BarTender as it is.

Share this post


Link to post
Share on other sites
savellano

We have multiple installations using Bartender V9.3 that are experiencing issues with error message 2402. Bartender unable to connect for 2 days. After 1 more day... Of course the number of days varies according to the site.

 

We find that the SLS service is not running even though it is set for automatic. After starting the service the system starts processing jobs normally. Site personnel will typically reboot the PC to restore production. SLS is on the same PC as Bartender. The frequency of these incidents varies from once a week to everyday even though the system runs continuously. Event logs do not show the service being shut down, but when we check, it is in fact not running.

Share this post


Link to post
Share on other sites
Ian C - BarTender ninja @ Seagull

We have multiple installations using Bartender V9.3 that are experiencing issues with error message 2402. Bartender unable to connect for 2 days. After 1 more day... Of course the number of days varies according to the site.

 

We find that the SLS service is not running even though it is set for automatic. After starting the service the system starts processing jobs normally. Site personnel will typically reboot the PC to restore production. SLS is on the same PC as Bartender. The frequency of these incidents varies from once a week to everyday even though the system runs continuously. Event logs do not show the service being shut down, but when we check, it is in fact not running.

 

It sounds like you are having the problem that is detailed in the below forum post.

 

http://seagullscientific.invisionzone.com/index.php?showtopic=688

Share this post


Link to post
Share on other sites
savellano

It sounds like you are having the problem that is detailed in the below forum post.

 

http://seagullscientific.invisionzone.com/index.php?showtopic=688

 

Unfortunately, the issue has been going on for longer than just this week. We have one site with two identical systems, only one of which is affected by the issue. The one not affected has worked fine both before and after the switch to DST.

Share this post


Link to post
Share on other sites
nilodorweb

I was having a similar problem. I ended up running the licensing server as a program instead of a service and that worked for me.

Share this post


Link to post
Share on other sites

×