Trouble Getting Snapshot Agent To Initialize Publication
Nov 16, 2006
I have been trying to set up transactional replication between an OLTP SQL Server 2005 Standard edition server and a BI SQL Server 2005 Enterprise edition server. I am using a pull subscription. I was able to establish the replication from the developement server to the BI server however when I tried setting up the replication between the production environment and the BI server, using the same configuration settings, I ran into a problem. The production server had been renamed after it was initially set up. I used the sp_dropserver and sp_addserver to solve this issue and was able to run the replication wizard. However once the wizard finishes the snapshot agent doesn't initialize the publication. When I look at the replication monitor it has a status of "never run". I try to run it manually and it appears to run for a few seconds then stops and still has the status of "never run". I don't get any error messages and can't find anything in the log. I am wondering if this is related to the server rename? I am hoping to find a soultion that doesn't involve uninstalling SQL Server and reinstalling since this is a production environment.
Thanks.
View 3 Replies
ADVERTISEMENT
Feb 20, 2006
I am unable to get my snapshot agent to initialize. When I start the "View Snapshot Agent Status" and press the Start button, it appears that the snapshot agent attempts to starts and then it doesn't.
I have configured the a distribution server and need to push a replication to another database, both can connect, etc.
I used the wizard to configure the distributon server and subscription server. I am using AdventureWorks, and am attempting to replicate a single small table.
View 4 Replies
View Related
Apr 19, 2007
Hi all,
I have a merge publisher with Snapshot agent for that scheduled to run everyday morning, This was runnning till yesterday. But it is not running today and giving the below error.
Can anyone help me out to solve this error? This is occuring in production environment, i really need a solution as fast as possible.
Error messages:
· Message: Failed to read column data
Stack: at Microsoft.SqlServer.Replication.Snapshot.SqlServer.NativeBcpOutProvider.ThrowNativeBcpOutException(CConnection* pNativeConnectionWrapper)
at Microsoft.SqlServer.Replication.Snapshot.SqlServer.NativeBcpOutProvider.BcpOut(String strBcpObjectName, String strBcpObjectOwner, String strBaseBcpObjectName, Boolean fUnicodeConversion, String strDataFile, String strLoadOrderingHint, String strWhereClause)
at Microsoft.SqlServer.Replication.Snapshot.SqlServer.NativeBcpOutProvider.BcpOut(String strBcpObjectName, String strBcpObjectOwner, String strBaseBcpObjectName, Boolean fUnicodeConversion, String strDataFile, String strLoadOrderingHint)
at Microsoft.SqlServer.Replication.Snapshot.SqlServer.NativeBcpOutProvider.BcpOut(String strBcpObjectName, String strBcpObjectOwner, String strDataFile)
at Microsoft.SqlServer.Replication.Snapshot.MergeContentsBcpOutWorkItem.DoWork(MergeSnapshotProvider snapshotProvider, IBcpOutProvider bcpOutProvider)
at Microsoft.SqlServer.Replication.Snapshot.MergeContentsBcpOutThreadProvider.DoWork(WorkItem workItem)
at Microsoft.SqlServer.Replication.WorkerThread.NonExceptionBasedAgentThreadProc()
at Microsoft.SqlServer.Replication.WorkerThread.AgentThreadProc()
at Microsoft.SqlServer.Replication.AgentCore.BaseAgentThread.AgentThreadProcWrapper() (Source: MSSQLServer, Error number: 0)
Get help: http://help/0
· Message: Shared Memory Provider: No process is on the other end of the pipe.
Stack: (Source: MSSQLServer, Error number: 233)
Get help: http://help/233
· Message: Communication link failure
Stack: (Source: MSSQLServer, Error number: 233)
Get help: http://help/233
· Message: Shared Memory Provider: No process is on the other end of the pipe.
Stack: (Source: MSSQLServer, Error number: 233)
Get help: http://help/233
Message: Communication link failure
Stack: (Source: MSSQLServer, Error number: 233)
Thanks,
Thams
View 16 Replies
View Related
Nov 9, 2006
I'm trying to setup merge replication and get the following error from the snapshot agent after I've finished the 'New Publication Wizard'. This doesn't make sense to me as it is an automatic process. Also, it looks like it is complaining about a 'dbo.MSmerge_cont...' view which is a view created automatically for the merge publication.
ERROR MESSAGE:
The identifier that starts with '<EVENT_INSTANCE><EventType>CREATE_VIEW</EventType><PostTime>2006-11-09T09:56:48.390</PostTime><SPID>152</SPID><ServerName>XF4SWC' is too long. Maximum length is 128.
FULL DETAILS:
Message: The identifier that starts with '<EVENT_INSTANCE><EventType>CREATE_VIEW</EventType><PostTime>2006-11-09T09:56:48.390</PostTime><SPID>152</SPID><ServerName>XF4SWC' is too long. Maximum length is 128.
Command Text: IF OBJECT_ID(N'[<EVENT_INSTANCE><EventType>CREATE_VIEW</EventType><PostTime>2006-11-09T09:56:48.390</PostTime><SPID>152</SPID><ServerName>XF4SWCS464</ServerName><LoginName>NT AUTHORITYSYSTEM</LoginName><UserName>dbo</UserName><DatabaseName>liport2_gts</DatabaseName><SchemaName>dbo</SchemaName><ObjectName>MSmerge_contAE2EB588ABFA4C13825D4D44CB2D50CB_90</ObjectName><ObjectType>VIEW</ObjectType><TSQLCommand><SetOptions ANSI_NULLS="OFF" ANSI_NULL_DEFAULT="ON" ANSI_PADDING="ON" QUOTED_IDENTIFIER="ON" ENCRYPTED="FALSE" /><CommandText>create view dbo.MSmerge_contAE2EB588ABFA4C13825D4D44CB2D50CB_90 as select * from MSmerge_contents where 1 = 2</CommandText></TSQLCommand></EVENT_INSTANCE>]', 'V') IS NOT NULL DROP VIEW [<EVENT_INSTANCE><EventType>CREATE_VIEW</EventType><PostTime>2006-11-09T09:56:48.390</PostTime><SPID>152</SPID><ServerName>XF4SWCS464</ServerName><LoginName>NT AUTHORITYSYSTEM</LoginName><UserName>dbo</UserName><DatabaseName>liport2_gts</DatabaseName><SchemaName>dbo</SchemaName><ObjectName>MSmerge_contAE2EB588ABFA4C13825D4D44CB2D50CB_90</ObjectName><ObjectType>VIEW</ObjectType><TSQLCommand><SetOptions ANSI_NULLS="OFF" ANSI_NULL_DEFAULT="ON" ANSI_PADDING="ON" QUOTED_IDENTIFIER="ON" ENCRYPTED="FALSE" /><CommandText>create view dbo.MSmerge_contAE2EB588ABFA4C13825D4D44CB2D50CB_90 as select * from MSmerge_contents where 1 = 2</CommandText></TSQLCommand></EVENT_INSTANCE>]
Parameters:
Stack: at Microsoft.SqlServer.Replication.AgentCore.ReMapSqlException(SqlException e, SqlCommand command)
at Microsoft.SqlServer.Replication.AgentCore.AgentExecuteNonQuery(SqlCommand command, Int32 queryTimeout)
at Microsoft.SqlServer.Replication.AgentCore.ExecuteDiscardResults(CommandSetupDelegate commandSetupDelegate, Int32 queryTimeout)
at Microsoft.SqlServer.Replication.AgentCore.ExecuteAdHocQueryDiscardResults(String strQuery, SqlConnection connection)
at Microsoft.SqlServer.Replication.Snapshot.MergeSnapshotProvider.GenerateSystemTableBcpFiles()
at Microsoft.SqlServer.Replication.Snapshot.MergeSnapshotProvider.DoPostArticleFilesGenerationProcessing()
at Microsoft.SqlServer.Replication.Snapshot.SqlServerSnapshotProvider.GenerateSnapshot()
at Microsoft.SqlServer.Replication.SnapshotGenerationAgent.InternalRun()
at Microsoft.SqlServer.Replication.AgentCore.Run() (Source: MSSQLServer, Error number: 103)
Get help: http://help/103
Server XF4SWCS464, Level 15, State 4, Procedure , Line 1
The identifier that starts with '<EVENT_INSTANCE><EventType>CREATE_VIEW</EventType><PostTime>2006-11-09T09:56:48.390</PostTime><SPID>152</SPID><ServerName>XF4SWC' is too long. Maximum length is 128. (Source: MSSQLServer, Error number: 103)
Get help: http://help/103
View 3 Replies
View Related
Mar 18, 2015
I have automated process, which synchronizes a transactional publication using initialize from backup approach. It drops subscriptions and puts them back again once the restore on the subscriber is completed.
Dropping the subscriptions causes a lot of blocking and deadlocking. I've decided to remove those steps, but it causes loss of data on the subscriber.
Is it a must to drop and re-create the subscriptions during such process? If not, how can I avoid the loss of data?
View 0 Replies
View Related
Jun 2, 2006
Hence you have a database which huge tables and a transactional replication (push subscriptions).
Now my question:
1. if I have to initialize a snapshot but I would like to do it without the snapshot agent, what methods are available?
2. Usually the distribution agent will request an initialize snapshot. How can I tell him, that I would like to use an alternative method and that the distribution agent should NOT request a snapshot?
3. Any suggestions about a good practive for materializing huge and big tables wihtout using the disitrbution agent (e.g. "switch off" replication, bcp table out of the primary site and bcp it into the target site, "start" distribution agent so that it doesn't request a snapshot).
Regards
Nobsay
View 6 Replies
View Related
Feb 1, 2007
Hello all,
I am developing a system using SQL Server replication between SQL Server EXPRESS 2005 clients and SQL Server 2005 servers. I initialize the replica databases with a script, then I do not want to initilize the subscriber with the snapshot; I configure each subscriber to "not initilize", but when I run the first synchronization the snapshot copy process is always is executed.
Maybe am I forgetting something? Can I use this SQL Server EXPRESS - SQL Server replication scheme without initialize the subscribers with the snapshot?
Thaks for reading!
View 5 Replies
View Related
Feb 20, 2006
I have a pretty big (350 gb) OLTP database that I want to replicate in its entirety. I'm concerned about the impact of taking a snapshot of it (it is processing at some level pretty much 24x7). I know on SQL2005 there is the option to initialize from backup, but unfortunately we won't be on 2005 in time.
I'm thinking of doing something like this:
Set up the distributor, publication, and subscription
Turn off distribution agent
Set the publisher to "sync with backup"
Backup the publisher, full then log
Truncate tables MSrepl_transactions and MSrepl_commands in the distribution db (I don't have any other replication going on)
Turn off "sync with backup"
Restore the full and tran log backups to new subscriber db
Create subscriber stored procs in subscriber
Start up distribution agent
I'm looking for opinions on whether it's worth going this route to avoid taking the snapshot. Data integrity is the number one priority -- if I have to do a snapshot to ensure that, I will do it.
Thanks in advance!
Mike
View 1 Replies
View Related
Nov 21, 2006
Hi,
I am in need of some help with this error - I am seeing on my PDA units. Here is my scenario:
I have 5 PDA units that use merge replication with SQL 2005. These PDA units replicate fine. But when I try to sync a 6th or 7th PDA unit, I see the following error:
Source : Microsoft SQL Server 2005 Mobile Edition - The snapshot for this publication has become obsolete. The snapshot agent needs to be run again before the subscription can be synchronized. -2147198698
I know that if I regenerate a new snapshot, I will be able to sync fine. But here are my concerns and questions:
What happens to the first 5 PDAs when I regenerate the a new snapshot.
Will they be able to sync without losing the data?
Does generating a new snapshot, relinitialize all the subscriptions?
Am I missing the whole picture with generating a new snapshot?
Thanks,
P
View 4 Replies
View Related
Feb 14, 2007
When I am trying to synchronize my sql server ce database with sql server 2000, I am getting this error in the Replication Monitor and Synchronization gets fail.
How to Create initial snapshot or is there any step by step configuration document available for Merge Replication with SQL server 2000 and sql ce.
View 9 Replies
View Related
Jul 13, 2006
Hello all,
I have a unusual problem with a snapshot publication that I am having a hard time troubleshooting. The servers in question are all SQL 05 Enterprise. Here is the scenario:
Staging Server - This server acts as the publisher of the snapshot
Production Server - This server is the subscriber of the staging snapshot
Cascade Servers - These servers receive transactional updates from the production server
The staging server applies the snapshot to production successfully. From there the production server has a transactional publication which the subscribers are the cascade servers.
This model worked for a long time where we would generate the snapshot apply it to production and the updates would be sent to the cascade servers. All of a sudden there is a problem with the transactional publication from production -> cascade. There are 7-10 tables that do not receive the updates and all data in the problematic tables is truncated. The other remaining tables in the subscription receive the updates as needed. Looking at replication monitor and all other logs shows that the transactions are being replicated, but yet the 7-10 problematic tables do not contain any data. The only solution I have found for this is to recreate the entire replication model from scratch.
Any advice on how to handle this scenario? Is my model for using a transactional publication to cascade changes to a subset of servers incorrect?
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
Feb 6, 2006
Hi
I've big problems with my SQL Server 2005 Std. merge replication/snapshot share
I want to create a mobile application based on a ms sql 2005 mobile database running on a pocketpc 2003se.
for this task i installed iis, sql server 2005 std. and the sql server mobile tools.
i created a dedicated user for making snapshots in the new created and functionable publication, but when i start the web sync wizard, i alwas get the failurmessages
snapshot share "......" cannot be accessed, please specify a new share
the access permissions based on the share an based on the ntfs area are set right.
the user, i chose for the anonymus access (the same, as for creating snapshots), has enough rights on the folder. also when creating a new share, with different share name, and using another user for anonymus access (standard iusr_machine_name) i get the same message
do you have any suggestions for my problem??
please i need help as soon as possible
best regards
View 6 Replies
View Related
Jul 21, 2006
I re-created a publication that was having problems and it gives this error when I start the snapshot agent from SQL Server Management Studio: I am stuck on how to resolve - any ideas?
"The publisher's identity range allocation entry could not be found in MSmerge_identity_range table. Transaction count after EXECUTE indicates that a commit or ROLLBACK TRANSACTION statement is missing. Previous Count = 1, current count = 2."
select * from MSmerge_identity_range returns 19 entries but I don't know how to fix.
I have tried deleting and re-creating but always get this error.
My other publications and subscriptions are working fine and I was able to create a new test publication that worked but can not get this one to work that worked fine up until today.
Any ideas?
View 2 Replies
View Related
Sep 24, 2006
Dear Colleagues,
I am using Windows Server 2003 RT, and SQL Server 2005.
When Replication is performed with SQL Server Mobile. All 3 taskes i.e. Publisher creation, Article Publish, Snapshot agen starting. All are ok.
However after replication is done when checking the Status of the Snapshot Agent it is not Running, and I cannot make it Run as well.
Please advice me as to what could possibily be wrong with it, what can I do.
Thankx.
View 5 Replies
View Related
Feb 3, 2006
Hello,
I need to run the sql server snapshot agent from within my c#.net 1.0 code. Regards
View 1 Replies
View Related
Jun 22, 2006
Hi, I was wondering if changing the schedule of the snapshot agent will do any effect the unc/snapshot files ? I'm now doing merge replication and i am applying snapshot from alternate location. If i change the schedule do i need to re run the snapshot agent ? I'm afraid that the current snapshot will be expired..
View 1 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
Nov 30, 2015
We have initiated reinitialize subscription by which snapshot agent is started and hanged at 26%.We have a publication of 6 articles, transactional replication, using SQL Server 2008R2.
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
Oct 14, 2007
hi, there;
I got a snapshot agent error:
[SQL-DMO]WriteFile error on '\Mysnapshotunc20071013231104Tracer_4.cft'.
(Source: Tracer (Data source); Error number: 0)
where "Tracer" is one of my tables, but it is never used.
This replication has been used for about three years without anyproblem. But suddenly I got this error.
Does anybody know what cause this and how I can fix it?
Cheers,
View 3 Replies
View Related
Mar 16, 2006
I have spent all day reading microsoft material and reading through this site to figure out what is wrong with my schedule job without success. I have come to the point where I can't take it no more. Would someone pleaseee help out a sister?
This is the situation: I created a very simple package on my server A. This package pull data from server B and load into server C:
B====> C
I deployed and copy and install the package successfully to the target server c. When
Now, I can run the package from either MSDB and file system storage.
My problem is when I schedule this package. It failed with the log below.
All my server are on the same domain and I have a domain account. When I schedule and run the job with my domain account, I get the following error: I have administrative rights in all the servers.
Job Name DW_DataImport
Step Name (Job outcome)
Duration 00:00:00
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
Message
The job failed. Unable to determine if the owner (Weblogeomon) of job Dw_DataImport has server access (reason: Could not obtain information about Windows NT group/user 'Weblogeomon', error code 0x5. [SQLSTATE 42000] (Error 15404) The statement has been terminated. [SQLSTATE 01000] (Error 3621)).
When I change it to sa, I get the following:
Date 3/16/2006 2:25:05 PM
Log Job History (Dw_DataImport)
Step ID 0
Server DW_Server3
Job Name Dw_DataImport
Step Name (Job outcome)
Duration 00:01:55
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
Message
The job failed. The Job was invoked by User sa. The last step to run was step 1 (Dw_DataImport).
Worst yet, I created
CREATE CREDENTIAL [SSISCredential] WITH IDENTITY = 'Weblogeomon',
secret = '<password>'
Sp_add_proxy @proxy_name='SSIS_Proxy', @credential_name='SSISCredential'
Sp_grant_login_to_proxy @login_name='DwAdmin', @proxy_name='SSIS_Proxy'
Sp_grant_proxy_to_subsystem @proxy_name='SSIS_Proxy', @subsystem_name='SSIS'
When I schedule and run the job with DwAdmin, It still fails.
What am I doing wrong? and whay do I need to do?
Your contribution will be appreciated.
Thanks
Omon
View 9 Replies
View Related
Aug 16, 2006
Hello Sir,
Now I'm choosing Trasactional publication as my publication type. I now can successfully replicate the data from publisher to subscriber without any error.
But now my question is what is the usage of snapshot agent? When I go to Replication Monitor > Agents > Snapshot Agents > Start Agent but failed.
I need to check with you whether the way I start the snapshot agent was not correct? What is the effect if I drop snapshot agent during the replication and DBUpdate are running?
Please kindly help me .
Thank You.
View 13 Replies
View Related
Aug 4, 2006
Hello, need some guidance.
I noticed that my snapshot agent never got moving at all and has been failing. It keeps on generating errors in the System Log with every retry...
The server {08B0B2D9-3FB3-11D3-A4DE-00C04F610189} did not register with DCOM within the required timeout.
and this
SubSystem Message - Job 'mws-cpmorder-CPmOrder_Mobile-2' (0x669FF0D471C2A54FA11F764B1E3B0DFD), step 2 - Server execution failed
in the application log.
Any help is appreciated.
Rgds
View 1 Replies
View Related
Jun 27, 2007
Why would you schedule a Snapshot Agent to run daily, weekly, monthly, etc. for Transactional replication when the transactions are replicated once the change is committed to the Publication database?
Does this help to replicate DDL against the Subscriber?
Thanks,
Thomas LeBlanc
View 1 Replies
View Related
Apr 25, 2007
I have a problem when i Want to run the Snapshot Agent in SQL Server 2005. I have done all the tutorial called Replication Data with Mobile Clients and i done the previous tutorial called : Preparing the Server for Replication. But in the Lesson One i can't run the Snapshot Agent but the publicationis good. Can you help me ?
This is the error's code :
Date 25/04/2007 10:44:27
Log Job History (NTI-PC-118-AdventureWorks-AdvWorksSalesOrdersMerge-2)
Step ID 2
Server NTI-PC-118
Job Name NTI-PC-118-AdventureWorks-AdvWorksSalesOrdersMerge-2
Step Name Run agent.
Duration 00:00:01
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
Message
2007-04-25 09:44:28.29 -Publisher NTI-PC-118
2007-04-25 09:44:28.29 -PublisherDB AdventureWorks
2007-04-25 09:44:28.29 -Publication AdvWorksSalesOrdersMerge
2007-04-25 09:44:28.29 -ReplicationType 2
2007-04-25 09:44:28.29 -Distributor NTI-PC-118
2007-04-25 09:44:28.29 -DistributorSecurityMode 1
2007-04-25 09:44:28.29 -XJOBID 0x893D7BB9E72044489F0A1C1878663E1D
2007-04-25 09:44:28.29 --------------------------------------
2007-04-25 09:44:28.29 Connecting to Distributor 'NTI-PC-118'
2007-04-25 09:44:28.43 The replication agent had encountered an exception.
2007-04-25 09:44:28.43 Source: Replication
2007-04-25 09:44:28.43 Exception Type: Microsoft.SqlServer.Replication.ReplicationAgentSqlException
2007-04-25 09:44:28.43 Exception Message: The remote server "NTI-PC-118" does not exist, or has not been designated as a valid Publisher, or you may not have permission to see available Publishers.
2007-04-25 09:44:28.43 Message Code: 14080
2007-04-25 09:44:28.43
Thanks you
View 4 Replies
View Related
Apr 24, 2006
I'm trying to set up merge replication between SqlServer 2000 and SqlMobile 2005. When I create the publication, I select merge replication for SqlServer CE. When I view the status of the snapshot agent, the error message is "the process could not connect to Distributor. The step failed".
I've verified both SqlServer and SqlServer Agent are running under the same domain account (with admin access to the server). This domain account has full access to the snapshot shared folder. I've also run "exec sp_helpserver", which gives me the server name for both the name and network_name fields where id=0.
I'm able to successfully set up merge replication between SqlServer 2005 and SqlMobile 2005, but my production servers are sql 2000.
View 2 Replies
View Related
Sep 7, 2006
When you create a transactional Replication.Is there a way to disable to snapshot agent scheduler. I believe that there is a way to disble it when you create a publisher.
Help ME!!!!!!!!!!!!!!!
View 3 Replies
View Related
Jan 16, 2007
My Snapshot Agent for SQL Server 2005 sometimes does not fully complete. I am expecting around 2073 files in the snapshot folder but only get 492 (this number does change). I have immediate_sync set to true, so I should get a full snapshot every time. It seems to quit after all data has been BCP'ed out and before the schema generation starts. I do get the "The replication agent has not logged a progress message in 10 minutes. This might indicate an unresponsive agent or high system activity. Verify that records are being replicated to the destination and that connections to the Subscriber, Publisher, and Distributor are still active. " message in the MSSnapshot_history table.
I am guessing that there is some sort of blocking that is preventing the snapshot agent from continuing and then it times out and dies. But that is a total guess as I have not been able to observe the behavior, only the outcome.
Any suggestions to what the cause is or how I can fix it?
Thanks, Amy
View 4 Replies
View Related
Feb 17, 2006
I am setting up a large number of Push subscribers to a single publication. because of the large number of subscribers, I am not doing the merge with agent jobs, but with SQL RMO. All works well, but from time to time I am getting a funny error when I add a event handler to the snapshotagent, to return the messages, if some feedback to the screen on how the process is getting along.
The error also happen when the process is al most done. Basically when I am not compiling in this line, then NO error.
//Add the Event Handler to receive the Status changes
DynamicSnapshotAgent.Status += AgentEvent;
But once I started getting the error, then it would not go away, sometimes if the publication & subscribers is recreated it goes away but not always, first do not use the event anymore, and at some stage I can put is back after a few succesful dynamic snapshot, then I can enable the event and it will work again........
Any help welkom
Regards
Gertus
Error:
The replication agent had encountered an exception.
Source: Unknown
Exception Type: System.InvalidOperationException
Exception Message: Operation is not valid due to the current state of the object.
Message Code: Not Applicable
View 7 Replies
View Related
Mar 27, 2008
Greetings
We're having trouble getting the Agent started. The service is set to login as NT AUTHORITY/System. In an effort to attempt to diagnose the problem we changed the service (using Service Control Manager) to login as a user with Administrator rights on the server and we got the same error, except for that user.
[298] SQLServer Error: 18456 Login failed for user NT AUTHORITYSYSTEM [SQL STATE 28000]
[298] SQL Server Error: 4060 Cannot open database "EP_SessionState" requested by the login. The login failed [SQL STATE 42000]
I'm sure this is a common problem with an easy solution however I can not find out much about EP_SessionState through Google and was hoping someone could help.
Thanks
View 4 Replies
View Related
Jun 26, 2015
We have transactional replication publications from SQL 2014 to SQL 20122008 R2. When we add new tables to the existing publication and start the snapshot agent, Snapshot agent updates the statistics for random tables on the publisher DB. It appears that all the outdated statistics are being updated regardless which table is being initiated. In a highly transactional environment we can't update the statistics every time. its causing huge issues for us. Is there any work around for this ?Â
View 8 Replies
View Related
