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.

error 15004: Name cannot be NULL'

Hi,
I am tring to create a pull subscription from a server and
receiving an error '15004: Name cannot be NULL'. Is any
one knows hot to resolve this issue? Please help me.
Thanks,
PingPlease see my reply in the Replication group.
Paul Ibison

error 15004: Name cannot be NULL'

Hi,
I am tring to create a pull subscription from a server and
receiving an error '15004: Name cannot be NULL'. Is any
one knows hot to resolve this issue? Please help me.
Thanks,
PingPlease see my reply in the Replication group.
Paul Ibison

error 15004: Name cannot be NULL'

Hi,
I am tring to create a pull subscription from a server and
receiving an error '15004: Name cannot be NULL'. Is any
one knows hot to resolve this issue? Please help me.
Thanks,
Ping
Please see my reply in the Replication group.
Paul Ibison
sql

Error 15004 Name cannot be null

I made a publisher for marge replication via ISDN Dialup connected server and registered server x to y and y to x with TCP/IP.

I can see both data on each other.

I publish one database and try to configure pull subscription on 2nd one got following error.

SQL Server enterprise manager could not create a pull asubscription to publication pmst

Error 15004 Name cannot be null

Thanks to all of youYou've got a relatively unusual configuration for replication. I don't know of anywhere to look for specific details to help you, but I've got some ideas.

I'd start by synchronizing the clocks on both servers, preferably to a common time source or better yet synch one machine's clock to the other's clock. Open a copy of SQL Profiler on both machines and trace with no filtering (so you can see every command executed against the server). Try to re-subscribe again. The last command in each profile is suspect, the one with the later timestamp is likely to be the source of your problem.

You are probably looking for an empty string or NULL string parameter. Once you find it, you'll have to post what you find and maybe one of us can help you.

-PatP|||Do "SELECT @.@.SERVERNAME" on both servers.

Erroneous behaviour of COALESCE versus ISNULL??

I am getting very of why COALESCE doesnt report NULL as NULL.
Can somebody please explain the behavoiour described below?
Create these tables:
create table dbo.Warrants (
WarrantId bigint not null
constraint WarrantsPKCO primary key nonclustered (WarrantId)
)
go
create table dbo.TextLimitations (
WarrantId bigint not null,
LimitationText text not null,
constraint TextLimitationsPKCO primary key clustered (WarrantId)
)
go
EXECUTE SP_TABLEOPTION 'dbo.TextLimitations',
'TEXT IN ROW', 'ON'
go
Insert this data:
insert into dbo.Warrants values (1)
insert into dbo.Warrants values (2)
go
insert into dbo.TextLimitations values (1, 'a very long text')
go
Run this query:
SELECT W.WarrantId
,Text1 = COALESCE(LimitationText, '')
,Text2 = CASE
WHEN (LimitationText IS NOT NULL) THEN LimitationText
WHEN (LimitationText IS NULL) THEN 'it is null'
ELSE 'else null'
END
,Text3 = ISNULL(LimitationText, '')
FROM dbo.Warrants W
LEFT JOIN dbo.TextLimitations T
ON W.WarrantId = T.WarrantId
WHERE W.WarrantId = 2
go
Why is text1 and text2 NULL?
/kHi
I get
WarrantId Text1 Text2 Text3
-- -- -- --
2 it is null
Which is what I would expect. Text1 and Text3 are both empty strings (which
is different to NULL)
You may want to check version and compatibility settings.
John
"kurt sune" wrote:

> I am getting very of why COALESCE doesnt report NULL as NULL.
> Can somebody please explain the behavoiour described below?
> Create these tables:
> create table dbo.Warrants (
> WarrantId bigint not null
> constraint WarrantsPKCO primary key nonclustered (WarrantId)
> )
> go
> create table dbo.TextLimitations (
> WarrantId bigint not null,
> LimitationText text not null,
> constraint TextLimitationsPKCO primary key clustered (WarrantId)
> )
> go
> EXECUTE SP_TABLEOPTION 'dbo.TextLimitations',
> 'TEXT IN ROW', 'ON'
> go
> Insert this data:
> insert into dbo.Warrants values (1)
> insert into dbo.Warrants values (2)
> go
> insert into dbo.TextLimitations values (1, 'a very long text')
> go
> Run this query:
> SELECT W.WarrantId
> ,Text1 = COALESCE(LimitationText, '')
> ,Text2 = CASE
> WHEN (LimitationText IS NOT NULL) THEN LimitationText
> WHEN (LimitationText IS NULL) THEN 'it is null'
> ELSE 'else null'
> END
> ,Text3 = ISNULL(LimitationText, '')
> FROM dbo.Warrants W
> LEFT JOIN dbo.TextLimitations T
> ON W.WarrantId = T.WarrantId
> WHERE W.WarrantId = 2
> go
>
> Why is text1 and text2 NULL?
>
> /k
>
>|||Addendum:
on two machines I get
2 NULL NULL emptystring
on all others I get
2 emptystring it is null emptystring
What makes the first two machines answer incorrectly?
/k
"kurt sune" <apa@.apa.com> wrote in message
news:uzi99p%23xFHA.3408@.TK2MSFTNGP09.phx.gbl...
> I am getting very of why COALESCE doesnt report NULL as NULL.
> Can somebody please explain the behavoiour described below?
> Create these tables:
> create table dbo.Warrants (
> WarrantId bigint not null
> constraint WarrantsPKCO primary key nonclustered (WarrantId)
> )
> go
> create table dbo.TextLimitations (
> WarrantId bigint not null,
> LimitationText text not null,
> constraint TextLimitationsPKCO primary key clustered (WarrantId)
> )
> go
> EXECUTE SP_TABLEOPTION 'dbo.TextLimitations',
> 'TEXT IN ROW', 'ON'
> go
> Insert this data:
> insert into dbo.Warrants values (1)
> insert into dbo.Warrants values (2)
> go
> insert into dbo.TextLimitations values (1, 'a very long text')
> go
> Run this query:
> SELECT W.WarrantId
> ,Text1 = COALESCE(LimitationText, '')
> ,Text2 = CASE
> WHEN (LimitationText IS NOT NULL) THEN LimitationText
> WHEN (LimitationText IS NULL) THEN 'it is null'
> ELSE 'else null'
> END
> ,Text3 = ISNULL(LimitationText, '')
> FROM dbo.Warrants W
> LEFT JOIN dbo.TextLimitations T
> ON W.WarrantId = T.WarrantId
> WHERE W.WarrantId = 2
> go
>
> Why is text1 and text2 NULL?
>
> /k
>|||On Mon, 3 Oct 2005 09:40:53 +0200, kurt sune wrote:

>Addendum:
>on two machines I get
>2 NULL NULL emptystring
>on all others I get
>2 emptystring it is null emptystring
>
>What makes the first two machines answer incorrectly?
Hi Kurt,
Maybe an older service pack? What's the output of SELECT @.@.VERSION on
each of the machines?
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)|||One machine that answers correctly:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
One machine that answers wrong:
Microsoft SQL Server 2000 - 8.00.534 (Intel X86)
Nov 19 2001 13:23:50
/k
"Hugo Kornelis" <hugo@.pe_NO_rFact.in_SPAM_fo> wrote in message
news:lp63k1pjr8uh3us6o63abhiirh6lhkfcra@.
4ax.com...
> On Mon, 3 Oct 2005 09:40:53 +0200, kurt sune wrote:
>
> Hi Kurt,
> Maybe an older service pack? What's the output of SELECT @.@.VERSION on
> each of the machines?
> Best, Hugo
> --
> (Remove _NO_ and _SPAM_ to get my e-mail address)|||Hi
After you have upgraded to SP3a or possibly standardised on SP4, check out
differences in the output sp_dboption and sp_dbcmptlevel for each of the
databases.
John
"kurt sune" wrote:

> One machine that answers correctly:
> Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
> Dec 17 2002 14:22:05
> One machine that answers wrong:
> Microsoft SQL Server 2000 - 8.00.534 (Intel X86)
> Nov 19 2001 13:23:50
> /k
>
> "Hugo Kornelis" <hugo@.pe_NO_rFact.in_SPAM_fo> wrote in message
> news:lp63k1pjr8uh3us6o63abhiirh6lhkfcra@.
4ax.com...
>
>|||On Tue, 4 Oct 2005 08:14:09 +0200, kurt sune wrote:

>One machine that answers correctly:
>Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
> Dec 17 2002 14:22:05
>One machine that answers wrong:
>Microsoft SQL Server 2000 - 8.00.534 (Intel X86)
> Nov 19 2001 13:23:50
Hi Kurt,
Upgrade all your machines to at least SP 3a (version 8.00.760) ASAP.
This will probably remove your bug. But even better is that it will cure
your current vulnerability to the SQL Slammer worm.
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)|||Unfortunately I work for a very bureaucratic company and upgrading is a
veeery slow affair.
Thanks for the tip of slammer, now I have three arguments in my
argumentation box.
(the coalesce bug, length of mail message body bug, slammer worm)
/k
"Hugo Kornelis" <hugo@.pe_NO_rFact.in_SPAM_fo> wrote in message
news:jgv5k1dh91hno6m50l1a8gtk85ufumrr66@.
4ax.com...
> On Tue, 4 Oct 2005 08:14:09 +0200, kurt sune wrote:
>
> Hi Kurt,
> Upgrade all your machines to at least SP 3a (version 8.00.760) ASAP.
> This will probably remove your bug. But even better is that it will cure
> your current vulnerability to the SQL Slammer worm.
> Best, Hugo
> --
> (Remove _NO_ and _SPAM_ to get my e-mail address)|||Hi Hugo
Is there a KB for this COALESCE bug?
John
"Hugo Kornelis" wrote:

> On Tue, 4 Oct 2005 08:14:09 +0200, kurt sune wrote:
>
> Hi Kurt,
> Upgrade all your machines to at least SP 3a (version 8.00.760) ASAP.
> This will probably remove your bug. But even better is that it will cure
> your current vulnerability to the SQL Slammer worm.
> Best, Hugo
> --
> (Remove _NO_ and _SPAM_ to get my e-mail address)
>|||Also have a look at
http://toponewithties.blogspot.com/...es.blogspot.com
"kurt sune" <apa@.apa.com> wrote in message
news:eovaSQXyFHA.3312@.TK2MSFTNGP09.phx.gbl...
> Unfortunately I work for a very bureaucratic company and upgrading is a
> veeery slow affair.
> Thanks for the tip of slammer, now I have three arguments in my
> argumentation box.
> (the coalesce bug, length of mail message body bug, slammer worm)
> /k
>
> "Hugo Kornelis" <hugo@.pe_NO_rFact.in_SPAM_fo> wrote in message
> news:jgv5k1dh91hno6m50l1a8gtk85ufumrr66@.
4ax.com...
>