MS SQL Server 2005 - SQL Agent problems

I am currently running SQL Server 2005 on a stand alone (not a domain
member) Windows Server 2003, this server was installed during setup
using local user accounts as service accounts.
As far as I recall at the time everything, including the SQL agent
functioned normally. At this time, the server itself still seems to
be running fine, however the SQL Agent service will not start.
I can not be sure as up until recently we haven't really been using
the SQL Agent, however I believe the problem would have started around
the time that service pack 1 was installed.
The following is the event log error message that is generated
everytime the SQL Agent service attempts to start:
###
Event Type: Error
Event Source: SQLSERVERAGENT
Event Category: Service Control
Event ID: 103
Date: 7/24/2007
Time: 3:55:22 PM
User: N/A
Computer: DBSERVER
Description:
SQLServerAgent could not be started (reason: SQLServerAgent must be
able to connect to SQLServer as SysAdmin, but '(Unknown)' is not a
member of the SysAdmin role).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
###
Please note that where the error message should indicate the name of
the service account (svc_sqlagent) it instead indicates "Unknown".
Also that SQL Server database engine running under the its own local
user service account (svc_sqlserver) works fine.
I have since tried recreating and reassigning a new local user service
account for the SQL Agent using two methods,
the first, the official approved method using the SQL Server
Configuration Manager:
results in the simple and vague error dialog box:
Title bar: WMI Provider Error
Error message: The process terminated unexpectedly. [0x8007042b]
The above error however produces no entries in any of the event logs.
If I start with a plain vanilla local user account, the config manager
does manage to setup some but not all of the special permissions/group
memberships necessary for the account to operate, before the error
occurs, but it does not appear to be consistent in how far it gets in
applying the correct parameters to the account.
the second method I used, was the manual service account setup from
knowledge base article Q283811.
this allows me to get the account setup, and the service set to log in
as the account, but when the service attempts to start, it fails, with
the same event log entry shown above.
also while trying to resolve all this SP2 became available, I first
tried to resolve this issue before installing SP2 however when I was
unable to, I went ahead and applied SP2 in the hopes that it might
help, as near as I can tell it has no effect, I attempted all the
previous methods and got the same results.
Any help with this would be greatly appreciated.
Thank you,
Jeffrey WilliamsDid you verify that the local account that you want to use for running SQL
Agent service is a member of the Local Users & Groups in the Group
'Administrators'?
and that the SQL Server login has the server role of 'sysadmin'
If the local user has that security it should be able to run SQL Agent
~Ellen
Thank you for sharing your knowledge
"sailorfej" wrote:

> I am currently running SQL Server 2005 on a stand alone (not a domain
> member) Windows Server 2003, this server was installed during setup
> using local user accounts as service accounts.
> As far as I recall at the time everything, including the SQL agent
> functioned normally. At this time, the server itself still seems to
> be running fine, however the SQL Agent service will not start.
> I can not be sure as up until recently we haven't really been using
> the SQL Agent, however I believe the problem would have started around
> the time that service pack 1 was installed.
> The following is the event log error message that is generated
> everytime the SQL Agent service attempts to start:
> ###
> Event Type: Error
> Event Source: SQLSERVERAGENT
> Event Category: Service Control
> Event ID: 103
> Date: 7/24/2007
> Time: 3:55:22 PM
> User: N/A
> Computer: DBSERVER
> Description:
> SQLServerAgent could not be started (reason: SQLServerAgent must be
> able to connect to SQLServer as SysAdmin, but '(Unknown)' is not a
> member of the SysAdmin role).
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> ###
> Please note that where the error message should indicate the name of
> the service account (svc_sqlagent) it instead indicates "Unknown".
> Also that SQL Server database engine running under the its own local
> user service account (svc_sqlserver) works fine.
> I have since tried recreating and reassigning a new local user service
> account for the SQL Agent using two methods,
> the first, the official approved method using the SQL Server
> Configuration Manager:
> results in the simple and vague error dialog box:
> Title bar: WMI Provider Error
> Error message: The process terminated unexpectedly. [0x8007042b]
> The above error however produces no entries in any of the event logs.
> If I start with a plain vanilla local user account, the config manager
> does manage to setup some but not all of the special permissions/group
> memberships necessary for the account to operate, before the error
> occurs, but it does not appear to be consistent in how far it gets in
> applying the correct parameters to the account.
> the second method I used, was the manual service account setup from
> knowledge base article Q283811.
> this allows me to get the account setup, and the service set to log in
> as the account, but when the service attempts to start, it fails, with
> the same event log entry shown above.
> also while trying to resolve all this SP2 became available, I first
> tried to resolve this issue before installing SP2 however when I was
> unable to, I went ahead and applied SP2 in the hopes that it might
> help, as near as I can tell it has no effect, I attempted all the
> previous methods and got the same results.
> Any help with this would be greatly appreciated.
> Thank you,
> Jeffrey Williams
>|||On Aug 15, 2:56 pm, Ellen <DBAEl...@.community.nospam> wrote:[vbcol=seagreen]
> Did you verify that the local account that you want to use for running SQL
> Agent service is a member of the Local Users & Groups in the Group
> 'Administrators'?
> and that the SQL Server login has the server role of 'sysadmin'
> If the local user has that security it should be able to run SQL Agent
> ~Ellen
> --
> Thank you for sharing your knowledge
> "sailorfej" wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
Hi Ellen,
Yes, I did. As I described in my previous message, both methods I
used in setting up the service account resulted in the correct
permissions for the account, in addition, the original account setup
carried out during the SQL Servers installation setup the service
account with the correct permissions, and the service didn't start to
have problems until later.
I believe the there is some break in the interface between the WMI/NT
Auth components, and the SQL Server Auth mechanism, this is why I made
sure to include the info for the WMI error dialog, and pointed that in
the event log error message the service account is not correctly
identified, but is instead listed as "unknown". If this were a
standard permissions issue, the account would have been correctly
identified as "svc_sqlagent".
If you have any other ideas, I would very much appreciate hearing
them.
Thanks,
Jeff

MS SQL Server 2005 - SQL Agent problems

I am currently running SQL Server 2005 on a stand alone (not a domain
member) Windows Server 2003, this server was installed during setup
using local user accounts as service accounts.
As far as I recall at the time everything, including the SQL agent
functioned normally. At this time, the server itself still seems to
be running fine, however the SQL Agent service will not start.
I can not be sure as up until recently we haven't really been using
the SQL Agent, however I believe the problem would have started around
the time that service pack 1 was installed.
The following is the event log error message that is generated
everytime the SQL Agent service attempts to start:
###
Event Type: Error
Event Source: SQLSERVERAGENT
Event Category: Service Control
Event ID: 103
Date: 7/24/2007
Time: 3:55:22 PM
User: N/A
Computer: DBSERVER
Description:
SQLServerAgent could not be started (reason: SQLServerAgent must be
able to connect to SQLServer as SysAdmin, but '(Unknown)' is not a
member of the SysAdmin role).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
###
Please note that where the error message should indicate the name of
the service account (svc_sqlagent) it instead indicates "Unknown".
Also that SQL Server database engine running under the its own local
user service account (svc_sqlserver) works fine.
I have since tried recreating and reassigning a new local user service
account for the SQL Agent using two methods,
the first, the official approved method using the SQL Server
Configuration Manager:
results in the simple and vague error dialog box:
Title bar: WMI Provider Error
Error message: The process terminated unexpectedly. [0x8007042b]
The above error however produces no entries in any of the event logs.
If I start with a plain vanilla local user account, the config manager
does manage to setup some but not all of the special permissions/group
memberships necessary for the account to operate, before the error
occurs, but it does not appear to be consistent in how far it gets in
applying the correct parameters to the account.
the second method I used, was the manual service account setup from
knowledge base article Q283811.
this allows me to get the account setup, and the service set to log in
as the account, but when the service attempts to start, it fails, with
the same event log entry shown above.
also while trying to resolve all this SP2 became available, I first
tried to resolve this issue before installing SP2 however when I was
unable to, I went ahead and applied SP2 in the hopes that it might
help, as near as I can tell it has no effect, I attempted all the
previous methods and got the same results.
Any help with this would be greatly appreciated.
Thank you,
Jeffrey WilliamsDid you verify that the local account that you want to use for running SQL
Agent service is a member of the Local Users & Groups in the Group
'Administrators'?
and that the SQL Server login has the server role of 'sysadmin'
If the local user has that security it should be able to run SQL Agent
~Ellen
--
Thank you for sharing your knowledge
"sailorfej" wrote:
> I am currently running SQL Server 2005 on a stand alone (not a domain
> member) Windows Server 2003, this server was installed during setup
> using local user accounts as service accounts.
> As far as I recall at the time everything, including the SQL agent
> functioned normally. At this time, the server itself still seems to
> be running fine, however the SQL Agent service will not start.
> I can not be sure as up until recently we haven't really been using
> the SQL Agent, however I believe the problem would have started around
> the time that service pack 1 was installed.
> The following is the event log error message that is generated
> everytime the SQL Agent service attempts to start:
> ###
> Event Type: Error
> Event Source: SQLSERVERAGENT
> Event Category: Service Control
> Event ID: 103
> Date: 7/24/2007
> Time: 3:55:22 PM
> User: N/A
> Computer: DBSERVER
> Description:
> SQLServerAgent could not be started (reason: SQLServerAgent must be
> able to connect to SQLServer as SysAdmin, but '(Unknown)' is not a
> member of the SysAdmin role).
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> ###
> Please note that where the error message should indicate the name of
> the service account (svc_sqlagent) it instead indicates "Unknown".
> Also that SQL Server database engine running under the its own local
> user service account (svc_sqlserver) works fine.
> I have since tried recreating and reassigning a new local user service
> account for the SQL Agent using two methods,
> the first, the official approved method using the SQL Server
> Configuration Manager:
> results in the simple and vague error dialog box:
> Title bar: WMI Provider Error
> Error message: The process terminated unexpectedly. [0x8007042b]
> The above error however produces no entries in any of the event logs.
> If I start with a plain vanilla local user account, the config manager
> does manage to setup some but not all of the special permissions/group
> memberships necessary for the account to operate, before the error
> occurs, but it does not appear to be consistent in how far it gets in
> applying the correct parameters to the account.
> the second method I used, was the manual service account setup from
> knowledge base article Q283811.
> this allows me to get the account setup, and the service set to log in
> as the account, but when the service attempts to start, it fails, with
> the same event log entry shown above.
> also while trying to resolve all this SP2 became available, I first
> tried to resolve this issue before installing SP2 however when I was
> unable to, I went ahead and applied SP2 in the hopes that it might
> help, as near as I can tell it has no effect, I attempted all the
> previous methods and got the same results.
> Any help with this would be greatly appreciated.
> Thank you,
> Jeffrey Williams
>|||On Aug 15, 2:56 pm, Ellen <DBAEl...@.community.nospam> wrote:
> Did you verify that the local account that you want to use for running SQL
> Agent service is a member of the Local Users & Groups in the Group
> 'Administrators'?
> and that the SQL Server login has the server role of 'sysadmin'
> If the local user has that security it should be able to run SQL Agent
> ~Ellen
> --
> Thank you for sharing your knowledge
> "sailorfej" wrote:
> > I am currently running SQL Server 2005 on a stand alone (not a domain
> > member) Windows Server 2003, this server was installed during setup
> > using local user accounts as service accounts.
> > As far as I recall at the time everything, including the SQL agent
> > functioned normally. At this time, the server itself still seems to
> > be running fine, however the SQL Agent service will not start.
> > I can not be sure as up until recently we haven't really been using
> > the SQL Agent, however I believe the problem would have started around
> > the time that service pack 1 was installed.
> > The following is the event log error message that is generated
> > everytime the SQL Agent service attempts to start:
> > ###
> > Event Type: Error
> > Event Source: SQLSERVERAGENT
> > Event Category: Service Control
> > Event ID: 103
> > Date: 7/24/2007
> > Time: 3:55:22 PM
> > User: N/A
> > Computer: DBSERVER
> > Description:
> > SQLServerAgent could not be started (reason: SQLServerAgent must be
> > able to connect to SQLServer as SysAdmin, but '(Unknown)' is not a
> > member of the SysAdmin role).
> > For more information, see Help and Support Center at
> >http://go.microsoft.com/fwlink/events.asp.
> > ###
> > Please note that where the error message should indicate the name of
> > the service account (svc_sqlagent) it instead indicates "Unknown".
> > Also that SQL Server database engine running under the its own local
> > user service account (svc_sqlserver) works fine.
> > I have since tried recreating and reassigning a new local user service
> > account for the SQL Agent using two methods,
> > the first, the official approved method using the SQL Server
> > Configuration Manager:
> > results in the simple and vague error dialog box:
> > Title bar: WMI Provider Error
> > Error message: The process terminated unexpectedly. [0x8007042b]
> > The above error however produces no entries in any of the event logs.
> > If I start with a plain vanilla local user account, the config manager
> > does manage to setup some but not all of the special permissions/group
> > memberships necessary for the account to operate, before the error
> > occurs, but it does not appear to be consistent in how far it gets in
> > applying the correct parameters to the account.
> > the second method I used, was the manual service account setup from
> > knowledge base article Q283811.
> > this allows me to get the account setup, and the service set to log in
> > as the account, but when the service attempts to start, it fails, with
> > the same event log entry shown above.
> > also while trying to resolve all this SP2 became available, I first
> > tried to resolve this issue before installing SP2 however when I was
> > unable to, I went ahead and applied SP2 in the hopes that it might
> > help, as near as I can tell it has no effect, I attempted all the
> > previous methods and got the same results.
> > Any help with this would be greatly appreciated.
> > Thank you,
> > Jeffrey Williams
Hi Ellen,
Yes, I did. As I described in my previous message, both methods I
used in setting up the service account resulted in the correct
permissions for the account, in addition, the original account setup
carried out during the SQL Servers installation setup the service
account with the correct permissions, and the service didn't start to
have problems until later.
I believe the there is some break in the interface between the WMI/NT
Auth components, and the SQL Server Auth mechanism, this is why I made
sure to include the info for the WMI error dialog, and pointed that in
the event log error message the service account is not correctly
identified, but is instead listed as "unknown". If this were a
standard permissions issue, the account would have been correctly
identified as "svc_sqlagent".
If you have any other ideas, I would very much appreciate hearing
them.
Thanks,
Jeff

MS SQL Server 2005 - SQL Agent problems

I am currently running SQL Server 2005 on a stand alone (not a domain
member) Windows Server 2003, this server was installed during setup
using local user accounts as service accounts.
As far as I recall at the time everything, including the SQL agent
functioned normally. At this time, the server itself still seems to
be running fine, however the SQL Agent service will not start.
I can not be sure as up until recently we haven't really been using
the SQL Agent, however I believe the problem would have started around
the time that service pack 1 was installed.
The following is the event log error message that is generated
everytime the SQL Agent service attempts to start:
###
Event Type: Error
Event Source: SQLSERVERAGENT
Event Category: Service Control
Event ID: 103
Date: 7/24/2007
Time: 3:55:22 PM
User: N/A
Computer: DBSERVER
Description:
SQLServerAgent could not be started (reason: SQLServerAgent must be
able to connect to SQLServer as SysAdmin, but '(Unknown)' is not a
member of the SysAdmin role).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
###
Please note that where the error message should indicate the name of
the service account (svc_sqlagent) it instead indicates "Unknown".
Also that SQL Server database engine running under the its own local
user service account (svc_sqlserver) works fine.
I have since tried recreating and reassigning a new local user service
account for the SQL Agent using two methods,
the first, the official approved method using the SQL Server
Configuration Manager:
results in the simple and vague error dialog box:
Title bar: WMI Provider Error
Error message: The process terminated unexpectedly. [0x8007042b]
The above error however produces no entries in any of the event logs.
If I start with a plain vanilla local user account, the config manager
does manage to setup some but not all of the special permissions/group
memberships necessary for the account to operate, before the error
occurs, but it does not appear to be consistent in how far it gets in
applying the correct parameters to the account.
the second method I used, was the manual service account setup from
knowledge base article Q283811.
this allows me to get the account setup, and the service set to log in
as the account, but when the service attempts to start, it fails, with
the same event log entry shown above.
also while trying to resolve all this SP2 became available, I first
tried to resolve this issue before installing SP2 however when I was
unable to, I went ahead and applied SP2 in the hopes that it might
help, as near as I can tell it has no effect, I attempted all the
previous methods and got the same results.
Any help with this would be greatly appreciated.
Thank you,
Jeffrey Williams
Did you verify that the local account that you want to use for running SQL
Agent service is a member of the Local Users & Groups in the Group
'Administrators'?
and that the SQL Server login has the server role of 'sysadmin'
If the local user has that security it should be able to run SQL Agent
~Ellen
Thank you for sharing your knowledge
"sailorfej" wrote:

> I am currently running SQL Server 2005 on a stand alone (not a domain
> member) Windows Server 2003, this server was installed during setup
> using local user accounts as service accounts.
> As far as I recall at the time everything, including the SQL agent
> functioned normally. At this time, the server itself still seems to
> be running fine, however the SQL Agent service will not start.
> I can not be sure as up until recently we haven't really been using
> the SQL Agent, however I believe the problem would have started around
> the time that service pack 1 was installed.
> The following is the event log error message that is generated
> everytime the SQL Agent service attempts to start:
> ###
> Event Type: Error
> Event Source: SQLSERVERAGENT
> Event Category: Service Control
> Event ID: 103
> Date: 7/24/2007
> Time: 3:55:22 PM
> User: N/A
> Computer: DBSERVER
> Description:
> SQLServerAgent could not be started (reason: SQLServerAgent must be
> able to connect to SQLServer as SysAdmin, but '(Unknown)' is not a
> member of the SysAdmin role).
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> ###
> Please note that where the error message should indicate the name of
> the service account (svc_sqlagent) it instead indicates "Unknown".
> Also that SQL Server database engine running under the its own local
> user service account (svc_sqlserver) works fine.
> I have since tried recreating and reassigning a new local user service
> account for the SQL Agent using two methods,
> the first, the official approved method using the SQL Server
> Configuration Manager:
> results in the simple and vague error dialog box:
> Title bar: WMI Provider Error
> Error message: The process terminated unexpectedly. [0x8007042b]
> The above error however produces no entries in any of the event logs.
> If I start with a plain vanilla local user account, the config manager
> does manage to setup some but not all of the special permissions/group
> memberships necessary for the account to operate, before the error
> occurs, but it does not appear to be consistent in how far it gets in
> applying the correct parameters to the account.
> the second method I used, was the manual service account setup from
> knowledge base article Q283811.
> this allows me to get the account setup, and the service set to log in
> as the account, but when the service attempts to start, it fails, with
> the same event log entry shown above.
> also while trying to resolve all this SP2 became available, I first
> tried to resolve this issue before installing SP2 however when I was
> unable to, I went ahead and applied SP2 in the hopes that it might
> help, as near as I can tell it has no effect, I attempted all the
> previous methods and got the same results.
> Any help with this would be greatly appreciated.
> Thank you,
> Jeffrey Williams
>
|||On Aug 15, 2:56 pm, Ellen <DBAEl...@.community.nospam> wrote:[vbcol=seagreen]
> Did you verify that the local account that you want to use for running SQL
> Agent service is a member of the Local Users & Groups in the Group
> 'Administrators'?
> and that the SQL Server login has the server role of 'sysadmin'
> If the local user has that security it should be able to run SQL Agent
> ~Ellen
> --
> Thank you for sharing your knowledge
> "sailorfej" wrote:
>
>
>
>
>
>
>
>
Hi Ellen,
Yes, I did. As I described in my previous message, both methods I
used in setting up the service account resulted in the correct
permissions for the account, in addition, the original account setup
carried out during the SQL Servers installation setup the service
account with the correct permissions, and the service didn't start to
have problems until later.
I believe the there is some break in the interface between the WMI/NT
Auth components, and the SQL Server Auth mechanism, this is why I made
sure to include the info for the WMI error dialog, and pointed that in
the event log error message the service account is not correctly
identified, but is instead listed as "unknown". If this were a
standard permissions issue, the account would have been correctly
identified as "svc_sqlagent".
If you have any other ideas, I would very much appreciate hearing
them.
Thanks,
Jeff

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 restore

I have a MS SQL database backup from a client and would like to use this to create the database on my local machine.

I have been advised to do this by using restore database in enterprise manager.

I am lost though as I really dont know much about MS SQL - sorry people but can anyone tell me how to do this?Sure (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_bkprst_20h1.asp).

-PatP|||I think they had the database on their D:/ drive and I only have a C: drive

That is whats causing the problem I think.

Any suggestions on how to get round this?

Thanks

Paul|||When restoring in EM, click on Options tab and change the path for every device there.|||and buy a copy of this book...
Inside SQL Server 2000 By Kalen Delaney (http://www.bestwebbuys.com/Inside_Microsoft_SQL_Server_2000-ISBN_0735609985.html?isrc=b-search)

MS Sql Express Tookit error during install

Trying to install MS Sql Server 2005 Express tool-kit on local PC to manage SQL Express on Server. Was able to get this installed on the server but would like to be able to run the tool kit on PC to build reports + publish on reports server. when i try and install on pc i get

Error 1335.The cabinet file '_1979_RTL_x86_enu_VS_SCC_TeamCore.cab required for this installation is corrupt or cannot be used. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.

I used the exact same install SQLEXPR_TOOLKIT.EXE on the server & didnot receive this error. Is it possible to run the toolkit on PC + connect to SQL 2005 Express on another server? I am running VWD 2005 Express on client PC + can connect to SQL 2005 EXPRESS on the other server just fine. I needed a way to build + publish reports so I looked at SQL 2005 EXPRESS + REPORTS SERVICES. These are working but I don't want to have to use the server to build the reports + publish them.

Thanks.

Before we do a bunch of whacky troubleshooting, just try downloading a new copy of the toolkit installer. Who ever knows what cabinet files do at night when you're not looking. If the fresh download doesn't clear up the problem I'll move this thread over to the Setup group so they can give you some suggestions.

Regards,

Mike Wachal
SQL Express team

|||OK - Thanks. I will download a new copy + give it a try.|||I tried the install again + I get the same results. Please move to Install Forum. Thanks.|||

Moving to setup

Mike

MS SQL database Transfer

How can I transfer an online MS SQL Database with all data to a local machine MS SQL server. I am using Import Export Tool provided by MS SQL Enterprise manager but the referential integraity breaks (Primary and secondary key relationship). Thus the Data concurrency is lost and the database becaomes of no us.

Most of our database projects have Stored procs, Views, Triggers and contain data. Sometimes we have to take back up of the running database.

The same problem comes when we try to install an offline database with data online. We have to run the scripts through Query Analyser on the online server to install database tables, procs, triggers etc and then repopulate the database once again.

But if you see mySQL one can import the complete database with all data using phpmyAdmin tool. Most hosts provide this tool so becomes easier.

Though MS SQL has a database restoration option but 90% hosts do not allow you to automatically generate back up and download. You have to request them and then they generate the backup and upload to web server folder for us to download and restore.

Can anyone explain a solution to this daily problem..axaya

This is the DTS import/export wizard. Have you tried the "Copy objects and data Between SQL Server databases" option ?? This should copy all objects when doing the export. this copied all constraints, indexes...

Hope that helps :-)|||Any other way. DTS takes huge time and connection fails.|||How about detaching and attaching the DB, check out the link.

http://support.microsoft.com/kb/224071/

MS SQL conn string

My MS SQL Server was working perfectly fine locally when I used the following connection string:

server=(local)\\DB;Integrated Security=True;uid=;pwd=;database=AspNetDb

When I moved my SQL server to another machine within my LAN, it stopped functioning.
server=(192.168.1.3)\\DB;IntegratedSecurity=True;uid=;pwd=;database=AspNetDb

Could someone kindly give me some advice? I appreciate your assistance.look at:

http://www.connectionstrings.com/

ms sql cluster: should i and how to place tempdb on local drive

Hi all
we are about to set up database on sql server cluster. Up to this point we
had set up ms sql cluster using vm.
My intention was to set up tempdb on local c drive. It turned out, that we
could not mount c drive at all and only drives which we mounted were drives
defined for cluster.
1. Do we miss something? Does clustered software allows to mount local
drives along with cluster defined drives?
2. If yes, do you recommend to use local drive for tempdb.
Thank you for your respond.
You can only place SQL data files on clustered drives where SQL is dependent
on the particular disk resource. This includes data files for tempdb.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Gene." <Gene@.discussions.microsoft.com> wrote in message
news:0A7A9EAC-DF71-499C-A615-8B26F99CD15C@.microsoft.com...
> Hi all
> we are about to set up database on sql server cluster. Up to this point we
> had set up ms sql cluster using vm.
> My intention was to set up tempdb on local c drive. It turned out, that we
> could not mount c drive at all and only drives which we mounted were
> drives
> defined for cluster.
> 1. Do we miss something? Does clustered software allows to mount local
> drives along with cluster defined drives?
> 2. If yes, do you recommend to use local drive for tempdb.
> Thank you for your respond.
|||Hi all
I would like to remark myself regarding my post below.
C drive is visable to cluster pc but...
it's not visable to sql server.
When you create new db either using tsql or windows inerface, 1 one produce
error complaining about not visable drive.
Windows interface does not show c drive as one generaly available for
database creation.
"Gene." wrote:

> Hi all
> we are about to set up database on sql server cluster. Up to this point we
> had set up ms sql cluster using vm.
> My intention was to set up tempdb on local c drive. It turned out, that we
> could not mount c drive at all and only drives which we mounted were drives
> defined for cluster.
> 1. Do we miss something? Does clustered software allows to mount local
> drives along with cluster defined drives?
> 2. If yes, do you recommend to use local drive for tempdb.
> Thank you for your respond.
|||Geoff
Do you mind if i ask you:
We can not do it because cluster does not have c drive defined to it (and
likely can not have c drive defined to it)?
Gene.
"Geoff N. Hiten" wrote:

> You can only place SQL data files on clustered drives where SQL is dependent
> on the particular disk resource. This includes data files for tempdb.
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
>
> "Gene." <Gene@.discussions.microsoft.com> wrote in message
> news:0A7A9EAC-DF71-499C-A615-8B26F99CD15C@.microsoft.com...
>
|||C: is local to each node and cannot be defined as a cluster resource even
when it exists on all nodes. You cannot place tempdb for a cluster on local
disks.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Gene." <Gene@.discussions.microsoft.com> wrote in message
news:C7F5E403-A592-452C-B5C0-7DCC7D1B437B@.microsoft.com...[vbcol=seagreen]
> Geoff
> Do you mind if i ask you:
> We can not do it because cluster does not have c drive defined to it (and
> likely can not have c drive defined to it)?
> Gene.
> "Geoff N. Hiten" wrote:
|||Thank you Geoff. now I understand.
"Geoff N. Hiten" wrote:

> C: is local to each node and cannot be defined as a cluster resource even
> when it exists on all nodes. You cannot place tempdb for a cluster on local
> disks.
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
>
> "Gene." <Gene@.discussions.microsoft.com> wrote in message
> news:C7F5E403-A592-452C-B5C0-7DCC7D1B437B@.microsoft.com...
>

ms sql cluster: should i and how to place tempdb on local drive

Hi all
we are about to set up database on sql server cluster. Up to this point we
had set up ms sql cluster using vm.
My intention was to set up tempdb on local c drive. It turned out, that we
could not mount c drive at all and only drives which we mounted were drives
defined for cluster.
1. Do we miss something? Does clustered software allows to mount local
drives along with cluster defined drives?
2. If yes, do you recommend to use local drive for tempdb.
Thank you for your respond.You can only place SQL data files on clustered drives where SQL is dependent
on the particular disk resource. This includes data files for tempdb.
--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Gene." <Gene@.discussions.microsoft.com> wrote in message
news:0A7A9EAC-DF71-499C-A615-8B26F99CD15C@.microsoft.com...
> Hi all
> we are about to set up database on sql server cluster. Up to this point we
> had set up ms sql cluster using vm.
> My intention was to set up tempdb on local c drive. It turned out, that we
> could not mount c drive at all and only drives which we mounted were
> drives
> defined for cluster.
> 1. Do we miss something? Does clustered software allows to mount local
> drives along with cluster defined drives?
> 2. If yes, do you recommend to use local drive for tempdb.
> Thank you for your respond.|||Hi all
I would like to remark myself regarding my post below.
C drive is visable to cluster pc but...
it's not visable to sql server.
When you create new db either using tsql or windows inerface, 1 one produce
error complaining about not visable drive.
Windows interface does not show c drive as one generaly available for
database creation.
"Gene." wrote:
> Hi all
> we are about to set up database on sql server cluster. Up to this point we
> had set up ms sql cluster using vm.
> My intention was to set up tempdb on local c drive. It turned out, that we
> could not mount c drive at all and only drives which we mounted were drives
> defined for cluster.
> 1. Do we miss something? Does clustered software allows to mount local
> drives along with cluster defined drives?
> 2. If yes, do you recommend to use local drive for tempdb.
> Thank you for your respond.|||Geoff
Do you mind if i ask you:
We can not do it because cluster does not have c drive defined to it (and
likely can not have c drive defined to it)?
Gene.
"Geoff N. Hiten" wrote:
> You can only place SQL data files on clustered drives where SQL is dependent
> on the particular disk resource. This includes data files for tempdb.
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
>
> "Gene." <Gene@.discussions.microsoft.com> wrote in message
> news:0A7A9EAC-DF71-499C-A615-8B26F99CD15C@.microsoft.com...
> > Hi all
> > we are about to set up database on sql server cluster. Up to this point we
> > had set up ms sql cluster using vm.
> > My intention was to set up tempdb on local c drive. It turned out, that we
> > could not mount c drive at all and only drives which we mounted were
> > drives
> > defined for cluster.
> > 1. Do we miss something? Does clustered software allows to mount local
> > drives along with cluster defined drives?
> > 2. If yes, do you recommend to use local drive for tempdb.
> >
> > Thank you for your respond.
>|||C: is local to each node and cannot be defined as a cluster resource even
when it exists on all nodes. You cannot place tempdb for a cluster on local
disks.
--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Gene." <Gene@.discussions.microsoft.com> wrote in message
news:C7F5E403-A592-452C-B5C0-7DCC7D1B437B@.microsoft.com...
> Geoff
> Do you mind if i ask you:
> We can not do it because cluster does not have c drive defined to it (and
> likely can not have c drive defined to it)?
> Gene.
> "Geoff N. Hiten" wrote:
>> You can only place SQL data files on clustered drives where SQL is
>> dependent
>> on the particular disk resource. This includes data files for tempdb.
>> --
>> Geoff N. Hiten
>> Senior SQL Infrastructure Consultant
>> Microsoft SQL Server MVP
>>
>>
>> "Gene." <Gene@.discussions.microsoft.com> wrote in message
>> news:0A7A9EAC-DF71-499C-A615-8B26F99CD15C@.microsoft.com...
>> > Hi all
>> > we are about to set up database on sql server cluster. Up to this point
>> > we
>> > had set up ms sql cluster using vm.
>> > My intention was to set up tempdb on local c drive. It turned out, that
>> > we
>> > could not mount c drive at all and only drives which we mounted were
>> > drives
>> > defined for cluster.
>> > 1. Do we miss something? Does clustered software allows to mount local
>> > drives along with cluster defined drives?
>> > 2. If yes, do you recommend to use local drive for tempdb.
>> >
>> > Thank you for your respond.
>>|||Thank you Geoff. now I understand.
"Geoff N. Hiten" wrote:
> C: is local to each node and cannot be defined as a cluster resource even
> when it exists on all nodes. You cannot place tempdb for a cluster on local
> disks.
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
>
> "Gene." <Gene@.discussions.microsoft.com> wrote in message
> news:C7F5E403-A592-452C-B5C0-7DCC7D1B437B@.microsoft.com...
> > Geoff
> >
> > Do you mind if i ask you:
> > We can not do it because cluster does not have c drive defined to it (and
> > likely can not have c drive defined to it)?
> >
> > Gene.
> >
> > "Geoff N. Hiten" wrote:
> >
> >> You can only place SQL data files on clustered drives where SQL is
> >> dependent
> >> on the particular disk resource. This includes data files for tempdb.
> >>
> >> --
> >> Geoff N. Hiten
> >> Senior SQL Infrastructure Consultant
> >> Microsoft SQL Server MVP
> >>
> >>
> >>
> >>
> >> "Gene." <Gene@.discussions.microsoft.com> wrote in message
> >> news:0A7A9EAC-DF71-499C-A615-8B26F99CD15C@.microsoft.com...
> >> > Hi all
> >> > we are about to set up database on sql server cluster. Up to this point
> >> > we
> >> > had set up ms sql cluster using vm.
> >> > My intention was to set up tempdb on local c drive. It turned out, that
> >> > we
> >> > could not mount c drive at all and only drives which we mounted were
> >> > drives
> >> > defined for cluster.
> >> > 1. Do we miss something? Does clustered software allows to mount local
> >> > drives along with cluster defined drives?
> >> > 2. If yes, do you recommend to use local drive for tempdb.
> >> >
> >> > Thank you for your respond.
> >>
> >>
>

ms sql cluster: should i and how to place tempdb on local drive

Hi all
we are about to set up database on sql server cluster. Up to this point we
had set up ms sql cluster using vm.
My intention was to set up tempdb on local c drive. It turned out, that we
could not mount c drive at all and only drives which we mounted were drives
defined for cluster.
1. Do we miss something? Does clustered software allows to mount local
drives along with cluster defined drives?
2. If yes, do you recommend to use local drive for tempdb.
Thank you for your respond.You can only place SQL data files on clustered drives where SQL is dependent
on the particular disk resource. This includes data files for tempdb.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Gene." <Gene@.discussions.microsoft.com> wrote in message
news:0A7A9EAC-DF71-499C-A615-8B26F99CD15C@.microsoft.com...
> Hi all
> we are about to set up database on sql server cluster. Up to this point we
> had set up ms sql cluster using vm.
> My intention was to set up tempdb on local c drive. It turned out, that we
> could not mount c drive at all and only drives which we mounted were
> drives
> defined for cluster.
> 1. Do we miss something? Does clustered software allows to mount local
> drives along with cluster defined drives?
> 2. If yes, do you recommend to use local drive for tempdb.
> Thank you for your respond.|||Hi all
I would like to remark myself regarding my post below.
C drive is visable to cluster pc but...
it's not visable to sql server.
When you create new db either using tsql or windows inerface, 1 one produce
error complaining about not visable drive.
Windows interface does not show c drive as one generaly available for
database creation.
"Gene." wrote:

> Hi all
> we are about to set up database on sql server cluster. Up to this point we
> had set up ms sql cluster using vm.
> My intention was to set up tempdb on local c drive. It turned out, that we
> could not mount c drive at all and only drives which we mounted were drive
s
> defined for cluster.
> 1. Do we miss something? Does clustered software allows to mount local
> drives along with cluster defined drives?
> 2. If yes, do you recommend to use local drive for tempdb.
> Thank you for your respond.

MS SQL client not found for connect to local running server

Hi

I got this error when I try to install SSMAExtPack.exe that is required by SS Migration Assistant.

MS SQL client not found for connect to local running server

I got Sql server 2005 trivial version installed and SS Studio Express on my laptop, everything on one machine. Do I need to install MS SQL client? If so, where and how can I donwload it? Is it free trival version?

Thanks in advanced

Li

When you install SQL Server 2005, SQL Native Client(SNAC) will be installed automatically. Also, MDAC is part of Windows OS. So, you should not have this problem unless the machine is messed up.

|||

Hi

Thanks.

Have anyone else got this problem?

|||

Yes i got the same problem. And my machine is not messed up.

Got all programs clean installed. VS .NET 2005 SQL Server developer 2005.

All programs working fine. But running SSMAExtPack.exe returns the described error.

|||Moving to tools, hope somebody knows what the issue is.|||Have you chosen to install client tools when Evaluation edition is select to install?|||

Satya SKJ wrote:

Have you chosen to install client tools when Evaluation edition is select to install?

Hi,

When i install development software, i always do a full install, to prevent things from missing.

I do not run any evaluation software, but fully registered software. In order to resolve this

problem i tried to download and install the SQL Client components from Microsoft with no

result. The setup told me if i wanted to remove or repair the current installation, so my initial

installation was successfull. Tried selecting the repaire option did not do the trick.

Rgrds,

Chris

MS SQL client not found for connect to local running server

Hi

I got this error when I try to install SSMAExtPack.exe that is required by SS Migration Assistant.

MS SQL client not found for connect to local running server

I got Sql server 2005 trivial version installed and SS Studio Express on my laptop, everything on one machine. Do I need to install MS SQL client? If so, where and how can I donwload it? Is it free trival version?

Thanks in advanced

Li

When you install SQL Server 2005, SQL Native Client(SNAC) will be installed automatically. Also, MDAC is part of Windows OS. So, you should not have this problem unless the machine is messed up.

|||

Hi

Thanks.

Have anyone else got this problem?

|||

Yes i got the same problem. And my machine is not messed up.

Got all programs clean installed. VS .NET 2005 SQL Server developer 2005.

All programs working fine. But running SSMAExtPack.exe returns the described error.

|||Moving to tools, hope somebody knows what the issue is.|||Have you chosen to install client tools when Evaluation edition is select to install?|||

Satya SKJ wrote:

Have you chosen to install client tools when Evaluation edition is select to install?

Hi,

When i install development software, i always do a full install, to prevent things from missing.

I do not run any evaluation software, but fully registered software. In order to resolve this

problem i tried to download and install the SQL Client components from Microsoft with no

result. The setup told me if i wanted to remove or repair the current installation, so my initial

installation was successfull. Tried selecting the repaire option did not do the trick.

Rgrds,

Chris

MS SQL 2005 SP2 x64 & SSIS Packages

On my local desktop, I can create and run ssis packages, when I try to do the same thing on server I get he following error right clicking on running packages or stored packages.

failed to retrieve data for this request. Library not Registered. (exception from HRESULT: 0x8002801D

there are 2 instances of SQL on this server. Both are named with one being use by SQLExpress and the other by SQL2005 Std

Give this a try; Integration Services installs just once no matter how many instances are installed on the machine. For the instance you are wishing to work with you can change the instance viewed by modifying C:\Program Files\Microsoft SQL Server\90\DTS\Binn\MsDtsSrvr.ini.xml

Change the entry below to match your instance name.

--Prior to change

<ServerName>.</ServerName>

--After change

<ServerName>MySQLServer\MySQLInstancename</ServerName>

|||

Hi,

This is setup problem, partially discussed in this KB: http://support.microsoft.com/kb/919224

If reapplying SP2 to both instances does not work, please run the following command to manually fix it (the KB is to be modified soon):

%windir%\syswow64\regsvr32 "%ProgramFiles(x86)%\Microsoft SQL Server\90\dts\binn\dts.dll”

|||Still no luck|||

I'm still getting same error. I do not have the hotfix installed do I need it?

Microsost SQL Server Management Studio

Failed to retrieve data for this request. ( Microsoft.SqlServer.SmoEnum)

Additional Information:

Library not registered.( Exception from HRESULT: 0x80002801D(TYPE_E_LIBNOTREGISTERED))

(Microsoft.SqlServer.DTSRuntimeWrap)

Library not registered.( Exception from HRESULT: 0x80002801D(TYPE_E_LIBNOTREGISTERED))

(Microsoft.SqlServer.DTSRuntimeWrap)

MS SQL 2005 SP2 x64 & SSIS Packages

On my local desktop, I can create and run ssis packages, when I try to do the same thing on server I get he following error right clicking on running packages or stored packages.

failed to retrieve data for this request. Library not Registered. (exception from HRESULT: 0x8002801D

there are 2 instances of SQL on this server. Both are named with one being use by SQLExpress and the other by SQL2005 Std

Give this a try; Integration Services installs just once no matter how many instances are installed on the machine. For the instance you are wishing to work with you can change the instance viewed by modifying C:\Program Files\Microsoft SQL Server\90\DTS\Binn\MsDtsSrvr.ini.xml

Change the entry below to match your instance name.

--Prior to change

<ServerName>.</ServerName>

--After change

<ServerName>MySQLServer\MySQLInstancename</ServerName>

|||

Hi,

This is setup problem, partially discussed in this KB: http://support.microsoft.com/kb/919224

If reapplying SP2 to both instances does not work, please run the following command to manually fix it (the KB is to be modified soon):

%windir%\syswow64\regsvr32 "%ProgramFiles(x86)%\Microsoft SQL Server\90\dts\binn\dts.dll”

|||Still no luck|||

I'm still getting same error. I do not have the hotfix installed do I need it?

Microsost SQL Server Management Studio

Failed to retrieve data for this request. ( Microsoft.SqlServer.SmoEnum)

Additional Information:

Library not registered.( Exception from HRESULT: 0x80002801D(TYPE_E_LIBNOTREGISTERED))

(Microsoft.SqlServer.DTSRuntimeWrap)

Library not registered.( Exception from HRESULT: 0x80002801D(TYPE_E_LIBNOTREGISTERED))

(Microsoft.SqlServer.DTSRuntimeWrap)

MS SQL 2000 Remote Administration

Hello and thank you in advance for your assistance.
I am trying to rid myself of the necessity of running a local server (2000).
I am currently relying on Enterprise manager in SQL 2000 to administer
databases that are hosted by my ISP.
Is there an application like Enterprise Manager that I can run on my XP box?
Thanks,
Julian
Assuming you have the proper license you can load Enterprise Manager on XP
with no problem. Just install the client tools and not the server itself.
Andrew J. Kelly SQL MVP
"Julian Forniss" <Julian Forniss@.discussions.microsoft.com> wrote in message
news:35AEAE46-919A-4AFA-9A44-53A02F7B726D@.microsoft.com...
> Hello and thank you in advance for your assistance.
> I am trying to rid myself of the necessity of running a local server
> (2000).
> I am currently relying on Enterprise manager in SQL 2000 to administer
> databases that are hosted by my ISP.
> Is there an application like Enterprise Manager that I can run on my XP
> box?
> Thanks,
> Julian
|||Thank you very much.
"Andrew J. Kelly" wrote:

> Assuming you have the proper license you can load Enterprise Manager on XP
> with no problem. Just install the client tools and not the server itself.
> --
> Andrew J. Kelly SQL MVP
>
> "Julian Forniss" <Julian Forniss@.discussions.microsoft.com> wrote in message
> news:35AEAE46-919A-4AFA-9A44-53A02F7B726D@.microsoft.com...
>
>