Re: Handling Script Timeout when invoking ActiveX Object involving ADODB from ASP2.0 pages- SQL Client setting
From: Patrick (patl_at_reply.newsgroup.msn.com)
Date: 11/19/04
- Next message: freddy parra: "CONECCIONES CLIENTE SQL SERVER"
- Previous message: Mike MacSween: "Re: RADiest Client for SQL Server"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 19 Nov 2004 11:22:08 -0000
Sorted at last!
For educational purposes, I would like to advise the root cause of the
problem!
The SQL Client Network Utility on the remote SQL Server 2000 SP3a on Windows
2003 server (same network segment and domain as the WinXP) was set to use
TCP/IP followed by Named Pipes
I had to remove Named Pipes from the protocol enabled (it having a lower
priority than TCP/IP doesn't make a single bit of difference. I am
fowarding this info to the SQL newsgroup, just in case anyone is interested
and/or if it is a SQL Client BUG? I had similar problems before with
Microsoft Content Management Server(MCMS) 2002 SP1a, where by I had to use
TCP/IP (instead of Named Pipes) to get MCMS 2002 Scripted Site Deployment
using SDO working. Changing the prioirty makes no difference and had to
resolve using an alias that is TCP/IP or removing Named Pipes from the
enabled protocol
"Yan-Hong Huang[MSFT]" <yhhuang@online.microsoft.com> wrote in message
news:egzQzPezEHA.3152@cpmsftngxa10.phx.gbl...
> Hi Patrick,
>
> Thanks very much for the detailed information. I have also got your 2
> emails. :)
>
> Yes, after following the steps, I did reproduce the same error. The error
> message in the asp page on XP box is:
>
> Transactional Web Page
>
> --------------------------------------------------------------------------
-- > ---- > > This is an example of an Aborted Transaction. This transaction will abort > due to a Script Time-out error, which is an error that you could not trap > without a transaction. > > Please wait until the script times out... > > ERROR-2147168246 > New transaction cannot enlist in the specified transaction coordinator. > > If there is any miscommunication, please feel free to post here to let me > know. > > Based on my experiecne, under this situation, (MTS and SQL server in > different machines), MSDTC must be running on both machines and they must > be able to ping each other by NAME not IP address i.e. from a cmd prompt > type > ping machinename > If they can't then you will get a distributed transaction error message. So > please test above to make sure network has no problem. > > By the way, do you have any special settings between two machines? Such as > Firewall or something else? I suppost not, seems you mentioned they are in > the same network segment. > > Also, please check the following article: > "Event ID 12293: Transacted Commerce Server Pipeline Failure" > http://support.microsoft.com/?id=248403 > > It is not directly related to this problem. However, the troubleshooting > steps in it is quite useful under this situation. You can also check them > one by one on your side to fix it. Also, at the end of this article, you > can see a similar testing asp file. > > If the problem still can't be resolved yet, I am afraid that we may need to > contact Microsoft Product Support Service to trace DTC log to isolate the > problem. Thanks very much for your understanding. > > Best regards, > Yanhong Huang > Microsoft Community Support > > Get Secure! ¨C www.microsoft.com/security > Register to Access MSDN Managed Newsgroups! > -http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam. as > p&SD=msdn > > This posting is provided "AS IS" with no warranties, and confers no rights.
- Next message: freddy parra: "CONECCIONES CLIENTE SQL SERVER"
- Previous message: Mike MacSween: "Re: RADiest Client for SQL Server"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
