App-V publishing fails due to UserConfig files

[German]Here's an article about App-V and a problem that publishing App-V applications fails because a UserConfig file is used. Windows returns the error code 0x0FD0A725-0000000057 in the log file when the App-V packages are delivered.


What is App-V?

The abbreviation App-V stands for Microsoft Application Virtualization and is Microsoft's solution for application virtualization. The applications are streamed from a server to a client in a virtualized way and then executed in a virtual environment in a sandbox. The Wikipedia has some explanations on this topic.

The advantage is that you can start on an almost 'software-free' computer and access all App-V applications provided by the server without having to install anything. Only an App-V client is required, which has to be installed on the computer. In addition, a fast network connection should be available to load the application into the sandbox. However, the user can already use the application shortly after the start of the stream, as additional program parts are loaded in the background.

The virtualized applications can be Win32 applications. The whole thing is available in the Enterprise versions from Windows 10 version 1607. Microsoft has published some documentation about App-V.  The applications (App-V package) are made available via MSI files (MSI = Microsoft Installer format), which are then loaded by the App-V client. This Microsoft document contains some information about deploying App-V packages, which includes configuration files, reporting files, and so on, in addition to the MSI file.

App-V publishing fails due to UserConfig file

As it looks now, there are occasional problems with App-V deployment failing because of the UserConfig files used. Microsoft has probably received some reports from customers in late 2019 that application publishing fails when using a user configuration file applied to these packages. The following tweet refers to this issue.


If the publication fails when using a UserConfig file in the App-V management console, the following entry is found in the detailed log files:

5756 [7]14D4.4320::12/10/19-08:28:34.9973489 [Microsoft.Windows.AppMan.AppV] LOGLEVEL=1, MESSAGE=Catalog: Failed to set the last modification time on policy file 'C:\Users\sgern\AppData\Roaming\Microsoft\AppV\Client\Catalog\Packages\{1D45F06B-874D-4A85-86EF-2330B430E47D}\{DB5DE6F6-15E8-4932-A7CF-2DA12EA5B068}\DynamicConfiguration.xml. Error code: 0x0FD0A725-00000057, FUNCTION=AppV::Client::Catalog::DocumentStoreImpl::SavePolicyDocumentToFile, LINENO=1078, UTCReplace_AppSessionGuid=true

Windows returns the error code 0x0FD0A725-0000000057, which means "Wrong parameters". After some research, Microsoft specialists were able to outline the problem, the root cause and the solution for this error.

In short summary: It is related to timestamps and a change in SQL Server 2016 and higher versions, where a time field is filled with values between 1-9 instead of zeros. Sebastian Gernert, Escalation Engineer for App-V, has published a separate article about this in the Techcommunity, which deals with the details. There are workarounds that Gernert describes. Maybe it helps if someone in the enterprise environment runs into this bug.

Cookies helps to fund this blog: Cookie settings

This entry was posted in Software, Virtualization, Windows and tagged , , , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *