Error when using IExplorerUtil.UpdateFileProperties from within job processor extension - only in 2026

[stp44QQS]

Hi,

have a issue with using IExplorerUtil.UpdateFileProperties from within an job processor extension in 2026. The exact same code works fine in all previous releases (2021-2025).

When the line for IExplorerUtil.UpdateFileProperties runs i first get an pop up error dialog from the job processor like below.

and the exception thrown looks like this from within visual studio. 

[zongbo_li]

@stp44QQS , would you please provide your test code and dataset?

A full call stacktrace of this exception is also appreciated.

[stp44QQS]

Hi, thanks for the reply. 

I have uploaded a test extension for the job processor which shows the issue.

[zongbo_li · Accepted solution]

@stp44QQS , thanks. We confirmed this is a regression. Will be fixed in upcoming release.

[gbadziura]

Hello
Is it already clear when the problem with IexpliorerUtils will be resolved? I am currently trying it in 2026.0.1 and it does not seem to have been fixed yet.

[StefanGutmann]

Hello,
the same problem occurs in one of our standalone applications in Vault 2026 and also in Vault 2025.3. Would be very nice if you could find a solution to the problem. Our customers cannot work with our software because of that.
Thanks in advance.

[jamesY3MCP]

Has there been any update on this? has anyone found a workaround?

[JanInventor]

This is blocking the Upgrade to Vault 2026.

[omar_semenzato]

Please, we have a customer that requires 2026 with our addin, this stop the activity !! we have the same problem!!

[JanInventor]

Strange enough, the code does work when using it for the Job Processor Publisher, but not as an stand alone application. 

[ivan_gani]

Any news about the fix?2 When it will be release?  This is block update addins into 2026.

[omar_semenzato]

Also in my case, I was porting a stand alone application from 2025 to 2026, ancd I re-installed just yesterday the SDK. 

[zongbo_li · Accepted solution]

This will be fix in 2026.1. Please wait until it is released. 

[jamesY3MCP]

Is there an ETA on 2026.1??
also, it seems like others have been able to solve this issue. There are 2026 plugins generally available that can update properties.
are they using work arounds?? if so, What?

[jamesY3MCP]

I have a work around for this but its ugly!!!

the only way i can see to update properties is to go back to the old way 

1. Check out the file
 - _conn.WebServiceManager.DocumentService.CheckoutFile
2. Get the monikers and values to update in the file (PropWriteRequests)
 - first use _conn.WebServiceManager.FilestoreService.GetContentSourcePropertyDefinitions
 - then _conn.WebServiceManager.PropertyService.GetPropertyDefinitionsByContentSourceIdAndMoniker to get the PropDef[]
3. Copy the file with the PropWriteRequests (this updates the property values in the file if mapped)
 - _conn.WebServiceManager.FilestoreService.CopyFile
4. Get the PropInstParamArray - for database property updates
5. Update the properties with the PropInstParamArray
 - _conn.WebServiceManager.DocumentService.UpdateFileProperties
6. check in the file
 - _conn.WebServiceManager.DocumentService.CheckinUploadedFile

or, just wait for Autodesk to fix the issue.

[omar_semenzato]

Any news about this issue ? When will be released 2026.1 ? 

[Markus.Koechl]

Please accept that we cannot publicly share any release date. I've already had the opportunity to test the upcoming fix successfully and will keep you posted here.

[omar_semenzato]

Thanks. I can understand. I hope as soon as possible.

[JanInventor]

I get still the same error after updating to Vault 2026.1

Dim oExplUtil As ACET.IExplorerUtil = Autodesk.Connectivity.Explorer.ExtensibilityTools.ExplorerLoader.LoadExplorerUtil(oConnection.Server, oConnection.Vault, oConnection.UserID, oConnection.Ticket)

System.NullReferenceException: 'Object reference not set to an instance of an object.'

oExplUtil was Nothing.

[gbadziura]

I can only confirm this for the project that uses the SDK DLLs in .NET Framework 4.8. The same code now works under .NET Core 8 without errors.

My sample projects are console applications that change properties.
In standalone mode under framework 4.8, there still seem to be problems here, or something else needs to be taken into account.
A Framework 4.8 Vault Extension that uses Iexplorerutils works. Here, ExplorerLoader.GetExplorerUtil(_application) is used instead of ExplorerLoader.LoadExplorerUtil(Va...).