Font size: + –
  Print
34 minutes reading time (6891 words)

All App-V Events And Messages

24685 Hits
AppVMS

It's been a while since I've published anything here. I often don't have the time to do some really cool things in the basement. Only some time ago I played with the App-V Eventlog and found out which App-V events there are at all. That's interesting because there are news that nobody actually knows about. The messages are no real help for errors. I recommend rather the website http://app-v.de/html/app-v_5_error_codes.html . Still, maybe you can do something with it. By the way, there are many more App_V log providers. Please ask if you need one


Microsoft-AppV-Client

 EventId  Level  Value  Description
3 win:Error 2 A required component (%1) cannot be loaded. Please repair your installation. {error: %2}
4 win:Error 2 The Client service could not get the list of currently logged-on users. If users experience any issues running virtual applications, please logoff and logon again, or restart the service. {error: %1}
5 win:Error 2 The Client could not register a logged-on user. The user will not be able to access any App-V services, including running virtual applications. Please have the user logoff and logon again. {error: %1-%2}
6 win:Error 2 The Client could not unregister a user that logged off. If other users experience any issues logging on, please restart the Client service. {error: %1-%2}
7 win:Error 2 The Client could not determine the identity of a caller on a public request, and the request was denied. {error: %1}
8 win:Error 2 The Client could not register a caller, or verify the registration status of a caller, on a public request, and the request was denied. {error: %1-%2}
9 win:Error 2 A public request to the Client was initiated by a caller which granted the Client the authority for %1, whereas the Client requires at a minimum RPC_C_IMP_LEVEL_IMPERSONATE in order to satisfy a request on the caller's behalf. The calling application will need to modify its security settings for outbound calls in order to successfully access the Client API.
10 win:Error 2 The access to the client was denied. The caller didn't have required permission for this operation.
11 win:Warning 3 The Client failed to register for power notifications. {error: %1-%2}.
12 win:Warning 3 The Client failed to unregister for power notifications. {error: %1-%2}.
16 win:Error 2 The Client service cannot be started due to component %1 failing during the global maintenance phase. {error: %2-%3}.
17 win:Error 2 The maintenance phase has failed for user %1 in component %2. {error: %3-%4}.
1001 win:Error 2 Active processing could not be shut down, this may lead to delays or hangs for Client shutdown. {error: %1-%2}
1008 win:Error 2 Package %1 version %2 failed configuration in folder '%3' with error %4-%5.
1010 win:Error 2 Virtual application connection group %1 version %2 failed configuration with error %3-%4.
1016 win:Error 2 Failed to unpublish package %1 version %2 because the package is published as part of one or more connection groups. Unpublish all connection groups that reference this package and try again.
1017 win:Error 2 Failed to remove package %1 version %2 because the package is configured as part of one or more connection groups. Remove all connection groups that reference this package and try again.
1018 win:Error 2 A package could not be unpublished for the user because it is currently in use by the user. Shut down all applications in the package, and try again. Package %1 Version %2 Activity #%3
1019 win:Error 2 A package could not be globally unpublished because it is currently in use. Make sure all users have shut down all applications in the package, and try again. Package %1 Version %2 Activity #%3
1020 win:Error 2 A package could not be removed because it is currently in use. Make sure all users have shut down all applications in the package, and try again. Package %1 Version %2 Activity #%3
1021 win:Error 2 An app connection group could not be unpublished for the user because it is currently in use by the user. Shut down all applications in the group, and try again. Connection Group %1 Version %2 Activity #%3
1022 win:Error 2 An app connection group could not be globally unpublished because it is currently in use. Make sure all users have shut down all applications in the group, and try again. Connection Group %1 Version %2 Activity #%3
1023 win:Error 2 An app connection group could not be removed because it is currently in use. Make sure all users have shut down all applications in the group, and try again. Connection Group %1 Version %2 Activity #%3
1024 win:Error 2 The package %1 version %2 could not be reconfigured because it is not configured on the system. Ensure the package ID and version ID are correct and try again.
1025 win:Error 2 The package %1 version %2 could not be configured because it can only be used with 64-bit versions of Windows.
1026 win:Error 2 The package %1 version %2 could not be configured because it is not compatible with this version of Windows.
1027 win:Error 2 The package %1 version %2 could not be configured becaused the Deployment Configuration file '%3' could not be found. Ensure the path is correct and try again.
1028 win:Error 2 The package %1 version %2 could not be configured because the Deployment Configuration file '%3' is not valid. Verify that the document is valid and try again.
1029 win:Error 2 The package %1 version %2 could not be configured because the Deployment Configuration file does not match the the specified package. Ensure the GUIDs in the Deployment Configuration file match those of the package and try again.
1030 win:Error 2 The package %1 version %2 could not be configured because the user account does not have administrative privileges.
1031 win:Error 2 The package %1 version %2 could not be published globally because the user account does not have administrative privileges.
1032 win:Error 2 The package %1 version %2 could not be published because the package has not been configured on the system. Configure the package and try again.
1033 win:Error 2 The package %1 version %2 could not be published becaused the User Configuration file '%3' could not be found. Ensure the path is correct and try again.
1034 win:Error 2 The package %1 version %2 could not be published because the User Configuration file '%3' is not valid. Verify that the document is valid and try again.
1035 win:Error 2 The package %1 version %2 could not be published because the User Configuration file does not match the the specified package. Ensure the GUIDs in the User Configuration file match those of the package and try again.
1036 win:Error 2 The package %1 version %2 could not be published globally because a User Configuration file was specified. Either publish the package for the user with the User Configuration file specified or do not supply a User Configuration.
1037 win:Error 2 The package %1 version %2 could not be unpublished globally because the user account does not have administrative privileges.
1038 win:Error 2 The package %1 version %2 could not be unpublished because it is not published to the target of the unpublish operation.
1039 win:Error 2 The package %1 version %2 could not be removed because the package is not configured on the system.
1040 win:Error 2 The package %1 version %2 could not be removed because the user account does not have administrative privileges.
1041 win:Error 2 The package %1 version %2 cannot be repaired because the package is not configured on the system.
1042 win:Error 2 The package %1 version %2 was repaired successfully, but the package is published in one or more Virtual Application Connection Groups. Settings are associated with the group, so you may need to clear settings for the Virtual Application Connection Groups associated with this package.
1043 win:Error 2 The app connection group %1 version %2 could not be added because the app connection group file '%3' could not be found. Ensure the path is correct and try again.
1044 win:Error 2 The app connection group %1 version %2 could not be added because the package %3 version %4 is not configured on the system. Configure the package and try again.
1045 win:Error 2 The app connection group %1 version %2 could not be added because the app connection group file '%3' is not valid. Verify that the document is valid and try again.
1046 win:Error 2 The app connection group %1 version %2 could not be added because the user account does not have administrative privileges.
1047 win:Error 2 The app connection group %1 version %2 could not be enabled because the app connection group has not been added on the system. Add the app connection group and try again.
1048 win:Error 2 The app connection group %1 version %2 could not be enabled because the package %3 version %4 is not published to the target of the operation. Publish the package and try again.
1049 win:Error 2 The app connection group %1 version %2 could not be enabled globally because the user account does not have administrative privileges.
1050 win:Error 2 The app connection group %1 version %2 could not be disabled because it is not enabled for the target of the disable operation.
1051 win:Error 2 The app connection group %1 version %2 could not be disabled globally because the user account does not have administrative privileges.
1052 win:Error 2 The app connection group %1 version %2 could not be removed because the package it has not been added on the system.
1053 win:Error 2 The app connection group %1 version %2 could not be removed because the user account does not have administrative privileges.
1054 win:Error 2 The app connection group %1 version %2 cannot be repaired because the app connection group has not been added on the system.
1057 win:Informational 4 The package %1 version %2 was detected to have a pending global Unpublish task. The App-V Client cannot start the virtual environment. Please close all running applications in the package or stop the package.
1058 win:Informational 4 The app connection group %1 version %2 was detected to have a pending global Unpublish task. The App-V Client cannot start the virtual environment. Please close all running applications in the app connection group or stop the app connection group.
1059 win:Informational 4 The package %1 version %2 was detected to have a pending user Unpublish task. The App-V Client cannot start the virtual environment. Please close all running applications in the package or stop the package.
1060 win:Informational 4 The app connection group %1 version %2 was detected to have a pending user Unpublish task. The App-V Client cannot start the virtual environment. Please close all running applications in the app connection group or stop the app connection group.
1063 win:Error 2 A package could not be published for the user because it is currently in use by the user. Shut down all applications in the package, and try again. Package %1 Version %2 Activity #%3
1064 win:Error 2 A package could not be globally published because it is currently in use. Make sure all users have shut down all applications in the package, and try again. Package %1 Version %2 Activity #%3
1065 win:Error 2 An app connection group could not be published for the user because it is currently in use by the user. Shut down all applications in the group, and try again. Connection Group %1 Version %2 Activity #%3
1066 win:Error 2 An app connection group could not be globally published because it is currently in use. Make sure all users have shut down all applications in the group, and try again. Connection Group %1 Version %2 Activity #%3
1071 win:Informational 4 The package %1 version %2 was detected to have an upgrading task. The App-V Client cannot start the virtual environment. Please try again in several minutes once the update is complete.
1072 win:Informational 4 The application connection group %1 version %2 was detected to have an upgrading task. The App-V Client cannot start the virtual environment. Please try again in several minutes once the update is complete.
1073 win:Error 2 The pending publish operation for package %1 version %2 was not performed because network connectivity is not available.
1074 win:Error 2 The package %1 version %2 was detected to have a pending publish or unpublish operation. The App-V Client cannot remove the package. Pending user operations are processed at logon, and pending global operations are processed at startup. Please try again when any related pending operations are complete. Activity #%3
1075 win:Error 2 The app connection group %1 version %2 was detected to have a pending task. The App-V Client cannot remove the app connection group. Pending user operations are processed at logon, and pending global operations are processed at startup. Please try again when any related pending operations are complete. Activity #%3
1076 win:Error 2 The UserSID value %1 is not valid. Please ensure it is a valid SID and that the associated user is logged in when you run the cmdlet. {error: %2-%3}
1077 win:Error 2 While publishing package %1 version %2 an error occurred when obtaining the integration settings for each of the connection groups that the package belongs to {error %3 - %4}. The package has not been published.
1078 win:Warning 3 Package %1 version %2 was user published while belonging to globally published Connection Group %3 version %4. Therefore, although the package will be published to the user, it will not be assocated with the Connection Group until it is also published globally.
1079 win:Error 2 The App-V driver mappings were not successfully updated when Package %1 version %2 was added (error: %3-%4). Connection Groups containing this package may not work correctly.
1080 win:Error 2 The App-V driver mappings were not successfully updated when Package %1 version %2 was removed (error: %3-%4). Connection Groups previously containing this package may not work correctly.
1082 win:Error 2 The App-V driver mappings were not successfully updated when Package %1 version %2 was published (error: %3-%4). Connection Groups previously containing this package may not work correctly.
1083 win:Error 2 The App-V driver mappings were not successfully updated when Package %1 version %2 was unpublished (error: %3-%4). Connection Groups previously containing this package may not work correctly.
2001 win:Error 2 Failed to move Catalog folder ‘%1’ to new required location ‘%2’. {error: %3}
2002 win:Warning 3 Catalog folder ‘%1’ was migrated to new required location ‘%2’, but the old location could not be removed. The Catalog will be used from the new location. {error: %3}
2003 win:Warning 3 Catalog folder ‘%1’ was migrated to new required location ‘%2’, but the new location previously existed.
2004 win:Error 2 Failed due to could not get catalog folder. {error: %1-%2}
2005 win:Error 2 The package %1 version %2 was detected to be in an irreconcilable state and has been removed. Please manually remove any remaining data (by default under %ProgramData%\App-V\) when re-adding the package.
2006 win:Error 2 The app connection group %1 version %2 was detected to be in an irreconcilable state and has been removed. Please manually remove any remaining data (by default under %ProgramData%\App-V\) when re-adding the app connection group.
3001 win:Critical 1 The Client service has encountered a critical security issue and must shut down immediately. {error %1-%2}
3002 win:Critical 1 The Client service has encountered a critical security issue and must shut down immediately. {error %1-%2}
4001 win:Error 2 The App-V client failed to create a process for %1 script event %2 with command line: '%3'. Windows error: %4. The path must be a Windows application (.exe file).
4002 win:Error 2 The App-V client waited for the designated Timeout of %1 seconds for %2 script event %3 with executable: '%4' to complete. Because the Timeout was reached, the script process was terminated. Since RollbackOnError is set to true in script definition, the current AppV Client operation was rolled back due to script timeout.
4006 win:Error 2 Parsing of Embedded Script XML in package Manifest failed. Package: %1; event name: %2; XML parsing error: %3-%4. Please ensure that the XML script section in the package manifest for event %2 is well formed.
4007 win:Error 2 An error was encountered while reading the setting to enable scripts. Error code: %1-%2.
4008 win:Warning 3 The App-V client waited for the designated Timeout of %1 seconds for %2 script event %3 with executable: '%4' to complete. Because the Timeout was reached, the script process was terminated. Since RollbackOnError is set to false in script definition, the timeout is ignored and current AppV Client operation will continue.
4009 win:Error 2 %1 script for event %2 with command line: '%3' exited with failure error code: %4. Because Rollback is set to true in the script definition, the current AppV Client operation was rolled back.
4010 win:Warning 3 %1 script for event %2 with command line: '%3' exited with failure error code: %4. Because Rollback is set to false in the script definition, the script process failure is ignored and the current AppV Client operation will continue.
4011 win:Warning 3 Appv Client Scripting Component failed to acquire a proper token before querying Appv Client settings for Scripting, the query of the settings for Scripting may fail.
7001 win:Error 2 The client service has encountered an error monitoring settings. Changes to some settings will not take effect until the service is restarted. {error: %1}
8001 win:Error 2 Failed to load provided xml. DOM Error: %1 Reason: %2 Line: %3 Column: %4 Offset: %5
8002 win:Error 2 Failed to validate provided xml. DOM Error: %1 Reason: %2
8003 win:Error 2 Invalid connection group document format. There are no packages specified in the connection group document for connection group %1, version %2.
8004 win:Error 2 Invalid connection group XML document format. There needs to be at least one mandatory package in the connection group XML document for connection group %1, version %2.
8005 win:Error 2 Failed to update the connection groups for user %1. Some virtualized applications may fail to execute properly. Error: %2
8006 win:Error 2 All of the package groups associated with the publishing of package %1, version %2 were not successfully refreshed. Error: %3
8007 win:Error 2 All of the package groups associated with the unpublishing of package %1, version %2 were not successfully refreshed. Error: %3
8008 win:Error 2 All of the package groups associated with the adding of package %1, version %2 were not successfully refreshed. Error: %3
8009 win:Error 2 Failed to get the package groups associated with the removal of package %1, version %2. Error: %3.
8010 win:Error 2 All of the package groups associated with the removal of package %1, version %2 were not successfully refreshed. Error: %3
8011 win:Error 2 Package group %1, version %2 was not successfully refreshed. Error: %3
8012 win:Error 2 Mandatory package %3, version %4 specified in connection group %1, version %2 has not been added to the computer or has not been entitled to the user.
8013 win:Warning 3 Error %3-%4 occurred while attempting to delete the user publishing data associated with group %1, version %2 for user %5. The publishing data may need to be removed manually.
8014 win:Warning 3 Error %3-%4 occurred while attempting to unpublish group %1, version %2 for user %5. This error should correct itself on the next publishing refresh for the user.
8015 win:Error 2 Failed to get the package groups associated with the unpublish of package %1, version %2. Error: %3.
8016 win:Warning 3 Registry path %1 was malformed in dynamic configuration file for package %2, version %3.
9001 win:Error 2 Error encountered while executing command %1. Error: %2
9002 win:Warning 3 Warning raised while executing command %1. Warning: %2
9003 win:Error 2 Error encountered when accessing a property value of an App-V Publishing Server. This Publishing Server has been skipped.
9004 win:Error 2 Error encountered when accessing a property value of an App-V Client Connection Group. This Connection Group has been skipped.
9005 win:Error 2 Error encountered when accessing a property value of an App-V Client Package. This Package has been skipped.
9006 win:Error 2 Error encountered when accessing a property value of an App-V Client Application. This Application has been skipped.
9007 win:Error 2 Error encountered when attempting to access the packages of an App-V Client Connection Group. This Connection Group will display no Packages.
9008 win:Error 2 Error encountered when attempting to access the applications of an App-V Client Package. This Package will display no Applications.
9009 win:Error 2 Error encountered during Powershell process startup or exit while executing command '%1'.
9010 win:Error 2 Error encountered while executing command '%1'. Please refer to the AppV Client log for error details.
9012 win:Error 2 Error encountered when accessing a property value of an App-V Client Configuration.
10001 win:Error 2 Process %1 failed to start due to %4 subsystem failure. Package ID %2. Version ID %3. Error: %5-%6
10002 win:Error 2 Unable to inject into a non-virtual process with PID %1. This process will not be able to use virtual components.
11002 win:Error 2 Could not takeover extension points ownership from legacy package %1. Error: %2
11003 win:Error 2 Could not give extension points ownership back to legacy package %1. Error: %2
11004 win:Warning 3 MigrationMode is enabled but legacy App-V Client is not installed on the machine. Managing Authority policy will not be applied for the package %1.
11007 win:Error 2 Failed reading Managing Authority policy for package %1. Error: %2-%3
11008 win:Error 2 Failed reading old Managing Authority policy for package %1. Error: %2-%3
11009 win:Error 2 Error '%2' waitig for command: %1
11010 win:Warning 3 Timed out waitig for command: %1
11011 win:Warning 3 Error '%2' getting exit code for command: %1
12001 win:Error 2 A conflict was detected in the user configuration setting for enabling the virtual registry in virtual application connection group %1 version %2. The virtual application could not be started.
13007 win:Warning 3 Security information for VFS directory %1 has changed from its previous value.
13008 win:Error 2 Error: %1-%2. Process %3 already belongs to a job. It cannot be added to the virtual environment. Package %4, Version %5.
13009 win:Error 2 Error: %3-%4. Package %1, Version %2 has not been updated to the latest version for this client. The package can be updated by either running a repair operation or by unpublishing and removing it and then adding and publishing it again.
13010 win:Error 2 Error: %3-%4. Package Group %1, Version %2 has not been updated to the latest version for this client. The package group can be updated by either running a repair operation or by disabling and removing it and then adding and enabling it again.
13011 win:Error 2 Package %1, Version %2 contained errors in the user state data and has been repaired as part of an upgrade operation. The user-specific application settings have been reset to their original state when the package was originally added to the system.
13012 win:Error 2 Package Group %1, Version %2 contained errors in the user state data and has been repaired as part of an upgrade operation. The user-specific application settings have been reset to their original state when the package group was originally added to the system.
14003 win:Error 2 App-V client has detected that you are trying to launch a new application on a mobile network connection. The launch has been blocked due to the mobile network approaching/exceeding the data limit or roaming.
14004 win:Warning 3 Unexepected error. The App-V client was unable to register for the network cost callback and will be unable to suspend background loads if the network cost increases.
14005 win:Warning 3 Unexpected error %1-%2. The App-V client was unable to start the background load queue. Packages will not be loaded in the background automatically.
14006 win:Warning 3 Unexpected error. The App-V client was unable to start the background load queue properly. Package information is not available to determine if background loads are local or remote.
14009 win:Warning 3 App-V client has detected an HTTP error 502 while attempting to stream a package. This can be the result of a proxy server not being configured to allow a high enough rate of requests from the client to the package server.
14010 win:Error 2 The package %1 version %2 could not be configured because the path %3 could not be reached. Ensure the path is correct and try again.
14011 win:Error 2 The package %1 version %2 could not be configured because the package is corrupt. Ensure that the package file is a valid App-V package and try again.
14012 win:Error 2 The package %1 version %2 could not be configured because the package store location is not on a valid NTFS file system. Ensure that the package store location is a valid NTFS file system and try again.
14013 win:Error 2 The package %1 version %2 could not be configured due to low disk space. Ensure that there is enough disk space and try again.
14014 win:Error 2 The package %1 version %2 could not be configured because the specified URL is not valid. Ensure that the URL is valid and try again.
14015 win:Error 2 The package %1 version %2 could not be configured because the target location %3 already exists. Ensure that this location is removed and try again.
14016 win:Error 2 The package %1 version %2 could not be mounted because the network connection has been lost or is unavailable. Check your network connection and try again.
14017 win:Error 2 The package %1 version %2 could not be mounted. The operation failed with HRESULT %3, probably due to low disk space. Ensure that there is enough disk space and try again.
14018 win:Error 2 The package %1 version %2 could not be mounted due to the network connection timing out. Check your network connection and try again.
14019 win:Warning 3 The package %1 version %2 full mount was suspended because the user who initiated the operation has logged off.
14020 win:Error 2 The package %1 version %2 failed to be configured because the package is not valid for the current CPU architecture.
14021 win:Error 2 Content required by an application could not be retrieved from the network. A request for file %2 from package version %1 failed with error %3. Check your network connection and try again.
14022 win:Critical 1 The App-V Client failed to initialize properly. The Streaming Mini-Filter failed to initialize with error code %1. Please verify that the App-V Client is installed properly.
14029 win:Error 2 App-V package root folder ownership has been changed from LocalSystem to %1.
15001 win:Error 2 The AppVStreamingUX application experienced an AppV error while attempting to connect to the AppVClient service. The AppVStreamingUX process will now exit. AppV Error: %1-%2
15002 win:Error 2 The AppVStreamingUX application experienced a COM error while attempting to connect to the AppVClient service. The AppVStreamingUX process will now exit. HResult: %1
15003 win:Error 2 The AppVStreamingUX application experienced an AppV error while attempting to stop a package or connection group. Running Virtual Environment ID: %1, Version: %2, AppV Error: %3 - %4
16001 win:Error 2 A conflict was detected in the configuration settings for Virtual Object exclusions in virtual application connection group %1 version %2. The virtual application could not be started. Verify that the settings are correct and try again.
16002 win:Error 2 A conflict was detected in the 'enabled' setting for Virtual Object subsystem in virtual application connection group %1 version %2. The virtual application could not be started. Verify that the settings are correct and try again.
16003 win:Error 2 The connection group %1 version %2 could not be published because the virtual objects settings of the individual packages conflict. Verify that the virtual objects settings are the same for all member packages and try again. Error code: %3 - %4
16004 win:Error 2 Failed to publish package %1 version %2 because its virtual objects settings do not match those of other packages in connection group %3 version %4. Verify that the virtual objects settings are the same for all member packages and try again. Error code: %5 - %6
17001 win:Warning 3 Failed to save last report data cache file path %1 to the registry due to error %2. If there is a Client failure before the next save attempt, and the report data must be loaded from the cache, some records may be missing.
17002 win:Error 2 Reporting data cache could not be loaded from %1 due to error %2-%3. A new report data cache file will be generated and saved separately. Any report data from the previous cache file will be lost.
17003 win:Error 2 Reporting data manager queue worker thread is exiting on unexpected wait condition %1, error code %2. No further report records will be processed.
17004 win:Warning 3 Reporting data cache could not be saved to disk after adding new records (rc = %1-%2); those records may be lost if the Client shuts down before the next attempt to save or transmit the cache.
17006 win:Error 2 Reporting data cache could not be sent to Reporting Server. (rc = %1-%2).
17007 win:Error 2 Failed to add application launch data to the reporting queue. This application launch will not be reported to the reporting server. (rc = %1-%2).
17008 win:Error 2 Failed to add application shutdown data to the reporting queue. This application shutdown will not be reported to the reporting server. (rc = %1-%2).
17009 win:Error 2 Failed to add virtual environment created data for the launching application. The application launch will not be reported to the reporting server. (rc = %1-%2).
17010 win:Error 2 Failed to add virtual environment terminated data for the terminating application. The application shutdown will not be reported to the reporting server. (rc = %1-%2).
17011 win:Warning 3 Failed to save updated cached file after upload due to error %1-%2; duplicate records may be sent to the server if the cache must be reloaded before the next save attempt.
17012 win:Error 2 Failed to add virtual process launch failure information for the terminating process. The application launch failure will not be reported to the reporting server. (rc = %1-%2).
18001 win:Error 2 A virtual application could not be launched from package '%1' because the App-V Client Service is not running. Start the App-V Client Service and try again.
18002 win:Error 2 The virtual application '%1' could not be launched because the user is not entitled to the package to which it belongs. Either publish the package to the user or globally and try again.
18003 win:Error 2 The virtual application '%1' could not be launched because the App-V Client could not determine which environment to use. Provide a priority to the app connection group for the package and try again.
18004 win:Error 2 The virtual application '%1' could not be launched because the service '%2' could not be started.
18006 win:Error 2 The virtual environment for connection group %1 version %2 could not be created because the package %3 version %4 is not published. Publish the package and try again.
19011 win:Error 2 Settings sync failed. Error code: %1 - %2
19101 win:Error 2 Getting client information failed. Error code: %1 - %2
19102 win:Error 2 Getting server publishing data failed. URL: %1 Error code: %2 - %3
19103 win:Error 2 Getting client published data failed. Error code: %1 - %2
19104 win:Error 2 Part or all packages publish failed. published: %1 failed: %2 Please check the error events of 'Configure/Publish Package' before this message for the details of the failure.
19105 win:Error 2 Part or all packages un-publish failed. un-published: %1 failed: %2 Please check the error events of 'Unpublish Package' before this message for the details of the failure.
19106 win:Error 2 Part or all groups publish failed. published: %1 failed: %2 Please check the error events of 'Configure/Publish Virtual Application Connection Group' before this message for the details of the failure.
19107 win:Error 2 Part or all groups un-publish failed. un-published: %1 failed: %2 Please check the error events of 'Unpublish Virtual Application Connection Group' before this message for the details of the failure.
19108 win:Error 2 Failed to publish group due to the failure of the package. Group GUID: %1 Group Version GUID: %2 Package GUID: %3
19201 win:Error 2 Unknown protocol for package URI. input: %1
19202 win:Error 2 HttpRequest initialize failed. URL: %1 Error code: %2 - %3
19203 win:Error 2 HttpRequest sendRequest failed. URL: %1 Error code: %2 - %3
19204 win:Error 2 The content could not be coverted to unicode. URL: %1
19205 win:Error 2 The content from server is not valid XML for publishing. URL: %1 Error code: %2 - %3
19301 win:Error 2 Failed to create default machine policy document. Package: %1, %2 Error code: %3 - %4
19302 win:Error 2 Failed to create machine policy document from string. Package: %1, %2 Error code: %3 - %4
19303 win:Error 2 Failed to create user policy document from string. Package: %1, %2 Error code: %3 - %4
19304 win:Error 2 Failed to create package group descriptor document from string. Group: %1, %2 Error code: %3 - %4
19401 win:Error 2 Failed to get publishing server record from registry. Server ID: %1 Error code: %2 - %3
19402 win:Error 2 The URL has already been used by other publishing server. Server ID: %1 URL: %2
19403 win:Error 2 No URL was supplied for the publishing server. Server ID: %1
19404 win:Error 2 The ID for the publishing server is out of the range. Server ID: %1 Valid Range: [1~5]
19405 win:Error 2 The interval of hours for the publishing server is out of the range. Server ID: %1 Interval: %2 Valid Range: [0~23]
19406 win:Error 2 The interval of days for the publishing server is out of the range. Server ID: %1 Interval: %2 Valid Range: [0~365]
19407 win:Error 2 The interval unint for the publishing server is not valid. Server ID: %1 Interval Unit: %2 Valid Values: 0/Hour, 1/Day
19502 win:Error 2 SyncAppvPublishingServer failed due to a PowerShell error. Error: '%1'
19801 win:Error 2 Deimpersonation failed. Error: %1 - %2.
19802 win:Error 2 Read policy identities failed. URL: %1 Global: %2 For deployment configuration: %3 Error: %4 - %5.
19803 win:Error 2 Write policy identities failed. URL: %1 Global: %2 For deployment configuration: %3 Error: %4 - %5.
20001 win:Error 2 The connection group %1 version %2 could not be published because the virtual COM settings of the individual packages conflict. Verify that the virtual COM settings are the same for all member packages and try again. Error code: %3 - %4
20002 win:Error 2 Package %1 version %2 could not be published because its virtual COM settings conflict with those of other packages in connection group %3-%4. Verify that the virtual COM settings are the same for all member packages and try again. Error code: %5 - %6
20101 win:Error 2 Package %1 version %2 could not be published because its virtual file system settings conflict with other packages in connection group %3-%4. Verify that the virtual COM settings are the same for all member packages and try again. Error code: %5 - %6
22001 win:Warning 3 The SxS assembly '%1' could not be installed because its payload file '%2' is not part of the package. Please ensure this assembly is installed natively to ensure package functionality.



