Prezados, parabéns pelos excelentes argumentos.

Jcésar Carvalló


2012/1/27, Thiago Elvas <thiagoelvas@...>:
> Boa tarde.
> Procure nos servicos do windows se estao todos startados e procure alguma
> coisa chamada sourface no sql. Tem que marcar TCP/IP
>
> -----Original Message-----
>
> From: Fernando Junior
> Sent: 27 Jan 2012 17:02:39 GMT
> To: ms-bel@...
> Subject: Re: [ms-bel] Problema com acesso local sqlexpress ..
>
> tenta com "localhost"
>
> 2012/1/27 Mauricio Borges Nunes <mauriciobnunes@...>
>
>> **
>>
>>
>> Alguem já passou por esta situação.?
>> So conbsigo logar em servidor remoto, na minha máquina não. Segue abaixo
>> mensagem do manager studio e log de erro.
>> Aguardo opiniões...
>>
>> Agradecido
>>
>> Mauricio Nunes
>>
>> ----------------------------------------------------------
>> ----------------------------------------------------------
>>
>> TÍTULO: Conectar ao Servidor
>> ------------------------------
>>
>> Não é possível conectar-se a NOTE\SQLEXPRESS.
>>
>> ------------------------------
>> INFORMAÇÕES ADICIONAIS:
>>
>> Erro de rede ou específico à instância ao estabelecer conexão com o SQL
>> Server. O servidor não foi encontrado ou não estava acessível. Verifique
>> se
>> o nome da instância está correto e se o SQL Server está configurado para
>> permitir conexões remotas. (provider: Interfaces de Rede SQL, error: 26 -
>> Erro ao Localizar Servidor/Instância Especificada) (Microsoft SQL Server,
>> Erro: -1)
>>
>> Para obter ajuda, clique em:
>>
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&\
EvtID=-1&LinkId=20476
>>
>> ------------------------------
>> BOTÕES:
>>
>> OK
>> ------------------------------
>>
>> ----------------------------------------------------------
>> ----------------------------------------------------------
>>
>> 2012-01-27 09:28:14.95 Server Microsoft SQL Server 2008 R2 (SP1) -
>> 10.50.2500.0 (Intel X86)
>> Jun 17 2011 00:57:23
>> Copyright (c) Microsoft Corporation
>> Express Edition with Advanced Services on Windows NT 6.1 <X86> (Build
>> 7601: Service Pack 1)
>>
>> 2012-01-27 09:28:14.97 Server (c) Microsoft Corporation.
>> 2012-01-27 09:28:14.97 Server All rights reserved.
>> 2012-01-27 09:28:14.97 Server Server process ID is 1860.
>> 2012-01-27 09:28:14.97 Server System Manufacturer: 'Hewlett-Packard',
>> System Model: 'Compaq Presario CQ42 Notebook PC'.
>> 2012-01-27 09:28:14.97 Server Authentication mode is WINDOWS-ONLY.
>> 2012-01-27 09:28:14.97 Server Logging SQL Server messages in file
>> 'c:\Program Files\Microsoft SQL
>> Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
>> 2012-01-27 09:28:15.01 Server This instance of SQL Server last
>> reported using a process ID of 2316 at 15/01/2012 23:06:07 (local)
>> 16/01/2012 02:06:07 (UTC). This is an informational message only; no user
>> action is required.
>> 2012-01-27 09:28:15.01 Server Registry startup parameters:
>> -d c:\Program Files\Microsoft SQL
>> Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\master.mdf
>> -e c:\Program Files\Microsoft SQL
>> Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG
>> -l c:\Program Files\Microsoft SQL
>> Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
>> 2012-01-27 09:28:15.09 Servidor SQL Server is starting at normal
>> priority base (=7). This is an informational message only. No user action
>> is required.
>> 2012-01-27 09:28:15.09 Servidor Detected 2 CPUs. This is an
>> informational message; no user action is required.
>> 2012-01-27 09:28:15.65 Servidor 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.
>> 2012-01-27 09:28:16.40 Servidor Node configuration: node 0: CPU mask:
>> 0x00000003:0 Active CPU mask: 0x00000003:0. This message provides a
>> description of the NUMA configuration for this computer. This is an
>> informational message only. No user action is required.
>> 2012-01-27 09:28:17.20 spid7s Starting up database 'master'.
>> 2012-01-27 09:28:17.62 spid7s The tail of the log for database master
>> is being rewritten to match the new sector size of 4096 bytes. 3584 bytes
>> at offset 1057280 in file c:\Program Files\Microsoft SQL
>> Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\mastlog.ldf will be written.
>> 2012-01-27 09:28:18.20 spid7s FILESTREAM: effective level = 0,
>> configured level = 0, file system access share name = 'SQLEXPRESS'.
>> 2012-01-27 09:28:18.73 spid7s SQL Trace ID 1 was started by login
>> "sa".
>> 2012-01-27 09:28:18.73 spid7s Starting up database
>> 'mssqlsystemresource'.
>> 2012-01-27 09:28:18.73 spid7s The resource database build version is
>> 10.50.2500. This is an informational message only. No user action is
>> required.
>> 2012-01-27 09:28:19.18 spid7s Server name is 'NOTE\SQLEXPRESS'. This
>> is an informational message only. No user action is required.
>> 2012-01-27 09:28:19.18 spid10s Starting up database 'model'.
>> 2012-01-27 09:28:19.24 spid7s Informação: não foram encontrados
>> idiomas com suporte a texto completo.
>> 2012-01-27 09:28:19.24 spid7s Starting up database 'msdb'.
>> 2012-01-27 09:28:19.46 Servidor A self-generated certificate was
>> successfully loaded for encryption.
>> 2012-01-27 09:28:19.46 Servidor Server local connection provider is
>> ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ].
>> 2012-01-27 09:28:19.46 Servidor Server local connection provider is
>> ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ].
>> 2012-01-27 09:28:19.46 Servidor Dedicated administrator connection
>> support was not started because it is disabled on this edition of SQL
>> Server. If you want to use a dedicated administrator connection, restart
>> SQL Server using the trace flag 7806. This is an informational message
>> only. No user action is required.
>> 2012-01-27 09:28:19.51 Servidor The SQL Server Network Interface
>> library could not register the Service Principal Name (SPN) for the SQL
>> Server service. Error: 0x54b, state: 3. Failure to register an SPN may
>> cause integrated authentication to fall back to NTLM instead of Kerberos.
>> This is an informational message. Further action is only required if
>> Kerberos authentication is required by authentication policies.
>> 2012-01-27 09:28:19.52 Servidor SQL Server is now ready for client
>> connections. This is an informational message; no user action is required.
>> 2012-01-27 09:28:19.37 spid10s Erro: 9003, Gravidade: 20, Estado: 1.
>> 2012-01-27 09:28:19.37 spid10s The log scan number (37:168:1) passed
>> to log scan in database 'model' is not valid. This error may indicate data
>> corruption or that the log file (.ldf) does not match the data file
>> (.mdf).
>> If this error occurred during replication, re-create the publication.
>> Otherwise, restore from backup if the problem results in a failure during
>> startup.
>> 2012-01-27 09:28:20.51 spid10s SQL Trace was stopped due to server
>> shutdown. Trace ID = '1'. This is an informational message only; no user
>> action is required.
>>
>> ----------------------------------------------------------
>> ----------------------------------------------------------
>>
>>
>>
>
>
>
> --
> Fernando Amandio.
> Bacharel em Ciência da Computação - CESUPA.
> Tel.:(19) 8271-4788
>


--
IMPORTANTE:
Se pretende redirecionar este e-mail, apague todos os endereços que
aparecem nele. Use a opção de segurança Cco ou Bcc. Desta forma você
estará protegendo seus amigos e a você mesmo. Participe da campanha
contra a propagação de vírus.