cancel
Showing results for 
Search instead for 
Did you mean: 

Upgrade from 6.0 Sp4 to 2007 Sp2 and Monitoring having issue.

LBrignol
Level 4
Partner Certified
Monitoring not working after upgrade to 2007 Sp2.  I am getting the following event ids: 41122 and 41123

(Monitoring Configuration Utility reported error: Monitoring database was not found.   AND   

Monitoring Configuration Utility completed unsuccessfully. Exit code UpgradeError(21). Additional info: Upgrade failed.)

Any ideas on how to fix this?    We reinstalled binaries and rebooted the server but neither seemed to have helped. 
 
Thanks!
LB
1 ACCEPTED SOLUTION

Accepted Solutions

LBrignol
Level 4
Partner Certified

This is the workaround/resolution I was provided for this issue. 

 

Un-installed and re-installed Monitoring as follows:

1. Renamed the d:\Program Files\Enterprise Vault\monitoringwebapp folder.

2. Modified the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\KVS\Enterprise Vault\Install\EVOMMonitoringWebApp from "Installed" to "Not Installed"

3. Stopped Enterprise Vault Admin Service to stop all EV services (make sure the EV console is not open)

4. Stopped IIS.

5. Opened SQL, EnterpriseVaultDirectory, MonitoringSettings. Cleared the entries in this table.

6. Detached and deleted the MonitoringWebApp database, renamed the database files.

7. Ran the Enterprise Vault 2007 setup program, selecting Operations Manager.

8. Ran the "Operations Manager Web App Configuration" utility.

Database was not created so we manually created the EnterpriseVaultMonitoring database manually as follows:

 

-- Stopped the Admin Service

-- Opened a command prompt and changed the path to D:\program files\enterprise vault

-- Used the following command:

MonitoringConfigUtility /create wmstutsqlprod1 wmstutsqlprod1 1 7.5.2.1862 1C7E44AD64546FA40AE8F0C486ED00E961d10000williamskvs.williams.com "k:\...\data" "k:\...\logs" monitoringconfig.log

-- Restarted EV services

View solution in original post

1 REPLY 1

LBrignol
Level 4
Partner Certified

This is the workaround/resolution I was provided for this issue. 

 

Un-installed and re-installed Monitoring as follows:

1. Renamed the d:\Program Files\Enterprise Vault\monitoringwebapp folder.

2. Modified the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\KVS\Enterprise Vault\Install\EVOMMonitoringWebApp from "Installed" to "Not Installed"

3. Stopped Enterprise Vault Admin Service to stop all EV services (make sure the EV console is not open)

4. Stopped IIS.

5. Opened SQL, EnterpriseVaultDirectory, MonitoringSettings. Cleared the entries in this table.

6. Detached and deleted the MonitoringWebApp database, renamed the database files.

7. Ran the Enterprise Vault 2007 setup program, selecting Operations Manager.

8. Ran the "Operations Manager Web App Configuration" utility.

Database was not created so we manually created the EnterpriseVaultMonitoring database manually as follows:

 

-- Stopped the Admin Service

-- Opened a command prompt and changed the path to D:\program files\enterprise vault

-- Used the following command:

MonitoringConfigUtility /create wmstutsqlprod1 wmstutsqlprod1 1 7.5.2.1862 1C7E44AD64546FA40AE8F0C486ED00E961d10000williamskvs.williams.com "k:\...\data" "k:\...\logs" monitoringconfig.log

-- Restarted EV services