Beehive Troubleshooting

Beehive Software, Inc. - P.O. Box 29527 - Bellingham, WA 98228 - Tel: 360-738-6863

Beehive TroubleShooting Guide

Beehive Macintosh Client Troubleshooting

Beehive Windows Client Troubleshooting

Beehive Macintosh Client Troubleshooting

Beehive was designed to eliminate a number of typical ftp file transfer problems experienced by users. If a problem occurs, it usually means that something is improperly configured in the ftp site setup. To test the connection, just launch Beehive ftp forms and open the Site window from the SendFile menu. Select the site you want to test by highlighting it in the list. Now select "Edit site", this will open a window which contains a "Test" button that can check if the connection is properly setup. If the connection is OK a dialog box will return a "No error" message. If an error dialog occurs, then you must fix the site setup, then save and test again:

Error Description: When you click on the "Test" button in the FTP site setup window and you get a connection error message.

Error Description: When you click on the "Send" button the job is not sent and you receive a user licensing message.

Error Description: When a form opens up, the user information fields are not being auto-filled.

Error Description: There are no destination options in the "To:" field of the forms.

Error Description: The Beehive ftp forms program unexpectedly quits or displays: "Type 1 error".

Error Description: The Beehive ftp forms program displays a -192 error when you attempt to launch it.

Error Description: After the Beehive ftp forms client is done sending its files it returns the following two line error message: Command RNFR form.inc Reply 550 RNFR command failed (file/folder not found)

Error Description: The Beehive ftp forms program will only send one job correctly. The second job form overwrites the first and all of the attachments for all the jobs are lumped into one attachment folder.

Error Description: The ftp manager is not decoding or decompressing the received files, even though the Decode and uncompress checkboxes are checked in the configuration window.

