none
SQL Server network name indisponivel após failover RRS feed

  • Pergunta

  • Boa tarde Galera,

    Trago uma questão que está ocorrendo em um de meus ambientes com FCI (WSFC), quando os serviços estão rodando no node02 tudo fica disponível, mas se ocorre um failover para o node01 o recurso "Server Name" que é o serviço pelo qual atende na rede as requisições de conexão fica indisponível (nenhuma conexão é aceita mais, retorna mensagem de erro como na imagem abaixo).

    Até o momento percebi que isso acontece sempre com failover automático, amanhã irei testar se acontece tbm quando faço failover manual. Nesse meio tempo se alguem tiver alguma sugestão do que pode ser o problema, agradeço desde já.

    Obs: executei várias vezes o "validate cluster" e está tudo ok.

    Atenciosamente,

    quinta-feira, 21 de setembro de 2017 17:46

Respostas

  • Rogério,

    veja se o problema se enquadra em algum dos tópicos desse link:

    https://docs.microsoft.com/en-us/sql/sql-server/failover-clusters/windows/failover-cluster-troubleshooting


    Vinicius Fonseca - MCP | MCTS | MCDBA | MCITP | MCTS | MCT | ITIL Foundation - DGA SISTEMAS - Se minha resposta for útil, classifique-a. :)

    sexta-feira, 29 de setembro de 2017 18:47

Todas as Respostas

  • Olá,

    tentou conectar pelo VIP (IP virtual do cluster) para ver se também ocorre o erro?

    Abs


    Vinicius Fonseca - MCP | MCTS | MCDBA | MCITP | MCTS | MCT | ITIL Foundation - DGA SISTEMAS - Se minha resposta for útil, classifique-a. :)

    sábado, 23 de setembro de 2017 11:28
  • Rogério,

    Com esta a configuração das placas de rede em cada Nó?

    Você esta forçando o failover manual ou realmente esta ocorrendo?

    No Windows Server Cluster como o Nó1 esta sendo apresentado no momento do Failover?


    Pedro Antonio Galvao Junior [MVP | MCC | MSTC | MIE | Microsoft Evangelist | Microsoft Partner | Engenheiro de Softwares | Especialista em Banco de Dados | Professor Universitário | @JuniorGalvaoMVP | http://pedrogalvaojunior.wordpress.com]

    quinta-feira, 28 de setembro de 2017 00:18
    Moderador
  • O erro reportado ocorreu com um failover automático, quando faço manualmente não acontece. Já testei várias vezes fazendo manualmente, mas não da o erro. estou aguardando acontecer novamente para poder investigar melhor. Por enquanto segue algumas imagens do ambiente. 

    Outra informação que pode ser relevante, quando aconteceu o problema o ip (10.1.83.21) não atendia, deium ping no ip e tbm pelo nome que ele atende no DNS (celsqldb03) e não pingava. Se ajudar vou postar tbm o log do dia do problema.

    sexta-feira, 29 de setembro de 2017 18:16
  • Segue log do SQLServer quando houve o failover automático para o node01, até o horário em que fiz o failover manual para o node02.

    2017-08-23 07:12:08.34 Server      Microsoft SQL Server 2016 (SP1) (KB3182545) - 13.0.4001.0 (X64) 
    Oct 28 2016 18:17:30 
    Copyright (c) Microsoft Corporation
    Standard Edition (64-bit) on Windows Server 2016 Datacenter 6.3 <X64> (Build 14393: ) (Hypervisor)

    2017-08-23 07:12:08.36 Server      UTC adjustment: -3:00
    2017-08-23 07:12:08.36 Server      (c) Microsoft Corporation.
    2017-08-23 07:12:08.36 Server      All rights reserved.
    2017-08-23 07:12:08.36 Server      Server process ID is 388.
    2017-08-23 07:12:08.36 Server      System Manufacturer: 'VMware, Inc.', System Model: 'VMware Virtual Platform'.
    2017-08-23 07:12:08.36 Server      Authentication mode is MIXED.
    2017-08-23 07:12:08.36 Server      Logging SQL Server messages in file 'F:\MSSQL13.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
    2017-08-23 07:12:08.36 Server      The service account is 'XXXXXXXX\svc.sqlwss'. This is an informational message; no user action is required.
    2017-08-23 07:12:08.36 Server      Registry startup parameters: 
    -d F:\MSSQL13.MSSQLSERVER\MSSQL\DATA\master.mdf
    -e F:\MSSQL13.MSSQLSERVER\MSSQL\Log\ERRORLOG
    -l F:\MSSQL13.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
    2017-08-23 07:12:08.36 Server      Command Line Startup Parameters:
    -s "MSSQLSERVER"
    2017-08-23 07:12:08.41 Server      SQL Server detected 6 sockets with 1 cores per socket and 1 logical processors per socket, 6 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
    2017-08-23 07:12:08.41 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2017-08-23 07:12:08.41 Server      Detected 16383 MB of RAM. This is an informational message; no user action is required.
    2017-08-23 07:12:08.41 Server      Using conventional memory in the memory manager.
    2017-08-23 07:12:08.99 Server      Default collation: Latin1_General_CI_AS (us_english 1033)
    2017-08-23 07:12:09.77 Server      Buffer pool extension is already disabled. No action is necessary. 
    2017-08-23 07:12:10.55 Server      InitializeExternalUserGroupSid failed. Implied authentication will be disabled.
    2017-08-23 07:12:10.55 Server      Implied authentication manager initialization failed. Implied authentication will be disabled.
    2017-08-23 07:12:10.88 Server      The maximum number of dedicated administrator connections for this instance is '1'
    2017-08-23 07:12:10.89 Server      This instance of SQL Server last reported using a process ID of 29836 at 23/08/2017 07:11:26 (local) 23/08/2017 10:11:26 (UTC). This is an informational message only; no user action is required.
    2017-08-23 07:12:10.92 Server      Node configuration: node 0: CPU mask: 0x000000000000003f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
    2017-08-23 07:12:11.06 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2017-08-23 07:12:11.08 Server      Database Instant File Initialization: enabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.
    2017-08-23 07:12:11.16 Server      Query Store settings initialized with enabled = 1, 
    2017-08-23 07:12:11.20 spid5s      Starting up database 'master'.
    2017-08-23 07:12:11.43 spid5s      209 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
    2017-08-23 07:12:11.46 spid5s      0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
    2017-08-23 07:12:11.46 spid5s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
    2017-08-23 07:12:11.61 Server      CLR version v4.0.30319 loaded.
    2017-08-23 07:12:13.57 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
    2017-08-23 07:12:13.75 spid5s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
    2017-08-23 07:12:13.78 spid5s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
    2017-08-23 07:12:15.42 spid5s      SQL Trace ID 1 was started by login "sa".
    2017-08-23 07:12:15.57 spid5s      Server name is 'CELSQLDB03'. This is an informational message only. No user action is required.
    2017-08-23 07:12:15.57 spid5s      The NETBIOS name of the local node that is running the server is 'CELSQLDB01'. This is an informational message only. No user action is required.
    2017-08-23 07:12:17.51 spid10s     A self-generated certificate was successfully loaded for encryption.
    2017-08-23 07:12:17.62 spid10s     Server is listening on [ 10.1.83.21 <ipv4> 1433].
    2017-08-23 07:12:17.62 spid10s     Started listening on virtual network name 'CELSQLDB03'. No user action is required.
    2017-08-23 07:12:17.63 spid10s     Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
    2017-08-23 07:12:17.63 spid10s     Server named pipe provider is ready to accept connection on [ \\.\pipe\$$\CELSQLDB03\sql\query ].
    2017-08-23 07:12:17.65 spid10s     SQL Server is now ready for client connections. This is an informational message; no user action is required.
    2017-08-23 07:12:17.67 Server      SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
    2017-08-23 07:12:17.94 Server      The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/CELSQLDB03.XXXXXXXX.corp ] for the SQL Server service.
    2017-08-23 07:12:17.95 Server      The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/CELSQLDB03.XXXXXXXX.corp:1433 ] for the SQL Server service.
    2017-08-23 07:12:18.00 Logon       Error: 18456, Severity: 14, State: 38.
    2017-08-23 07:12:18.00 Logon       Login failed for user 'smartcount'. Reason: Failed to open the explicitly specified database 'SmartCount'. [CLIENT: 10.10.0.7]
    2017-08-23 07:12:18.01 Logon       Error: 18456, Severity: 14, State: 38.
    2017-08-23 07:12:18.01 Logon       Login failed for user 'wbc'. Reason: Failed to open the explicitly specified database 'WBC_XXXXXXXX_GERACAO'. [CLIENT: 10.0.17.68]
    2017-08-23 07:12:18.01 Logon       Error: 18456, Severity: 14, State: 38.
    2017-08-23 07:12:18.01 Logon       Login failed for user 'wbc'. Reason: Failed to open the explicitly specified database 'WBC_RISCO'. [CLIENT: 10.0.17.203]
    2017-08-23 07:12:18.01 Logon       Error: 18456, Severity: 14, State: 38.
    2017-08-23 07:12:18.01 Logon       Login failed for user 'nextccuser'. Reason: Failed to open the explicitly specified database 'nextccdb'. [CLIENT: 10.0.224.77]
    2017-08-23 07:12:18.02 Logon       Error: 18456, Severity: 14, State: 38.
    2017-08-23 07:12:18.02 Logon       Login failed for user 'smartshare'. Reason: Failed to open the explicitly specified database 'SmartShare'. [CLIENT: 10.1.74.15]
    2017-08-23 07:12:18.03 Logon       Error: 18456, Severity: 14, State: 38.
    2017-08-23 07:12:18.03 Logon       Login failed for user 'nextccuser'. Reason: Failed to open the explicitly specified database 'nextccdb'. [CLIENT: 10.0.224.77]
    2017-08-23 07:12:18.08 Logon       Error: 18456, Severity: 14, State: 38.
    2017-08-23 07:12:18.08 Logon       Login failed for user 'nextccuser'. Reason: Failed to open the explicitly specified database 'nextccdb'. [CLIENT: 10.0.224.77]
    2017-08-23 07:12:18.10 Logon       Error: 18456, Severity: 14, State: 38.
    2017-08-23 07:12:18.10 Logon       Login failed for user 'nextccuser'. Reason: Failed to open the explicitly specified database 'nextccdb'. [CLIENT: 10.0.224.77]
    2017-08-23 07:12:18.15 Logon       Error: 18456, Severity: 14, State: 38.
    2017-08-23 07:12:18.15 Logon       Login failed for user 'smartcount'. Reason: Failed to open the explicitly specified database 'SmartCount'. [CLIENT: 10.20.0.7]
    2017-08-23 07:12:18.20 Logon       Error: 18456, Severity: 14, State: 38.
    2017-08-23 07:12:18.20 Logon       Login failed for user 'smartshare'. Reason: Failed to open the explicitly specified database 'smartsharedi'. [CLIENT: 10.0.22.61]
    2017-08-23 07:12:18.20 Logon       Error: 18456, Severity: 14, State: 38.
    2017-08-23 07:12:18.20 Logon       Login failed for user 'smartshare'. Reason: Failed to open the explicitly specified database 'SmartshareDI'. [CLIENT: 10.1.74.15]
    2017-08-23 07:12:18.47 Server      Software Usage Metrics is enabled.
    2017-08-23 07:12:18.65 Logon       Error: 18456, Severity: 14, State: 38.
    2017-08-23 07:12:18.65 Logon       Login failed for user 'wbc'. Reason: Failed to open the explicitly specified database 'WBC'. [CLIENT: 10.0.17.68]
    2017-08-23 07:12:18.70 Logon       Error: 18456, Severity: 14, State: 38.
    2017-08-23 07:12:18.70 Logon       Login failed for user 'wbc'. Reason: Failed to open the explicitly specified database 'WBC'. [CLIENT: 10.0.17.68]
    2017-08-23 07:12:18.93 Logon       Error: 18456, Severity: 14, State: 38.
    2017-08-23 07:12:18.93 Logon       Login failed for user 'nextccuser'. Reason: Failed to open the explicitly specified database 'nextccdb'. [CLIENT: 10.0.224.77]
    2017-08-23 07:12:19.20 spid12s     A new instance of the full-text filter daemon host process has been successfully started.
    2017-08-23 07:12:19.51 spid20s     Starting up database 'msdb'.
    2017-08-23 07:12:19.62 spid22s     Starting up database 'WBC_ENERGY_DW'.
    2017-08-23 07:12:19.70 spid23s     Starting up database 'SISBASE'.
    2017-08-23 07:12:19.74 spid25s     Starting up database 'WBC_XXXXXXXX_GERACAO'.
    2017-08-23 07:12:19.74 spid24s     Starting up database 'RISKMANAGER'.
    2017-08-23 07:12:19.81 spid28s     Starting up database 'WBC_FWKSIGN'.
    2017-08-23 07:12:19.85 spid26s     Starting up database 'WBC_RISCO'.
    2017-08-23 07:12:19.86 spid27s     Starting up database 'WBC_LEILAO'.
    2017-08-23 07:12:19.94 spid21s     Starting up database 'WBC'.
    2017-08-23 07:12:19.96 spid30s     Starting up database 'WBC_ETRM18_GERACAO_DW'.
    2017-08-23 07:12:19.98 spid31s     Starting up database 'Monitor'.
    2017-08-23 07:12:20.02 spid29s     Starting up database 'NEXTCCDB'.
    2017-08-23 07:12:20.22 spid6s      Starting up database 'mssqlsystemresource'.
    2017-08-23 07:12:20.23 spid33s     Starting up database 'SMARTCAPTURE'.
    2017-08-23 07:12:20.23 spid34s     Starting up database 'SMARTCOUNT'.
    2017-08-23 07:12:20.23 spid36s     Starting up database 'SMARTSHAREDI'.
    2017-08-23 07:12:20.23 spid32s     Starting up database 'SMARTSHARE'.
    2017-08-23 07:12:20.59 spid6s      The resource database build version is 13.00.4001. This is an informational message only. No user action is required.
    2017-08-23 07:12:22.51 Logon       Error: 18456, Severity: 14, State: 38.
    2017-08-23 07:12:22.51 Logon       Login failed for user 'nextccuser'. Reason: Failed to open the explicitly specified database 'nextccdb'. [CLIENT: 10.0.224.77]
    2017-08-23 07:12:22.52 spid31s     50 transactions rolled forward in database 'Monitor' (15:0). This is an informational message only. No user action is required.
    2017-08-23 07:12:22.54 spid23s     Recovery completed for database SISBASE (database ID 7) in 2 second(s) (analysis 75 ms, redo 180 ms, undo 462 ms.) This is an informational message only. No user action is required.
    2017-08-23 07:12:22.57 spid26s     164 transactions rolled forward in database 'WBC_RISCO' (10:0). This is an informational message only. No user action is required.
    2017-08-23 07:12:22.62 spid28s     Recovery completed for database WBC_FWKSIGN (database ID 12) in 2 second(s) (analysis 682 ms, redo 222 ms, undo 248 ms.) This is an informational message only. No user action is required.
    2017-08-23 07:12:22.66 spid29s     16 transactions rolled forward in database 'NEXTCCDB' (13:0). This is an informational message only. No user action is required.
    2017-08-23 07:12:22.69 spid26s     0 transactions rolled back in database 'WBC_RISCO' (10:0). This is an informational message only. No user action is required.
    2017-08-23 07:12:22.70 spid26s     Recovery completed for database WBC_RISCO (database ID 10) in 2 second(s) (analysis 86 ms, redo 141 ms, undo 56 ms.) This is an informational message only. No user action is required.
    2017-08-23 07:12:22.72 spid27s     Recovery completed for database WBC_LEILAO (database ID 11) in 2 second(s) (analysis 99 ms, redo 0 ms, undo 50 ms.) This is an informational message only. No user action is required.
    2017-08-23 07:12:22.78 spid31s     0 transactions rolled back in database 'Monitor' (15:0). This is an informational message only. No user action is required.
    2017-08-23 07:12:22.78 spid31s     Recovery completed for database Monitor (database ID 15) in 2 second(s) (analysis 204 ms, redo 144 ms, undo 110 ms.) This is an informational message only. No user action is required.
    2017-08-23 07:12:22.80 spid29s     0 transactions rolled back in database 'NEXTCCDB' (13:0). This is an informational message only. No user action is required.
    2017-08-23 07:12:22.80 spid29s     Recovery completed for database NEXTCCDB (database ID 13) in 2 second(s) (analysis 287 ms, redo 306 ms, undo 130 ms.) This is an informational message only. No user action is required.
    2017-08-23 07:12:22.86 spid6s      Starting up database 'model'.
    2017-08-23 07:12:22.86 spid20s     1296 transactions rolled forward in database 'msdb' (4:0). This is an informational message only. No user action is required.
    2017-08-23 07:12:22.94 spid20s     0 transactions rolled back in database 'msdb' (4:0). This is an informational message only. No user action is required.
    2017-08-23 07:12:22.94 spid20s     Recovery is writing a checkpoint in database 'msdb' (4). This is an informational message only. No user action is required.
    2017-08-23 07:12:22.96 spid20s     Recovery completed for database msdb (database ID 4) in 2 second(s) (analysis 763 ms, redo 698 ms, undo 64 ms.) This is an informational message only. No user action is required.
    2017-08-23 07:12:22.96 spid36s     264 transactions rolled forward in database 'SMARTSHAREDI' (19:0). This is an informational message only. No user action is required.
    2017-08-23 07:12:23.04 spid36s     0 transactions rolled back in database 'SMARTSHAREDI' (19:0). This is an informational message only. No user action is required.
    2017-08-23 07:12:23.35 spid6s      Polybase feature disabled.
    2017-08-23 07:12:23.35 spid6s      Clearing tempdb database.
    2017-08-23 07:12:23.90 spid6s      Starting up database 'tempdb'.
    2017-08-23 07:12:23.92 spid32s     346 transactions rolled forward in database 'SMARTSHARE' (18:0). This is an informational message only. No user action is required.
    2017-08-23 07:12:23.95 spid32s     0 transactions rolled back in database 'SMARTSHARE' (18:0). This is an informational message only. No user action is required.
    2017-08-23 07:12:24.11 spid6s      The tempdb database has 1 data file(s).
    2017-08-23 07:12:24.13 spid40s     The Service Broker endpoint is in disabled or stopped state.
    2017-08-23 07:12:24.14 spid40s     The Database Mirroring endpoint is in disabled or stopped state.
    2017-08-23 07:12:24.21 spid30s     CHECKDB for database 'WBC_ETRM18_GERACAO_DW' finished without errors on 2017-08-22 20:01:16.297 (local time). This is an informational message only; no user action is required.
    2017-08-23 07:12:24.38 spid31s     CHECKDB for database 'Monitor' finished without errors on 2017-08-22 20:00:09.557 (local time). This is an informational message only; no user action is required.
    2017-08-23 07:12:24.38 spid23s     CHECKDB for database 'SISBASE' finished without errors on 2017-08-22 20:00:16.890 (local time). This is an informational message only; no user action is required.
    2017-08-23 07:12:24.39 spid26s     CHECKDB for database 'WBC_RISCO' finished without errors on 2017-08-22 20:01:31.870 (local time). This is an informational message only; no user action is required.
    2017-08-23 07:12:24.39 spid28s     CHECKDB for database 'WBC_FWKSIGN' finished without errors on 2017-08-22 20:01:28.350 (local time). This is an informational message only; no user action is required.
    2017-08-23 07:12:24.41 spid32s     CHECKDB for database 'SMARTSHARE' finished without errors on 2017-08-22 20:01:08.940 (local time). This is an informational message only; no user action is required.
    2017-08-23 07:12:24.42 spid27s     CHECKDB for database 'WBC_LEILAO' finished without errors on 2017-08-22 20:01:29.083 (local time). This is an informational message only; no user action is required.
    2017-08-23 07:12:24.44 spid36s     CHECKDB for database 'SMARTSHAREDI' finished without errors on 2017-08-22 20:01:11.930 (local time). This is an informational message only; no user action is required.
    2017-08-23 07:12:24.46 spid29s     CHECKDB for database 'NEXTCCDB' finished without errors on 2017-08-22 20:00:10.820 (local time). This is an informational message only; no user action is required.
    2017-08-23 07:12:24.77 spid40s     Service Broker manager has started.
    2017-08-23 07:12:24.88 spid24s     CHECKDB for database 'RISKMANAGER' finished without errors on 2017-08-22 20:00:12.380 (local time). This is an informational message only; no user action is required.
    2017-08-23 07:12:24.92 Logon       Error: 18456, Severity: 14, State: 38.
    2017-08-23 07:12:24.92 Logon       Login failed for user 'smartcount'. Reason: Failed to open the explicitly specified database 'SmartCount'. [CLIENT: 10.160.0.7]
    2017-08-23 07:12:25.45 spid33s     CHECKDB for database 'SMARTCAPTURE' finished without errors on 2017-08-22 20:00:17.990 (local time). This is an informational message only; no user action is required.
    2017-08-23 07:12:26.47 spid22s     CHECKDB for database 'WBC_ENERGY_DW' finished without errors on 2017-08-22 20:01:13.190 (local time). This is an informational message only; no user action is required.
    2017-08-23 07:12:27.22 Logon       Error: 18456, Severity: 14, State: 38.
    2017-08-23 07:12:27.22 Logon       Login failed for user 'smartcount'. Reason: Failed to open the explicitly specified database 'SmartCount'. [CLIENT: 10.0.0.12]
    2017-08-23 07:12:27.24 spid25s     3104 transactions rolled forward in database 'WBC_XXXXXXXX_GERACAO' (9:0). This is an informational message only. No user action is required.
    2017-08-23 07:12:27.27 Logon       Error: 18456, Severity: 14, State: 38.
    2017-08-23 07:12:27.27 Logon       Login failed for user 'smartcount'. Reason: Failed to open the explicitly specified database 'SmartCount'. [CLIENT: 10.20.0.7]
    2017-08-23 07:12:27.27 spid25s     0 transactions rolled back in database 'WBC_XXXXXXXX_GERACAO' (9:0). This is an informational message only. No user action is required.
    2017-08-23 07:12:27.37 spid25s     CHECKDB for database 'WBC_XXXXXXXX_GERACAO' finished without errors on 2017-08-20 20:00:04.113 (local time). This is an informational message only; no user action is required.
    2017-08-23 07:12:27.55 spid34s     221 transactions rolled forward in database 'SMARTCOUNT' (17:0). This is an informational message only. No user action is required.
    2017-08-23 07:12:27.62 spid34s     0 transactions rolled back in database 'SMARTCOUNT' (17:0). This is an informational message only. No user action is required.
    2017-08-23 07:12:27.65 spid56      Attempting to load library 'xpsqlbot.dll' into memory. This is an informational message only. No user action is required.
    2017-08-23 07:12:27.68 spid56      Using 'xpsqlbot.dll' version '2015.130.1601' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
    2017-08-23 07:12:27.78 spid34s     CHECKDB for database 'SMARTCOUNT' finished without errors on 2017-08-22 20:00:24.557 (local time). This is an informational message only; no user action is required.
    2017-08-23 07:12:27.81 spid56      Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
    2017-08-23 07:12:27.84 spid21s     3126 transactions rolled forward in database 'WBC' (5:0). This is an informational message only. No user action is required.
    2017-08-23 07:12:27.86 spid56      Using 'xpstar.dll' version '2015.130.1601' to execute extended stored procedure 'xp_sqlagent_notify'. This is an informational message only; no user action is required.
    2017-08-23 07:12:27.94 spid21s     0 transactions rolled back in database 'WBC' (5:0). This is an informational message only. No user action is required.
    2017-08-23 07:12:28.15 spid21s     CHECKDB for database 'WBC' finished without errors on 2017-08-19 15:00:04.020 (local time). This is an informational message only; no user action is required.
    2017-08-23 07:12:28.18 spid5s      Recovery is complete. This is an informational message only. No user action is required.
    2017-08-23 07:14:21.61 Logon       Error: 18456, Severity: 14, State: 5.
    2017-08-23 07:14:21.61 Logon       Login failed for user 'teste'. Reason: Could not find a login matching the name provided. [CLIENT: 10.1.83.32]
    2017-08-23 07:14:21.62 Logon       Error: 18456, Severity: 14, State: 5.
    2017-08-23 07:14:21.62 Logon       Login failed for user 'teste'. Reason: Could not find a login matching the name provided. [CLIENT: 10.1.83.32]
    2017-08-23 07:14:21.63 Logon       Error: 18456, Severity: 14, State: 5.
    2017-08-23 07:14:21.63 Logon       Login failed for user 'teste'. Reason: Could not find a login matching the name provided. [CLIENT: 10.1.83.32]
    2017-08-23 07:14:21.64 Logon       Error: 18456, Severity: 14, State: 5.
    2017-08-23 07:14:21.64 Logon       Login failed for user 'teste'. Reason: Could not find a login matching the name provided. [CLIENT: 10.1.83.32]
    2017-08-23 07:14:21.65 Logon       Error: 18456, Severity: 14, State: 5.
    2017-08-23 07:14:21.65 Logon       Login failed for user 'teste'. Reason: Could not find a login matching the name provided. [CLIENT: 10.1.83.32]
    2017-08-23 07:14:21.65 Logon       Error: 18456, Severity: 14, State: 5.
    2017-08-23 07:14:21.65 Logon       Login failed for user 'teste'. Reason: Could not find a login matching the name provided. [CLIENT: 10.1.83.32]
    2017-08-23 07:14:21.66 Logon       Error: 18456, Severity: 14, State: 5.
    2017-08-23 07:14:21.66 Logon       Login failed for user 'teste'. Reason: Could not find a login matching the name provided. [CLIENT: 10.1.83.32]
    2017-08-23 07:14:21.67 Logon       Error: 18456, Severity: 14, State: 5.
    2017-08-23 07:14:21.67 Logon       Login failed for user 'teste'. Reason: Could not find a login matching the name provided. [CLIENT: 10.1.83.32]
    2017-08-23 07:14:21.68 Logon       Error: 18456, Severity: 14, State: 5.
    2017-08-23 07:14:21.68 Logon       Login failed for user 'teste'. Reason: Could not find a login matching the name provided. [CLIENT: 10.1.83.32]
    2017-08-23 07:14:21.70 Logon       Error: 18456, Severity: 14, State: 5.
    2017-08-23 07:14:21.70 Logon       Login failed for user 'smartshareteste'. Reason: Could not find a login matching the name provided. [CLIENT: 10.1.83.32]
    2017-08-23 07:14:21.85 Logon       Error: 18456, Severity: 14, State: 5.
    2017-08-23 07:14:21.85 Logon       Login failed for user 'teste'. Reason: Could not find a login matching the name provided. [CLIENT: 10.1.83.32]
    2017-08-23 07:14:21.87 Logon       Error: 18456, Severity: 14, State: 5.
    2017-08-23 07:14:21.87 Logon       Login failed for user 'teste'. Reason: Could not find a login matching the name provided. [CLIENT: 10.1.83.32]
    2017-08-23 07:14:21.88 Logon       Error: 18456, Severity: 14, State: 5.
    2017-08-23 07:14:21.88 Logon       Login failed for user 'teste'. Reason: Could not find a login matching the name provided. [CLIENT: 10.1.83.32]
    2017-08-23 07:14:21.89 Logon       Error: 18456, Severity: 14, State: 5.
    2017-08-23 07:14:21.89 Logon       Login failed for user 'teste'. Reason: Could not find a login matching the name provided. [CLIENT: 10.1.83.32]
    2017-08-23 07:14:21.90 Logon       Error: 18456, Severity: 14, State: 5.
    2017-08-23 07:14:21.90 Logon       Login failed for user 'teste'. Reason: Could not find a login matching the name provided. [CLIENT: 10.1.83.32]
    2017-08-23 07:14:21.91 Logon       Error: 18456, Severity: 14, State: 5.
    2017-08-23 07:14:21.91 Logon       Login failed for user 'teste'. Reason: Could not find a login matching the name provided. [CLIENT: 10.1.83.32]
    2017-08-23 07:14:21.92 Logon       Error: 18456, Severity: 14, State: 5.
    2017-08-23 07:14:21.92 Logon       Login failed for user 'teste'. Reason: Could not find a login matching the name provided. [CLIENT: 10.1.83.32]
    2017-08-23 07:14:21.93 Logon       Error: 18456, Severity: 14, State: 5.
    2017-08-23 07:14:21.93 Logon       Login failed for user 'teste'. Reason: Could not find a login matching the name provided. [CLIENT: 10.1.83.32]
    2017-08-23 07:14:21.94 Logon       Error: 18456, Severity: 14, State: 5.
    2017-08-23 07:14:21.94 Logon       Login failed for user 'smartshareteste'. Reason: Could not find a login matching the name provided. [CLIENT: 10.1.83.32]
    2017-08-23 07:17:27.59 spid58      Using 'dbghelp.dll' version '4.0.5'
    2017-08-23 07:30:58.25 Backup      Log was backed up. Database: Monitor, creation date(time): 2017/07/03(10:06:51), first LSN: 504:20695:1, last LSN: 504:20795:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-000018F0-0000'}). This is an informational message only. No user action is required.
    2017-08-23 07:30:59.04 Backup      Log was backed up. Database: NEXTCCDB, creation date(time): 2017/06/26(15:00:52), first LSN: 145:24040:1, last LSN: 145:24070:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-000018F0-0000'}). This is an informational message only. No user action is required.
    2017-08-23 07:30:59.69 Backup      Log was backed up. Database: RISKMANAGER, creation date(time): 2017/06/14(13:56:04), first LSN: 24303:3195:1, last LSN: 24303:3203:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-000018F0-0000'}). This is an informational message only. No user action is required.
    2017-08-23 07:31:00.50 Backup      Log was backed up. Database: SISBASE, creation date(time): 2017/06/14(10:25:33), first LSN: 173:6757:1, last LSN: 173:6762:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-000018F0-0000'}). This is an informational message only. No user action is required.
    2017-08-23 07:31:01.30 Backup      Log was backed up. Database: SMARTCAPTURE, creation date(time): 2017/07/04(09:08:39), first LSN: 27594:22608:1, last LSN: 27594:22613:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-000018F0-0000'}). This is an informational message only. No user action is required.
    2017-08-23 07:31:02.50 Backup      Error: 3201, Severity: 16, State: 7.
    2017-08-23 07:31:02.50 Backup      Cannot open backup device 'TDPSQL-0000522C-0000'. Operating system error 0x80070002(The system cannot find the file specified.).
    2017-08-23 07:31:02.51 Backup      Error: 3041, Severity: 16, State: 1.
    2017-08-23 07:31:02.51 Backup      BACKUP failed to complete the command BACKUP LOG Monitor. Check the backup application log for detailed messages.
    2017-08-23 07:31:02.66 Backup      Log was backed up. Database: SMARTCOUNT, creation date(time): 2017/07/04(09:12:50), first LSN: 73023:6267:1, last LSN: 73023:21984:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-000018F0-0000'}). This is an informational message only. No user action is required.
    2017-08-23 07:31:03.60 Backup      Log was backed up. Database: SMARTSHARE, creation date(time): 2017/07/05(11:21:27), first LSN: 10115:4100:1, last LSN: 10115:4521:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-000018F0-0000'}). This is an informational message only. No user action is required.
    2017-08-23 07:31:04.38 Backup      Log was backed up. Database: SMARTSHAREDI, creation date(time): 2017/07/05(11:28:53), first LSN: 38830:21178:1, last LSN: 38830:21462:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-000018F0-0000'}). This is an informational message only. No user action is required.
    2017-08-23 07:31:05.69 Backup      Log was backed up. Database: WBC, creation date(time): 2017/06/26(07:40:17), first LSN: 624739:138081:1, last LSN: 624739:143578:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-000018F0-0000'}). This is an informational message only. No user action is required.
    2017-08-23 07:31:09.32 Backup      Log was backed up. Database: WBC_XXXXXXXX_GERACAO, creation date(time): 2017/06/26(08:56:07), first LSN: 627184:126662:1, last LSN: 627184:132178:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-000018F0-0000'}). This is an informational message only. No user action is required.
    2017-08-23 07:31:09.87 Backup      Log was backed up. Database: WBC_ENERGY_DW, creation date(time): 2017/06/23(15:21:53), first LSN: 96212:19422:1, last LSN: 96212:19452:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-000018F0-0000'}). This is an informational message only. No user action is required.
    2017-08-23 07:31:10.40 Backup      Log was backed up. Database: WBC_ETRM18_GERACAO_DW, creation date(time): 2017/06/27(15:37:30), first LSN: 1843:8278:1, last LSN: 1843:8299:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-000018F0-0000'}). This is an informational message only. No user action is required.
    2017-08-23 07:31:11.46 Backup      Log was backed up. Database: WBC_FWKSIGN, creation date(time): 2017/06/23(15:18:21), first LSN: 217:15271:1, last LSN: 217:15276:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-000018F0-0000'}). This is an informational message only. No user action is required.
    2017-08-23 07:31:12.58 Backup      Log was backed up. Database: WBC_LEILAO, creation date(time): 2017/06/23(15:16:01), first LSN: 62816:884:1, last LSN: 62816:892:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-000018F0-0000'}). This is an informational message only. No user action is required.
    2017-08-23 07:31:13.32 Backup      Log was backed up. Database: WBC_RISCO, creation date(time): 2017/06/23(15:13:17), first LSN: 966:24494:1, last LSN: 966:24671:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-000018F0-0000'}). This is an informational message only. No user action is required.
    2017-08-23 08:30:21.03 Backup      Error: 3201, Severity: 16, State: 7.
    2017-08-23 08:30:21.03 Backup      Cannot open backup device 'TDPSQL-00000F10-0000'. Operating system error 0x80070002(The system cannot find the file specified.).
    2017-08-23 08:30:21.03 Backup      Error: 3041, Severity: 16, State: 1.
    2017-08-23 08:30:21.03 Backup      BACKUP failed to complete the command BACKUP LOG Monitor. Check the backup application log for detailed messages.
    2017-08-23 08:30:29.86 Backup      Log was backed up. Database: Monitor, creation date(time): 2017/07/03(10:06:51), first LSN: 504:20795:1, last LSN: 504:20863:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-000015A4-0000'}). This is an informational message only. No user action is required.
    2017-08-23 08:30:30.37 Backup      Log was backed up. Database: NEXTCCDB, creation date(time): 2017/06/26(15:00:52), first LSN: 145:24070:1, last LSN: 145:24088:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-000015A4-0000'}). This is an informational message only. No user action is required.
    2017-08-23 08:30:31.47 Backup      Log was backed up. Database: RISKMANAGER, creation date(time): 2017/06/14(13:56:04), first LSN: 24303:3203:1, last LSN: 24303:3212:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-000015A4-0000'}). This is an informational message only. No user action is required.
    2017-08-23 08:30:32.58 Backup      Log was backed up. Database: SISBASE, creation date(time): 2017/06/14(10:25:33), first LSN: 173:6762:1, last LSN: 173:6768:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-000015A4-0000'}). This is an informational message only. No user action is required.
    2017-08-23 08:30:33.55 Backup      Log was backed up. Database: SMARTCAPTURE, creation date(time): 2017/07/04(09:08:39), first LSN: 27594:22613:1, last LSN: 27594:22619:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-000015A4-0000'}). This is an informational message only. No user action is required.
    2017-08-23 08:30:34.33 Backup      Log was backed up. Database: SMARTCOUNT, creation date(time): 2017/07/04(09:12:50), first LSN: 73023:21984:1, last LSN: 73023:22017:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-000015A4-0000'}). This is an informational message only. No user action is required.
    2017-08-23 08:30:35.41 Backup      Log was backed up. Database: SMARTSHARE, creation date(time): 2017/07/05(11:21:27), first LSN: 10115:4521:1, last LSN: 10115:4530:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-000015A4-0000'}). This is an informational message only. No user action is required.
    2017-08-23 08:30:36.39 Backup      Log was backed up. Database: SMARTSHAREDI, creation date(time): 2017/07/05(11:28:53), first LSN: 38830:21462:1, last LSN: 38830:21476:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-000015A4-0000'}). This is an informational message only. No user action is required.
    2017-08-23 08:30:37.52 Backup      Log was backed up. Database: WBC, creation date(time): 2017/06/26(07:40:17), first LSN: 624739:143578:1, last LSN: 624739:143602:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-000015A4-0000'}). This is an informational message only. No user action is required.
    2017-08-23 08:30:39.35 Backup      Log was backed up. Database: WBC_XXXXXXXX_GERACAO, creation date(time): 2017/06/26(08:56:07), first LSN: 627184:132178:1, last LSN: 627184:132207:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-000015A4-0000'}). This is an informational message only. No user action is required.
    2017-08-23 08:30:39.77 Backup      Log was backed up. Database: WBC_ENERGY_DW, creation date(time): 2017/06/23(15:21:53), first LSN: 96212:19452:1, last LSN: 96212:19461:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-000015A4-0000'}). This is an informational message only. No user action is required.
    2017-08-23 08:30:40.34 Backup      Log was backed up. Database: WBC_ETRM18_GERACAO_DW, creation date(time): 2017/06/27(15:37:30), first LSN: 1843:8299:1, last LSN: 1843:8307:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-000015A4-0000'}). This is an informational message only. No user action is required.
    2017-08-23 08:30:41.39 Backup      Log was backed up. Database: WBC_FWKSIGN, creation date(time): 2017/06/23(15:18:21), first LSN: 217:15276:1, last LSN: 217:15282:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-000015A4-0000'}). This is an informational message only. No user action is required.
    2017-08-23 08:30:42.68 Backup      Log was backed up. Database: WBC_LEILAO, creation date(time): 2017/06/23(15:16:01), first LSN: 62816:892:1, last LSN: 62816:901:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-000015A4-0000'}). This is an informational message only. No user action is required.
    2017-08-23 08:30:43.43 Backup      Log was backed up. Database: WBC_RISCO, creation date(time): 2017/06/23(15:13:17), first LSN: 966:24671:1, last LSN: 966:24684:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-000015A4-0000'}). This is an informational message only. No user action is required.
    2017-08-23 09:30:41.83 Backup      Error: 3201, Severity: 16, State: 7.
    2017-08-23 09:30:41.83 Backup      Cannot open backup device 'TDPSQL-00005554-0000'. Operating system error 0x80070002(The system cannot find the file specified.).
    2017-08-23 09:30:41.83 Backup      Error: 3041, Severity: 16, State: 1.
    2017-08-23 09:30:41.83 Backup      BACKUP failed to complete the command BACKUP LOG Monitor. Check the backup application log for detailed messages.
    2017-08-23 09:31:03.92 Backup      Log was backed up. Database: Monitor, creation date(time): 2017/07/03(10:06:51), first LSN: 504:20863:1, last LSN: 504:20926:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-00001AF8-0000'}). This is an informational message only. No user action is required.
    2017-08-23 09:31:05.12 Backup      Log was backed up. Database: NEXTCCDB, creation date(time): 2017/06/26(15:00:52), first LSN: 145:24088:1, last LSN: 145:24093:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-00001AF8-0000'}). This is an informational message only. No user action is required.
    2017-08-23 09:31:07.21 Backup      Log was backed up. Database: RISKMANAGER, creation date(time): 2017/06/14(13:56:04), first LSN: 24303:3212:1, last LSN: 24303:3217:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-00001AF8-0000'}). This is an informational message only. No user action is required.
    2017-08-23 09:31:08.10 Backup      Log was backed up. Database: SISBASE, creation date(time): 2017/06/14(10:25:33), first LSN: 173:6768:1, last LSN: 173:6773:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-00001AF8-0000'}). This is an informational message only. No user action is required.
    2017-08-23 09:31:08.78 Backup      Log was backed up. Database: SMARTCAPTURE, creation date(time): 2017/07/04(09:08:39), first LSN: 27594:22619:1, last LSN: 27594:22624:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-00001AF8-0000'}). This is an informational message only. No user action is required.
    2017-08-23 09:31:10.15 Backup      Log was backed up. Database: SMARTCOUNT, creation date(time): 2017/07/04(09:12:50), first LSN: 73023:22017:1, last LSN: 73023:22022:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-00001AF8-0000'}). This is an informational message only. No user action is required.
    2017-08-23 09:31:10.93 Backup      Log was backed up. Database: SMARTSHARE, creation date(time): 2017/07/05(11:21:27), first LSN: 10115:4530:1, last LSN: 10115:4535:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-00001AF8-0000'}). This is an informational message only. No user action is required.
    2017-08-23 09:31:11.50 Backup      Log was backed up. Database: SMARTSHAREDI, creation date(time): 2017/07/05(11:28:53), first LSN: 38830:21476:1, last LSN: 38830:21481:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-00001AF8-0000'}). This is an informational message only. No user action is required.
    2017-08-23 09:31:12.56 Backup      Log was backed up. Database: WBC, creation date(time): 2017/06/26(07:40:17), first LSN: 624739:143602:1, last LSN: 624739:143607:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-00001AF8-0000'}). This is an informational message only. No user action is required.
    2017-08-23 09:31:17.04 Backup      Log was backed up. Database: WBC_XXXXXXXX_GERACAO, creation date(time): 2017/06/26(08:56:07), first LSN: 627184:132207:1, last LSN: 627184:132212:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-00001AF8-0000'}). This is an informational message only. No user action is required.
    2017-08-23 09:31:19.76 Backup      Log was backed up. Database: WBC_ENERGY_DW, creation date(time): 2017/06/23(15:21:53), first LSN: 96212:19461:1, last LSN: 96212:19466:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-00001AF8-0000'}). This is an informational message only. No user action is required.
    2017-08-23 09:31:20.12 Backup      Log was backed up. Database: WBC_ETRM18_GERACAO_DW, creation date(time): 2017/06/27(15:37:30), first LSN: 1843:8307:1, last LSN: 1843:8311:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-00001AF8-0000'}). This is an informational message only. No user action is required.
    2017-08-23 09:31:21.21 Backup      Log was backed up. Database: WBC_FWKSIGN, creation date(time): 2017/06/23(15:18:21), first LSN: 217:15282:1, last LSN: 217:15287:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-00001AF8-0000'}). This is an informational message only. No user action is required.
    2017-08-23 09:31:22.36 Backup      Log was backed up. Database: WBC_LEILAO, creation date(time): 2017/06/23(15:16:01), first LSN: 62816:901:1, last LSN: 62816:906:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-00001AF8-0000'}). This is an informational message only. No user action is required.
    2017-08-23 09:31:24.39 Backup      Log was backed up. Database: WBC_RISCO, creation date(time): 2017/06/23(15:13:17), first LSN: 966:24684:1, last LSN: 966:24689:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-00001AF8-0000'}). This is an informational message only. No user action is required.
    2017-08-23 10:22:06.55 spid56      Configuration option 'Agent XPs' changed from 1 to 0. Run the RECONFIGURE statement to install.
    2017-08-23 10:22:06.58 spid5s      SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required.
    2017-08-23 10:22:07.35 spid40s     Service Broker manager has shut down.
    2017-08-23 10:22:07.36 spid5s      .NET Framework runtime has been stopped.
    2017-08-23 10:22:08.45 spid5s      SQL Server shutdown has been initiated
    2017-08-23 10:22:08.45 spid5s      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
    2017-08-23 10:22:08.51 spid10s     The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvc/CELSQLDB03.XXXXXXXX.corp ] for the SQL Server service.
    2017-08-23 10:22:08.51 spid10s     The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvc/CELSQLDB03.XXXXXXXX.corp:1433 ] for the SQL Server service.



    sexta-feira, 29 de setembro de 2017 18:22
  • Rogério,

    veja se o problema se enquadra em algum dos tópicos desse link:

    https://docs.microsoft.com/en-us/sql/sql-server/failover-clusters/windows/failover-cluster-troubleshooting


    Vinicius Fonseca - MCP | MCTS | MCDBA | MCITP | MCTS | MCT | ITIL Foundation - DGA SISTEMAS - Se minha resposta for útil, classifique-a. :)

    sexta-feira, 29 de setembro de 2017 18:47