Inventory Server 6.0 upgrade install

Portal User asked a question.

September 27, 2018 at 7:00 AM

Just noticed the Inventory Server 6.0 upgrade is pending installation, and requiring a new key (requested from sales rep).

Has anyone done this upgrade yet? Did it go smoothly? Any gotchas? Any pre-install tasks?

Given it is available via SUS, I assume it is just a rolling upgrade right?

Snow-good
8 years ago
Erm.... Is there any documentation on this? This will be our first major upgrade since we installed snow and looking at all the issues others have had, and not having the benefit of a test environment, I wonder if SNOW have a upgrade walk-through and prerequisites ?? ‌
Expand Post
- rfellmann
  7 years ago
  I'm in the same position - need to upgrade to INV 6/SLM 9 (from INV 5 and SLM 8.3.8), no test-environment (yet) and first major upgrade. Since Snow Professional Services charges a total rip-off price to assist during the upgrade I will probably have to do it myself. Besides following the SLM 9 user/upgrade guide I have collected the following steps to be performed .. ... before initiating the SLM 9 update via SUS: Update to INV 6 before updating to SLM 9 Backup database/transaction log Get new license keys from Snow Sales Rep Allow SQL db / transaction log to increase in size according to ‌ ... during installation: If necessary manually create missing views Anything else? Thank you
  Expand Post
  - Siegfried Gammay (Flexera Software)
    7 years ago
    Hello, Robin, Yes, of course. What about customizing? There are many other points that should be checked before upgrading from INV 6 & SLM 9. From a technical point of view I can only recommend to upgrade together with the Snow Professional Service. regards Siggi
    Expand Post
