Comments on: Dynamics AX 2009 RU5 backwards compatibility problem

By: Klaas Deforche

Klaas Deforche — Tue, 19 Apr 2011 18:22:56 +0000

Very odd indeed, I’m glad you solved it.

By: Gonzalo Garcia

Gonzalo Garcia — Tue, 19 Apr 2011 17:06:54 +0000

Hello Klaas,

This issue was solved by reinstalling everything once again, I have to admit that it was a very odd situation. The good part is that now everything is working fine.

By: Klaas Deforche

Klaas Deforche — Wed, 02 Mar 2011 09:04:19 +0000

Hi Gonzalo,

That’s strange, if the versions are the same, everyting should work.
The only thing I can think of is removing the AUC and KTI files ( (C:\Documents and Settings\[USERNAME]\Local Settings\Application Data for XP, or C:\Users\USERNAME\AppData\Local for Vista/7)). I noticed some problems with those files after upgrading in the past.

Also, check the version info on ax32.exe and ax32serv.exe to be absolutely sure you have the correct versions. Also start you client bij clicking on ax32.exe instead of using a shortcut.

You are connecting to you local (HR5 upgraded) AOS, right? If you connect to an other AOS, this one should be HR5 too.

By: Gonzalo Garcia

Gonzalo Garcia — Tue, 01 Mar 2011 20:54:38 +0000

We recently updated to RU5 in our company, and this problem showed up, and as Klass suggest, the solution is to make both client and server the same version.

But now I am facing a weird problem, I updated my local development environment to RU5 (5.0.1500.2985) both client and server and the problem remains, i have reinstalled everything (Client, AOS and App files) from zero and when I tried to run the upgrade again the installer told me that there was nothing to be updated.

I am basically stuck with this. Any of you guys have an idea about what is going on?

Regards,
Gonzalo

By: Klaas Deforche

Klaas Deforche — Thu, 23 Dec 2010 18:45:18 +0000

Hi Ajit,

The solution is to use the same version for your client and you server. So if you have updated you server, apply the same update to all clients.

Regards.

By: Ajit

Ajit — Thu, 23 Dec 2010 14:02:13 +0000

Is any one has permanent solution of this issue?

By: JimChw

JimChw — Tue, 02 Nov 2010 15:35:50 +0000

Back in 3.0, the app and kernel versions had to be the same, but then Microsoft “de-linked” the versions (around SP6) so that kernel and app could be different versions.

I think the intent is to stay within the same service pack with app and kernel versions. You could apply a kernel fix that doesn’t affect the app version and vice versa. That should be OK. However, if an app fix comes with a kernel fix I like to install both.

By: Klaas Deforche

Klaas Deforche — Fri, 22 Oct 2010 13:57:26 +0000

Hi Arno,

Like you say: client en server kernel version MUST be the same, on every machine.
Thanks for the update!

By: Arno

Arno — Fri, 22 Oct 2010 12:47:03 +0000

We finally solve the problem by installing again the RU5 on the AOS and now we see all the records :-)
But after digging on the web and after harassing MBS I can confirm that:
1) the kernel version of the AOS and the kernel version of the client OF the workstation HAS TO BE the same.
2) after installing a RU, you have to check if in the install folders there is a MSI folder
3) SO YES, you should install the components32.msp (or 64 if you are on Windows 7) on the workstation running AX2009. Doing this put the client of the station on the same level kernel of the AOS. By doing this keep in mind to do a backup as suggested by Klaas here above. Thanks to all!

By: Arno

Arno — Fri, 22 Oct 2010 10:05:42 +0000

Hi Klaas,
Thx for your answer.
That’s what I also understood by googling on the web.
But I repeat, the problem I’ve is only on the AOS and Server.
If I connect on AX via a workstation and where the client is on Kernel 5.0.593.0 and on Application on 5.0.1500.2985, I don’t have this kind of problem. Nevertheless I’ll try to do what you suggest (and taking before a BU of the client folder :-)) but I’m affraid that I will have the same problem on my server.
In any case I keep you informed. Greetz, Arno