cannot drop mdf file

Hi All,
I cannot drop a mdf file that don't have a database but is in data
directory,.
Can you help-me ?
I'am using sql server 2005.
TIAYeah!!!
shift+delete is the solution.
Please ignore this!!!
"Roger" <roger@.rnospam.com> escreveu na mensagem
news:%23lOqzGHLIHA.4684@.TK2MSFTNGP06.phx.gbl...
> Hi All,
>
> I cannot drop a mdf file that don't have a database but is in data
> directory,.
> Can you help-me ?
> I'am using sql server 2005.
> TIA
>
>|||Shift + Delete would just delete the file without any warning\confirmation.
That's only the difference between Delete and Shift + Delete.
File must be using by another process somehow when you were trying to delete
the file and when you tried the Delete with Shift it was not being used so
it was deleted I believe.
--
Ekrem Önsoy
"Roger" <roger@.rnospam.com> wrote in message
news:%23dkmWQHLIHA.1188@.TK2MSFTNGP04.phx.gbl...
> Yeah!!!
> shift+delete is the solution.
> Please ignore this!!!
>
> "Roger" <roger@.rnospam.com> escreveu na mensagem
> news:%23lOqzGHLIHA.4684@.TK2MSFTNGP06.phx.gbl...
>> Hi All,
>>
>> I cannot drop a mdf file that don't have a database but is in data
>> directory,.
>> Can you help-me ?
>> I'am using sql server 2005.
>> TIA
>>
>|||Actually, the biggest difference between delete and shift+delete is that
shift+delete
doesn't send files to the recycle bin.
"Ekrem Ã?nsoy" wrote:
> Shift + Delete would just delete the file without any warning\confirmation.
> That's only the difference between Delete and Shift + Delete.
> File must be using by another process somehow when you were trying to delete
> the file and when you tried the Delete with Shift it was not being used so
> it was deleted I believe.
> --
> Ekrem Ã?nsoy
>
> "Roger" <roger@.rnospam.com> wrote in message
> news:%23dkmWQHLIHA.1188@.TK2MSFTNGP04.phx.gbl...
> > Yeah!!!
> >
> > shift+delete is the solution.
> >
> > Please ignore this!!!
> >
> >
> > "Roger" <roger@.rnospam.com> escreveu na mensagem
> > news:%23lOqzGHLIHA.4684@.TK2MSFTNGP06.phx.gbl...
> >> Hi All,
> >>
> >>
> >> I cannot drop a mdf file that don't have a database but is in data
> >> directory,.
> >>
> >> Can you help-me ?
> >> I'am using sql server 2005.
> >>
> >> TIA
> >>
> >>
> >>
> >
> >
>

cannot connect/login error message

I am trying to connect to a virtual directory where there is an application
that was developed in .asp.net - it is linked to a sql server database. I am
using IIS, Server 2003 and SQL Server 2000 - same server - Any ideas where
this may be coming from? I posted this message under connect and security
sections. Thanks.
Server Error in '/Admin' Application.
Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information about
the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: Login failed for user
'NT AUTHORITY\NETWORK SERVICE'.
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.
Stack Trace:
[SqlException: Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.]
System.Data.SqlClient.ConnectionPool.GetConnection (Boolean&
isInTransaction) +474
System.Data.SqlClient.SqlConnectionPoolManager.Get PooledConnection(SqlConnectionString options, Boolean& isInTransaction) +372
System.Data.SqlClient.SqlConnection.Open() +384
ut.hfrp.asap.DAO.BaseDAO.getConnection() +83
[DAOException: Unable to create connection to database]
ut.hfrp.asap.DAO.BaseDAO.getConnection() +154
ut.hfrp.asap.DAO.UserDAO.GetList() +70
ut.hfrp.asap.BusObj.Settings.AirlineSettings.GetUs erList() +30
ut.hfrp.asap.ManagerApp.Login.SubmitLogin_Click(Ob ject sender, EventArgs
e) +51
System.Web.UI.WebControls.Button.OnClick(EventArgs e) +108
System.Web.UI.WebControls.Button.System.Web.UI.IPo stBackEventHandler.RaisePostBackEvent(String eventArgument) +57
System.Web.UI.Page.RaisePostBackEvent(IPostBackEve ntHandler
sourceControl, String eventArgument) +18
System.Web.UI.Page.RaisePostBackEvent(NameValueCol lection postData) +33
System.Web.UI.Page.ProcessRequestMain() +1292
LizW
The ASP service Account is running under Networkservice Account which
is not priviledged in the SQL Server database. Either you change the
authentication in your application to SQL Server authentication
(Checkout the connectionstrings on www.connectionstrings.com for that)
or you change the service account of ASP to a domain or local account
which has to be priviledged in SQL Server.
HTH, Jens Suessmeyer.

cannot connect/login error message

I am trying to connect to a virtual directory where there is an application
that was developed in .asp.net - it is linked to a sql server database. I am
using IIS, Server 2003 and SQL Server 2000 - same server - Any ideas where
this may be coming from? I posted this message under connect and security
sections. Thanks.
Server Error in '/Admin' Application.
----
--
Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information abou
t
the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: Login failed for user
'NT AUTHORITY\NETWORK SERVICE'.
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.
Stack Trace:
[SqlException: Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.]
System.Data.SqlClient.ConnectionPool.GetConnection(Boolean&
isInTransaction) +474
System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnec
tionString options, Boolean& isInTransaction) +372
System.Data.SqlClient.SqlConnection.Open() +384
ut.hfrp.asap.DAO.BaseDAO.getConnection() +83
[DAOException: Unable to create connection to database]
ut.hfrp.asap.DAO.BaseDAO.getConnection() +154
ut.hfrp.asap.DAO.UserDAO.GetList() +70
ut.hfrp.asap.BusObj.Settings.AirlineSettings.GetUserList() +30
ut.hfrp.asap.ManagerApp.Login.SubmitLogin_Click(Object sender, EventArgs
e) +51
System.Web.UI.WebControls.Button.OnClick(EventArgs e) +108
System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePo
stBackEvent(String eventArgument) +57
System.Web.UI.Page. RaisePostBackEvent(IPostBackEventHandler
sourceControl, String eventArgument) +18
System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +33
System.Web.UI.Page.ProcessRequestMain() +1292
LizWThe ASP service Account is running under Networkservice Account which
is not priviledged in the SQL Server database. Either you change the
authentication in your application to SQL Server authentication
(Checkout the connectionstrings on www.connectionstrings.com for that)
or you change the service account of ASP to a domain or local account
which has to be priviledged in SQL Server.
HTH, Jens Suessmeyer.

cannot connect/login error message

I am trying to connect to a virtual directory where there is an application
that was developed in .asp.net - it is linked to a sql server database. I am
using IIS, Server 2003 and SQL Server 2000 - same server - Any ideas where
this may be coming from? I posted this message under connect and security
sections. Thanks.
Server Error in '/Admin' Application
----
Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information about
the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: Login failed for user
'NT AUTHORITY\NETWORK SERVICE'.
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.
Stack Trace:
[SqlException: Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.]
System.Data.SqlClient.ConnectionPool.GetConnection(Boolean&
isInTransaction) +474
System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString options, Boolean& isInTransaction) +372
System.Data.SqlClient.SqlConnection.Open() +384
ut.hfrp.asap.DAO.BaseDAO.getConnection() +83
[DAOException: Unable to create connection to database]
ut.hfrp.asap.DAO.BaseDAO.getConnection() +154
ut.hfrp.asap.DAO.UserDAO.GetList() +70
ut.hfrp.asap.BusObj.Settings.AirlineSettings.GetUserList() +30
ut.hfrp.asap.ManagerApp.Login.SubmitLogin_Click(Object sender, EventArgs
e) +51
System.Web.UI.WebControls.Button.OnClick(EventArgs e) +108
System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +57
System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler
sourceControl, String eventArgument) +18
System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +33
System.Web.UI.Page.ProcessRequestMain() +1292
--
LizWThe ASP service Account is running under Networkservice Account which
is not priviledged in the SQL Server database. Either you change the
authentication in your application to SQL Server authentication
(Checkout the connectionstrings on www.connectionstrings.com for that)
or you change the service account of ASP to a domain or local account
which has to be priviledged in SQL Server.
HTH, Jens Suessmeyer.

Cannot connect to SQL Server 2005 after Active Directory upgrade

Hi, we recently installed Active Directory here and I can no longer connect to our SQL Server 2005 box. Active Directory was installed on a different server and my development machine was added to the Active Directory. The AD server was also made a domain controller and my development machine was also added to the domain. The SQL Server sits outside the domain, and is NOT included in AD. Now when I attempt to connect via SQL authentication in my c# code, I get the following error:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

If I attempt to connect to the SQL Server box using SQL authentication from SQL Server Management Studio, the connection attempt simply times out. However, if I change the protocol used to connect to Named Pipes, I am able to connect to the SQL box.

Can anyone tell me why I cannot connect to the SQL box using SQL authentication and TCP/IP anymore?

I apologize if this post is misplaced.

I'm moving your question to the database engine forum where I hope they can help...

Paul

|||What is your connection string? If it is "<machinename>\<instancename>", then you could try to change this to "<machinename>\<instancename,<portnumber>". Maybe this will help.

Cannot connect to localhost using Windows Security Group as login

I have a test environment set up at home with a small windows server 2003 Active Directory domain. I created a windows security group on the dc and added myself and another user to the group. I then use this group as a login for SQL Server and add the login to the sysadmin server role. This works exactly as I would expect on the Windows Server computer (which is also the Domain Controller) regardless of which computer I use to connect to this Windows Server computer. However, when I set up the exact same login on the local sql server instance of my client laptop running windows xp pro, the I get an error message (Login failed for user MYDOMAIN\dgolds...) when I attempt to connect to the local instance of SQL server, even though I am able to connect to the instance on the domain controller with no problems using this same client laptop under the same user account. The only way I am able to connect locally on the laptop under this account (which does not have local admin privileges on any box, for testing purposes) is to add the user account separately as a login, rather than as part of a group. I'm curious as to why being a member of a security group that is part of the sysadmin server role does not allow me to connect to the local instance of SQL Server on this client laptop. The windows server computer is running SQL2k5 Enterprise, and the client laptop is running SQL2k5 developer. Any insight into this would be appreciated.

Thanks,

Dave

Let's focus on the laptop for a moment, becuase that seems to be where your question is. Is all this true?

1. You have an instance of SQL Server on the laptop

2. You have a user (UserA) in a Windows group (GroupA)

3. The Windows Group (GroupA) has been added as a login to SQL Server as a Windows account

4. When UserA tries to log in to the local instance of SQL Server on the laptop, they can't get in

5. If you add UserA to the local Instance of SQL Server on the laptop, they can get in

Do I have all that right?

|||

All of that is correct.

Thanks,

-Dave

|||

Then let me ask a few more questions:

1. Is the user a domain Windows user?

2. Which service accounts did you use to start SQL Server on the laptop? Are they starting with a user account or the localsystem account?

|||

The user is a domain Windows user. Originally the laptop was using the local system account as its service account, but I thought that might be the problem so I tried using the same service account (a domain user account that I configured specifically as a SQL Server Service Account) that I use on the server, but unfortunately I got the same results.

Thanks,

-Dave

|||

OK - I think we're getting closer. I'm going to assume the laptop is on the domain, since you say you've added that Windows group to SQL Server as a login. Does the account that you are starting SQL Server with on the laptop have the ability to resolve network names?

To help investigate your problem, make sure you check the logs the system creates. You can read more about that here:

http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=242&rl=1

|||

The laptop is definitely on the domain. As far as the account that I am starting SQL Server with on the laptop having the ability to resolve network names, I'm not sure-how would I find that out?

Thanks,

Dave

|||I'm sure there's an easier way, but I normally just log on as that user, create a local group and then try to add someone from the domain to that local group.|||

Hi,

The SQL Server Service Account that I'm using does have the ability to resolve network names on the laptop.

Thanks,

-Dave

|||

Very odd. At this point, it sounds like you're doing everything properly. It has to be something to do with the security policies on that machine, but without access to it I'm afraid it would take a lot of back-and-forth to figure out where it is. I would suggest checking the logs for the system, using the techniques I outline in this guide:

http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=242&rl=1

If that doesn't help point out the issue, then you may have to open a support call so that someone can gain access to your machine. sorry that I couldn't be more help here.

|||

Dave, I don't know if this will help, but could you check the error message for the login failure in the ERRORLOG file and post here the two lines that describe the state and message of the error?

Thanks
Laurentiu

|||

Thanks for all the suggestions. It turns out that there was something going on with this group (I'm not sure what). I created another group in the same Active Directory location with the same users as members and it works fine.

Thanks,

-Dave

Cannot connect to localhost using Windows Security Group as login

I have a test environment set up at home with a small windows server 2003 Active Directory domain. I created a windows security group on the dc and added myself and another user to the group. I then use this group as a login for SQL Server and add the login to the sysadmin server role. This works exactly as I would expect on the Windows Server computer (which is also the Domain Controller) regardless of which computer I use to connect to this Windows Server computer. However, when I set up the exact same login on the local sql server instance of my client laptop running windows xp pro, the I get an error message (Login failed for user MYDOMAIN\dgolds...) when I attempt to connect to the local instance of SQL server, even though I am able to connect to the instance on the domain controller with no problems using this same client laptop under the same user account. The only way I am able to connect locally on the laptop under this account (which does not have local admin privileges on any box, for testing purposes) is to add the user account separately as a login, rather than as part of a group. I'm curious as to why being a member of a security group that is part of the sysadmin server role does not allow me to connect to the local instance of SQL Server on this client laptop. The windows server computer is running SQL2k5 Enterprise, and the client laptop is running SQL2k5 developer. Any insight into this would be appreciated.

Thanks,

Dave

Let's focus on the laptop for a moment, becuase that seems to be where your question is. Is all this true?

1. You have an instance of SQL Server on the laptop

2. You have a user (UserA) in a Windows group (GroupA)

3. The Windows Group (GroupA) has been added as a login to SQL Server as a Windows account

4. When UserA tries to log in to the local instance of SQL Server on the laptop, they can't get in

5. If you add UserA to the local Instance of SQL Server on the laptop, they can get in

Do I have all that right?

|||

All of that is correct.

Thanks,

-Dave

|||

Then let me ask a few more questions:

1. Is the user a domain Windows user?

2. Which service accounts did you use to start SQL Server on the laptop? Are they starting with a user account or the localsystem account?

|||

The user is a domain Windows user. Originally the laptop was using the local system account as its service account, but I thought that might be the problem so I tried using the same service account (a domain user account that I configured specifically as a SQL Server Service Account) that I use on the server, but unfortunately I got the same results.

Thanks,

-Dave

|||

OK - I think we're getting closer. I'm going to assume the laptop is on the domain, since you say you've added that Windows group to SQL Server as a login. Does the account that you are starting SQL Server with on the laptop have the ability to resolve network names?

To help investigate your problem, make sure you check the logs the system creates. You can read more about that here:

http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=242&rl=1

|||

The laptop is definitely on the domain. As far as the account that I am starting SQL Server with on the laptop having the ability to resolve network names, I'm not sure-how would I find that out?

Thanks,

Dave

|||I'm sure there's an easier way, but I normally just log on as that user, create a local group and then try to add someone from the domain to that local group.|||

Hi,

The SQL Server Service Account that I'm using does have the ability to resolve network names on the laptop.

Thanks,

-Dave

|||

Very odd. At this point, it sounds like you're doing everything properly. It has to be something to do with the security policies on that machine, but without access to it I'm afraid it would take a lot of back-and-forth to figure out where it is. I would suggest checking the logs for the system, using the techniques I outline in this guide:

http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=242&rl=1

If that doesn't help point out the issue, then you may have to open a support call so that someone can gain access to your machine. sorry that I couldn't be more help here.

|||

Dave, I don't know if this will help, but could you check the error message for the login failure in the ERRORLOG file and post here the two lines that describe the state and message of the error?

Thanks
Laurentiu

|||

Thanks for all the suggestions. It turns out that there was something going on with this group (I'm not sure what). I created another group in the same Active Directory location with the same users as members and it works fine.

Thanks,

-Dave

Cannot connect to localhost using Windows Security Group as login

I have a test environment set up at home with a small windows server 2003 Active Directory domain. I created a windows security group on the dc and added myself and another user to the group. I then use this group as a login for SQL Server and add the login to the sysadmin server role. This works exactly as I would expect on the Windows Server computer (which is also the Domain Controller) regardless of which computer I use to connect to this Windows Server computer. However, when I set up the exact same login on the local sql server instance of my client laptop running windows xp pro, the I get an error message (Login failed for user MYDOMAIN\dgolds...) when I attempt to connect to the local instance of SQL server, even though I am able to connect to the instance on the domain controller with no problems using this same client laptop under the same user account. The only way I am able to connect locally on the laptop under this account (which does not have local admin privileges on any box, for testing purposes) is to add the user account separately as a login, rather than as part of a group. I'm curious as to why being a member of a security group that is part of the sysadmin server role does not allow me to connect to the local instance of SQL Server on this client laptop. The windows server computer is running SQL2k5 Enterprise, and the client laptop is running SQL2k5 developer. Any insight into this would be appreciated.

Thanks,

Dave

Let's focus on the laptop for a moment, becuase that seems to be where your question is. Is all this true?

1. You have an instance of SQL Server on the laptop

2. You have a user (UserA) in a Windows group (GroupA)

3. The Windows Group (GroupA) has been added as a login to SQL Server as a Windows account

4. When UserA tries to log in to the local instance of SQL Server on the laptop, they can't get in

5. If you add UserA to the local Instance of SQL Server on the laptop, they can get in

Do I have all that right?

|||

All of that is correct.

Thanks,

-Dave

|||

Then let me ask a few more questions:

1. Is the user a domain Windows user?

2. Which service accounts did you use to start SQL Server on the laptop? Are they starting with a user account or the localsystem account?

|||

The user is a domain Windows user. Originally the laptop was using the local system account as its service account, but I thought that might be the problem so I tried using the same service account (a domain user account that I configured specifically as a SQL Server Service Account) that I use on the server, but unfortunately I got the same results.

Thanks,

-Dave

|||

OK - I think we're getting closer. I'm going to assume the laptop is on the domain, since you say you've added that Windows group to SQL Server as a login. Does the account that you are starting SQL Server with on the laptop have the ability to resolve network names?

To help investigate your problem, make sure you check the logs the system creates. You can read more about that here:

http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=242&rl=1

|||

The laptop is definitely on the domain. As far as the account that I am starting SQL Server with on the laptop having the ability to resolve network names, I'm not sure-how would I find that out?

Thanks,

Dave

|||I'm sure there's an easier way, but I normally just log on as that user, create a local group and then try to add someone from the domain to that local group.|||

Hi,

The SQL Server Service Account that I'm using does have the ability to resolve network names on the laptop.

Thanks,

-Dave

|||

Very odd. At this point, it sounds like you're doing everything properly. It has to be something to do with the security policies on that machine, but without access to it I'm afraid it would take a lot of back-and-forth to figure out where it is. I would suggest checking the logs for the system, using the techniques I outline in this guide:

http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=242&rl=1

If that doesn't help point out the issue, then you may have to open a support call so that someone can gain access to your machine. sorry that I couldn't be more help here.

|||

Dave, I don't know if this will help, but could you check the error message for the login failure in the ERRORLOG file and post here the two lines that describe the state and message of the error?

Thanks
Laurentiu

|||

Thanks for all the suggestions. It turns out that there was something going on with this group (I'm not sure what). I created another group in the same Active Directory location with the same users as members and it works fine.

Thanks,

-Dave

Cannot connect to localhost using Windows Security Group as login

I have a test environment set up at home with a small windows server 2003 Active Directory domain. I created a windows security group on the dc and added myself and another user to the group. I then use this group as a login for SQL Server and add the login to the sysadmin server role. This works exactly as I would expect on the Windows Server computer (which is also the Domain Controller) regardless of which computer I use to connect to this Windows Server computer. However, when I set up the exact same login on the local sql server instance of my client laptop running windows xp pro, the I get an error message (Login failed for user MYDOMAIN\dgolds...) when I attempt to connect to the local instance of SQL server, even though I am able to connect to the instance on the domain controller with no problems using this same client laptop under the same user account. The only way I am able to connect locally on the laptop under this account (which does not have local admin privileges on any box, for testing purposes) is to add the user account separately as a login, rather than as part of a group. I'm curious as to why being a member of a security group that is part of the sysadmin server role does not allow me to connect to the local instance of SQL Server on this client laptop. The windows server computer is running SQL2k5 Enterprise, and the client laptop is running SQL2k5 developer. Any insight into this would be appreciated.

Thanks,

Dave

Let's focus on the laptop for a moment, becuase that seems to be where your question is. Is all this true?

1. You have an instance of SQL Server on the laptop

2. You have a user (UserA) in a Windows group (GroupA)

3. The Windows Group (GroupA) has been added as a login to SQL Server as a Windows account

4. When UserA tries to log in to the local instance of SQL Server on the laptop, they can't get in

5. If you add UserA to the local Instance of SQL Server on the laptop, they can get in

Do I have all that right?

|||

All of that is correct.

Thanks,

-Dave

|||

Then let me ask a few more questions:

1. Is the user a domain Windows user?

2. Which service accounts did you use to start SQL Server on the laptop? Are they starting with a user account or the localsystem account?

|||

The user is a domain Windows user. Originally the laptop was using the local system account as its service account, but I thought that might be the problem so I tried using the same service account (a domain user account that I configured specifically as a SQL Server Service Account) that I use on the server, but unfortunately I got the same results.

Thanks,

-Dave

|||

OK - I think we're getting closer. I'm going to assume the laptop is on the domain, since you say you've added that Windows group to SQL Server as a login. Does the account that you are starting SQL Server with on the laptop have the ability to resolve network names?

To help investigate your problem, make sure you check the logs the system creates. You can read more about that here:

http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=242&rl=1

|||

The laptop is definitely on the domain. As far as the account that I am starting SQL Server with on the laptop having the ability to resolve network names, I'm not sure-how would I find that out?

Thanks,

Dave

|||I'm sure there's an easier way, but I normally just log on as that user, create a local group and then try to add someone from the domain to that local group.|||

Hi,

The SQL Server Service Account that I'm using does have the ability to resolve network names on the laptop.

Thanks,

-Dave

|||

Very odd. At this point, it sounds like you're doing everything properly. It has to be something to do with the security policies on that machine, but without access to it I'm afraid it would take a lot of back-and-forth to figure out where it is. I would suggest checking the logs for the system, using the techniques I outline in this guide:

http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=242&rl=1

If that doesn't help point out the issue, then you may have to open a support call so that someone can gain access to your machine. sorry that I couldn't be more help here.

|||

Dave, I don't know if this will help, but could you check the error message for the login failure in the ERRORLOG file and post here the two lines that describe the state and message of the error?

Thanks
Laurentiu

|||

Thanks for all the suggestions. It turns out that there was something going on with this group (I'm not sure what). I created another group in the same Active Directory location with the same users as members and it works fine.

Thanks,

-Dave