| rforsha@hotmail.com 2005-03-24, 5:50 pm |
| I was having a similar problem with sheduling task using the .NET
eConnect API and this was a fix! Thanks Russ!
Russ Larrivee wrote:[vbcol=seagreen]
> The reason this is happening is because there are a couple
> of Biztalk COM+ components which use the interactive user
> by default. (I have no idea why MS would do this).
>
> What you have to do is go into Components Services and
> change the identity of the following COM+ applications:
>
> Biztalk Server Interchange Application
> XLang Scheduler
>
> If you are using Biztalk Server 2002 then you'll need to
> do this COM+ component too:
>
> XLang Schedule Pool
>
> Make sure the user is granted the Biztalk Server
> Administrator group.
>
> Regards,
>
> Russ
>
>
> Biztalk Databases &
> NOT Physically
> physically logged
> Terminal Services the
> Microsoft BizTalk
> Here is the list:
> have tried changing
> seemed to make a
> the machine.
> component that is
> information is provided in
> started because
> and password.
> COMBinder.cpp
|