Troubleshooting Web Output

This chapter contains information that you can use to resolve rendering problems on client workstations.
If you or a member of your audience cannot display your presentation, then refer to the following table for solutions.
Note: To ensure that software requirements have been met, see What does your audience need to view the presentation?.
Web Troubleshooting
Cannot access the HTML file.
Incorrect URL.
Check the URL in the browser.
Network access denied.
Check operating environment permissions for the HTML file.
Check firewall access permissions for Internet clients.
Browser cannot display the file.
Browser or Java plug-in might not meet requirements.
ActiveX control might not have been installed or might be out of date.
Install the ActiveX control manually (see Customizing the SAS/GRAPH ActiveX Control Installation Process). Consider updating the presentation to prompt users to install the control (see Configuring an Existing ActiveX Presentation to Install the SAS/GRAPH ActiveX Control from Your Local Network).
User attempting to run the ActiveX control in a browser other than Internet Explorer.
Switch to the required version of the Internet Explorer Web browser.
User has not been authenticated for that browser and that Web page.
Check to see whether authentication is needed, and then authenticate. See Connecting to Web Servers That Require Authentication.
Browser does not recognize the file as HTML.
Ensure that the type of the HTML file is correctly specified.
Ensure that the DOCTYPE and MIME tags are correctly formatted.
Browser permissions too restrictive.
Check browser permissions. See Checking Browser Permissions.
Browser displays blank page.
Browser cannot access the referenced image file.
If not running an applet or control, check the image file at the location specified in the HTML file.
Browser cannot run the applet or control.
For Java, ensure that the HTML file is correctly referencing the Java plug-in and SAS Java archive. See Specifying the Location of Control and Applet Files (CODEBASE= and ARCHIVE= Options).
Check browser permissions for running Java scripts. See Checking Browser Permissions.
In the UNIX operating environment, remove any CLASSPATH environment variables. See Removing CLASSPATH Environment Variables.
Open the browser's Java Console and trace the source of the error.
Browser displays popup message Error: Not enough virtual memory to produce plot.
Client RAM is insufficient for rendering.
Generate a new graph using a smaller data set or a simpler graph. If using PROC GMAP, consider using PROC GREDUCE.
Graph is not rendering as specified by the ODS graph style.
A style attribute might not be enabled for your ODS destination.
Ensure that the attribute is enabled for your ODS destination. For example, the URL attribute is not enabled for the PS destination. Refer to the table of style attributes for the STYLE statement of the TEMPLATE procedure in SAS Output Delivery System: User's Guide.
A style attribute might be overridden by a global option, global statement option, procedure option, or statement option.
Specify the minimum options needed for your graph, for example:goptions reset=all device=activex;
In ActiveX, the user gets the message There is a pending reboot for this machine...
  1. Virus-scanning software might be interfering with the installation of the control.
  2. Other instances of the control might be running.
  1. Turn off any virus-scanning software before installing the control.
  2. Be sure to close all instances of Internet Explorer before installing the control.
Text font is incorrect.
Java font is defined differently.
Change browser fonts or change the SAS/GRAPH program. See Correcting Text Fonts.
Text in browser shows incorrect characters.
Browser misinterpreting special characters.
Replace special characters with character entities. See Using HTML Character Entities.
Graph in browser differs from graph in SAS.
A graphics option or global statement might be unsupported or partially supported for that applet or control. See also Resolving Differences between Graphs Generated with Different Technologies.
Refer to the descriptions for the options that you are using and to Summary of ActiveX and Java Support for information about whether a statement or option is supported.
A default value in the applet or control is overriding a default option value.
Specify a value for the option rather than relying on the default. See Resolving Differences between Graphs Generated with Different Technologies.
GPLOT lines drawn in reverse order on the client.
This change was made intentionally to maintain the integrity of plots drawn with the AREAS= option.
In ActiveX, black-and-white image is not displayed
ActiveX does not enable 8-bit grayscales images.
Convert the image to 24-bit monochrome.
Graph loses attributes after graph type is changed in the Web browser.
Some attribute loss is inherent in graph type changes.
Select the Refresh button in the Web browser to restore the original graph.
Changes made through the Data Options dialog box cause the graph to revert to its original view.
The graph discards subsetting information if you make changes through the Data Options dialog box.
Make any changes needed through the Data Options dialog box before subsetting the graph.