MSSQLSERVER Service ... just gone

I just attempted to log into an application that uses
SQL. I received the error "Net Service
Configuration" ... "The specified service does not exist
as an installed service."
I'm shocked. Why would this service just disappear?It wouldn't. To ensure it hasn't logon locally to the SQL Server, control
panel, services, MSSQLServer.
I would imagine the error message relates to a different service.
--
HTH
Ryan Waight, MCDBA, MCSE
"Tom" <anonymous@.discussions.microsoft.com> wrote in message
news:0a4701c3b2ff$a8c87560$a101280a@.phx.gbl...
> I just attempted to log into an application that uses
> SQL. I received the error "Net Service
> Configuration" ... "The specified service does not exist
> as an installed service."
> I'm shocked. Why would this service just disappear?|||It wouldn't. Check the <SQL> dir for stuff in the LOG and INSTALL directories
for evidence on what might have happened.
> I just attempted to log into an application that uses
> SQL. I received the error "Net Service
> Configuration" ... "The specified service does not exist
> as an installed service."
> I'm shocked. Why would this service just disappear?
>
Neil Pike MVP/MCSE. Protech Computing Ltd
Reply here - no email
SQL FAQ (484 entries) see
http://forumsb.compuserve.com/gvforums/UK/default.asp?SRV=MSDevApps
(faqxxx.zip in lib 7)
or www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
or www.sqlserverfaq.com
or www.mssqlserver.com/faq

MSSQLSERVER is MIA

To start a named instance of SQL Server

On the Start menu, point to All Programs, point to

Microsoft SQL Server 2005, point to Configuration Tools, and then

click SQL Server Configuration Manager.

In SQL Server Configuration Manager, expand Services, and

then click SQL Server (MSSQLSERVER).

There is no MSSQLSERVER to click!!!!!!!!

If you open services.msc (services page), is MSSQLSERVER listed there? Do you have the appropriate WMI permissions? Try this article to see if it applies:

http://msdn2.microsoft.com/en-us/library/ms188690.aspx

Thanks,
Sam Lester (MSFT)

mssql8 AND mssql 2005

I have both 8 and 2005 installed on a windows 2003 server. However from a remote machine I can only see the 2005 instance. Is there a configuration I have missed or is this not possible?Are you using SQL Server 2005 Management Studio to connect to a remote database engine? If so, you may wanna try to select <Browse for more...> option from the Server Name dropdown list and then switch to the Network Servers tab. Let me know how you're getting along.|||I can see both instances on the Windows 2003 system and can connect to the v8 thru sql server management as you suggest. My issue is a remote machine with only 8's client cannot connect to the mssql v8 instance.|||Are you getting any error at all? Try to quickly create a .udl file on the remote machine to see if you could make and test a connection to the server.|||I get a server not found message.|||How did you name your 2000 and 2005 instances on the same box?|||2005 = server
other is server\server2003|||And server\server2003 is not visible from 2000 client, right?|||Yes. I wonder if I should name it something else maybe it doesn;t like that name. Maybe OldSQL?|||

Quote:

Originally Posted by kitspid

Yes. I wonder if I should name it something else maybe it doesn;t like that name. Maybe OldSQL?

Try to name it without slash. I doubt though it'll help. I once experienced a very funny problem with my replication whereby the distributor wouldn't connect to the subscriber. I had to enable Naming Pipes on the subscriber via the SQL config console to fix it. Just a thought.|||Tried the name pipes didn;t help. Don;t think I can rename it as the machine is called server which is where that comes from shoulf just be server2003 to connect. Going to move this db to a different machine and not worry about it anymore. Chalk it up to a 2005 quirk I think.|||Thanx for your help anyway.|||Good luck to you. Sorry couldn't help you better. Try to search in MSDN troubleshooting articles.|||I had to change the port for the mssql8 version to get it to work.