You’re offline. This is a read only version of the page.
58
Hi everyone,
I’m currently facing a critical issue after deploying a working AIF web service from our test environment to production in Dynamics AX 2012 R3. I would greatly appreciate any guidance or suggestions from the community.
In our test environment, I created a custom AIF service, configured the service group, and successfully tested it. All operations, including SOAP requests and responses, worked as expected.
After validating the service in the test environment, I moved the exact same AIF service objects to the live (production) environment. This includes:
Service class and data contracts
Service node
Service group deployment
Once deployed in production, the service fails to start. Every time I try to access the service URL, the IIS Application Pool for MicrosoftDynamicsAXAif60 automatically goes into a “Stopped” state.
Event Viewer logs provide the following error:
I also noticed similar duplicate type errors referencing other custom classes prefixed with XXX_ in the same assembly.
So far, I have attempted the following standard solutions to fix the problem:
Stopped IIS and AOS services on the production server.
Deleted the relevant records from the SYSXPPASSEMBLY table in SQL for the affected objects.
Performed full CIL compilation (both incremental and full compilation) to refresh the assemblies.
Redeployed the service group through AOT.
Restarted AOS and IIS to apply all changes.
Despite these steps, the issue persists. The IIS Application Pool still stops immediately, and the duplicate type error continues to appear.
The same service works perfectly in the test environment with the exact same configuration and code.
I have checked the AOT for duplicate class names and there are no manually duplicated classes.
The production environment is running Dynamics AX 2012 R3 (6.3.6000.149) with .NET Framework 4.8.
The AOS and IIS are on the same server.
Has anyone encountered this duplicate type error when moving a service from test to production?
Could there be hidden assembly or IL conflicts causing IIS to crash?
Are there any additional steps I should take to completely remove the duplicate type and get the AIF service running in production?
Could this be related to XppIL cache, model conflicts, or leftover test environment artifacts?
Any help, hints, or detailed instructions on how to resolve this would be greatly appreciated 🙏
Share
Report
All responses (
Answers (
