Hi! We would like to upgrade our SCCM 2007 to SP1, but we get the following errors which block the installation process: - WSUS 3.0 SP1 is required on site server - SMS Provider Communication and a couple of warnings... BUT, the problem is, we don't have any WSUS configured on this server, and into SCCM too (no WSUS role, except for Component Configurationwhere we have a Software Update Point Component which we could not delete!). How we could completely remove anything related to WSUS in SCCM??? And for the SMS Provider error, yes our SQL SCCM instance use the local system account, but does it exist a way to avoid this error (we don't want to reconfigure the SQL SCCM instance)? Thanks. Claude Lachapelle Systems Administrator, MCSE

Found what was the problem with the WSUS 3.0... now weonly have awarning for the WSUS 3.0 SDK? What's this? Regarding SMS Provider Communication error... does it is really required to used an Active Directory user account for our SQL Server SCCM instance or we could avoid this verification into the Prereq checker? Thanks. Claude Lachapelle Systems Administrator, MCSE

Incredible but true, now the SQL SCCM instance run using a domain service account, but we still have the SMS Provider Communication error... Here the error message found into configmgrprereq.log: SMS Provider Communication; Error; A communication error has been detected between the SMS Provider computer and the site database computer. This error can occur when the site database server is offline or if a valid SPN has not been registered in Active Directory Domain Services for the SQL Server instance hosting the site database. Setup cannot continue. What's wrong? Claude Lachapelle Systems Administrator, MCSE

Just before specifying the SMS Provider Communication error, we always get: Could not open \\smsserver\admin$\sccm_sysroletosql_connect_test.rst And the file does not exist... Still having the same problem when running setup /prereq /pri /sql <sqlservername> This is becoming a nightmare! Claude Lachapelle Systems Administrator, MCSE

It seems as if there are major problems that possibly cannot be resolved here at the forums. You might consdier calling PSS/CSS. There's one thing you did not mention: are all your sitesystems on one box or are the located on different boxes?

Finally we got it to work... but for only few minutes, setup failed with an unexpected error during the upgrade process!!! Now, this is worst than before, the actual installation have been seriously altered, we could not start the console anymore. We restored the SCCM server from the backup (OS, system state, all files), but even if we do a site reset (the database is located on another server/SQL server), we always get when starting the console (even from another pc): ConfigMgr Error Object: instance of __ExtendedStatus { Operation = "ExecQuery"; ParameterInfo = "SELECT * FROM SMS_Site WHERE ReportingSiteCode = ''"; ProviderName = "WinMgmt"; }; Error Code: ProviderLoadFailure What a bad experience... very bad. What's next? We are seriously thinking of re-installing everything from scratch, since technical support people could not build PCs anymore. NOTE: On the SCCM server, we have no error message from the application and system event logs, and from all SCCM logs files, everything seem to be ok!!! Strange... does the WHERE ReportingSiteCode = "" have something to do with the problem we have??? Thanks. Claude Lachapelle Systems Administrator, MCSE

I have no clue as to your error. Howvever, for the WSUS SDK, it never was an error, only a warning. If you want to do automated patch management using Configuration Manager, we require WSUS 3.0 SP1 (if you are using Configuration Manager SP1). We look to see if it (it being at least the WSUS admin console) is installed on the site server. If not, then you get this warning. But as to the failure, the common issues with SQL Server are: * the site server computer account requires admin rights to the physical SQL Server computer * your SQL Server SPNs must be registered properly * attempting to use a wrong version of SQL Server, such as MDSE or something like that Oh, and I could not argue against you starting from scratch, unless you had a lot of data that you needed to keep. If so, then customer support would be the thing to do.

I had a similar error and therefore would like to share my story.After upgrading SCCM 2007 to Service Pack 1I was unable to connect to the site server using the Configuration Manager console. The error was very generic, "The ConfigMgr console could not connect to the ConfigMgr site database". The server log files lookedclean and I verified that the SQL server was running properly by running reports from the IIS website, http://servername/SMSReporting_SiteCodeThe smsAdminUI.log showed the same errors that clachapelle listed:instance of __ExtendedStatus{Operation = "ExecQuery";ParameterInfo = "SELECT * FROM SMS_Site WHERE ReportingSiteCode = ''";ProviderName = "WinMgmt";};I could be wrong about this assumption, but I assumed that the select statementshould be looking aReportingSiteCode that matched my site's three letter code. Since it was looking for a nul value I assumed that my three letter code was missing from a MOF file. By usingwbemtest.exe I was able to confirm this assumption. The solution was simply to recompile the MOF. I ran the following command from the site server'scommand line and the console came back to life.mofcomp "C:\Program Files (x86)\Microsoft Configuration Manager\bin\i386\smsprov.mof"

For all that I remember, The WSUS SDK is nothing more than than the management console. do you have that installed?

I just ran into this .... I removed the test file that it was copying. I believe it might had been UAC that was disabling the overwriting of this file while run under domain creditials(not elevated). Remove the following file and rerun setup \\smsserver\admin$\sccm_sysroletosql_connect_test.rst

Hi, You might want to refer to kevin remde's post You can easily find free tools and instructions such as the Microsoft Deployment Toolkit at http://www.microsoft.com/deployment or http://www.microsoft.com/mdt. For patch management you can look at the free Windows Server Update Service (WSUS) (http://www.microsoft.com/wsus). And for a more enterprise-class solution you could consider System Center Configuration Manager (http://www.microsoft.com/sccm), but that's probably more than you need. A relatively new option is a product called Windows InTune. It's a cloud-based desktop monitoring solution that will let you watch for issues such as patch levels on systems you're monitoring. (http://www.windowsintune.com). Hope this gets you started, Guowen Su | CCNA, CCIP, MCP, MCSA, MCSE, MCTS, MCITP, CEH | http://www.microsoft.com/en/sg/default.aspx Our Goal? VERY SATISFIED Customers. If you're not...let's talk!!