web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

"Failed to initialize the managed interoperability layer of Microsoft Dynamics AX."

(0) ShareShare
ReportReport
Posted on by 970

Hello,

My .NET application utilizes the .NET Business Connector to interface with Dynamics AX.

I'm receiving the following error on the LogonAs function:

"Failed to initialize the managed interoperability layer of Microsoft Dynamics AX."

I was able to get the .NET Business Connector to work previously on a different deployment and I never got this error. I'm not really sure how to debug this one.

Any ideas?

*This post is locked for comments

I have the same question (0)
  • Community Member Profile Picture
    on at

    hi,

    got same issue no; were you maybe able to resolve pls?

    regards

    Tomasz

  • Verified answer
    Tommy Skaue Profile Picture
    Microsoft Employee on at

    Please try install the Business Connector on the server side.

    See here:

    community.dynamics.com/.../155794.aspx

  • bdzevel Profile Picture
    970 on at

    To be perfectly honest, I did end up solving this issue, but I can't remember how, exactly.

    I remember installing the .NET connector on the server, but I don't remember if that resolved our problems.

  • Community Member Profile Picture
    on at

    thanks; just to be sure:

    - businessconnectornet - is it some component available on AX installation CD, correct?

    - read it should be installed on web server - in this case by web server acts project server, correct?

    regards

    Tomasz

  • bdzevel Profile Picture
    970 on at

    .NET Business Connector is a component in the installation media.

    He meant, you should install it on the server hosting your AOS (I think).

  • Community Member Profile Picture
    on at

    just checked - seems it is already installed on server where AOS is running; so still, any other ideas where problem can be with AX<->PS integration? any suggestion appreciated..

  • Tommy Skaue Profile Picture
    Microsoft Employee on at

    Can you check to see if the Business Connector is on the same version as your AOS Service. Business Connector will have a kernel version, just as the client and the service.

    One way to check is to head over to the bin folder holding the binaries, sort the files by date descending, find a dll with the Microsoft.Dynamics-namespace, open properties and look at details. This applies both to the location holding the Business Connector binaries and the Server AOS binaries.

    Is your .Net app utilizing its own copy of the Business Connector dll?

  • Community Member Profile Picture
    on at

    Tommy,

    Thanks for your answer; in the meantime, being desperated, I've installed business connector on project server as well - and voila, seems it did the job; if someone else would face similar problem, then answer would be that net business connector needs to be installed but not only on AOS, but on project server as well; will try to configure synchronization now, let you know shortly if it is (or not) working.

    Thanks for your help again.

    regards

    t

  • Community Member Profile Picture
    on at

    ..sems I was too happy again :) last (hopefully) problem now is:

    - sync service working fine on project server; queue is available and visible there (IP is .191)

    - sync service is not starting on AX server (IP is .190); message from error log is as below:

    ----

    ---ERROR MESSAGE---

    An error occurred while starting the synchronization service

    ---MORE DETAILS---

    There was an error opening the queue. Ensure that MSMQ is installed and running, the queue exists and has proper authorization to be read from. The inner exception may contain additional information.

    An error occurred while opening the queue:The queue does not exist or you do not have sufficient permissions to perform the operation. (-1072824317, 0xc00e0003). The  message cannot be sent or received from the queue. Ensure that MSMQ is installed and running. Also ensure that the queue is available to open with the required access mode and authorization.

    ---STACK TRACE---

      at System.ServiceModel.Channels.MsmqVerifier.VerifyReceiver(MsmqReceiveParameters receiveParameters, Uri listenUri)

      at System.ServiceModel.Channels.MsmqTransportBindingElement.BuildChannelListener[TChannel](BindingContext context)

      at System.ServiceModel.Channels.BindingContext.BuildInnerChannelListener[TChannel]()

      at System.ServiceModel.Channels.MessageEncodingBindingElement.InternalBuildChannelListener[TChannel](BindingContext context)

      at System.ServiceModel.Channels.BinaryMessageEncodingBindingElement.BuildChannelListener[TChannel](BindingContext context)

      at System.ServiceModel.Channels.BindingContext.BuildInnerChannelListener[TChannel]()

      at System.ServiceModel.Channels.Binding.BuildChannelListener[TChannel](Uri listenUriBaseAddress, String listenUriRelativeAddress, ListenUriMode listenUriMode, BindingParameterCollection parameters)

      at System.ServiceModel.Description.DispatcherBuilder.MaybeCreateListener(Boolean actuallyCreate, Type[] supportedChannels, Binding binding, BindingParameterCollection parameters, Uri listenUriBaseAddress, String listenUriRelativeAddress, ListenUriMode listenUriMode, ServiceThrottle throttle, IChannelListener& result, Boolean supportContextSession)

      at System.ServiceModel.Description.DispatcherBuilder.BuildChannelListener(StuffPerListenUriInfo stuff, ServiceHostBase serviceHost, Uri listenUri, ListenUriMode listenUriMode, Boolean supportContextSession, IChannelListener& result)

      at System.ServiceModel.Description.DispatcherBuilder.InitializeServiceHost(ServiceDescription description, ServiceHostBase serviceHost)

      at System.ServiceModel.ServiceHostBase.InitializeRuntime()

      at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout)

      at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)

      at Microsoft.Dynamics.SyncServices.SyncServiceBase.OnStart(String[] args)

    ----

    and status on .190 is:

    - message queuing service is running there

    - there is not any queue configured (I believe it is ok, only one should be configured on project server - correct?)

    - AX setup related to synchronization is not working, throwing same error as above; I guess it just starts windows synchronization service, am I right? and if so, there is no need to do anything in AX until synchronization service will start to work, correct?

    ..and if so, what may be the reason sench service is not starting on .190?

    regards

    t

  • Community Member Profile Picture
    on at

    ..and latest details; sync service working fine, all compnents seems to be ok, I am trying now to setup synchronization, and here is a problem - as on picture below

    maybe somebody could advice where error ;..The version of MSMQ cannot be detected..; comes from? suggestions I found in internet does not seem to be the case here :(

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
CP04-islander Profile Picture

CP04-islander 24

#2
Michel ROY Profile Picture

Michel ROY 14

#3
Jagadabi Profile Picture

Jagadabi 6

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans