Client First Time Open KernelBase.dll Error

(0) Share

Report

Posted on by HAIRUL HAZRI

1,214

Hi,

My goal is to update AX2012 R2 CU7 to R2 CU9.

In a fresh test environment, I installed the R2 CU7, then the CU9 update, but I messed up here so I decided to uninstall everything and start over.

So, I reinstalled the R2 CU7 just like last time, but this time, after I finished installation, running the AX client for the first time crashed with following error on event viewer:

Faulting application name: Ax32.exe, version: 6.2.158.0, time stamp: 0x50a63c26
Faulting module name: KERNELBASE.dll, version: 6.3.9600.19724, time stamp: 0x5ec50c3e
Exception code: 0xe0434352
Fault offset: 0x000156e8
Faulting process id: 0x3b5c
Faulting application start time: 0x01d66a417bce7e5f
Faulting application path: C:\Program Files (x86)\Microsoft Dynamics AX\60\Client\Bin\Ax32.exe
Faulting module path: C:\Windows\SYSTEM32\KERNELBASE.dll
Report Id: cd993163-d634-11ea-80ea-005056978d2c
Faulting package full name: 
Faulting package-relative application ID:

I didn't even get to do initialization checklist, full compilation, etc..

I deleted .kti and .auc files, restarted SQL Server service, AOS service, but the error persists.

What else can I do to fix this? Thank you.

I have the same question (0)

All responses (21)

Answers (3)

Suggested answer

nmaenpaa 101,160 Moderator on at

Like (0)

Report

Ax32.exe version number 6.2.158.0 tells us that it's RTM version of AX2012 R2, not R2 CU7.

Perhaps you forgot to update all the binary components after reinstalling R2 CU7.

All components should be in the same version before proceeding with the checklist and other tasks.

How did you "reinstall R2 CU7"? The expected way is to use R2 installation media, and put CU7 package in the Updates folder of the installation media before installing. This is called "slipstream update" and it will install R2 CU7 for you right away.

You can find the build numbers here: cloudblogs.microsoft.com/.../

Was this reply helpful? Yes No
HAIRUL HAZRI 1,214 on at

Like (0)

Report

Hi Nikolaos,

thank you for clarification on the version number. After double checking, these are the working versions on Production & Staging environment:

Application Version = 6.2.158.0

Kernel Version = 6.2.1000.2473

I mistook the Kernel Version with Application Version, assuming it's between CU6 and CU7.

After clearing the misunderstandings, let me explain the situation again.

We currently have Staging & Production environments running on R2 RTM version. We need to update these environments to R2 CU9 because we need the AxBuild.exe tool.

So we are actually testing the CU9 installation in a new empty environment. Since we will install the update on the running staging & production environments later, we avoided performing "slipstream update" in this test environment. Hence, we decided to install the update separately here.

Anyway, I installed R2 RTM in test environment, restored Production db & db_model here, did the full compile, full CIL, full db sync, then I installed the CU9 update. I realized I messed up, so I decided to start over.

I removed all AX components using the AX installer, then I deleted the databases in SQL Server Management Studio.

Now that the environment is empty again, I reinstalled the R2 RTM with new databases and it was installed successfully. But the AX client crashed and I got the KernelBase.dll error.

Was this reply helpful? Yes No
Suggested answer

nmaenpaa 101,160 Moderator on at

Like (0)

Report

Perhaps you can start with a clean system, most likely it's the fastest and cheapest way forward.

Here's what you should do in that new system (in my opinion of course):

1) Install AX2012 R2 CU7 all components

2) Copy databases from prod to this new system

3) Install AX2012 R2 CU7 update for "Database" component (this will update the Microsoft code in the modelstore)

4) Run software update checklist

5) Deploy reports and Enterprise portal sites

Once that's done, here's how to upgrade your prod system:

1) Install AX2012 R2 CU7 update on all binary components (not database!)

2) Export-import modelstore from your new system (it contains Microsoft's code in CU7 version, and your customizations)

3) Run software update checklist - no need to compile anything or do any of the code upgrade steps anymore. Only data upgrade.

