Setup:

• FlashConnect does not have to be installed.

• The Web server must be running.

• The browser must be able to connect to the Web server.

Process:

Enter the URL to a Web page on your Web site.

Success:

The expected Web page displays.

Failure:

Web server or browser may be improperly configured, not running, or the network connection may be down.

Follow-up:

This problem does not involve FlashConnect. Contact your site administrator for assistance.

Setup:

• FlashConnect must be installed on your Web server.

• FlashConnect need not be installed on the database server.

Process:

Use a browser and load a static Web page in the w3library directory. The URL will look something like:

http://yourwebhost/w3library/index.html

For example:

http://mywebhost.rainingdata.com/w3library/index.html

Success:

FlashConnect welcoming page displays.

Failure:

Other than the static Web page, this test does not use FlashConnect. Most likely the problem is with the Web site configuration.

Follow-up:

Confirm the following are true:

• The URL is correct.

• The Web server has read access to the files in the w3library directory.

This problem does not involve FlashConnect. Contact your site administrator for assistance.

Setup:

• FlashConnect must be installed on your Web server.

• FlashConnect need not be installed on the database server.

• FlashConnect does not have to be running on the Web server nor D3 server.

• Copy the program helloworld.exe from the WebContent directory to the Web server’s cgi-bin directory where fccgi.exe is located.

Process:

Use a browser to access the helloworld.sh file. The URL will look something like:

http://yourwebhost/path/helloworld.sh

For example:

http://mywebhost.rainingdata.com/cgi-bin/helloworld.sh

Success:

A Web page containing the message "Hello World" displays.

Failure:

An error message displays.

Follow-up:

Confirm the following are true:

• The URL is correct.

• The Web server has execute access to the directory.

• Windows file and directory permissions allow execution.

Perform these actions:

• Shut down and restart the Web server.

• Shut down and restart Windows.

This problem does not involve FlashConnect. Contact your site administrator for assistance.

NOTE

This diagnostic tests the ability for the Web server to execute shell scripts. Since FlashConnect does not use shell scripts, it is possible for FlashConnect to work even if this diagnostic fails.

Setup:

• FlashConnect must be installed on your Web server.

• FlashConnect need not be installed on the database server.

• The PERL scripting language must be installed on the Web server.

• Copy the following applications from the w3library directory to the cgi-bin directory on the Web server:

Process:

Use a browser to access the helloworld.sh file. The URL will look something like:

http://yourwebhost/path/helloworld.sh

For example:

http://mywebhost.rainingdata.com/cgi-bin/helloworld.sh

Success:

A Web page showing the parameters and environmental variables displays. Generally the parameters section is empty and the environmental section is not usually empty.

Failure:

An error message displays.

Follow-up:

Confirm the following are true:

• The URL is correct.

• PERL exists on the Web server.

• PERL is accessible by the Web server.

• The Web server has execute access to the files in the cgi-bin directory.

This problem does not involve FlashConnect. Contact your site administrator for assistance.

Setup:

• FlashConnect must be installed on your Web server.

• FlashConnect need not be installed on your database server.

• Your Web server must be running.

Process:

Use a browser to access the fccgi.exe program.The URL will look something like:

http://yourwebhost/path/fccgi.exe

For example:

http://mywebhost.rainingdata.com/cgi-bin/fccgi.exe

Success:

One or both of these messages display to indicate success:

• ERROR - Missing required elements in form

• QUERYSTRING must be set for CGI

Failure:

A server error occurs.

Follow-up:

Confirm the following are true:

• The URL is correct.

• The Web server has access to the directory containing fccgi.exe.

• fccgi.exe is executable by the user used by the Web server.

• fccgi.exe is an executable file.

• fccgi.exe is in the correct directory.

• Files in the directory are executable by the Web server.

These two diagnostics may help resolve this problem:

Test 3. Verify the Web server can run a script in the cgi-bin directory.

Test 4. Verify the Web server can run a script in the cgi-bin directory, using PERL.

NOTE

This diagnostic is not designed for use with fcisapi.dll. If it is used in that manner, the results are meaningless.

Setup:

FlashConnect must be installed on the Web server.

Process:

From the command prompt, enter these commands:

where:

path is the location where FlashConnect is installed.

Success:

FlashConnect header information displays. A description of the header information is located in Using the FlashConnect Server Debug Program.

Failure:

FlashConnect not running message displays.

Follow-up:

The following options are available from the Services program (accessed from the Control Panel):

• If the FCService is not running, start FCService.

• If the FCService is already running, stop FCService. Restart FCService again.

• Stop the Web server and FCService. Restart the Web server and FCService.

• Stop the database, the Web server and FCService. Restart the database, the Web server and FCService.

Setup:

FCService must be running on the Web server.

Process:

From the UNIX prompt in the directory that contains FCdebug, execute:

Success:

FCService configuration displays.

Failure:

An error message displays.

Follow-up:

See the following sections:

Using the FlashConnect Server Debug Program

Diagnostic Messages Displayed On the Browser

Setup:

• FlashConnect must be installed and running on the Web server.

• FlashConnect must be installed and running on the database server.

Process:

From the MS-DOS command prompt in the directory that contains fcdebug, enter:

Success:

Appropriate server pools are listed in the Host Name column.

Failure:

Appropriate server pools are not listed in the Host Name column.

Follow-up:

• Check that FCService is running.

• Shut down and restart the D3 FlashConnect component.

• Shut down and restart FCService.

• Shut down and restart database.

• Shut down and restart Windows.

Setup:

• FlashConnect must be installed and running on the Web server.

• FlashConnect must be installed and running on the database server.

• Determine the first few characters of the database server's host name.

Process:

From the MS-DOS prompt on the Web server, enter:

For example:

One or two lines for each connection between the FCService and database server should display.

Success:

Status ESTABLISHED displays on line one for each connection. The status LISTEN displays on the second line, if it exists.

Failure:

There is not an entry with the status ESTABLISHED for each connection to database.

Follow-up:

• Use the Task Manager to verify there is only one copy of FCService running.

• Verify FlashConnect was started on the database server.

• Shut down and restart both the Web and database components of FlashConnect.

Setup:

• FlashConnect must be installed and running on the Web server.

• FlashConnect must be installed and running on the database server.

• The FlashConnect demonstration program must be installed on the database server.

• Copy the program fccgi.to.d3.test.bat from the FlashConnect WebContent directory to the Web server’s script (cgi-bin) directory where fccgi.exe is located.

Process:

From the MS-DOS command prompt in the directory that contains both fccgi.exe and fccgi.to.d3.test.bat, enter:

Success:

Resulting message contains the text connection OK.

Failure:

Resulting message contains the text connection failed.

Follow-up:

• Confirm that the Boo program is in the database server in the www bp file.

• Check that FCService is running.

• Check that database FlashConnect connections are established to the Web server using WWW-STATUS. See Using WWW-STATUS.

• Use fcdebug -t to confirm FCService is connected to database server.

• Shut down and restart FCService.

• Shut down and restart database.

• Shut down and restart Windows.