SQL 2000 - Replication Error 2812
May 4, 2006
Windows Server 2003
SQL Server 2000 on both servers
Attempting to configure replication from server A to Server B using publishing configuration wizard.
Using Enterprise Manager and we received error 2812: Could not find stored Procedure 'msdb.dbo.sp_add_jobstep_internal'.
Following the analysis of general Microsoft help which pointed to a user/rights problem I used the Query Analyser, login with 'sa' and executed sp_adddistributor . I basicly received the same error. I also executed sp_help looking for the specifice procedure - not found.
Is it possible the sp is really not there. All help is appreciated.
Thanks,
View 7 Replies
ADVERTISEMENT
Feb 10, 2004
Hi !
When trying to start a Merge Replication agent I get the following Error message:
The process could not enumerate the changes at the subscriber. 2812
The snapshot agent works fine as far as I can see.
The replication is set up between a Win2000 / SQL7 / SP 4 and a Win2003 / SQL2000 / SP 3a machine. Sqlserveragent on both machines is run as a system account.
Any tip is welcome!
Thanks
VincentJS
View 6 Replies
View Related
Feb 12, 2004
Hi colleagues!
In trying to activate a merge replication between a Win2000/SQL7 distributor/publisher and a Win2003/SQL2000 subscriber I keep getting the following error:
Process could not enumerate changes at the subscriber (error 2812)
Merge publication works fine between the distributor and another subscriber (NT4/SQL7).
When i look at the details of the merge agent history i can see the process stopped with :
call sp_MSenumeratechanges(?,?,?,?,?)
I read article 308743 on microsoft/technet, and there they advise to install SP3a for SQL2000 on the subscriber. Ive done that but the error persists.
SQLServerAgent on the subscriber starts up with a local administrator account, the (physical) server itself is not a member of the local network; (outside the DMZ). The server is declared in the Client Network Utility of the distributor/publisher and is therefore known as a potential subscriber. In fact, the snapshot agent works perfectly (or so it seems).
Can anyone give me a helpfull hint?
Thanks!
VincentJS
View 1 Replies
View Related
Sep 8, 1999
In SQL EM:
Trying to schedule a nightly disk dump, I get the following message:
Error 2812: Stored Procedure 'sp_verifytaskdate' not found.
I can run the job immediately - but can't schedule at all.
Nothing found in TechNet. Thought of copying Stored Procedure from another install of SQL - how?
Anyone?
View 1 Replies
View Related
Jun 29, 2007
I have been trying to get a SQL 2000 server replicated with another - and keep getting the same error:
SQL Server Enterprise Manager could not configure "Server Name" as the Distributor for "Server Name"
Error 18483: Could not connect to server "Server Name" because 'distributor_admin' is not defined as a remote log in at the server.
I found several sites that helped me to get some feedback - but I am still hitting the same error.
Any thoughts would really help now.
Thanks!
M
View 4 Replies
View Related
Apr 27, 2006
I have a merge replication publication that has been running for
months. This week the Snapshot started failing, reporting that an
article was not included in the publication. I checked and found
3 articles that mysteriously no longer show up as being in the
publication. When I attempt to add them it reports that it can't
add them because there is already an article by that name in the
publication. Apparently some table has lost its rows for these
articles while another table(s) still has its rows.
Has anyone had this problem? Is there a solution short of
dropping the publication and starting over - a solution that would
literally take weeks for us?
Thanks for any help.
View 4 Replies
View Related
May 10, 2004
Hi,
I am getting an error while replicating the sql 2000 database.
The error no is 20598...It stopped replicating the database...
Can any body tell me what is this pls....
Tks in advance...
Joyce
View 5 Replies
View Related
May 14, 2007
Hi.. I tried to setup MSSQL2000 trans replicatiom using push subscription method. My Publisher is also my distributor. But whenever I started the dstribution agent, I got the following error. It has problem connecting to subscriber's DB with the following error. I had tried that the login is 100% fine. But why this error appear ? Any help?
The name ' ' is not permitted in this context. Only constants, expressions, or variables allowed here. Column names are not permitted.
(Source: Subsriber (Data source); Error number: 128)
View 1 Replies
View Related
Jan 23, 2007
I have few databases with SAME database structure in
SQL Server 2000 in different locations. Data will be
updated in different places with different sets of
data. Basically, i need to synchronize the data
especially to the headquarters database periodically
(may be everyday at night).
DB : SQL Server 2000
OS : Both are running on Windows XP for testing
purposes.
Situation : Now i have 2 database from 2 different
estates. Now, need to be synched into 1.
Have 2 publisher namely TH1, TH2
1 subscriber : THFinal
I've created 2 individual publications using "Create
Publication" and published database namely TH1 and
TH2.
Publication type : Merge publication
Default table article properties setting are as
follows :
a. When merging from different sources : "Treate
changes to the same column as a conflict (changes to
different columns in the same row will be merged)".
Snapshot
i Choose "DELETE DATA IN THE EXISTING TABLE that
matches the ROW FILTER statement".
Resolver :
I checked "yes" for - Allow Subscribers to resolve
conflicts interactively during on-demand
synchronizations".
Now, when i sync the TH1, all the records from TH1
goes to the subscriber database "THFinal".
When i sync the TH2, all the records which was
synched earlier (from TH1) being DELETED. and all
the records from TH2 goes to the subscriber database
"THFinal".
Basically, i WANT to retain the ALL THE data from in
"THFinal" which came from TH1 database since the
primary key is different. Also, all the database
contains running no (Identity increment = 1) .
Identity : Yes (Not For Replication) (Identit seed=1)
===================================================
PROBLEM : 1ST (TH1) database can be synched. when
I try to replicate the 2nd (TH2) database, the
following ERROR displayed : The process could not
drop one or more tables because the tables are being
used by other publications.
The process could not drop one or more tables because
the tables are being used by other publications.
(Source: Merge Replication Provider (Agent); Error
number: -2147200976)
Thanks in Advance
Reagards
Ihsan
View 6 Replies
View Related
Mar 15, 2007
I have used skiperrors parameter for 2601,2627 and 20598 errors in my Transaction replication setup. When transactions with above error are encountered, its skipped but I€™m not getting sql command that is skipped in MSrepl_errors table. Since SQL server 2000 is not saving transaction sequence number in the MSrepl_errors we are not getting the command, which have the errors.
Is there any way to track the commands those are skipped in transactional replication.
View 11 Replies
View Related
Jun 27, 2006
i went through the documentation but i was not clear on following, here is the scenario :-
a Central server is having SQL Server 2000
3 Remote Locations :- Each having 4-5 no of computers, connected on a Lan, and on one of the machines MSDE 2000 will be running.
My Questions are :-
1. Can remote locations, update data locally and send changes (say in every one hour) to central server. If yes, then how ??
2. Same way they can receive updates from Central Server on whatever was updated on Centra Server or on the 3 remote locations. If yes, then How ??
any help will be highly appreciable.
View 8 Replies
View Related
Jun 15, 2007
I'm getting this, after upgrading from 2000 to 2005.Replication-Replication Distribution Subsystem: agent (null) failed.The subscription to publication '(null)' has expired or does notexist.The only suggestions I've seen are to dump all subscriptions. Sincewe have several dozen publications to several servers, is there adecent way to script it all out, if that's the only suggestion?Thanks in advance.
View 3 Replies
View Related
Mar 6, 2007
Hello,I'm getting the following error message when I try add a row using aStored Procedure."The identity range managed by replication is full and must be updatedby a replication agent".I read up on the subject and have tried the following solutionsaccording to MSDN without any luck.(http://support.Microsoft.com/kb/304706 )sp_adjustpublisheridentityrange (http://msdn2.microsoft.com/en-us/library/aa239401(SQL.80).aspx ) has no effectFor Testing:I've reloaded everything from scratch, created the pulications from byrunning the sql scripts generated,created replication snapshots andstarted the agents.I've checked the current Identity values in the Agent Table:DBCC CHECKIDENT ('Agent', NORESEED)Checking identity information: current identity value '18606', currentcolumn value '18606'.I check the Table to make sure there will be no conflicts with theprimary key:SELECT AgentID FROM Agent ORDER BY AgentID DESC18603 is the largest AgentID in the table.Using the Table Article Properties in the Publications PropertiesDialog, I can see values of:Range Size at Publisher: 100,000Range Size at Subscribers: 100New range @ percentage: 80In my mind this means that the Publisher will assign a new range whenthe Current Indentity value goes over 80,000?The Identity range for this table cannot be exhausted! I'm not surewhat to try next.Please! any insight will be of great help!Regards,Bm
View 1 Replies
View Related
Mar 21, 2001
Hi,
I have no idea of SQL2000.Can anyonetell me steps /precuations involved in going for Replication in SQL2K.
Also,How do we do log shipping in SQL2K?
TIA
pd
View 1 Replies
View Related
Apr 4, 2001
I am trying to set up transactional replication (not immediate updating) via a push subscription between a SQL 7.0 Server and a SQL 2000 Server. The SQL 7 server is the Publisher / Distributor, and the SQL 2000 server is the subscriber. Replication will not work between the two, I have removed then setup replication to no avail. The SQL 7 server always reports that it can't connect to the SQL 2000 server. Same problems the other way if I try a pull subscription.
Anyone have any ideas?
thanks,
Kyle Freeman
zilchfrag@zilchfrag.com
View 1 Replies
View Related
Oct 23, 2001
I'm trying to replicate a sql 7.0 table to a sql 2000 server. Does anyone know how I can register a sql 2000 box through Ent. Manager onto 7.0? I've been told that I need to upgrade my production server's Ent. Manager to 2000 but I not sure if that is a real safe bet. Can anyone give me any insight to this?
Thanks,
Jeff
View 1 Replies
View Related
Sep 6, 2003
I am trying replication on sql 2000
I want to do replication using two databases. suppose say Db1 and Db2
if new record is added in db1.table1 then the same record should get added to Db2.table1 and vice versa.
using enterprise manager I have successfully created replication from Db1 to Db2.
how to do it from Db2 to Db1?
any suggestion would be helpful.
thanks
View 6 Replies
View Related
Feb 10, 2004
How do I know whether the record in a row was insert,update and delete that replicated to a subscriber?
Is there a flag or an indicator in msmerge_contents,msmerge_tombstone ,msmerge_genhistory tables or any other msdb/replication system tables?
View 6 Replies
View Related
Jun 4, 2007
I would like some simple input on achieving true two-way replication with SQL 2000. We have need to load balance our website between two sites and since it is SQL based, would need to have dual DB servers at each site with two-way replicated data. They would need to be replicated at real-time. Will the built in SQL replication tools work OK? Has anyone done this? Thanks in advance.
View 1 Replies
View Related
Jul 23, 2005
Here is what we are trying to solve:-We have a SQL 6.5 server (version 6.50.258) we will call SQL65-A, onan NT 4.0 machine (version 4.00.1381), on Domain-A-We are trying to replicate directly to a SQL 2000 server (version8.00.818) we will call SQL2000-A, on a Windows 2000 machine (version5.00.2195), on Domain-B-We also have a SQL 6.5 server we will call SQL65-B in Domain-B-The domains are trusted-We get the error that it cannot connect to the SQL 2000 server whentrying to replicate, even though I can register the SQL 2000 server asa Remote ServerThe work-around we have right now is replicating from SQL65-A toSQL65-B, then using SQL65-B as a subscriber as well as adistributor/publisher to SQL2000-A.
View 1 Replies
View Related
May 30, 2007
sql 2000 replication: Is there a way of getting tables to replicate without them having a pramary key?
View 1 Replies
View Related
Sep 1, 2006
Hello.
We've a SQl Server 2000 with a DB with 4GB.
Now we need to reply our server with another server that will be connected with us for comunications.
We want that the replicacion is on-line.
Can you recommend me if we upgrade the servers to SQL 2005?
Does this replicacion process consume many resources of the server?
Which the requirements hardware minimum are for this process?
As much wide of band for the comunications I can need?
Thanks.
A greeting.
View 1 Replies
View Related
May 22, 2002
I get this error in my Agent after starten to synchronise.
I see the access mdb been created and then deleted and renamed to
name_old.mdb
Do you have some help?
Richard
View 1 Replies
View Related
Feb 9, 2004
Hi,
I wantked know the best tool or way for Replication between SQL server and DB2/IBM(MVS).
Thanks,
Ravi
View 6 Replies
View Related
Mar 7, 2002
Hi guys.
I have two scenerio.
One:
Two servers (SQL 7.0), transaction replication
Two:
Four servers (SQL 7.0), transactional replication one publisher, one distributor and 2 subsribers.
I need to upgrade these two scenerio to 2000.
Please advice me with suggestions and your experience.
Is Online replication possible?
-MAK
View 1 Replies
View Related
Aug 15, 2001
Hi,
I am in between of analysis for Upgradation of SQL server 7.0 to SQL server 2000.
I have few server on SQl server 7.0
I wanted to know , is the replication supported between SQL server 7.0 and SQL server 2000.
a ) from SQl server 2000 to SQL server 7.0
and
b ) from SQL server 7.0 to SQL server 2000.
Both this scenarios will exist.
Thanks in advance
Vikram
View 1 Replies
View Related
Jun 27, 2007
Hi Friends
What are the main differences between Sql Server 2000 Replication and Sql server 2005 Replication?
Thanks
Vic
View 2 Replies
View Related
Feb 20, 2008
I doing a transactional replication with two servers. Server A, the Publisher and Distributor. Server B, the Subcriber. I did the replication using a dummy DB for practice purpose and it works fine. When I try to implement the replication in original DB, I found that some tables don't have primary keys and to be able to implement transactinal replication all the replicated tables need to have a primary key. I want to add the primary keys to those tables and also implement the replication but the problem is those tables have data in it. I'm thinking in create the new table and do a DTS to import the data to the new table or it's fine just to modify the table in design to add the primary key "Those table have record in it".
Some of you have any advice to me?
View 4 Replies
View Related
May 31, 2006
Hello,
I am using MSDE 2000 for replication of my Data. I have one publisher and two subscribers. but i need t filter rows for publications. Problem is that for filtering, i need host_name and in push replication host_name is name of system in which Agents are running but in MSDE all agents are running in publisher system ( distributor System). so everytime for any publication i get only id of server.
i am facing same problem in pull replication also.
Regards,
View 4 Replies
View Related
Mar 23, 2006
Any suggestions on how to replicate from AS/400 to SQL Server 2000?
Data is stored on a AS/400, but applications use a SQL Server 2000 DB. Currently, DTS packages drop the SQL DB, rebuild the tables from a script, copy the data, and then rebuild the indexes as a nightly batch job. Is there a better way to do this? Also is there a clean way to replicate daily transactions as well?
View 1 Replies
View Related
Jan 26, 2006
Hey everyone,
This may be in the wrong forum, but I have a database in SQL Server SP3a that I will be replicating out to SQL Mobile 5.0. The setup of the replication will not be a problem, however, once replication is setup, I will have to change the DTS Package that creates these tables.
I have created a DTS Package that drops the tables and recreates them from a DB2 database. My problem is that I won't be able to drop these tables once a publication has been established.
I really don't need to drop the tables if I can create a script to pull just the new records from the DB2 database.
Does anyone know of an easy way to do this? Are there any products out there that would make this easier? Has anyone else out there had to create a publication with this scenario?
Just a little background, I originally created the DTS Package from an import, and then modified it. I added the DROP TABLE scripts so that I wouldn't just append the same data over and over. Perhaps there is a better way of doing this than a DTS Package.
This would probably be a lot easier to handle if I weren't pulling from a DB2 database because I would probably be able to create a trigger or something on the source database, however I know nothing about DB2 datasets other than how to pull the data out. I would appreciate any input on this.
Thanks,
Lee
View 3 Replies
View Related
Jul 3, 2007
Hi
I'm trying to determine if it is possible to do many to many replication in sql server 2000.
What i basically want is to have n databases share the same basedate (share a common database) and allow updates in any database to be replicated to all the other databases (with a simple conflict resolution, like last update wins).
My goal is total autonomy, without a single point of failure. If any node goes down, the other nodes will continue to work and continue to replicate their data to the remaining nodes. When a node comes back up it will catch up with the over nodes (or get reinitialized if it was a serious crash).
The amount of data i want to replicate is not that big (less than 100MB) and does not change that often. All servers are sql server 2000 instances connected by a gigabit network and the number of nodes involved is less than 10. Some latency is also acceptable.
the question is: is this at all possible? I have read i bit in 'SQL Server High Availability By Paul Bertucci' and some other resources and it looks like a multiple publishers or multiple subscribers with merge replication setup should work, but i'm not too sure if it will work for n > 2 nodes (where all nodes publish and subscribe to each other) and it also mentions constraints on which data a given node is allowed to update (i hope this could be handled by simple conflict resolution).
And if it is not possible in 2000, could it be accomplished en 2005?
TIA Jens
View 3 Replies
View Related
Feb 8, 2006
Hi,
Can anyone help me?
How do I implement SQL Server Replication?
Where, and how? Do I have to download specific software to do this, or how?
What would be the right option?
Thanks
SJB
View 3 Replies
View Related
