Hi everyone, Tyler Franke here again with one more issue I ran into recently. Consider a scenario where you have your System Center Configuration Manager 2007 (ConfigMgr) site database on a remote/dedicated SQL Server wherein a drive fails or has to be replaced. Afterward, the 'Backup ConfigMgr Site Server' site maintenance task fails to run and the following site status error messages are found under SMS Component manager thread:
SMS Site Component Manager could not create the SMS server components' installation directory "I:\SMS_site_server_name" on site system "\\My_SQL_Server" or set the correct permissions on the directory. The operating system reported error 53: The network path was not found.
Possible cause: The destination drive is full.
Solution: Make more space available on that drive.
Possible cause: The site system is not exporting the default drive letter shares, such as "\\My_SQL_Server\C$", "\\My_SQL_Server\D$", and so on.
Solution: You might have disabled the default drive letter shares for security purposes. SMS requires these shares. Please re-enable these shares using the Windows NT Disk Administrator.
Possible cause: The site system is turned off, not connected to the network, or not functioning properly.
Solution: Verify that the site system is turned on, connected to the network, and functioning properly.
This occurs as a result of the ConfigMgr site server not being able to access the folders and files on the SQL server site system.
<drive-letter>:\SMS_site_server_name\srvacct\srvacct.<site_code> (e.g. srvacct.PR1)
NOTE The last folder shown above (i.e. srvacct) is a hidden folder
Please take the following steps to resolve:
1. On the site server, click on the start menu and navigate to Microsoft System Center-> Configuration Manager 2007, then click on “ConfigMgr Setup”.
2. Once the setup wizard appears on the screen click next on the Welcome page.
3. On the available setup options page, select “Perform site maintenance or reset this Site” and click Next.
4. On the site maintenance page, select only the “Modify SQL Server Configuration” option and then click Next.
5. On the SQL Server Configuration page, verify the existing information is correct for the SQL Server instance and site database names, then click Next and wait for the process to complete.
In a situation where the drive has not failed and/or changed and only the drive-letter was changed you can most likely resolve this by simply going into the registry of the SQL Server under HKLM\System\CurrentControlSet\services\SMS_SITE_SQL_BACKUP and changing the value of the "ImagePath" string value to reflect the new and correct drive-letter.
Tyler Franke | Senior Support Escalation Engineer
App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/
The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/