Showing posts with label mapped. Show all posts
Showing posts with label mapped. Show all posts

Tuesday, March 27, 2012

Error 18452 Login failed for user <null>. The user account is not

We have a SQL 2005 installation using SQL and Windows Authentication. We
have a login that is mapped to a active directory group and has the
appropriate permissions to the database. However, when we try to create
an ODBC connection to the server from an XP client (and the user is a
member of the appropriate domain group) we get the above mentioned error.
Also logged on the SQL server is the following error:
SSPI handshake failed with error code 0x8009030c...
The only info I can find on this error has to do with IIS
configurations, but I don't see what IIS has to do with this as we are
only trying to make an ODBC connection.Maybe your service account is Local System.
You can change to AD Service account.
"Jan Leste"?? ??? ??:

> We have a SQL 2005 installation using SQL and Windows Authentication. We
> have a login that is mapped to a active directory group and has the
> appropriate permissions to the database. However, when we try to create
> an ODBC connection to the server from an XP client (and the user is a
> member of the appropriate domain group) we get the above mentioned error.
> Also logged on the SQL server is the following error:
> SSPI handshake failed with error code 0x8009030c...
> The only info I can find on this error has to do with IIS
> configurations, but I don't see what IIS has to do with this as we are
> only trying to make an ODBC connection.
>

Thursday, March 22, 2012

Error 15185: There is no remote user 'sa' mapped to local user '(null)' from the remote serv

I am trying to add a linked server from a AMD x64 server (Windows 2003) with SQL Server 2005 64 bit to a Server running SQL 2000. These are not in the same domain.

I can create a linked server using the option "Be made using the login's current security context" but can not when trying to specify the security context, i.e. sa and the sa password. When I try I get the following message:

Msg 15185, Level 16, State 1, Procedure sp_addlinkedsrvlogin, Line 98
There is no remote user 'sa' mapped to local user '(null)' from the remote server 'DTS_FSERVER'.

I have several other x64 server that I have no problem creating a linked server and specifying sa and the sa password.

The problem with using "the login's current security context" option is that I get an error when trying to run any Jobs against the linked server. The job fails withe the following error:

Executed as user: NT AUTHORITY\SYSTEM. Access to the remote server is denied because no login-mapping exists. [SQLSTATE 42000] (Error 7416). The step failed.

I'm sure the two errors are related. Any ideas what is going on?

What is your context on the server when you get the first error message? How do your sp_addlinkedserver and sp_addlinkedsrvlogin commands look like?

For the second error message, the jobs probably execute with the SQL Agent service account credentials, which is LocalSystem and is unmapped. You should check the SQL Server Tools General forum for more information about SQL Agent.

Thanks
Laurentiu

|||I am also facing the same problem for linked servers. My server is in cluster environment.
i have both servers in the same domain however when i try to link it show the above mentioned error. when i try to link from ne other server i m able to do but not from the clustered one.
please reply asap.
|||

Iam trying to create a linked server(which is 32 bit SQL Server 2000) on 64 bit SLQ Server 2005 and iam receiving the following error.

Msg 15466, Level 16, State 2, Procedure sp_addlinkedsrvlogin, Line 91

An error occurred during decryption.

Msg 15185, Level 16, State 1, Procedure sp_addlinkedsrvlogin, Line 98

There is no remote user 'user1' mapped to local user '(null)' from the remote server 'SERVER1'.

Kerry- were you able to fix the error that you received. Anyone who are aware of this, please help me.

Thanks

|||Sorry, no we were never able to completely solve this. We have created linked servers using windows integrated security and as long as the user exists on both machines it does allow some limited access.sql

Error 15185: There is no remote user 'sa' mapped to local user '(null)' from the remote serv

I am trying to add a linked server from a AMD x64 server (Windows 2003) with SQL Server 2005 64 bit to a Server running SQL 2000. These are not in the same domain.

I can create a linked server using the option "Be made using the login's current security context" but can not when trying to specify the security context, i.e. sa and the sa password. When I try I get the following message:

Msg 15185, Level 16, State 1, Procedure sp_addlinkedsrvlogin, Line 98
There is no remote user 'sa' mapped to local user '(null)' from the remote server 'DTS_FSERVER'.

I have several other x64 server that I have no problem creating a linked server and specifying sa and the sa password.

The problem with using "the login's current security context" option is that I get an error when trying to run any Jobs against the linked server. The job fails withe the following error:

Executed as user: NT AUTHORITY\SYSTEM. Access to the remote server is denied because no login-mapping exists. [SQLSTATE 42000] (Error 7416). The step failed.

I'm sure the two errors are related. Any ideas what is going on?

What is your context on the server when you get the first error message? How do your sp_addlinkedserver and sp_addlinkedsrvlogin commands look like?

For the second error message, the jobs probably execute with the SQL Agent service account credentials, which is LocalSystem and is unmapped. You should check the SQL Server Tools General forum for more information about SQL Agent.

Thanks
Laurentiu

|||I am also facing the same problem for linked servers. My server is in cluster environment.
i have both servers in the same domain however when i try to link it show the above mentioned error. when i try to link from ne other server i m able to do but not from the clustered one.
please reply asap.|||

Iam trying to create a linked server(which is 32 bit SQL Server 2000) on 64 bit SLQ Server 2005 and iam receiving the following error.

Msg 15466, Level 16, State 2, Procedure sp_addlinkedsrvlogin, Line 91

An error occurred during decryption.

Msg 15185, Level 16, State 1, Procedure sp_addlinkedsrvlogin, Line 98

There is no remote user 'user1' mapped to local user '(null)' from the remote server 'SERVER1'.

Kerry- were you able to fix the error that you received. Anyone who are aware of this, please help me.

Thanks

|||Sorry, no we were never able to completely solve this. We have created linked servers using windows integrated security and as long as the user exists on both machines it does allow some limited access.

Error 15185: There is no remote user 'sa' mapped to local user '(null)' from the remote

I am trying to add a linked server from a AMD x64 server (Windows 2003) with SQL Server 2005 64 bit to a Server running SQL 2000. These are not in the same domain.

I can create a linked server using the option "Be made using the login's current security context" but can not when trying to specify the security context, i.e. sa and the sa password. When I try I get the following message:

Msg 15185, Level 16, State 1, Procedure sp_addlinkedsrvlogin, Line 98
There is no remote user 'sa' mapped to local user '(null)' from the remote server 'DTS_FSERVER'.

I have several other x64 server that I have no problem creating a linked server and specifying sa and the sa password.

The problem with using "the login's current security context" option is that I get an error when trying to run any Jobs against the linked server. The job fails withe the following error:

Executed as user: NT AUTHORITY\SYSTEM. Access to the remote server is denied because no login-mapping exists. [SQLSTATE 42000] (Error 7416). The step failed.

I'm sure the two errors are related. Any ideas what is going on?

What is your context on the server when you get the first error message? How do your sp_addlinkedserver and sp_addlinkedsrvlogin commands look like?

For the second error message, the jobs probably execute with the SQL Agent service account credentials, which is LocalSystem and is unmapped. You should check the SQL Server Tools General forum for more information about SQL Agent.

Thanks
Laurentiu

|||I am also facing the same problem for linked servers. My server is in cluster environment.
i have both servers in the same domain however when i try to link it show the above mentioned error. when i try to link from ne other server i m able to do but not from the clustered one.
please reply asap.|||

Iam trying to create a linked server(which is 32 bit SQL Server 2000) on 64 bit SLQ Server 2005 and iam receiving the following error.

Msg 15466, Level 16, State 2, Procedure sp_addlinkedsrvlogin, Line 91

An error occurred during decryption.

Msg 15185, Level 16, State 1, Procedure sp_addlinkedsrvlogin, Line 98

There is no remote user 'user1' mapped to local user '(null)' from the remote server 'SERVER1'.

Kerry- were you able to fix the error that you received. Anyone who are aware of this, please help me.

Thanks

|||Sorry, no we were never able to completely solve this. We have created linked servers using windows integrated security and as long as the user exists on both machines it does allow some limited access.

Error 15185: There is no remote user 'sa' mapped to local user '(null)' from the remote

I am trying to add a linked server from a AMD x64 server (Windows 2003) with SQL Server 2005 64 bit to a Server running SQL 2000. These are not in the same domain.

I can create a linked server using the option "Be made using the login's current security context" but can not when trying to specify the security context, i.e. sa and the sa password. When I try I get the following message:

Msg 15185, Level 16, State 1, Procedure sp_addlinkedsrvlogin, Line 98
There is no remote user 'sa' mapped to local user '(null)' from the remote server 'DTS_FSERVER'.

I have several other x64 server that I have no problem creating a linked server and specifying sa and the sa password.

The problem with using "the login's current security context" option is that I get an error when trying to run any Jobs against the linked server. The job fails withe the following error:

Executed as user: NT AUTHORITY\SYSTEM. Access to the remote server is denied because no login-mapping exists. [SQLSTATE 42000] (Error 7416). The step failed.

I'm sure the two errors are related. Any ideas what is going on?

What is your context on the server when you get the first error message? How do your sp_addlinkedserver and sp_addlinkedsrvlogin commands look like?

For the second error message, the jobs probably execute with the SQL Agent service account credentials, which is LocalSystem and is unmapped. You should check the SQL Server Tools General forum for more information about SQL Agent.

Thanks
Laurentiu

|||I am also facing the same problem for linked servers. My server is in cluster environment.
i have both servers in the same domain however when i try to link it show the above mentioned error. when i try to link from ne other server i m able to do but not from the clustered one.
please reply asap.|||

Iam trying to create a linked server(which is 32 bit SQL Server 2000) on 64 bit SLQ Server 2005 and iam receiving the following error.

Msg 15466, Level 16, State 2, Procedure sp_addlinkedsrvlogin, Line 91

An error occurred during decryption.

Msg 15185, Level 16, State 1, Procedure sp_addlinkedsrvlogin, Line 98

There is no remote user 'user1' mapped to local user '(null)' from the remote server 'SERVER1'.

Kerry- were you able to fix the error that you received. Anyone who are aware of this, please help me.

Thanks

|||Sorry, no we were never able to completely solve this. We have created linked servers using windows integrated security and as long as the user exists on both machines it does allow some limited access.