Subscription create. An error has occurred. Please try again later.

Paul Shepard 1 Reputation point
2021-01-05T21:37:19.557+00:00

We had created over 30 subscriptions in our SQL Server 2017 Reporting Services environment. When I go to create or modify an existing subscription, I get the error - An error has occurred. Please try again later. The subscriptions are still running but we cannot make changes.

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 No comments
{count} votes

5 answers

Sort by: Most helpful
  1. Joyzhao-MSFT 15,646 Reputation points
    2021-01-06T03:06:29.06+00:00

    Hi @Paul Shepard ,

    An error has occurred. Please try again later.

    It can be due to quite a few things. The first place to check would be the Reporting Services logs and see what errors you can find in the logs. If it is 2017 and above, The files are located at: C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\LogFiles
    Most of the time errors are located in those files. And what to do depends on what the error is.

    Could you describe what version you are currently using? Did you perform other operations before reporting the error? Can a new subscription be successfully created?

    For the case of encountering this error after upgrading, you can refer to: An Error occurred try again later when trying to modify subscription.

    Finally, I look forward to you providing the relevant error log, it may be helpful to resolve your issue.
    Best Regards,
    Joy


    If the answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  2. Joyzhao-MSFT 15,646 Reputation points
    2021-01-08T06:59:55.15+00:00

    Hi @Paul Shepard ,
    Has your issue been resolved?
    If you have any question, please feel free to let me know.
    If the answer is helpful, please click "Accept Answer" and upvote it.
    Best Regards,
    Joy


    If the answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  3. Paul Shepard 1 Reputation point
    2021-01-08T14:33:34.973+00:00

    Joy,
    In report server config mgr
    Edition - sql server standard
    product version 14.0.600.906
    report server mode - standard
    service account - use built in account - Virtual service account
    execution account - empty
    subscription settings - empty

    I can create and modify reports. We have existing subscriptions that are executing fine. I just cant modify/create new subscriptions. Ive created a report from scratch and tried to no effect.

    When I click on the NEW SUBSCRIPTION button on the report - I get the error, An error has occurred.
    Subscription can't be created or edited because the credentials used to run the report are not stored, or if a linked report, the link is no longer valid.

    0 comments No comments

  4. Joyzhao-MSFT 15,646 Reputation points
    2021-01-11T06:03:46.673+00:00

    Hi @Paul Shepard ,

    Thanks for your feedback.

    Subscription can't be created or edited because the credentials used to run the report are not stored, or if a linked report, the link is no longer valid.

    The problem sounds like the report expects the user to provide credentials when it is viewed. When you create a subscription, it does not have the credentials to execute the report.
    I have encountered this error once, and I reconfigured the data source authentication and connection in the report manager.
    55144-01.jpg

    And then GoTo: Report>Properties> Click on the Data Sources tab and you will see following options:

    a)A shared data source
    b)A custom data source

    Are you using a shared data source? Is it using Windows integrated security? If so, can you change it to use a service account made just to run these reports? You may need to view these properties by viewing the data source itself.
    If it is a custom data source is the option "Credentials supplied by the user running the report" selected? If so, can you change it to "Credentials stored securely in the report server"?

    Use option b) and click on option Credentials stored securely in the report server and provide credential information and further you can use options: Windows credentials and Impersonate the authenticated User if you require. Click on apply button.

    *You can use any option of them provided in first option(a) also using the shared data source which is having credential saved into report server.

    Once you have done with above you will be able to create subscription.

    Either way, if you want to set up a subscription, I have made it work by providing credentials in the data source rather than have the user input them.
    If you are worried about security, I would suggest managing that on the report level rather than the data source level.

    Best Regards,
    Joy


    If the answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


  5. Paul Shepard 1 Reputation point
    2021-01-13T14:27:39.923+00:00

    Joy,
    I tried going into our shared data sources and receive the An error has occurred message. I am also not able to modify or add there. The data source properties are set to use the following credentials - database username and password. Does Microsoft offer the ability to log a case and have a teams meeting to look at our environment?


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.