When clicking New Subscription (or Manage Shared Schedules) I get the following error: An internal error occurred on the report server. See the error log for more details. (rsInternalError) Get Online Help For more information about this error navigate to the report server on the local server machine, or enable remote errors I can't find any information about this error. Does anyone know what is wrong?

Good idea! Here is the error message I am getting then: The EXECUTE permission was denied on the object 'sp_verify_job_identifiers', database 'msdb', schema 'dbo'.

Did you recently change the service or execution account for your Reporting Services Install, or did you recently remove an account like NT Authority\network service from SQL?

No, it is recently installed and this hasn't worked yet. I need to know what it is that is preventing it from working. Any specific access rights for the unattended execution account?

Here is how to configure the account: Configuring the Unattended Execution AccountConfiguring an Account for Unattended Report Processing

I'm really thankful for your help but I'm afraid this doesn't solve the problem. We already have an Unattended Execution Account registered in the Reporting Services Configuration (SQL 2005).Maybe that account needs any specific access rights on specific tables? (Is it that account that is used for subscriptions? When I look at the documentation it mentions that this is for "connecting to external report data sources that do not require or use authentication" and fetching images. I just want to add a subscription to a report with a predefined access account so maybe this isn't dependent on the Unattended Execution Account? I mean, I get the error "The EXECUTE permission was denied on the object 'sp_verify_job_identifiers', database 'msdb', schema 'dbo'." right away when I click "New Subscription". What account need that permission? I as the logged in user?)

Your failure is a lack of permissions for this account, so you can one by one grant the needed permissions to the account for the objects it needs to access, and probably resolve this, but I don't know what all those objects are, and I don't see a specific reference online for them either. Something isn't quite right with how you are configured, that is obvious. Is SSRS running under Local\System or a Domain User?

SSRS is running under LocalSystem. (By the way, when you say "this account" do you mean the SSRS account, the unattended service account or the logged in user?)

I'm having the same problem except I'm getting a different error. There are two or more jobs named '7BD6E0A6-2886-49AC-BF8D-2250ABDC641D'. Specify @job_id instead of @job_name to uniquely identify the job. Anyone have any info on this error? I found the job except I only see one when browsing in object explorer. If I view job history, then I see two. There is no history and no job steps to look at. Any help would be appreciated.

May be too late but in order to get around the above error you need to go the sql server hosting the report server db and delete one of the duplicate jobs with the above id and delete the other from the report server ui. I think that should resolve the issue. but not sure what causes this?

Vikram's solution to beatwork question worked for me. There is no need however to erase the second job through UI, just deleting one through ssms is enough. Thanks.

I too received the following error : What a user was doing was simply changing a shared schedule time from AM to PM. An internal error occurred on the report server : There are two or more jobs named " <GUID>" Deleting the duplicate job in Management Studio fixed it but does anyone know what causes this error to occur?

Hi Everyone, This was filed as an item on Connect - http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=650123 However, the connect item does not have enough information for us to diagnose the issue. Could one or more of you add your Log Files to the connect item that correspond to the time that the error occurrs? Also, we need information about your deployment to put the log file information into context - is the report server in a scale-out deployment? What activity happened before this issue started happening - e.g. did you backup/restore your report server dataase, or change service accounts, etc? Thanks in advance, -LukaszGot a bug or feature request? Tell me about it at http://connect.microsoft.com. This posting is provided "AS IS" with no warranties, and confers no rights.