Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Configuration Manager; nothing under SQL Server Services Expand / Collapse
Author
Message
Posted Tuesday, July 02, 2013 4:58 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Today @ 8:31 AM
Points: 292, Visits: 1,141
Honestly, I give up. I can't connect to this database as sa ('a network-related or instance-specific error occurred error 40 [etc.]') so I open up Configuration Manager, click on SQL Server Services, and... it's completely empty (see attached).

Why would this happen?

I'm connecting via remote desktop, and I'm an administrator on that machine (Windows Server 2008 R2). I've tried Google. The SQL Server service must be up and running because people are using that database right now.

As before if you've read any of my posts, I'm fairly new here, everybody else has left and I know nothing about how this machine was set up. This job sucks. Any pointers would be gratefully received! Thanks.



  Post Attachments 
ConfigurationManagerScreeshot.docx (15 views, 31.80 KB)
Post #1469391
Posted Tuesday, July 02, 2013 5:28 AM
Say Hey Kid

Say Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey Kid

Group: General Forum Members
Last Login: Today @ 8:05 AM
Points: 681, Visits: 1,338
The SQL Server service must be up and running because people are using that database right now.


Just because people are connecting to a db does not mean that the db instance is where you think it is. If people are connecting to a database that you are trying to maintain/troubleshoot through an application you need to find where the connection string in the application is. It should tell you the instance name where the database is located.

It is also possible that SQL Server is installed on the server you are trying to access yet you are just not seeing the services in SQL Server Configuration Manager. For example in your screenshot you are running SQL Server Configuration Manager that is from SQL Server 2008/2008 R2. If a newer instance of SQL Server is installed, like SQL Server 2012 it will not be able to see those newer services. Go to Control Panel > Services and see if any SQL Server services are listed.


Joie Andrew
"Since 1982"
Post #1469410
Posted Tuesday, July 02, 2013 6:56 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Today @ 8:31 AM
Points: 292, Visits: 1,141
Thanks for the reply. There are no newer instances. The service is running, although it took a while to find because it was given a very unusual name for some reason.

Is there anything I can do to enable me to see the missing services in Configuration Manager?
Post #1469463
Posted Tuesday, July 02, 2013 9:06 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Saturday, April 12, 2014 1:20 PM
Points: 86, Visits: 674
Unusual name? That raises a red flag.

Go to Start > Run > Services.msc

and post the full name of the service running SQL


Another option... if you are sure you have the correct box, you should be able to open Command Prompt and use sqlcmd -E
thanks
Post #1469590
Posted Wednesday, July 03, 2013 2:50 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Today @ 8:31 AM
Points: 292, Visits: 1,141
Thanks for the help!

Ok, it's called [Application name] 5.5 Server - [Application name], and under log on as it has .\[a username related to application name]

sqlcmd -E returns:
"Named Pipes Provider: Could not open a connection to SQL Server [2]. Sqlcmd: Error: Miscrosft SQL Server Native Client 10.0 : A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections."


Ironically that's exactly what I can't do . I'm just going to Google it.

Exactly the same thing happens whether I'm logged in as me (local administrator) or that username mentioned above.
Post #1469915
Posted Wednesday, July 03, 2013 2:59 AM
Say Hey Kid

Say Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey Kid

Group: General Forum Members
Last Login: Today @ 8:05 AM
Points: 681, Visits: 1,338
There is something else you can try. Can you go to the directory that the SQL binaries are installed (normally something like c:\program files\microsoft sql server\MSSQL10_50.<instancename>\MSSQL), go to the log directory and there should be a series of files labelled ERRORLOG*. Can you post a copy of the ERRORLOG file (the one with no number at the end)? If it has the startup info we should be able to tell you how to connect.

Joie Andrew
"Since 1982"
Post #1469920
Posted Wednesday, July 03, 2013 3:07 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Today @ 8:31 AM
Points: 292, Visits: 1,141
I can't find anything like that at all; the menu structure looks very strange. I think I might have to get the contractor for the application in question to have a look at it when he's next in in a couple of weeks. It's a complete shambles.

Thanks for the help, everybody. If I'd had any idea what I'd be taking on I wouldn't have touched this job with a bargepole .
Post #1469925
Posted Wednesday, July 03, 2013 5:43 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Saturday, April 12, 2014 1:20 PM
Points: 86, Visits: 674
If you can't see a service called "SQL server..." something, it means you may not even have SQL installed there anymore... Or you are using express version.
Last shot... You mention that is running under ./username. That means that someone created a local username on that server and its running those services. Do you have the password? If you do, you can logging to windows and try again connecting using ssms.
Post #1470005
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse