As we can see from the picture the problem is related with an insertion of a duplicated key row of index CIX Tracking Message References. After a brief search in the web I found some helping info:KB 936124.
As we can see from link the resolution was to "select the Ignore duplicate values check box"* from Options menu of the target index (CIX_TrackingMessageReferences). After this change I stop having this type of error, however this was not enough because HAT stop working and I couldn't see tracked messages/orchestrations/pipelines anymore.
Finally I decided to "unconfigure" the BTS2006, to delete the DBs of BTS and reconfigure it from scratch. Of course this resolved all my problems.
* = To select this check box I had to 1) unselect the "unique index" check box, then 2) select the "ignore duplicated values" check box and finally 3) re-select the "unique index" check box.
Update (04 May 2008):
After less than a week the problem returned, this time I decided not to reconfigure the Biztalk. I tried once again the solution mentioned in this post, and this time it worked. The solution managed to correct the problem related with the index and I still have HAT running good. Conclusion: The other time something else mess up HAT.
Update (19 May 2008):
More useful information:
http://support.microsoft.com/kb/936124
http://support.microsoft.com/kb/936894/
http://support.microsoft.com/kb/917845/
No comments:
Post a Comment