Hello,

In our prod environment, we pump in large amount of transactions through the
 Biztalk Orchestration, which depends on few external interfaces.  we keep g
etting the following errors frequently, some times it goes up to more than 1
00 a day

[0x8004e024] The XLANG schedule activation timed out.
[0x0159] The server encountered a transport error while processing the m
essaging port "XXXXXXX", which uses a transport component with a ProgID of "
BizTalk.BPOActivation.1".

[0x012b] A transmission attempt failed.

We are running the orchestration with the option, Xlang Schedule has the Tra
nsaction and not as COM+.  Does this setting have any effect on this error?
We dont have any transaction in the orchestration. We tried increasing the C
OM+
activation for this particular Xlang Pool, even that is also not helping muc
h.

Any help to resolve the same and finding out the root cause, would be really
appeciated.

Thanks in advance,
shankar

[ Post a follow-up to this message ]

Shankar,

I have the exact same problem which I have just started to research.  So far
I have not found a solution.

Phil

"Shankar" <Shankar@discussions.microsoft.com> wrote in message
news:AB3CEC0B-98F3-4770-A92E-608DB7BA09E7@microsoft.com...
> Hello,
>
>   In our prod environment, we pump in large amount of transactions through
the Biztalk Orchestration, which depends on few external interfaces.  we
keep getting the following errors frequently, some times it goes up to more
than 100 a day
>
>  [0x8004e024] The XLANG schedule activation timed out.
>  [0x0159] The server encountered a transport error while processing the[/vbcol
]
messaging port "XXXXXXX", which uses a transport component with a ProgID of
"BizTalk.BPOActivation.1".[vbcol=seagreen]
>
>  [0x012b] A transmission attempt failed.
>
> We are running the orchestration with the option, Xlang Schedule has the
Transaction and not as COM+.  Does this setting have any effect on this
error?
> We dont have any transaction in the orchestration. We tried increasing the
COM+
> activation for this particular Xlang Pool, even that is also not helping
much.
>
> Any help to resolve the same and finding out the root cause, would be
really
> appeciated.
>
> Thanks in advance,
> shankar
>

[ Post a follow-up to this message ]

Phil,

Microsoft is recommending this Post service pack 4, COM+ hot fix to
resolve the problem.  http://support.microsoft.com/?id=822618.
Hopefully this should take care of some of the Xlang schedule
activation problem.

Thanks,
Shankar




"Phil Lodwick" <phil_lodwick@hotmail.com> wrote in message news:<10h2209bm07ed65@news.supern
ews.com>...[vbcol=seagreen]
> Shankar,
>
> I have the exact same problem which I have just started to research.  So f
ar
> I have not found a solution.
>
> Phil
>
> "Shankar" <Shankar@discussions.microsoft.com> wrote in message
> news:AB3CEC0B-98F3-4770-A92E-608DB7BA09E7@microsoft.com... 
> the Biztalk Orchestration, which depends on few external interfaces.  we
> keep getting the following errors frequently, some times it goes up to mor
e
> than 100 a day 
> messaging port "XXXXXXX", which uses a transport component with a ProgID o
f
> "BizTalk.BPOActivation.1". 
> Transaction and not as COM+.  Does this setting have any effect on this
> error? 
>  COM+ 
>  much. 
>  really 

[ Post a follow-up to this message ]

Shankar,

Thanks for the information.  Unfortunately when I apply this hotfix things
get worse instead of better.  The frequent warnings that you mention below
are still there.  Along with those I now see these errors for the first
time:

Event Type: Error
Event Source: XLANG Scheduler
Event Category: Engine
Event ID: 12315
Date:  8/23/2004
Time:  3:01:44 PM
User:  N/A
Computer: TEST
Description:
There is a problem with the data-flow specification. A message that is
indicated as a source of data does not currently exist while this XLANG
schedule is running. Detailed information is provided in the following
message.

Port name:  oprtMSMQ
Message name: 'oprtOutbound'
Field: Document
Data flow from message: TestRequestReceive_out

Module name: skdTest
Module ID: {3BA784C7-5A51-4045-A631-A6E005F96BFD}
Instance ID: {3D690F32-A783-4DC3-9C6F-C1A8739DDFEB}


Error Code = 0x80004005 : Unspecified error

XLANG Scheduler Engine Internals Information:
File:  e:\bizetsp\private\sked\src\runtime\exec
ctxt\messageinstance.cpp
Line: 645


"siva sanks" <sivasanks@gmail.com> wrote in message
news:ec0b1398.0408060524.2cedf98@posting.google.com...
> Phil,
>
> Microsoft is recommending this Post service pack 4, COM+ hot fix to
> resolve the problem.  http://support.microsoft.com/?id=822618.
> Hopefully this should take care of some of the Xlang schedule
> activation problem.
>
> Thanks,
> Shankar
>
>
>
>
> "Phil Lodwick" <phil_lodwick@hotmail.com> wrote in message
news:<10h2209bm07ed65@news.supernews.com>...[vbcol=seagreen] 
far[vbcol=seagreen] 
through[vbcol=seagreen] 
more[vbcol=seagreen] 
the[vbcol=seagreen] 
of[vbcol=seagreen] 
the[vbcol=seagreen] 
the[vbcol=seagreen] 
helping[vbcol=seagreen] 

[ Post a follow-up to this message ]