AX 2012 R2 client configuration utility is not opening
And when looking in to the event viewer log it shows the following error
Faulting application name: AxCliCfg.exe, version: 6.0.947.0, time stamp: 0x4e098703Faulting module name: KERNELBASE.dll, version: 6.1.7601.17651, time stamp: 0x4e21213cException code: 0xe0434352Fault offset: 0x000000000000cacdFaulting process id: 0x1244Faulting application start time: 0x01ce2abd220101d7Faulting application path: C:\Program Files\Microsoft Dynamics AX\60\BusinessConnector\Bin\AxCliCfg.exeFaulting module path: C:\Windows\system32\KERNELBASE.dllReport Id: 601ba348-96b0-11e2-afc2-5cf9dd759361
Any idea about why client configuration utility is not opening
can you also specify the operating system you are using? Which version of Windows?
I am using Windows 7 professional 64- bit OS
2 things to try:
a) reinstall client
b) reinstall .net framework
did you try run as administrator
it can work out sometimes
I have tried to completely remove AX and re install everything still it dint work
Also tried running as administrator still the configuration utility is not shown
And this is what is receive in the event viewer which shows the application client configuration utility crashes
Can you ping the AOS server?
can you open a telnet session to the AOS?
does the AX client it self work ok?
O have seen issues when SQL server was down, the server configuration took for ever to start.
I've had exactly the same (similar) problerm starting the Ax32.Exe client (but only on some machines). Didn't do anything beside installing a "new small program"
Can you please check if the Length of your Enviroment variable PATH exceeds 2048 ????
I never had beliebed that - but this was the real problem in my personal case.
After cutting the path - immediately everything runs fine.
This seems to be a known problem - even SAP client has similarentires within support database.
Your components are not properly upgraded. The error says your AXCliCfg is of the RTM version and not the R2 version.
Reinstall the business connector and make sure it is upgraded to the correct version: