KnowledgeBase - How do I test for a script-blocker?
Article

How do I test for a script-blocker?

« Go Back
Products
Webtrends Analytics 9.2
Webtrends Analytics 8.7
Webtrends Analytics 8.5
Webtrends Analytics 8.1
Webtrends Analytics 8.0
Webtrends Analytics Legacy
Symptoms
Webtrends is unable to analyze profiles, a possible indication of a third-party application preventing Visual Basic scripts from running.
Cause

Resolution
To test the system's ability to run Visual Basic scripts, follow the steps below:

1. Download and extract test.vbs (attached) to the Webtrends server.

2. Open a command line window and navigate to the location where the file was extracted.

3. Type the following command:

cscript test.vbs

The following (or similar) information displays:

Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

3. If the above information did not open a script-blocker pop-up window, type the following command:

echo %ERRORLEVEL% 

The following information displays:

22

If a pop-up or a value other than 22 displays then a script-blocker may be running.

Note: In the event that the following message displays:

CScript Error: Can’t find script engine “VBScript” for script “C:\test.vbs”

Run the following command from the command line or the run dialogue box:

regsvr32 vbscript

Running this command will repair the registry entry for the vbscript dynamic link library, after which the above tests should be performed again to confirm whether this was the issue.
Was this article helpful?

Please tell us how we can make this article more useful.

Characters Remaining: 255