If there are any problems that arise during the course of usage, below is a list
of symptoms with resolutions.
503 - Service Unavailable
When deploying, the message "The request failed with HTTP status 503: Service Unavailable"
appears. You may also receive a similar message when you test the service from the
Globals tab via the "Test" button adjacent to the Web service URL.
- Resolution: The SSRS deployment/publish service requires SSRS to be started (also
make sure it has a Startup Type of Automatic). Go to Control Panel | Administration
| Local/Services | SQL Server Reporting Services | right-click and select Start
- Note that the SSRS service name depends on the target SSRS instance
The report server cannot open a connection to the report server database
When deploying, the message "The report server cannot open a connection to the report
server database (rsReportServerDatabaseUnavailable)" appears.
- Resolution: The SSRS deployment/publish requires SQL Server to be started (also
make sure it has a Startup Type of Automatic) as it needs to access the SSRS database.
Go to Control Panel | Administration | Local/Services | SQL Server (SQL-Server-instance-name)
| right-click and select Start.
- Note that the SQL Server service name depends on the target SSRS instance
Subscriptions - SQL Agent
If subscriptions are being published, the deployment will fail if the SQL Agent
service is not Started
- Resolution: Make sure the target server has the SQL Agent server started (and has
a Startup Type of Automatic). Go to Control Panel | Administration | Local/Services
| SQL Server Agent | right-click and select Start.
- Note that the SQL Server Agent service name depends on the target SSRS instance
As objects are uploaded (i.e. at publish time) SSRS validates to make sure the references
entered actually exist (eg. the deployment will fail if a connection string contained
within a data source does not resolve)
- Resolution: Test such things as connection strings with the credentials supplied
and amend accordingly
SSRS objects can also upload when references within the object do not resolve (eg.
if a report contains a dataset that doesn't exist in any of the folders the tool
is aware of, the tool cannot link the two and the publish will fail)
- Resolution: Make sure all targets are entered into the publisher configuration file
Subscriptions delivery (file) path
If the deployment fails due to the target delivery (file) path not being in UNC
format - the error message "A delivery error has occurred. ---> Microsoft.ReportingServices.Diagnostics.Utilities.InvalidExtensionParameter:
One of the extension parameters is not valid for the following reason: The path
is not valid. The path must conform to Uniform Naming Convention (UNC) format" is
- Resolution: Within the rsNeatPublish.XmlGenerator Subscriptions tab select the subscription's
'Report delivery options', then enter a UNC 'Path' that exists and has the appropriate
Deployment - Failure Due to Permissions
If the deployment fails due to permissions, and you are confident the account the
deployment is running under has sufficient access, it is likely that the user that
the deployment is running under does not have sufficient privileges because of Windows
UAC (User Access Control).
- Resolution: rsNeatPublish needs to be "Run as administrator" - eg. if run on the
command line open the command prompt as administrator; similarly if run from the
rsNeatPublisher.XmlGenerator UI, run rsNeatPublish.XmlGenerator as administrator.
Deployment - Failure Due to Schema Version Conflict
If the deployment fails due to schema version conflict - the error message "The
definition of this report is not valid or supported by this version of Reporting
Services. The report definition may have been created with a later version of Reporting
Services, or contain content that is not well-formed or not valid based on Reporting
Services schemas" is received
- Resolution: It is likely the report(s) being deployed was saved using a version
of Visual-Studio/BIDS that is not compatible with the SSRS instance version. When
saving a report within Visual Studio the RDL (report definition language) schema
used is aligned to the Visual Studio version. The target SSRS instance version will
only accept particular RDL schema versions. For this reason if this message appears
follow the steps below
- Go to the Project's | Properties dialog
- Change the TargetServerVersion to the target SSRS instance version
- Rebuild the project
- Within rsNeatPublish.XmlGenerator open the relevant rsNeatPublish XML Configuration
- On the Globals tab, change the "Source path" field to point to the folder that was
the destination of the re-build (typically this is just a case of adding "\bin\Debug"
onto the end of what you have currently assuming you have rebuilt against the Debug
build config - eg. if you had C:\Projects\MySsrsProject, change this to C:\Projects\MySsrsProject\bin\Debug)
- Re-publish (can be done within rsNeatPublish.XmlGenerator via Publish! | Save and
Publish to Server)