Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
My client is looking to migrate their BizTalk Server 2009 solution to BizTalk Server 2013 R2. The current solution uses the BizTalk Server adapter for Dynamics AX 4.0 to move data to and from AX. I have not found any recent information indicating whether or not the BizTalk Server adapter for Dynamics AX 4.0 is compatible with BizTalk Server 2013 R2. Does anyone have any information that can be shared.
Note that the client is looking to upgrade to Dynamics AX 2012 in the next 12 months or so.
this is a really interesting question. Can you please post any information here if you have got any.
We've some customers using this too.
Btw: Does your question aim to the compatibility of Ax40 BizTalkAdapter against an BT2013, or do you want to know, if any, if Ax2012 has compatibilty to any BT?
I have not seen any official note on this. Officially only AX2009 is certified with BizTalk 2013. Refer blogs.technet.com/.../compatibility-announcement-lync-2013-with-ax-2012-r2-and-ax-2012-biztalk-2013-with-ax-2009-sp1.aspx
Consolidated AX compatibility list is available in mbs2.microsoft.com/.../KBDisplay.aspx;en-us;2848872 (Requires partner source access)
The Dynamics AX 4.0 adapter can work with BizTalk Server 2013 R2. As noted in Daniel Hester post (http://geekswithblogs.net/danielh/archive/2012/02/29/148847.aspx), the adapter does not work in a 64-bit environment because the adapter executable is a 32-bit executable that is NOT marked as 32-bit only.
Follow the procedures below to get the Dynamic AX 4.0 adapter work in a 64-bit environment.
- This is an unsupported configuration. I would not recommend this configuration in production for the long term. This is more of a jury rig to buy the client time to complete their Dynamics AX upgrade.
- We were not able to establish a connection between BizTalk Server and Axapta using the adapter where the servers were in different data centers. We did not resolve this issue.
- Do not ask why some of the procedures are needed, just do it.
1. Using Regedit, change the version of the install BizTalk Server to the 2009 version number
a. Navigate to the BizTalk Server hive at Computer->HKEY_LOCAL_MACHINE->Software->Microsoft->BizTalk Server->3.0
b. Note the value of ProductVersion (126.96.36.199 for BizTalk Server 2013 R2)
c. Change ProductVersion to 3.8.368.0
- This will allow you to install the adapter.
2. Install Dynamics AX 4.0 SP1 and SP2 to the default location.
3. Using Regedit, restore the original value ProductVersion from step 1.
4. Apply fix from Daniel Hester's post:
a. Stop at host instances
b. Copy and paste the entire install folder (C:\Program Files (x86)\Microsoft Dynamics AX) to C:\Program Files).
c. Give the BizTalk Server host user group write access to the folder C:\Program Files\Microsoft Dynamics AX.
d. Navigate to the Dynamics AX 4.0 Bin folder (C:\Program Files (x86)\Microsoft Dynamics AX\4.0\Client\Bin).
e. Copy and paste the executable file AxAifRemSrv.exe to the Desktop (C:\Users\<username>\Desktop) or to any other local folder.
f. Open up a Visual Studio 2013 Command Prompt in administrator mode, and navigate to the folder specified above.
g. Execute the following command on the axaifremsrv.exe: corflags axaifremsrv.exe /32BIT+ /Force
h. Confirm the the 32BITREQ flag is set by running command: corflags axaifremsrv.exe
i. Copy and paste the executable axaifremsrv.exe from the desktop to both the Program Files and Program Files (x86) locations.
C:\Program Files (x86)\Microsoft Dynamics AX\40\Client\Bin
C:\Program Files\Microsoft Dynamics AX\40\Client\Bin
j. Restart instances
5. Set Firewall rules:
a. Inbound rule allowing axaifremsrv.exe
b. inbound rule allowing port 2712
c. outbound rule allowing port 2712
GREAT post. Where the hell did you get this information from.
In the original solution, I stated that we could not verify that the Dynamics AX 4.0 adapter works in the scenario where the BizTalk Server application server and the Dynamics AX 4.0 server are in different data centers within the same domain. Since that post, the IT folks were able to fix an issue related to IP address translation between the two data centers (I am not a systems guy...), so I can verify that the Dynamics AS X 4.0 adapter works just fine in this scenario. Of course, latency is another issue.
This information was tribal knowledge spread over several very busy colleagues. For them it was trial and error. It took some work to get all of the stars aligned.
Business Applications communities