<< PREVIOUS NEXT >>

 

 

VSP-MEMORY

 

PROVISIONING FAILURES

 

WINDOWS – AUTO-INSTRUMENTATION ENABLED

 

Symptom: Auto-instrumentation is enabled and provisioning fails

 

Recommended Actions:

1. Ensure that an entry for the application that is being provisioned does not exist in the registry path: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options

2. If it exists, VSP-Memory does not overwrite any existing entry (to prevent breaking any existing functionality)

   1. Remove the registry key if possible and re-provision the application

   2. If the key cannot be removed, uncheck the auto-instrumentation option in CMS and re-provision the application. After the application is provisioned, instrument the application manually

 

LINUX – AUTO-INSTRUMENTATION ENABLED

 

Symptom: Auto-instrumentation is enabled and provisioning fails

 

Recommended Actions:

1. Refer the VSP-memory-assist logs for information on where the issue occurred

2. If this application has been auto-instrumented previously, check the application path to see if existing VSP-memory auto-instrumentation binaries exist

   1. VSP-memory auto-instruments applications by renaming the original application with a "-virsec" appendage. A special VSP-memory auto-instrumentation binary is copied to the application path. When the application is started, the VSP-memory auto-instrumentation binary calls the real application with the “-virsec” appendage

   2. If provisioning fails after auto-instrumentation, rename the "-virsec" or "-virsec.backup" version of the application back the original name. Remove any remaining "-virsec*" binaries

 

AUTO-INSTRUMENTATION DISABLED

 

Symptom: Auto-instrumentation is disabled and provisioning fails

 

Recommended Actions:

1. Ensure the application path provided in CMS exists

2. Refer the VSP-memory-assist logs for more information

 

<< PREVIOUS NEXT >>