We support upgrading from OME 1.0 to OME 1.0.1. But what you did is slightly different I think. The 1.0.1 install upgrades and makes changes to the db. But then you restored a 1.0 db file to the new 1.0.1 db.
The process that I think would have worked would be:
1. Install 1.0 Open Eval
2. Restore your db
3. test out the restore to see that it works.
4. Then install 1.0.1
It looks like the 1.0 to 1.0.1 upgrades have been going pretty well. So if you are running into trouble, I think it could be the db restore.
Sorry .... I left out before the server was wiped out I actually did the upgrade from 1.0 to 1.0.1 and was running the new build for about a day before. When I rebuilt the server I purposely installed 1.0.1 directly since I had already been running that version and restoring a 1.0.1 DB to a 1.0 and then upgrading to 1.0.1 was not a good idea in my mind.
Also, not sure i see the correlation between a SQL DB restore and the Network Monitor service stopping and what looks like restarting as well on a regular basis.
Yes, I can open the console with no problems, see all of my devices since I did the DB restore. The issue is that the Network Monitor service fails which will not allow me to monitor or inventory anything. If I start the Network Monitor service, it will start and stay running for an unknown amount of time and then fail and shutdown again.
After talking with support we came to the conclusion is would be better and easier to just start from scratch. New server with 1.0.1 clean DB and re eneter in all the assets.
What turned out to be your solution? I've got two Server 2012 Hyper-V Hosts that won't start the Data Manager Service and failing with a similar error.
DELL-Rob C
3 Apprentice
•
2.8K Posts
0
March 6th, 2012 19:00
Hi Ron,
I'm suspicious of the db restore.
We support upgrading from OME 1.0 to OME 1.0.1. But what you did is slightly different I think. The 1.0.1 install upgrades and makes changes to the db. But then you restored a 1.0 db file to the new 1.0.1 db.
The process that I think would have worked would be:
1. Install 1.0 Open Eval
2. Restore your db
3. test out the restore to see that it works.
4. Then install 1.0.1
It looks like the 1.0 to 1.0.1 upgrades have been going pretty well. So if you are running into trouble, I think it could be the db restore.
Let me know what you think.
Thanks,
Rob
Ron Valkenburg
1 Rookie
•
53 Posts
0
March 7th, 2012 02:00
Sorry .... I left out before the server was wiped out I actually did the upgrade from 1.0 to 1.0.1 and was running the new build for about a day before. When I rebuilt the server I purposely installed 1.0.1 directly since I had already been running that version and restoring a 1.0.1 DB to a 1.0 and then upgrading to 1.0.1 was not a good idea in my mind.
Also, not sure i see the correlation between a SQL DB restore and the Network Monitor service stopping and what looks like restarting as well on a regular basis.
Ron Valkenburg
1 Rookie
•
53 Posts
0
March 7th, 2012 03:00
Here is also the adjoining error when the OME Network Monitor services fails:
Fault bucket , type 0
Event Name: BEX
Response: Not available
Cab Id: 0
Problem signature:
P1: DSM_OMSE_Netmon_32.exe
P2: 1.0.1.1253
P3: 4f347a68
P4: MSVCR90.dll
P5: 9.0.30729.6161
P6: 4dace5b9
P7: 000265ac
P8: c0000417
P9: 00000000
P10:
Attached files:
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_DSM_OMSE_Netmon__f1a9728eb1e7bd1e41bcd6b3e1f683178d71ea7_0fe215a0
Analysis symbol:
Rechecking for solution: 0
Report Id: ab4270b9-6845-11e1-8d49-0024e880803d
Report Status: 4
DELL-Abhijit P
Community Manager
•
711 Posts
0
March 7th, 2012 10:00
Are you able to use OME console? Also can you see if there are additional logs in Windows Temp folder?
Ron Valkenburg
1 Rookie
•
53 Posts
0
March 7th, 2012 14:00
Yes, I can open the console with no problems, see all of my devices since I did the DB restore. The issue is that the Network Monitor service fails which will not allow me to monitor or inventory anything. If I start the Network Monitor service, it will start and stay running for an unknown amount of time and then fail and shutdown again.
DELL-Abhijit P
Community Manager
•
711 Posts
0
March 8th, 2012 07:00
Hi Ron,
It would be better to open a ticket at: 800-945-3355![]( "Call: 800-945-3355")
That way support can work with you to gather additional logs and troubleshoot the issue.
Regards
Abhijit
DELL-Abhijit P
Community Manager
•
711 Posts
0
March 13th, 2012 08:00
Thanks for the update Ron. Let us know how it goes.
Ron Valkenburg
1 Rookie
•
53 Posts
0
March 13th, 2012 08:00
After talking with support we came to the conclusion is would be better and easier to just start from scratch. New server with 1.0.1 clean DB and re eneter in all the assets.
Ron Valkenburg
1 Rookie
•
53 Posts
0
March 13th, 2012 09:00
Our new server is up and running without a problem. Took a few days to get all of the assets back in the way we had them but thats OK.
usmpiano
4 Posts
0
June 28th, 2013 15:00
Ron:
What turned out to be your solution? I've got two Server 2012 Hyper-V Hosts that won't start the Data Manager Service and failing with a similar error.