Mombu the Microsoft Forum sponsored links

Go Back   Mombu the Microsoft Forum > Microsoft > BIZTALKSERVER (TECHNET) > TDDS failed to read from source database.
User Name
Password
REGISTER NOW! Mark Forums Read

sponsored links


Reply
 
1 6th September 08:14
gary
External User
 
Posts: 1
Default TDDS failed to read from source database.


Hi I am experiencing the following error:

TDDS failed to read from source database. SQLServer: U071606, Database:
BizTalkMsgBoxDb.Timeout expired. The timeout period elapsed prior to
completion of the operation or the server is not responding..

Trawling through the web I have found that this can be caused by sessions
hanging around on SQL. I have tried to kill as many processes as I could but
I still get this error.

Has anybody else had this or know how to resolve this issue?

Cheers,
Gary
  Reply With Quote


  sponsored links


2 28th September 03:18
garv&r
External User
 
Posts: 1
Default TDDS failed to read from source database.


Hi Gary,
I've no solution but 'm also having this problem did you get any resolution.
Slán
Gar
  Reply With Quote
3 28th September 03:18
gary
External User
 
Posts: 1
Default TDDS failed to read from source database.


Hi Gar,

After having killed off the sql sessions etc and restarted the server
numerous times I gave up and asked our IT guy if he new of any ideas. He said
try restarting the server so I did, telling him that I had tried this
numerous times before. But sods law meant that the only time our IT guy was
there it acutally worked after a reboot.

I haven't had the issue since but as to what caused it and why it suddenly
started working again remains a mystery to me.
  Reply With Quote
4 28th September 03:19
garv&r
External User
 
Posts: 1
Default TDDS failed to read from source database.


I'll give it a go you never know it just might work ;0) thanks for the quick
reply
  Reply With Quote
5 28th September 03:20
younes amar
External User
 
Posts: 1
Default TDDS failed to read from source database.


Hi,
are you doing message body tracking?
Y.
  Reply With Quote
6 29th September 03:23
marian drumea
External User
 
Posts: 1
Default TDDS failed to read from source database.


Hi gar,

This happened to me a couple of times. First, these are deadlocks on
the BizTalk management database (if I remember correctly) and they are
caused by heavy message tracking and, most likely, a recurrent error on
a busy flow. Gary is right that killing sessions will help you. You
should then take that further, because killing deadlocking processes
will get BizTalk functional enough to allow you to terminate instances
in HAT. Probably you will face a backlog of suspended messages with
errors. Also, make sure you stop the processing (orchestrations) before
that, otherwise you will have to do it several time before catching up.

This is a good set of steps to remember if and when this happens again.
Anyways, you should look into any original error, into reducing the
tracking, or maybe scaling up/out if this becomes a rule and happens
under normal cir***stances and if you really need all that tracking.

Thanks,

Marian
http://www.MarianDrumea.com/BizTalk
  Reply With Quote
7 29th September 03:24
garv&r
External User
 
Posts: 1
Default TDDS failed to read from source database.


Hi Marian, Younes, Gary,
Thanks for the help. Yes I had message body tracking on and lots of traffic
on a test system (probably overloaded). Here's what I had to do. Just in case
anyone else has this problem.

I turned off tracking using GlobalTrackingOption (see BTS dox)
Turned off message body tracking on everything. Through HAT
Pruned the tracking database - dtasp_PruneTrackingDatabase
Restarted BTS no problems or deadlocks
Turned back on GlobalTrackingOption
All is ok so far. So the lesson is be careful what you track.

Slán
Gar
  Reply With Quote


  sponsored links


Reply


Thread Tools
Display Modes




Copyright © 2006 SmartyDevil.com - Dies Mies Jeschet Boenedoesef Douvema Enitemaus -
666