Erreur lors de la connexion à la base de donnée

Résolu
cs_AmK Messages postés 368 Date d'inscription jeudi 13 mars 2003 Statut Membre Dernière intervention 27 janvier 2010 - 19 déc. 2007 à 18:13
cs_AmK Messages postés 368 Date d'inscription jeudi 13 mars 2003 Statut Membre Dernière intervention 27 janvier 2010 - 20 déc. 2007 à 00:28
Bonsoir ,
J'ai rencontré des difficultés lors de la connexion à mon instance SQLExpress.

En lançant SQL Server Manager (SSMS) , et en tentant de m'y connecter j'obtiens le message d'erreur suivant :



"Cannot connecte to AMOKRANE\`SQLEXPRESS

An error has occured while establishing a connection to the server .
When connecting to SQL Server 2005 , this falure may be aused by the
fact that under the default settings

SQL Server does not allow remote connections ( provider : SQL Network
Interfaces,error : 26-Error Locating Server/Insance Specified )
(Microsoft SQL Server)"

En allant jeter un coup d'oeil au configuration manager , j'ai vu que
mon instance SQL Server était stoppée , en essayent de la démarrer j'ai
eu le message d'erreur suivant :

"The request failed or the service did not respond in a timely fashion.
Consult the event log or the other applicable error logs for details"

Où est ce que ça cloche ?

Merci !

2 réponses

cs_AmK Messages postés 368 Date d'inscription jeudi 13 mars 2003 Statut Membre Dernière intervention 27 janvier 2010 1
19 déc. 2007 à 20:18
Pour info , voici ce que me dit le log d'erreur :

2007-12-18 19:36:12.20 Server Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.1 (Build 2600: Service Pack 2)

2007-12-18 19:36:12.20 Server (c) 2005 Microsoft Corporation.
2007-12-18 19:36:12.20 Server All rights reserved.
2007-12-18 19:36:12.20 Server Server process ID is 5080.
2007-12-18 19:36:12.20 Server Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2007-12-18 19:36:12.20 Server This instance of SQL Server last reported using a process ID of 1180 at 18/12/2007 19:12:20 (local) 18/12/2007 19:12:20 (UTC). This is an informational message only; no user action is required.
2007-12-18 19:36:12.20 Server Registry startup parameters:
2007-12-18 19:36:12.20 Server -d c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2007-12-18 19:36:12.20 Server -e c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2007-12-18 19:36:12.20 Server -l c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2007-12-18 19:36:12.20 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2007-12-18 19:36:12.20 Server Detected 2 CPUs. This is an informational message; no user action is required.
2007-12-18 19:36:12.40 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.
2007-12-18 19:36:12.42 Server Database Mirroring Transport is disabled in the endpoint configuration.
2007-12-18 19:36:12.43 spid4s Starting up database 'master'.
2007-12-18 19:36:12.50 spid4s Error: 9003, Severity: 20, State: 1.
2007-12-18 19:36:12.50 spid4s The log scan number (228:88:1) passed to log scan in database 'master' 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.
2007-12-18 19:36:12.50 spid4s Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
3
cs_AmK Messages postés 368 Date d'inscription jeudi 13 mars 2003 Statut Membre Dernière intervention 27 janvier 2010 1
20 déc. 2007 à 00:28
J'ai résolu le problème , en réinstallant !
0
Rejoignez-nous