Friday, March 30, 2012

Replication error thrown during normal T-SQL processing

Dear All,
During a long running piece of SQL script I received the following error:
Error Number: 2601
Error: "The job name '%s' was not generated for this replication agent,
delete the job manually when it is no longer in use."
There is no replication set up on this server at all, and the T-SQL is pure
with no calls to system stored or extended procedures.
Has anybody experience this before? A search of Google and MSDN has
returned no results at all for the assosiated message!
Spec:
Microsoft SQL Server 2000 - 8.00.760
Developer Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
HP ProLiant dual 3ghz HT Zeon
4gb ram
Thanks
Phil StandenOn my server,
SELECT *
FROM master..sysmessages
WHERE Error = 2601
returns:
Cannot insert duplicate key row in object '%.*ls' with unique index
'%.*ls'.
and
SELECT *
FROM master..sysmessages
WHERE Error = 21695
returns:
The job name '%s' was not generated for this replication agent, delete
the job manually when it is no longer in use.
Do you get the same results on your box?
Hope this helps.
Dan Guzman
SQL Server MVP
"Phil Standen" <PhilStanden@.discussions.microsoft.com> wrote in message
news:BEE3ED3E-FA80-4D98-A85D-36B4E37B374A@.microsoft.com...
> Dear All,
> During a long running piece of SQL script I received the following error:
> Error Number: 2601
> Error: "The job name '%s' was not generated for this replication agent,
> delete the job manually when it is no longer in use."
> There is no replication set up on this server at all, and the T-SQL is
> pure
> with no calls to system stored or extended procedures.
> Has anybody experience this before? A search of Google and MSDN has
> returned no results at all for the assosiated message!
> Spec:
> Microsoft SQL Server 2000 - 8.00.760
> Developer Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> HP ProLiant dual 3ghz HT Zeon
> 4gb ram
> Thanks
> Phil Standen

No comments:

Post a Comment