Message

The Client service started successfully.

Message

The Client service shut down.

Message

A required component (%1) cannot be loaded.  Please repair your installation. {error: %2}

Fields

Message

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}

Fields

Message

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}

Fields

Message

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}

Fields

Message

The Client could not determine the identity of a caller on a public request, and the request was denied. {error: %1}

Fields

Message

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}

Fields

Message

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.

Fields

Message

The access to the client was denied. The caller didn't have required permission for this operation.

Message

The Client failed to register for power notifications.  {error: %1-%2}.

Fields

Message

The Client failed to unregister for power notifications.  {error: %1-%2}.

Fields

Message

SLAPI check failed because of failure to read license info. {error: %1}

Fields

Message

The Client service cannot be started due to reboot required.

Message

The Client service cannot be started due AppV being disabled.

Message

The Client service cannot be started due to component %1 failing during the global maintenance phase. {error: %2-%3}.

Fields

Message

The maintenance phase has failed for user %1 in component %2. {error: %3-%4}.

Fields

Message

IAppVClient::%1 COM method entered.

Fields

Message

IAppVClient::%1 COM method exited. %2

Fields

Message

Active processing could not be shut down, this may lead to delays or hangs for Client shutdown. {error: %1-%2}

Fields

Message

Package %1 version %2 was successfully configured in folder '%3'.

Fields

Message

Package %1 version %2 was successfully published for the user.

Fields

Message

Package %1 version %2 was successfully published for all users.

Fields

Message

Package %1 version %2 was unpublished for the user.

Fields

Message

Package %1 version %2 was unpublished for all users.

Fields

Message

Package %1 version %2 was removed.

Fields

Message

Package %1 version %2 failed configuration in folder '%3' with error %4-%5.

Fields

Message

Virtual application connection group %1 version %2 was successfully configured.

Fields

Message

Virtual application connection group %1 version %2 failed configuration with error %3-%4.

Fields

Message

Virtual application connection group %1 version %2 was successfully published for the user.

Fields

Message

Virtual application connection group %1 version %2 was successfully published for all users.

Fields

Message

Virtual application connection group %1 version %2 was unpublished for the user.

Fields

Message

Virtual application connection group %1 version %2 was unpublished for all users.

Fields

Message

Virtual application connection group %1 version %2 was removed.

Fields

Message

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.

Fields

Message

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.

Fields

Message

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

Fields

Message

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

Fields

Message

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

Fields

Message

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

Fields

Message

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

Fields

Message

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

Fields

Message

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.

Fields

Message

The package %1 version %2 could not be configured because it can only be used with 64-bit versions of Windows.

Fields

Message

The package %1 version %2 could not be configured because it is not compatible with this version of Windows.

Fields

Message

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.

Fields

Message

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.

Fields

Message

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.

Fields

Message

The package %1 version %2 could not be configured because the user account does not have administrative privileges.

Fields

Message

The package %1 version %2 could not be published globally because the user account does not have administrative privileges.

Fields

Message

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.

Fields

Message

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.

Fields

Message

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.

Fields

Message

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.

Fields

Message

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.

Fields

Message

The package %1 version %2 could not be unpublished globally because the user account does not have administrative privileges.

Fields

Message

The package %1 version %2 could not be unpublished because it is not published to the target of the unpublish operation.

Fields

Message

The package %1 version %2 could not be removed because the package is not configured on the system.

Fields

Message

The package %1 version %2 could not be removed because the user account does not have administrative privileges.

Fields

Message

The package %1 version %2 cannot be repaired because the package is not configured on the system.

Fields

Message

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.

Fields

Message

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.

Fields

Message

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.

Fields

Message

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.

Fields

Message

The app connection group %1 version %2 could not be added because the user account does not have administrative privileges.

Fields

Message

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.

Fields

Message

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.

Fields

Message

The app connection group %1 version %2 could not be enabled globally because the user account does not have administrative privileges.

Fields

Message

The app connection group %1 version %2 could not be disabled because it is not enabled for the target of the disable operation.

Fields

Message

The app connection group %1 version %2 could not be disabled globally because the user account does not have administrative privileges.

Fields

Message

The app connection group %1 version %2 could not be removed because the package it has not been added on the system.

Fields

Message

The app connection group %1 version %2 could not be removed because the user account does not have administrative privileges.

Fields

Message

The app connection group %1 version %2 cannot be repaired because the app connection group has not been added on the system.

Fields

Message

A package could not be unpublished for the user because it is currently in use by the user.  The package will be unpublished at a later time.
Package %1
Version %2
Activity #%3

