Return To The uReserve Reference Site


You are viewing the legacy uReserve website. Click here to visit the latest version.




  1. For Absolute Beginners
  2. Server Error
  3. Script Is Displayed, Not Executed
  4. Script Is Being Downloaded, Not Executed
  5. "Unable to open resource-data.txt" Error
  6. General "Unable to open" Errors
  7. E-mail Not Sent to Admin/User Does Not Receive E-mail
  8. New Reservations Not Appearing On HTML Pages


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 reference site:

http://www.uburst.com/uReserve/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 the uReserve script that much easier.



2. Server Error

Upon installing the script on your server, the first thing you should do is use your browser to test the script going to the URL of the script on your server. Upon doing so, you should get the "uReserve Copyright Page" similar to when you go to the URL of the script on our site:

http://www.uburst.com/cgi-bin/ureserve/ureserve.pl

... if this is the first time you are running uReserve. Or if you have already been running uReserve on your server before, then you should just see the online schedule pages similar to when you go to the URL of the demo script on our site:

http://www.uburst.com/cgi-bin/ureserve/ureserve1.pl

If when going to the URL of the script on your server you get a "Server Error" instead, 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. 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. (Deluxe Edition Only) The script can not find the ureserve-languages.pl file.
    Make sure the ureserve-languages.pl script is in your cgi directory. On Windows servers, you might need to modify your answer to configuration question #12 such that it refers to the full path to the cgi directory. For example, on a Windows server, the answer to configuration question #12 might need to be modified to be something like this:

    require "c:/Inetpub/wwwroot/cgi-bin/ureserve-languages.pl"; # DO NOT MODIFY

    Second, after making the above modification, if you still get a server error, try specifying the path to perl on the very first line of the ureserve-languages.pl script, just as you did for your ureserve.pl script.

    As a last resort, the ureserve-languages file might need to be put into the perl\lib subdirectory.

3. Script Is Displayed, Not Executed

Upon installing the script on your server, the first thing you should do is use your browser to test the script going to the URL of the script on your server. Upon doing so, you should get the "uReserve Copyright Page" similar to when you go to the URL of the script on our site:

http://www.uburst.com/cgi-bin/ureserve/ureserve.pl

... if this is the first time you are running uReserve. Or if you have already been running uReserve on your server before, then you should just see the online schedule pages similar to when you go to the URL of the demo script on our site:

http://www.uburst.com/cgi-bin/ureserve/ureserve1.pl

If when going to the URL of the script on your server, the script is displayed instead of being executed, 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.


4. Script Is Being Downloaded, Not Executed

Upon installing the script on your server, the first thing you should do is use your browser to test the script going to the URL of the script on your server. Upon doing so, you should get the "uReserve Copyright Page" similar to when you go to the URL of the script on our site:

http://www.uburst.com/cgi-bin/ureserve/ureserve.pl

... if this is the first time you are running uReserve. Or if you have already been running uReserve on your server before, then you should just see the online schedule pages similar to when you go to the URL of the demo script on our site:

http://www.uburst.com/cgi-bin/ureserve/ureserve1.pl

If when going to the URL of the script on your server, the script tries to be downloaded instead of being executed, 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 open resource-data.txt" Error

The first time you "Add" a resource with uReserve, uReserve will create a resource data file called "resource-data.txt" in your "data" directory. If instead of creating this file, you get an "Unable to open resource-data.txt" Error, then the problem is usually one of two things:

  1. The path to your data directory is incorrect.
    That is, the directory path that you configured in question #6 of the script setup is not correct. Double-check the value of this setting or if possible, try using the Full Directory Path to your "data" directory instead of just a relative directory path. An example full path might be something like:

    $data_directory = "/www/youraccount/cgi-bin/data/";

    ...on UNIX servers, or perhaps something like this:

    $data_directory = "C:/users/youraccount/cgi-bin/data/";

    ....on NT servers.

    Note that this is a directory path...not a URL. So it won't start with "http". If you don't know the full path to your cgi-bin directory, then ask your web hosting provider.

  2. Your "data" directory does not have read/write/execute permissions.
    Try giving the directory full READ/WRITE permissions. On UNIX servers, this can be done via a chmod 777. On NT servers, you may have to contact your web hosting provider to make sure your "data" directory has READ/WRITE permissions.

    NOTE: On a Solaris/Unix Netscape webserver, the "data" directory should be owned by the Netscape server user.


6. General "Unable to open" Errors

"Unable to open " Errors, are usually caused by one of two things:

  1. The path to your "data" directory is incorrect.
    That is, the directory path that you configured in question #6 of the script setup is not correct. Double-check the value of this setting or if possible, try using the Full Directory Path to your "data" directory instead of just a relative directory path. An example full path might be something like:

    $data_directory = "/www/youraccount/cgi-bin/data/";

    ...on UNIX servers, or perhaps something like this:

    $data_directory = "C:/users/youraccount/cgi-bin/data/";

    ....on NT servers.

    Note that this is a directory path...not a URL. So it won't start with "http". If you don't know the full path to your cgi-bin directory, then ask your web hosting provider.

  2. Your "data" directory does not have read/write/execute permissions.
    Try giving the directory full READ/WRITE permissions. On UNIX servers, this can be done via a chmod 777. On NT servers, you may have to contact your web hosting provider to make sure your "data" directory has READ/WRITE permissions.

    NOTE: On a Solaris/Unix Netscape webserver, the "data" directory should be owned by the Netscape server user.


7. E-mail Not Sent to Admin/User Does Not Receive E-mail

E-mail errors are usually caused by one of two things:

  1. If you are using "SENDMAIL", the path you specified to the sendmail program on your server is wrong.
    Contact your web host to verify the correct path to sendmail.

  2. If you are using "SOCKETS", the SMTP server or IP that you specified is wrong.
    Contact your web host to verify your SMTP server name or IP.

All users: The reservee will not receive an e-mail reservation receipt if "E-mail User" is set to "NO" (from Main Control Panel-->General Settings-->E-mail Settings) or if the e-mail entered at the time of the reservation is invalid.

Sendmail users:After you verify that you have specified the correct sendmail path, if notification emails are still not sent, make sure you have at least specified a valid Primary Admin E-mail or a valid Secondary Admin E-mail. If you don't want a notification sent to either a primary or secondary admin, then you might need to hardcode a valid "sendfrom" address into the script in order for sendmail to successfully send a user the reservation receipt. This is based on your sendmail configuration. Contact support@uburst.com for instructions on where to make this change in the script.

Sockets users: We can send you a simple test script to verify that your Windows server can successfully send e-mail via a CGI script using sockets. Send your request for this script to support@uburst.com.



8. New Reservations Not Appearing On HTML Pages

If after adding/updating a reservation with uReserveTM, you don't see the reservation when you view the online schedule, the problem may be that your browser is just displaying an older version of the pages saved in cache. Try pressing "RELOAD" or "REFRESH" on your browser in order to make your browser reload the latest pages.


----------

  • If you didn't find a solution to your problem here, don't forget about our Support Forum.

  • And if that still doesn't solve your problem, visit our support page for other ways to get technical support .