OME 2.2 upgrade of OME 2.1 failure

Hi,

You can check the installutil logs. They should be under /Temp folder. But something like this should not happen. Can you give few more details on the config, eg: System configuration, local db or remote db, was DA service hung (were you able to perform discovery/inventory) before you tried upgrade?

Also, do you have a backup of OME 2.1 db? That would help you restore the older db at least.

Hi

The OME installer logs are located at C:\Users\[username]\AppData\Local\Temp

My 2.1 > 2.2 upgrade also fails :-( Maybe I will post more on that later.

To give more detail.  The server is a Xen VM.  The DB is local and using MS SQL Express 2014.  Since this is a VM I have a snapshot of the VM saved so that I can revert to it when things do not go as expected.  

OME before the upgrade works perfectly fine no issues.

One of the things I did notice was that I had Support Assist installed.  I was able to un-install it.  Beyond that the only other tool I have installed on this host is the OME tool.  Once support assist is removed and the VM rebooted I tried the install again.  Most of the time it succeeds but in the process wipes out the DB.  One time I did make a back up of the DB, ran the installer it wiped out the DB but installed.  When I went to try to restore the DB I never did get an OK button to press to do the restore.

I know very little about MS SQL so not sure what I am doing wrong with the restore.  I will have to do some more googling for that.

Now that I know where the logs are kept for the install I will re-do all of this and see what the logs have to say.  But I have to say I have been doing OME since version 1.1 and all the previous releases have had nice simple upgrades that were super slick.  Its strange that this one is giving me issues.  And from what I see other people.

Louis

I tried again and it failed.  Here are some of the items I found in the logs:

c:\windows\temp\MSI67de8.log:

ÿþError 1706. An installation package for the product SQL Server 2012 Database Engine Shared cannot be found. Try the installation again using a valid copy of the installation package 'SQL_ENGINE_CORE_SHARED.MSI'.
=== Logging stopped: 8/12/2016 5:05:56 ===

This is intresting since I am running sql server express 2014.

c:\windows\temp\install.log:

The .Net SqlClient Data Provider has received a severity 11, state 0 error number -2
on line 0 of procedure '' on server '(local)\SQLEXPRESSOME':
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

-- -- --
-- Gabe's migration database was found to fail unless it was resized.
DBCC SHRINKDATABASE(N'OMEssentials')

Undefined exception occurred:
System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out
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 asyncWrite)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at A.ca1613ae24769a28d48833571261901e3.c0b625d04901134c0eb3f74bc236bc4ac(SqlConnection c4eef4e4e04825f29a50c36fde612dc8a, String cbc836c9c71951115cacd044fc7beb2a3, String ce8ca792c5d6d0a86554671fa863ca3b0, String cede07db0b44b012babff46f4f673e0ca, String c416fa9905f8edb163897bc0e958dd7be)
at A.ca1613ae24769a28d48833571261901e3.c9b9ab3fd77dd4a5762519389c46ab8fa(cc96a45b1269d339bf2002e6c2a14177b ccde6988da3e0fc539f40d470ca6140b7)
at A.c8c481b59c2f61b28290f694f741409fb.c1791c9c6bcdc12bbfbbc579744998222(CommandLineArgumentsDictionary c43e80caba747a47b6a25ee731ee4ddbe)
at A.c8c481b59c2f61b28290f694f741409fb.c7f5e6760a3f3b4c52fdf0c18114992ad(String[] c57f375e92796f6c56863003c7554dc04)
ClientConnectionId:07f03657-971a-4c97-8804-1e7015801d06
Error Number:-2,State:0,Class:11

and

Expected Exception
Unable to delete the event log source: 'Essentials'
System.ArgumentException: The source 'Essentials' is not registered on machine '.', or you do not have write access to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog registry key.
at System.Diagnostics.EventLog.DeleteEventSource(String source, String machineName)
at A.cf1a6a0816809b5200baa72e0648e069e.cf156cd28f4dcf17fd786c4b76eec4707(List`1 c322f062c8e4ca9c9b31d3f98742a0a8b, Boolean cadcb1c8694f4d0d6d2b58ce5e5ea35a2)

EventLogs.UninstallLogSources(...) - Complete

OmeDAService.Uninstall()
Service exe file not found: C:\Program Files\Dell\SysMgt\Essentials\Services\DAService\Dell.ManagementEssentials.Service.DAService.exe

and

Deleting Database [OMEssentials]

An exception was thrown while deleting the database backup history.

This is an optional step and deleting the database can continue without it.
System.Data.SqlClient.SqlException (0x80131904): The EXECUTE permission was denied on the object 'sp_delete_database_backuphistory', database 'msdb', schema 'dbo'.
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 asyncWrite)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at A.c4da17cbd75feaae704fa275a64162718.cd2644ad50b333a0c4d5dc335d0034364(SqlConnection c4eef4e4e04825f29a50c36fde612dc8a, String ce8ca792c5d6d0a86554671fa863ca3b0)
ClientConnectionId:7b2d7293-efbd-4b1f-914f-6062fdc5d859
Error Number:229,State:5,Class:14
Uninstalling the [OMEService] SQL Server login.

Database.RemoveRegistryKeys()

Unable to locate any root registry keys.

Database.RemoveRegistryKeys() - Complete

In the install.log above I definitely see this: Deleting Database [OMEssentials].  Why on earth is it trying to delete the database.  This is supposed to be an upgrade.  

If there is a specific log file name I should be looking at let me know.  I will be happy to provide the full logs if you want.  I can also open a ticket with support but I have generally found that I get the run around with them.  The do not seem to know how to find the OME team and most are very reluctant to ask more experienced support people.

Louis

Hi,

Thanks for the detailed post and sharing the logs.

I understand from your post that you have backup of your OME 2.1 database and then you want to upgrade to OME 2.2. You have installed Microsoft SQL Server 2014 Express on your OME server.

If the above is correct, I will suggest you to try this steps:

1. Restore the OME 2.1 backup on your SQL Server 2014 Express instance.

2. Install OME 2.1 and go to "custom" and enter the "restored" database details what you restored in step 1.

3. Once after step 2, OME 2.1 is successfully installed, make sure you enter the credentials in the range/tasks again.

4. Try to install OME 2.2 now i.e. upgrade to OME 2.2.

I think, this should solve your problem. Pl. let us know if this works.

Thanks,
Vijay

I have spent months getting all the discovery ranges correct and filling in the passwords.  This is the one thing I cannot lose.  I do not care about the rest of the DB only the discovery ranges I have already configured.

If I lose them I would be set back maybe a year.

Louis