lukasz.dobrzynski
8 years ago
if someone might have problems getting Inventory Server 6.0 after updating: Logs 2018-10-05T19:10:54+02:00;trace;;;;Server manager started. 2018-10-05T19:10:56+02:00;trace;;;;{ "ExitCode": 1053, "LogText": "[SC] StartService FAILED 1053:\r\n\r\nThe service did not respond to the start or control request in a timely fashion.\r\n\r\n", "ClassName": "SnowSoftware.Inventory.Server.ConfigurationManager.ShellExecuteException", "HelpURL": , "StackTraceString": , "RemoteStackTraceString": , "RemoteStackIndex": 0, "ExceptionMethod": , "WatsonBuckets":
Expand Post
AvianFlew
8 years ago
I would suggest that Snow Customers looking to upgrade to INV6 make allowance for approximately 20% bump in database size and, during the installation process, a 100% bump in SQL Log size, If you are using the recommended SQL infrastructure i.e maintaining the Logs on a separate drive, this drive may need its capacity increased - at least for the installation. I have a vested interest in this, but I would advise all users to engage with their Snow Partners to assist them with this upgrade if it is something you wish to undertake at this time.
Expand Post
Portal User
8 years ago
Attempted to upgrade and it failed. This is the error from the update log: 2018-10-06 08:40:54,778 [InstallationWorker] ERROR SnowSoftware.Update.ProductUpdate [()] - An error occurred while executing instructions of v 6.0.00 for Snow Inventory (UR# 372). Beginning rollback. 2018-10-06 08:40:54,779 [InstallationWorker] ERROR SnowSoftware.Update.ProductUpdate [()] - The exception was: System.Data.SqlClient.SqlException (0x80131904): The transaction log for database 'SnowInventory' is full due to 'ACTIVE_TRANSACTION'. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at SnowSoftware.Update.Installation.UpdateDatabaseInstruction.ExecuteSqlFromFile(String filePath, Encoding encoding) at SnowSoftware.Update.Installation.UpdateDatabaseInstruction.Execute(ProductUpdate update) at SnowSoftware.Update.ProductUpdate.Install() ClientConnectionId:03aa264f-5d2e-44ba-b48d-cc6c20bebef4 Error Number:9002,State:4,Class:17 2018-10-06 08:40:54,990 [InstallationWorker] ERROR SnowSoftware.Update.ServiceControlWrapper [()] - The service, SnowInventoryServer5, cannot be started. System.InvalidOperationException: Cannot start service SnowInventoryServer5 on computer '.'. ---> System.ComponentModel.Win32Exception: The service did not respond to the start or control request in a timely fashion --- End of inner exception stack trace --- at System.ServiceProcess.ServiceController.Start(String[] args) at SnowSoftware.Update.ServiceControlWrapper.Start() 2018-10-06 08:40:55,202 [InstallationWorker] ERROR SnowSoftware.Update.ServiceControlWrapper [()] - The service, SnowInventoryServer5, cannot be started. System.InvalidOperationException: Cannot start service SnowInventoryServer5 on computer '.'. ---> System.ComponentModel.Win32Exception: The service did not respond to the start or control request in a timely fashion --- End of inner exception stack trace --- at System.ServiceProcess.ServiceController.Start(String[] args) at SnowSoftware.Update.ServiceControlWrapper.Start() 2018-10-06 08:40:55,409 [InstallationWorker] ERROR SnowSoftware.Update.ServiceControlWrapper [()] - The service, SnowInventoryServer5, cannot be started. System.InvalidOperationException: Cannot start service SnowInventoryServer5 on computer '.'. ---> System.ComponentModel.Win32Exception: The service did not respond to the start or control request in a timely fashion --- End of inner exception stack trace --- at System.ServiceProcess.ServiceController.Start(String[] args) at SnowSoftware.Update.ServiceControlWrapper.Start() 2018-10-06 08:40:55,646 [InstallationWorker] ERROR SnowSoftware.Update.ServiceControlWrapper [()] - The service, SnowInventoryServer5, cannot be started. System.InvalidOperationException: Cannot start service SnowInventoryServer5 on computer '.'. ---> System.ComponentModel.Win32Exception: The service did not respond to the start or control request in a timely fashion --- End of inner exception stack trace --- at System.ServiceProcess.ServiceController.Start(String[] args) at SnowSoftware.Update.ServiceControlWrapper.Start() 2018-10-06 08:40:55,868 [InstallationWorker] ERROR SnowSoftware.Update.ServiceControlWrapper [()] - The service, SnowInventoryServer5, cannot be started. System.InvalidOperationException: Cannot start service SnowInventoryServer5 on computer '.'. ---> System.ComponentModel.Win32Exception: The service did not respond to the start or control request in a timely fashion --- End of inner exception stack trace --- at System.ServiceProcess.ServiceController.Start(String[] args) at SnowSoftware.Update.ServiceControlWrapper.Start() 2018-10-06 08:40:55,869 [InstallationWorker] ERROR SnowSoftware.Update.ProductUpdate [()] - An error occurred while executing instructions of v 6.0.00 for Snow Inventory (UR# 372). Rollback complete. 2018-10-06 08:40:55,869 [InstallationWorker] ERROR SnowSoftware.Update.ProductUpdate [()] - Could not install update v 6.0.00 for Snow Inventory (UR# 372). System.ApplicationException: Update could not be installed. Instructions have been rolled back. ---> System.Data.SqlClient.SqlException: The transaction log for database 'SnowInventory' is full due to 'ACTIVE_TRANSACTION'. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at SnowSoftware.Update.Installation.UpdateDatabaseInstruction.ExecuteSqlFromFile(String filePath, Encoding encoding) at SnowSoftware.Update.Installation.UpdateDatabaseInstruction.Execute(ProductUpdate update) at SnowSoftware.Update.ProductUpdate.Install() --- End of inner exception stack trace ---
Expand Post
- DavidH
  8 years ago
  Hi ‌, I feel your pain. It looks like your transaction log got filled up, because it says: "The transaction log for database 'SnowInventory' is full" . Although I'm not totally sure if that was the cause ... or something that happened during the rollback process. In any case, you may have to do the same as us ... restore the Inventory database from a backup, allocate some more space to your SQL server and then try the upgrade again. If you look at this link on the support portal , you'll see at the end under ' Upgrade Information' that you may need to allocate extra space to your SQL Server. It talks about 15% extra space. But as ‌ suggests in a comment above , you may need a lot more space in the transaction log ... which might also be on a different drive. But we did get our upgrade to succeed in the end. I hope that you don't have too much hassle with it. Regards, David
  Expand Post
  - Portal User
    8 years ago
    Yeah, I did provide the "upgrade information" to the SQL guys and they supposedly did all that. I also ran this on the SQL Server. ALTER DATABASE [SNOWInventory] MODIFY FILE ( NAME = SNOWInventory', MAXSIZE = UNLIMITED) Looks like I need a command to run against the Transaction log. I'll keep working on it. thanks.
    Expand Post
    Siegfried Gammay (Flexera Software)
    8 years ago
    Hi all, here some additional information regarding INV 6 update and SQL database logfile size. "Prior to the update please makes sure that the Snow application servers and database servers are being backed up and that the transaction log has available space for an estimated size up to the following: (Total SnowInventory DB size) * 0.5 + (SnowInventory.inv.DataMetering size + SnowInventory.inv.DataMeteringConcurrency size) * 2.85 This is a temporary need that can be reduced to the original size after the update. After the update the Snow Inventory Server 6 Database can grow and to be permanently larger by max. 20%. As a result, please make sure that you have enough disc space is allocated prior to the update." Regards Siggi
    Expand Post
DavidH
8 years ago
Hi ?, I was also wondering about this, because I saw the message about a new key as well. I was hoping that I could leave SUS to do the upgrade automatically and everything would be fine, without manual intervention. Perhaps we are all doing the same thing ;-) Regards, David
Expand Post

10 of 22

Related Product Forums

→ Flexera One

→ Snow Atlas

→ FlexNet Manager

→ Snow License Manager

→ App Broker

Need help finding an answer?

Ask a Question →