SCCM Prerequisite check problem
Hi I need to update our SCCM infrastructure to R3. As we're currently only running SP1 R2 I need to upgrade to SP2 first. I'm running the prerequisite check for SP2 and receiving three warnings: MMC updates for Configuration Manager (Software Updates) Client Duplicate IDs SQL Server security mode I downloaded the relevant hotfix for the MMC warning and attempted to install but received a message that the currently installed service pack superseded the hotfix and was not required. I believe there is a know issue with this warning appearing erroneously? For the second warning I've looked through the ConfigMgrPrereq.log and manually ran the query that triggers the warning against our SCCM database. I receive seven results from the query with a total of four unique GUIDs. I have the global setting to automatically resolve conflicting records set and nothing appears under the conflicting records section of the SCCM console. Is it possible to resolve these manually while the automatic setting is configured? http://technet.microsoft.com/en-us/library/bb693963.aspx instructs me to resolve the records by selecting them in the console but obviously I can't do this if nothing is appearing. The SQL server hosting our site database is configured for SQL Server and Windows Authentication mode as it is also hosting another DB for which I believe this is required. The detailed description of this warning states that it is recommended to use Windows Authentication mode only, am I likely to encounter problems if I install SP2 and R3 with this mode still configured? The next problem I have is with the setup.exe /testdbupgrade check. I've successfully backed up our site and database from within the SCCM console. I was under the impression that I needed to restore the database on a separate machine running the same version of SQL but that this server does not need to have SCCM installed from reading http://technet.microsoft.com/en-us/library/bb693648.aspx. I've installed SQL Server 2005 on a VM and then attached the SCCM database in SQL Management Studio from the backup and log file generated by the SCCM backup service. When I run setup.exe /testdbupgrade <copied database name>. In ConfigMgrPrereq.log I get: <02-23-2011 16:49:39> ******************************************** <02-23-2011 16:49:39> ******* Start Prerequisite checking. ******* <02-23-2011 16:49:39> ******************************************** <02-23-2011 16:49:39> CPrereqManager: - Since Registry values empty, this is for fresh installation. In ConfigMgrSetup.log I get: ===================== << Starting SMS V4 SP2 Upgrade Setup >> ===================== <02-23-2011 16:49:39> Commandline : setUp.exe /testdbupgrade SMS_SHF <02-23-2011 16:49:39> This is 32 bit. <02-23-2011 16:49:39> Verifying the Reg for AssetIntelligence Installation <02-23-2011 16:49:39> Setting the default CSV folder path <02-23-2011 16:49:39> SMS Build Number = 6487 <02-23-2011 16:49:39> SMS Version = 4.0 <02-23-2011 16:49:39> SMS Minimum Build Number = 800 <02-23-2011 16:49:39> Verifying SMS Active Directory Schema Extensions. <02-23-2011 16:49:39> DS Root:CN=Schema,CN=Configuration,DC=****,DC=***,DC=** <02-23-2011 16:49:39> Verifying SMS Active Directory Schema Extensions. <02-23-2011 16:49:39> DS Root:CN=Schema,CN=Configuration,DC=****,DC=***,DC=** <02-23-2011 16:49:39> The command line options are /TESTDBUPGRADE SMS_SHF <02-23-2011 16:49:39> Registered type PACKAGINGVM MASTER for PACKAGINGVM master <02-23-2011 16:49:39> Registered type SMS Master for PACKAGINGVM master <02-23-2011 16:49:39> Registered type PACKAGINGVM SMS_SHF for PACKAGINGVM SMS_SHF <02-23-2011 16:49:39> Registered type SMS ACCESS for PACKAGINGVM SMS_SHF <02-23-2011 16:49:39> Testing database upgrade on SMS_SHF database, on the PACKAGINGVM server. <02-23-2011 16:49:39> Running test query. <02-23-2011 16:50:40> ***SqlError: [08001][17][Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access denied. <02-23-2011 16:50:40> ***SqlError: [01000][2][Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen (Connect()). <02-23-2011 16:50:40> Running test query. <02-23-2011 16:51:42> ***SqlError: [08001][17][Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access denied. <02-23-2011 16:51:42> ***SqlError: [01000][2][Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen (Connect()). <02-23-2011 16:51:42> Test query to sql database SMS_SHF failed. I don't know whether this is just indicating outright that the database upgrade will fail, possibly due to the fact the SQL server is in mixed authentication mode? I've tried changing the setting to mixed and windows authentication on the VM but get the same result with each. Also worth noting is the OS on my VM is XP SP3 simly because I had one sat ready. Our production DB server is Server 2003, I wasn't sure if my VM needed the same OS as this isn't mentioned in the kb. Our SCCM environment consists of a single site with no secondary site servers. Our database is hosted on a cluster, again I'm not sure if this has any impact on running testdbupgrade. Any help much appreciated and apologies for the fact this is a bit of a bloaty post. Thanks Stewart
February 26th, 2011 5:51am

Is anyone able to offer any advice at all on this? Cheers
Free Windows Admin Tool Kit Click here and download it now
March 21st, 2011 5:06pm

MMC updates: I can't recall the hotfix number (and you did not mention it in your post), but there was some confusion about the naming IIRC. Aren't there -SP2 and -SP3 hotfixes available? Have you tried installing both? Duplicate GUIDs: just examine those clients. Are they still online? If so: you tranguid.exe to generate a new GUID for them. Or just ignnore that warning. SQL: you can also restore the DB to the server where the ConfigMgr DB is hosted, no need for a separate server. You are experiencing an 'access denied' error, so double check the permissions and check the SQL logs (using SQL management studio). Torsten Meringer | http://www.mssccmfaq.de
March 21st, 2011 6:06pm

Hi Torsten Thanks for your reply. You're quite right, it looks like there's an SP3 version of the hotfix available further down the page which I hadn't seen. I've installed this and the MMC warning has now gone from the prereq check, I'll take a look at the duplicate GUIDs and remedy them individually. I'll also try restoring the database backup against our production server instead and see if I get different results. Thanks again for your help Stewart
Free Windows Admin Tool Kit Click here and download it now
March 22nd, 2011 1:09pm

One other question Torsten, in relation to restoring the SQL database. When I run the site backup job in SCCM it generates an MDF and associated log file. In SQL Management Studio, if I right click Databases and select Attach I can select my MDF file. As this has the same name as our production database, will this not overwrite or merge the live version with the backup data? Thanks Stewart
March 22nd, 2011 1:31pm

I have seen similar errors which was just related of missing permissions. Check if you can log on with a SQL admin account and try it again.Follow me through my blog and Twitter!
Free Windows Admin Tool Kit Click here and download it now
March 22nd, 2011 11:03pm

After messing about with the permissions for ages I finally spotted the problem and it turned out to be something completely different. I'd attached the SMS database backup as a SQL named instance. Whilst I'd already tried running /testdbupgrade <server>\<instance>\<SMS_DB> I hadn't realised that I didn't need the server in the string. I ran /testdbupgrade with just <instance>\<SMS_DB> and it runs fine. However, just as I was rejoicing in my progress I then got an error stating "Setup cannot upgrade the ConfigMgr database. Contact your SQL administrator." At least it turns out all my effort in running the /testdbupgrade was a worthwhile process. In ConfigMgrSetup.log I get: <03-31-2011 14:35:55> ***SqlError: [42000][468][Microsoft][ODBC SQL Server Driver][SQL Server]Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation. Followed by: <03-31-2011 14:35:55> Cannot execute sql command IF OBJECT_ID('#GroupList') IS NOT NULL drop table #GroupList CREATE TABLE #GroupList ( GroupName varchar(255), ClassName varchar(255), SpecificTableName varchar(255) ) insert into #GroupList(GroupName,ClassName,SpecificTableName) values('Workstation Status', 'MICROSOFT|WORKSTATION_STATUS|1.0', 'WorkstationStatus_DATA') insert into #GroupList(GroupName,ClassName,SpecificTableName) values('Add Remove Programs', 'MICROSOFT|ADD_REMOVE_PROGRAMS|1.0', 'Add_Remove_Programs_DATA') insert into #GroupList(GroupName,ClassName,SpecificTableName) values('Add Remove Programs (64)', 'MICROSOFT|ADD_REMOVE_PROGRAMS_64|1.0', 'Add_Remove_Programs_64_DATA') insert into #GroupList(GroupName,ClassName,SpecificTableName) values('BIOS', 'MICROSOFT|PC_BIOS|1.0', 'PC_BIOS_DATA') insert into #GroupList(GroupName,ClassName,SpecificTableName) values('CD-ROM', 'MICROSOFT|CDROM|1.0', 'CD_ROM_DATA') insert into #GroupList(GroupName,ClassName,SpecificTableName) values('Computer System', 'MICROSOFT|COMPUTER_SYSTEM|1.0', 'Computer_System_DATA') insert into #GroupList(GroupName,ClassName,SpecificTableName) values('Disk', 'MICROSOFT|DISK|1.0', 'Disk_DATA') insert into #GroupList(GroupName,ClassName,SpecificTableName) values('Partition', 'MICROSOFT|PARTITION|1.0', 'Partition_DATA') insert into #GroupList(GroupName,ClassName,SpecificTableName) values('Logical Disk', 'MICROSOFT|LOGICAL_DISK|1.0', 'Logical_Disk_DATA') insert into #GroupList(GroupName,ClassName,SpecificTableName) values('Memory', 'MICROSOFT|X86_PC_MEMORY|1.0', 'PC_Memory_DATA') insert into #GroupList(GroupName,ClassName,SpecificTableName) values('Modem', 'MICROSOFT|MODEM_DEVICE|1.0', 'Modem_DATA') insert into #GroupList(GroupName,ClassName,SpecificTableName) values('Motherboard', 'MICROSOFT|MOTHERBOARD_DEVICE|1.0', 'Motherboard_DATA') insert into #GroupList(GroupName,ClassName,SpecificTableName) values('Network Adapter', 'MICROSOFT|NETWORK_ADAPTER|1.0', 'Netcard_DATA') insert into #GroupList(GroupName,ClassName,SpecificTableName) values('Network Adapter Configuration', 'MICROSOFT|NETWORK_ADAPTER_CONFIGURATION|1.0', 'Network_DATA') insert into #GroupList(GroupName,ClassName,SpecificTableName) values('Network Client', 'MICROSOFT|NETWORK_CLIENT|1.0', 'Network_Client_DATA') insert into #GroupList(GroupName,ClassName,SpecificTableName) values('Operating System', 'MICROSOFT|OPERATING_SYSTEM|1.0', 'Operating_System_DATA') insert into #GroupList(GroupName,ClassName,SpecificTableName) values('Parallel Port', 'MICROSOFT|PARALLEL_PORT|1.0', 'Parallel_Port_DATA') insert into #GroupList(GroupName,ClassName,SpecificTableName) values('Pointing Device', 'MICROSOFT|POINTING_DEVICE|1.0', 'Mouse_DATA') insert into #GroupList(GroupName,ClassName,SpecificTableName) values('Keyboard', 'MICROSOFT|KEYBOARD_DEVICE|1.0', 'Keyboard_DATA') insert into #GroupList(GroupName,ClassName,SpecificTableName) values('Processor', 'MICROSOFT|PROCESSOR|1.0', 'Processor_DATA') insert into #GroupList(GroupName,ClassName,SpecificTableName) values('SCSI Controller', 'MICROSOFT|SCSI_CONTROLLER|1.0', 'SCSI_Controller_DATA') insert into #GroupList(GroupName,ClassName,SpecificTableName) values('Services', 'MICROSOFT|SERVICE|1.0', 'Services_DATA') insert into #GroupList(GroupName,ClassName,SpecificTableName) values('Tape Drive', 'MICROSOFT|TAPE_DRIVE|1.0', 'Tape_Drive_DATA') insert into #GroupList(GroupName,ClassName,SpecificTableName) values('Desktop Monitor', 'MICROSOFT|DESKTOP_MONITOR|1.0', 'Desktop_Monitor_DATA') insert into #GroupList(GroupName,ClassName,SpecificTableName) values('IDE Controller', 'MICROSOFT|IDE_CONTROLLER|1.0', 'IDE_Controller_DATA') insert into #GroupList(GroupName,ClassName,SpecificTableName) values('Sound Devices', 'MICROSOFT|SOUND_DEVICE|1.0', 'Sound_Devices_DATA') insert into #GroupList(GroupName,ClassName,SpecificTableName) values('USB Controller', 'MICROSOFT|USB_CONTROLLER|1.0', 'USB_Controller_DATA') insert into #GroupList(GroupName,ClassName,SpecificTableName) values('Video Controller', 'MICROSO Above is exactly how the error appears in the log file with Microsoft truncated at the end. Has anyone seen this before? Many thanks Stewart
March 31st, 2011 10:04am

<03-31-2011 14:35:55> ***SqlError: [42000][468][Microsoft][ODBC SQL Server Driver][SQL Server]Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation. See that article that talks about the collection settings: http://technet.microsoft.com/en-us/library/bb680951.aspxTorsten Meringer | http://www.mssccmfaq.de
Free Windows Admin Tool Kit Click here and download it now
March 31st, 2011 10:46am

I think I've spotted the reason I'm getting the above error. It looks like the server collation on my VM is SQL_Latin1_General_CP1_CI_AS whereas on the live DB server it's Latin1_General_CI_AS. It sounds like changing the server collation is no easy task for an existing instance so Looks like I'll need to reinstall SQL with the correct collation setting on my VM.
March 31st, 2011 11:19am

After reinstalling SQL with the correct collation setting I've now managed to successfully run /testdbupgrade against my database copy with no issues. Thank you very much for your assistance. Stewart
Free Windows Admin Tool Kit Click here and download it now
April 1st, 2011 7:32am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics