Troubleshooting Custom Actions on a Windows Client Computer
If the custom action is not being correctly run on a Windows client computer, you can troubleshoot custom action issues as follows:
• Verify the browser’s default folder for downloads.
If the downloads folder is customized by the user, update the following property in the wrvsca.properties file:
environment.file.location
For instance, the default folder for downloads can be specified as follows:
environment.file.location=D:\Temp
• Turn on custom action handler logging.
To turn on custom action handler logging, set the following property in the wrvsca.properties file on the Windows client computer:
debug=true
The logs are generated in the logs folder. For instance, wrvsca.log.
 |
Over time, the logs can consume a significant amount of disk space, so do not turn on logging for prolonged periods.
|
• Check the parameters that are passed as input to a custom action.
To check the parameters that are passed as input to a custom action, set the following property in the wrvsca.properties file on the Windows’ client computer:
params.show=true
When a custom action is run, the action will also launch the default text editor (Notepad) and display the parameters that were passed.
|
|
Set this property to true only when debugging an issue.
|
• Check the Windows Event log.
The custom action command that is executed, is logged to the Windows Event Log. To view the logged event, open the Windows Event Viewer and click Event Viewer > Windows Logs > Application. In the Source column, search for events logged by wrvsca.