Troubleshooting

In this section:

This section identifies several issues that can be encountered while using WebFOCUS Visual Discovery Workbench AE and WebFOCUS Visual Discovery Server AE. Corresponding workarounds are provided accordingly.


Top of page

x
Microsoft Internet Explorer Security Warnings

On Windows Server 2003, 2008, and 2012, you will see one or more warnings when WebFOCUS Visual Discovery Workbench AE is started, if the Internet Explorer Enhanced Security Configuration is in effect for your account. This occurs because the embedded Internet Explorer control is used in the application. The warnings can be dismissed, since pages from Internet sites are not normally displayed in the application. Alternatively, the warnings can be avoided by disabling the Enhanced Security Configuration from the Add/Remove Windows Components or the Server Manager, as described in the following Microsoft article:

http://technet.microsoft.com/en-us/library/dd883248(WS.10).aspx


Top of page

x
Cookie Errors

If you receive the following error message in a browser while connecting to the WebFOCUS Visual Discovery Server AE:

Server Error in '/ADV' Application and A potentially dangerous request. Cookies value was detected from the client

or the following exception:

System.Web.HttpRequestValidationException

You can eliminate these errors by modifying the web.config file. In the <system.web> section, add the following attribute to the httpRuntime line:

requestValidationMode="2.0"

For example:

<httpRuntime executionTimeout="1200" requestValidationMode="2.0" />

For more information on modifying the web.config file, see the WebFOCUS Visual Discovery Analyst Edition Implementation Guide.


Top of page

x
Process is Locked or Must be Terminated

If a WebFOCUS Visual Discovery AE process becomes locked or must be terminated, restart Microsoft IIS or stop the w3wp.exe process that runs as a Network Service in Windows Task Manager. This issue can be caused by an Activation Error (HOSTING_SERVICEACTIVATIONERROR).

As a workaround:

To identify any errors that may be logged, review the following log files:


Top of page

x
Using Standalone URLs

When using standalone URLs (not URL items in the Business Intelligence Portal) that are clicked multiple times, the link may become cached. As a result, the original token will be continuously passed, resulting in a token timeout error.

As a workaround, you can issue a JavaScript call when the URL is clicked. This JavaScript call appends a random number to the URL to make it unique and avoid the caching issue in most instances. The following is the sample JavaScript call that can be used:

<html>
<head>
<SCRIPT language="JavaScript">
function anchor_test()
{
window.location.href='http://installhead:8080/ibi_apps/WFServlet?IBI_visd
is=http://installhead/ADV/Projects/ASL/Customers.aspx?COUNTRY=ENGLAND'+'&
RAND='+Math.random();;
}
</SCRIPT>
</head>
<body>
<a href="javascript:anchor_test()">Stand Alone Link</a>
</body>
</html>

WebFOCUS