Bartender 2021 R6 License server restarted stopping Production server Integration and will not restart
Running 2021 R6 License server with Database and on another Production server running same 2021 R6 with a Integration. When the Bartender server is restarted (mostly for Windows Updates) the Production server Integration stops (as would be expected due to the database is not accessible) and does not recover. Still shows that it is running but is not processing any print jobs until we manually stop all Integrations and restart on the Production server. This this normal behavior or is there a configuration setting to correct this?
-
Hello Ron!
Thank you for posting your query in our Community Forum!
It would seem the Production Server is encountering a licensing error when the License Server is updating, perhaps something akin to Error 1402 (even if the linked article makes reference to an older version of BarTender, I would suggest troubleshooting the issue with the recommended steps).
This would not be expected behavior as BarTender 2021 has a 3-day grace period in place, so even if the Production Server can't locate the License Server, this should not prevent the Integration from working as expected.
Having said that, I would recommend taking a look at the service logs in search of error messages. You can find these logs on the following path:
Let's go through them and search via Ctrl+F for "error" on them. If you locate any error messages, let us know. However, please remember not to share any personal details on this open forum.
Hopefully, we can find something a little more clarifying in the logs.0 -
Thanks Xabier,
On the Production server when the License Server was restarted we see the below in the System Service log
2021.10.14.172902: Error: BSS StorageManager: Poll() failed with A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified): Seagull.Services.SecuritySettings.Server.StorageManager
2021.10.14.172928: Error: The BarTender system database table TargetServers could not be accessed. Details: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The specified network name is no longer available.): Seagull.Services.TargetServerDB.Server.TargetServerDB
2021.10.14.172931: Error: BSS StorageManager: Poll() failed with Cannot open database "Datastore" requested by the login. The login failed.
Login failed for user 'Username'.: Seagull.Services.SecuritySettings.Server.StorageManagerand in the Licensing Service log
2021.10.14.172915: Info: LicenseOwnerLocator OnOwnerTraced - owner: null, licenseInfo: null. Type: Undefined
2021.10.14.172915: Info: ActiveLicenseManager: license owner is lost.
2021.10.14.172917: Info: KnownLicensingServiceManager update service. 'allowNonMustUpdate' False ==> True, Service update 951036, 0
2021.10.14.172918: Info: NotifyRunBarTender() cannot find a license owner to notify. Process ID = 13780.
2021.10.14.172933: Info: NotifyRunBarTender() cannot find a license owner to notify. Process ID = 13780.
2021.10.14.172935: Info: Notify BarTender, Run: 1, Exit: 0, ElapsedMs: 21034
2021.10.14.172938: Info: UpdateService: server(xxxxxxxxxx]:5160). Running: True --> False
2021.10.14.172948: Info: NotifyRunBarTender() cannot find a license owner to notify. Process ID = 13780.
2021.10.14.173003: Info: NotifyRunBarTender() cannot find a license owner to notify. Process ID = 13780.
2021.10.14.173018: Info: NotifyRunBarTender() cannot find a license owner to notify. Process ID = 13780.
2021.10.14.173033: Info: NotifyRunBarTender() cannot find a license owner to notify. Process ID = 13780.
2021.10.14.173048: Info: LicenseOwnerLocator: Set located license owner to SERVER, Type: Initial, IsLocal: False, takes 11.523 seconds
2021.10.14.173048: Info: LicenseOwnerLocator OnOwnerTraced - owner: SERVER, licenseInfo: Success. Type: InitialSystem Service log shows the break to the SQL DB at time of License server restart.
2021.10.14.172902: Error: BSS StorageManager: Poll() failed with A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified): Seagull.Services.SecuritySettings.Server.StorageManager
2021.10.14.172928: Error: The BarTender system database table TargetServers could not be accessed. Details: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The specified network name is no longer available.): Seagull.Services.TargetServerDB.Server.TargetServerDB
2021.10.14.172931: Error: BSS StorageManager: Poll() failed with Cannot open database "Datastore" requested by the login. The login failed.
Login failed for user 'User'.: Seagull.Services.SecuritySettings.Server.StorageManagerIn the Print Scheduler Service log and Integration Service log there is a gap from when the License Server was restarted and the time I restarted the Production Integration. It does not seem to have an issues with finding the license, rather like I stated the Integration does not recover after the license is found.
0 -
Checking the logs you've sent us, it's not too clear whether the issue lies in BarTender's ability to find the license or connect with the database.
In your previous post, you mentioned having the database on the License Server; is this the System Database or the database the label on the integration is pulling data from?
I believe we would have a clearer picture if you could tell us the following:- What kind of integrations are you using?
- What type of database is currently on the License Server, and if it's the one we are pulling data from, what kind of database is it?
-
Have you tried just restarting the BarTender Integration Service instead of the machine? If not, could you give it a try and see if this works?
Thank you!
0 -
Sorry for the late response. Yes restarting the Integration (like I stated in the original question) corrects the issue. It is a simple integration, a file is dropped into a folder on the Production server with data to be printed on a label. Very basic. The SQL sever that comes with the Bartender install - SQL Express 2014. I do not believe we are pulling any data (not 100 % sure on this one) from the database, only writing to the logs. Again, looking to see why the integration on the Production server will not auto recover when the license/DB server is restarted.
0 -
Also, I did reply to this on 10/22/21 at 7:51 am PDT with a copy of the integration file, but do not see it here and have not gotten a response back.
0
請登入寫評論。
評論
5 條評論