Fields

Message

A package could not be globally unpublished because it is currently in use.  The package will be unpublished at a later time.
Package %1
Version %2
Activity #%3

Fields

Message

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.

Fields

Message

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.

Fields

Message

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.

Fields

Message

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.

Fields

Message

A connection group could not be unpublished for the user because it is currently in use by the user.  The connection group will be unpublished at a later time.
Connection Group %1
Version %2
Activity #%3

Fields

Message

A connection group could not be globally unpublished because it is currently in use.  The connection group will be unpublished at a later time.
Connection Group %1
Version %2
Activity #%3

Fields

Message

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

Fields

Message

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

Fields

Message

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

Fields

Message

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

Fields

Message

A package could not be published for the user because it is currently in use by the user.  The package will be published at a later time.
Package %1
Version %2
Activity #%3

Fields

Message

A package could not be globally published because it is currently in use.  The package will be published at a later time.
Package %1
Version %2
Activity #%3

Fields

Message

A connection group could not be published for the user because it is currently in use by the user.  The connection group will be published at a later time.
Connection Group %1
Version %2
Activity #%3

Fields

Message

A connection group could not be globally published because it is currently in use.  The connection group will be published at a later time.
Connection Group %1
Version %2
Activity #%3

Fields

Message

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.

Fields

Message

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.

Fields

Message

The pending publish operation for package %1 version %2 was not performed because network connectivity is not available.

Fields

Message

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

Fields

Message

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

Fields

Message

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}

Fields

Message

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.

Fields

Message

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.

Fields

Message

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.

Fields

Message

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.

Fields

Message

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.

Fields

Message

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.

Fields

Message

Failed to move Catalog folder ?%1? to new required location ?%2?. {error: %3}

Fields

Message

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}

Fields

Message

Catalog folder ?%1? was migrated to new required location ?%2?, but the new location previously existed.

Fields

Message

Failed due to could not get catalog folder. {error: %1-%2}

Fields

Message

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.

Fields

Message

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.

Fields

Message

The Client service has encountered a critical security issue and must shut down immediately. {error %1-%2}

Fields

Message

The Client service has encountered a critical security issue and must shut down immediately. {error %1-%2}

Fields

Message

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).

Fields

Message

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.

Fields

Message

Running %1 script defined in package %2 for event %3. Script execution was initiated by User Account: '%4'; command line: '%5'.

Fields

Message

A %1 script is defined in package %2 for event %3 but will not be run because embedded scripting is disabled for this client.

Fields

Message

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.

Fields

Message

An error was encountered while reading the setting to enable scripts. Error code:  %1-%2.

Fields

Message

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.

Fields

Message

%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.

Fields

Message

%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.

Fields

Message

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.

Message

The move/rename of a directory was blocked by the Virtual File System because it represented the merged view of more than one package directory and/or a non-package directory.

Message

The delete of a directory was blocked by the Virtual File System because it represented the merged view of more than one package directory and/or a non-package directory.

Message

The delete of directory '%1' was blocked by the Virtual File System because it represented the merged view of more than one package directory and/or a non-package directory.

Fields

Message

Failed to get Virtual Service information from manifest.
 Package: %1
 Version: %2
 Error: %3-%4

Fields

Message

Virtual Service startup type %1 is not supported. The only supported configuration values are Automatic, Manual and Disabled.

Fields

Message

Service %1 failed to start due to error %2.

Fields

Message

DependentService %1 failed to start due to error %2.

Fields

Message

Service %1 failed while handling a control message due to error %2.

Fields

Message

Could not acquire service start lock due to error %1.

Fields

Message

Starting automatic service %1.

Fields

Message

Service %1 could not be stopped.

Fields

Message

Automatic service %1 could not be started.

Fields

Message

Request to change the service configuration is rejected. Currently, changing service configuration during runtime is not supported.

Message

Request to delete a virtual service is rejected. Currently, deleting a service during runtime is not supported.

Message

Service %1 is created as a native service instead of a virtual service. Creating virtual service during runtime is not supported.

Fields

Message

Request to set virtual service security is rejected. Currently, changing service security during runtime is not supported.

Message

The client service has encountered an error monitoring settings. Changes to some settings will not take effect until the service is restarted. {error: %1}

Fields

Message

Failed to load provided xml.
DOM Error: %1
Reason: %2
Line: %3
Column: %4
Offset: %5

Fields

Message

Failed to validate provided xml.
DOM Error: %1
Reason: %2

Fields

Message

