Adobe GoLive (ASP) Troubleshooting Report

This report contains information about the status of your ASP server software and the Adobe GoLive files installed on the server. Below you will find the results of various tests performed by this troubleshooting script.

Please refer to the GoLive User Guide and 'readme' file for more information about installing and configuring your ASP server to work with Adobe GoLive.

Click here for some additional troubleshooting tools. These tools scan your entire site for dynamic content specific errors in pages.

Click here to run test queries directly to databases.

Test Summary

Test	Description	Results	Summary
1	Check ASP software	Passed	ASP software is present.
2	Check Web server version	Passed	ASP enabled web server "Microsoft-IIS/6.0" was found.
3	Check script engine version	Passed	Both server script versions are 5.0 or later.
4	Check MSXML version	Passed	Required MSXML version is installed.
5	Check XML DOM support	Passed	XML DOM is supported on this server.
6	Check virtual path setting	Verify	You should verify that your virtual path settings are correct.
7	Check session state setting	Passed	ASP Session State is enabled.
8	Check password setting of web server	Passed	Access is anonymous, requiring no password security.
9	Check server config files	Passed	All server configuration files are present.
10	Check config file's line endings	Passed	The file was uploaded correctly.
11	Check config/include/friends.asp file	Passed	Server configuration is done.
12	Check config/include folder write permission	Failed	File writing test failed.
13	Check XML files	Passed	All XML files appear to be fine.
14	Check database datasource files	Failed	Problem(s) were found with one or more datasource file(s), or OpenSchema() is not supported.
15	Check CustomMerchant datasource files	Verify	No CustomMerchant datasource (*.ecp) files found in datasources folder.
16	Check XML datasource files	Verify	No XML datasource file (*.xds) found in datasources folder.
17	Check server variables	Passed	ASP server variables.
18	Check other issues	Verify	Check these issues manually.

How to read the test results

Test 1: Check ASP software

Passed: ASP software is present.

Description: This test checks to see whether your web server is enabled for Active Server Pages. Note that IIS 2.0 requires an additional ASP pack. IIS 3 or later includes ASP support by default. The IIS configuration (Site Management Console or other application) should have "Script Enabled" for the web site folder.

Back to Top

Test 2: Check Web server version

Passed: ASP enabled web server "Microsoft-IIS/6.0" was found.

Description: This test checks to make sure your Microsoft IIS software version is 4.0 or later.

Back to Top

Test 3: Check script engine version

Passed: Both server script versions are 5.0 or later.

Description: This test checks to make sure your server script engine versions are 5.0 or later. The script versions are depend on installed IIS or IE on the server. If you install IIS 4.0, then you have version 3.0 script engine. After that, if you install IE 5.0, then you will have version 5.0 script engine. Windows 2000 comes with IIS 5, which has version 5.1 script engine.

Back to Top

Test 4: Check MSXML version

Passed: Required MSXML version is installed.

Description: This test checks to make sure your server MSXML versions are 3.0 or later. You can get updater from Microsoft website (http://www.microsoft.com/xml/).

Back to Top

Test 5: Check XML DOM support

Passed: XML DOM is supported on this server.

Description: This test checks to make sure your server support XML DOM.If it is not supported, XML source contents feature and some troubleshooting test won't work.In case of then, you can update IIS with installing IE 5 or later.

Back to Top

Test 6: Check virtual path setting

Verify: You should verify that your virtual path settings are correct.

Description: This test checks that the virtual path to your web site folder for your URL points to the correct place. APPL_PHYSICAL_PATH is your virtual root setting. PATH_TRANSLATED is the physical path setting for this page. PATH_INFO, SCRIPT_NAME & URL contains the URL to this page without the hostname.

Back to Top

Test 7: Check session state setting

Passed: ASP Session State is enabled.

Description: This test checks the virtual root's session state. CustomMerchant requires this setting to be enabled. This setting can be set in Internet Service Manager or GLOBAL.ASA. But if you don't want to enable the option (default is enabled) for the whole site or virtual folder, you can set it on each required page by using the <%@ ENABLESESSIONSTATE=True|False%> setting.

Back to Top

Test 8: Check password setting of web server

Passed: Access is anonymous, requiring no password security.

Description: This test checks whether the web server is set to require user names and passwords. If so, only basic authentication is supported by GoLive. If any of the following server variables have a value, there is a password required to access the server. In case of basic authentication, server variable HTTP_AUTHORIZATION's value will start "Basic ". Other http authentication methods are not supported.

Back to Top

Test 9: Check server config files

Passed: All server configuration files are present.

Description: This test checks to see whether the ASP and XML files for GoLive have been properly installed on the server. It also produces a directory tree list of all files in the config folder. The following files are required.

File	Exist	Note
actions/ado.actions6.asp	Found	for updating
actions/glerror.asp	Found	error page for failed actions
actions/custommerchant.actions6.asp	Found	for CustomMerchant
include/ado.runtime6.asp	Found	required
include/friends.asp	Found	required
include/custommerchant.runtime6.asp	Found	required
include/utils.runtime6.asp	Found	required
include/xml.runtime6.asp	Found	required
info/ADODataSourceEditor/Main.html	Found	for ASP authoring
info/CMDataSourceEditor/Main.html	Found	for CustomMerchant authoring
info/XMLDataSourceEditor/Main.html	Found	for XML authoring
info/ado.info6.asp	Found	for ASP authoring
info/ado.ui6.xml	Found	for ASP authoring
info/general.ui6.xml	Found	for authoring
info/custommerchant.cart.info6.asp	Found	for CustomMerchant
info/custommerchant.order.info6.asp	Found	for CustomMerchant
info/custommerchant.ui6.xml	Found	for CustomMerchant
info/custommerchant.xform.info6.xsl	Found	for CustomMerchant
info/parseasp.asp	Found	for ASP authoring
info/reservedwords.ui6.xml	Found	for ASP authoring
info/test.asp	Found	for ASP authoring
info/test.html	Found	for ASP authoring
info/testsql.asp	Found	for ASP authoring
info/troubleshooting.asp	Found	this page
info/ui6.asp	Found	for ASP authoring
info/vbscript.ui6.xml	Found	for ASP authoring
info/xml.info6.asp	Found	for XML authoring
info/xml.ui6.xml	Found	for XML authoring

Config files:

    Temp$$$11395326.asp
+---actions
|       ado.actions6.asp
|       custommerchant.actions6.asp
|       glerror.asp
+---datasources
|       inc.mdb
|       README_asp.txt
|       UdlConnectionTest.udl
+---include
|       ado.runtime6.asp
|       blockview.runtime6.asp
|       custommerchant.runtime6.asp
|       extrafilters.runtime6.asp
|       friends.asp
|       utils.runtime6.asp
|       xml.runtime6.asp
+---info
|       ado.info6.asp
|       ado.ui6.xml
|       blockview.info6.asp
|       blockview.ui6.xml
|       custommerchant.cart.info6.asp
|       custommerchant.jxform.info6.xsl
|       custommerchant.order.info6.asp
|       custommerchant.ui6.xml
|       custommerchant.xform.info6.xsl
|       extrafilters.ui6.xml
|       general.ui6.xml
|       gl.css
|       parseasp.asp
|       reservedwords.ui6.xml
|       test.asp
|       test.html
|       testsql.asp
|       troubleshooting.asp
|       troubleshooting2.asp
|       troubleshootinginclude.asp
|       ui6.asp
|       vbscript.ui6.xml
|       xml.info6.asp
|       xml.ui6.xml
+---+---ADODataSourceEditor
|   |       Main.html
+---+---CMDataSourceEditor
|   |       Main.html
+---+---XMLDataSourceEditor
|   |       check.gif
|   |       Main.html
|   |       rowset.gif
|   |       structure.gif
|   |       x.gif

Back to Top

Test 10: Check config file's line endings

Passed: The file was uploaded correctly.

Description: This test checks whether the GoLive text files have proper line endings. If you upload the config files or other ASP files from a Macintosh using binary upload, ASP may not work properly. You must upload ASP files as text. Also if the file's line ending is not set to Windows, ASP pages may not work. This is set in GoLive under Edit>Web Settings, Global tab, select Windows (CR/LF) from the popup menu.

53 line(s)

Back to Top

Test 11: Check config/include/friends.asp file

Passed: Server configuration is done.

Description: This test checks the friends.asp file, which is used to provide IP based security. By default, access to the GoLive Dynamic Content authoring features is only allowed from the machine on which the server is running ('localhost'). To allow access from machines you need must edit the config/include/friends.asp file to include the IP address of that machine or use the Dynamic Content setup wizard from the Site>Settings>Dynamic Content dialog.

IP address	Mask	Note
62.59.38.242	255.255.255.255	Other settings
e>.undefined.undefined.undefined	255.255.255.255	Other settings

Back to Top

Test 12: Check config/include folder write permission

Failed: File writing test failed.

Description: This test checks the write permission of config/include folder, which is used by GoLive's Preview function. To preview a dynamic page, GoLive uploads a temporary file to config/include folder so that the web server can process it. If the folder does not have write permission, the preview will not work. Note that you may want to disable write permission on your production servers. In that case, you will not be able to use the GoLive preview with the public server as your site URL. Other features will not be effected.

If error 'ASP 0177 : 800a0046' is returned when previewing a page in GoLive, the folder does not have write permission set.

Back to Top

Test 13: Check XML files

Passed: All XML files appear to be fine.

Description: This test performs a basic syntax check on the XML files in config/info folder.

Back to Top

Test 14: Check database datasource files

Failed: Problem(s) were found with one or more datasource file(s), or OpenSchema() is not supported.

Description: This test examines all the database datasource files found in the datasources folder and produces detailed information about each one. MS-Access (*.mdb) files should not be read-only. If they are read-only any update or other datasource modification action will fail. If MDB files failed to open a connection, the server may have old MDAC version. MDAC 1.5 is installed by default with IIS 4.0, but GoLive requires MDAC 2.1 or later. You can get updater from Microsoft website (http://www.microsoft.com/data/). If UDL, DSN or XDB files failed to open a connection, these files have incorrect settings or the datasource is unavailable. If OpenSchema fails and the other tests are OK, the local server's ASP engine may not support the OpenSchema() call. In this case, the server will not work as a development server with GoLive.

Back to Top

Test 15: Check CustomMerchant datasource files

Verify: No CustomMerchant datasource (*.ecp) files found in datasources folder.

Description: This test examines CustomMerchant datasource files (*.ecp) found in the datasources folder and produces detailed information about each one.

Back to Top

Test 16: Check XML datasource files

Verify: No XML datasource file (*.xds) found in datasources folder.

Description: This test examines XML datasource files (*.xds) found in the datasources folder and produces detailed information about each one.

Back to Top

Test 17: Check server variables

Passed: ASP server variables.

Description: This test generates a table of server variables so that you can review and verify their status.

Back to Top

Test 18: Check other issues

Verify: Check these issues manually.

Description: If you are still having problems, here's a listing of known issues you can check manually. Some problems may be dependent on web server versions, datasource server, datasource driver.

Back to Top