Hi Pandit,
Just checking if this is already solved. If not, I suggest the following.
1) Restart Biztalk Service and rerun your scnenario and see if the problem
still persist.
2) If so, provide me witht the details of the following:
a) The whole error and warning in event log pertaining to the TDDS.
b) please check to ensure that you have the BAMPrimaryImport database
c) please check the BizTalkMgmtDb the TDDS_Destinations tables the
content of the connection column and let me know what they are.
d) Also, let me know your scenario, what are you using to enable BAM
Tracking, e.g. thru deployment of TPE tracking profile or you
programmatically write EventStream code. Provide any specific info here
would be helpful as well, as if using BufferedEventStream, what is the
connection string used in the constructor.
Thanks,
Keith Lim [MSFT]
--------------------
<ujp1sXJOGHA.1124@TK2MSFTNGP10.phx.gbl>
TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA
03.phx.gbl
January/2006....
or
http://vamsibiztalk.blogspot.com/2006/01/list-of-various-bam-questions.html
could
BAMPrimaryImport.Parameter is
Thanks,
Keith Lim [MSFT]
My BizTalk BAM Blog: http://blogs.msdn.com/keithlim/default.aspx
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
|