All servers running SQL 2005
SQL server (NOLA) replicates to 35 remote locations (StoreXX).
Earlier this week, one publication started having problems connecting
to 30 of the 35 remote locations, with an error of:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Date 2/4/2010 10:00:01 AM
Log Job History (NOLA-Closing_Balance-CB Defaults to Stores-R99S-
Store1-2790)
Step ID 2
Server NOLA
Job Name NOLA-Closing_Balance-CB Defaults to Stores-R99S-Store1-2790
Step Name Run agent.
Duration 00:31:47
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
Message
2010-02-04 16:31:48.081 Parameter values obtained from agent profile:
-bcpbatchsize 2147473647
-commitbatchsize 100
-commitbatchthreshold 1000
-historyverboselevel 2
-keepalivemessageinterval 300
-logintimeout 15
-maxbcpthreads 1
-maxdeliveredtransactions 0
-pollinginterval 5000
-querytimeout 1800
-skiperrors
-transactionsperhistory 100
2010-02-04 16:31:48.081 Connecting to Subscriber 'R99S-Store1'
2010-02-04 16:31:48.440 Agent message code 20084. The process could
not connect to Subscriber 'R99S-Store1'.
2010-02-04 16:31:48.472 Category:NULL
Source: Microsoft SQL Native Client
Number: 10054
Message: TCP Provider: An existing connection was forcibly closed by
the remote host.
2010-02-04 16:31:48.472 Category:NULL
Source: Microsoft SQL Native Client
Number: 10054
Message: Communication link failure
2010-02-04 16:31:48.472 The agent failed with a 'Retry' status. Try to
run the agent at a later time.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The problem is only this one publication & not all subscriptions. I
have deleted a problem subscription & readded, same problem.
I have created another publication (same dB) & subscription (same &
new subscribers) with the same results (error above).
Now is where it gets weird…..
I created a new publication using a different dB on both the publisher
& subscriber & everything works fine.
I have had the network folks check what they need to check & have
googled until I am blue in the face.
Can anyone give me any insight into this issue.
AHIA,
Larry….
Related
I have a database running on an azure vm with sql server. The db is in full recovery mode. The backup is configured through the web interface. Database and log backups have been working flawlessly for years. But recently the log backup was interrupted halfway through and the log backup process somehow got stuck. The following event has been logged every 5 minutes since then (reading log with managed_backup.sp_get_backup_diagnostics):
[SSMBackup2WAAdminXevent] Database Name = DB, Database ID = 777, Stage =
VerifyJobOutcome, Error Code = 0, Error Message = Warning, Additional Info = A
progress update hasn't been received from SQL Server in more than 30 minutes
for log backup. SSMBackup2WA will continue to wait.
SSMBackup2WA seem to be stuck waiting for a progress update never being received. This has resulted in no log backups being taken. The database backup have continued running without problem.
I have trouble finding the job/task used by SSMBackup2WA. I understand its not in the usual batch of SQL Server Agent jobs but somehow hidden.
My idea is to somehow cancel the existing job that is stuck in waiting loop but I have not figured out how.
I have tried to "reset" the backup process by turning off the backup and then turning it on again but that did not help.
I have no possibility to restart the sql server (and I don't know if that would help).
So since no one seemed to have an answer to this one I resorted to restarting the SQL-server. And after the restart the transaction log backup started working again!
What is interesting is the following log that appeared in the application event log during the restart. It does seem like there was a thread hanging indefinitely, waiting for an status update that never arrived. The restart seems to have taken care of it by killing this status thread and not restarting it again in the erroneous state it had ended up in.
Log Name: Application
Source: Microsoft SQL Server Automated Backup
Date: 1/15/2022 11:16:20 AM
Event ID: 57007
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: wn-sqlserver1
Description:
[Warning] AutomatedBackupStatusMonitorError:
System.Exception:
Error in auto-backup status monitor thread --->
Microsoft.SqlServer.Management.IaaSAgentSqlQuery.Contract.IaaSAgentSqlQueryException:
A network-related or instance-specific error occurred while
establishing a connection to SQL Server. The server was not
found or was not accessible. Verify that the instance name
is correct and that SQL Server is configured to allow remote
connections. (provider: Named Pipes Provider, error: 40 - Could
not open a connection to SQL Server) --->
I am an Administrator for a company, we have multiple servers on premises,
1 is a Database Server (DATABASESERVER) running Windows Server 2008 R2 and SQL 2008 and IIS 7
1 is a Application Server (APPSERVER) running Windows Server 2008 R2
We have a company who owns and manages our CRM System installed across all 2 of these servers, DATABASESERVER contains the Database, the HTTPSERVER contains the Internal Web CRM for the staff to use, and the APPSERVER manages the print/sms/emails/timed executions etc through the 3rd party company's applications.
The 3rd Party Company's applications keep crashing on the APPSERVER and they are blaming this on the loss of connection to the DATABASESERVER which is what an error their system is producing is saying in the logs, however the staff do not have any issues with the Website which uses the same Database.
The error message they have provided for me to fix this is at the bottom, and they are fixating on this bit of the error.
[[DBNETLIB][ConnectionWrite (WrapperWrite()).]General network error. Check your network documentation.])
but it is my understanding that with the above section of the error there should be a SQLSTATE code?
Any help on this error would be greatly appreciated.
The VB Application identified by the event source logged this Application zXTmdExec: Thread ID: 12408 ,Logged: Timed execution: zX.clsDSHPrimary.iDSHandler_sqlRS: Unable to execute query (SELECT TOP 1 [zxPrcssMntr].[stts] AS [zxPrcssMntr_stts], [zxPrcssMntr].[autoPse] AS [zxPrcssMntr_autoPse], [zxPrcssMntr].[autoRsme] AS [zxPrcssMntr_autoRsme], [zxPrcssMntr].[lstStrtd] AS [zxPrcssMntr_lstStrtd], [zxPrcssMntr].[prcssCntrlId] AS [zxPrcssMntr_prcssCntrlId] FROM [zxPrcssMntr] WHERE (1 = 1) AND ([zxPrcssMntr].[id] = 'timedExecGeneral') [[DBNETLIB][ConnectionWrite (WrapperWrite()).]General network error. Check your network documentation.])
zX.clsDSHPrimary.iDSHandler_loadBO: Unable to execute load query (SELECT [zxPrcssMntr].[stts] AS [zxPrcssMntr_stts], [zxPrcssMntr].[autoPse] AS [zxPrcssMntr_autoPse], [zxPrcssMntr].[autoRsme] AS [zxPrcssMntr_autoRsme], [zxPrcssMntr].[lstStrtd] AS [zxPrcssMntr_lstStrtd], [zxPrcssMntr].[prcssCntrlId] AS [zxPrcssMntr_prcssCntrlId] FROM [zxPrcssMntr] WHERE (1 = 1) AND ([zxPrcssMntr].[id] = 'timedExecGeneral'))
zx.clsBOS.loadBO: Error during loadBO for data source (primary)
zxMisc.clsPrcssMntr.nextCycle: Unable to reload when cycling in prcssMntr
zX.clsDSHPrimary.iDSHandler_rollbackTx: Untrapped error (Connection failure)
zXTmdExec.modMain.goGoGo: Severe process monitor error
zX.clsDSHPrimary.iDSHandler_sqlExecute: Unable to execute query (DELETE FROM [zxSssn] WHERE (1 = 1) AND ([zxSssn].[id] = 79495)[[DBNETLIB][ConnectionWrite (WrapperWrite()).]General network error. Check your network documentation.])
zX.clsDSHPrimary.iDSHandler_deleteBO: Unable to delete BO
zx.clsBOS.deleteBO: Delete by data-source handler failed (primary)
zx.clsSession.disConnect: Unable to delete session
I'm trying to execute ssis package in sql server agent job . while start the job am facing the sql job fail. below i attached the screenshot of the error.
NOTE : it is running fine , if i execute ssis package.
Please find the below screenshot for more inforamtion.
the step -1 details
Date 3/23/2016 1:39:39 PM
Log Job History (cbr_report)
Step ID 1
Server CRM\CRMSERVER
Job Name cbr_report
Step Name execute
Duration 00:00:01
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
Message
Executed as user: CRM\SYSTEM. The package execution failed. The step failed.
Have two multiple geographically distributed SQL Server Databases with transactional replication.SQL Server agent sync two servers every 1 minute.After working for 10 minutes on server B (subscriber),it has an error, which lasts 10-15 minutes and corrected herself. Then again it working 10 minute and has an error. On server A (publication) I have log backup schedule it runs every 10 minutes. Maybe there is conflict between two jobs ?
SQLServerAgent Error: Request to run job XXX (from User sa)
refused because the job is already running from a request by Schedule 14 (Replication agent schedule.).
Changed database context to 'XXX'. (.Net SqlClient Data Provider)
How to fix it ?
We ran out of space on our Production Server and during this time we started getting: "Cannot execute 'sp_replcmds' on " on Replication. The Distributor is the Publisher as well.
After fixing the space issue - this is the only error I'm getting on my Replication
We have five databases set-up for Replication. The four small databases work with no error messages except that the Last Synchronization Status says the following: "The process could not connect to Distributor "
The one large database gets the error in the subject and also that it cannot connect to the Distributor . The Error Code is: MSSQL_REPL22037
I checked the DBOwner and it is set up correctly. I stopped and started the Log Reader Agents too many times to count. I restarted the MSSQLServer Agent Processes on the Subscriber Server as well.
I solved this one myself. After all the other suggestions
It was definitely the BatchSize and the QueryTimeOut properties.
In order to change this:
Launch Replication Monitor.
Expand to the Publication in question.
Go to Agents Tab.
Right Click on Log Reader Agent > Agent Profile.
Create a New Agent Profile with the new parameters you need.
Set the New Profile to 'Use for this Agent'
Restart the Log Reader Agent and just wait.
Rinse/Repeat until you get the right amount.
I set the Timeout to 2400 and the BatchSize to 100 from 1800 and 500 respectively.