Share
Report
70We are integrating AX 2009 with a few client home grown applications using the
.NET business connector. For connecting to AX, I am using the logonAs function
with the appropriate parameters. There are three home grown applications. I will
call these applications A1, A2 and A3.
The 'dll's of the C# scripts in which
I am logging in to AX and processing further, are kept in a
server.
Application A1 is working fine under all the
circumstances.
Application A2 runs fine IF application A3 is not trying
to connect to AX.
If A3 is already connected to AX, A2 throws an error 'The
requested operation cannot be performed because you are not logged on to
Microsoft Dynamics.' or 'The logon failed because the logon parameters do not
match those currently being used in Business Connector'. I am properly logging
off from AX at the end of the script using AX.logoff() but this logs off only
the web user session not the business connector session(which I think is the
normal functionality).
Similarly, IF A2 is already connected to AX, A3
shows the same error.
Sometimes, reseting IIS solves the problem and one
of the two is able to connect. Whichever application tries to connect first, it
gets connected while the other application faces the errors.
The server
hosting the dlls has a business connector installed, configured properly
pointing to the correct AOS.
All this while, A1 keeps running parallely
without any issues.
One more information : A1 is hosted in a different
server while A2 and A3 are hosted in the same server where the dlls are. All the
three are IIS web applications.
Please suggest. This is a critical stage
of the project.
*This post is locked for comments
All responses (
Answers (
