Ver. 10.0.40 update error Object reference not set to an instance of an object.

(1) Share

Report

Posted on by Vast

1. I have run with administrator rights.

2. Also decompress the installation package to the root directory of drive C, or create a folder in the root directory of drive C, and then decompress the installation package to this folder.

Object reference not set to an instance of an object.
at Microsoft.Dynamics.AX.AXUpdateInstallerBase.IOManager.CreateDirectory(DirectoryInfo directoryInfo)
at Microsoft.Dynamics.AX.AXUpdateInstallerBase.IOManager.CreateDirectory(DirectoryInfo directoryInfo)
at Microsoft.Dynamics.AX.AXUpdateInstallerBase.IOManager.CreateDirectory(DirectoryInfo directoryInfo)
at Microsoft.Dynamics.AX.AXUpdateInstallerBase.IOManager.CreateDirectory(DirectoryInfo directoryInfo)
at Microsoft.Dynamics.AX.AXUpdateInstallerBase.AxUpdateBaseData.<>c__DisplayClass8_0.<ExportToFile>b__0()
at Microsoft.Dynamics.AX.AXUpdateInstallerBase.AXUpdateInstallerBase.ExecuteWithRetry(Action action, String callerName, Int32 retryInterval, Int32 maxRetryCount)
at Microsoft.Dynamics.AX.AXUpdateInstallerBase.AxUpdateBaseData.ExportToFile(String filePath)
at Microsoft.Dynamics.AX.AXUpdateInstallerBase.RunbookData.Save()
at Microsoft.Dynamics.AX.AXUpdateInstaller.Program.InstallUpdate(String[] args)
at Microsoft.Dynamics.AX.AXUpdateInstaller.Program.Main(String[] args)

I have the same question (0)

All responses (9)

Answers (1)

Sort by

André Arnaud de Cal... 306,773 Super User 2026 Season 2 on at

Like (0)

Report
Copy link

Link copied!

Moved the question to the Dynamics 365 Finance forum as this is not related to the previous Dynamics AX product.

I do assume you have a question about how to solve this error. Can you tell us if you used the correct file name and if it has the correct details? Did you open the command prompt with the option "Run as administrator"?

Was this reply helpful? Yes No
Anton Venter 21,110 Super User 2026 Season 2 on at

Like (0)

Report
Copy link

Link copied!

Create a new directory called c:\tmp or c:\update or whatever. Don't use c:\Windows\temp because of permissions and it's not recommended. Creating a new directory will make you the owner and you won't have permission issues in the folder you created.

By the way, did you unblock the file after you downloaded it? Assuming you downloaded it from the internet using a browser.

Was this reply helpful? Yes No
Anton Venter 21,110 Super User 2026 Season 2 on at

Like (0)

Report
Copy link

Link copied!

Create a new directory called c:\tmp or c:\update or whatever. Don't use c:\Windows\temp because of permissions and it's not recommended. Creating a new directory will make you the owner and you won't have permission issues in the folder you created.

By the way, did you unblock the file after you downloaded it? Assuming you downloaded it from the internet using a browser.

Was this reply helpful? Yes No
Vast 30 on at

Like (1)

Report
Copy link

Link copied!

Create a new directory called c:\tmp or c:\update or whatever. Don't use c:\Windows\temp because of permissions and it's not recommended. Creating a new directory will make you the owner and you won't have permission issues in the folder you created.

By the way, did you unblock the file after you downloaded it? Assuming you downloaded it from the internet using a browser.

All try, but still error.

Was this reply helpful? Yes No
Anthony Blake 3,198 Super User 2026 Season 2 on at

Like (0)

Report
Copy link

Link copied!

Hi, are you sure C is the best drive to run that from? On the dev instances K: is normally the drive with plenty of space, or one of the backup drives. Even if there is enough space, its running the OS.

Was this reply helpful? Yes No
Clement Ruffin 2 on at

Like (0)

Report
Copy link

Link copied!

Hi,

Were you able to find a solution ? I have the same error on updating a devbox to 10.0.40

Was this reply helpful? Yes No
RV-18071211-0 2 on at

Like (0)

Report
Copy link

Link copied!

I am having the same issue when trying to update my local development VM.

When checking the logfile the AxUpdateInstaller generated (AxUpdateInstaller_import_20240718120525905.log) I see that it attempted to run action 'ExportToFile' and failed.

[12:06:23.1897] Failed to run action 'ExportToFile' after 20 attempt(s)
[12:06:23.1897] Object reference not set to an instance of an object.
[12:06:23.1897] at Microsoft.Dynamics.AX.AXUpdateInstallerBase.IOManager.CreateDirectory(DirectoryInfo directoryInfo)
[12:06:23.1897] at Microsoft.Dynamics.AX.AXUpdateInstallerBase.IOManager.CreateDirectory(DirectoryInfo directoryInfo)
[12:06:23.1897] at Microsoft.Dynamics.AX.AXUpdateInstallerBase.IOManager.CreateDirectory(DirectoryInfo directoryInfo)
[12:06:23.1897] at Microsoft.Dynamics.AX.AXUpdateInstallerBase.IOManager.CreateDirectory(DirectoryInfo directoryInfo)
[12:06:23.1897] at Microsoft.Dynamics.AX.AXUpdateInstallerBase.AxUpdateBaseData.<>c__DisplayClass8_0.<ExportToFile>b__0()
[12:06:23.1897] at Microsoft.Dynamics.AX.AXUpdateInstallerBase.AXUpdateInstallerBase.ExecuteWithRetry(Action action, String callerName, Int32 retryInterval, Int32 maxRetryCount)

And finishes with:
[12:06:26.1910] An error occurred during execution.
[12:06:26.1910] Object reference not set to an instance of an object.
[12:06:26.1910] at Microsoft.Dynamics.AX.AXUpdateInstallerBase.IOManager.CreateDirectory(DirectoryInfo directoryInfo)
[12:06:26.1910] at Microsoft.Dynamics.AX.AXUpdateInstallerBase.IOManager.CreateDirectory(DirectoryInfo directoryInfo)
[12:06:26.1910] at Microsoft.Dynamics.AX.AXUpdateInstallerBase.IOManager.CreateDirectory(DirectoryInfo directoryInfo)
[12:06:26.1910] at Microsoft.Dynamics.AX.AXUpdateInstallerBase.IOManager.CreateDirectory(DirectoryInfo directoryInfo)
[12:06:26.1910] at Microsoft.Dynamics.AX.AXUpdateInstallerBase.AxUpdateBaseData.<>c__DisplayClass8_0.<ExportToFile>b__0()
[12:06:26.1910] at Microsoft.Dynamics.AX.AXUpdateInstallerBase.AXUpdateInstallerBase.ExecuteWithRetry(Action action, String callerName, Int32 retryInterval, Int32 maxRetryCount)
[12:06:26.1910] at Microsoft.Dynamics.AX.AXUpdateInstallerBase.AxUpdateBaseData.ExportToFile(String filePath)
[12:06:26.1910] at Microsoft.Dynamics.AX.AXUpdateInstallerBase.RunbookData.Save()
[12:06:26.1910] at Microsoft.Dynamics.AX.AXUpdateInstaller.Program.InstallUpdate(String[] args)
[12:06:26.1910] at Microsoft.Dynamics.AX.AXUpdateInstaller.Program.Main(String[] args)
[12:06:26.1910] Exiting with exit code [196609]

Worked perfectly fine on my colleagues VM's with the same setup and methodology.
I have not found a solution yet. I think I will install a clean VM and see if the problem arises again.

Was this reply helpful? Yes No
Verified answer

Vast 30 on at

Like (0)

Report
Copy link

Link copied!

After using the latest version of VHD, this issue is resolved.

Was this reply helpful? Yes No
RN-24071723-0 41 on at

Like (0)

Report
Copy link

Link copied!
I was able to successfully install .40 upgrade using the -UseExistingTopologyFile parameter in the runbook script.

Example:

.\AXUpdateInstaller.exe generate -runbookid="(run book ID)" -topologyfile="DefaultTopologyData.xml" -UseExistingTopologyFile -servicemodelfile="DefaultServiceModelData.xml" -runbookfile="(run book ID).xml"

Discussed in more detail here:

https://github.com/d365collaborative/d365fo.tools/discussions/843

Was this reply helpful? Yes No