Did you try rollback to it's previous version?
Or try to repair it on control panel>add remove program?
I ran into the same issue this last week. How many Voip servers are you monitoring? Out of 16 VoipServers that we monitor only 2 had the Correct VoipMonitoringID in the VoipCCMPhoneStats.
Seeing how you started the the install and it made changes to the DB already for 2.1 you will get a DB Table error. You will need to stop all services on Orion. Then restore your DB. That will get you to VoIPMon2.0 again with no errors. Sounds like that you need to reinstall your APM as well.
You will more than likely need to open a Case with SW. Like I said I recently had the same issue and it took a few days between SW and I to figure out what exactly was stopping the upgrade.
For your Reference SW Case # 98251
@ neilmborilla - I did try the rollback and it seemed to have rolledback correctly. Until I checked the Orion website. APM, VoIP and any node details page was broken. I also tried repair.
@bleinauer - I am glad that I am not the only one that has seen this. I will be sure to follow up with SW with your case number and see if I can get some answers. Thanks.
For anyone that may come across this thread in the future here is what needed to be done:
After returning all services to original state and following up with SW it was determined that the database changes "may take a while" and to "let it run until it finishes"
I scheduled another maintenance window and started install only after backing up both web configuration and database.
Install took about 3 minutes. Configuration Wizard started and took about 23 minutes to complete. Our database is around 23 Gig so there may be a minute to gig correlation there (maybe not...maybe coincidence).
So lesson here is just waiting it out. If you wait for more than hour or so there may be a problem. Also do not be confused that you see no CPU processing on your local Orion machine as all work is being done on the SQL server.
Questions let me know.
It's always very helpful when members post on the forum the solution that came from a support ticket. That way other community members will have the information when they search for the same or a similar issue.