Merge Agent Not Started - Start Synchronizing Disabled
Aug 6, 2006
i'm running a SQL Server 2000 SP42000.8.00.2039, developer.
i'm trying to setup a merge replication between the default istance and a named one of the same machine, using the same domain account for both publisher and subscriber.
when it comes to "start synchronizing" (right click on the subscriber merge agent), i found it disabled, just like it is running, but it is not (the icon shows a stop sign, even refreshing.)
The state is "disactivated". When i stop sync and start it again things don't change.
If i setup a "pull" subscription, i get a sequence of a message like "interface not supported" (a translation from italian "Interfaccia non supportata"): after 10 attempts, it stops.
i cannot find this error searching in internet, could you address me?
thanks in advance!
View 2 Replies
ADVERTISEMENT
Apr 18, 2007
Hello
We're deploying the db schema changes via an T-SQL Script.
Now I've tried synchronize the changes to the (merge-)subscriber via replication.
I've tried something like that:
create table dbo.c(
c_id uniqueidentifier rowguidcol not null default newid(),
c_desc nvarchar(60) not null,
constraint PK_c primary key (c_id)
)
// table a already existed
IF EXISTS (SELECT * FROM dbo.sysobjects WHERE id = OBJECT_ID(N'[dbo].[FK1_c_a]') AND type = 'F')
ALTER TABLE a DROP CONSTRAINT [FK1_c_a]
go
exec sp_addmergearticle @publication = N'publicationname', @article = N'c', @source_owner = N'dbo', @source_object = N'c', @type = N'table', @description = null, @column_tracking = N'true', @pre_creation_cmd = N'drop', @creation_script = null, @schema_option = 0x000000000000CFF1, @article_resolver = null, @subset_filterclause = null, @vertical_partition = N'false', @destination_owner = N'dbo', @auto_identity_range = N'false', @verify_resolver_signature = 0, @allow_interactive_resolver = N'false', @fast_multicol_updateproc = N'true', @check_permissions = 0, @force_invalidate_snapshot = 1
go
alter table c
add constraint FK_a_c foreign key (a.col2)
references katalog_zivilstand (c)
not for replication
In the end, the update runs well on the publisher (Replication compabilitiy-Level =90, Replicate DDL =1). But on synch to the subscriber, the Foreign Key cannot be propagated "FK.. references invalid table... error number 1767)
I don't see why?
Aren't the statements executed in the same order as on the publisher - in my script?
Thanks much for your advice
Aline
View 3 Replies
View Related
May 2, 2007
I created a snapshot publication (the engine is SQL2005 and the compatibility is 2000).
I got this message:
"The agent could not be started.
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
SQLServerAgent Error: Request to run job REPLSM-6 (from User DOMcustuser) refused because the job has been suspended.
Changed database context to SM. (Microsoft SQL Server, Error: 22022)"
And when i'm trying to reinitialize the publication, I get this:
"Replication Monitor could not start the Snapshot Agent to generate a new snapshot. You must start the Snapshot Agent manually before the subscription(s) can be reinitialized..."
What can I do? Why it doesn't work?
thnx
View 7 Replies
View Related
Dec 5, 2007
If a job is currently running and I want to disable it so that it does not run as scheduled for the following night, will it disrupt the current process?
View 1 Replies
View Related
Apr 2, 2015
How to configure alert when SQL Server Agent Job gets disabled. I want to get notified when Agent Job gets disabled.
View 2 Replies
View Related
May 30, 2008
Sql server service has been started with a normal user who do not have any permission but he is a domain user.
The sql server service can be started successfuly in cluster
But if the Same user is used to start the SQL Server Agent service there is an error.What is the mininumum priviledge to
start a sql server agent in cluster. Why it cannot the domain user cannot be used to start the sql agent service.
View 1 Replies
View Related
Aug 10, 2015
Is there a way to find out who enabled or disabled a SQL server agent job?
View 3 Replies
View Related
Nov 7, 2011
The Agent has never been run occurred on Snapshot Agent Status-Replicationhow do I make it run successfully??
View 6 Replies
View Related
May 18, 2015
while failover from one node to another node in cluster environment. cluster node is moving to another node but my SQL server services are not started.in event viewer i am getting bellow errorr event id 19019
[sqsrvres] StartResourceService: StartService (MSSQLSERVER) failed. Error: 42d
[sqsrvres] OnlineThread: Error 42d bringing resource online.
View 2 Replies
View Related
Jul 23, 2005
I have database on SQL Server 2000 set up with a merge publication.This publication is configured with a number of dynamic filters toreduce the amount of data sent to each client. Each client has ananonymous pull subscription. The merge process can be triggered by thewindows sync manager and my application.To improve performance I have created some helper tables to hold themapping between user login and primary keys of selected entities.For the replicated data to be correct the contents of the helper tablesneeds to be up to date.I need to fire off a stored procedure on the publisher beforereplication starts to verify that this data is up to date. I can notsee any documented way of doing this however I have been experimentingwith some unorthodox systems.Firstly has anyone any ideas?I have been considering adding a trigger to some of the tables used bythe Microsoft replication code - yes I know this is very nasty.My problems arise because executing this stored procedure will causesome data to be updated. In updating data we could create a newgeneration in the database. I must therefore run my stored procedurebefore any the Microsoft code makes any generation checks / updates.Anyone done anything similar, Anyone have any better ideas?Any comments would be gratefully received.
View 1 Replies
View Related
Jul 23, 2005
It's a Windows 2000 Server box with SQL 2000 on it. MSSQLSERVER &SQLSERVERAGENT services are logged in as valid domain user. I set up amail profile for that user, and can send email via Outlook 2003.However, when I go to the SQL Agent Properties in Enterprise Manager,Mail Profile is disabled.I've restarted the services & even tried rebooting the server. Thisworks on my other servers, but they're Windows 2003. Not sure ifthat's the problem though.Anybody have any clues?
View 1 Replies
View Related
Apr 26, 2004
Hi!
I have a small problem , but it's still a problem.
I have a SQL Server Agent job that runs a .cmd file. This CMD is logged to a textfile.
This process is locked, waiting for me to type a password, but I have nowhere to type that pass.
What I want to do is kill the process that i locking the logfile, because since the logfile is locked, the job cannot be started again (and it's a scheduled job).
The jobs status is 'Not Running'.
I have solved the problem by making the cmd write to another logfile, so the schedule will work, but the file is still locked, and I don't want to restart the server since it's a productionserver.
How to I find the process that is initialized from SQL Agent, and kill it?
Thanks!
Bix
View 4 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
Oct 10, 2007
We have a Process Task component setup in a couple SSIS jobs to call a command batch file to support transfering a file via Secure FTP to other servers and the process works fine if we start the SQL Agent job manually, however when the job is started via the scheduler, it fails with an exit code of 4. Even though there is a proxy setup on the agent job, is there a different user account being invoked by the scheduler??? We're on 2005 SP1 Hotfix 1 (2153). Thanks
Some more info...have found that if we leave a login session open on the server (login is the proxy account) the process works. It appears the issue is associated with a need to render/create a command window for the command line/batch process to run in and without an active windows session it fails....would seem to be that a product setup to run on a server in a batch mode would be able to work without this...is this the case? if so, how? Thanks.
View 11 Replies
View Related
Nov 21, 2005
Whenever I start my SQL Express 2005 database, I get the following in the logs :
View 10 Replies
View Related
Aug 21, 2001
Hello everyone,
Any ideas of how to start a SQL Agent job, from OTHER-THAN Enterprise Manager !!!
Does Microsoft provide any stored procs, extended procs or any SDK that can help me force-start a scheduled task ?
There has got to be a way, coz' Enterprise Manager is doing it !!!!..
Any help is greately appreciated.
Thanks..
View 3 Replies
View Related
Nov 16, 2007
I changed my server's service account to Domainsqladmin and the service started successfully.
I did the same for SQL Agent but the service starts and stops. In Event Viewer saw this error:
SQLServerAgent could not be started (reason: SQLServerAgent must be able to connect to SQLServer as SysAdmin, but '(Unknown)' is not a member of the SysAdmin role).
I checked Logins under under security in SSMS and the Domainsqladmin is a member of SysAdmin roles. What's wrong?
Canada DBA
View 6 Replies
View Related
Apr 8, 2001
I'm trying to set up SQL 7 for replication, so I set SQLAgent to start automatically, same as SQL Server itself. SQL Server starts fine, but SQL Agent "fails to connect in a reasonable time" according to the Event log (3000 milliseconds).
Can you suggest how I go about fixing this? They both are using valid logins, so I don't know what else could be wrong.
Advice appreciated!
Arthur
View 3 Replies
View Related
Aug 23, 2001
I have a problem with a server where for some reason when it is rebooted the SQLAgent service does not start automatically. You have to go into control panel, services and start it, even the it is set to Automatic.
Thanking in advance for any ideas??
View 1 Replies
View Related
Jun 11, 2004
hi
when i try to start sql agent hang then mmc
i look the log and the problem is the mail profile
i try remove it from the property of sql agent but this hang the mmc too
can i remove this with tsql?
thanks
View 2 Replies
View Related
May 4, 2002
In attempt to run the SQLServer Job Agent, the following error occurs:
An error 1068 (the dependency service or group failed to start) occured while performing this service opertion on the SQLServer Agent Service.
An user a/c with Administrator rights is assigned to the SQLServer Agent Service upon setup.
Any idea what is causing it?
Thanks in advance,
Ben
View 1 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
Mar 11, 2008
Hi guys,
I'm trying to set up merge replication between a SQL Server 2000 SP4 / Win2k box and a MSDE SP4/WinXP box and I'm finding that the initial snapshot isn't being produced.
The SQL Agent runs as a windows user that has admin privileges, the snapshot agent impersonates the SQL Agent. The SQL Server login for the agent account has the server role "System Administrators" and database access to all db's.
When I turn on logging and try to start the agent, the following is written to the log:
Microsoft SQL Server Snapshot Agent 8.00.760
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: SVRName-POS-POS_Test_Suburb-1
Connecting to Distributor 'SVRName'
SourceTypeId = 5
SourceName = SVRName
ErrorCode = 18456
ErrorText = Login failed for user 'SVRNameSQLAgent'.
The process could not connect to Distributor 'SVRName'.
Most of the posts I've seen regarding problems like this are due to subscriber authentication issues (not up to that, this is the initial snapshot) or windows/domain user permissions.
Any ideas what else it might be?
View 1 Replies
View Related
Feb 23, 2004
Hi,
I have installed the MSDE and use mixed mode authenticaton.
The SQL Server Agent will not start due to login failures.
Normally, I would use the Enterprise Manager Managment wizard to
correct the System Account and Connection Credentials.
Can anyone tell me how to achieve this using OSQL?
Thanks
View 8 Replies
View Related
Jun 5, 2015
We came across a biggg issue with SQL Agent service on one of our SQL Server 2012 production servers. Suddenly, it stopped working. So we just thought of disabling and enabling the service, but once we disabled and try to set automatic (before starting it), gives us error message "The Remote Procedure Call Failed [0x800706be]".
View 1 Replies
View Related
Apr 18, 2008
We are having problems w/ our agent. When we try to start it in computer management, it will say the agent started then stopped because it has nothing to do. In surface area config, when we try to start it it times out. Does anyone have experience with this? We are desperate. Thanks!
View 3 Replies
View Related
May 12, 2008
hi
i have start sql server agent then dispaly following error message
(The system cannot find specified path) occured while performing this service operation on the sqlserveragent service
View 4 Replies
View Related
May 14, 2007
Straight from the sqlagent error file: (the username and login I'm providing is correct. for testing purposes only its and admin account and works on another instance)
2007-05-14 15:12:07 - ! [298] SQLServer Error: 10061, TCP Provider: No connection could be made because the target machine actively refused it. [SQLSTATE 08001]
2007-05-14 15:12:07 - ! [165] ODBC Error: 0, Login timeout expired [SQLSTATE HYT00]
2007-05-14 15:12:07 - ! [298] SQLServer Error: 10061, An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001]
2007-05-14 15:12:07 - ! [000] Unable to connect to server '(local)'; SQLServerAgent cannot start
2007-05-14 15:12:38 - ! [298] SQLServer Error: 10061, TCP Provider: No connection could be made because the target machine actively refused it. [SQLSTATE 08001]
2007-05-14 15:12:38 - ! [165] ODBC Error: 0, Login timeout expired [SQLSTATE HYT00]
2007-05-14 15:12:38 - ! [298] SQLServer Error: 10061, An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001]
2007-05-14 15:12:38 - ! [382] Logon to server '(local)' failed (DisableAgentXPs)
2007-05-14 15:12:39 - ? [098] SQLServerAgent terminated (normally)
View 10 Replies
View Related
Jun 18, 2007
I cannot run SQl Server Agent service. Each time I try I get these 2 errors
Event Type:Error
Event Source:SQLAgent$MY_INSTANCE
Event Category:(2)
Event ID:17310
Date:18/06/2007
Time:09:27:49
User:N/A
Computer:MY SERVER
Description:
A user request from the session with SPID 53 generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
Event Type:Error
Event Source:SQLAgent$MY_INSTANCE
Event Category:Service Control
Event ID:103
Date:18/06/2007
Time:09:27:49
User:N/A
Computer:MY SERVER
Description:
SQLServerAgent could not be started (reason: SQLServerAgent cannot start because the msdb database is not set to a compatibility level of 70 or higher).
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
I am on SQL Server 2005. Do you have any ideas what might cause it and how to fix it?
Chris
View 3 Replies
View Related
Jul 20, 2005
I have a SQL Server 2000 that failed to start after a Windows reboot.Agent properties are checked to auto start if stopped. Under the AgentError Log, I have the following data:Information:SQL Agent stopping because of Windows shutdown.SQL Agent terminated normally.Error:SQL Server Error: 1115, cannot generate SSPI context SQLState HY000.Logon to server(local) failed.Help apprecaited. ThanksFrank*** Sent via Developersdex http://www.developersdex.com ***Don't just participate in USENET...get rewarded for it!
View 2 Replies
View Related
Jun 18, 2007
I cannot run SQl Server Agent service. Each time I try I get these 2 errors
Event Type: Error
Event Source: SQLAgent$MY_INSTANCE
Event Category: (2)
Event ID: 17310
Date: 18/06/2007
Time: 09:27:49
User: N/A
Computer: MY SERVER
Description:
A user request from the session with SPID 53 generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
Event Type: Error
Event Source: SQLAgent$MY_INSTANCE
Event Category: Service Control
Event ID: 103
Date: 18/06/2007
Time: 09:27:49
User: N/A
Computer: MY SERVER
Description:
SQLServerAgent could not be started (reason: SQLServerAgent cannot start because the msdb database is not set to a compatibility level of 70 or higher).
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
I am on SQL Server 2005. Do you have any ideas what might cause it and how to fix it?
Chris
View 3 Replies
View Related
Dec 14, 2007
HELLO TO ALL OF YOU
IS THERE ANY SQL COMMAND IN ORDER TO START SQL AGENT ?
THANKS IN ADVANCE
View 3 Replies
View Related