|
Home > Archive > Commerce Server General > September 2004 > Timeout Expired when executing Custom Queries from Bizdesk
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Timeout Expired when executing Custom Queries from Bizdesk
|
|
|
| Hi all. We are running Commerce Server 2000 (SP3) on Windows 2000 Server
(SP4). When executing custom queries from within Bizdesk, we will often
receive the following error:
Microsoft OLE DB Provider for SQL Server error '80040e31'
Timeout expired
The same query may run fine several attempts later, but most of the time it
seems to encounter the timeout. Has anyone encountered this before? I am
wondering what SQL database(s) or resources are being accessed when these
queries are run. And, are there any settings or parameters which need to be
configured on the SQL server side to optimize things like connection pools,
# incoming connections, timeouts, etc. I would apreciate hearing any ideas
or comments.
Thanks in advance.
| |
| Vinayak Tadas[MSFT] 2004-09-09, 5:52 pm |
| You should look at sql profiler trace to see which queries are taking time.
--------------------
From: "Jim" <galax1an@hotmail.com>
Subject: Timeout Expired when executing Custom Queries from Bizdesk
Date: Wed, 1 Sep 2004 15:02:20 -0400
Lines: 18
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Message-ID: <#zjI2YFkEHA.2812@tk2msftngp13.phx.gbl>
Newsgroups: microsoft.public.commerceserver.general
NNTP-Posting-Host: bi-02pt1.bluebird.ibm.com 129.42.208.182
Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13
.phx.gbl
Xref: cpmsftngxa10.phx.gbl microsoft.public.commerceserver.general:14696
X-Tomcat-NG: microsoft.public.commerceserver.general
Hi all. We are running Commerce Server 2000 (SP3) on Windows 2000 Server
(SP4). When executing custom queries from within Bizdesk, we will often
receive the following error:
Microsoft OLE DB Provider for SQL Server error '80040e31'
Timeout expired
The same query may run fine several attempts later, but most of the time it
seems to encounter the timeout. Has anyone encountered this before? I am
wondering what SQL database(s) or resources are being accessed when these
queries are run. And, are there any settings or parameters which need to be
configured on the SQL server side to optimize things like connection pools,
# incoming connections, timeouts, etc. I would apreciate hearing any ideas
or comments.
Thanks in advance.
Thanks
Vinayak Tadas
Microsoft
http://blogs.msdn.com/vinayakt
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2002 Microsoft Corporation. All rights
reserved.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Get Secure! For more info visit http://www.microsoft.com/security. Please
reply to the newsgroups only. Thanks
|
|
|
|
|