Microsoft-AppV-Server-Management

 EventId  Level  Value  Description
202 win:Error 2 A database error occurred. Reason: '%1'
203 win:Error 2 Failed to perform the requested operation. Reason: '%1'
204 win:Error 2 The computer name '%1' is in invalid format.
205 win:Error 2 The publishing server '%1' is not found in the database.
206 win:Error 2 Could not determine security identifier for machine account for '%1'.
207 win:Error 2 Failed to generate publishing metadata. Reason: '%1'
208 win:Error 2 The requested package %1 was not found.
209 win:Error 2 The requested package %1 could not be accessed. Please ensure the file is available, and you have the proper permissions.
210 win:Error 2 The requested package %1 is not a valid App-V package file.
211 win:Error 2 There was an Active Directory error while searching for %1. Please ensure the server is connected to the domain, and that Active Directory is available.
212 win:Error 2 The manifest file retrieved from %1 is not a well-formed App-V manifest file. The operation failed.
213 win:Error 2 An error was encountered parsing dynamic configuration file '%1'.
214 win:Error 2 A dynamic configuration with ID %1 was not found on the server.
215 win:Error 2 A dynamic configuration operation failed because the relevant database records had been changed since they were requested.
216 win:Error 2 Updating the entitlements for dynamic configuration %1 failed - default dynamic configuration cannot be entitled. The operation was aborted.
217 win:Error 2 There was a problem retrieving the requested package %1 for import. Error message: %2
218 win:Error 2 An error was encountered while trying to update the VSS writer metadata.
219 win:Error 2 An error was encountered while trying to update the VSS writer metadata. Error: %1-%2
401 win:Informational 4 Dynamic configuration file %1 was created.
402 win:Informational 4 Dynamic configuration file %1 was deleted.
403 win:Informational 4 The entitlements for package %1 were updated.
404 win:Informational 4 Dynamic configuration %1 was updated.
405 win:Error 2 The user is not authorized to access the management server. The requestor info: User name: %1 User host name: %2 User host address: %3 Requested URL: %4
406 win:Error 2 An error was encountered while adding the sid %1 to the admin role. Reason: '%2'
407 win:Error 2 An error was encountered while trying to add the initial administrators from the file '%1'. Reason: '%2'
408 win:Error 2 An error was encountered while trying to retrieve the user or group account information for the SID '%1'. Consider removing this sid from the RoleAssignments table in the database.
409 win:Error 2 An error was encountered while trying to translate SID '%1' to account name. Error: '%2'
501 win:Informational 4 A new connection group '%1' with package id '%2', version id '%3', and priority '%4' is successfully created.
502 win:Informational 4 A new connection group version '%1' is successfully created.
503 win:Informational 4 Connection group '%1' is successfully deleted.
504 win:Informational 4 Connection group '%1' is successfully updated.
505 win:Informational 4 Package version '%1' is successfully added.
506 win:Informational 4 Package version '%1' is successfully deleted.
507 win:Informational 4 Description of package '%1' is successfully updated to '%2'.
508 win:Informational 4 Package version '%1' is successfully updated.
509 win:Informational 4 Package entitlements are successfully copied from '%1' to '%2'.
510 win:Informational 4 Package '%1' is successfully entitled to '%2'.
511 win:Informational 4 Deployment configuration for package '%1' is successfully changed.
512 win:Informational 4 User configuration for package '%1' and user '%2' is successfully changed.
513 win:Informational 4 Access permissions for policy for package '%1' are successfully changed.
514 win:Informational 4 Publishing server '%1' is successfully added.
515 win:Informational 4 Publishing server '%1' is successfully deleted.
516 win:Informational 4 Publishing server '%1' is successfully updated.
517 win:Informational 4 User '%1' is successfully added to the administrators group.
518 win:Informational 4 User '%1' is successfully deleted from administrators group.
519 win:Informational 4 Package version '%1' is successfully enabled.
520 win:Informational 4 Package version '%1' is successfully disabled.
521 win:Error 2 Enable JavaScript to use the management console.



Microsoft-AppV-Server-Publishing

 EventId  Level  Value  Description
100 win:Error 2 Unexpected exception. Message: %1
101 win:Error 2 Failed to initialiize application settings. Message: %1
102 win:Warning 3 Failed to pre-load publishing metadata. Message: %1 Details: %2
103 win:Error 2 Failed to refresh publishing metadata. Message: %1 Details: %2
104 win:Error 2 Failed to delete retired dynamic configuration folder. Message: %1
200 win:Error 2 Invalid AppSettings found. Name: %1 Value: %2.
201 win:Error 2 Invalid sequence number attribute in publishing metadata.
202 win:Error 2 Invalid root node in publishing metadata. Name: %1.
203 win:Error 2 Incompatible publishing metadata. Acceptable version: %1 Actual version: %2.
204 win:Error 2 Package is missing in publishing metadata. Id: %1.
205 win:Error 2 Dynamic configuration conflicts: Dynamic configuration Ids: %1 - %2.
206 win:Warning 3 Publishing metadata not ready yet. This may be due to: - Both the management service and local cache are not available, or - Publishing service hasn't refreshed publishing metadata yet since management service became available.
212 win:Warning 3 The virtual application connection group in metadata source is not entitled to anyone. Id: %1 Group Guid: %2 Version Guid: %3.
213 win:Warning 3 The compatible head virtual application connection group contains non-head package(s). Group Id: %1 Group Guid: %2 Group Version Guid: %3 Package Id: %4 Package Guid: %5 Package Version Guid: %6.
216 win:Error 2 The client OS is unknown: %1.
217 win:Error 2 The 'TargetOS' in package contains unsupported OS type. Id: %1 Package Guid: %2 Version Guid: %3.
218 win:Warning 3 The compatibility conflict for a group is detected. The group is removed. Id: %1 Group Guid: %2 Version Guid: %3.
219 win:Warning 3 Could not refresh the user's group list from ActiveDirectory. Falling back to the group list from the user's token. Changes to group membership since the user last logged on may not be reflected.
220 win:Error 2 The client version is in an unknown format: %1.
221 win:Error 2 The client version contains portions larger than 65535: %1.

Tags:
app-v Events EventID
Start Administrative PowerShell Tasks As A User Wi...
A Simple On Screen Keyboard In PowerShell

Related Posts

 

Comments 1

Guest - John D on Thursday, September 12, 2019 11:46

Thank you,

Very helpfull

0 Cancel Reply
Thank you, Very helpfull :)
Cancel Update Comment
Already Registered? Login Here
Saturday, December 21, 2024

Captcha Image

@nickinformation Tweets

My german Blog: 

http://www.software-virtualisierung.de

in 

We use cookies on our website. Some of them are essential for the operation of the site, while others help us to improve this site and the user experience (tracking cookies). You can decide for yourself whether you want to allow cookies or not. Please note that if you reject them, you may not be able to use all the functionalities of the site.

Ok
More information