BizTalk Server Orchestration - Error message when attempting to debug Orchestrations

This is Interesting: Free IT Magazines  
Home > Archive > BizTalk Server Orchestration > August 2004 > Error message when attempting to debug Orchestrations





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 Error message when attempting to debug Orchestrations
Dale Cantafio

2004-08-25, 5:53 pm

When I launch the Orchestration Debugger I get the following error message:
"Tracking database doesn't have any records about the selected service
instance yet."

Any ideas?
Christof [MVP]

2004-08-27, 6:06 pm

Is your SQL Agent enabled?

Best regards,
Christof

"Dale Cantafio" <dale@newsgroup.nospam> wrote in message
news:DF3E40D5-5DEF-4DF1-A704-F64A263CEF6E@microsoft.com...
> When I launch the Orchestration Debugger I get the following error

message:
> "Tracking database doesn't have any records about the selected service
> instance yet."
>
> Any ideas?



Dale Cantafio

2004-08-27, 6:06 pm

Solved our problem...

A custom pipline component that was being used in a custom pipeline by
another project had been installed using a BTSInstaller deployment package.
The dll was installed to the "C:\Program Files\Microsoft BizTalk Server
2004\Pipeline Components" and registered in the GAC. As it turns out, when
we removed the custome pipline component from the GAC the orchestration
debugger began to work again!

"Christof [MVP]" wrote:

> Is your SQL Agent enabled?
>
> Best regards,
> Christof
>
> "Dale Cantafio" <dale@newsgroup.nospam> wrote in message
> news:DF3E40D5-5DEF-4DF1-A704-F64A263CEF6E@microsoft.com...
> message:
>
>
>

Todd Sussman

2004-08-27, 6:06 pm

I know you can debug items in the GAC, or if you have a .net assembly
wrapped as a com\com+.

Todd

"Dale Cantafio" <dale@newsgroup.nospam> wrote in message
news:DE23A98A-B76E-4894-88CC-F7425FE6FB66@microsoft.com...[vbcol=seagreen]
> Solved our problem...
>
> A custom pipline component that was being used in a custom pipeline by
> another project had been installed using a BTSInstaller deployment
> package.
> The dll was installed to the "C:\Program Files\Microsoft BizTalk Server
> 2004\Pipeline Components" and registered in the GAC. As it turns out,
> when
> we removed the custome pipline component from the GAC the orchestration
> debugger began to work again!
>
> "Christof [MVP]" wrote:
>


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com