Sql 2000 Replication And Stopping Log Reader Agent
May 10, 2006
Question:
I am unclear what syntat to use to stop (suspend) the log reader agent.
Things I Understand:
I understand how to manually stop the reader agent using the enterprise manager.
I understand how to schedule the load reader frequency (properties of the agent)
My Intention:
to stop the log reader agent, execute another scheduled job, then restart the log reader
Any suggestions are appreciated: comment here or send to:fglomb@crtincbc.com
Thanks!
View 1 Replies
ADVERTISEMENT
Aug 2, 2001
Unable to start log reader agent after being manually stopped.
Any ideas.
View 1 Replies
View Related
Nov 30, 2006
Hi All,
I would appreciate any help here at all. I am pulling my hair out!
I am unable to start the snapshot agent or log reader agent from within SQL management studio. it fails on executing step 2 with unknown username or bad password.
I have checked all account details and they are correctly using my domain admin account. I can connect to SQL using teh same account and it also has sysadmin permissions.
If i copy the step 2 paramters and start from the cmd prompt (again logged in using the same domain account) they both start fine.
Any ideas would be gratefully received.
View 1 Replies
View Related
May 18, 2007
I am testing peer to peer replication in our environment. I simulated a three node peer to peer topology and a local distributor.
For some wierd reason I cannot get the Log Reader Agent and snapshot agent to start. The domain account under which SQL Server Agent runs has administrator previlage on the box. I also use a domain account for SQL Server Service. (none of the passwords changed).
This is the error I am getting - "Executed as user: abc. A required privilege is not held by the client. The step failed"
Any ideas???
Also this domain account is a member of
SQLServer2005MSSQLUsers$ServerName$MSSQLSERVER
SQLServer2005MSAgentUser$ServerName$MSSQLSERVER
View 3 Replies
View Related
May 7, 2007
I have a SQL Server agent that keeps stopping for no reason. It happens about every other day. I have to go in on the server and manually start it. What would cause this to happen? We have about 50+ computers that need to sync with the server and do so successfully without having to manually start the agent every other day. How do we fix it?
View 17 Replies
View Related
Oct 2, 2007
Maybe I'm just totally not getting it, but can someone tell me how to stop/start the distribution agent? The Books Online document - "How to: Start and Stop a Replication Agent (SQL Server Management Studio)" - shows how to stop/start the Snapshot Agent, Log Reader Agent and Queue Reader Agent, but not the Distribution Agent. Is it that stopping one of these agents in turn stops the Distribution Agent. I am trying to work through how to add an article to a peer-to-peer topology and need to stop the agent as part of that.
Thanks,
Larry
View 3 Replies
View Related
Jun 15, 2007
Hi am trying to create a snapshot (Merge replication) - My database is approx 6GB and one of my tables has 14.5M records - I have a total of 1500 articles to replicate.
When I start creating the snapshot - it seems to just stop on the Table that has the 14.5M records. When I delete all the data in that table it works fine. I have also check disk space and also the log files and tempdb size and all seem ok.
I am using SQL 2005 with the latest SP
Is there any form of verbose logging that I could enable to let me see what is going on
Any help would be greatly appreciated
Regards
Ants
View 2 Replies
View Related
May 22, 2014
prevent users from stopping sql server agent?
I have SQL2000 server installed and then SQL management studio 2008 R2 express edition in users desktop. I noticed that the user can stop the SQL server agent. Even a user is a reader access only.
View 8 Replies
View Related
Jun 22, 2004
We restored a database with replicated tables. Now, the Log Reader Agent will not run. This displays:
"The process could not execute 'sp_repldone/sp_replcounters' on 'ourservername'."
In Error Details for the agent:
"The process could not set the last distributed transaction."
And, from the logs:
"ForwardLogBlockReadAheadAsync: Operating system error 998(Invalid access to memory location.) encountered."
Does anyone know how we get the Distribution database and the Log Reader running again?
It is only affecting Transactional replication (not snapshot or merge).
View 4 Replies
View Related
Feb 15, 2006
HELP>>> I am getting desperate
we recently had a failure which ended up wrecking my replication. The basic layout is from a source server -> Distribution Server then out to several other servers. Long story short the distribution database had to be moved to a new drive and I am now getting the following error message
The specified LSN (0003d4f0:0000721e:001b) for repldone log scan occurs before the current start of replication in the log (0003d63a:00002803:0001).
(Source: fsdpdcis (Data source); Error number: 18768)
---------------------------------------------------------------------------------------------------------------
The process could not set the last distributed transaction.
(Source: fsdpdcis-DPDDATA-1 (Agent); Error number: 22017)
I have reinitialized all subscriptions on the fsdpdcis server and run subscription validation (with no response). The data did re-load during the reinitialization but does not seem to be getting updated. This is driving me crazy and I am desperate. Any suggestions would be greatly appreciated. I have search MS knowledge base with no results and BOL has not been any help so far.
Thanks
Steve
View 4 Replies
View Related
Apr 7, 2006
I recently set up transactional replication from one server database to another server database. I keep getting a Log Reader Agent error: An access violation occurred.
The SQL Server agent starts under one Windows account but the Server is registered under the system account. The log reader agent is using the system account.
I'm not sure what else to check or what database permissions or roles should be set. Can somebody help? Thanks.
View 5 Replies
View Related
Sep 19, 2006
Hello,
by mistake I added an queue reader agent to a distribution database. But how can I drop the queue agent. There isn't a stored proc 'sp_dropqreader_agent'.
The only way I found (apart from dropping the whole distribution databse) is to stop and disable the generated job!
Is there any other way to get rid of the queue reader agent ?
Wolfgang
View 7 Replies
View Related
Jun 12, 2002
hi,
among our server-agent jobs is one for the log-reader-agent and its run status is displayed as error though the log-reader is working correctly, replication is working fine.
it had hit an error some days ago after an unexpected shutdown - but it has been auto-restarted correctly on restart of the sql-server agent.
now - what can i do to get back to a sensible run-status report?
i have already deleted the job-history with the hope that this might help - but it didn't. should i just stop and restart the job again?
can i somehow delete the status in the jobhistory?
i would gladly appreciate any ideas because it's making me just mad to have a 'failed' job status on the monitor *g*
thank you,
kerstin
View 1 Replies
View Related
May 12, 2006
I'm using our development ID to set up peer-to-peer replication. I am following the steps outlined in the BOL using SQL Studio 2005. When I created the initial publication, I read the section on permissions and assigned the development login ID db_owner. Indeed, to eliminate any possible issues (I thought), I gave it db_datareader, db_datawriter, and all the db admin rights and made very sure the db_denydatareader and db_denydatawriter roles were not checked. I did this through the Logins section of the Security folder and applied the same rights to both the distribution and the publication database. Nevertheless, when I run the LogReader agent job, it fails with the message for step 2 that:
Executed as user: ourdomsqldev. A required privilege is not held by the client. The step failed.
The dev ID essentially has sa rights to the server and all the databases. It is also a domain authenticated ID. Any ideas what's causing this problem? I really need to get the replication going reliably before the weekend is out.
Thanks.
Randy
View 1 Replies
View Related
Feb 9, 2005
I've set up transactional replication with queued updating. If I stop the queue reader agent through EM, I can't start it again. Agent's history says "Queue Reader aborting. The step failed."
All servers are SQL Server 2000 SP3.
Help is greatly appreciated!
View 1 Replies
View Related
Dec 3, 2002
Hi, I am unsure whether i can delete some system created tables from a database.
I was testing replication and then used the wizard to disable it all. I am however left with three tables that are replication based that have not been deleted. they are :
MSreplication_subscriptions
MSsubscriptions_agents
MSsubscriptions_properties
these tables are causing problems with some third party software due to the length of their names. I have tried to 'Exec sp_rename' but i get an error saying the objects are not valid for this operation.
Can i just delete them or will this cause problems if i want to start up replication in the future?
View 2 Replies
View Related
Jan 31, 2006
The situation is as follows: Database A is being replicated to database B on a networked server. The application vendor is in the process of doing customizations which require frequent table changes. So the vendor (who has access to the replicated DB) stops replication in order to upgrade some tables. But I am finding that either he has forgotten to restart replication or, more than likely, has broken it.
So, if anyone is able to comment on a process which will allow changes to database tables and the restoration of replication, I would be very grateful. thanks in advance.
View 4 Replies
View Related
Mar 19, 2001
Log Reader:
The process could not execute 'sp_repldone/sp_replcounters' on 'prdSQL01'.
I have configured replication locally; from prdSQL01 to prdSQL01 in order to
troubleshoot this problem.
Is the problem is local to the box?????????
Do I need to re-install MSSQL SERVER? CORRUPT INSTALL????
HELP IS DESPERATELY NEEDED. APPRECIATE ALL SUGGESTIONS.
THANKS
SAM
View 4 Replies
View Related
Apr 30, 2015
In ReplMon, some Log Reader agent jobs display as "not running". Rigt-clicking on it the only option is to "Stop" the agent. Seems to me if it's NOT RUNNING you should be able to Start it but that option is disabled. Also, looking at the Agent Job Activity Monitor on the distribution server it says that the job is currently executing.
Running the Replication Agents Checkup job yields nothing and those jobs are still "not running". I can easily Stop/Start the Log Reader in ReplMon or insert a tracer token and then all looks fine. I'm just puzzled by the inconsistency and wondering how I can programmatically check and resolve it.
View 0 Replies
View Related
Jan 19, 2006
Guys,
I get the error message: Queue reader aborting. The steps failed...in queue reader agents of SQL 2000 replication. Could any one give me a hint of how to troubleshoot this problem? Thanks a lot in advance.
View 1 Replies
View Related
Jul 3, 2007
I have just started getting the following error from the queue reader but I can't see why.
The Queue Reader Agent has encountered the error ''Row handle is invalid.'' when connecting to ''Database'' on ''ServerName''. Ensure that the publication and subscription are defined properly and that both servers are running.
Does anybody know what it means / how I can fix the problem?
Thanks
View 11 Replies
View Related
Feb 19, 2007
We just moved source server to newer, bigger box ... Windows 2003 and Active Directory ... Snapshot agent worked but distribution failed ... Same login as on older machine, login is sysadm, used DCOMCNFG to allow ability to launch process ... What are we missing?
View 4 Replies
View Related
Feb 27, 2007
Hi,
during install of SRS 2000 in a dev environment I get the following error:
Error Code 6
Installing Performance Monitor Objects failed.
If I choose ignore, the wizard freezes and no further activity is performed regardless of how long I leave it.
Also, during the install it does not automatically detect the SQL server name when nominating the server, you have to type this in manually even after refreshing the list.
The SQL server was installed using the default instance.
Being installed on 2000 Server with latest service pack, and with SQL 2000 on sp4.
Any help on this would be appreciated.
Thanks.
View 1 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
Jun 26, 2007
As you see in the images the connection is closing. During the read it counts 5 columns which is correct. When I step through the code it closes the connection when it hits dt.Load(reader) and nothing is loaded into the datatable.
------------------------------------------------------------AS I STEP THROUGH -----------------------------------------------------------------------------------------------------------------------
Please help,
Thanks,
Tom
View 1 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
May 31, 2001
I seem to be having trouble with the distribution agent not doing what I want it to do. I have set up a few publications to run all the time but when I want to schedule a publication to run once a day this doesn't happen it defaults to run all the time.
Can the distrubition agent run some publications continusly and some publications scheduled?
Can anyone shed some light on this problem.
View 2 Replies
View Related
May 3, 2000
Please, i need some help with the replication i had configured.
I have two publications to the same subscriber, one with data filters and other not.
The one without data filters i have test manualy. But now after i have created the other one, the log reader says that '145 transactions with 347 commands' were delivered, but the distribution agents says that 'no replicated transactions are avaiable'.
I know that have many things to be replicated, but doesn´t work.
The Sql server agent is working on the distributor.
There is something that can be causing this error ?????
Please, if someone can help me i apologize
Thanks in regards
Sandra Lino
View 4 Replies
View Related
Feb 4, 2004
Hello,
What happens to these REPLication agents if SQL Agent is stopped and started:
Snapshot Agents
Merge Agents
Misc Maintenance Agents
Can the agent be stopped and started with no thought to the status of replication, or should the replication state be modified in some way before any change to the status of the Agent?
(I know REPL depends on agent, so wuestion is, can REPL simply resume or not when agent is re-started.)
Thanks.
MichaelGG
View 2 Replies
View Related
Mar 22, 2004
Hi Guys,
Ive accidently gone and deleted a snapshot agent off a working publication (tables distribution.dbo.mssnapshot_agents, msdb.dbo.sysjobs etc).
Is there a workaround to create a new snapshot agent for the publication without having to break or recreate the publication?
I have tried adding a snapshot and only to fail, can anyone help? thanks a million
---*** Tried adding a snapshot agent ***---
use publishing_database
go
-- Add snapshot job
exec sp_addpublication_snapshot @publication = N'publication_name',
@frequency_type = 4,
@frequency_interval = 1,
@frequency_relative_interval = 1,
@frequency_recurrence_factor = 0,
@frequency_subday = 8,
@frequency_subday_interval = 1,
@active_start_date = 20040101,
@active_end_date = 20040101,
@active_start_time_of_day = 0,
@active_end_time_of_day = 235959
GO
-- RESULT:
Server: Msg 14101, Level 11, State 1, Procedure sp_MSaddpub_snapshot, Line 73
The publication 'publication_name' already has a Snapshot Agent defined.
View 4 Replies
View Related
May 10, 2002
During testing, the log for tempdb filled up.
That caused the replication agents to get an error and stop.
Is there an easy way to have the agents wait a minute or 2 then try to restart?
Thanks
John
View 1 Replies
View Related
Sep 27, 2006
Hi all,
after creating the replication job (works) other agent jobs hang up. after restart the agent, the jobs work one time. t
can it be a problem with dieffernt agent profiles/accounts
many thanks
oliver
View 6 Replies
View Related
