RE: Machine x receives results meant for machine y
- From: Nick <SaintNick@xxxxxxxxxxxxx>
- Date: Mon, 3 Mar 2008 07:01:02 -0800
Hi Charles,
do you know if an ADO connection knows its process id (SPID), and whether
it's exposed at runtime so we can log it? I can't find it anywhere.
Regards, Nick
"Charles Wang[MSFT]" wrote:
Hi Nick,.
I will discuss this with WenYuan, since I did not hear that before.
Personally I do not think that it is possible, if so, it is a serious issue
of ADO.NET.
SQL Profiler is helpful for tracing this issue, though it may impact your
SQL Server performance at that time. However if this issue can be easily
reproduced, you may arrange a not busy time to do this. I am not an expert
of ASP.NET, after I consulted some ASP.NET engineer, I know that ASP.NET
Web farm is working in a load balanced environment, right?
If so, I would like to ask you a question:
Since your two web servers were in the same web farm, how did you know that
the original query request was from your Web Server 1, but not Web Server
2?
You may also check if this issue was related to session state management in
your web farm:
Session-State Modes
http://msdn2.microsoft.com/en-us/library/ms178586.aspx
PRB: Session State Is Lost in Web Farm If You Use SqlServer or StateServer
Session Mode
http://support.microsoft.com/kb/325056
Please feel free to let me know if you have any other questions or
concerns. Have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================
- Follow-Ups:
- RE: Machine x receives results meant for machine y
- From: Charles Wang[MSFT]
- RE: Machine x receives results meant for machine y
- Prev by Date: Re: SQL Server 2000 SP4 client connection problem
- Next by Date: Re: SQL 2005 connectivity error
- Previous by thread: Re: SQL Server 2000 SP4 client connection problem
- Next by thread: RE: Machine x receives results meant for machine y
- Index(es):
Relevant Pages
|