1 of 1 people found this helpful
This document covers how to increase the database timeout:
It may also help to run the database setup tool for Protect and ensure that you're able to re-link the database for Protect. The database setup tool is under Start > All Programs > Shavlik > Database Setup Tool.
I hope that helps.
I followed the steps exactly as the document above describes in order to increase the database timeout error I was geting a while back, basically just changing the timeout from "30" to "3600" and running the Database Setup Tool.
1) Changed timeout from 30-->3600
2) Ran DB Tool, hit next, next, finish, and it finished without any errors
3) Rebooted the server and ran a scan, yet still experienced the same SQL error I have linked in my original question
4) Went back to check the ST.Data.Config file, and saw that the timeout changed back from 3600 to 30
5) Changed it back to 3600 and rebooted to see if it changed on reboot, this time it stayed at 3600
Then when I launch Shavlik, I now get this error as well. I found
http://community.shavlik.com/docs/DOC-23044 which looks like your how-to for a console service that crashes frequently, but I feel like changing the timeout and running the DB tool screwed something else up. Any help would be appreciated, one error has turned into 3 and I'm not sure why.
With the message you're getting now this document might be more helpful:
If you can send me the ST.DatabaseConfiguration.log from your console system it might be helpful as well.
It should be located in C:\ProgramData\LANDesk\Shavlik Protect\Logs.
(or under Documents & Settings\All Users for 2003/XP)
Also, I need to update the document on increasing the timeout. Running the database setup tool actually resets the timeout. I apologize for the misleading info in that document. I believe the timeout document was originally written back on version 7 or 8 of Protect.
The one from 2014 would be best
Is there a way to attach a document or send you a PM with the attachement? I'm only seeing attach picture/video and the log is quite long.
Well I've never previously seen the errors coming up in your log.
Did you by chance modify anything else in the config files for Protect?
I have created a case on our side for this issue and plan to see if our engineering team has an idea what these errors may be coming from.
No, I changed the timeout from 30 to 3600, ran the DB setup tool (which finished w/o any errors the first time around) and kicked off a scan. When the SQL errors (from my original question back in December) appeared again during the scan, I checked the ST.Data.Config file to check on the timeout, and noticed that it set itself back to 30. I tried changing it back to 3600 and running the DB setup tool once more, and that is when I ran into all these other errors. I didn't modify any other file except for ST.Data.Config per the documentation that was originally linked.
Ok just making sure. Even if you had - we could have you try an uninstall of Protect from add/remove programs and reinstall. That would clear out the config files and put new ones back into place.
What's the OS of the console system as well? I'm assuming the database is on a remote SQL server, but can you let me know the version of SQL the database is on also?
I spoke with my boss about this issue, and he restored the ST.Data.Config file from a day old Veeam backup. We ran Shavlik and the error from my previous screenshot is now gone. We did a test scan and were able to push patches as usual. This brings us back to square 1 with the Timeout error persisting from my original question I posted back in December. Will changing the timeout value to '3600' and NOT running the DB Setup Tool get rid of the that error?
Will changing the timeout value to '3600' and NOT running the DB Setup Tool get rid of the that error?
Hopefully it will. It depends how long the operation is taking. How large is your Protect database anyway? If the timeout isn't fixed by changing the timeout period at this point I'd suggest installing a local SQL express installation on the Protect console system and migrating the database to the local SQL instance.
If that's the route you end up taking this doc explains how to migrate the database:
I'm a newbie when it comes to anything SQL, however our SQL DB is located on the same server as Shavlik is. I'm not sure how to find out how big the DB is, however we have around 120 or so machines we scan if that is any help.
Usually timeout issues are less common with a local SQL install. At this point it might be best to open a case directly with support so we can better address this.
Please send in console logs based on this document if you do open a case:
Support contact info can be found here: