Discussion:
BizTalk 2009 issue
(too old to reply)
Tony
2009-08-27 01:24:01 UTC
Permalink
We have developed, deployed and tested BizTalk 2009 orchestrations on a dev
machine for integration with Dynamics AX2009 SP1. When we deploy these to our
UAT environment we can’t get the orchestrations to work. The following error
is reported in the event log “The adapter "Microsoft Dynamics AX 2009" raised
an error message. Details "The source was not found, but some or all event
logs could not be searched. Inaccessible logs: Security.".

The UAT machine appears to be configured correctly, but we cannot get things
working.

Physical Dev Machine (32-bit Windows XP)
BizTalk 2009
SQL Server 2005
AX2009 SP1 Business Connector and BizTalk Adapter
Visual Studio 2008

UAT environment running under VM Ware
VM BizTalk Server (64-bit Windows Server 2008)
BizTalk 2009
AX2009 SP1 Business Connector and BizTalk Adapter

VM SQL Server (64-bit Windows Server 2008)
SQL Server 2005

Has anyone got any ideas as to what might be wrong?
Pavel Stikhin
2011-06-14 16:30:24 UTC
Permalink
Hello

Colud You have found a solution to the issue?
I have actually the same problem and can find nothing to solve it.

Thanks
Pavel
Post by Tony
We have developed, deployed and tested BizTalk 2009 orchestrations on a dev
machine for integration with Dynamics AX2009 SP1. When we deploy these to our
UAT environment we can???t get the orchestrations to work. The following error
is reported in the event log ???The adapter "Microsoft Dynamics AX 2009" raised
an error message. Details "The source was not found, but some or all event
logs could not be searched. Inaccessible logs: Security.".
The UAT machine appears to be configured correctly, but we cannot get things
working.
Physical Dev Machine (32-bit Windows XP)
BizTalk 2009
SQL Server 2005
AX2009 SP1 Business Connector and BizTalk Adapter
Visual Studio 2008
UAT environment running under VM Ware
VM BizTalk Server (64-bit Windows Server 2008)
BizTalk 2009
AX2009 SP1 Business Connector and BizTalk Adapter
VM SQL Server (64-bit Windows Server 2008)
SQL Server 2005
Has anyone got any ideas as to what might be wrong?
Loading...