Violation of PRIMARY KEY constraint 'PK_ScheduleID'. Cannot insert duplicate key in object 'dbo.Schedule'. - by owenphil

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 407166 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 1/28/2009 10:38:29 PM
Access Restriction Public


Hi All,
I've got a SQL 2005 Reporting Services database that has been migrated from SQL 2000. On creating a custom subscription on any report i get the following message:
"Violation of PRIMARY KEY constraint 'PK_ScheduleID'. Cannot insert duplicate key in object 'dbo.Schedule'. The statement has been terminated." Shared subscriptions do not give this error. I have deleted all subscriptions, effectively emptying the table, yet i still get the same error? I can get this error on the console as 'sa', 'admin' or a 'user' All the columns concerned seem to be uniqueidentifier type. Any ideas on why this error is occurring?? or how to re-seed/reset this GUID, given it's not an identity??? or how i can trap the details of this insert (wizard) to track down the duplicate??? I cannot find this issue reported anywhere. All other RS functions work fine??
Sign in to post a comment.
Posted by Microsoft on 8/17/2010 at 4:22 PM
To work around the problem, you may manually delete the offending row in table. To find out which row to delete, use SQL Profiler to trace the statements sent from RS server to the RS catalog DB server.

After investigation, it is not clear what caused the system to get into this state. If you have addition information, please provide it to us.
Posted by Microsoft on 2/24/2009 at 9:37 AM
Thank you for filing this issue. We have assigned it to a developer to investigate.