Oracle 9i -&&> SQL Server 2005: Snapshot Agent Aborts Suddenly Uninterrupted

Jun 14, 2006

Hi - I hope some of you can help me with this problem.

I'm trying to run the snapshot agent for 77 published tables, but the agent stops suddenly uninterrupted. It stops in the middle of taking a snapshot of a table containing 81,719,531 rows. The error message is pasted below.

Message
2006-06-14 05:33:33.53 [89%] Bulk copied 100000 rows from "ORAMSSQLREPL"."HREPL_ARTICLE_21_21" (57200000 total rows copied)
2006-06-14 05:34:12.57 [89%] Bulk copied 100000 rows from "ORAMSSQLREPL"."HREPL_ARTICLE_21_21" (57300000 total rows copied)
2006-06-14 05:34:51.23 [89%] Bulk copied 100000 rows from "ORAMSSQLREPL"."HREPL_ARTICLE_21_21" (57400000 total rows copied)
2006-06-14 05:35:29.99 [89%] Bulk copied 100000 rows from "ORAMSSQLREPL"."HREPL_ARTICLE_21_21" (57500000 total rows copied)
2006-06-14 05:36:09.82 [89%] Bulk copied 100000 rows from "ORAMSSQLREPL"."HREPL_ARTICLE_21_21" (57600000 total rows copied)
2006-06-14 05:36:49.38 [89%] Bulk copied 100000 rows from "ORAMSSQLREPL"."HREPL_ARTICLE_21_21" (57700000 total rows copied)
2006-06-14 05:37:28.56 [89%] Bulk copied 100000 rows from "ORAMSSQLREPL"."HREPL_ARTICLE_21_21" (57800000 total rows copied)
2006-06-14 05:37:35.36 [89%] The replication agent was shut down in response to an abort request.


Does anyone know what is causing this error and how I can possibly solve it?

Best Regards,
JB Plum

View 14 Replies


ADVERTISEMENT

Stored Procedure Works, Agent Job Aborts

Oct 8, 2006

One of my clients has a stored procedure on their secondary server thatcopies a bunch of data from the production server. (Replication willbreak the accounting software, according to its authors. The productionserver generates a nightly full backup, so if the secondary can bescripted to do a nightly restore from that same file, then that wouldprobably be a Big Win.)Anyway, if I execute the stored procedure from Query Analyzer, itfinishes (after nearly 24 hours) - tested once recently, and I'm sureat least a few times at some point in the past. If I run a SQL ServerAgent job that executes the stored procedure, then it gets cut off afterabout 15-20 minutes - tested once recently with a manual run, and forseveral weeks of scheduled runs before that. (This being a secondaryserver, it took a while for the problem to be noticed.) What are thelikely causes of this?Both servers are running SQL 2K with SP3, and limited to TCP/IP andnamed pipes. RPC is allowed, with a 600-second timeout, but thatdoesn't seem relevant, since both the successful and unsuccessfulmethods go well past that length. The production server is a recentpurchase, and works well for their daily operations; the secondaryserver and/or its network connection might be flaky for all I know,but that doesn't seem relevant either, since success appears todepend consistently on method of execution.

View 1 Replies View Related

Backup Database Aborts Job In The Agent, But Not When In A Query Window

Sep 17, 2007



Does anyone know why a backup database statement aborts a job in a stored procedure so that you can't handle the error with @@error, but when you run the same stored procedure in a query window the error handling does get run?

The snippet of code looks like this:


SET XACT_ABORT OFF

SET ANSI_NULLS OFF

set ansi_warnings off

set arithabort on

declare @backup_status int

declare @cmd varchar(1024)



SET NOCOUNT ON

print 'Options value: ' + convert(varchar, @@options)



set @backup_status = 0

if (@backup_mode = 'F')

begin


BACKUP DATABASE

@DB TO DISK = @BackupFile

with

NAME = @Name,

DESCRIPTION = @Description,

MEDIANAME = @MediaName,

MEDIADESCRIPTION = @Description,

STATS = 10,

init, nounload, noskip






if @@error != 0

begin


set @backup_status = 1


print '**************** Backup of ' + @DB + ' Failed'


end end

When this is run in a query window, the print statement at the bottom does get executed, but when run as a step in a sql agent job it does not.

Thanks.

View 1 Replies View Related

Notification To SQL Server 2005 Agent Job On Completion Of Oracle Package

Dec 21, 2007



Is there any built-in way of kicking off a job on SQL Server 2005 Agent whenever a package/job completes in Oracle?
Are there any (Triggers? Msft queue? Event Notification?) mechanisms to automate running a job on the SQL side?
Any article or knowledge articles would be appreciated also.

If not are there any built-in stardardized polling techniques? Or are there any timers in SSIS?
That way I can delay executing a child package until a certain record has been inserted into a control table in Oracle.
I don't want to write an inefficient for loop that blocks all other processing on the server and iterates once every second.

Thanks

View 1 Replies View Related

Run Sql Server Snapshot Agent From Within My C#.net

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

MS SQL Server 2000 Snapshot Agent

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

Clustered Sql Server 2005 Restarted Suddenly

Nov 4, 2007

Hi EveryOne,

WIndows 2003 sp2 and sqlserver 2005 standard edition -sp2.

Found following erors in The cluster and event logs.

error: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect
failed

error: [sqsrvres] OnlineThread: QP is not online.

error: [sqsrvres] printODBCError: sqlstate = HYT00;
native error = 0; message = [Microsoft][ODBC SQL Server
Driver]Timeout expired

[sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure

[sqagtres] SvcStop: service did not stop; giving up.
[sqsrvres] OnlineThread: asked to terminate while waiting for QP.


SQL Server is terminating in response to a 'stop' request from Service Control Manager



Earlier we had sudden Sql agent restart but this time sql server services were restarted .

What could be he reasons for this.

This machine has 64 GB ram and sql server has been alloted 30 Gb.
I found 30 Gb Usage in the dump file of Sqlserver

Can a memory Starved sql server could be a rason why sql server would have restarted

Thanks,
Gautham.R

View 1 Replies View Related

SQL Server 2008 :: Transactional Replication (Snapshot Agent)

Mar 19, 2015

Is there a way to force the snapshot to use a format file when bcp'ng the data to the subscriber?

The publisher and subscriber schemas are slightly different. Mainly added columns to the subscriber.

We have a post snapshot script that updates these additional columns on the subscriber.

I'd like to force the snapshot to use a format file, so it doesn't error when initially loading the data to the subscriber.

Is this possible?

View 1 Replies View Related

Snapshot Agent Cannot Start Server Execution Failed

May 22, 2006

Hello, I've configured SQL Server 2000 for merge replication and am trying to start the snapshot agent for the publication and after about 20 minutes of it trying to start, it gives up with this error.



Server execution failed

There is no more information in the event viewer. I've tried it with a bunch of different subscriptions. SQL Server and SQL Agent are running under a local account which has access to the replcation data directory. SQL Agent is running.

I'm Running SQL 2000 SP3.

Thanks

Robert Brown

View 3 Replies View Related

Snapshot Agent && Log Reader Agent Will Not Start.

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

Cannot Start Log Reader Agent And Snapshot Agent

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

Snapshot Agent,

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

SQL Server Agent And X64 Using OraOLEDB.Oracle.1: Dtexec From Cmd Works, But Job Fails

Aug 16, 2007

I am extracting data from an Oracle database and have installed the latest x64 ODAC. When I run the 64 bit dtexec in cmd the package runs fine with no errors, but when creating and executing a SSIS job in the agent it fails. I've tried creating the job using CmdExec as well and I get the same errors:

Microsoft (R) SQL Server Execute Package Utility
Version 9.00.3042.00 for 64-bit
Copyright (C) Microsoft Corp 1984-2005. All rights reserved.
Started: 11:12:43 AM
Error: 2007-08-15 11:12:45.63
Code: 0xC0202009
Source: Load Dimension Data Connection manager "ora"
Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x800703E6.
An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x800703E6 Description: "Invalid access to memory location.".
End Error
Error: 2007-08-15 11:12:45.65
Code: 0xC020801C
Source: CopyCustomers CustomerSource [1]
Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "ora" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
End Error
Error: 2007-08-15 11:12:45.65

The CmdExec job step uses the _exact_ same command as the one I execute successfully in cmd:
"c:Program FilesMicrosoft SQL Server90DTSBinnDTExec.exe" /FILE "C:PackagesLoad Dimension Data.dtsx" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EW


I have managed to find two work arounds, but they are quite ugly:

1) Schedule the package execution using Windows Task Scheduler, basically create a bat file which runs the package.
2) Schedule the package in SQL Server agent, but as T-SQL script and use xp_cmdshell, i.e. EXEC xp_cmdshell 'dtexec /FILE "C:PackagesLoad Dimension Data.dtsx" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EW'

Both work and use the 64 bit dtexec. Not that elegant though..

CmdExec and the 32 bit version of dtexec works, but is not good enough for me since we bought new hardware and 64 bit software just to be able to address more memory. Has anyone managed to execute a SSIS package successfully using the agent and the 64 bit OraOLEDB.Oracle.1?


