When a DC refresh occurs, we upload this to the server, the XML gets parsed and it will be inserted into the SQL database after which the local file will be flushed. It contains all the application usage information amongst some additional data in XML format. This XML file is a physical file on the App-V client. HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\Client\Reporting\LastCacheFile HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\Reporting\LastCacheFile This key holds the information on the latest reporting cache XML file. If the reporting key mentioned above is set to 1, you will have the following registry key as well. HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\Client\DC Servers\Reporting HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\DC Servers\Reporting In addition to this, when a 4.5+ client reports against a SoftGrid 4.1 VAS, you will notice that the below registry value is set to 0 and when it is reporting against a 4.5 VAS, it is set to 1. ĭC server does not want to receive v4.5+ reporting In your App-V client log (sftlog.txt), you will find an entry similar to the one below if you have the issue. Increasing disk space usage on the App-V clients, because the XML files will never be cleared.Missing or incomplete data in the Management server reports.Warnings in the logs (Application Event log and App-V Client log).In general, the symptoms of this issue would be: A remedy would then be to turn off reporting data collection. If your App-V server is configured to request reporting data from your clients, but if you do not use App-V reports, you will likely not even know if you have this issue. Not all clients have to have this issue, so don’t be surprised if some clients do work, but if some clients have the issue your reports will be incomplete and not reliable. In this reporting cache we store the application usage data so if you have this issue you will not be able to run proper reports on App-V’s application usage. The issue that occurs here is that the App-V client fails to upload its reporting cache back to the server. NOTE Before applying the actions in this article, make sure to back up your SQL database at any time before making changes! The problem Some time ago I was working on a reporting issue for App-V and because this issue keeps popping up every once in a while I thought I’d write a blog post about it so you would be aware of it as well.
Rssowl duplicates code#
Comments Off on The App-V Client does not upload reporting data, resulting with Event 3144 and error code 0A-200001F4įiled under: 200001F4, 3144, App-V, Reporting.
0 kommentar(er)
