Share via

SSRS Report Credential Error

Raju Kothapally 10 Reputation points
2026-01-09T08:20:00.89+00:00

SSRS report works initially but fails after 10–15 minutes of idle time.

When user clicks Next page, Print, or Download, the report throws error:

"Credentials have not been supplied for a data source used by the report."

The report is generated using Microsoft SQL Server Reporting Services (SSRS)

and is embedded in a CRM application.

Issue occurs during report re-execution (pagination/export)

and is related to authentication handling in SSRS.

SQL Server Reporting Services
SQL Server Reporting Services

A SQL Server technology that supports the creation, management, and delivery of both traditional, paper-oriented reports and interactive, web-based reports.

0 comments
Answer recommended by moderator
  1. Akhil Gajavelly 1,570 Reputation points Microsoft External Staff Moderator
    2026-01-12T04:39:03.3433333+00:00

    Hi @Raju Kothapally ,

    This is expected SSRS behavior for embedded reports. After idle time, SSRS loses the user token and fails during re-execution (Next page / Export / Print).

    To fix this, configure the report data source to use Stored Credentials (SQL or service account). Avoid Integrated Security=True for embedded SSRS reports.

    If stored credentials aren’t allowed, configure the Unattended Execution Account.

    This resolves the error works for pagination/export after idle time.

    Thanks,
    Akhil.

    0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2026-01-09T08:20:09.8666667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The issue you are experiencing with SSRS reports throwing a "Credentials have not been supplied for a data source used by the report" error after a period of idle time is likely related to the authentication handling in SSRS. When a report is initially run, it may have valid credentials, but after a period of inactivity, those credentials may no longer be valid or may not be retained for subsequent actions like pagination, printing, or downloading.

    To resolve this issue, you can consider the following options:

    1. Use Stored Credentials: Ensure that the data source for your report is configured to use stored credentials instead of relying on Windows authentication. This can help maintain the necessary credentials for the duration of the report session.
    2. Configure Unattended Execution Account: If your report server is configured to use an unattended execution account, ensure that it is set up correctly. This allows the server to run reports without needing user credentials every time.
    3. Modify Data Source Settings: Check the data source settings in the Report Manager. Ensure that the connection string does not have Integrated Security=True, as this can lead to issues when the report is re-executed after being idle.
    4. Session Timeout Settings: Review the session timeout settings in your CRM application and SSRS to ensure that they are set appropriately to prevent session expiration during idle times.

    By implementing these changes, you should be able to mitigate the credential error when users attempt to interact with the report after a period of inactivity.

    References:

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.