MS Sql Server User ID, Password and connection string

Hi;
I am making a software (.Net) which is going to connect a ms sql server but I cant conect yet :(.

1- I dont know what I have to type for user id (name)
2- What is my password, it has been long time that I hvae installed it but I dont need any password with Microsoft SQL Server Management Studio Express which has windows authentication option. My software can work via internet or network. So I need to know my user name and password. I am using oledbconnection. Do I need any password?
3- I visited www.connectionstrings.com already so I have the format of it.

Thanks very much for any help...you need to either use your windows account and use the example from connection strings dot com that uses windows auth or you need to go to SQL Server management studio to create a sql server login and password and you will need to give that account access to the specific database you are accessing.

man do the redskins suck.

MS SQL Server 2005 -- Cant not attach to AdventureWorks Database

I have MS SQL Server 2005 installed and when trying to connect to AdventureWorks DB

Downloaded AdventureWorksDB.msi file and when trying to attach recieve this error when running script ?

Msg 1813, Level 16, State 2, Line 1

Could not open new database 'AdventureWorks'. CREATE DATABASE is aborted.

Msg 602, Level 21, State 50, Line 1

Could not find row in sysindexes for database ID 8, object ID 1, index ID 1. Run DBCC CHECKTABLE on sysindexes.

Then tried to attach the DB and get this

TITLE: Microsoft SQL Server Management Studio

Attach database failed for Server 'JKIMBLE1'. (Microsoft.SqlServer.Smo)

ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

Could not find row in sysindexes for database ID 8, object ID 1, index ID 1. Run DBCC CHECKTABLE on sysindexes.
Could not open new database 'AdventureWorks'. CREATE DATABASE is aborted. (Microsoft SQL Server, Error: 602)

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

BUTTONS:

OK

Is there a difference between MS SQL Server 2005 and SQL Server 2005 Express Edition

I am having the same problem. I've done some research, trying to fix this.

This thing is just curious because a coworker successfully installed the AdventureWorks DB and our computers are almost identical, HW and SW.

Anyone?
|||

Are you a server admin on the box where you are trying to attach the database? Or a local admin on the box?

There is no difference in the file format between the various editions of SQL Server 2005. This sounds like a rights problem to me.

|||Fortunately I solved my problem. The thing with me was that I had MSSQL Server 2000 installed on my machine. And when I opened the SQL Server Management Studio I used to connect to the instance of 2000 and not 2005. (e.g. LOCALHOST, instead of LOCALHOST\SQLEXPRESS)

Such a stupid thing, but I never read about it anywhere else.

I guess my problem was that there's no compatibility from 2005 to 2000.

Hope this works for you as well JKimble.
|||Thanks for the info...!! I had exact same issue - I downloaded AdventureWorks database and got the same error when I tried to attach to LOCALHOST but it worked Ok when I changed to LOCALHOST\SQLEXPRESS... NB: the same occurs for AdventureWorksDW database...|||

SteveSatriani wrote:

Thanks for the info...!! I had exact same issue - I downloaded AdventureWorks database and got the same error when I tried to attach to LOCALHOST but it worked Ok when I changed to LOCALHOST\SQLEXPRESS... NB: the same occurs for AdventureWorksDW database...

Two things AdventureWorksDW DB will not work with Express because there is no BI management studio and I know it was not created to work with 2000. But the OLTP AdventureWorks DB comes in both 2000 and 2005. Hope this helps.

MS SQL Server 2005 -- Cant not attach to AdventureWorks Database

I have MS SQL Server 2005 installed and when trying to connect to AdventureWorks DB

Downloaded AdventureWorksDB.msi file and when trying to attach recieve this error when running script ?

Msg 1813, Level 16, State 2, Line 1

Could not open new database 'AdventureWorks'. CREATE DATABASE is aborted.

Msg 602, Level 21, State 50, Line 1

Could not find row in sysindexes for database ID 8, object ID 1, index ID 1. Run DBCC CHECKTABLE on sysindexes.

Then tried to attach the DB and get this

TITLE: Microsoft SQL Server Management Studio

Attach database failed for Server 'JKIMBLE1'. (Microsoft.SqlServer.Smo)

ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

Could not find row in sysindexes for database ID 8, object ID 1, index ID 1. Run DBCC CHECKTABLE on sysindexes.
Could not open new database 'AdventureWorks'. CREATE DATABASE is aborted. (Microsoft SQL Server, Error: 602)

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

BUTTONS:

OK

Is there a difference between MS SQL Server 2005 and SQL Server 2005 Express Edition

I am having the same problem. I've done some research, trying to fix this.

This thing is just curious because a coworker successfully installed the AdventureWorks DB and our computers are almost identical, HW and SW.

Anyone?
|||

Are you a server admin on the box where you are trying to attach the database? Or a local admin on the box?

There is no difference in the file format between the various editions of SQL Server 2005. This sounds like a rights problem to me.

|||Fortunately I solved my problem. The thing with me was that I had MSSQL Server 2000 installed on my machine. And when I opened the SQL Server Management Studio I used to connect to the instance of 2000 and not 2005. (e.g. LOCALHOST, instead of LOCALHOST\SQLEXPRESS)

Such a stupid thing, but I never read about it anywhere else.

I guess my problem was that there's no compatibility from 2005 to 2000.

Hope this works for you as well JKimble.
|||Thanks for the info...!! I had exact same issue - I downloaded AdventureWorks database and got the same error when I tried to attach to LOCALHOST but it worked Ok when I changed to LOCALHOST\SQLEXPRESS... NB: the same occurs for AdventureWorksDW database...|||

SteveSatriani wrote:

Thanks for the info...!! I had exact same issue - I downloaded AdventureWorks database and got the same error when I tried to attach to LOCALHOST but it worked Ok when I changed to LOCALHOST\SQLEXPRESS... NB: the same occurs for AdventureWorksDW database...

Two things AdventureWorksDW DB will not work with Express because there is no BI management studio and I know it was not created to work with 2000. But the OLTP AdventureWorks DB comes in both 2000 and 2005. Hope this helps.

MS SQL server 2005 - cant connect to server

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.

MS SQL server 2005 - cant connect to server

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.

MS SQL server 2005 - cant connect to server

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.sql

MS SQL Server 2000: Can Insert New Rows, but can't Update or Delete!!

I'm facing a strange problem here (SQL Server 2000).
I can Insert new rows from My ASP.NET 2.0 Pages but Can't Update or Delete.
usualy I test and build my web applications offline on my home workstation before I uppload them to my Server (Windows Server 2003 Standard), and I make sure that its error free.
The problem goes as follows:
1- I created a data grid that you can insert, delete and update and it worked fine when I tested it on my home computer.
2- When I updated the application to my server, I've noticed that I can Insert new columns to the database but When I try to update or delete the old columns, it doesn't allow me (so I have to use interprise manager to delete them from under- using same username and password!!!!).

I've never faced anything like this before, so please if anyone can give me any advice...

The problem only happened when I was using ASP.NET 2.0 Beta on my Home computer, and the full version on my server. so it was obvious that i need to install the same thing on both computers. but when I did I had to reconfigure my connection to accomodate the changes with the version. and now its working fine...

MS SQL Server 2000: Can Insert New Rows, but can't Update or Delete!!

I'm facing a strange problem here (SQL Server 2000).
I can Insert new rows from My ASP.NET 2.0 Pages but Can't Update or Delete.
usualy I test and build my web applications offline on my home workstation before I uppload them to my Server (Windows Server 2003 Standard), and I make sure that its error free.
The problem goes as follows:
1- I created a data grid that you can insert, delete and update and it worked fine when I tested it on my home computer.
2- When I updated the application to my server, I've noticed that I can Insert new columns to the database but When I try to update or delete the old columns, it doesn't allow me (so I have to use interprise manager to delete them from under- using same username and password!!!!).

I've never faced anything like this before, so please if anyone can give me any advice...

The problem only happened when I was using ASP.NET 2.0 Beta on my Home computer, and the full version on my server. so it was obvious that i need to install the same thing on both computers. but when I did I had to reconfigure my connection to accomodate the changes with the version. and now its working fine...

sql

MS SQL MSDE Quick Question About Databases

Hey,
Im using MSSQL MSDE with the ASP.NET WebMatrix Project to build databases, but i cant find where the database is stored on my hard drive. I am about to format and reinstall Windows and would like to backup these databases so that i can continue to work with them after i reinstall. Can anyone help me?

Thanks in advance, all help is appreciated :)

E.The quick and dirty answer is to look at C:\Inetpubs\wwwroot. That is where mine were stored. A safer, more complete approach is to simply use a Windows Explorer seach for "My Computer".|||I believe that the default installation location for msde data files is:

\\[yourserver]\c$\Program Files\Microsoft SQL Server\MSSQL$[yourserver]\Data

-Sam

MS SQL 6 yes 6

Does anyone know if the MS SQL 7 client can connect to a MSSQL 6 database?
We have a 6 running that can't be upgraded and now it's in need of some TLC.
Mike
It's been a while but i seem to remember. SQL 7 client can connect to SQL
6.5, but SQL 7 EnterPrise Manager can't control SQL 6.5 installs.
If you've got a spare client PC give it a try...
HTH. Ryan
"Mike" <Mike@.discussions.microsoft.com> wrote in message
news:1AAB45AD-9A72-49AD-A9A5-DC4A08BA69E9@.microsoft.com...
> Does anyone know if the MS SQL 7 client can connect to a MSSQL 6 database?
> We have a 6 running that can't be upgraded and now it's in need of some
> TLC.
> Mike
|||"Mike" <Mike@.discussions.microsoft.com> wrote in message
news:1AAB45AD-9A72-49AD-A9A5-DC4A08BA69E9@.microsoft.com...
> Does anyone know if the MS SQL 7 client can connect to a MSSQL 6 database?
> We have a 6 running that can't be upgraded and now it's in need of some
> TLC.
> Mike
I don't remeber or sure, but I don't think you can do it.
You may be stuck with isql and/or osql.
Rick Sawtell
MCT, MCSD, MCDBA
|||Correct. The 7.0 QA and the MDAC that came with 7.0 can connect downwards. But EM 7.0 can only
connect to 7.0 instance.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Ryan" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:utaUTY6FGHA.2652@.tk2msftngp13.phx.gbl...
> It's been a while but i seem to remember. SQL 7 client can connect to SQL 6.5, but SQL 7
> EnterPrise Manager can't control SQL 6.5 installs.
> If you've got a spare client PC give it a try...
> --
> HTH. Ryan
> "Mike" <Mike@.discussions.microsoft.com> wrote in message
> news:1AAB45AD-9A72-49AD-A9A5-DC4A08BA69E9@.microsoft.com...
>
|||Thanks all. Unfortunately this application was purchased many years ago and
is only validated on SQL 6.5. The company has since gone out of business. I
may have to write a new app.
Thanks
Mike
"Rick Sawtell" wrote:

> "Mike" <Mike@.discussions.microsoft.com> wrote in message
> news:1AAB45AD-9A72-49AD-A9A5-DC4A08BA69E9@.microsoft.com...
> I don't remeber or sure, but I don't think you can do it.
> You may be stuck with isql and/or osql.
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>