web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Kernel Version is 5.0....
Microsoft Dynamics AX (Archived)

Kernel Version is 5.0.593 in web server after upgrading to SP1

(0) ShareShare
ReportReport
Posted on by Community Member
Hi Gents, When I upgraded the AX 2009 to SP1 on all AX servers, I can see both the AX Kernel and application version in the AOS server is 5.0.1000, but the Kernel version in the Web server is 5.0.593 (RTM) and Application version in the Web server is 5.0.1000. It looks very weird. Has anyone got the same error before? Please leave some suggestions here. Thanks, Pin

*This post is locked for comments

I have the same question (0)
  • Denis Patrakov Profile Picture
    Denis Patrakov on at
    Your Web server most likely uses a locally installed component of AX - .NET Business Connector - to communicate with an AOS. Have you upgraded it, too?
  • Community Member Profile Picture
    Community Member on at

    Hi Gl00mie,

    Alll the components have been upgraded to SP1.

  • Denis Patrakov Profile Picture
    Denis Patrakov on at
    Ok, then how can you tell that «the Kernel version in the Web server is 5.0.593»? What do you do to see this build number?
  • Community Member Profile Picture
    Community Member on at

    In AX --> Help --> About Dynamics AX --> Kernel Version

  • Denis Patrakov Profile Picture
    Denis Patrakov on at
    Do you have a client installed on you web server? If so then you can go to the client location, find its executable (ax32.exe), open its properties and see its executable file version. If it is 5.0.593 then the client installed on you web server (or wherever you run it from) obviously has not been upgraded.
  • Community Member Profile Picture
    Community Member on at

    What I want to know is why the error is coming even the SP1 application installation shows successfully and how to fix that.

     I have tried many times to reinstall and upgrade the client, but no success.

  • Denis Patrakov Profile Picture
    Denis Patrakov on at
    Upgrade to a new SP consists of 3 parts:
    • Application upgrade - porting any customizations to a new SP
    • Database upgrade - running upgrade checklist including any required data upgrade scripts at the first time you start with an upgraded application
    • Kernel upgrade - in fact the easiest part of the three
    Application upgrade and database upgrade must be done only once per application per database but in case of the kernel upgrade you have to run it everywhere where you have previously installed any part of AX kernel - either object server, or client, or business connector.
    Now what's the problem with upgrading a client? If you can identify where you run a client from then just go and upgrade it on that host. Turn on verbose MsiExec logging during upgrade. If the client is not upgraded immediately then it's probably locked by another user and you'll have to reboot the host. If MsiExec fails for some reason then read the log and troubleshoot the cause of failure (or write the error messages here if you can't figure out how to fix it). If you haven't installed a client but instead just have copied it's executables (in that case MsiExec would complain that it couldn't find an installed product to update) then copy the new ones from a host where the client has already been upgraded.
    Anyway it's a pretty straightforward operation. If you have any further problems upgrading a client then please specify any details (a part of a verbose log with error messages, or eventlog error messages and error codes, or anything like that). Without this it's quite hard to guess why in your specific situation with one of your servers an AX client upgrade fails.
  • Community Member Profile Picture
    Community Member on at
    Thanks, gl00mie. I have installed the whole AX application on many clients but I only got the issue this time. It is very weird as the client installed in other workstations work fine. Only the web server get the problem. I have submitted a support to Microsoft and will have a shared session with them to validate the issue. Appreciate your help in this post. Cheers, Pin
  • Community Member Profile Picture
    Community Member on at
    Got the solution. It is due to the hot fix installation defect.
  • Denis Patrakov Profile Picture
    Denis Patrakov on at
    What's the defect? Is it specific to a particular Windows version?

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans