Skip to main content

36115_carloscor

217 Posts

December 6th, 2011 05:00

Hi Agracci,

this could be permission related issue.

What is the user account starting up the SQL Instance service?

Microsoft recommends that the two SQL Server Services (MS SQL Server and SQL Agent) be logged in using either the local system account \ a domain account that has the necessary rights to run SQL Services per the following MS article:  http://msdn.microsoft.com/en-us/library/aa176610.aspx

Once the changes are made, a restart of the SQL Server \ services is required.

Also you could try to start the Microsoft SQL System with the Domain Administrator account.

Is this a cluster SQL? If so please check the following information:

Using a domain account that is a local administrator to each physical node of the cluster will ensure that it has all necessary privileges to initialize VDI, to have sysadmin role in SQL and Cluster administrator role.

In addition, add one of the following to the Networker Administrator's Usergroup

user=accountname

OR 

host=node1

host=node2

where,

accountname is the domain account

node1 , node2 are the hostnames of the physical nodes of MSCS Cluster.

Thank you.

Carlos.

agracci

34 Posts

December 7th, 2011 08:00

Hi Carlos,

I put the user in the permissions with this system still can not make the sql backup via online
Take the logs directory C: \ Program Files \ Legato \ nsr \ applogs

The following log attached. But could help me with guidance on this?

thank you

Part 1:

43621 12/7/2011 11:44:43 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Computer Name: SAOWS1905     User Name: SYSTEM

52702 12/7/2011 11:44:43 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) System Version: 6.1 Build 7600 

37975 12/7/2011 11:44:43 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Microsoft Data Access Component(MDAC) version: 6.1.7600.16385

29446 12/7/2011 11:44:43 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Local host has following SQL Server online: 

37977 12/7/2011 11:44:43 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208)   MSSQL server : SAOWS1905\MSSQLSERVER2010

37982 12/7/2011 11:48:13 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Use Legato Networker Server :  saobs1902

37983 12/7/2011 11:48:13 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Legato Networker Server Version: NetWorker 7.6.1.Build.397 Network Edition/85

73064 12/7/2011 11:48:13 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Version information for C:\Program Files\Legato\nsr\bin\nsrexecd.exe:\n Original file name: nsrexecd.exe\n Version: 7.6.Build.142\n Comments: 

73064 12/7/2011 11:48:13 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Version information for C:\Program Files\Legato\nsr\bin\nsrsqlsv.exe:\n Original file name: nsrsqlsv.exe\n Version: 5.2.2.23\n Comments: Supporting SQL 2000, SQL 2005, SQL 2008 and SQL 2008 R2

43337 12/7/2011 11:48:13 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Command line:

43338 12/7/2011 11:48:13 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208)   C:\Program Files\Legato\nsr\bin\nsrsqlsv.exe -f aes -s 10.20.136.40 -g Re-schedule -E -LL -f - -m saows1905 -b DCN -l full -W 78 -N MSSQL: MSSQL: 

37693 12/7/2011 11:48:14 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) SQL Connection to SAOWS1905 is created. SQL Server Version is 10.00.4064

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up Application_Registry_Service_DB_44d9b1bb14d642d393edc027e3a8c4b8...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing Application_Registry_Service_DB_44d9b1bb14d642d393edc027e3a8c4b8 failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up BRDCPMT_Projetos...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing BRDCPMT_Projetos failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up BRDCPipeline_Projetos...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing BRDCPipeline_Projetos failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up Bdc_Service_DB_db91a8896fa0427d85c467d578907d35...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing Bdc_Service_DB_db91a8896fa0427d85c467d578907d35 failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up Managed Metadata Service_7d2413d728b546efa624f17646fc0b93...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing Managed Metadata Service_7d2413d728b546efa624f17646fc0b93 failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up PerformancePoint Service Application_9357e8c80f6a45b988b97f9ff98cec25...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing PerformancePoint Service Application_9357e8c80f6a45b988b97f9ff98cec25 failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up ReportServer$MSSQLSERVER2010...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing ReportServer$MSSQLSERVER2010 failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up ReportServer$MSSQLSERVER2010TempDB...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing ReportServer$MSSQLSERVER2010TempDB failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up Search_Service_Application_CrawlStoreDB_d254382339c54230a8e0d82679d8914e...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing Search_Service_Application_CrawlStoreDB_d254382339c54230a8e0d82679d8914e failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up Search_Service_Application_DB_b1274081320e470781c58169638aa804...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing Search_Service_Application_DB_b1274081320e470781c58169638aa804 failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up Search_Service_Application_PropertyStoreDB_e0c9450d5719428ea898048e7225480a...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing Search_Service_Application_PropertyStoreDB_e0c9450d5719428ea898048e7225480a failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up Secure_Store_Service_DB_333ff5862cb44f5496f66d6733048c27...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing Secure_Store_Service_DB_333ff5862cb44f5496f66d6733048c27 failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up SharePoint_AdminContent_9d65222a-e15f-41ef-b245-cf1a23ce6dfa...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing SharePoint_AdminContent_9d65222a-e15f-41ef-b245-cf1a23ce6dfa failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up SharePoint_Config...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing SharePoint_Config failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up StateService_d4dfd126da70496d99061d4a6b22c80e...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing StateService_d4dfd126da70496d99061d4a6b22c80e failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up User Profile Service Application_ProfileDB_fde32a9302b24fb5bd33c36b3804f6d4...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing User Profile Service Application_ProfileDB_fde32a9302b24fb5bd33c36b3804f6d4 failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up User Profile Service Application_SocialDB_1de88c06e731412a84f8d9f6c81afdb0...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing User Profile Service Application_SocialDB_1de88c06e731412a84f8d9f6c81afdb0 failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up User Profile Service Application_SyncDB_bfde47d938cf486ab3f86ee5bbf6b2ef...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing User Profile Service Application_SyncDB_bfde47d938cf486ab3f86ee5bbf6b2ef failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up WSS_Content...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing WSS_Content failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up WSS_Content_Acesso_Anonimo...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing WSS_Content_Acesso_Anonimo failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up WSS_Content_KBClusterFinancial...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing WSS_Content_KBClusterFinancial failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up WSS_Content_S10_Avanade...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing WSS_Content_S10_Avanade failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up WSS_Content_S10_Avanade_RH...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing WSS_Content_S10_Avanade_RH failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up WSS_Content_S11_Avanade_CP...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing WSS_Content_S11_Avanade_CP failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up WSS_Content_S1_ItauM2...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing WSS_Content_S1_ItauM2 failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up WSS_Content_S2_SKY...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing WSS_Content_S2_SKY failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up WSS_Content_S3_InteligDC...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing WSS_Content_S3_InteligDC failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up WSS_Content_S4_IG...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing WSS_Content_S4_IG failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up WSS_Content_S5_CTSS...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing WSS_Content_S5_CTSS failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up WSS_Content_S6_IG...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing WSS_Content_S6_IG failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up WSS_Content_S7_Sap_Projects...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing WSS_Content_S7_Sap_Projects failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up WSS_Content_S8_BI_HPD...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing WSS_Content_S8_BI_HPD failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up WSS_Content_S9_Anglo_Suporte_Pos_Go_Live...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing WSS_Content_S9_Anglo_Suporte_Pos_Go_Live failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up WSS_Content_Tools...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing WSS_Content_Tools failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up WSS_Logging...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing WSS_Logging failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up WebAnalyticsServiceApplication_ReportingDB_93b6b755-8ea0-4180-8bd6-299aab7c6ee4...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing WebAnalyticsServiceApplication_ReportingDB_93b6b755-8ea0-4180-8bd6-299aab7c6ee4 failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up WebAnalyticsServiceApplication_StagingDB_5908f1e8-91c3-4584-9c76-36b921a658f6...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing WebAnalyticsServiceApplication_StagingDB_5908f1e8-91c3-4584-9c76-36b921a658f6 failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up WordAutomationServices_f897ad3db3bf478abe078072007b33a7...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing WordAutomationServices_f897ad3db3bf478abe078072007b33a7 failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up master...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing master failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up model...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing model failed, the item will be skipped.

37994 12/7/2011 11:56:44 AM  1 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Backing up msdb...

37827 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Can't configure VDI set (failed to recognize the SQL Server instance name).

37829 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) bsVdiAbort: SignalAbort failed: protocol error.

53084 12/7/2011 11:56:44 AM  5 0 0 3784 3208 0 saows1905.dir.svc.accenture.com (pid3208) Processing msdb failed, the item will be skipped.

52769 12/7/2011 12:00:57 PM  1 0 0 3040 3208 0 saows1905.dir.svc.accenture.com (pid3208) sigHandler received signal: 9

Unable to render the following message: 43709 1323266457 1 0 0 3040 3208 0 saows1905.dir.svc.accenture.com (pid3208) 13 Stop time: %s 1 35 25 Wed Dec 07 12:00:57 201

Part 2:

43621 12/7/2011 1:35:10 PM  1 0 0 3436 1288 0 saows1905.dir.svc.accenture.com (pid1288) Computer Name: SAOWS1905     User Name: SYSTEM
52702 12/7/2011 1:35:10 PM  1 0 0 3436 1288 0 saows1905.dir.svc.accenture.com (pid1288) System Version: 6.1 Build 7600 
37975 12/7/2011 1:35:10 PM  1 0 0 3436 1288 0 saows1905.dir.svc.accenture.com (pid1288) Microsoft Data Access Component(MDAC) version: 6.1.7600.16385
29446 12/7/2011 1:35:10 PM  1 0 0 3436 1288 0 saows1905.dir.svc.accenture.com (pid1288) Local host has following SQL Server online: 
37977 12/7/2011 1:35:10 PM  1 0 0 3436 1288 0 saows1905.dir.svc.accenture.com (pid1288)   MSSQL server : SAOWS1905\MSSQLSERVER2010
37982 12/7/2011 1:38:40 PM  1 0 0 3436 1288 0 saows1905.dir.svc.accenture.com (pid1288) Use Legato Networker Server :  saobs1902
37983 12/7/2011 1:38:40 PM  1 0 0 3436 1288 0 saows1905.dir.svc.accenture.com (pid1288) Legato Networker Server Version: NetWorker 7.6.1.Build.397 Network Edition/85
73064 12/7/2011 1:38:40 PM  1 0 0 3436 1288 0 saows1905.dir.svc.accenture.com (pid1288) Version information for C:\Program Files\Legato\nsr\bin\nsrexecd.exe:\n Original file name: nsrexecd.exe\n Version: 7.6.Build.142\n Comments: 
73064 12/7/2011 1:38:40 PM  1 0 0 3436 1288 0 saows1905.dir.svc.accenture.com (pid1288) Version information for C:\Program Files\Legato\nsr\bin\nsrsqlsv.exe:\n Original file name: nsrsqlsv.exe\n Version: 5.2.2.23\n Comments: Supporting SQL 2000, SQL 2005, SQL 2008 and SQL 2008 R2
43337 12/7/2011 1:38:40 PM  1 0 0 3436 1288 0 saows1905.dir.svc.accenture.com (pid1288) Command line:
43338 12/7/2011 1:38:40 PM  1 0 0 3436 1288 0 saows1905.dir.svc.accenture.com (pid1288)   C:\Program Files\Legato\nsr\bin\nsrsqlsv.exe -f aes -s 10.20.136.40 -g Re-schedule -E -LL -f - -m saows1905 -b DCN -l full -W 78 -N MSSQL: MSSQL: 
37693 12/7/2011 1:38:40 PM  1 0 0 3436 1288 0 saows1905.dir.svc.accenture.com (pid1288) SQL Connection to SAOWS1905 is created. SQL Server Version is 10.00.4064
52769 12/7/2011 1:45:10 PM  1 0 0 1460 1288 0 saows1905.dir.svc.accenture.com (pid1288) sigHandler received signal: 9
Unable to render the following message: 43709 1323272710 1 0 0 1460 1288 0 saows1905.dir.svc.accenture.com (pid1288) 13 Stop time: %s 1 35 25 Wed Dec 07 13:45:10 2011

Unable to render the following message: 43709 1323272710 1 0 0 1460 1288 0 saows1905.dir.svc.accenture.com (pid1288) 13 Stop time: %s 1 35 25 Wed Dec 07 13:45:10 2011

Was this post helpful?

View All

No Events found!

Top