Just a heads up on a new ConfigMgr 2007 Knowledge Base article we published today where a Reporting point fails with 'SRS root folder "configmgr_<sitecode>" is not present':
=====
Symptoms
The Microsoft System Center Configuration Manager 2007 Reporting Services point (ConfigMgr 2007 SRS) may report the following errors in the SMS_SRS_REPORTING_POINT Component Status Log:
SMS_SRS_REPORTING_POINT 7404 SRS is not installed or properly configured on SRS Reporting point server "<servername>".
Cause
This error can occur if the Copy Reports to Reporting Services Wizard has not been run on the server. This is a manual step that must be completed to create the default reporting structure that the component expects. This error will be logged every time the Reporting Services SMS_SRS_REPORTING_POINT thread restarts.
Resolution
To correct this error use the following steps:
1. Run the Configuration Manager 2007 Administration Console as an administrator and navigate to Site Database\Computer Management\Reporting\Reporting Services\<SERVERNAME> (where <SERVERNAME is the name of your Reporting Services server).
2. Right-click on Reporting Services and choose Copy Reports to Reporting Services
3. Follow the wizard, using the appropriate choices as outlined in http://technet.microsoft.com/en-us/library/cc161781.aspx
4. Restart the SMS_SRS_REPORTING_POINT thread in ConfigMgr Service Manager.
=====
For the latest version of this article see the link below:
J.C. Hornbeck | System Center Knowledge Engineer
The App-V Team blog: http://blogs.technet.com/appv/
The WSUS Support Team blog: http://blogs.technet.com/sus/
The SCMDM Support Team blog: http://blogs.technet.com/mdm/
The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
The SCOM 2007 Support Team blog: http://blogs.technet.com/operationsmgr/
The SCVMM Team blog: http://blogs.technet.com/scvmm/
The MED-V Team blog: http://blogs.technet.com/medv/
The DPM Team blog: http://blogs.technet.com/dpm/
The OOB Support Team blog: http://blogs.technet.com/oob/
The Opalis Team blog: http://blogs.technet.com/opalis