Access to the remote server is denied because the current security context is not trusted.

Hello,

In SQL 2005, from a stored procedure in a local database I am attempting to execute a remote stored procedure in another database on another server. I am getting the error referred to in the Subject when the local stored procedure tries to execute the remote stored procedure. A couple of comments:

The remote database is set up as a linked server in the local database. As part of the linked server definition I selected the 'be made using this security context', and provided a local user name and password.

The remote database is set to Trustworthy.

I have tried every combination of WITH Execute As on the remote stored procedure but nothing works.

I can query against the remote database successfully within Management Studio. I can even execute the remote stored procedure successfully from within M.S., but not from within my local stored procedure when it is run.

Thank you for your help on this - Amos.

I assume you are using a Windows principal for the EXECUTE AS statement, correct? If that is the case, I think I know the problem. When using EXECUTE AS <windows_principal> there is no real authentication for the Windows user:

* If you have a OS older than Windows 2003, the Windows token would really be valid for SQL Server and not a real Windows token

* if you are using Windows 2003, and Kerberos is available, the system should use a S4USelf token and these type of tokens are, as far as I understand these tokens are restricted, and out of the box you should not be able to use them on another machine.

If your scenario falls under the S4USelf token, it may be possible to use delegation and use this token on the remote server (during the remote SP call), but I would personally not recommend it.I would prefer to suggest changing the EXECUTE AS clause to use a SQL principal (SQL authentication should work).

Remember that for remote calls to work with EXECUTE AS, it is necessary to trust the impersonated token on the server, turning on the TRUSTWORTHY bit on the source DB (the DB where the local SP resides) and making sure the DBO has AUTHENTICATE SERVER permission (if DBO is a member of sysadmin, this permission is implicitly granted).

Let us know if this information was of any help or if you have additional questions.

Thanks a lot,

-Raul Garcia

SDE/T

SQL Server Engine

|||

Raul,

Thank you for taking the time to answer. I am getting a bit desperate for an answer!

First let me say that I don't have a great deal of experience in this area (security). Therefore, I might be asking some pretty dumb questions. My first question is this. On my remote stored proc, do I have to use 'WITH EXECUTE AS'? I would rather not if I don't have to. I cannot get this to work whether I use it or not. So, let's start there. Can I get this to work with the Execute As?

Amos.

|||

You don’t have to use EXECUTE AS on the remote SP unless you want to. I am assuming you want to execute always under the exactly same principal (on the local DB) and that’s why you used execute as on the local SP, but as you will always connect as the same principal on the remote machine, using EXECUTE AS will be of little value.Even for the local SP, you don’t need EXECUTE AS unless you want to always use the same principal (i.e. use it as a proxy) to connect to the remote machine and execute the remote SP.

If you prefer, you can describe the problem you want to solve and I will do my best to help you find a solution.

Thanks a lot,

-Raul Garcia

SDE/T

SQL Server Engine

|||

Raul,

You are giving me too much credit :). I only used Execute As to try to get this to work. So, let's go under the assumption I don't need it. Here is my current setup now:

The remote stored proc does not have 'Execute As'|||

I can see one mistake here: the trustworthy bit is enabled on the remote server, but it should be for the local server. Also make sure that if the DBO for the local SP DB is not a member of sysadmin, to grant AUTHENTICATE SERVER to the DBO login.

The TW bit + AUTEHNTICATE SERVER will tell the local server that the impersonated context is valid across the SQL Server instance, and only then it can be used in remote calls.

BTW. What is the impersonated context (EXECUTE AS clause) being used? Is it a Windows principal or a SQL principal?

|||

Raul,

I don't know how to thank you! That was it. My local database was not set to Trustworthy. I actually thought about changing this yesterday but it didn't make any sense to me to do that so I didn't try it.

Amos.

|||

No problem, I am glad I was able to help you resolve this problem.

Please let us know if you have any further questions or feedback.

-Raul Garcia

SDE/T

SQL Server Engine

|||

For additional information on the TRUSTWORTHY bit, see the following whitepaper:

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

Thanks
Laurentiu

|||

Hi,

Great post, only it doesn't fix the problem that I am having. All the criteria above is true to my situation and I have run through the checklist described, but I still receve the "Access to the remote server is denied because the current security context is not trusted" error message.

Is there anything else that I can try?

Thanks

MIke

|||

thats got it.

The Authenticator of the trust is the DBO of the database, if the DBO is not a member of the target db (and trusted) then the error occurs.

By updating the source DBO to one that is trusted I now have working links.

Thanks for all your help peeps.

Mike

|||

Can you explain the solution in more detail?

I am having a similar problem:

I have a Linked server on a SQL 2005 database that connects to an Ingres DB

I am able to run stored procedures manually in management studio but when I schedule a job to run these procedures I get a similar error - Security context is not trusted.

I've set the local database to have Trustworthy bit on. But how can I set the remote server via the linked server object with the Trustworthy bit. Also I have the Security Context on the linked server - with the option - Connections be made with the following security context - and I have provided a username and password that has access to the remote database.

Thanks

Sg

|||

IIRC, I had to set both the local database and the remote database to Trustworthy. In addition, make sure the "RPC" and "RPC Out" options on the Linked Server defintion are set to True.

Amos.

Access to the remote server is denied because the current security context is not trusted.

Hello,

In SQL 2005, from a stored procedure in a local database I am attempting to execute a remote stored procedure in another database on another server. I am getting the error referred to in the Subject when the local stored procedure tries to execute the remote stored procedure. A couple of comments:

The remote database is set up as a linked server in the local database. As part of the linked server definition I selected the 'be made using this security context', and provided a local user name and password.

The remote database is set to Trustworthy.

I have tried every combination of WITH Execute As on the remote stored procedure but nothing works.

I can query against the remote database successfully within Management Studio. I can even execute the remote stored procedure successfully from within M.S., but not from within my local stored procedure when it is run.

Thank you for your help on this - Amos.

I assume you are using a Windows principal for the EXECUTE AS statement, correct? If that is the case, I think I know the problem. When using EXECUTE AS <windows_principal> there is no real authentication for the Windows user:

* If you have a OS older than Windows 2003, the Windows token would really be valid for SQL Server and not a real Windows token

* if you are using Windows 2003, and Kerberos is available, the system should use a S4USelf token and these type of tokens are, as far as I understand these tokens are restricted, and out of the box you should not be able to use them on another machine.

If your scenario falls under the S4USelf token, it may be possible to use delegation and use this token on the remote server (during the remote SP call), but I would personally not recommend it.I would prefer to suggest changing the EXECUTE AS clause to use a SQL principal (SQL authentication should work).

Remember that for remote calls to work with EXECUTE AS, it is necessary to trust the impersonated token on the server, turning on the TRUSTWORTHY bit on the source DB (the DB where the local SP resides) and making sure the DBO has AUTHENTICATE SERVER permission (if DBO is a member of sysadmin, this permission is implicitly granted).

Let us know if this information was of any help or if you have additional questions.

Thanks a lot,

-Raul Garcia

SDE/T

SQL Server Engine

|||

Raul,

Thank you for taking the time to answer. I am getting a bit desperate for an answer!

First let me say that I don't have a great deal of experience in this area (security). Therefore, I might be asking some pretty dumb questions. My first question is this. On my remote stored proc, do I have to use 'WITH EXECUTE AS'? I would rather not if I don't have to. I cannot get this to work whether I use it or not. So, let's start there. Can I get this to work with the Execute As?

Amos.

|||

You don’t have to use EXECUTE AS on the remote SP unless you want to. I am assuming you want to execute always under the exactly same principal (on the local DB) and that’s why you used execute as on the local SP, but as you will always connect as the same principal on the remote machine, using EXECUTE AS will be of little value.Even for the local SP, you don’t need EXECUTE AS unless you want to always use the same principal (i.e. use it as a proxy) to connect to the remote machine and execute the remote SP.

If you prefer, you can describe the problem you want to solve and I will do my best to help you find a solution.

Thanks a lot,

-Raul Garcia

SDE/T

SQL Server Engine

|||

Raul,

You are giving me too much credit :). I only used Execute As to try to get this to work. So, let's go under the assumption I don't need it. Here is my current setup now:

The remote stored proc does not have 'Execute As'|||

I can see one mistake here: the trustworthy bit is enabled on the remote server, but it should be for the local server. Also make sure that if the DBO for the local SP DB is not a member of sysadmin, to grant AUTHENTICATE SERVER to the DBO login.

The TW bit + AUTEHNTICATE SERVER will tell the local server that the impersonated context is valid across the SQL Server instance, and only then it can be used in remote calls.

BTW. What is the impersonated context (EXECUTE AS clause) being used? Is it a Windows principal or a SQL principal?

|||

Raul,

I don't know how to thank you! That was it. My local database was not set to Trustworthy. I actually thought about changing this yesterday but it didn't make any sense to me to do that so I didn't try it.

Amos.

|||

No problem, I am glad I was able to help you resolve this problem.

Please let us know if you have any further questions or feedback.

-Raul Garcia

SDE/T

SQL Server Engine

|||

For additional information on the TRUSTWORTHY bit, see the following whitepaper:

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

Thanks
Laurentiu

|||

Hi,

Great post, only it doesn't fix the problem that I am having. All the criteria above is true to my situation and I have run through the checklist described, but I still receve the "Access to the remote server is denied because the current security context is not trusted" error message.

Is there anything else that I can try?

Thanks

MIke

|||

thats got it.

The Authenticator of the trust is the DBO of the database, if the DBO is not a member of the target db (and trusted) then the error occurs.

By updating the source DBO to one that is trusted I now have working links.

Thanks for all your help peeps.

Mike

|||

Can you explain the solution in more detail?

I am having a similar problem:

I have a Linked server on a SQL 2005 database that connects to an Ingres DB

I am able to run stored procedures manually in management studio but when I schedule a job to run these procedures I get a similar error - Security context is not trusted.

I've set the local database to have Trustworthy bit on. But how can I set the remote server via the linked server object with the Trustworthy bit. Also I have the Security Context on the linked server - with the option - Connections be made with the following security context - and I have provided a username and password that has access to the remote database.

Thanks

Sg

|||

IIRC, I had to set both the local database and the remote database to Trustworthy. In addition, make sure the "RPC" and "RPC Out" options on the Linked Server defintion are set to True.

Amos.

Access to the remote server is denied because the current security context is not trusted.

Hello,

In SQL 2005, from a stored procedure in a local database I am attempting to execute a remote stored procedure in another database on another server. I am getting the error referred to in the Subject when the local stored procedure tries to execute the remote stored procedure. A couple of comments:

The remote database is set up as a linked server in the local database. As part of the linked server definition I selected the 'be made using this security context', and provided a local user name and password.

The remote database is set to Trustworthy.

I have tried every combination of WITH Execute As on the remote stored procedure but nothing works.

I can query against the remote database successfully within Management Studio. I can even execute the remote stored procedure successfully from within M.S., but not from within my local stored procedure when it is run.

Thank you for your help on this - Amos.

I assume you are using a Windows principal for the EXECUTE AS statement, correct? If that is the case, I think I know the problem. When using EXECUTE AS <windows_principal> there is no real authentication for the Windows user:

* If you have a OS older than Windows 2003, the Windows token would really be valid for SQL Server and not a real Windows token

* if you are using Windows 2003, and Kerberos is available, the system should use a S4USelf token and these type of tokens are, as far as I understand these tokens are restricted, and out of the box you should not be able to use them on another machine.

If your scenario falls under the S4USelf token, it may be possible to use delegation and use this token on the remote server (during the remote SP call), but I would personally not recommend it.I would prefer to suggest changing the EXECUTE AS clause to use a SQL principal (SQL authentication should work).

Remember that for remote calls to work with EXECUTE AS, it is necessary to trust the impersonated token on the server, turning on the TRUSTWORTHY bit on the source DB (the DB where the local SP resides) and making sure the DBO has AUTHENTICATE SERVER permission (if DBO is a member of sysadmin, this permission is implicitly granted).

Let us know if this information was of any help or if you have additional questions.

Thanks a lot,

-Raul Garcia

SDE/T

SQL Server Engine

|||

Raul,

Thank you for taking the time to answer. I am getting a bit desperate for an answer!

First let me say that I don't have a great deal of experience in this area (security). Therefore, I might be asking some pretty dumb questions. My first question is this. On my remote stored proc, do I have to use 'WITH EXECUTE AS'? I would rather not if I don't have to. I cannot get this to work whether I use it or not. So, let's start there. Can I get this to work with the Execute As?

Amos.

|||

You don’t have to use EXECUTE AS on the remote SP unless you want to. I am assuming you want to execute always under the exactly same principal (on the local DB) and that’s why you used execute as on the local SP, but as you will always connect as the same principal on the remote machine, using EXECUTE AS will be of little value.Even for the local SP, you don’t need EXECUTE AS unless you want to always use the same principal (i.e. use it as a proxy) to connect to the remote machine and execute the remote SP.

If you prefer, you can describe the problem you want to solve and I will do my best to help you find a solution.

Thanks a lot,

-Raul Garcia

SDE/T

SQL Server Engine

|||

Raul,

You are giving me too much credit :). I only used Execute As to try to get this to work. So, let's go under the assumption I don't need it. Here is my current setup now:

The remote stored proc does not have 'Execute As'|||

I can see one mistake here: the trustworthy bit is enabled on the remote server, but it should be for the local server. Also make sure that if the DBO for the local SP DB is not a member of sysadmin, to grant AUTHENTICATE SERVER to the DBO login.

The TW bit + AUTEHNTICATE SERVER will tell the local server that the impersonated context is valid across the SQL Server instance, and only then it can be used in remote calls.

BTW. What is the impersonated context (EXECUTE AS clause) being used? Is it a Windows principal or a SQL principal?

|||

Raul,

I don't know how to thank you! That was it. My local database was not set to Trustworthy. I actually thought about changing this yesterday but it didn't make any sense to me to do that so I didn't try it.

Amos.

|||

No problem, I am glad I was able to help you resolve this problem.

Please let us know if you have any further questions or feedback.

-Raul Garcia

SDE/T

SQL Server Engine

|||

For additional information on the TRUSTWORTHY bit, see the following whitepaper:

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

Thanks
Laurentiu

|||

Hi,

Great post, only it doesn't fix the problem that I am having. All the criteria above is true to my situation and I have run through the checklist described, but I still receve the "Access to the remote server is denied because the current security context is not trusted" error message.

Is there anything else that I can try?

Thanks

MIke

|||

thats got it.

The Authenticator of the trust is the DBO of the database, if the DBO is not a member of the target db (and trusted) then the error occurs.

By updating the source DBO to one that is trusted I now have working links.

Thanks for all your help peeps.

Mike

|||

Can you explain the solution in more detail?

I am having a similar problem:

I have a Linked server on a SQL 2005 database that connects to an Ingres DB

I am able to run stored procedures manually in management studio but when I schedule a job to run these procedures I get a similar error - Security context is not trusted.

I've set the local database to have Trustworthy bit on. But how can I set the remote server via the linked server object with the Trustworthy bit. Also I have the Security Context on the linked server - with the option - Connections be made with the following security context - and I have provided a username and password that has access to the remote database.

Thanks

Sg

|||

IIRC, I had to set both the local database and the remote database to Trustworthy. In addition, make sure the "RPC" and "RPC Out" options on the Linked Server defintion are set to True.

Amos.

Access to the remote server is denied because the current security context is not trusted.

Hi all,
What I did:
Created a SQL Job that accesses another database on some other server.
I get the error:
Access to the remote server is denied because the current security
context is not trusted. [SQLSTATE 42000] (Error 15274).
I have the remote server as the linked server to my local server.
The login account used for the job step is present on both the servers
(with the role sysadmin)
Any pointers?
All help would be appreciated.
Thanks in anticipation,
Vivek Balagangadharan
Software Engineer,
Fast Track Software Services,
India
Forgot to mention one thing:
I tried executing the same query through my management studio with the
same login, and it works great.
It also works when i try using it from my web application.
But, it doesnt work when i use a SQL job
Thanks,
Vivek Balagangadharan
Software Engineer,
Fast Track Software Services,
India
|||Hi Vivek,
How is security defined on that linked server? Are you using Intergrated
Security (Windows account) or are you using SQL server authentication.
If you are using Intergrated security, then make sure that the account
that runs your SQL Server Agent service has proper rights to the linked
server (is Trusted for delegation).
Regards
Steen Schlter Persson
Database Administrator / System Administrator
vivekbg@.fasttrackteam.com wrote:
> Hi all,
> What I did:
> Created a SQL Job that accesses another database on some other server.
> I get the error:
> Access to the remote server is denied because the current security
> context is not trusted. [SQLSTATE 42000] (Error 15274).
> I have the remote server as the linked server to my local server.
> The login account used for the job step is present on both the servers
> (with the role sysadmin)
> Any pointers?
> All help would be appreciated.
> Thanks in anticipation,
> Vivek Balagangadharan
> Software Engineer,
> Fast Track Software Services,
> India
>
|||Thanks Steen.
I am using SQL authentication and my user is present on both the DB
servers with the role sysadmin.
Now, both these DB servers are on different domains.
But, that still does not explain why it runs from the studio, but not
from the SQL job.
Thanks,
Vivek Balagangadharan
|||And to provide you with more info on the linked server setting, i just
"scripted" the create query for this.
/****** Object: LinkedServer [DB Server 2] Script Date: 06/22/2007
13:02:52 ******/
EXEC master.dbo.sp_addlinkedserver @.server = N'DB Server 2',
@.srvproduct=N'SQL Server'
/* For security reasons the linked server remote logins password is
changed with #### */
EXEC master.dbo.sp_addlinkedsrvlogin @.rmtsrvname=N'DB Server
2',@.useself=N'False',@.locallogin=NULL,@.rmtuser=N'l ogin1',@.rmtpassword='####'
EXEC master.dbo.sp_addlinkedsrvlogin @.rmtsrvname=N'DB Server
2',@.useself=N'False',@.locallogin=N'login1',@.rmtuse r=N'login1',@.rmtpassword='####'
GO
EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
@.optname=N'collation compatible', @.optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
@.optname=N'data access', @.optvalue=N'true'
GO
EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
@.optname=N'dist', @.optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
@.optname=N'pub', @.optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
@.optname=N'rpc', @.optvalue=N'true'
GO
EXEC master.dbo.sp_serveroption @.server=N'DB Server 2', @.optname=N'rpc
out', @.optvalue=N'true'
GO
EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
@.optname=N'sub', @.optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
@.optname=N'connect timeout', @.optvalue=N'0'
GO
EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
@.optname=N'collation name', @.optvalue=null
GO
EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
@.optname=N'lazy schema validation', @.optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
@.optname=N'query timeout', @.optvalue=N'0'
GO
EXEC master.dbo.sp_serveroption @.server=N'DB Server 2', @.optname=N'use
remote collation', @.optvalue=N'true'
|||Hi
I can see that your script creates 2 linkedserver logins where one of
them has a locallogin specified. I'd try to create the linked server
without a local login specified and see if that works (or just drop the
login with a local login specified).
Regards
Steen Schlter Persson
Database Administrator / System Administrator
vivekbg@.fasttrackteam.com wrote:
> And to provide you with more info on the linked server setting, i just
> "scripted" the create query for this.
> /****** Object: LinkedServer [DB Server 2] Script Date: 06/22/2007
> 13:02:52 ******/
> EXEC master.dbo.sp_addlinkedserver @.server = N'DB Server 2',
> @.srvproduct=N'SQL Server'
> /* For security reasons the linked server remote logins password is
> changed with #### */
> EXEC master.dbo.sp_addlinkedsrvlogin @.rmtsrvname=N'DB Server
> 2',@.useself=N'False',@.locallogin=NULL,@.rmtuser=N'l ogin1',@.rmtpassword='####'
> EXEC master.dbo.sp_addlinkedsrvlogin @.rmtsrvname=N'DB Server
> 2',@.useself=N'False',@.locallogin=N'login1',@.rmtuse r=N'login1',@.rmtpassword='####'
> GO
> EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
> @.optname=N'collation compatible', @.optvalue=N'false'
> GO
> EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
> @.optname=N'data access', @.optvalue=N'true'
> GO
> EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
> @.optname=N'dist', @.optvalue=N'false'
> GO
> EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
> @.optname=N'pub', @.optvalue=N'false'
> GO
> EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
> @.optname=N'rpc', @.optvalue=N'true'
> GO
> EXEC master.dbo.sp_serveroption @.server=N'DB Server 2', @.optname=N'rpc
> out', @.optvalue=N'true'
> GO
> EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
> @.optname=N'sub', @.optvalue=N'false'
> GO
> EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
> @.optname=N'connect timeout', @.optvalue=N'0'
> GO
> EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
> @.optname=N'collation name', @.optvalue=null
> GO
> EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
> @.optname=N'lazy schema validation', @.optvalue=N'false'
> GO
> EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
> @.optname=N'query timeout', @.optvalue=N'0'
> GO
> EXEC master.dbo.sp_serveroption @.server=N'DB Server 2', @.optname=N'use
> remote collation', @.optvalue=N'true'
>
|||Thanks Steen.
Yes, initially i had not created any linked server login. But, the job
started failing. That is when i created a linked server login, but
that didn't help either.
I even tried to impersonate a login (since the login was available on
both the servers).
Even forced the connections to use a fixed context (by specifying a
remote server login credential)
This did not work either.
The question that is bothering me is, why is it that the context is
trusted when i use the management studio, but not trusted when i use a
SQL job? (though i use the same login)
Thanks,
Vivek Balagangadharan
|||hmmmm...that sounds a bit strange.
What does the job/script actually do? Could it be that it is trying to
do something on the local/source server that the job hasn't got access
to and that's the error you see rather than an error on the remote
server. I know the error meesage indicates something else, but you never
know..:-).
From where are you executing the job? If you are starting it from your
local PC, could you then try to log on to the server (with e.g. Remote
Desktop) and try to start it from there?
Regards
Steen Schlter Persson
Database Administrator / System Administrator
vivekbg@.fasttrackteam.com wrote:
> Thanks Steen.
> Yes, initially i had not created any linked server login. But, the job
> started failing. That is when i created a linked server login, but
> that didn't help either.
> I even tried to impersonate a login (since the login was available on
> both the servers).
> Even forced the connections to use a fixed context (by specifying a
> remote server login credential)
> This did not work either.
> The question that is bothering me is, why is it that the context is
> trusted when i use the management studio, but not trusted when i use a
> SQL job? (though i use the same login)
> Thanks,
> Vivek Balagangadharan
>
|||Thanks for the reply Steen.
Well, all the job has/should do, is a simple "select count(*) from [DB
Server 2].[DB_name].[dbo].[table_name]" query.
In my job step, I have specified to "run as user" login1, which is
present on both the DBs and belongs to the sysadmin role group.
I was initially running the job from my management studio (which is
not the server which has the job)
Then, I moved to the local server which actually had the SQL Server
agent, created the job all over again (the owner being login1). But,
no success.
I hope I have answered your queries. Let me know if there is some
confusion.
Thanks,
Vivek Balagangadharan
|||Have you tried running the job without specifying a proxy account (Run
As account)?
Regards
Steen Schlter Persson
Database Administrator / System Administrator
vivekbg@.fasttrackteam.com wrote:
> Thanks for the reply Steen.
> Well, all the job has/should do, is a simple "select count(*) from [DB
> Server 2].[DB_name].[dbo].[table_name]" query.
> In my job step, I have specified to "run as user" login1, which is
> present on both the DBs and belongs to the sysadmin role group.
> I was initially running the job from my management studio (which is
> not the server which has the job)
> Then, I moved to the local server which actually had the SQL Server
> agent, created the job all over again (the owner being login1). But,
> no success.
> I hope I have answered your queries. Let me know if there is some
> confusion.
> Thanks,
> Vivek Balagangadharan
>

Access to the remote server is denied because the current security context is not trusted.

Hi all,
What I did:
Created a SQL Job that accesses another database on some other server.
I get the error:
Access to the remote server is denied because the current security
context is not trusted. [SQLSTATE 42000] (Error 15274).
I have the remote server as the linked server to my local server.
The login account used for the job step is present on both the servers
(with the role sysadmin)
Any pointers?
All help would be appreciated.
Thanks in anticipation,
Vivek Balagangadharan
Software Engineer,
Fast Track Software Services,
IndiaForgot to mention one thing:
I tried executing the same query through my management studio with the
same login, and it works great.
It also works when i try using it from my web application.
But, it doesnt work when i use a SQL job :(
Thanks,
Vivek Balagangadharan
Software Engineer,
Fast Track Software Services,
India|||Hi Vivek,
How is security defined on that linked server? Are you using Intergrated
Security (Windows account) or are you using SQL server authentication.
If you are using Intergrated security, then make sure that the account
that runs your SQL Server Agent service has proper rights to the linked
server (is Trusted for delegation).
--
Regards
Steen Schlüter Persson
Database Administrator / System Administrator
vivekbg@.fasttrackteam.com wrote:
> Hi all,
> What I did:
> Created a SQL Job that accesses another database on some other server.
> I get the error:
> Access to the remote server is denied because the current security
> context is not trusted. [SQLSTATE 42000] (Error 15274).
> I have the remote server as the linked server to my local server.
> The login account used for the job step is present on both the servers
> (with the role sysadmin)
> Any pointers?
> All help would be appreciated.
> Thanks in anticipation,
> Vivek Balagangadharan
> Software Engineer,
> Fast Track Software Services,
> India
>|||Thanks Steen.
I am using SQL authentication and my user is present on both the DB
servers with the role sysadmin.
Now, both these DB servers are on different domains.
But, that still does not explain why it runs from the studio, but not
from the SQL job.
Thanks,
Vivek Balagangadharan|||And to provide you with more info on the linked server setting, i just
"scripted" the create query for this.
/****** Object: LinkedServer [DB Server 2] Script Date: 06/22/2007
13:02:52 ******/
EXEC master.dbo.sp_addlinkedserver @.server = N'DB Server 2',
@.srvproduct=N'SQL Server'
/* For security reasons the linked server remote logins password is
changed with #### */
EXEC master.dbo.sp_addlinkedsrvlogin @.rmtsrvname=N'DB Server
2',@.useself=N'False',@.locallogin=NULL,@.rmtuser=N'login1',@.rmtpassword='####'
EXEC master.dbo.sp_addlinkedsrvlogin @.rmtsrvname=N'DB Server
2',@.useself=N'False',@.locallogin=N'login1',@.rmtuser=N'login1',@.rmtpassword='####'
GO
EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
@.optname=N'collation compatible', @.optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
@.optname=N'data access', @.optvalue=N'true'
GO
EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
@.optname=N'dist', @.optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
@.optname=N'pub', @.optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
@.optname=N'rpc', @.optvalue=N'true'
GO
EXEC master.dbo.sp_serveroption @.server=N'DB Server 2', @.optname=N'rpc
out', @.optvalue=N'true'
GO
EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
@.optname=N'sub', @.optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
@.optname=N'connect timeout', @.optvalue=N'0'
GO
EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
@.optname=N'collation name', @.optvalue=null
GO
EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
@.optname=N'lazy schema validation', @.optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
@.optname=N'query timeout', @.optvalue=N'0'
GO
EXEC master.dbo.sp_serveroption @.server=N'DB Server 2', @.optname=N'use
remote collation', @.optvalue=N'true'|||Hi
I can see that your script creates 2 linkedserver logins where one of
them has a locallogin specified. I'd try to create the linked server
without a local login specified and see if that works (or just drop the
login with a local login specified).
--
Regards
Steen Schlüter Persson
Database Administrator / System Administrator
vivekbg@.fasttrackteam.com wrote:
> And to provide you with more info on the linked server setting, i just
> "scripted" the create query for this.
> /****** Object: LinkedServer [DB Server 2] Script Date: 06/22/2007
> 13:02:52 ******/
> EXEC master.dbo.sp_addlinkedserver @.server = N'DB Server 2',
> @.srvproduct=N'SQL Server'
> /* For security reasons the linked server remote logins password is
> changed with #### */
> EXEC master.dbo.sp_addlinkedsrvlogin @.rmtsrvname=N'DB Server
> 2',@.useself=N'False',@.locallogin=NULL,@.rmtuser=N'login1',@.rmtpassword='####'
> EXEC master.dbo.sp_addlinkedsrvlogin @.rmtsrvname=N'DB Server
> 2',@.useself=N'False',@.locallogin=N'login1',@.rmtuser=N'login1',@.rmtpassword='####'
> GO
> EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
> @.optname=N'collation compatible', @.optvalue=N'false'
> GO
> EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
> @.optname=N'data access', @.optvalue=N'true'
> GO
> EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
> @.optname=N'dist', @.optvalue=N'false'
> GO
> EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
> @.optname=N'pub', @.optvalue=N'false'
> GO
> EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
> @.optname=N'rpc', @.optvalue=N'true'
> GO
> EXEC master.dbo.sp_serveroption @.server=N'DB Server 2', @.optname=N'rpc
> out', @.optvalue=N'true'
> GO
> EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
> @.optname=N'sub', @.optvalue=N'false'
> GO
> EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
> @.optname=N'connect timeout', @.optvalue=N'0'
> GO
> EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
> @.optname=N'collation name', @.optvalue=null
> GO
> EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
> @.optname=N'lazy schema validation', @.optvalue=N'false'
> GO
> EXEC master.dbo.sp_serveroption @.server=N'DB Server 2',
> @.optname=N'query timeout', @.optvalue=N'0'
> GO
> EXEC master.dbo.sp_serveroption @.server=N'DB Server 2', @.optname=N'use
> remote collation', @.optvalue=N'true'
>|||Thanks Steen.
Yes, initially i had not created any linked server login. But, the job
started failing. That is when i created a linked server login, but
that didn't help either.
I even tried to impersonate a login (since the login was available on
both the servers).
Even forced the connections to use a fixed context (by specifying a
remote server login credential)
This did not work either.
The question that is bothering me is, why is it that the context is
trusted when i use the management studio, but not trusted when i use a
SQL job? (though i use the same login)
Thanks,
Vivek Balagangadharan|||hmmmm...that sounds a bit strange.
What does the job/script actually do? Could it be that it is trying to
do something on the local/source server that the job hasn't got access
to and that's the error you see rather than an error on the remote
server. I know the error meesage indicates something else, but you never
know..:-).
From where are you executing the job? If you are starting it from your
local PC, could you then try to log on to the server (with e.g. Remote
Desktop) and try to start it from there?
--
Regards
Steen Schlüter Persson
Database Administrator / System Administrator
vivekbg@.fasttrackteam.com wrote:
> Thanks Steen.
> Yes, initially i had not created any linked server login. But, the job
> started failing. That is when i created a linked server login, but
> that didn't help either.
> I even tried to impersonate a login (since the login was available on
> both the servers).
> Even forced the connections to use a fixed context (by specifying a
> remote server login credential)
> This did not work either.
> The question that is bothering me is, why is it that the context is
> trusted when i use the management studio, but not trusted when i use a
> SQL job? (though i use the same login)
> Thanks,
> Vivek Balagangadharan
>|||Thanks for the reply Steen.
Well, all the job has/should do, is a simple "select count(*) from [DB
Server 2].[DB_name].[dbo].[table_name]" query.
In my job step, I have specified to "run as user" login1, which is
present on both the DBs and belongs to the sysadmin role group.
I was initially running the job from my management studio (which is
not the server which has the job)
Then, I moved to the local server which actually had the SQL Server
agent, created the job all over again (the owner being login1). But,
no success.
I hope I have answered your queries. Let me know if there is some
confusion.
Thanks,
Vivek Balagangadharan|||Have you tried running the job without specifying a proxy account (Run
As account)?
--
Regards
Steen Schlüter Persson
Database Administrator / System Administrator
vivekbg@.fasttrackteam.com wrote:
> Thanks for the reply Steen.
> Well, all the job has/should do, is a simple "select count(*) from [DB
> Server 2].[DB_name].[dbo].[table_name]" query.
> In my job step, I have specified to "run as user" login1, which is
> present on both the DBs and belongs to the sysadmin role group.
> I was initially running the job from my management studio (which is
> not the server which has the job)
> Then, I moved to the local server which actually had the SQL Server
> agent, created the job all over again (the owner being login1). But,
> no success.
> I hope I have answered your queries. Let me know if there is some
> confusion.
> Thanks,
> Vivek Balagangadharan
>|||Thanks, I just tried and it returns me an error that the windows
account is invalid. (Login failed)
That's because the windows account on local server is not available on
remote server.
Thanks,
Vivek Balagangadharan|||That doesn't make sense. When your Linked Server is setup to use a SQl
Server account, then this account needs to exists on the remote server.
When you then use the linked server, it doesn't use any Windows
accounts. I'm accesing a number of remote servers from many different
servers and I'm always using SQL Server authentication for this. Then
there are no Windows/AD account involved. That works fine even to
servers in our DMZ where we (of course) have a seperate domain that
knows nothing about any of our "normal" domains.
Try to set up your linked server to only use SQL Server authentication
and then make sure that the account you are using exists (and with the
same password) on the remote server. Then try to run the query from
QA/Management Studio to verify that it works. Then try to create a job
step that just runs that query and with no Run As/proxy account defined.
--
Regards
Steen Schlüter Persson
Database Administrator / System Administrator
vivekbg@.fasttrackteam.com wrote:
> Thanks, I just tried and it returns me an error that the windows
> account is invalid. (Login failed)
> That's because the windows account on local server is not available on
> remote server.
> Thanks,
> Vivek Balagangadharan
>|||Thank you Steen! It works now :D
Actually, it was a combination of a couple of things.
1) Remove the run as 'login1' for the step (which i started trying
after your post :) )
2) Force all the connections to use a fixed context (by specifying
login1 and his password) in the linked server properties.
And I get this message: "Executed as user: NT AUTHORITY\SYSTEM. The
step succeeded."
:) :) :)
Also, in my desperate attempt to get the code working, I had
introduced "Execute as user = 'login1' " in my sql query. I had to do
away with this too.
Thanks for the quick and continuous help.
Cheers,
Vivek Balagangadharan
Software Engineer,
Fast Track Software Services,
India|||Good to hear that it finally worked...:-).
--
Regards
Steen Schlüter Persson
Database Administrator / System Administrator
vivekbg@.fasttrackteam.com wrote:
> Thank you Steen! It works now :D
> Actually, it was a combination of a couple of things.
> 1) Remove the run as 'login1' for the step (which i started trying
> after your post :) )
> 2) Force all the connections to use a fixed context (by specifying
> login1 and his password) in the linked server properties.
> And I get this message: "Executed as user: NT AUTHORITY\SYSTEM. The
> step succeeded."
> :) :) :)
> Also, in my desperate attempt to get the code working, I had
> introduced "Execute as user = 'login1' " in my sql query. I had to do
> away with this too.
> Thanks for the quick and continuous help.
> Cheers,
> Vivek Balagangadharan
> Software Engineer,
> Fast Track Software Services,
> India
>

Access to the ADO.net Managed Provider SqlClientFactory was denied

In a previous post in Installation and Setup I was having problems just getting an ASP.NET 2.0 app to run on my web server. Now I'm having some different weird security issues.

I'm getting this message when just trying to open a database and put its contents into a gridview.

Access to the ADO.net Managed Provider 'SqlClientFactory' was denied in the data source with ID 'sqlEmployees' because of security settings.

I think this may have to do with our web server and our SQL server being separate machines. That always gives us issues. But I have impersonation=true in my web.config along with windows authentication and I have SQL Server configured with Windows and SQL authentication so things should be right, I'm thinking.

Any ideas??

I guess I stumped everyone. Thanks anyways.|||

Did you find the solution? If so please post it, so that it will help others :)

|||Had the same problem. There was a web.config in the root directory, deleted it and solved the problem

Access to snapshot tempfiles is denied

I take a snapshot of a report an it views fine the first time but I get the
following error on subsequent viewings:
An internal error occurred on the report server. See the error log for more
details. (rsInternalError) Get Online Help
Access to the path "C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\RSTempFiles\RSFile_6b4351c3-0cfb-4c51-bda1-ac280f1d7eea" is denied.
where the name of the file changes when i re-snapshot it. I've checked the
permissions on the RSTempFiles folder and both the System and ASPNET have
Full Control over it.
Any ideas why this is still happening?
TIA,
Dan Fell.Has anyone solved this issue? I am having the same exact problem with users
who are browsers.
"Dan Fell" wrote:
> I take a snapshot of a report an it views fine the first time but I get the
> following error on subsequent viewings:
> An internal error occurred on the report server. See the error log for more
> details. (rsInternalError) Get Online Help
> Access to the path "C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\RSTempFiles\RSFile_6b4351c3-0cfb-4c51-bda1-ac280f1d7eea" is denied.
> where the name of the file changes when i re-snapshot it. I've checked the
> permissions on the RSTempFiles folder and both the System and ASPNET have
> Full Control over it.
> Any ideas why this is still happening?
> TIA,
> Dan Fell.|||I am having the same exact problem too with snapshots but it doesn't
happen with all the reports. I am assuming that it's a new issue with
reporting services SP2, because snapshots always worked for me prior to
upgrading to SP2. Any help is greatly appreciated. Thanks.
T Robichaux wrote:
> Has anyone solved this issue? I am having the same exact problem with users
> who are browsers.
> "Dan Fell" wrote:
> >
> > I take a snapshot of a report an it views fine the first time but I get the
> > following error on subsequent viewings:
> >
> > An internal error occurred on the report server. See the error log for more
> > details. (rsInternalError) Get Online Help
> > Access to the path "C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> > Services\RSTempFiles\RSFile_6b4351c3-0cfb-4c51-bda1-ac280f1d7eea" is denied.
> >
> > where the name of the file changes when i re-snapshot it. I've checked the
> > permissions on the RSTempFiles folder and both the System and ASPNET have
> > Full Control over it.
> >
> > Any ideas why this is still happening?
> >
> > TIA,
> >
> > Dan Fell.|||I had the same Problem: Only one of many reports with the same settings
as the others (render with temporary copy for 30 min) creates always a
file in the RSTempFiles Folder.
I checked the Readme Files and found that since SP1 (section 4.4.4 New
Configuration Settings in sp2Readme_EN.htm) there are settings for
FileSharing.
I added the settings to the configuration
...
<Add Key="WebServiceUseFileShareStorage" Value="false" />
...
<WindowsServiceUseFileShareStorage>False</WindowsServiceUseFileShareStorage>
<FileShareStorageLocation>
<Path> XXXXX </Path>
</FileShareStorageLocation>
but it still creates the temporary file. You can see that the settings
are regarded when you change the Path. Then the tempfile is placed there
and the errormessage shows the access denied for this path. Either the
setting for the useFileShare = false is ignored or there is some other
setting (in the report?) which "overwrites" the setting.
WORKAROUND:
I gave read permission to everyone on the folder
C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\RSTempFiles
and it works.
System:
SQL Server 2000, Reporting Services SP2 on as w2k Server, Windows 2003
AD, Integrated Security for SQLServer and IIS, mixed language (englisch,
german) for OS and Applications.
I hope the workaround helps and I still wait for a better solution or
explanation for this file creation.
Best regards,
Markus Mahlitz
Vasu Bojja schrieb:
> I am having the same exact problem too with snapshots but it doesn't
> happen with all the reports. I am assuming that it's a new issue with
> reporting services SP2, because snapshots always worked for me prior to
> upgrading to SP2. Any help is greatly appreciated. Thanks.
>
> T Robichaux wrote:
>> Has anyone solved this issue? I am having the same exact problem with users
>> who are browsers.
>> "Dan Fell" wrote:
>> I take a snapshot of a report an it views fine the first time but I get the
>> following error on subsequent viewings:
>> An internal error occurred on the report server. See the error log for more
>> details. (rsInternalError) Get Online Help
>> Access to the path "C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
>> Services\RSTempFiles\RSFile_6b4351c3-0cfb-4c51-bda1-ac280f1d7eea" is denied.
>> where the name of the file changes when i re-snapshot it. I've checked the
>> permissions on the RSTempFiles folder and both the System and ASPNET have
>> Full Control over it.
>> Any ideas why this is still happening?
>> TIA,
>> Dan Fell.
>

Access to RSReportServer.config is denied

Dear All,

i am a new in the SSRS , and i face a problem when i try the link http://localhost/reportserver

an error message appear as the following

The report server has encountered a configuration error. See the report server log files for more information. (rsServerConfigurationError)

Access to the path 'C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\RSReportServer.config' is denied

(i am accessing my PC with a user that under domain differ from my local domain i dont know that if the information help or not )

i dont know what i do , but i excepect someone answer me soon.

Best wishes and sorry for the long talking

Maylo

http://prologika.com/CS/blogs/blog/archive/2007/07/12/ssrs-setup-woes.aspx

|||

About the Question i had asked ,

i found its solution and know what was the problem,

so i like to share it with You all ,

all i have done is setting the Reporting Services Configuration that was need to be configure

you can find it in the following path:

from the start menu ==> All program ==>Microsoft SQL Server 2005 ==>Configuration Tools ==>Reporting Services Configuration

in my case most of the configration Was invalid and not configure right so i Reconfigure it and then everything is great after that.

Regards,

Maylo

Access to ReportManager\bin is denied

There has been a few posts like this. I have given ASPNET access to the
folder.
Here is the long message...
Access to the path "C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportManager\bin" is denied.
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.UnauthorizedAccessException: Access to the path
"C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportManager\bin" is denied.
ASP.NET is not authorized to access the requested resource. Consider
granting access rights to the resource to the ASP.NET request identity.
ASP.NET has a base process identity (typically {MACHINE}\ASPNET on IIS 5 or
Network Service on IIS 6) that is used if the application is not
impersonating. If the application is impersonating via <identity
impersonate="true"/>, the identity will be the anonymous user (typically
IUSR_MACHINENAME) or the authenticated request user.
To grant ASP.NET write access to a file, right-click the file in Explorer,
choose "Properties" and select the Security tab. Click "Add" to add the
appropriate user or group. Highlight the ASP.NET account, and check the boxes
for the desired access.
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:
[UnauthorizedAccessException: Access to the path "C:\Program Files\Microsoft
SQL Server\MSSQL\Reporting Services\ReportManager\bin" is denied.]
System.IO.__Error.WinIOError(Int32 errorCode, String str) +393
System.IO.Directory.InternalGetFileDirectoryNames(String fullPath, String
userPath, Boolean file) +229
System.IO.Directory.InternalGetDirectories(String path, String userPath,
String searchPattern) +24
System.IO.Directory.GetDirectories(String path, String searchPattern) +477
Microsoft.ReportingServices.Diagnostics.Localization.GetInstalledCultures()
Microsoft.ReportingServices.Diagnostics.Localization..cctor()
[TypeInitializationException: The type initializer for
"Microsoft.ReportingServices.Diagnostics.Localization" threw an exception.]
Microsoft.ReportingServices.Diagnostics.Localization.SetCultureFromPriorityList(String[] localeList) +0
Microsoft.ReportingServices.UI.GlobalApp.Application_BeginRequest(Object
sender, EventArgs e)
System.Web.SyncEventExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute() +60
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
completedSynchronously) +87I too have just installed and received the same message. Any help appreciated.
"CraigZello" wrote:
> There has been a few posts like this. I have given ASPNET access to the
> folder.
> Here is the long message...
> Access to the path "C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportManager\bin" is denied.
> 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.UnauthorizedAccessException: Access to the path
> "C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportManager\bin" is denied.
> ASP.NET is not authorized to access the requested resource. Consider
> granting access rights to the resource to the ASP.NET request identity.
> ASP.NET has a base process identity (typically {MACHINE}\ASPNET on IIS 5 or
> Network Service on IIS 6) that is used if the application is not
> impersonating. If the application is impersonating via <identity
> impersonate="true"/>, the identity will be the anonymous user (typically
> IUSR_MACHINENAME) or the authenticated request user.
> To grant ASP.NET write access to a file, right-click the file in Explorer,
> choose "Properties" and select the Security tab. Click "Add" to add the
> appropriate user or group. Highlight the ASP.NET account, and check the boxes
> for the desired access.
> 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:
>
> [UnauthorizedAccessException: Access to the path "C:\Program Files\Microsoft
> SQL Server\MSSQL\Reporting Services\ReportManager\bin" is denied.]
> System.IO.__Error.WinIOError(Int32 errorCode, String str) +393
> System.IO.Directory.InternalGetFileDirectoryNames(String fullPath, String
> userPath, Boolean file) +229
> System.IO.Directory.InternalGetDirectories(String path, String userPath,
> String searchPattern) +24
> System.IO.Directory.GetDirectories(String path, String searchPattern) +477
> Microsoft.ReportingServices.Diagnostics.Localization.GetInstalledCultures()
> Microsoft.ReportingServices.Diagnostics.Localization..cctor()
> [TypeInitializationException: The type initializer for
> "Microsoft.ReportingServices.Diagnostics.Localization" threw an exception.]
> Microsoft.ReportingServices.Diagnostics.Localization.SetCultureFromPriorityList(String[] localeList) +0
> Microsoft.ReportingServices.UI.GlobalApp.Application_BeginRequest(Object
> sender, EventArgs e)
> System.Web.SyncEventExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute() +60
> System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
> completedSynchronously) +87
>
>

Access to "C:/etc/etc/etc.rptproj.user" is denied

Hi All!!

I have recently come across the following problem when attempting to access the solution file for the project in question. I double click to access the file and VS2003 fires up, only for it to give me the above warning. At which point nothing is loaded in the tree!

When I check things out they do show up in Source Safe but if I need to add any new reports (which I do), I am unable to add them...

Cany anyone shed any light on the matter?

Thanks a million!!

I believe this answers your question:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=988559&SiteID=1

|||Issue been resolved thanks for the suggestion

Access is denied: 'Microsoft.Samples.ReportingServices.CustomSecur

I am installing Reporting Services on a Veritas cluster environment on a
named Instance of SQL Server. The installation seems to go OK, but
afterwards when I try to call up the ReportManager I get this error:
Access is denied: 'Microsoft.Samples.ReportingServices.CustomSecurity'
I'm using a Domain Account with administrator privlidges, so I'm not sure
what to do next? Can anyone help?
thanksHere, I think, your report manager is somehow refering to custom
security extension which is configured in configuration files. Please
check if ur RM is pointing to proper server.
Thanks,
Mahesh

Access is denied: 'Interop.ADODB'.

I am using a com component in my asp.net programme and it was working fine for many days . now I am getting following error .

Source Error:

Line 196: <add assembly="System.EnterpriseServices, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>Line 197: <add assembly="System.Web.Mobile, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>Line 198: <add assembly="*"/>Line 199: </assemblies>Line 200: </compilation>

Source File: c:\windows\microsoft.net\framework\v1.1.4322\Config\machine.config Line: 198

Assembly Load Trace: The following information can be helpful to determine why the assembly 'Interop.ADODB' could not be loaded.

=== Pre-bind state information ===LOG: DisplayName = Interop.ADODB (Partial)LOG: Appbase = file:///e:/inetpub/wwwroot/SAPTRainingLOG: Initial PrivatePath = binCalling assembly : (Unknown).=== LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind).LOG: Post-policy reference: Interop.ADODBLOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET Files/saptraining/8932fe97/1bed5ea1/Interop.ADODB.DLL.LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET Files/saptraining/8932fe97/1bed5ea1/Interop.ADODB/Interop.ADODB.DLL.LOG: Attempting download of new URL file:///e:/inetpub/wwwroot/SAPTRaining/bin/Interop.ADODB.DLL.LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind).LOG: Post-policy reference: Interop.ADODB, Version=2.6.0.0, Culture=neutral, PublicKeyToken=null

---

Version Information: Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET Version:1.1.4322.2300

How this can be solved ? Please help

Something has probably changed.

Check that the config file still contains a valid configuration, and that the file(s) that are needed for your app still are at the expected place(s). ie paths, filenames etc...

/Kenneth

Access is denied. [0x80070005]

Hi frnds,

I am having a SQL 2005 instance on win2003 server.

SQL Server 2005, Standard Edition with SP1
Windows Server 2003, Standard Edition with SP1

2 days back, all services went down and I was not able to see anything in logs,how they went down? I restarted all the SQL Services again thru services.msc but when I am trying to open 'SQL Server Configuration Manager'.... .I am getting this error...

Cannot connect to WMI provider.You do not have permission or the server is unreachable. Note that you can only manage SQL Server 2005 servers with SQL Server Configuration Manager.
Access is denied. [0x80070005]

I googled and got some good links about this error...
1 - http://www.sql- server-performan ce.com/faq/ sqlviewfaq. aspx?faqid= 296

2 - http://forums. microsoft. com/MSDN/ ShowPost. aspx?PostID= 142375&SiteID= 1

3 - http://www.ocforums .com/showthread. php?t=482307

I followed but didn't get success...has someone faced this issue and resolved also plz guide me......

And one more thing......sql services are running on this machine 'A' but Start, Stop, Pause, Resume and Restart option are not highlighted on this instance. I connected one another instance 'B' on this machine and got same issue (options were not highlighted) but when I opened that perticular machine where that instance 'B' is installed, i was able to see all option runable so i registered that instance 'A' on 'B' machine and got here also I was not able to see these option highlighted only for 'A'...

Please help me....a lot of thanks to all of you...

Thanks & Regards,
Mohd Rizwan

frnds...

finally I got success to resolve my issue.....first I run this command thru command prompt....

secedit /configure /cfg %windir%\repair\secsetup.inf /db secsetup.sdb /verbose

then re-started the windows and then run this command from command prompt....

C:\Program Files\Microsoft SQL Server\90\Shared>mofcomp "C:\Program Files\Microsoft SQL Server\90\Shared\sqlmgmproviderxpsp2up.mof"

I got this idea thru this link..
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1721211&SiteID=1

Thanks you.........

Rizwan................

Access is denied. [0x80070005]

Hi frnds,

I am having a SQL 2005 instance on win2003 server.

SQL Server 2005, Standard Edition with SP1
Windows Server 2003, Standard Edition with SP1

2 days back, all services went down and I was not able to see anything in logs,how they went down? I restarted all the SQL Services again thru services.msc but when I am trying to open 'SQL Server Configuration Manager'.... .I am getting this error...

Cannot connect to WMI provider.You do not have permission or the server is unreachable. Note that you can only manage SQL Server 2005 servers with SQL Server Configuration Manager.
Access is denied. [0x80070005]

I googled and got some good links about this error...
1 - http://www.sql- server-performan ce.com/faq/ sqlviewfaq. aspx?faqid= 296

2 - http://forums. microsoft. com/MSDN/ ShowPost. aspx?PostID= 142375&SiteID= 1

3 - http://www.ocforums .com/showthread. php?t=482307

I followed but didn't get success...has someone faced this issue and resolved also plz guide me......

And one more thing......sql services are running on this machine 'A' but Start, Stop, Pause, Resume and Restart option are not highlighted on this instance. I connected one another instance 'B' on this machine and got same issue (options were not highlighted) but when I opened that perticular machine where that instance 'B' is installed, i was able to see all option runable so i registered that instance 'A' on 'B' machine and got here also I was not able to see these option highlighted only for 'A'...

Please help me....a lot of thanks to all of you...

Thanks & Regards,
Mohd Rizwan

Hi,

by using the The WMI Diagnosis Utility it will give your more information about your WMI provider

BTW, what about installing the client tools on another box?

|||

Thanks to reply....

finally I got success to resolve my issue.....first I run this command thru command prompt....

secedit /configure /cfg %windir%\repair\secsetup.inf /db secsetup.sdb /verbose

then re-started the windows and then run this command from command prompt....

C:\Program Files\Microsoft SQL Server\90\Shared>mofcomp "C:\Program Files\Microsoft SQL Server\90\Shared\sqlmgmproviderxpsp2up.mof"

I got this idea thru this link..
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1721211&SiteID=1

Thanks once again for your kind help...

Access is Denied writing bak file to another disk

We have been writing a nightly bak file to our backup server without a
problem. We are now getting Error = 5 Access is denied.
BACKUP DATABASE [ABCDE] TO DISK = N'F:\LNCENTER\C$\AURIOBAK Backup
files\MP100BACK.BAK' WITH NOINIT , NOUNLOAD , NAME = N'MP100', SKIP ,
STATS = 10, NOFORMAT
It has been working fine until both servers were added to a domain. Using
either a local admin account or domain account does not correct the problem.
SQL is running under the local account. Production server is running SQL2000
and Win2000. Backup server running SQL2000 and Win 2003. Any ideas would be
greatly appreciated. Thank you.FRR wrote:
> We have been writing a nightly bak file to our backup server without a
> problem. We are now getting Error = 5 Access is denied.
> BACKUP DATABASE [ABCDE] TO DISK = N'F:\LNCENTER\C$\AURIOBAK Backup
> files\MP100BACK.BAK' WITH NOINIT , NOUNLOAD , NAME = N'MP100', SKIP ,
> STATS = 10, NOFORMAT
> It has been working fine until both servers were added to a domain. Using
> either a local admin account or domain account does not correct the problem.
> SQL is running under the local account. Production server is running SQL2000
> and Win2000. Backup server running SQL2000 and Win 2003. Any ideas would be
> greatly appreciated. Thank you.
First off, don't use a drive mapping (i.e. F:), that just adds
complexity - backup straight to the UNC path \\servername\LNCENTER...
Second, SQL running under a local account won't have access to network
resources. Create a domain account for it to run under, and give that
domain account access to the network share.|||SQL Services should run under domain account and use UNC instead of drive
letters. The domain account that SQL runs under must have permissions to the
destination folder including a share if one is used.
"FRR" wrote:
> We have been writing a nightly bak file to our backup server without a
> problem. We are now getting Error = 5 Access is denied.
> BACKUP DATABASE [ABCDE] TO DISK = N'F:\LNCENTER\C$\AURIOBAK Backup
> files\MP100BACK.BAK' WITH NOINIT , NOUNLOAD , NAME = N'MP100', SKIP ,
> STATS = 10, NOFORMAT
> It has been working fine until both servers were added to a domain. Using
> either a local admin account or domain account does not correct the problem.
> SQL is running under the local account. Production server is running SQL2000
> and Win2000. Backup server running SQL2000 and Win 2003. Any ideas would be
> greatly appreciated. Thank you.|||Thanks for the info.
"Jeff Ericson" wrote:
> SQL Services should run under domain account and use UNC instead of drive
> letters. The domain account that SQL runs under must have permissions to the
> destination folder including a share if one is used.
> "FRR" wrote:
> > We have been writing a nightly bak file to our backup server without a
> > problem. We are now getting Error = 5 Access is denied.
> >
> > BACKUP DATABASE [ABCDE] TO DISK = N'F:\LNCENTER\C$\AURIOBAK Backup
> > files\MP100BACK.BAK' WITH NOINIT , NOUNLOAD , NAME = N'MP100', SKIP ,
> > STATS = 10, NOFORMAT
> >
> > It has been working fine until both servers were added to a domain. Using
> > either a local admin account or domain account does not correct the problem.
> > SQL is running under the local account. Production server is running SQL2000
> > and Win2000. Backup server running SQL2000 and Win 2003. Any ideas would be
> > greatly appreciated. Thank you.|||SQL starts up fine with the domain account, however I am now getting error
17052 'you do not have sufficient operating system permission to open the SQL
ServerAgent status event.' I have a tape backup scheduled, which is running
but I can't see that from within EM - SQL Server Agent. I changed the MSSQL
Server service to run under the domain account. Is there something else I
need to do? The doomain account has local admin rights. Thank you for any
help.
"FRR" wrote:
> Thanks for the info.
> "Jeff Ericson" wrote:
> > SQL Services should run under domain account and use UNC instead of drive
> > letters. The domain account that SQL runs under must have permissions to the
> > destination folder including a share if one is used.
> >
> > "FRR" wrote:
> >
> > > We have been writing a nightly bak file to our backup server without a
> > > problem. We are now getting Error = 5 Access is denied.
> > >
> > > BACKUP DATABASE [ABCDE] TO DISK = N'F:\LNCENTER\C$\AURIOBAK Backup
> > > files\MP100BACK.BAK' WITH NOINIT , NOUNLOAD , NAME = N'MP100', SKIP ,
> > > STATS = 10, NOFORMAT
> > >
> > > It has been working fine until both servers were added to a domain. Using
> > > either a local admin account or domain account does not correct the problem.
> > > SQL is running under the local account. Production server is running SQL2000
> > > and Win2000. Backup server running SQL2000 and Win 2003. Any ideas would be
> > > greatly appreciated. Thank you.|||FRR wrote:
> SQL starts up fine with the domain account, however I am now getting error
> 17052 'you do not have sufficient operating system permission to open the SQL
> ServerAgent status event.' I have a tape backup scheduled, which is running
> but I can't see that from within EM - SQL Server Agent. I changed the MSSQL
> Server service to run under the domain account. Is there something else I
> need to do? The doomain account has local admin rights. Thank you for any
> help.
Did you also change the SQLSERVERAGENT service account? Look up
"Setting up Windows Services Accounts" in Books Online. There are
specific permissions that the domain account requires on the local
machine in order to run the services.
--
Tracy McKibben
MCDBA
http://www.realsqlguy.com

Access is Denied writing bak file to another disk

FRR wrote:
> We have been writing a nightly bak file to our backup server without a
> problem. We are now getting Error = 5 Access is denied.
> BACKUP DATABASE [ABCDE] TO DISK = N'F:\LNCENTER\C$\AURIOBAK Backup
> files\MP100BACK.BAK' WITH NOINIT , NOUNLOAD , NAME = N'MP100', SKIP ,
> STATS = 10, NOFORMAT
> It has been working fine until both servers were added to a domain. Using
> either a local admin account or domain account does not correct the proble
m.
> SQL is running under the local account. Production server is running SQL2
000
> and Win2000. Backup server running SQL2000 and Win 2003. Any ideas would
be
> greatly appreciated. Thank you.
First off, don't use a drive mapping (i.e. F, that just adds
complexity - backup straight to the UNC path \\servername\LNCENTER...
Second, SQL running under a local account won't have access to network
resources. Create a domain account for it to run under, and give that
domain account access to the network share.SQL Services should run under domain account and use UNC instead of drive
letters. The domain account that SQL runs under must have permissions to th
e
destination folder including a share if one is used.
"FRR" wrote:

> We have been writing a nightly bak file to our backup server without a
> problem. We are now getting Error = 5 Access is denied.
> BACKUP DATABASE [ABCDE] TO DISK = N'F:\LNCENTER\C$\AURIOBAK Backup
> files\MP100BACK.BAK' WITH NOINIT , NOUNLOAD , NAME = N'MP100', SKIP ,
> STATS = 10, NOFORMAT
> It has been working fine until both servers were added to a domain. Using
> either a local admin account or domain account does not correct the proble
m.
> SQL is running under the local account. Production server is running SQL2
000
> and Win2000. Backup server running SQL2000 and Win 2003. Any ideas would
be
> greatly appreciated. Thank you.|||We have been writing a nightly bak file to our backup server without a
problem. We are now getting Error = 5 Access is denied.
BACKUP DATABASE [ABCDE] TO DISK = N'F:\LNCENTER\C$\AURIOBAK Backup
files\MP100BACK.BAK' WITH NOINIT , NOUNLOAD , NAME = N'MP100', SKIP ,
STATS = 10, NOFORMAT
It has been working fine until both servers were added to a domain. Using
either a local admin account or domain account does not correct the problem.
SQL is running under the local account. Production server is running SQL200
0
and Win2000. Backup server running SQL2000 and Win 2003. Any ideas would b
e
greatly appreciated. Thank you.|||FRR wrote:
> We have been writing a nightly bak file to our backup server without a
> problem. We are now getting Error = 5 Access is denied.
> BACKUP DATABASE [ABCDE] TO DISK = N'F:\LNCENTER\C$\AURIOBAK Backup
> files\MP100BACK.BAK' WITH NOINIT , NOUNLOAD , NAME = N'MP100', SKIP ,
> STATS = 10, NOFORMAT
> It has been working fine until both servers were added to a domain. Using
> either a local admin account or domain account does not correct the proble
m.
> SQL is running under the local account. Production server is running SQL2
000
> and Win2000. Backup server running SQL2000 and Win 2003. Any ideas would
be
> greatly appreciated. Thank you.
First off, don't use a drive mapping (i.e. F, that just adds
complexity - backup straight to the UNC path \\servername\LNCENTER...
Second, SQL running under a local account won't have access to network
resources. Create a domain account for it to run under, and give that
domain account access to the network share.|||SQL Services should run under domain account and use UNC instead of drive
letters. The domain account that SQL runs under must have permissions to th
e
destination folder including a share if one is used.
"FRR" wrote:

> We have been writing a nightly bak file to our backup server without a
> problem. We are now getting Error = 5 Access is denied.
> BACKUP DATABASE [ABCDE] TO DISK = N'F:\LNCENTER\C$\AURIOBAK Backup
> files\MP100BACK.BAK' WITH NOINIT , NOUNLOAD , NAME = N'MP100', SKIP ,
> STATS = 10, NOFORMAT
> It has been working fine until both servers were added to a domain. Using
> either a local admin account or domain account does not correct the proble
m.
> SQL is running under the local account. Production server is running SQL2
000
> and Win2000. Backup server running SQL2000 and Win 2003. Any ideas would
be
> greatly appreciated. Thank you.|||Thanks for the info.
"Jeff Ericson" wrote:
[vbcol=seagreen]
> SQL Services should run under domain account and use UNC instead of drive
> letters. The domain account that SQL runs under must have permissions to
the
> destination folder including a share if one is used.
> "FRR" wrote:
>|||SQL starts up fine with the domain account, however I am now getting error
17052 'you do not have sufficient operating system permission to open the SQ
L
ServerAgent status event.' I have a tape backup scheduled, which is runnin
g
but I can't see that from within EM - SQL Server Agent. I changed the MSSQL
Server service to run under the domain account. Is there something else I
need to do? The doomain account has local admin rights. Thank you for any
help.
"FRR" wrote:
[vbcol=seagreen]
> Thanks for the info.
> "Jeff Ericson" wrote:
>|||FRR wrote:
> SQL starts up fine with the domain account, however I am now getting error
> 17052 'you do not have sufficient operating system permission to open the
SQL
> ServerAgent status event.' I have a tape backup scheduled, which is runn
ing
> but I can't see that from within EM - SQL Server Agent. I changed the MSS
QL
> Server service to run under the domain account. Is there something else I
> need to do? The doomain account has local admin rights. Thank you for an
y
> help.
Did you also change the SQLSERVERAGENT service account? Look up
"Setting up Windows Services Accounts" in Books Online. There are
specific permissions that the domain account requires on the local
machine in order to run the services.
Tracy McKibben
MCDBA
http://www.realsqlguy.com

Access is denied when trying to restore Anaylsis Services 2005 Databases

I'm getting a "access is denied" error when I try to create a new analysis services 2005 database by restoring one from a backup created from a different server. I can restore a backup created from the same machine w/o any problems. The login I'm using is a domain admin account.

Both machine is running SQL 2005 SP2. Any help would be appreciated.

Thanks,

Henry

Hello! I recommend you to use the BI-Dev project instead and deploy it on a new server. Delete any roles you have in the project because I think they are the cause of problem.

I think that there is an issue with moving cubes between servers and the cube roles.

HTH

Thomas Ivarsson

access is denied when starting service

We have a user who could start and stop the sql server service through EM at
one time and then he started getting an "error 5 (access is denied) occurred
while performing this service operation on the MSSQLServer service."
I removed his login and created a new one for him and gave him sysadmin
permissions but he still gets the same error when trying to start the
service.
Any ideas?
Thanks,
--
Dan D.Starting/ stopping services are OS specific. Make sure he's allowed to do
this at the OS level, also make sure that his password is correct in EM. Did
he change his password since the lat time he was able to do this?
--
TIA,
ChrisR
"Dan D." wrote:

> We have a user who could start and stop the sql server service through EM
at
> one time and then he started getting an "error 5 (access is denied) occurr
ed
> while performing this service operation on the MSSQLServer service."
> I removed his login and created a new one for him and gave him sysadmin
> permissions but he still gets the same error when trying to start the
> service.
> Any ideas?
> Thanks,
> --
> Dan D.|||I saw this recently when some of our users switched to a new Win 2003
domain.
We had forgotten to set them up in sql server.
Paul
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:7BB943F7-C48F-406A-A44D-22C200686A8C@.microsoft.com...[vbcol=seagreen]
> Starting/ stopping services are OS specific. Make sure he's allowed to do
> this at the OS level, also make sure that his password is correct in EM.
> Did
> he change his password since the lat time he was able to do this?
> --
> TIA,
> ChrisR
>
> "Dan D." wrote:
>|||They have logins in sqlserver and they are sysadmins in sqlserver.
--
Dan D.
"Paul Cahill" wrote:

> I saw this recently when some of our users switched to a new Win 2003
> domain.
> We had forgotten to set them up in sql server.
> Paul
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:7BB943F7-C48F-406A-A44D-22C200686A8C@.microsoft.com...
>
>|||I'm thinking it is OS related too. They also can't stop and start IIS. They
say they haven't changed their passwords recently.
--
Dan D.
"ChrisR" wrote:
[vbcol=seagreen]
> Starting/ stopping services are OS specific. Make sure he's allowed to do
> this at the OS level, also make sure that his password is correct in EM. D
id
> he change his password since the lat time he was able to do this?
> --
> TIA,
> ChrisR
>
> "Dan D." wrote:
>|||Another thing that happened with our new domain.
One of my colleagues (a user on our old domain) mapped a drive on the new
domain as the NEWDOMAIN\administrator (remember by password).
We then noticed that when he connected to an SQL Server on the new domain he
was logging in as NEWDOMAIN\administrator and not his OLDDOMAIN\username.
Ie the authentication of network resources affects sql server too. I guess
this makes sense but caught me out.
Maybe not the same issue for you but it looks like an authentication issue
of some sort.
Paul
"Dan D." <DanD@.discussions.microsoft.com> wrote in message
news:90E92723-FA30-48F4-9415-50A4A0EF8797@.microsoft.com...[vbcol=seagreen]
> I'm thinking it is OS related too. They also can't stop and start IIS.
> They
> say they haven't changed their passwords recently.
> --
> Dan D.
>
> "ChrisR" wrote:
>

access is denied when starting service

We have a user who could start and stop the sql server service through EM at
one time and then he started getting an "error 5 (access is denied) occurred
while performing this service operation on the MSSQLServer service."
I removed his login and created a new one for him and gave him sysadmin
permissions but he still gets the same error when trying to start the
service.
Any ideas?
Thanks,
Dan D.
Starting/ stopping services are OS specific. Make sure he's allowed to do
this at the OS level, also make sure that his password is correct in EM. Did
he change his password since the lat time he was able to do this?
TIA,
ChrisR
"Dan D." wrote:

> We have a user who could start and stop the sql server service through EM at
> one time and then he started getting an "error 5 (access is denied) occurred
> while performing this service operation on the MSSQLServer service."
> I removed his login and created a new one for him and gave him sysadmin
> permissions but he still gets the same error when trying to start the
> service.
> Any ideas?
> Thanks,
> --
> Dan D.
|||I saw this recently when some of our users switched to a new Win 2003
domain.
We had forgotten to set them up in sql server.
Paul
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:7BB943F7-C48F-406A-A44D-22C200686A8C@.microsoft.com...[vbcol=seagreen]
> Starting/ stopping services are OS specific. Make sure he's allowed to do
> this at the OS level, also make sure that his password is correct in EM.
> Did
> he change his password since the lat time he was able to do this?
> --
> TIA,
> ChrisR
>
> "Dan D." wrote:
|||They have logins in sqlserver and they are sysadmins in sqlserver.
Dan D.
"Paul Cahill" wrote:

> I saw this recently when some of our users switched to a new Win 2003
> domain.
> We had forgotten to set them up in sql server.
> Paul
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:7BB943F7-C48F-406A-A44D-22C200686A8C@.microsoft.com...
>
>
|||I'm thinking it is OS related too. They also can't stop and start IIS. They
say they haven't changed their passwords recently.
Dan D.
"ChrisR" wrote:
[vbcol=seagreen]
> Starting/ stopping services are OS specific. Make sure he's allowed to do
> this at the OS level, also make sure that his password is correct in EM. Did
> he change his password since the lat time he was able to do this?
> --
> TIA,
> ChrisR
>
> "Dan D." wrote:
|||Another thing that happened with our new domain.
One of my colleagues (a user on our old domain) mapped a drive on the new
domain as the NEWDOMAIN\administrator (remember by password).
We then noticed that when he connected to an SQL Server on the new domain he
was logging in as NEWDOMAIN\administrator and not his OLDDOMAIN\username.
Ie the authentication of network resources affects sql server too. I guess
this makes sense but caught me out.
Maybe not the same issue for you but it looks like an authentication issue
of some sort.
Paul
"Dan D." <DanD@.discussions.microsoft.com> wrote in message
news:90E92723-FA30-48F4-9415-50A4A0EF8797@.microsoft.com...[vbcol=seagreen]
> I'm thinking it is OS related too. They also can't stop and start IIS.
> They
> say they haven't changed their passwords recently.
> --
> Dan D.
>
> "ChrisR" wrote:

access is denied when starting service

We have a user who could start and stop the sql server service through EM at
one time and then he started getting an "error 5 (access is denied) occurred
while performing this service operation on the MSSQLServer service."
I removed his login and created a new one for him and gave him sysadmin
permissions but he still gets the same error when trying to start the
service.
Any ideas?
Thanks,
--
Dan D.Starting/ stopping services are OS specific. Make sure he's allowed to do
this at the OS level, also make sure that his password is correct in EM. Did
he change his password since the lat time he was able to do this?
--
TIA,
ChrisR
"Dan D." wrote:
> We have a user who could start and stop the sql server service through EM at
> one time and then he started getting an "error 5 (access is denied) occurred
> while performing this service operation on the MSSQLServer service."
> I removed his login and created a new one for him and gave him sysadmin
> permissions but he still gets the same error when trying to start the
> service.
> Any ideas?
> Thanks,
> --
> Dan D.|||I saw this recently when some of our users switched to a new Win 2003
domain.
We had forgotten to set them up in sql server.
Paul
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:7BB943F7-C48F-406A-A44D-22C200686A8C@.microsoft.com...
> Starting/ stopping services are OS specific. Make sure he's allowed to do
> this at the OS level, also make sure that his password is correct in EM.
> Did
> he change his password since the lat time he was able to do this?
> --
> TIA,
> ChrisR
>
> "Dan D." wrote:
>> We have a user who could start and stop the sql server service through EM
>> at
>> one time and then he started getting an "error 5 (access is denied)
>> occurred
>> while performing this service operation on the MSSQLServer service."
>> I removed his login and created a new one for him and gave him sysadmin
>> permissions but he still gets the same error when trying to start the
>> service.
>> Any ideas?
>> Thanks,
>> --
>> Dan D.|||They have logins in sqlserver and they are sysadmins in sqlserver.
--
Dan D.
"Paul Cahill" wrote:
> I saw this recently when some of our users switched to a new Win 2003
> domain.
> We had forgotten to set them up in sql server.
> Paul
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:7BB943F7-C48F-406A-A44D-22C200686A8C@.microsoft.com...
> > Starting/ stopping services are OS specific. Make sure he's allowed to do
> > this at the OS level, also make sure that his password is correct in EM.
> > Did
> > he change his password since the lat time he was able to do this?
> > --
> > TIA,
> > ChrisR
> >
> >
> > "Dan D." wrote:
> >
> >> We have a user who could start and stop the sql server service through EM
> >> at
> >> one time and then he started getting an "error 5 (access is denied)
> >> occurred
> >> while performing this service operation on the MSSQLServer service."
> >>
> >> I removed his login and created a new one for him and gave him sysadmin
> >> permissions but he still gets the same error when trying to start the
> >> service.
> >>
> >> Any ideas?
> >>
> >> Thanks,
> >> --
> >> Dan D.
>
>|||I'm thinking it is OS related too. They also can't stop and start IIS. They
say they haven't changed their passwords recently.
--
Dan D.
"ChrisR" wrote:
> Starting/ stopping services are OS specific. Make sure he's allowed to do
> this at the OS level, also make sure that his password is correct in EM. Did
> he change his password since the lat time he was able to do this?
> --
> TIA,
> ChrisR
>
> "Dan D." wrote:
> > We have a user who could start and stop the sql server service through EM at
> > one time and then he started getting an "error 5 (access is denied) occurred
> > while performing this service operation on the MSSQLServer service."
> >
> > I removed his login and created a new one for him and gave him sysadmin
> > permissions but he still gets the same error when trying to start the
> > service.
> >
> > Any ideas?
> >
> > Thanks,
> > --
> > Dan D.|||Another thing that happened with our new domain.
One of my colleagues (a user on our old domain) mapped a drive on the new
domain as the NEWDOMAIN\administrator (remember by password).
We then noticed that when he connected to an SQL Server on the new domain he
was logging in as NEWDOMAIN\administrator and not his OLDDOMAIN\username.
Ie the authentication of network resources affects sql server too. I guess
this makes sense but caught me out.
Maybe not the same issue for you but it looks like an authentication issue
of some sort.
Paul
"Dan D." <DanD@.discussions.microsoft.com> wrote in message
news:90E92723-FA30-48F4-9415-50A4A0EF8797@.microsoft.com...
> I'm thinking it is OS related too. They also can't stop and start IIS.
> They
> say they haven't changed their passwords recently.
> --
> Dan D.
>
> "ChrisR" wrote:
>> Starting/ stopping services are OS specific. Make sure he's allowed to do
>> this at the OS level, also make sure that his password is correct in EM.
>> Did
>> he change his password since the lat time he was able to do this?
>> --
>> TIA,
>> ChrisR
>>
>> "Dan D." wrote:
>> > We have a user who could start and stop the sql server service through
>> > EM at
>> > one time and then he started getting an "error 5 (access is denied)
>> > occurred
>> > while performing this service operation on the MSSQLServer service."
>> >
>> > I removed his login and created a new one for him and gave him sysadmin
>> > permissions but he still gets the same error when trying to start the
>> > service.
>> >
>> > Any ideas?
>> >
>> > Thanks,
>> > --
>> > Dan D.