Recently we figured out that when you are installing a Dynamics AX 2009 Application Object Server (AOS) on a Windows Server 2008, that has the Windows Firewall turned on and you are trying to connect with a Dynamics AX 2009 client to the new Dynamics AX 2009 AOS, the Client is unable to connect. Also any applications using the business connector fail.
The reason for this is, that when you install an AOS on Windows Server 2008/2008 R2, the AX setup automatically creates a Windows Firewall rule for you. However the firwall rule created is incorrect as it does not point to the correct name of teh AOS service,ax32serv.exe, and hence the rule is not applied and therefore the Windows Firewall blocks access to the AOS service.
Some sample error message that you might get, for example when trying to install Reporting Extensions and .NET Business Connector is given in the attached screenshot. The error will be along the lines:
On Screen:
In the DynamicsSetupLog.txt file:
MSI file: Components64.msi Installed: True
MSI file: ClientHelp.msi Installed: False
Previously Installed Component: .NET Business Connector
Property RunMode set to: ‘AddRemoveFeatures’
=== Checking parameters ===
Property InstallPath set to: ‘C:\Program Files\Microsoft Dynamics AX\50’
Property InstallPath32Bit set to: ‘C:\Program Files (x86)\Microsoft Dynamics AX\50’
Property RemoveComponents set to: ‘0’
Property BypassWarnings set to: ‘0’
Entering method GetBusinessConnectorProxyAccount
An error has occured while Setup was establishing a connection through Business Connector. Error: No .NET Business Connector session could be found.
Leaving method GetBusinessConnectorProxyAccount
An error has occured while Setup was establishing a connection through Business Connector. Error: No .NET Business Connector session could be found.
Microsoft.Dynamics.Framework.Deployment.Web.EPWebException
In the Windows Application Event log:
Event ID: 1000
Level: Error
Description:
Dynamics Adapter Logon failed.Connection with the Application Object Server could not be established.Microsoft.Dynamics.BusinessConnectorNet.LogonFailedException at Microsoft.Dynamics.BusinessConnectorNet.Axapta.Logon(BC_PROXY_ACCOUNT_INFO* pBCProxyAccountInfo, String company, String language, String objectServer, String configuration)
at Microsoft.Dynamics.BusinessConnectorNet.Axapta.Logon(String company, String language, String objectServer, String configuration)
at Microsoft.Dynamics.Framework.BusinessConnector.Session.DynamicsAdapter.Logon(String company, String language, String objectServer, String configuration)
You can resolve this issue by manually correcting the Windows Firewall Rule created for each of your AOS instances:
1. 1n Windows click Start -> Administrative Tools -> Windows Firewall with Advanced Security” or run WF.msc
2. Click on “Inbound Rules”
3. Locate the rule starting with the words “Dynamics AX 5.0…” and double-click on it to open its properties
4. Click on the “Programs and Services” tab
5. Correct the text field specified for the radio button “This program” by adding the missing “.exe” extension to the path to your AOS service application, ax32serv.exe, and click on OK.
For example on my test system I had the path specified as “C:\Program Files\Microsoft Dynamics AX\50\Server\ContosoTransDemoDataAx2009\Bin\Ax32Serv” and I modified it to “C:\Program Files\Microsoft Dynamics AX\50\Server\ContosoTransDemoDataAx2009\Bin\Ax32Serv.exe“, and then after a couple of seconds I was able to access the AOS service from a remote AX client/.NET Business Connector
| –author: | Anup Shah |
| –editor: | Anup Shah |
| –date: | 28/Apr/2009 |
| –last edited: | 12/Aug/2010 |
