Yesterday our Snow Update Service started the update to version 5.3.0. Unfortunately, nothing happened. I canceled the update process this morning after 8 hours. Does somebody have the same problems?
if you experience difficulties with the update process, please have a look in the associated logs here:
If you want to perform a clean reinstallation, you can deinstall the product and download the 5.3.0 installation source.
If you have any difficulties, please let me know.
For your information. I also started that update in our test environment and get the same problem like you.
Depending on the log the update is hanging while executing the database update by SQL.So I think you should create a support ticket.
I don't think that reinstallation will help, because the database is the same
i think also that the Query in this update is the problem. i create a ticket. i hope we find a solution tomorrow
thank you for the info. Support is on your case and will contact you tomorrow. Feel free to update here, if you found a solution.
really weird, as I had no issues updating my environment at all. Update was finished in less than a minute and worked like a charm.
The only thing I have seen is a second entry in the Inventory servers list in SMACC.
But I have to say that my environment is a Test environment and was originally installed with Inventory 5.2, so my database might be "more current" than yours.
Kind regards, Axel
Hi all,I think it's not a general problem, but it can depend on the size of SnowInventory database.My SUS log file listed a timeout error, after some time. So it was not really a hangup.I already had a similar issue last year with a SLM update as I also got a timeout error and then support needed to execute the database update in SQL Management Studio.Let's see what Snow will answer.
Upgrade went smooth over here. Let me know if and how your problem is solved so we can learn from this when it happens in future.
Hi at all,
I am doing the upgrade manually. Currently, the execution of the SQL part already takes 2.5 hours and is still ongoing.
Retrieving data ...