• Overview of the Interactive Schedule Viewer

• Change Content
• Change Appearance
• Partition the Display
• Zoom In or Out
• Save Your Changes
• Troubleshoot an Applet Error

• File Menu
• View Menu
• Format Menu
• Project Menu

• Table Pop-up Menu

Troubleshoot an Error

Common problems that occur with the ISV Applet include the following:

• The chart does not display in the browser
• A Data set read error message is received when the chart is opened
• A logo or background image access error message is received when the chart is opened or when you attempt to specify a background or logo image for your chart

For other problems, contact your on-site SAS support personnel for assistance.

The Chart Does Not Display

If the chart does not display in your Web browser, your browser might be using an incompatible version of the Java JRE. The ISV Applet requires the Java 1.5 or later JRE. Verify that your browser is using a compatible version of the JRE. For example, on Windows, do the following:

1. Select Start Settings Control Panel to open the Windows Control Panel.
2. Do one of the following based on whether the JRE or the Java Plug-in is installed:
   • If Java is installed, double-click the Java icon, and then do the following in the window that opens :
     • Click the Advanced tab.
     • Do one of the following based on your JRE version:
       • For version 1.5, expand <APPLET> tag support.
       • For version 1.6, expand Default Java for browsers.
     • If your browser is not selected, select it, and then click Apply.
     • Click OK to close the dialog box.
   • If the Java Plug-in is installed, double-click the Java Plug-in icon, and then do the following in the window that opens:
     • Click the Advanced tab.
     • In the Java Runtime Environment drop-down list, select a run-time environment.
     • Click the Browser tab.
     • If your browser is not selected, select it, and then click Apply.
     • Click OK to close the dialog box.

For browsers on other platforms, refer to the browser documentation for instructions on how to determine the version of the JRE that it is using and how to change it, if necessary.

If your browser is using a compatible version of the JRE, check the Java Console for error messages. To open the Java Console window, in your Windows icon tray, right-click the Java icon (), and then select Open Console from the pop-up menu.

Note: If you closed your browser window, the Java icon might have been removed from the icon tray. In that case, open the chart again, and then leave the browser window open.

If messages appear in the Java Console, you might be able to determine the source of the problem from the messages. You can usually ignore the messages that begin with "at." If the source of the problem is not apparent from the messages, contact your on-site SAS support personnel for assistance.

A Data Set Read Error Is Displayed

If the schedule data cannot be read, a Data Set Read Error dialog box appears in which an error message is displayed. Common data set read errors include the following:

• The data set or data file cannot be found
• Mandatory information, such as the early start date, is missing from the schedule data
• The ISV Applet cannot access the SAS server or does not have permission to read the data file

If you are receiving a data set read error message, contact your on-site SAS support personnel for assistance.

A Logo or Background Image Access Error Is Displayed

The ISV Applet can be configured to display a background image and a logo image on the chart. The chart author can configure the chart so that you can specify a company logo and background image to use. If so, you can select View Background and Logo to specify a logo and background image in the Logo and Background dialog box. When you open a chart that uses a background image and a logo image, or if you attempt to add a background image or logo image to your chart using the Background and Logo dialog box, one or more of the following error messages might be displayed.

Logo Image and Background Image Access Error Messages

Error Message	Meaning
Inaccessible browsing path "http://hostname". Provide an accessible browsing path.	The host hostname is a valid host, but the Web server on hostname is not available. By default, the ISV Applet uses localhost as the Web server host name. If hostname is localhost and your local computer does not host a Web server, the chart that you are viewing might not be configured to access the logo and background image files. In that case, you cannot add a logo or background image to the chart. Otherwise, the Web server on localhost might be down. Contact your on-site SAS support personnel for assistance.
No such host: invalid-URL	The host name specified in invalid-URL is not a valid host. Contact your on-site SAS support personnel for assistance.
Provide a valid image path starting with http:	The URL specified does not use the HTTP protocol. For example, the URL might begin with FILE instead of HTTP. Contact your on-site SAS support personnel for assistance.
No such directory: invalid-URL	The Web server path specified in invalid-URL does not exist on the Web server or the Web server does not allow access to the specified directory. Contact your on-site SAS support personnel for assistance.
Logo image file "invalid-URL" could not be found.	The logo image file name specified in invalid-URL does not exist on the Web server. You might be able to use the View Background and Logo option to locate the logo image file.
Background image file "invalid-URL" could not be found.	The logo image file name specified in invalid-URL does not exist on the Web server. You might be able to use the View Background and Logo option to locate the background image file.
The specified background image or logo "image-URL" is password protected. Cannot be accessed.	The URL of the background or logo image is password protected. Because the ISV Applet cannot prompt you for your user credentials in that case, it cannot access the image files. If both the background image and logo image URL are password protected, this error message appears twice.