login failure for SSMS

  • TITLE: Connect to Server

    ------------------------------

    I am not able to login to the SSMS, while I am logging I got this error please help me how to troubleshoot this error..

    Cannot connect to LAASYA.

    ------------------------------

    ADDITIONAL INFORMATION:

    A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)

    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476

    ------------------------------

    The system cannot find the file specified

    ------------------------------

    BUTTONS:

    OK

    ------------------------------

  • Is the instance name correct? Is SQL recently installed?

    ---------------------------------------------------
    "Thare are only 10 types of people in the world:
    Those who understand binary, and those who don't."

  • yes instance name and server name correct and it was recently installed and I am using daily ssms but today after upgrading os to windows 8.1 this login error is coming . I think there is an error in admin permission how to solve this..

  • Can you ping the SQL server from the command prompt?

    Can you connect using sqlcmd? From a command prompt like this:

    sqlcmd -S [server name] -E

    The -E is integrated security

  • In services.msc I clicked on sql server sart it is running ,again it is going to terminate and the error in error log is as fallows....

    2014-06-26 07:05:50.44 Server Microsoft SQL Server 2012 (SP1) - 11.0.3128.0 (Intel X86)

    Dec 28 2012 19:06:41

    Copyright (c) Microsoft Corporation

    Developer Edition on Windows NT 6.2 <X86> (Build 9200: )

    2014-06-26 07:05:50.44 Server (c) Microsoft Corporation.

    2014-06-26 07:05:50.44 Server All rights reserved.

    2014-06-26 07:05:50.44 Server Server process ID is 2616.

    2014-06-26 07:05:50.44 Server System Manufacturer: 'System manufacturer', System Model: 'System Product Name'.

    2014-06-26 07:05:50.44 Server Authentication mode is MIXED.

    2014-06-26 07:05:50.44 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG'.

    2014-06-26 07:05:50.44 Server The service account is 'WORKGROUP\LAASYA$'. This is an informational message; no user action is required.

    2014-06-26 07:05:50.44 Server Registry startup parameters:

    -d C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\master.mdf

    -e C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG

    -l C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\mastlog.ldf

    2014-06-26 07:05:50.44 Server Command Line Startup Parameters:

    -s "MSSQLSERVER"

    2014-06-26 07:05:50.65 Server SQL Server detected 1 sockets with 2 cores per socket and 2 logical processors per socket, 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational message; no user action is required.

    2014-06-26 07:05:50.65 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.

    2014-06-26 07:05:50.65 Server Detected 1919 MB of RAM. This is an informational message; no user action is required.

    2014-06-26 07:05:50.65 Server Using locked pages in the memory manager.

    2014-06-26 07:05:50.71 Server This instance of SQL Server last reported using a process ID of 4016 at 26-06-2014 07:05:48 (local) 26-06-2014 01:35:48 (UTC). This is an informational message only; no user action is required.

    2014-06-26 07:05:50.71 Server 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.

    2014-06-26 07:05:50.71 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.

    2014-06-26 07:05:50.72 Server Software Usage Metrics is disabled.

    2014-06-26 07:05:50.73 spid7s Starting up database 'master'.

    2014-06-26 07:05:50.78 spid7s 25 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.

    2014-06-26 07:05:50.79 spid7s 0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.

    2014-06-26 07:05:50.83 Server CLR version v4.0.30319 loaded.

    2014-06-26 07:05:50.86 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework\v4.0.30319\.

    2014-06-26 07:05:50.87 spid7s Resource governor reconfiguration succeeded.

    2014-06-26 07:05:50.87 spid7s SQL Server Audit is starting the audits. This is an informational message. No user action is required.

    2014-06-26 07:05:50.87 spid7s SQL Server Audit has started the audits. This is an informational message. No user action is required.

    2014-06-26 07:05:50.90 spid7s SQL Trace ID 1 was started by login "sa".

    2014-06-26 07:05:50.90 spid7s Server name is 'LAASYA'. This is an informational message only. No user action is required.

    2014-06-26 07:05:51.00 spid13s A self-generated certificate was successfully loaded for encryption.

    2014-06-26 07:05:51.00 spid13s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].

    2014-06-26 07:05:51.00 spid13s Server local connection provider is ready to accept connection on [ \\.\pipe\sql\query ].

    2014-06-26 07:05:51.00 Server Server is listening on [ ::1 <ipv6> 1434].

    2014-06-26 07:05:51.00 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].

    2014-06-26 07:05:51.00 Server Dedicated admin connection support was established for listening locally on port 1434.

    2014-06-26 07:05:51.01 spid13s SQL Server is now ready for client connections. This is an informational message; no user action is required.

    2014-06-26 07:05:51.01 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.

    2014-06-26 07:05:51.01 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/LAASYA ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.

    2014-06-26 07:05:51.95 spid14s A new instance of the full-text filter daemon host process has been successfully started.

    2014-06-26 07:05:51.99 spid9s Starting up database 'mssqlsystemresource'.

    2014-06-26 07:05:52.00 spid17s Starting up database 'msdb'.

    2014-06-26 07:05:52.00 spid18s Starting up database 'ReportServer'.

    2014-06-26 07:05:52.00 spid19s Starting up database 'ReportServerTempDB'.

    2014-06-26 07:05:52.00 spid20s Starting up database 'raghu'.

    2014-06-26 07:05:52.00 spid21s Starting up database 'AdventureWorks2012'.

    2014-06-26 07:05:52.00 spid22s Starting up database 'model2'.

    2014-06-26 07:05:52.09 spid9s The resource database build version is 11.00.3000. This is an informational message only. No user action is required.

    2014-06-26 07:05:52.55 spid19s 1 transactions rolled forward in database 'ReportServerTempDB' (6:0). This is an informational message only. No user action is required.

    2014-06-26 07:05:52.62 spid22s 6 transactions rolled forward in database 'model2' (9:0). This is an informational message only. No user action is required.

    2014-06-26 07:05:52.82 spid7s 0 transactions rolled back in database 'ReportServerTempDB' (6:0). This is an informational message only. No user action is required.

    2014-06-26 07:05:52.93 spid7s 0 transactions rolled back in database 'model2' (9:0). This is an informational message only. No user action is required.

    2014-06-26 07:05:53.22 spid9s Starting up database 'model'.

    2014-06-26 07:05:53.33 spid9s The database 'model' is marked RESTORING and is in a state that does not allow recovery to be run.

    2014-06-26 07:05:53.33 spid9s Error: 927, Severity: 14, State: 2.

    2014-06-26 07:05:53.33 spid9s Database 'model' cannot be opened. It is in the middle of a restore.

    2014-06-26 07:05:53.33 spid9s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

    2014-06-26 07:05:53.57 spid18s 1 transactions rolled forward in database 'ReportServer' (5:0). This is an informational message only. No user action is required.

    2014-06-26 07:05:53.86 spid7s 0 transactions rolled back in database 'ReportServer' (5:0). This is an informational message only. No user action is required.

    could you help me how to solve this error...

  • Did you follow Jack Corbett's suggestion?

  • Your model database is corrupt so the SQL server instance can't start. You need to rebuild the model database. If you don't have good backups of master, model, nad msdb then you'll have to re-attach user databases, make any changes to model configuration that you previously had made, and recreate any jobs, operators, and alerts that you had previously. You need to do the rebuild to get SQL Server up and running so you can then restore any system database backups you may have. You need to make sure you are doing the rebuild with 2012 SP1 since that is what you had.

Viewing 7 posts - 1 through 6 (of 6 total)

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