Invalid connection group document format. There are no packages specified in the connection group document for connection group %1, version %2.

Fields

Message

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.

Fields

Message

Failed to update the connection groups for user %1. Some virtualized applications may fail to execute properly. Error: %2

Fields

Message

All of the package groups associated with the publishing of package %1, version %2 were not successfully refreshed. Error: %3

Fields

Message

All of the package groups associated with the unpublishing of package %1, version %2 were not successfully refreshed. Error: %3

Fields

Message

All of the package groups associated with the adding of package %1, version %2 were not successfully refreshed. Error: %3

Fields

Message

Failed to get the package groups associated with the removal of package %1, version %2. Error: %3.

Fields

Message

All of the package groups associated with the removal of package %1, version %2 were not successfully refreshed. Error: %3

Fields

Message

Package group %1, version %2 was not successfully refreshed. Error: %3

Fields

Message

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.

Fields

Message

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.

Fields

Message

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.

Fields

Message

Failed to get the package groups associated with the unpublish of package %1, version %2. Error: %3.

Fields

Message

Registry path %1 was malformed in dynamic configuration file for package %2, version %3.

Fields

Message

Error encountered while executing command %1. Error: %2

Fields

Message

Warning raised while executing command %1. Warning: %2

Fields

Message

Error encountered when accessing a property value of an App-V Publishing Server. This Publishing Server has been skipped.

Message

Error encountered when accessing a property value of an App-V Client Connection Group. This Connection Group has been skipped.

Message

Error encountered when accessing a property value of an App-V Client Package. This Package has been skipped.

Message

Error encountered when accessing a property value of an App-V Client Application. This Application has been skipped.

Message

Error encountered when attempting to access the packages of an App-V Client Connection Group. This Connection Group will display no Packages.

Message

Error encountered when attempting to access the applications of an App-V Client Package. This Package will display no Applications.

Message

Error encountered during Powershell process startup or exit while executing command '%1'.

Fields

Message

Error encountered while executing command '%1'. Please refer to the AppV Client log for error details.

Fields

Message

Error encountered when accessing a property value of an App-V Client Configuration.

Message

Process %1 failed to start due to %4 subsystem failure. Package ID %2. Version ID %3. Error: %5-%6

Fields

Message

Unable to inject into a non-virtual process with PID %1. This process will not be able to use virtual components.

Fields

Message

Could not takeover extension points ownership from legacy package %1. Error: %2

Fields

Message

Could not give extension points ownership back to legacy package %1. Error: %2

Fields

Message

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.

Fields

Message

Taking over extension points ownership using command: %1

Fields

Message

Give back extension points ownership using command: %1

Fields

Message

Failed reading Managing Authority policy for package %1. Error: %2-%3

Fields

Message

Failed reading old Managing Authority policy for package %1. Error: %2-%3

Fields

Message

Error '%2' waitig for command: %1

Fields

Message

Timed out waitig for command: %1

Fields

Message

Error '%2' getting exit code for command: %1

Fields

Message

Command '%1' exited with code: %2

Fields

Message

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.

Fields

Message

User VFS COW state deleted for package ID %1.

Fields

Message

User VFS COW state deletion failed for package ID %1, error %2-%3.

Fields

Message

%1 application from package ID %2 failed to launch. process ID %3, error %4-%5.

Fields

Message

User VFS COW folder validation failed for source: %1, target: %2.

Fields

Message

Failed to publish roaming packages, error %1-%2.

Fields

Message

Failed to publish roaming groups, error %1-%2.

Fields

Message

Security information for VFS directory %1 has changed from its previous value.

Fields

Message

Error: %1-%2. Process %3 already belongs to a job. It cannot be added to the virtual environment. Package %4, Version %5.

Fields

Message

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.

Fields

Message

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.

Fields

Message

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.

Fields

Message

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.

Fields

Message

App-V client is relying on a mobile network connection to stream packages.  Background streaming has been suspended due to the mobile network approaching/exceeding the data limit or roaming.

Message

App-V client has detected an unrestricted network connection or a mobile connection with sufficient remaining data capacity.  Background streaming has resumed.

Message

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.

Message

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.

Message

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.

Fields

Message

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.

Message

App-V client has entered connected standby mode.  Background streaming has been suspended.

Message

App-V client has exited connected standby mode.  Background streaming has resumed.

Message

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.

Message

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.

Fields

Message

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.

Fields

Message

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.

Fields

Message

The package %1 version %2 could not be configured due to low disk space.  Ensure that there is enough disk space and try again.

Fields

Message

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.

Fields