Не работает репликация БД - System.Data.SqlClient.SqlException (0x80131904): Timeout expired

Ответить
Юрий
Завсегдатай
Сообщения: 26
Зарегистрирован: 14 сен 2016 05:05

Не работает репликация БД - System.Data.SqlClient.SqlException (0x80131904): Timeout expired

Сообщение Юрий » 05 дек 2016 11:22

Здраствуйте перестала работать репликация баз данных между сервером sccmCAS и sccmPS1 из за этого я не могу установить службу отчетов.Изображение

Возникло необработанное исключение - System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out
a.

Дополнительные сведения см. в файле журнала rcmctrl.log.




rcmctrl.log.
There are 8 Drs Activations sprocs running. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:00:01.911-120><thread=3932 (0xF5C)>
InvokeRcmConfigure thread wait one more minute for incoming event... $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:00:24.472-120><thread=3936 (0xF60)>
Wait for inbox notification timed out. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:00:24.473-120><thread=3888 (0xF30)>
Cleaning the RCM inbox if there are any *.RCM files for further change notifications.... $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:00:24.473-120><thread=3888 (0xF30)>
Initializing RCM. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:00:24.474-120><thread=3888 (0xF30)>
Processing Replication Monitor $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:00:24.498-120><thread=3940 (0xF64)>
Processing Replication Configure $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:00:24.499-120><thread=3936 (0xF60)>
Summarizing all replication links for monitoring UI. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:00:24.546-120><thread=3940 (0xF64)>
The current site status: ReplicationActive. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:00:24.856-120><thread=3940 (0xF64)>
Running configuration ConfigureNonUpdateableTriggersForSiteTables. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:00:24.890-120><thread=3936 (0xF60)>
Rcm control is waiting for file change notification or timeout after 60 seconds. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:00:25.540-120><thread=3888 (0xF30)>
Processing Replication success. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:00:26.284-120><thread=3940 (0xF64)>
Cleaning the RCM inbox if there are any *.RCM files for further change notifications.... $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:00:26.285-120><thread=3888 (0xF30)>
Rcm control is waiting for file change notification or timeout after 60 seconds. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:00:26.286-120><thread=3888 (0xF30)>
DRS sync started. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:00:35.204-120><thread=3928 (0xF58)>
Error: Received unhandled SQL exception, printing info and throwing it again. This will be retried in next cycle. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:00:54.911-120><thread=3936 (0xF60)>
Error: Exception message: [Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.] $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:00:54.912-120><thread=3936 (0xF60)>
STATMSG: ID=7832 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_REPLICATION_CONFIGURATION_MONITOR" SYS=vSCCM-CAS.kbu.net SITE=CAS PID=2100 TID=3936 GMTDATE=Mon Dec 05 11:00:54.913 2016 ISTR0="System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out~~ at" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:00:54.919-120><thread=3936 (0xF60)>
Processing Replication failed. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:00:54.922-120><thread=3936 (0xF60)>
Cleaning the RCM inbox if there are any *.RCM files for further change notifications.... $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:00:54.923-120><thread=3888 (0xF30)>
Rcm control is waiting for file change notification or timeout after 60 seconds. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:00:54.924-120><thread=3888 (0xF30)>
DRS change application started. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:01:01.912-120><thread=3932 (0xF5C)>
Launching 4 sprocs on queue ConfigMgrDRSQueue and 4 sprocs on queue ConfigMgrDRSSiteQueue. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:01:01.969-120><thread=3932 (0xF5C)>
There are 8 Drs Activations sprocs running. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:01:02.011-120><thread=3932 (0xF5C)>
InvokeRcmMonitor thread wait one more minute for incoming event... $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:01:26.286-120><thread=3940 (0xF64)>
DRS sync started. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:01:35.322-120><thread=3928 (0xF58)>
InvokeRcmConfigure thread wait one more minute for incoming event... $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:01:54.924-120><thread=3936 (0xF60)>
Wait for inbox notification timed out. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:01:54.925-120><thread=3888 (0xF30)>
Cleaning the RCM inbox if there are any *.RCM files for further change notifications.... $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:01:54.925-120><thread=3888 (0xF30)>
Initializing RCM. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:01:54.926-120><thread=3888 (0xF30)>
Processing Replication Configure $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:01:54.938-120><thread=3936 (0xF60)>
Processing Replication Monitor $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:01:54.938-120><thread=3940 (0xF64)>
Summarizing all replication links for monitoring UI. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:01:54.997-120><thread=3940 (0xF64)>
The current site status: ReplicationActive. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:01:55.273-120><thread=3940 (0xF64)>
Running configuration ConfigureNonUpdateableTriggersForSiteTables. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:01:55.373-120><thread=3936 (0xF60)>
Rcm control is waiting for file change notification or timeout after 60 seconds. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:01:56.010-120><thread=3888 (0xF30)>
Processing Replication success. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:01:56.322-120><thread=3940 (0xF64)>
Cleaning the RCM inbox if there are any *.RCM files for further change notifications.... $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:01:56.323-120><thread=3888 (0xF30)>
Rcm control is waiting for file change notification or timeout after 60 seconds. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:01:56.323-120><thread=3888 (0xF30)>
DRS change application started. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:02:02.013-120><thread=3932 (0xF5C)>
Launching 4 sprocs on queue ConfigMgrDRSQueue and 4 sprocs on queue ConfigMgrDRSSiteQueue. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:02:02.071-120><thread=3932 (0xF5C)>
There are 8 Drs Activations sprocs running. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:02:02.114-120><thread=3932 (0xF5C)>
Error: Received unhandled SQL exception, printing info and throwing it again. This will be retried in next cycle. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:02:25.398-120><thread=3936 (0xF60)>
Error: Exception message: [Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.] $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:02:25.399-120><thread=3936 (0xF60)>
STATMSG: ID=7832 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_REPLICATION_CONFIGURATION_MONITOR" SYS=vSCCM-CAS.kbu.net SITE=CAS PID=2100 TID=3936 GMTDATE=Mon Dec 05 11:02:25.400 2016 ISTR0="System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out~~ at" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:02:25.416-120><thread=3936 (0xF60)>
Processing Replication failed. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:02:25.419-120><thread=3936 (0xF60)>
Cleaning the RCM inbox if there are any *.RCM files for further change notifications.... $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:02:25.420-120><thread=3888 (0xF30)>
Rcm control is waiting for file change notification or timeout after 60 seconds. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:02:25.420-120><thread=3888 (0xF30)>
DRS sync started. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:02:35.670-120><thread=3928 (0xF58)>
InvokeRcmMonitor thread wait one more minute for incoming event... $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:02:56.322-120><thread=3940 (0xF64)>
DRS change application started. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:03:02.115-120><thread=3932 (0xF5C)>
Launching 4 sprocs on queue ConfigMgrDRSQueue and 4 sprocs on queue ConfigMgrDRSSiteQueue. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:03:02.125-120><thread=3932 (0xF5C)>
The asynchronous command finished with return message: [spDRSActivation finished at 12/5/2016 1:02:15 PM. End execute query finished at 12/5/2016 1:02:15 PM.]. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:03:02.128-120><thread=3932 (0xF5C)>
The asynchronous command finished with return message: [spDRSActivation finished at 12/5/2016 1:02:11 PM. End execute query finished at 12/5/2016 1:02:11 PM.]. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:03:02.129-120><thread=3932 (0xF5C)>
The asynchronous command finished with return message: [spDRSActivation finished at 12/5/2016 1:02:10 PM. End execute query finished at 12/5/2016 1:02:10 PM.]. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:03:02.129-120><thread=3932 (0xF5C)>
The asynchronous command finished with return message: [spDRSActivation finished at 12/5/2016 1:02:10 PM. End execute query finished at 12/5/2016 1:02:10 PM.]. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:03:02.130-120><thread=3932 (0xF5C)>
The asynchronous command finished with return message: [spDRSActivation finished at 12/5/2016 1:02:15 PM. End execute query finished at 12/5/2016 1:02:15 PM.]. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:03:02.140-120><thread=3932 (0xF5C)>
The asynchronous command finished with return message: [spDRSActivation finished at 12/5/2016 1:02:10 PM. End execute query finished at 12/5/2016 1:02:10 PM.]. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:03:02.141-120><thread=3932 (0xF5C)>
The asynchronous command finished with return message: [spDRSActivation finished at 12/5/2016 1:02:11 PM. End execute query finished at 12/5/2016 1:02:11 PM.]. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:03:02.142-120><thread=3932 (0xF5C)>
The asynchronous command finished with return message: [spDRSActivation finished at 12/5/2016 1:02:10 PM. End execute query finished at 12/5/2016 1:02:10 PM.]. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:03:02.144-120><thread=3932 (0xF5C)>
There are 8 Drs Activations sprocs running. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><12-05-2016 13:03:02.145-120><thread=3932 (0xF5C)>


Изображение

Аватара пользователя
Алексей Максимов
Администратор сайта
Сообщения: 419
Зарегистрирован: 14 сен 2012 06:50
Откуда: г.Сыктывкар
Контактная информация:

Re: Репликация базы данных

Сообщение Алексей Максимов » 05 дек 2016 12:09

Error: Received unhandled SQL exception, printing info and throwing it again. This will be retried in next cycle.
Error: Exception message: [Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.]
STATMSG: ID=7832 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_REPLICATION_CONFIGURATION_MONITOR" SYS=vSCCM-CAS.kbu.net SITE=CAS PID=2100 TID=3936 GMTDATE=Mon Dec 05 11:00:54.913 2016 ISTR0="System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out~~ at" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SQL-клиент не может выполнить операцию на SQL-сервере. Проверять адекватность SQL-сервера.

Юрий
Завсегдатай
Сообщения: 26
Зарегистрирован: 14 сен 2016 05:05

Re: Репликация базы данных

Сообщение Юрий » 05 дек 2016 12:13

а можно поконкретней сказать что делать, так как я в SQL новичек грубо говоря(((

Аватара пользователя
Алексей Максимов
Администратор сайта
Сообщения: 419
Зарегистрирован: 14 сен 2012 06:50
Откуда: г.Сыктывкар
Контактная информация:

Re: Репликация базы данных

Сообщение Алексей Максимов » 05 дек 2016 12:14

Можно попрбовать включить расширенное логирование rcmctrl.log, replmgr.log, как описано здесь:
Tips for troubleshooting SC 2012 Configuration Manager Data Replication Service (DRS)
Возможно из расширенного лога станет понятней в чём именно проблема

Юрий
Завсегдатай
Сообщения: 26
Зарегистрирован: 14 сен 2016 05:05

Re: Репликация базы данных

Сообщение Юрий » 05 дек 2016 12:41

Алексей Максимов писал(а):Можно попрбовать включить расширенное логирование rcmctrl.log, replmgr.log, как описано здесь:
Tips for troubleshooting SC 2012 Configuration Manager Data Replication Service (DRS)
Возможно из расширенного лога станет понятней в чём именно проблема
Поменял значение в реестре на 2. просматриваю rcmctrl.log пока что не вижу чего то нового.

Аватара пользователя
Алексей Максимов
Администратор сайта
Сообщения: 419
Зарегистрирован: 14 сен 2012 06:50
Откуда: г.Сыктывкар
Контактная информация:

Re: Не работает репликация БД - System.Data.SqlClient.SqlException (0x80131904): Timeout expired

Сообщение Алексей Максимов » 05 дек 2016 17:19

Ну могу ещё посоветовать поработать по другим статьям с рекомендациями по решению проблем.
Вот хорошая обширная статья:
ConfigMgr 2012 DRS – Troubleshooting FAQs
Также, возможно, окажется полезной книжка:
Microsoft System Center - Troubleshooting Configuration Manager

Ответить

Вернуться в «System Center Configuration Manager»