4) Deploy reports and Enterprise portal sites

Was this reply helpful? Yes No
HAIRUL HAZRI 1,214 on at

Like (0)

Report

Sorry Nikolaos, but I don't understand.

Why do I need to install R2 CU7? Furthermore, R2 CU7 is not available to download anymore.

On our hands right now we only have the Ax2012 R2 RTM version installer and R2 CU9 update installer.

So our testing plan is to install R2 RTM version like in other working environments, then install the R2 CU9 update.

If the update is working fine in this testing environment, then we will install the R2 CU9 update in other environments as well.

Is this wrong?

Was this reply helpful? Yes No
Verified answer

nmaenpaa 101,160 Moderator on at

Like (0)

Report

Wait a minute, you wrote in your first message that you "installed R2 CU7". And now you say that you don't have CU7 package and you want to install RTM. I'm confused.

My advice was based on the information that you shared. By the way, it's good to keep a copy of any update / installation package that is in use in your prod system, this way you could always install a new "prod copy" system even if the updates are not available for download anymore.

Anyway you can't use your R2 CU7 database in R2 RTM system. If you tried to, then that would explain your issue.

But, there were typos in my previous message - it should say CU9, not CU7.

Anyway, here's an updated list of steps for you:

1) Install AX2012 R2 CU9 all components in your new system

2) Copy databases from prod to this new system

3) Install AX2012 R2 CU9 update for "Database" component (this will update the Microsoft code in the modelstore)

4) Run software update checklist

5) Deploy reports and Enterprise portal sites

Once that's done, here's how to upgrade your prod system:

1) Install AX2012 R2 CU9 update on all binary components (not database!)

2) Export-import modelstore from your new system (it contains Microsoft's code in CU9 version, and your customizations)

3) Run software update checklist - no need to compile anything or do any of the code upgrade steps anymore. Only data upgrade.

4) Deploy reports and Enterprise portal sites

Was this reply helpful? Yes No
HAIRUL HAZRI 1,214 on at

Like (0)

Report

Hi Nikolaos,

I have some concerns.

1. The production environment is currently running SharePoint Foundation 2010 with Service Pack 2.

But in the testing environment I installed SharePoint Foundation 2013 with Service Pack 1.

With the difference SharePoint version, If I deploy the testing modelstore to production, will there be any problems?

2. Production environment has multiple AOSs with database(MSSQL & SSRS) and SharePoint installed on separate machine.

How to deploy the update to Production? Is there any difference in steps? Or any additional steps/precautions I should follow?

Thank you.

Was this reply helpful? Yes No
Suggested answer

nmaenpaa 101,160 Moderator on at

Like (0)

Report

The modelstore doesn't care about your Sharepoint version. So the steps would still be the same.

Eventually you should make sure that you have same Sharepoint version in all your systems.

Sharepoint 2010 is not supported anymore, and neither is AX2012 R2. I recommend to use only supported versions.

Was this reply helpful? Yes No
HAIRUL HAZRI 1,214 on at

Like (0)

Report

Hi Nikolaos,

I run full compilation, and got about 59 errors, mostly about missing enums & variables on standard forms & classes:

Is this expected? Since these are standard codes, how can I resolve these errors without over layering?

Was this reply helpful? Yes No
Verified answer

nmaenpaa 101,160 Moderator on at

Like (0)

Report

You have these errors because you have some overlayering customizations, which are now hiding part of the new MS code.

Biggest part of the update is to compare MS code in SYP against your customization layer and merge the changes onto your layer. You must compare all objects, not only the ones that cause compiler errors - there are many things that could be wrong even if the code compiles succesfully.

Was this reply helpful? Yes No
HAIRUL HAZRI 1,214 on at

Like (0)

Report

Hi Nikolaos,

I have run the Compare Layers & created the private project:

And I was able to see the difference between the two layers:

From here, I'm confused. Given above DMFEntityType enum as example, how do I merge these two layers? I'm expecting a button that might be automatically help to update the VAR layer? Am I expecting a miracle here?

Thank you.

Was this reply helpful? Yes No