Support Tip: Reports fail to show up after installing a ConfigMgr 2012 Reporting Service Point

Support Tip: Reports fail to show up after installing a ConfigMgr 2012 Reporting Service Point

  • Comments 5
  • Likes

Prabhat JoshiHello Everyone, Prabhat Joshi here with another System Center 2012 Configuration Manager support tip for you, this time for reporting services.

At times we have seen issues wherein after installing a ConfigMgr 2012 Reporting Services Point we don't see reports either in the console or under the report manager URL. It’s also possible that you will see some reports but others are missing.

If you check srsrp.log you’ll see entries similar to the ones below.

System.Web.Services.Protocols.SoapException: The path of the item 'Site - General' is not valid. The full path must be less than 260 characters long; other restrictions apply. If the report server is in native mode, the path must start with slash. ---> Microsoft.ReportingServices.Diagnostics.Utilities.InvalidItemPathException: The path of the item 'Site - General' is not valid. The full path must be less than 260 characters long; other restrictions apply. If the report server is in native mode, the path must start with slash.~ at Microsoft.ReportingServices.Library.ReportingService2005Impl.GetPolicies(String Item, Policy[]& Policies, Boolean& InheritParent)~ at Microsoft.ReportingServices.WebServer.ReportingService2005.GetPolicies(String Item, Policy[]& Policies, Boolean& InheritParent)

Failed to retrieve existing folder security for folder [Site - General].

System.Web.Services.Protocols.SoapException: The path of the item 'Site - Server Information' is not valid. The full path must be less than 260 characters long; other restrictions apply. If the report server is in native mode, the path must start with slash. ---> Microsoft.ReportingServices.Diagnostics.Utilities.InvalidItemPathException: The path of the item 'Site - Server Information' is not valid. The full path must be less than 260 characters long; other restrictions apply. If the report server is in native mode, the path must start with slash.~ at Microsoft.ReportingServices.Library.ReportingService2005Impl.GetPolicies(String Item, Policy[]& Policies, Boolean& InheritParent)~ at Microsoft.ReportingServices.WebServer.ReportingService2005.GetPolicies(String Item, Policy[]& Policies, Boolean& InheritParent)

Failed to retrieve existing folder security for folder [Site - Server Information].

If you find yourself in this situation then here are a couple of steps to fix it:

- Start by compiling sqlmgmproviderxpsp2up.mof by running the command below:

mofcomp.exe C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof

This should help when you cannot see the reports in the console or reports are not getting copied over.

- If you have some reports that are missing and you also see intermittent health check failures in srsrp.log, check the reporting services log under <drive>:/Program Files/Microsoft SQL Server/<Instance ID>/Reporting Services/LogFiles. A good log to check is ReportServerService_<timestamp>.log as it logs all errors and will provide a complete call stack that should explain why we got an error message.

If you see an entry that mentions something like "Only one usage of each socket address (protocol/network address/port) is normally permitted ::1:80" in the above mentioned log, run the command netstat –ano and check the number of open ports (i.e. connections). If you see a relatively small number of connections (e.g. 240) then run the command netsh int ipv4 show dynamicport tcp. Here’s an example of the output we got on an affected machine:

Protocol tcp Dynamic Port Range
---------------------------------
Start Port : 20000
Number of Ports : 240

This tells us that we may not have access to the ports we need. Try changing the amount of ports by running the command netsh int ipv4 set dynamicportrange protocol=tcp start 40000 numberofports=20000.

NOTE This opened 20000 ports after tcp port 40000 so that the Reporting Services Point can more easily find an open port.

Once the command above is run, restart reporting services. If this was your issue, reports should now start showing up and fix your intermittent health check failures as well.

Prabhat Joshi | Technical Lead | Microsoft

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection 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/

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment