Hello,
i use a transactional replication to load my datawarehouse DB everynight.
This works fine for the first repliaction but on the second i get the error "Agent message code 21074 the subscriptions need to be reinitialized..." and i have to reinitialize with new snapshots.
I can't see why this happen.
Somebody got an idee ?
Thanks for your help and best regards
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 RelatedHello,
We are consistently getting the error message below on our subscribers that have blob images. Is there a way to increase a setting to avoid SQL to throw this error, or another suggestion? Thanks in advance.
John
Error messages:
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.
18 -BcpBatchSize 100000
18 -ChangesPerHistory 100
18 -DestThreads 2
18 -DownloadGenerationsPerBatch 5
18 -DownloadReadChangesPerBatch 100
18 -DownloadWriteChangesPerBatch 100
18 -FastRowCount 1
18 -HistoryVerboseLevel 3
18 -KeepAliveMessageInterval 300
18 -LoginTimeout 15
18 -MaxBcpThreads 2
18 -MaxDownloadChanges 0
18 -MaxUploadChanges 0
18 -MetadataRetentionCleanup 1
18 -NumDeadlockRetries 5
18 -PollingInterval 60
18 -QueryTimeout 400
18 -SrcThreads 2
18 -StartQueueTimeout 0
18 -UploadGenerationsPerBatch 3
18 -UploadReadChangesPerBatch 100
18 -UploadWriteChangesPerBatch 100
18 -Validate 0
18 -ValidateInterval 60
Due to the memory leak issue with respect to replicating blobbed images we have changed UploadGenerationsPerBatch to = 3.
I have Visual Web Developer worked on my computer, but I can't make SQL Server work for data-driven. I have uninstalled and install VWD from http://msdn.microsoft.com/vstudio/express/downloads/default.aspx , the same Error message...... "..unexpected fail to install SQL server...", the copy of Summary.txt as below:
-----------------------------------------------------------------------------------------------------------------------------------------------------------
Microsoft SQL Server 2005 Setup beginning at Sat Jul 28 06:54:25 2007
Process ID : 3324
c:8845baf7ee339eaf6setup.exe Version: 2005.90.3042.0
Running: LoadResourcesAction at: 2007/6/28 6:54:24
Complete: LoadResourcesAction at: 2007/6/28 6:54:24, returned true
Running: ParseBootstrapOptionsAction at: 2007/6/28 6:54:24
Loaded DLL:c:8845baf7ee339eaf6xmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2007/6/28 6:54:25, returned false
Error: Action "ParseBootstrapOptionsAction" failed during execution. Error information reported during run:
Could not parse command line due to datastore exception.
Source File Name: utillibpersisthelpers.cpp
Compiler Timestamp: Wed Jun 14 16:30:14 2006
Function Name: writeEncryptedString
Source Line Number: 124
----------------------------------------------------------
writeEncryptedString() failed
Source File Name: utillibpersisthelpers.cpp
Compiler Timestamp: Wed Jun 14 16:30:14 2006
Function Name: writeEncryptedString
Source Line Number: 123
----------------------------------------------------------
Error Code: -2146893813
Windows Error Text: Key not valid for use in specified state.
Source File Name: cryptohelpercryptsameusersamemachine.cpp
Compiler Timestamp: Wed Jun 14 16:28:04 2006
Function Name: sqls::CryptSameUserSameMachine:rotectData
Source Line Number: 50
2148073483
Could not skip Component update due to datastore exception.
Source File Name: datastorecachedpropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:27:59 2006
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "InstallMediaPath" {"SetupBootstrapOptionsScope", "", "3324"} in cache
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:28:01 2006
Function Name: SetupBootstrapOptionsScope.InstallMediaPath
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupBootstrapOptionsScope"
Running: ValidateWinNTAction at: 2007/6/28 6:54:25
Complete: ValidateWinNTAction at: 2007/6/28 6:54:25, returned true
Running: ValidateMinOSAction at: 2007/6/28 6:54:25
Complete: ValidateMinOSAction at: 2007/6/28 6:54:25, returned true
Running: PerformSCCAction at: 2007/6/28 6:54:25
Complete: PerformSCCAction at: 2007/6/28 6:54:25, returned true
Running: ActivateLoggingAction at: 2007/6/28 6:54:25
Error: Action "ActivateLoggingAction" threw an exception during execution. Error information reported during run:
Datastore exception while trying to write logging properties.
Source File Name: datastorecachedpropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:27:59 2006
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "primaryLogFiles" {"SetupStateScope", "", ""} in cache
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:28:01 2006
Function Name: SetupStateScope.primaryLogFiles
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupStateScope"
00D5CFC0Unable to proceed with setup, there was a command line parsing error. : 2
Error Code: 0x80070002 (2)
Windows Error Text: The system cannot find the file specified.
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:28:01 2006
Function Name: SetupBootstrapOptionsScope.InstallMediaPath
Source Line Number: 44
Class not registered.
Failed to create CAB file due to datastore exception
Source File Name: datastorecachedpropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:27:59 2006
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "HostSetup" {"SetupBootstrapOptionsScope", "", "3324"} in cache
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:28:01 2006
Function Name: SetupBootstrapOptionsScope.HostSetup
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupBootstrapOptionsScope"
Message pump returning: 2
Hello,
I am unable to send a message to a target service on a different SQL Server instance. Using the SQL Profiler, I get the following error from the target machine:
Broker::Connection: Connection handshake failed: An OS call failed: (80090326) 0x80090326(The message received was unexpected or badly formatted.). State 106.
On the initiator side, the transmission_status shows the following error:
An error occurred while receiving data: '64(The specified network name is no longer available.)'.
Any ideas on why the target thinks the message is "unexpected or badly formatted"? Btw, I am specifying the default message type and contract for the services.
Thanks.
In Executing "E:EmailDelivery.exe" "EP12A 4" at "", The process exit code was "-532459699" while the expected was "0".
View 4 Replies View RelatedI am using snapshot replication to copy data from one database to another. I truncate the destination table first. The publisher and the subscriber are different databases on the same server. The data turns into 1 unrecognizable row.
Here is what the source table looks like:
displayTypeID, displayType
1, Title List Formats
2, Title Details
3, Title List Export
4, Pricing Notes
5, clone Mask 001
6, clone Mask 002
7, clone Mask 004
8, clone Mask 008
9, hide From Admin
10, not Common Attr
11, Insert Title
12, title Types
The resulting data looks like this:
DisplayType, displayTypeId
, 1660953600
I see no errors in replication and nothing in the source table looks like bad data that could cause such a malady. I see the problem on two different servers now and identified the source of the problem, the column order is reversed in the source and destination tables. The data types do not even match so I would at the very least expect an error from bcp.
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 RelatedI'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 RelatedI've just created a Maintenance Plan with Maintenance Plan Wizard, after I hit the Finish button and the SQL Server Management Studio start executing the wizard, it said something has conflict with the new maintenance wizard. Next thing I know, there's this DB Backup agent in SQL Agent Job (in SQL Server Management Studio); and I can't delete it although I'm able to disable it.
Can someone help? Here's the detail of the error message I received every time I tried to delete the job agent:
Drop failed for Job 'DB Backup'. (Microsoft.sqlServer.Smo)
Additional information:
- An exception occured while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
- The DELETE statement conflicted with the REFERENCE constraint
"FK_subplan_job_id". The conflict occurred in database "msdb" ,table
"dbo.sysmainplan_subplans", column "job_id".
The statement has been terminated. (Microsoft.SQL Server, error:547)
Thanks!
Replication Distribution Agent often dies with the following log entry. At that hour little is ever going on so I am surprised that the error occurs.
Failed Job -> JobName: Instance1-DB1-Instance2-33, StepName: Run agent., Message: Timeout expired. NOTE: The step was retried the requested number of times (10) without succeeding. The step failed..
Any ideas where to start?
Thanks
There is no SQL Agent forum so if this isn't the correct place please move this post.
Windows 2003 R2 x64 with SQL Server x64.
One of the steps in a SQL job I have setup requires me to run an exe. I can run this exe from the command line or by double-clicking it on this same server but when running it from a SQL job it does not run, the job just has the status 'executing' but does not do anything. I have enabled xp_cmdshell. I have also tried calling a bat file which then runs the exe and I have tried calling the bat file with SysWOW64cmd.exe. Same problem.
It seems to me the the operating system recognises the 32bit exe and runs it in that context but the SQL Agent thread keeps trying to run it as a 64bit exe and hence never gets anywhere. (My best guess)
Is there a way to force SQL job/steps to run an exe or bat file in a 32bit thread? Any other ideas.
Thanks
Scott
What does this code mean and what can I do to fix it? I need to update vista when applicable.
Thanks in advance for your help.
Iam trying to backup my database but nothing is backedup and no error message is displayed. Here is my code.
<%@ Page Language="VB" %>
<%@ Import Namespace="System.Data.SqlClient" %>
<%@ Import Namespace="System.Data" %>
<%@ Import Namespace="System.Net.Mail" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<script runat="server">
Protected Sub LinkButton1_Click(ByVal sender As Object, ByVal e As System.EventArgs)
Try
Dim con As SqlConnection
con = New SqlConnection("Data Source=.SQLEXPRESS;AttachDbFilename=|DataDirectory|safetydata.mdf;Integrated Security=True;User Instance=True")
Dim com As New SqlCommand("BACKUP DATABASE safetydata TO c:ackuptest")
com.Connection = con
com.Connection.Open()
com.ExecuteNonQuery()
com.Connection.Close()
Response.Redirect("DeveloperBackup_success.aspx")
Catch ex As Exception
Response.Redirect("~Developerackup_error.aspx")
End Try
End Sub
</script>
<html xmlns="http://www.w3.org/1999/xhtml" >
<head runat="server">
<title>BackUP Page</title>
Hi all,
View 1 Replies View RelatedI 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.
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
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
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.
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
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
hi all ,
i have larg table (images) and i want to replicate it to two locations by the merge replication . in the first location , i was appling the merge replication for 10 months without problems. but at last week ,aftre reinilizing the publication( after generating the snapshot successfully) , i stoped the synchronization for some problems in the network line and increased the minimum and the maximum retention periods .now , when i am going to start synchronizing i receive this message
:"the merge process could not perform retention-based meta data cleanup in database "
and the number of rows between tow locations for this table are different .
please help me quickly before to be the difference in number of rows is too large and i can't to stop the system for the long period.
note : i have other publications that is replicated by transactional replication.
Hi Guys,
I've got a merge replication set up between boxes. They're on separate sites both behind an ADSL Nat modem router. The publisher connects to the subscriber via a port forward / Nat translation at the router. This replication set up has been running for some months now. This morning I got this failure message from the merge agent on the publisher.
"the specified remote server name may not be the network name of the remote server or the remote server is unreachable due to network problems. The step failed"
Currently the Enterprise Mgr at the publisher can see the subscriber as can query analyzer running on the publisher.
The host name of the subscriber is the same name used in the server registration at the publisher. The registration uses a Client Network Utility alias to resolve the name.
If I run a ping command at the publisher using the subscribers name I get replies (the resolution of that name is done via a hosts file entry)
Both machines are Win2k Server boxes running SQL Server 2000 Standard.
Any ideas why the agent can't see the subscriber despite the fact its usual communications channel is working just fine?
I'm getting the error message below when trying to synchronise a sql compact database to a sql server 2005 db. Can anyone suggest a reason for this?
RDA works fine, permissions look ok. I've run process monitor and can see the IN/OUT files being created, no ACCESS DENIED messages etc. help!
New Subscription Wizard
- Beginning Synchronization (Success)
- Synchronizing Data (100%) (Error)
Messages
Initializing SQL Server Reconciler has failed. Try again.
HRESULT 0x80045901 (29045)
The merge process could not initialize the message file from Subscriber 'D:InetpubwwwrootSync30.59FA6BD9893A_9BFA53BB-1D7C-4E84-967A-799C6FEBFCE3.IN:D:InetpubwwwrootSync30.59FA6BD9893A_9BFA53BB-1D7C-4E84-967A-799C6FEBFCE3.OUT'.
HRESULT 0x80045901 (0)
The operation could not be completed.
- Finalizing Synchronization (Stopped)
- Saving Subscription Properties (Stopped)
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.
Unable to start log reader agent after being manually stopped.
Any ideas.
I have setup a replication and after 24 hours this are the error messages I have got:Last action; The database 'supersite' on server 'solomon' does not exist. Full error message: Could not locate entry in sysdatabases for database 'superiste'. No entry found with that name.Make sure that the name is entered correctly. Can anyone out there help me out?
View 1 Replies View RelatedI seem to have an orphaned Distribution Agent. There is no associated Publication and the agent is sending errors. The errors would be legitimate if only I had an associated publication. I also do not have an associated Snapshot Agent.
How can I get rid of this bogus agent? I already deleted the associated job and rebooted SQL and SQLAgent but it still persists.
Any help would be appreciated.
Colleen
What does this error message mean ?
The process could not bulk copy out of table '[dbo].[syncobj_0x3732313945323046]'.
I ran transaction replication successfully last night. Then it was scheduled to run again in the morning, but failed .... any ideas ?
SQL2K SP2
I have been seeing this issue for several weeks now. The distribution agent will become idle even though there is activity occurring within the replicated database. If I manually start the distribution agent, it will begin retrieving the transactions. I thought that this might be due to inactivity but I have modified the inactivity threshold and I am not receiving an actual inactive agent warning. There are no warnings -- it simply sits there and does not resume sending transactions.
Any thoughts? This is a transactional replication with a distribution agent that is run at the subscriber.
Thanks,
MV
Hi
We are repeatedly having the trouble of our publisher database becoming unresponsive during network problems.
We have publisher in carribean, distribution agent in canada and subscribers all over. The problem comes when publisher cant deliver to distributor due to network outages.
We are planning on moving the distributor to the carribean ultimately but that will take a while, and our application repeatedly needs to be restarted due to these freezes.
Does anyone know of this problem & possible ways to fix it in the short term (short of changing our replication topology).
is this a bug in replication?
ps.database is merge & transactional pubs. (some tables merge/some trans)
help much apprec,
des
Hi,For some magical reason, my database replication has suddenly stoppedworking. I modified the publication but the Distribution agent willnot run; the snapshot does not get applied to the subscriber, andchanges made at the publisher do not get replicated.My configuration is: Transactional Replication with a 'Pull'Subscription. The Subscriber is Updateable with Immediate UpdatesOnly. All created via the SQL Server Enterprise Manager. Both thePublisher and Subscriber are on the same server. I'm running SQLServer 2000 (8.00.760 SP3), on Windows 2000 Server (5.0 (2195)).I manually run the snapshop agent. It runs fine with the status'Succeeded' and the Last Action is 'A Snapshot of X article(s) wasgenerated'.When I look at the distribution agent, things start to get a bitconfusing in ( <SERVERNAME>/Replication Monitor/ Publishers/<SERVERNAME?>/ Publication/ Subscription), the status staysconstantly at 'Never Started'. All other columns are either blank or0. When I right click over the subscription, both Start Synchronisingand Stop Synchronising are NOT greyed out. If I click on either StartSynchronising or Stop Synchronising (absolutely) nothing happens(except the mouse turns 'busy' for a fraction of a second). There areno error messages.I added -output c:sqlout.txt -outputverboselevel 3 to thedistribution agent command. C:sqlout.txt did not get created.It worked fine up to a couple of days ago. I'm not sure exactly whatcaused the problem, as I made a few changes at the same time. Thechanges included: adding a new transactional publication, adding morearticles to an existing transaction publication, and adding a mergepublication. I've tried to go back to the set up before I made thechanges, even disabling replication and starting again from scratch.Still the problem persists.The owner of the distribution agent has dbo permissions in both thepublishing and subscribing database. Under 'Publisher and DistributorProperties' I've set the 'Replication Agent Connection to Publisher'and 'Agent Connection to the Subscriber' both to Use SQL ServerAuthentication, both with the same account that has dbo permissions inboth publishing and subscribing database.Has anybody come across this problem before? Can anybody make anysuggestions? Thanks in advance for your help.RegardsDamian HelmeIS ManagerINTEC Engineering (UK) Ltd.
View 1 Replies View RelatedWhy 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