Error Description : Client (manager or forms client attempts to connect to ftp server and just hangs.

Error Description: Certain forms fields, such as checkboxes always are received filled-out or checked, even thought the customer never checked the field.

Error Description: When you try and send a file in Sendfile, the file transfer window opens up and the following erroris displayed: JAVA Error NO route to host. Netscape/Mac only.

Error Description: When the Beehive ftp forms client for Mac is launched it generates the "NavigationLib not found" error.

Solution: this means that one of the ftp parameters for your ftp site is not properly configured. Check with your admin for the correct Internet name of the ftp server (or TCP/IP address), path, UserID and Password. Also remember that ftp is case sensitive. The "unable to connect to ftp server" error usually means that either the TCP/IP connection to the Internet is faulty or the "server name" (usually the site domain name or the TCP/IP address of ftp server) is incorrect. When the "Command: MKD XXXXXX.com" fails, it means that the userID and password does not provide write access, i.e. the Beehive ftp forms client cannot create the directory for the job on the destination ftp server. Beehive ftp forms will typically not work with anonymous ftp rights because this typically only provides read and retrieve privileges. The "FTP log on error" is obvious, check that you have the ftp connection parameters entered correctly, especially the UserID and password.

When you click on the "Send" button the job is not sent and you receive a user licensing message.

Solution: this means that the serial number entered in the User Setup Window is invalid; contact your administrator and receive a valid number.

Solution: the administrator probably did not set up the forms template correctly. The template must contain the correct field names in all caps in the form fields to enable auto-fill.

Solution: the administrator probably did not distribute a secure key for the destination site in the installer archive. Contact the administrator to obtain a secure key file or create a non-secure key with the client.

Solution: the administrator probably did not distribute a form in the forms template folder of the installer. Contact the administrator to obtain the form(s). OR in some cases where the client was downloaded from the Internet, the forms may have been corrupted by Stuffit Expander. If the Stuffit Expander preferences are set to convert all text files to Mac text format, this error may occur. Turning off this text conversion in the Epander preferences will fix this problem. Version 2.4 of the client works around this problem by allowing the Beehive client to read the forms even if they were converted to a new format by the Expander.

Solution: This typically indicates that a memory error has occurred. This error will usually disappear after more memory is allocated to the application and the computer is restarted. Highlight the Beehive ftp forms application and then select File/Get Info from the menu bar. Adding an extra 512K to the preferred memory is probably sufficient. Restart.

The Beehive ftp forms program displays a -192 error when you attempt to launch it.

Solution: This error is displayed when PPC code is launched on a 68K (030/040) machine. Obtain the 68K version of Beehive ftp forms from your administrator.

After the Beehive ftp forms client is done sending its files it returns the following two line error message: Command RNFR form.inc Reply 550 RNFR command failed (file/folder not found)

Solution: This error is caused by a redundancy between the MacBinary operations of the ftp server and the MacBinary conversion performed by the Beehive ftp client. Some ftp servers (principally MacOS based) will automatically perform a MacBinary conversion and they may also give the file a temporary name to indicate that the file is MacBinary. This renaming will confuse the Beehive client, causing the file/folder not found error. Just turn off the auto-MacBinary function on the ftp server and the problem will go away. Version 2.4 of the client will perform this special handling automatically, without turning off Macbinary on the server.

The Beehive ftp forms program will only send one job correctly. The second job form overwrites the first and all of the attachments for all the jobs are lumped into one attachment folder.

Solution: This error is caused by the ftp server returning a non-UNIX ftp listing. When the Beehive client requests information from the server, it receives a file listing - the Internet standard for this listing is UNIX but some NT based servers return a Microsoft NT listing as their default. There are two solutions to this problem

The ftp manager is not decoding or decompressing the received files, even though the Decode and uncompress checkboxes are checked in the configuration window.

Solution: Both of these errors could occur in versions of the Beehive ftp manager and Beehive ftp forms on the Mac prior to v2.72. Upgrading to version 3.0 of the Manager and the client will fix this problem. The Mac client must rename certain file name characters when files are stored on the server. The file name buffer was not large enough to store files with lots of illegal characters and the file names were sometimes corrupted.

Solution: Sometimes the Ftp manager's preferences files may become corrupted and must be trashed and reconfigured. Go into the preferences folder and trash the Beehive ftp manager preferences, all versions and then restart the computer. Run the ftp manager application and open the configuration window from the "ftp-manager" menu item. Also be sure to reconfigure the connection window.

Client (manager or forms client attempts to connect to ftp server and just hangs.

Solution : this often indicates that there is a proxy server setup that is intercepting the ftp port (21). The site key usually must be reconfigured to support the proxy server. Firewalls/proxy servers typically strip off the parameters for the remote ftp server and pass them only if the login parameters to the proxy server were correct. Logging into a remote ftp server through a firewall is done with a composite UserID and Password.

Before you can configure this setup you must get the following parameters from your firewall administrator:

Server = proxy-ip
userid = ftplogin@proxylogin@ftp-site-ip
password = ftppasswd@proxypasswd

Certain forms fields, such as checkboxes always are received filled-out or checked, even thought the customer never checked the field.

Solution : the editable fields in the form are probablly not unique. Every editable field must have its own unique name to display its data correctly.

Solution: -43 errors usually indicate that a "destination directory" is not available for the ftp manager to write incoming files. Sometimes a network drive may be unavailable or the selected drive may be corrupt. Just confirm the destination path in the ftp manager configuration window and ensure that a destination is chosen AND available

When you try and send a file in Sendfile, the file transfer window opens up and the following error is displayed: JAVA Error NO route to host. Netscape/Mac only.

Solution: PASV mode ftp transfers typically don't work with environments that have firewalls. Netscape for the Mac unfortunately will ONLY support PASV (passive mode) transfers. When the NO route to host error occurs, the firewall is intercepting the ftp connection and the JAVA client errors. The only solution is to have the administrator drop the ftp firewall to enable the passive mode connection.

When the Beehive ftp forms client for Mac is launched it generates the "NavigationLib not found" error.

Solution: When the Beehive Mac client was updated for Carbon (MacOS X) in version 3.0, several new features were implemented that require the NavigationLib to be installed. In MacOS 8.6 and above, this library is automatically included on the system. If you are running Mac OS 8.1 - 8.5, you can add the library and still use Beehive version 3.0. If you are running Mac OS version 8.0 or earlier, you must run Beehive version 2.7 or earlier.

Beehive was designed to eliminate a number of typical ftp file transfer problems experienced by users. If a problem occurs, it usually means that something is improperly configured in the ftp site setup. To test the connection, just launch the Beehive client and open the Site window from the SendFile menu. Select the site you want to test by highlighting it in the list. Now select "Edit site", this will open a window which contains a "Test" button that can check if the connection is properly setup. If the connection is OK a dialog box will return a "No error" message. If an error dialog occurs, then you must fix the site setup, then save and test again:

Error Descriptions

Error Description: When you click on the "Test" button in the Site setup window, you get a connection error message.

Error Description: When you click on the "Send" button the job is not sent and you receive a user licensing message.

Error Description: When a form opens up, the user information fields are not being auto-filled.

Error Description: There are no destination options in the "To:" field of the forms.

Error Description: There are no custom forms, destination site keys, serial number or custom splash screen.

Error Description: The installshield program progresses to 44% during installation but then hangs.

When you click on the "Test" button in the FTP site setup window, you get a connection error message.

When you click on the "Send" button the job is not sent andyou receive a user licensing message.

Solution: this means that the serial number entered in the User Setup Window is invalid or missing; contact your administrator and receive a valid number. This may also indicate that the user did not "launch" the application as the last part of the installation procedure (only required in versions prior to v2.5).

Solution: the administrator probably did not distribute a secure key for the destination site in the installer archive. Contact the administrator to obtain this file.

There are no custom forms, destination site keys, serial number or custom splash screen.

Solution: the administrator may not have added the custom form in the forms template folder of the installer, the site key into the keys folder, and the serial number and splash.bmp file into the root of the installer directory. However, more than likely, this error was caused when the user did not select the "launch" checkbox at the end of the installation. Launching the application finishes the installation by loading all of the customizations including forms, site keys, serial number and splash screen. Reinstall and check "launch" button.

The Beehive ftp forms program will only send one job correctly. The second job form overwrites the first and all of the attachments for all the jobs are lumped into one attachment folder.

2: ensure that the Beehive ftp forms client is version 2.3.1 or later and that the Beehive ftp manager is version 2.4.1 or later. All versions after these support NT and UNIX listing types.

The installshield program progresses to 44% during installation but then hangs

Solution: The "Installshield" program does not like having other applications and processes running when it is running. Restart the machine, ensure no applications are running, and re-run the Beehive installer. This only occurs in Beehive versions 2.3 or earlier, an upgrade to version 2.4 will eliminate this problem.

Solution: the administrator probably did not set up the forms template correctly. The template must contain the correct field names in all caps in the form fields to enable auto-fill.

Error Description: When attempting to use the Sendfile.NET application the user gets the error: "Class not found"

Error Description: When you try and send a file in Sendfile, the file transfer window opens up and the following error is displayed: JAVA Error NO route to host. Netscape/Mac only.

Solution: This may occur if the user rejected any of the digital certificates when the dialog boxes popped up. If you click "No" to accepting the digital certificates the first time you use the application, you have not authorized certain classes in the application to operate. Login as a new user and Grant all rights requested.

When you try and send a file in Sendfile, the file transfer window opens up and the following error is displayed: JAVA Error NO route to host. Netscape/Mac only.

Error Description: The ftp manager does not seem to be deleting the job files from the ftp server after they are processed and the job is being processed over and over again with every polling cycle.

Error Description: The ftp manager does not allow me to log onto the ftp server even though all my parameters are correct. It gives me an error of "Check your TCP/IP settings"

Solution: The solution to this is to click off the Passive Mode Transfer check box in the connection setup window on the ftp manager. Some ftp servers do not allow passive mode transfers and you are blocked from entering the ftp site because you are trying to log onto the server using this configuration.

return to top

Solution: This usually means that the ftp account (userID and password) assigned to Beehive does not have sufficient permissions to delete files from the ftp server. Contact your ftp administrator and have "delete" permissions added to the account.

Return to Top