Last updated: November 14, 2026
Use this guide to diagnose common SSRS Reports Migration Wizard issues. Most migration problems involve permissions, target-server configuration, data-source connectivity, or credentials.
Quick Checks for Common Connection Errors #
Use the response code and the stage of the migration to narrow down the cause. These checks complement the detailed issue-specific guidance below.
- HTTP 401 — Unauthorized: Check the selected authentication method and credentials. Confirm that the account can access the Report Server Web Service URL, and run the wizard under the intended Windows account if using current domain credentials.
- HTTP 403 — Forbidden: The request reached the server, but the account may lack the required folder-level or system-level role. Review the Prerequisites and permissions, including system permissions for shared schedules.
- TLS/SSL or certificate errors: Use the correct HTTPS endpoint and verify that the certificate is trusted, valid, and issued for the server name in the URL. Do not disable certificate validation as a workaround.
- Timeout, connection refused, or server not found: Verify the Report Server URL and port, DNS resolution, firewall rules, proxy/VPN routing, and that the report server endpoint is reachable from the computer running the wizard.
- Failure while creating or updating an existing target item: Check whether an item already exists at the mapped target path, whether the migration account can update it, and the target ReportServerService log for the corresponding timestamp.
If these checks do not identify the cause, use Retrieve Detailed Errors from SSRS Report Server Logs. That section explains which source or target logs to collect, how to correlate entries with the migration action, and how to redact sensitive information before sharing logs.
AccessDenied When Creating or Updating a Dataset #
An AccessDenied error during dataset creation or update may indicate that the migration account lacks the required effective item-level permission at the destination. SSRS site-level system roles and item-level catalog roles are separate. A System Administrator site role alone does not grant permission to create or update items in a catalog folder.
- Check the effective item-level role on the exact parent folder where the dataset is being created or updated.
- Check whether folder permission inheritance is disabled or overridden on that folder.
- The migration may overwrite an existing dataset at the mapped target path, so the account may need update permission as well as permission to create a new item.
Compare the task with the item-level role matrix in Prerequisites → Required Permissions. Do not treat a system-level role as a substitute for the catalog-folder role.
1. Data-Driven Subscriptions Fail to Import #
Data-driven subscriptions may fail to import when the target report server cannot connect to the data sources used by the report.
Common causes #
- Required database drivers or client providers are missing on the target server, such as an Oracle provider.
- The connection string, server name, database name, or connection identifier is invalid for the target environment.
- Data-source credentials are missing, incorrect, expired, or unavailable to a background subscription process.
- The target server cannot reach the database because of firewall, DNS, routing, or authentication restrictions.
Resolution #
- Open the Migration Wizard’s Manage Connection Properties screen and verify every data source.
- Confirm that the target server has the required database drivers and can connect to each database.
- Validate connection strings and database permissions using the same account configured for the report.
- For subscriptions, use a supported non-interactive credential configuration, normally stored credentials or a correctly configured execution account.
- For the SQL Server Agent requirement for scheduled subscriptions, see Prerequisites.
2. “The user data source credentials do not meet the requirements to run this report or shared dataset” #
Error message: The user data source credentials do not meet the requirements to run this report or shared dataset. Either the user data source credentials are not stored in the report server database, or the user data source is configured not to require credentials but the unattended execution account is not specified.
This means SSRS cannot execute the report in a background context using the configured data-source authentication method. For source-password and subscription credential handling, see Getting Started.
Common causes #
- The data source uses credentials supplied by the user rather than stored credentials.
- Windows Integrated Security is configured, but the report server service account or execution context does not have database access.
- The data source uses No Credentials, but an unattended execution account has not been configured where required.
- Source stored credentials are not migrated by the wizard. Re-enter and validate the required credentials on the target report server.
- The configured account lacks the required permissions on the database, views, stored procedures, or other referenced objects.
Resolution #
- Open the affected report or shared dataset’s data-source properties on the target server.
- For subscriptions, configure Credentials stored securely in the report server and enter an account with the required database permissions, if permitted by your security policy.
- If using Windows Integrated Security or No Credentials, configure and validate the appropriate unattended execution account in Report Server Configuration Manager.
- Check that the account can execute all required queries, views, and stored procedures.
- If the report uses multiple data sources, validate every data source—not only the one shown in the first error.
3. HTTP 500 Error When Retrieving Shared Schedules #
Error message: Response status code does not indicate success: 500 (Internal Server Error)
Important: In this scenario, the HTTP 500 response can indicate missing SSRS site-level permissions. It does not necessarily mean that the report server has crashed or needs to be restarted.
Shared schedules are system-level SSRS objects. Folder-level permissions alone are not sufficient to enumerate or create them.
Required permissions #
Shared schedules require system-level permissions. Use the role matrix and Site Settings instructions in Prerequisites → Required Permissions for the source and target role requirements.
Note: System User may be sufficient on the source for reading schedules, but it is not sufficient on the target when the migration must create shared schedules.
Continue without shared schedules #
If your organization cannot grant the required system permissions, the wizard can offer the option to continue without shared schedule migration when you select subscription migration. Subscriptions can still be migrated, but shared schedule assignments will not be recreated.
4. Reports or Datasets Fail After Migration #
If reports or shared datasets migrate successfully but fail when opened on the target server, check the target environment before repeating the migration.
- Verify that every migrated data source exists and is associated with the correct report or dataset.
- Check connection strings, database names, authentication method, and stored credentials.
- Confirm that the target report server can reach the database and that the account has the required permissions.
- Install any required database drivers or providers on the target server.
- Review the SSRS execution log and Windows Event Viewer for the underlying provider or authentication error.
5. Retrieve Detailed Errors from SSRS Report Server Logs #
When the wizard reports a generic error, retrieve the detailed error from the source or target report server. Check the source when reading or exporting reports, subscriptions, schedules, or data sources; check the target when creating or updating migrated items.
Step 1: Identify the affected report server #
- Open the failed item’s detailed message or trace in the wizard and record the diagnostic timestamps. For SOAP HTTP 500 errors, the wizard may show both the client-local timestamp and its UTC equivalent.
- Identify whether the failed operation occurred on the source or target report server. Use the server identification shown in the wizard rather than assuming which endpoint failed.
- Record the SOAP operation, endpoint URL, affected catalog item/path, and complete exception details where available.
Step 2: Open the SSRS log folder #
On the affected report server, locate the SSRS log directory. The default location is commonly:
C:\Program Files\Microsoft SQL Server\MSRS<version>.<instance>\Reporting Services\LogFiles
The exact folder depends on the SQL Server/SSRS version and instance name. You can also locate it from Reporting Services Configuration Manager or search the server for the Reporting Services\LogFiles directory.
Step 3: Review the relevant log files #
- ReportServerService_*.log — Report server service activity, report execution, subscriptions, data-source access, and server-side exceptions.
- Microsoft.ReportingServices.Portal.WebHost_*.log — Web portal activity and portal-side errors, when available.
- HTTPERR, IIS, or Windows Event Viewer logs — Useful for HTTP, hosting, authentication, service, or connectivity failures.
Step 4: Search around the failure time #
- Open the newest log file in a text editor with administrator access if required.
- Search for the failure time, report name, folder path, subscription name, correlation/activity ID, or terms such as
ERROR,WARN,Exception,Unauthorized,Access denied,timeout, anddatabase. - Read several lines before and after the matching entry. The first visible error may be only a wrapper; the inner exception often contains the actual cause.
- Repeat the search on the other report server if the migration involves both source and target operations.
Step 5: Correlate the log entry with the migration action #
| Migration symptom | Log location to check first |
|---|---|
| Cannot read or export a source report | Source ReportServerService log |
| Cannot retrieve subscriptions or shared schedules | Source ReportServerService log and source security-related events |
| Report, dataset, or data source creation fails | Target ReportServerService log |
| Subscription or schedule creation fails | Target ReportServerService log |
| HTTP 401, 403, 404, or 500 response | Relevant server log plus IIS/HTTPERR or Windows Event Viewer, where applicable |
| Database connection, provider, or credential error | ReportServerService log and the target/source database or provider logs |
Step 6: Collect diagnostic information for support #
When contacting AzureOps support, provide one concise diagnostic package containing:
- The relevant source or target log file name and a short excerpt around the failure, including its timestamp, error message, inner exception, and correlation/activity ID where available.
- The wizard version, source and target report-server products and versions, and migration mode (server-to-server or server-to-file).
- The migration step where the issue occurred, the affected item or path, and whether it affects one item or multiple items.
- A brief note about what you have already checked or tried and whether the issue is reproducible.
- Redact passwords, connection-string secrets, access tokens, sensitive usernames, and report data. Send only the relevant excerpt—not the entire log directory—unless support requests it.
Unexpected-Exception Log #
For unexpected application exceptions, check the local fallback log at %LOCALAPPDATA%\AzureOps\SSRS Reports Migration Wizard\Logs\unexpected-errors.log. This file is stored on the computer running the wizard, may contain sensitive operational details, and is not automatically uploaded to AzureOps. Review and redact it before sharing.
Diagnosing SOAP HTTP 500 Errors #
When an SSRS SOAP operation fails with HTTP 500, the wizard’s detailed item message can help identify where the failure occurred and which server logs to inspect. Depending on the error, the diagnostic trace may include source-versus-target identification, SOAP operation, endpoint URL, client-local timestamp, corresponding UTC timestamp, the full SOAP fault, and underlying exception. Inspect the matching server’s ReportServerService_*.log around that time. Server and client time zones may differ; use the UTC timestamp as an additional correlation point where available.

Identify the server and operation #
Open the affected item’s status or details to inspect the full message and trace. Confirm whether the error identifies the source or target server. Then note the operation and endpoint. For example, an error naming CreateDataDrivenSubscription indicates a failure during that subscription-creation operation; use the identified target or source server to determine which ReportServerService log to inspect.
Correlate diagnostic timestamps with server logs #
- Record the client-local timestamp and UTC timestamp shown in the wizard, where available.
- Open the
ReportServerService_*.logfiles on the server identified by the error. - Search around the corresponding time and use the operation name, endpoint, catalog path, and exception text to narrow the results.
- Read the surrounding entries, including events immediately before the failure, to find the underlying server-side cause.
Time-zone warning: The report server may use a different time zone from the computer running the wizard. Server log timestamps may therefore differ from the client-local timestamp displayed by the wizard. Convert or adjust the search window using the server’s time zone; use the UTC timestamp as an additional correlation point where available.
Retain the complete wizard trace, including its diagnostic timestamps, operation, endpoint, and source/target identification. Do not rely on the HTTP 500 status alone. For the matching server-side entry, follow the log-location and correlation steps above.
For additional help, see the SSRS Reports Migration Wizard Troubleshooting Guide.