Return To The uSignIn Reference Site


1. For Absolute Beginners

If you've never installed or executed any Perl scripts on your server before, it is recommended that you first try installing our basic test script as described at our uStorekeeper reference site:

http://www.uburst.com/uStorekeeper/testscript.html

This simple Perl script is the most basic of Perl scripts and should help you to understand how to install and execute scripts on your server. It also will verify that your web hosting account is configured properly to run Perl scripts and will make installing and running scripts that much easier.



2. Server Error

If when going to the uSignInTM URL you get a "Server Error", then the problem is usually one of four things:

  1. The path to Perl is incorrect.
    The Path to perl is specified as the very first line of the CGI scripts. Typical values are /usr/bin/perl, /usr/local/bin/perl/ and /bin/perl. If you do not know what the path to perl is on your server, then you can ask your web hosting provider or system administrator. NOTE: When specifying this path to perl, you must include the "#!" in front of the path. Example: #!/usr/bin/perl

  2. The file was transferred in BINARY mode (as opposed to ASCII or TEXT mode).
    When transferring the CGI script to your server, you must transfer it in ASCII or TEXT mode - as opposed to BINARY mode. Your FTP program should give you an option to do this - so be sure to transfer the CGI script in ASCII or TEXT mode.

  3. The script does not have execute permissions.
    Once the CGI script is transferred to your CGI directory on your server, you must change the permissions to READ and EXECUTE (chmod 755). If your server is a UNIX server, you should be able to change the file's permissions via your FTP program. If your server is an NT server, then you may have to get your web hosting provider to make the file executable.

  4. The directory the script is installed in is not configured to execute scripts.
    Make sure that if you created a subdirectory of cgi-bin to install uSignIn into, that your server is configured to run scripts from that directory and that the directory is readable, writable and executable (mode 755 on unix servers is normally ok).



3. Script Is Displayed, Not Executed

If when going to the uSignInTM URL your server displays the script instead of actually executing it, then the problem is usually one of three things:

  1. The CGI script does not have the correct file extension for your server.
    That is, some servers are configured to only execute scripts that end in .pl and others are configured to only execute scripts that end in .cgi. Check with your web hosting server and rename the file if necessary. Also, if you have to rename the script, change the URL in question #2 of the script as well.

  2. The directory that you put the script is not configured to execute CGI scripts.
    That is, usually your web hosting service will have to make a special directory for you to put your cgi scripts in such as cgi-bin or cgi-local. Again you can check with your web hosting provider.

  3. The permissions on the script itself are not correct.
    That is, you must make sure the script has read and execute permissions. This can be done with your FTP program on UNIX machines (chmod 755). People using NT servers, may have to get their web hosting service to change the permissions to executable for them.



4. Script Is Being Downloaded, Not Executed

If when going to the uSignInTM URL your browser tries to download the script instead of actually executing it, then the problem is usually one of three things:

  1. The CGI script does not have the correct file extension for your server.
    That is, some servers are configured to only execute scripts that end in .pl and others are configured to only execute scripts that end in .cgi. Check with your web hosting server and rename the file if necessary.

  2. The directory that you put the script is not configured to execute CGI scripts.
    That is, usually your web hosting service will have to make a special directory for you to put your cgi scripts in such as cgi-bin or cgi-local. Again you can check with your web hosting provider.

  3. The permissions on the script itself are not correct.
    That is, you must make sure the script has read and execute permissions. This can be done with your FTP program on UNIX machines (chmod 755). People using NT servers, may have to get their web hosting service to change the permissions to executable for them.



5. "Unable to create/open main usignin csv OR unable to create/open message csv

The first time you access uSignInTM the script will attempt to create the necessary database files. If you get an "Unable to create csv" Error , then the problem is generally one of these two things:

  1. The directory usignin.cgi is installed in does not have the correct permissions.
    That is, the directory is not writable by the web server and the script cannot create the required csv files. Make sure the directory is at least mode 755 on unix machines. To TEST the problem, you can change the mode of the directory to 777 on unix machines. On NT machines, you may have to contact your system administrator or your web hosting provider.

  2. On NT machines, the script is trying to create the csv files in a directory other than the one uSignIn is installed in.
    We have seen on occasion incorrect configuration of an NT machine will cause cgi scripts to create files in the /wwwroot or /wwwroot/inetpub directories. If this happens, you can check with your administrator or hosting provider to try to solve the problem. Or you can change question #11 to use the FULL PATH to your scripts directory instead of the relative file name.


    ----------

    Here are some other places that you can look for assistance: