|
Home > Archive > BizTalk Server > April 2006 > HAT Error executing Query on Tracking Database
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 |
HAT Error executing Query on Tracking Database
|
|
|
| Hello,
every time I run HAT Query/Messages sent in pass day OR
Query/Messages Received in pass day - I get the following
error: The following error occurred when executing your SQL Query on the
Tracking Database: Timeout Expired
Can someone please tell me how to fix this.
Thanks in advance for your help!!!
--
mj
| |
| Eric Stott 2006-04-27, 7:25 am |
| Check the event log, I think that it gives a more descriptive error.
Eric
http://stottcreations.com/blog
"mj" <mj@newsgroup.nospam> wrote in message
news:95E6CEA7-4CFC-481F-80FE-DA3C9CC7C459@microsoft.com...
> Hello,
> every time I run HAT Query/Messages sent in pass day OR
> Query/Messages Received in pass day - I get the following
> error: The following error occurred when executing your SQL Query on the
> Tracking Database: Timeout Expired
>
> Can someone please tell me how to fix this.
>
> Thanks in advance for your help!!!
> --
> mj
| |
| Eric Stott 2006-04-27, 7:25 am |
| We had this same issue before and if memory serves me correct, it was a
permissions issue.
Eric
http://stottcreations.com/blog
"mj" <mj@newsgroup.nospam> wrote in message
news:95E6CEA7-4CFC-481F-80FE-DA3C9CC7C459@microsoft.com...
> Hello,
> every time I run HAT Query/Messages sent in pass day OR
> Query/Messages Received in pass day - I get the following
> error: The following error occurred when executing your SQL Query on the
> Tracking Database: Timeout Expired
>
> Can someone please tell me how to fix this.
>
> Thanks in advance for your help!!!
> --
> mj
| |
| Alan Smith 2006-04-27, 7:25 am |
| Hi mj,
Thiss tendt to occur when you have a large amount of data in the tracking
database. Check the size of the BizTalkDTADb, if it is larger than 1 GB, this
is probaably the cause. If so, you should look at installing andd running the
PruneTrackingDb stored porcedure, and scheduling a job in SQL Server Agent to
keep the tracking database to a reasonable size.
Regards,
ALan
--
The Bloggers Guide to BizTalk
http://geekswithblogs.com/asmith
"mj" wrote:
> Hello,
> every time I run HAT Query/Messages sent in pass day OR
> Query/Messages Received in pass day - I get the following
> error: The following error occurred when executing your SQL Query on the
> Tracking Database: Timeout Expired
>
> Can someone please tell me how to fix this.
>
> Thanks in advance for your help!!!
> --
> mj
| |
| Paul Somers 2006-04-27, 7:25 am |
| It is what it says it is, a time out issue, As with database lots of data
can make a query take long to return, and HAT will time out in this
scenario.
There is a registry setting:
HKEY_CURRRENT_USER\Software\Microsoft\Bi
zTalk
Server\3.0\Tracking\ConnectionTimeout
ConnectionTimeout is a dword, set it to 0 and it will never time out, you
can also set it to 100 or 500 to increase the time out so it will time out,
but after a longer period. Restart hat to have it effected.
However, there could be a larger issue here, check the size of your DTA
database. If its massive you should purge it, and trim it. It is a potential
performance issue waiting to happen. Post SP1 there was a hotfix to allow
you to do this. In 2006 its supposed to be a lot easier, have not tried it
yet.....
Paul.
"Eric Stott" <eric@stottcreations_nospam.com> wrote in message
news:%2393lNgPZGHA.3972@TK2MSFTNGP04.phx.gbl...
> We had this same issue before and if memory serves me correct, it was a
> permissions issue.
>
> Eric
> http://stottcreations.com/blog
>
> "mj" <mj@newsgroup.nospam> wrote in message
> news:95E6CEA7-4CFC-481F-80FE-DA3C9CC7C459@microsoft.com...
>
>
| |
|
| Hello,
Thank you all for your responses. I pretty much did what you all suggested.
I also ran the SQL Script Purge_DTADB.sql to create the sproc
dtasp_PruneTrackingDatabase etc. After I executed the script etc. HAT now
works like normal. I then created a scheduled job to run the script to clean
up the tracking database more frequently.
Thanks again for your quick responses and help!
--
mj
"Alan Smith" wrote:
[vbcol=seagreen]
> Hi mj,
>
> Thiss tendt to occur when you have a large amount of data in the tracking
> database. Check the size of the BizTalkDTADb, if it is larger than 1 GB, this
> is probaably the cause. If so, you should look at installing andd running the
> PruneTrackingDb stored porcedure, and scheduling a job in SQL Server Agent to
> keep the tracking database to a reasonable size.
>
> Regards,
>
> ALan
>
>
> --
> The Bloggers Guide to BizTalk
> http://geekswithblogs.com/asmith
>
>
>
> "mj" wrote:
>
| |
| WenJun Zhang[msft] 2006-04-27, 7:25 am |
| Glad to hear the problem has been resolved.
Just a side note, there is a known issue of dtasp_PruneTrackingdatabase
when the tracking database size is big. If you meet this problem, you can
contact our CSS to request the following hotfix which includes a new purge
stored produce(different to dtasp_PruneTrackingdatabase).
894253 FIX: The dtasp_PruneTrackingdatabase() stored procedure may take
many hours to clean up the DTA database in BizTalk Server 2004
http://support.microsoft.com/defaul...kb;EN-US;894253
Best regards,
WenJun Zhang
Microsoft Online Partner Support
This posting is provided "AS IS" with no warranties, and confers no rights.
|
|
|
|
|