Link to home
Start Free TrialLog in
Avatar of ryanwei88
ryanwei88

asked on

SQL Server 2000 Enterprise Edition: Error 14261: The specified primary_server_name.primary_database_name already exists.

SQL Server 2000 Enterprise Edition: Error 14261: The specified primary_server_name.primary_database_name already exists. I tried to clean up all log_shipping_* tables but the error still shows up.
Avatar of redrumkev
redrumkev
Flag of United States of America image

ryanwei88,

How are you doing?

See if this helps:
http://support.microsoft.com/default.aspx?scid=kb;en-us;q298743&sd=tech

Kevin
Avatar of ryanwei88
ryanwei88

ASKER

I tried this. but the issue remained.
ryanwei88,

Did you upgrade from standard edition to enterprise edition, because there is an issue with that (MS KB 295306).

I found this as well, which mentioned the above (As well as my first posting):
 
Had two difficulties, the first being the 14261 error. Theworkaround for this is to be found in KB article 298743 BUG: AllChanges May Not Be Rolled Back when Log Shipping Maintenance Wizardfails. The second part of this is that the procedures do not exist onthe standby server. In my case it was due to the fact that I hadupgraded from standard to enterprise edition and there is a bug in theupgrade process such that these procedures are not created. This isaddressed in KB article 295306. BUG: Log Shipping Elements are MissingAfter You Upgrade From Standard to Enterprised Edition. Theresoloution  is to run the instls.sql script shich is located in the\Install folder of the Enterprise Edition. I hope this helps.

Also - see this (you might need to sign up, which is free, this is a great SQL site):
http://www.sqlservercentral.com/Forums/Topic457911-54-1.aspx#bm476691
Hope this helps,
Kevin
Hi, Kevin,

thanks for the link. I did upgrade from standard edition to enterprise edition for the Primary DB. I had tried everything but it keeps throwing the same error message. Is there any kind of tools for this?

Thanks
ryanwie88,

I do not know of any tools in particular, but yes, I am sure there is a work around or some stored procedure (documented or not) that can do this. I would really ask on the forum over on SQL Server Central.

Also - ask the Mods here on EE to add the SQL zones, as there are some SQL Guru's here at EE. To do this, just click the "request attention" by the question and say that you need some help in the SQL zone.

I will keep both monitoring and searching...

Kevin
How may I help?
ASKER CERTIFIED SOLUTION
Avatar of ryanwei88
ryanwei88

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial