cant log in to SSMS

  • Hi everyone,

    Evreything worked fine till i tried to make changes using:SQL Server Configuration manager and SQL Server Surface Area Configuration (well, in SSIS i couldnt add connection..). Now i cannot log in to my SQL Server 2005. In both configuration managers the: Database engine service is stopped ! When I click "start" I get an error message that says:"An error occured while performing this operation".

    Is there as way to get out of this ?!

    Thanks

  • What exactly did you change?

  • ps-490891 (2/7/2010)


    Hi everyone,

    Evreything worked fine till i tried to make changes using:SQL Server Configuration manager and SQL Server Surface Area Configuration (well, in SSIS i couldnt add connection..). Now i cannot log in to my SQL Server 2005. In both configuration managers the: Database engine service is stopped ! When I click "start" I get an error message that says:"An error occured while performing this operation".

    Is there as way to get out of this ?!

    Thanks

    Do you remember what have you changed? Can you see any errors in your application even logs?? What error do you exactly encounter??

  • I assume you have either changed the service account to an account that doesnt exist, or you have the password wrong. Like the others said check the error logs to find out why the service wont work. Also try putting it to local service just to make sure the service is still working ok before changing it back to the domain account your using.

  • Hi,

    This is the present configuration:

    "Surface Area Configuration Services and connections"

    "Database Engine>Service"

    "Service Name":MSSQL$MYSERVER

    "Display name": Sql Server(MYSERVER)

    "Description": Provides storage, processing and controlled

    access of data and rapid transaction processing.

    "Startup type": Automatic

    "Service status": stopped

    When i click: "Start" I get the following error message:

    "An error occured while performing this operation"

    "Remote connections"

    "Local and remote connections" selected and "Using both tcp/ip and

    named pipes" selected.

    "Analysis services->service"

    "Service name": MSOLAP$MYSERVER

    "Display name": SQL Server Analysis Services (MYSERVER)

    "Description": Supplies online analytical processing (OLAP)

    and data mining functionality for business intelligence applications.

    "Startup type": Automatic

    "Service status": Running

    "Remote connections"

    "Local and remote connections" selected

    "Reporting services->service"

    "Service name": ReportServer$MYSERVER

    "Display name": SQL Server Reporting Services (MYSERVER)

    "Description": Manages, executes, renders, schedules and delivers reports.

    "Startup type": Automatic

    "Service status": stopped. When i click "Start" i get:

    An error occured while perfo9rming thuis operation

    "SQL Server service agent->service"

    "Service name": SQLAgent$MYSERVER

    "Display name": SQL Server Agent(MYSERVER)

    "Description": Executes jobs, monitors SQL Server, and

    fires alerts, and allows automation of some administrative tasks.

    "Startup type": Automatic

    "Service status": stopped. When i click "Start" i get:

    An error occured while perfo9rming thuis operation

    "Full text search->service"

    "Service name": MSFTESQL$MYSERVER

    "Display name": SQL Server FullText Search(MYSERVER)

    "Description": Quickly creates full-text indexes on content and

    properties of structured and semi-structured data to allow fast linguistic

    "Startup type": Automatic

    "Service status": running

    "Integration service"

    "Service name": MsDtsServer

    "Display name": SQL Server Integration Services

    "Description": Provides management support for

    SSIS package storage and execution.

    "Startup type": Automatic

    "Service status": running

    SQL Server browser" is running..

    "Surface Area Configuration for features" All "enable" options selected

    "SQL Server configuration manager"

    "SQL Server 2005 services"

    SQL Server, reporting and Agent are stopped

    "SQL Server 2005 network configuration"

    "Protocols for MYSERVER: all 4 protocols are enabled.

    "SQL native client configuration"

    "Aliases": no aliases

    Is there a reason, viewing the above configuration, no deprive me from logging into me server ?

    Thanks

    ps

    Where can i view the error log ?

  • Hi,

    Could you tell me please which event log i should look and where to find it ?

    Thanks

  • Look for the SQL Server Error Log .. You would find it in the MSSQL\LOG.. Find a file named ERRORLOG (No extension will be there for the file)


    Bru Medishetty

    Blog -- LearnSQLWithBru

    Join on Facebook Page Facebook.comLearnSQLWithBru

    Twitter -- BruMedishetty

  • Hi Bru,

    That error log i know, but it is so meaningless to me..

    Can the following be helpful ?

    2010-02-08 22:03:13.07 Server (c) 2005 Microsoft Corporation.

    2010-02-08 22:03:13.07 Server All rights reserved.

    2010-02-08 22:03:13.07 Server Server process ID is 1856.

    2010-02-08 22:03:13.07 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.

    2010-02-08 22:03:13.07 Server This instance of SQL Server last reported using a process ID of 916 at 2/8/2010 9:53:20 PM (local) 2/8/2010 7:53:20 PM (UTC). This is an informational message only; no user action is required.

    2010-02-08 22:03:13.07 Server Registry startup parameters:

    2010-02-08 22:03:13.07 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf

    2010-02-08 22:03:13.07 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG

    2010-02-08 22:03:13.07 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf

    2010-02-08 22:03:13.09 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.

    2010-02-08 22:03:13.09 Server Detected 2 CPUs. This is an informational message; no user action is required.

    2010-02-08 22:03:13.21 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.

    2010-02-08 22:03:13.21 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.

    2010-02-08 22:03:13.23 Server The Microsoft Distributed Transaction Coordinator (MS DTC) service could not be contacted. If you would like distributed transaction functionality, please start this service.

    2010-02-08 22:03:13.23 Server Database Mirroring Transport is disabled in the endpoint configuration.

    2010-02-08 22:03:13.23 spid5s Starting up database 'master'.

    2010-02-08 22:03:13.31 spid5s SQL Trace ID 1 was started by login "sa".

    2010-02-08 22:03:13.34 spid5s Starting up database 'mssqlsystemresource'.

    2010-02-08 22:03:13.51 spid5s Server name is 'YOSSI\YOSQL'. This is an informational message only. No user action is required.

    2010-02-08 22:03:13.51 spid9s Starting up database 'model'.

    2010-02-08 22:03:13.54 spid9s Clearing tempdb database.

    2010-02-08 22:03:13.71 Server A self-generated certificate was successfully loaded for encryption.

    2010-02-08 22:03:13.73 Server Error: 17182, Severity: 16, State: 1.

    2010-02-08 22:03:13.73 Server TDSSNIClient initialization failed with error 0x7e, status code 0x60.

    2010-02-08 22:03:13.73 Server Error: 17182, Severity: 16, State: 1.

    2010-02-08 22:03:13.73 Server TDSSNIClient initialization failed with error 0x7e, status code 0x1.

    2010-02-08 22:03:13.73 Server Error: 17826, Severity: 18, State: 3.

    2010-02-08 22:03:13.73 Server Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.

    2010-02-08 22:03:13.73 Server Error: 17120, Severity: 16, State: 1.

    2010-02-08 22:03:13.73 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

    Thanks

  • TDSSNIClient initialization failed with error 0x7e, status code 0x60.

    2010-02-08 22:03:13.73 Server Error: 17182, Severity: 16, State: 1.

    2010-02-08 22:03:13.73 Server TDSSNIClient initialization failed with error 0x7e, status code 0x1.

    2010-02-08 22:03:13.73 Server Error: 17826, Severity: 18, State: 3.

    2010-02-08 22:03:13.73 Server Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.

    Have you looked for this error message in Google ? I guess that is the reason for the SQL Server not able to start...


    Bru Medishetty

    Blog -- LearnSQLWithBru

    Join on Facebook Page Facebook.comLearnSQLWithBru

    Twitter -- BruMedishetty

  • Thank you so much Bru ! you are my savior (google comes next to you..).

    I finally logged into the server without reinstalling it.

    Thanks again.

  • ps-490891 (2/9/2010)


    Thank you so much Bru ! you are my savior (google comes next to you..).

    I finally logged into the server without reinstalling it.

    Thanks again.

    what exactly did you do to get over that error message. May help others in the same position

  • I did what Bru Medishetty told me to do:

    I searched : "TDSSNIClient initialization failed with error 0x7e, status code 0x60." (The error in my ERRORLEVEL file) in Google and found the same question asked in msdn forum where the one who asked was instructed to put the "via" protocol into "disable" status. I opened: SQL Server Configuration tool, "Protocols for MYSERVER" and "Client protocols" and from right click menu selected "disable" status for both the "via" protocols. I thought i was the only one not to know this so i didnt think i should explain anything... Sorry...

  • ps-490891 (2/9/2010)


    Thank you so much Bru ! you are my savior (google comes next to you..).

    I finally logged into the server without reinstalling it.

    Thanks again.

    You are welcome !..

    Glad it could help, and yeah, the VIA protocol should not be enabled on systems specific to them. I did see many times people enable all the protocols and have big trouble in starting SQL Server..


    Bru Medishetty

    Blog -- LearnSQLWithBru

    Join on Facebook Page Facebook.comLearnSQLWithBru

    Twitter -- BruMedishetty

Viewing 13 posts - 1 through 12 (of 12 total)

You must be logged in to reply to this topic. Login to reply