vCM 5.5 upgrade

[HCC]

Trying to upgrade my configuration manager to 5.5.  It starts install and gets to SQL scripts and I think fails in one of the last core SQL scripts.  SQL server 2008 R2 64bit running on same server as the application.  Any thoughts what might be going on here? 

[firestartah]

Hi

Is there anything mentioned in the debug logs? Try follow the following steps to save the logs so you can check them right after you have the sql failure:

1. Start the VCM portal.
2. Select Administration > Settings > General Settings > Collector. The Collector Settings data grid
appears.
3. Select the Type of information that should be logged, and then click Edit Settings. The Edit Settings
page appears.
4. Select all the options: Exception, Error, Warning, and Info.
5. Complete the other pages in the wizard, and then click Finish.

6. Select Administration > Settings > General Settings > Database. The Database data grid appears.
7.
8. Select the Type of information that should be logged, and then click Edit Settings. The Edit Settings
page appears.
9. Select all the options: Exception, Error, Warning, and Info.
10. Complete the other pages in the wizard, and then click Finish.
11. Select Administration > Settings > Windows > Agent - General. The Agent General Settings data
grid appears.
12. Select the Type of information that should be logged, and then click Edit Settings. The Edit Settings
page appears.
13. Select all the options: Exception, Error, Warning, and Info.
14. Complete the other pages in the wizard, and then click Finish.
15. Select Administration > Settings > UNIX > Agent - General. The Agent General Settings data grid
appears.
16. Select the Type of information that should be logged, and then click Edit Settings. The Edit Settings
page appears.
17. Select all the options: Exception, Error, Warning, and Info.
18. Complete the other pages in the wizard, and then click Finish.
19. Restart the VCM Collector service in the Services manager.
20. Now run the job in question again. You must wait 5 minutes after it completes before proceeding.
21. Minimize the console and navigate to <Drive>:\Program Files (x86)\VMware\VCM\Tools. In this
directory, double-click ECMDebugEventViewer.exe.
22. In ECMDebugEventViewer, click Filter Settings. The Filter Settings dialog box appears.
23. Select all the check boxes in the Message Type and Message Source areas. Click OK.
24. In the Data Source area, type the names of the servers and databases.
25. Click OK to close the dialog box.
26. Click Date/Time. The Data/Time dialog box appears.
27. Select the between option, specify the dates and add five or more minutes to the beginning and end
times during which the collection ran.
28. Click File, and then select Fetch. The displayed data is refreshed.
29. Click File, and then select Fetch Next. Continue the Fetch Next process until no additional data is
added to the displayed debug log.
30. Click File and select Save as Dbe. Save the file as a DBE file and note where it was saved for later use.
31. Repeat steps 1-4 and reverse the settings for the Collector, Database, and Windows Agent and UNIX
Agent objects back to their original logging levels (usually Exception, Error, and Warning).

Gregg

[admin]

Hi HCC

Is screen poping  up any error or its taking time due to that you guessed .

It would be great if you can share log file .

"Life is never easy for those who dream"

[stubbint]

Hi

Did you get this sorted. I seem to have a similar problem with a new install.

The SUITE_00000610_LINDSEY_SR1_01_CORE script fails.

Error 468, Level 16, State 9, Procedure LINDSEY_SR1_CORE_PRE_01450_vCenterHostProfiles, Line 183, Message: @statement_id=9100;Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.

[firestartah]

Hi

It looks like from your error it is down to the collation on your SQL server DB

"Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS"

[stubbint]

Hi Firestartah

Yes, you are correct. The SQL database server uses the  "Latin1_General_CI_AS, which appears to be the default for a SQL 2008R2 installation.

Unfortunately I have a central SQL server with a number of databases already running (including VC, VUM and VCOP's and others) so changing the option (reinstalling SQL) is going to be a bit of a problem. As is finding the cash for more SQL licenses if I use a fresh install on another server. I'll have to scratch my head for a while and come up with another plan.

Thanks for your help.

regards

Trev.

[firestartah]

Hi

You can just remove the VCM specific DB and recreate it and change the collation in there. no need to rebuild the whole SQL server

Gregg

[firestartah]

Did you get this fixed in the end?