Any help would be greatly appreciated. Thanks!

Btw, I am using Windows Server 2003 x64 and SQL Server with SP2.

View 9 Replies View Related

SQL 2005 - Why Do Databases Suddenly Think They Are Replicated?

Nov 10, 2007



Hello All

I hope somebody can help. This is the second time I've seen this issue. The first time I thought it was a one off, but now I'm getting concerned.

I have two clients - one had Merge replication set up on a database that had a log log file that just grew and grew. The database was set to SIMPLE recovery. I could understand the log file growing if it was set up for transactional replication, but it wasn't transactional, just merge. Looking in sys.databasese the log_reuse column was set to REPLICATION.

I ran the sp_repldone stored proc on this database and all was well - I could shrink the log file down to a reasonable size. This server was SQL Server 2005, Service Pack 2.

Now I have yet another client who has a growing transaction log file. Low and behold the log_reuse for the database is set to REPLICATION again. This server has never had any type of replication set up at all!!!! The log file is still growing and DBCC OPENTRAN indicates undistributed transcations. This particular server is SQL Server 2005 Service Pack 1.

Can someone PLEASE shed some light on what's going on here? Is there some kind of bug that I don't know about? Searching Goolgle Groups seems to indicate that other people have had this problem, and they have have to set up replication and run sp_repldone to resolve it, but that's surely uncalled for on a database that has never seen replication?

Thanks

SQLGal2

View 2 Replies View Related

Questions About Snapshot Agent

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

Snapshot Agent Won't Start

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

Snapshot Agent Is On Hang

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

Snapshot Agent - Stopping

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

Snapshot Agent Error

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

Snapshot Agent Retried And Failed

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

Transactional Replication && Snapshot Agent

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

Snapshot Agent Error : Running

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

Snapshot Agent Can Not Connect To Distributor

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

Transactional Replication- Snapshot Agent

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

Snapshot Agent Missing Files.

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

Dynamic Snapshot Agent Error

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

Unable To Get Snapshot Agent To Initialize

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

SQL Server Admin 2014 :: BCP Aborts On First FK Violation

Sep 26, 2013

I want to use BCP to load data from a text file.

By default, constraints are turned off in bcp, so I use the CHECK_CONSTRAINTS hint.

bcp aborts if ANY of the rows contains a FK violation. No data get loaded.

So if I add the -b 1 batch size option, it loads all data UNTIL the first FK violation, but nothing after that.

I want to load EVERYTHING ... except for the violations. But bcp won't let me. Is there a way?

View 2 Replies View Related

SQL 2005 Merge Repl Suddenly Stopped Working

Mar 28, 2006

Hello...

We have had Merge Replication working for the past few months (SQL 2005 to SQL Mobile) and suddenly today the replication URL that points to the SqlCESA30.DLL does not work. I have tried re-running the SQL Mobile virtual folder wizard a few times....resetting IIS and even a re-boot...and still the URL is not available.

Is there anything that might provide some clue as to why this has unexpectedly failed?

thanks for any help!

- will

View 3 Replies View Related

Replication :: Snapshot Agent Updates Statistics

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

How To Programmatically Find Out Whether Snapshot Agent Has Finished?

Oct 15, 2007

Hi,

I want to generate a new snapshot using stored procedures. I want to wait for the snapshot files to be created and then execute a stored procedure. What's the best way to determine that the snapshot has completed successfully? I thought of doing something like:

exec msdb.dbo.sp_help_job
@job_name = @job_name
@job_aspect = 'job',
@execution_status = 1

however I can't put the results of that proc into a temp table because I get this error:
Msg 8164, Level 16, State 1, Procedure sp_get_composite_job_info, Line 72
An INSERT EXEC statement cannot be nested.

Any ideas? I'd like a T-SQL solution.

Thanks,
Mark.

View 3 Replies View Related

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 View Related

Snapshot Agent: Query For Data Failed

Jul 6, 2007

When running the snapshot agent for a new publication I get the message:



Message: Query for data failed
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: COLV_90_TO_80: Cannot convert parameter param1: Resulting colv would have too many entries.
Stack: (Source: MSSQLServer, Error number: 20005)
Get help: http://help/20005
Message: The statement has been terminated.
Stack: (Source: MSSQLServer, Error number: 3621)



The database has another publication, that was created prior to upgrade to sql server 2005 from sql server 2000 sp4. This publication is working ok, and there are no problems when running the snapshot agent for this publication.

The publications are using filtered articles, and all properties for the publications are the same.



Any help to solve this problem will be much apreciated.

View 3 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved