Showing posts with label denied. Show all posts
Showing posts with label denied. Show all posts

Thursday, March 22, 2012

Error 15274: Access to the remote server is denied because the current security context is not t

Hi,

I have a stored procedure servicing a queue (sql 2005).

The stored procedure updates some data in a different server and database.

If the queue contains messages and I execute manually the stored procedure, I don't have any problem at all.

However, if I set the queue to use the same stored procedure, it gives me the following error:

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

Any ideas?

Thanks,

Aron

Please, see if the following link to a similar question on this forum has the answer for your particular scenario: https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1064271&SiteID=1

If the answers in this thread do not help you to resolve the problem, please let us know and we will be glad to provide further assistance.

Thanks a lot,

-Raul Garcia

SDE/T

SQL Server Engine

Friday, March 9, 2012

Error 0x800c0005 when calling Microsoft.XMLHTTP from inside SQLSer

0x800c0005 = Error 5 = Access Denied.
What has changed on the server?
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"SammyBar" wrote:

> Hi all,
> We have a sp that sends http requests. It uses Microsoft XMLHTTP component
> that is part of XML pack that is standard with SQL Server 2000 SP3. For an
> unknown reason the XMLHTTP component started to fail raising the error:
> OLE Automation Error Information
> HRESULT: 0x800c0005
> I've seen this error in Visual Basic 6 when trying to create a component
> that is not well installed. But here this error is raised when creating th
e
> object but when sending the request:
> Exec @.nError = sp_OACreate 'Microsoft.XMLHTTP', @.iReq OUT
> If @.nError != 0
> Begin
> Select @.nError = Null
> Raiserror('sp_OACreate Microsoft.XMLHTTP FAILED! [sp_send_http]', 16, -1)
> Goto Fin
> End
> Exec @.nError = sp_OAMethod @.iReq, 'Open', NULL, 'POST', @.sUrl, false,
> @.sUser, @.sPassword
> If @.nError != 0
> Begin
> Raiserror('sp_OAMethod Open FAILED! [sp_send_http]', 16, -1)
> Goto Fin
> End
> Exec @.nError = sp_OAMethod @.iReq, 'send'
> If @.nError != 0
> Begin
> Raiserror('sp_OAMethod Send FAILED! [sp_send_http]', 16, -1)
> Goto Fin
> End
> then it goes well through sp_OACreate and sp_OAMethod "Open" calls.
> I reregister msxml.dll, msxml2.dll, msxml2.dll, and restarted the server b
ut
> it was useless.
> Looking around on the server logs the only suspected entry I've found was:
> SqlDumpExceptionHandler: Process 397 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process..
> * ---
--
> * Short Stack Dump
> * 09C73F85 Module(UNKNOWN+00000000)
> * 0066A220 Module(sqlservr+0026A220) (MSXMLThreadDetach+0000003D)
> * 00505DF1 Module(sqlservr+00105DF1) (clean_process+000000C6)
> * 0050611D Module(sqlservr+0010611D) (kill_proc+000000EE)
> * 00506513 Module(sqlservr+00106513) (logout+000001AC)
> * 005063D8 Module(sqlservr+001063D8) (release_srvproc+00000045)
> * 004270F9 Module(sqlservr+000270F9) (process_commands+000002A2)
> * 41075002 Module(UMS+00005002) (ProcessWorkRequests+00000272)
> * 41074698 Module(UMS+00004698) (ThreadStartRoutine+00000098)
> * 7800C9EB Module(MSVCRT+0000C9EB) (beginthread+000000CE)
> * 77E8B2D8 Module(KERNEL32+0000B2D8) (lstrcmpiW+000000B7)
> * ---
--
> It looks like after that the XMLHTTP doesn't works.
> Then my problem is to restore the XMLHTTP component to normal state. It ru
ns
> on a production server so the rules here are very strict. We cannot instal
l
> any new package there. So just reinstalling the xml package is the least
> desirable solution. I'd prefer just reregister the proper dlls but it look
s
> like reregistering msxml?.dll is not enought.
> What should I do?
> Should I register any other dll associated to msxml?.dll
> Any idea is welcomed
> Thanks in advance
> Sammy
>
>> 0x800c0005 = Error 5 = Access Denied.
!!!
Where did you find error codes?

> What has changed on the server?
Nothing. It is in the production server and it is forbidden to change
anything..., even security patches...|||> Where did you find error codes?
From an OS command prompt:
NET HELPMSG 5
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"SammyBar" <sammybar@.gmail.com> wrote in message news:%23ZP6ykskFHA.3144@.TK2MSFTNGP12.phx.g
bl...
> !!!
> Where did you find error codes?
>
> Nothing. It is in the production server and it is forbidden to change
> anything..., even security patches...
>|||Hi
It is the standard COM error. After seeing the same ones for 10 years, you
generally get to know them.
You can strip the last 4 characters, and use them as Tibor Karaszi noted in
his post.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"SammyBar" <sammybar@.gmail.com> wrote in message
news:%23ZP6ykskFHA.3144@.TK2MSFTNGP12.phx.gbl...
> !!!
> Where did you find error codes?
>
> Nothing. It is in the production server and it is forbidden to change
> anything..., even security patches...
>|||> What has changed on the server?
Ok, I found the error. Somebody activated a second NIC on the server and
that mangled the network routes. The server that was being requested was not
available by pinging. That is way the error was raising on the "send"
method.
Thanks you all for the hints
Best regards
Sammy

Wednesday, March 7, 2012

Error : SQL server does not exist or access denied.

Error : SQL server does not exist or access denied.
We are replacing the box the SQL server resides on and we have set up the
new server as a copy of the old one. It is a Win2000server with DNS and
active directory.
SQL server ver 8.00.760
We are able to:
Attach to the new server from workstations including exploring and
mapping the drives (actually our old server mappings worked)
We can establish an ODBC connection to the SQL server from the new box
and it tests fine so the server is started and running.
We were able to get one workstation to access the SQL server after
enabling name pipes but another still could not.
We are able to connect to the old DNS server and SQL server from all
workstations with no difficlties. Only one of the servers is connected at at
ime.
We can not set up an ODBC connection from any other workstation attached to
the new server. This is the error message we receive:
Connection failed:
SQL State 01000
SQL Server error: 10060
[Microsoft][ODBC SQL Server driver[tcp/ip sockets] Connectionopen (Connect
()).
Connection failed:
SQL State 08001
SQL Server error 17
[Microsoft][ODBC SQL Server driver[tcp/ip sockets] SQL Server does not exist
or access denied.
There is no firewall in between the server and workstations (a fire wall
resides between the server and the internet with NAT enabled).
Login is set to use both windows and SQL authentication. We have tried it
as SQL only login with the same error message.
We have worked through Microsoft document 328306 "Potential causes of the
"SQL Server does not exist or access denied" error message"
Any ideas where our problem is?
Thank you,
Michael
Hi All,
We are facing exactly similar problem. Does anyone have any idea/thoughts as
to why this could be happening and what we can do to troubleshoot/solve this
problem.
Many Thanks,
Parag
"MABrown58" wrote:

> Error : SQL server does not exist or access denied.
> We are replacing the box the SQL server resides on and we have set up the
> new server as a copy of the old one. It is a Win2000server with DNS and
> active directory.
> SQL server ver 8.00.760
> We are able to:
> Attach to the new server from workstations including exploring and
> mapping the drives (actually our old server mappings worked)
> We can establish an ODBC connection to the SQL server from the new box
> and it tests fine so the server is started and running.
> We were able to get one workstation to access the SQL server after
> enabling name pipes but another still could not.
> We are able to connect to the old DNS server and SQL server from all
> workstations with no difficlties. Only one of the servers is connected at at
> ime.
> We can not set up an ODBC connection from any other workstation attached to
> the new server. This is the error message we receive:
> Connection failed:
> SQL State 01000
> SQL Server error: 10060
> [Microsoft][ODBC SQL Server driver[tcp/ip sockets] Connectionopen (Connect
> ()).
> Connection failed:
> SQL State 08001
> SQL Server error 17
> [Microsoft][ODBC SQL Server driver[tcp/ip sockets] SQL Server does not exist
> or access denied.
> There is no firewall in between the server and workstations (a fire wall
> resides between the server and the internet with NAT enabled).
> Login is set to use both windows and SQL authentication. We have tried it
> as SQL only login with the same error message.
> We have worked through Microsoft document 328306 "Potential causes of the
> "SQL Server does not exist or access denied" error message"
> Any ideas where our problem is?
> Thank you,
> Michael
|||Since you didn't provide any specifics (other than "exactly similar"), how
about:
http://support.microsoft.com/?kbid=328306
http://support.microsoft.com/?kbid=888228
http://www.aspfaq.com/
(Reverse address to reply.)
"Parag Gaikwad" <Parag Gaikwad@.discussions.microsoft.com> wrote in message
news:7F1BC52B-CF3E-4661-B50B-5DA4E460F666@.microsoft.com...
> Hi All,
> We are facing exactly similar problem. Does anyone have any idea/thoughts
as
> to why this could be happening and what we can do to troubleshoot/solve
this
> problem.
> Many Thanks,
> Parag

Error : SQL server does not exist or access denied.

Error : SQL server does not exist or access denied.
We are replacing the box the SQL server resides on and we have set up the
new server as a copy of the old one. It is a Win2000server with DNS and
active directory.
SQL server ver 8.00.760
We are able to:
Attach to the new server from workstations including exploring and
mapping the drives (actually our old server mappings worked)
We can establish an ODBC connection to the SQL server from the new box
and it tests fine so the server is started and running.
We were able to get one workstation to access the SQL server after
enabling name pipes but another still could not.
We are able to connect to the old DNS server and SQL server from all
workstations with no difficlties. Only one of the servers is connected at at
ime.
We can not set up an ODBC connection from any other workstation attached to
the new server. This is the error message we receive:
Connection failed:
SQL State 01000
SQL Server error: 10060
[Microsoft][ODBC SQL Server driver[tcp/ip sockets] Connectionopen (Connect
()).
Connection failed:
SQL State 08001
SQL Server error 17
[Microsoft][ODBC SQL Server driver[tcp/ip sockets] SQL Server does not exist
or access denied.
There is no firewall in between the server and workstations (a fire wall
resides between the server and the internet with NAT enabled).
Login is set to use both windows and SQL authentication. We have tried it
as SQL only login with the same error message.
We have worked through Microsoft document 328306 "Potential causes of the
"SQL Server does not exist or access denied" error message"
Any ideas where our problem is?
Thank you,
MichaelHi All,
We are facing exactly similar problem. Does anyone have any idea/thoughts as
to why this could be happening and what we can do to troubleshoot/solve this
problem.
Many Thanks,
Parag
"MABrown58" wrote:
> Error : SQL server does not exist or access denied.
> We are replacing the box the SQL server resides on and we have set up the
> new server as a copy of the old one. It is a Win2000server with DNS and
> active directory.
> SQL server ver 8.00.760
> We are able to:
> Attach to the new server from workstations including exploring and
> mapping the drives (actually our old server mappings worked)
> We can establish an ODBC connection to the SQL server from the new box
> and it tests fine so the server is started and running.
> We were able to get one workstation to access the SQL server after
> enabling name pipes but another still could not.
> We are able to connect to the old DNS server and SQL server from all
> workstations with no difficlties. Only one of the servers is connected at at
> ime.
> We can not set up an ODBC connection from any other workstation attached to
> the new server. This is the error message we receive:
> Connection failed:
> SQL State 01000
> SQL Server error: 10060
> [Microsoft][ODBC SQL Server driver[tcp/ip sockets] Connectionopen (Connect
> ()).
> Connection failed:
> SQL State 08001
> SQL Server error 17
> [Microsoft][ODBC SQL Server driver[tcp/ip sockets] SQL Server does not exist
> or access denied.
> There is no firewall in between the server and workstations (a fire wall
> resides between the server and the internet with NAT enabled).
> Login is set to use both windows and SQL authentication. We have tried it
> as SQL only login with the same error message.
> We have worked through Microsoft document 328306 "Potential causes of the
> "SQL Server does not exist or access denied" error message"
> Any ideas where our problem is?
> Thank you,
> Michael|||Since you didn't provide any specifics (other than "exactly similar"), how
about:
http://support.microsoft.com/?kbid=328306
http://support.microsoft.com/?kbid=888228
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Parag Gaikwad" <Parag Gaikwad@.discussions.microsoft.com> wrote in message
news:7F1BC52B-CF3E-4661-B50B-5DA4E460F666@.microsoft.com...
> Hi All,
> We are facing exactly similar problem. Does anyone have any idea/thoughts
as
> to why this could be happening and what we can do to troubleshoot/solve
this
> problem.
> Many Thanks,
> Parag