Hi everybody, please help me!!! I just installed MS SQL 2005, but somehow I cant connect to the server wich is on my local computer, or BD engine to be exact, because other services work fine(like Analysis service). I get the following error message, can anyone please help me resolve this problem:
An Error occured while performing this operation (Surface Area Configuration for Services and Connections - localhost)
=============================================
An Error occured while performing this operation (SQLSAC)
-
Program Location:
at Microsoft.SqlSac.MainPanel.UserControlService.ActOnService(ServiceAction action)
Saaniok,
Did you ever get the answer to your problem? I am having the same problem. I cannot start the SQL 2005. Please help if you have the answer.
Regards,
Carlos
|||is the sqlserver service started. do a 'net start' and see if your sqlserver instance is started. also, can you connect to your instance via sqlcmd/sqlwb?|||Hi, thanks for the answer. I tried starting the SQL service, but when I try to get it started, it gives me an error message at the end. Any ideas? How can I connect via sqlcmd/sqlwb?|||Have an look in the eventlog to see what errors are raised when you try and start sql server|||As Simon said, the event log might give some clues. Also, try taking a look at the sql log - typically found under C:\Program Files\Microsoft SQL Server\MSSQL\LOG\ERRORLOG (default instance).
sqlcmd and sqlwb are client tools/utilities. They're only good if the service is started.
|||Thanks the answers. I have the log below. Any suggestions?
2006-09-22 07:48:15.09 Server (c) 2005 Microsoft Corporation.
2006-09-22 07:48:15.09 Server All rights reserved.
2006-09-22 07:48:15.09 Server Server process ID is 568.
2006-09-22 07:48:15.09 Server Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2006-09-22 07:48:15.09 Server This instance of SQL Server last reported using a process ID of 508 at 9/22/2006 7:43:02 AM (local) 9/22/2006 11:43:02 AM (UTC). This is an informational message only; no user action is required.
2006-09-22 07:48:15.09 Server Registry startup parameters:
2006-09-22 07:48:15.09 Server -d c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2006-09-22 07:48:15.09 Server -e c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2006-09-22 07:48:15.09 Server -l c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2006-09-22 07:48:15.15 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2006-09-22 07:48:15.15 Server Detected 2 CPUs. This is an informational message; no user action is required.
2006-09-22 07:48:16.23 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.
2006-09-22 07:48:16.32 Server Database Mirroring Transport is disabled in the endpoint configuration.
2006-09-22 07:48:16.39 spid5s Starting up database 'master'.
2006-09-22 07:48:16.42 spid5s Error: 17207, Severity: 16, State: 1.
2006-09-22 07:48:16.42 spid5s FCB::Open: Operating system error 5(Access is denied.) occurred while creating or opening file 'c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf'. Diagnose and correct the operating system error, and retry the operation.
2006-09-22 07:48:16.42 spid5s Error: 17204, Severity: 16, State: 1.
2006-09-22 07:48:16.42 spid5s FCB::Open failed: Could not open file c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf for file number 1. OS error: 5(Access is denied.).
2006-09-22 07:48:16.42 spid5s Error: 5120, Severity: 16, State: 101.
2006-09-22 07:48:16.42 spid5s Unable to open the physical file "c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf". Operating system error 5: "5(Access is denied.)".
2006-09-22 07:48:16.45 spid5s Error: 17207, Severity: 16, State: 1.
2006-09-22 07:48:16.45 spid5s FCB::Open: Operating system error 5(Access is denied.) occurred while creating or opening file 'c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf'. Diagnose and correct the operating system error, and retry the operation.
2006-09-22 07:48:16.45 spid5s Error: 17204, Severity: 16, State: 1.
2006-09-22 07:48:16.45 spid5s FCB::Open failed: Could not open file c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf for file number 2. OS error: 5(Access is denied.).
2006-09-22 07:48:16.45 spid5s Error: 5120, Severity: 16, State: 101.
2006-09-22 07:48:16.45 spid5s Unable to open the physical file "c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf". Operating system error 5: "5(Access is denied.)".
ocol transport is disabled or not configured.
2006-09-16 20:21:47.51 spid11s Service Broker manager has started.
2006-09-16 22:47:08.28 Server SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.
2006-09-16 22:47:21.45 spid11s Service Broker manager has shut down.
2006-09-16 22:47:21.76 spid11s Error: 17054, Severity: 16, State: 1.
2006-09-16 22:47:21.76 spid11s The current event was not reported to the Windows Events log. Operating system error = 1717(The interface is unknown.). You may need to clear the Windows Events log if it is full.
2006-09-16 22:47:23.23 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
The SQL Server Service can't access the systems database files required for it to operate.
FCB::Open: Operating system error 5(Access is denied.) occurred while creating or opening file 'c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf'. Diagnose and correct the operating system error, and retry the operation.
Have you changed the service account. If so did you do it throught the configuration manager. This ensures that the account has access to the files.
If you change it again using the configuration manager the account should have the correct access permissions to the folders and registry and the service should start
|||Simon,
No, I have not changed the service account. I don't even know how to. However, I am remembering now that I a few days after I installed VS Express, I think I needed to run the Windows XP CD again to repair (or to avoid doubts about a Windows behavior) Windows. So, I am guessing that something happened to the original VS Express Setup. I am going to run the VS Express setup install again on repair mode just make sure I did not mess something up by runnin the XP setup.
Does that make sense?
|||I had the same error as one of the posts above and couldn't get any of the services to start.
ERRORLOG
2007-05-24 08:43:31.52 Server Error: 17054, Severity: 16, State: 1.2007-05-24 08:43:31.52 Server The current event was not reported to the Windows Events log. Operating system error = 1717(The interface is unknown.). You may need to clear the Windows Events log if it is full.
2007-05-24 08:43:32.36 spid12s Service Broker manager has shut down.
2007-05-24 08:43:33.77 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
I found out why!
I recently changed my password for my account which is specified as the server login account. You have to update your password within the service properties of the MSSQLSERVER service. During install I think the default is to use a local account to run the service.
Go to your configuration manager and right click on the MSSQLSERVER service and go to properties, then under the "Log On" tab it will probably have the "this account" radio checked with a domain login account specified along with the password, change it here. If you have the service running under a built-in account and you recently changed that password you would have to change that instead if it doesn't update.
|||If you launch Sql server configuration manager, right click on the sqlserver service and change the startup account to LocalSystem. This should definitely allow you to startup sqlserver.|||You are entirely correct, I think I was confused or something when I mentioned changing password for a built-in account (thinking of database specific logins like SA). Depending on setup running the services using a built-in account should work and "Local System" sounds like a safe default. For a network or otherwise accessible server you might want to read up on or test out using built-in accounts "Network Service" or "Local Service". Maybe there are more built-in accounts based on your version or setup. If anybody knows a good link for the built-in account setup vs. using a windows account for the server startup please post it.
No comments:
Post a Comment