Errors to run some custom reports after migration

If Running into errors while attempting to run custom reports after a migration can be a common challenge, and it often requires careful troubleshooting. Here are some potential reasons for encountering errors and steps to address them:

Data Source Issues:

• Cause: The data source used in the custom reports may be pointing to a location or database that is different from the post-migration environment.
• Solution: Verify and update the data source connection strings in your reports to match the new environment.

Database Schema Changes:

• Cause: If there were changes in the database schema during migration, custom reports that rely on specific tables or fields may fail.
• Solution: Review the database schema in the new environment and modify the reports accordingly to align with any changes.

Permissions and Security:

• Cause: Insufficient permissions for the account running the reports may lead to errors.
• Solution: Ensure that the account has the necessary permissions to access the data source, execute queries, and view the required data.

Report Definition Issues:

• Cause: The custom reports might contain errors in the report definition (RDLC or RDL).
• Solution: Review the report definition for any syntax errors or issues. Use tools like Visual Studio or Report Builder to validate and correct the report structure.

Parameter Mismatch:

• Cause: If the reports use parameters, the parameters' names or values may not align with the new environment.
• Solution: Check and update parameters in the reports to match the data available in the new environment.

Data Migration Completeness:

• Cause: Incomplete or inaccurate data migration may result in missing or incorrect information for the reports.
• Solution: Verify the completeness and accuracy of the data migration. If necessary, rerun the migration process.

Report Server Configuration:

• Cause: Configuration issues with the report server, such as incorrect settings or services not running, can lead to errors.
• Solution: Validate the configuration of the reporting services and ensure that they are properly set up in the new environment.

Version Compatibility:

• Cause: If there are differences in the versions of reporting tools or services between the old and new environments, it can cause compatibility issues.
• Solution: Update the reporting tools, services, and report definitions to versions compatible with the new environment.

Network and Firewall Settings:

• Cause: Network issues or firewall restrictions might prevent the reports from accessing the necessary resources.
• Solution: Confirm that network connectivity is established, and check firewall settings to allow the required communication.

Logs and Error Messages:

• Solution: Review error messages and logs generated during report execution. They often provide specific details about the nature of the error, helping to pinpoint the issue more precisely.

By systematically addressing these potential causes, you can troubleshoot and resolve errors encountered when running custom reports after a migration. If the issue persists, reaching out to your IT support or the team responsible for the migration for further assistance is advisable.

First and foremost, You need to run the report from the SSRS/PBRS website first, If it doesn't run there then it will never run within the console.

Next you will likely need to enable remote errors to see the real error. Base on what it says you will take you next steps.

https://askgarth.com/blog/how-to-enable-remote-errors/