error: 18452; very urgent

We have 2 failover servers and one client in our test environment. We
have all the three configured in mixed mode authentication(windows +
sql server authentication). But when we are failing over from 1st
server to 2nd one, we are getting the following error message,
'Unable to connected to server xxxx: Server : Msg 18452, Level 16,
State 1 [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user 'null'. Reason: Not associated with a trusted SQL server
connection.'
I got some clue.
For instance we have ser1 and ser2 as clusters. I registered both in
the client's EM. Now what I did was, I made ser1 to run and stopped sql
service in ser2 (active/passive) through failover. Now in the client's
EM I'm able to open ser1 and I cannot access ser2. Now what I did was,
I failed over to ser2 ( so sql service in ser1 is stopped). But now I
can still be able to access ser1 and also I can access ser2, even I'm
able to open query analyzer in ser1 through EM.But when I try to open
query analyzer directly, it is giving the same error message. ser1 is
the virtual name given to both ser1 and ser2. So I think when
connecting through EM, failover is occuring fine.I'm just wondering why
is this happening only with dsn. Can anybody help me?
Thanks,
Preethihttp://support.microsoft.com/default.aspx?scid=kb;en-us;555332
"sqldbapree" <mohanpreethi0125@.gmail.com> wrote in message
news:1129898680.495504.25600@.g44g2000cwa.googlegroups.com...
> We have 2 failover servers and one client in our test environment. We
> have all the three configured in mixed mode authentication(windows +
> sql server authentication). But when we are failing over from 1st
> server to 2nd one, we are getting the following error message,
> 'Unable to connected to server xxxx: Server : Msg 18452, Level 16,
> State 1 [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
> user 'null'. Reason: Not associated with a trusted SQL server
> connection.'
> I got some clue.
> For instance we have ser1 and ser2 as clusters. I registered both in
> the client's EM. Now what I did was, I made ser1 to run and stopped sql
> service in ser2 (active/passive) through failover. Now in the client's
> EM I'm able to open ser1 and I cannot access ser2. Now what I did was,
> I failed over to ser2 ( so sql service in ser1 is stopped). But now I
> can still be able to access ser1 and also I can access ser2, even I'm
> able to open query analyzer in ser1 through EM.But when I try to open
> query analyzer directly, it is giving the same error message. ser1 is
> the virtual name given to both ser1 and ser2. So I think when
> connecting through EM, failover is occuring fine.I'm just wondering why
> is this happening only with dsn. Can anybody help me?
> Thanks,
> Preethi
>

error: 18452; very urgent

We have 2 failover servers and one client in our test environment. We
have all the three configured in mixed mode authentication(windows +
sql server authentication). But when we are failing over from 1st
server to 2nd one, we are getting the following error message,
'Unable to connected to server xxxx: Server : Msg 18452, Level 16,
State 1 [Microsoft][ODBC SQL Server Driver][SQL Server]Login fai
led for
user 'null'. Reason: Not associated with a trusted SQL server
connection.'
I got some clue.
For instance we have ser1 and ser2 as clusters. I registered both in
the client's EM. Now what I did was, I made ser1 to run and stopped sql
service in ser2 (active/passive) through failover. Now in the client's
EM I'm able to open ser1 and I cannot access ser2. Now what I did was,
I failed over to ser2 ( so sql service in ser1 is stopped). But now I
can still be able to access ser1 and also I can access ser2, even I'm
able to open query analyzer in ser1 through EM.But when I try to open
query analyzer directly, it is giving the same error message. ser1 is
the virtual name given to both ser1 and ser2. So I think when
connecting through EM, failover is occuring fine.I'm just wondering why
is this happening only with dsn. Can anybody help me?
Thanks,
Preethihttp://support.microsoft.com/defaul...kb;en-us;555332
"sqldbapree" <mohanpreethi0125@.gmail.com> wrote in message
news:1129898680.495504.25600@.g44g2000cwa.googlegroups.com...
> We have 2 failover servers and one client in our test environment. We
> have all the three configured in mixed mode authentication(windows +
> sql server authentication). But when we are failing over from 1st
> server to 2nd one, we are getting the following error message,
> 'Unable to connected to server xxxx: Server : Msg 18452, Level 16,
> State 1 [Microsoft][ODBC SQL Server Driver][SQL Server]Login f
ailed for
> user 'null'. Reason: Not associated with a trusted SQL server
> connection.'
> I got some clue.
> For instance we have ser1 and ser2 as clusters. I registered both in
> the client's EM. Now what I did was, I made ser1 to run and stopped sql
> service in ser2 (active/passive) through failover. Now in the client's
> EM I'm able to open ser1 and I cannot access ser2. Now what I did was,
> I failed over to ser2 ( so sql service in ser1 is stopped). But now I
> can still be able to access ser1 and also I can access ser2, even I'm
> able to open query analyzer in ser1 through EM.But when I try to open
> query analyzer directly, it is giving the same error message. ser1 is
> the virtual name given to both ser1 and ser2. So I think when
> connecting through EM, failover is occuring fine.I'm just wondering why
> is this happening only with dsn. Can anybody help me?
> Thanks,
> Preethi
>

error: 18452; very urgent

We have 2 failover servers and one client in our test environment. We
have all the three configured in mixed mode authentication(windows +
sql server authentication). But when we are failing over from 1st
server to 2nd one, we are getting the following error message,
'Unable to connected to server xxxx: Server : Msg 18452, Level 16,
State 1 [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user 'null'. Reason: Not associated with a trusted SQL server
connection.'
I got some clue.
For instance we have ser1 and ser2 as clusters. I registered both in
the client's EM. Now what I did was, I made ser1 to run and stopped sql
service in ser2 (active/passive) through failover. Now in the client's
EM I'm able to open ser1 and I cannot access ser2. Now what I did was,
I failed over to ser2 ( so sql service in ser1 is stopped). But now I
can still be able to access ser1 and also I can access ser2, even I'm
able to open query analyzer in ser1 through EM.But when I try to open
query analyzer directly, it is giving the same error message. ser1 is
the virtual name given to both ser1 and ser2. So I think when
connecting through EM, failover is occuring fine.I'm just wondering why
is this happening only with dsn. Can anybody help me?
Thanks,
Preethi
http://support.microsoft.com/default...b;en-us;555332
"sqldbapree" <mohanpreethi0125@.gmail.com> wrote in message
news:1129898680.495504.25600@.g44g2000cwa.googlegro ups.com...
> We have 2 failover servers and one client in our test environment. We
> have all the three configured in mixed mode authentication(windows +
> sql server authentication). But when we are failing over from 1st
> server to 2nd one, we are getting the following error message,
> 'Unable to connected to server xxxx: Server : Msg 18452, Level 16,
> State 1 [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
> user 'null'. Reason: Not associated with a trusted SQL server
> connection.'
> I got some clue.
> For instance we have ser1 and ser2 as clusters. I registered both in
> the client's EM. Now what I did was, I made ser1 to run and stopped sql
> service in ser2 (active/passive) through failover. Now in the client's
> EM I'm able to open ser1 and I cannot access ser2. Now what I did was,
> I failed over to ser2 ( so sql service in ser1 is stopped). But now I
> can still be able to access ser1 and also I can access ser2, even I'm
> able to open query analyzer in ser1 through EM.But when I try to open
> query analyzer directly, it is giving the same error message. ser1 is
> the virtual name given to both ser1 and ser2. So I think when
> connecting through EM, failover is occuring fine.I'm just wondering why
> is this happening only with dsn. Can anybody help me?
> Thanks,
> Preethi
>

Error with linked server after failover

Hi all,

The following query that uses a linked server is giving me the error message below after I initiate a failover (ALTER DATABASE Northwind SET PARTNER FAILOVER).I have SQL Server 2005 SP2.I think that without the service pack there is another error too.

The query is run from a database other than northwind of course.

select * from DualLink.northwind.dbo.Test1

Please note that:

without a failover itworks perfectly

it always work if I try to run it a second time - only the first time it fails.

it fails the first time for each of the open connections. A new connection that was open after the failover will work fine.

A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)

A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)

The linked server is defined as

EXEC master.

dbo.sp_addlinkedserver

@.server = N'DualLink',

@.srvproduct=N'',

@.provider=N'SQLOLEDB',

@.catalog=N'northwind',

@.provstr=N'Server=(local);FailoverPartner=MyIPAddr;'

EXEC master.dbo.sp_addlinkedsrvlogin

@.rmtsrvname = 'DualLink',

@.useself = false,

@.locallogin = 'sa',

@.rmtuser = 'sa',

@.rmtpassword = 'MyPwd'

Thanks,

Avi

I am having the same problem except I don't have a linked server.

I am running SQL Server 2005 sp1 and Windows 2003 using clustering.

In addition to your symptoms I have noticed the following:

1. The error occurs when I make a query through Server Manager and when using a java app that queries a database using an ASP page. However, if I bring up our website as the first request after failover it works fine.

2. If I failover from Server1 to Server2 and don't make any requests while it is on Server2 and then failover back to Server1 I do not get the error. If I make any requests while it is on Server2 then the first request I make on Server1 after failing over will cause the error.

If you have solved the problem I would like to know how. If I find a solution I will post it here.

Blake