Welcome, Guest. Please login or register.
Did you miss your activation email?


Login with username, password and session length

Search

 
Advanced search

8043 Posts in 1856 Topics- by 2099 Members - Latest Member: roi
Pages: [1]   Go Down
Print
Author Topic: Internal Server Error upon upgrade?  (Read 512 times)
0 Members and 1 Guest are viewing this topic.
OperaDivaMommy
New Member
*

Karma: 0
Offline Offline

Posts: 0

mommy, opera singer, violinist, website designer


WWW
« on: August 12, 2004, 06:36:00 PM »

Hi there,
Am trying to accomplish the upgrade right now (thought I had a few more hours but my host went in and disabled it earlier today already).  We'd customized the script - I *thought* was primarily through templates though, but I could be wrong - it was awhile ago now (over a year).  But after I checked all the permissions I went to the page on my site and am just getting an internal server error.

Got any thoughts?  I could really use some help here.  My clients website is primarily visited for her calendar!

All the best,
Laura Ruiz

Logged

Laura Ruiz
http://www.increDesign.com

==========
This will be our reply to violence:
 To make music more intensely,
 more beautifully,
 more devotedly than ever before.
    -Leonard Bernstein
==========

DanO
Moderator
Full Member
*****

Karma: 13
Offline Offline

Posts: 230

Please don't PM me. Post in the open forum.


WWW
« Reply #1 on: August 12, 2004, 07:09:00 PM »

An "Internal Server Error" error message is just a general error message saying something went wrong but says nothing about what. It could be anything from incorrect file or directory permissions to file(s) being uploaded in binary instead of ascii mode or an actual coding problem.

Check your server error logs to see if a more detailed error message was recorded or if you have shell access (telnet, SSH, etc.) try running the script from there to see what error(s) Perl reports.

Once you find a more detailed error message, if you can't figure out the problem, post that error message and we'll see what we can suggest.

Dan O.

------------------

Logged
OperaDivaMommy
New Member
*

Karma: 0
Offline Offline

Posts: 0

mommy, opera singer, violinist, website designer


WWW
« Reply #2 on: August 12, 2004, 07:17:00 PM »

Hmmm...don't know if this is helpful at all, not even sure if I'm looking at the right thing.  But it seems that my error log says the following:

[sh: /usr/bin/date: No such file or directory]

Does that sound right at all?

Laura

------------------
Laura Ruiz
http://www.increDesign.com

==========
This will be our reply to violence:
 To make music more intensely,
 more beautifully,
 more devotedly than ever before.
    -Leonard Bernstein
==========

Logged

Laura Ruiz
http://www.increDesign.com

==========
This will be our reply to violence:
 To make music more intensely,
 more beautifully,
 more devotedly than ever before.
    -Leonard Bernstein
==========

DanO
Moderator
Full Member
*****

Karma: 13
Offline Offline

Posts: 230

Please don't PM me. Post in the open forum.


WWW
« Reply #3 on: August 12, 2004, 08:32:00 PM »

I'm afraid I have no idea if that message pertains to CalendarScript or not. Maybe your host can help getting it back up and running or at least determine the cause of the current problem??

Dan O.

------------------

Logged
Dr. Cardio
Guest
« Reply #4 on: August 12, 2004, 10:18:00 PM »

Hi.  I also experienced the same dilemma as you.  After I re-visited the CHMOD issues using the WS-FTP software, I realized that my settings were correct and the paths in the calendar.pl and calendar_admin.pl files.  As I initially installed this script on 2003, I made detailed notes as the the installation.  I could not find any error in my install and I followed the install instructions that Matt K. provided to the letter.   I then decided to take another approach to the server error, and expand on my directory heirarchy.  I decided to "Recalculate the Web" using the FrontPage Server Admin services built into the software <Tools - Server - Administration Home>.  I also have a sitecontrol service that my web host provider offers (as many good web hosting companies offer) where I can perform this same operation.  
To make a long story longer, after the web recalculation, Calendarscript miraculously began functioning normally.
NOTE: I also ran the dubug.pl file and it returned an "all ok" message and that let me to research my links and structure in the web.  At any rate, I hope this helps and perhaps you will resolve your issues as I did.  

Dr. Charles McGregor
Cardiology

Logged
Armature
New Member
*

Karma: 0
Offline Offline

Posts: 0


WWW
« Reply #5 on: August 16, 2004, 05:49:00 PM »

Same thing. Server Error upon upgrade. The NEW versions of calendar.pl and calendar_admin.pl do this immediately and independently. Putting the old .pl files back make it work. Absolutely 100% replicatable.

------------------

Logged
DanO
Moderator
Full Member
*****

Karma: 13
Offline Offline

Posts: 230

Please don't PM me. Post in the open forum.


WWW
« Reply #6 on: August 16, 2004, 07:21:00 PM »

** Server Error upon upgrade. The NEW versions of calendar.pl and calendar_admin.pl do this immediately and independently. Putting the old .pl files back make it work.**

Did you maybe have the base directory variable set in the old but not the new? Maybe the file(s) got corrupted like uploaded in binary instead of ascii? Maybe the .zip archive you downloaded got corrupted? Incorrect permissions set for tham?

Just some possibilities. The files DO work.

JFYI

Dan O.


[This message has been edited by DanO (edited August 16, 2004).]

Logged
Armature
New Member
*

Karma: 0
Offline Offline

Posts: 0


WWW
« Reply #7 on: August 16, 2004, 09:42:00 PM »

Did you maybe have the base directory variable set in the old but not the new? Maybe the file(s) got corrupted like uploaded in binary instead of ascii? Maybe the .zip archive you downloaded got corrupted? Incorrect permissions set for tham?

All common causes of scripts not running. None of them true here.

However, I did download the entire program in addition to the Upgrade. I noticed that the config.txt file has a different format: one line longer and some line items are different.

Think I'll try the new-style config file....

Logged
Scott
Guest
« Reply #8 on: August 17, 2004, 12:15:00 AM »

The config file will of course be different, as your version has your preferences and other things saved.

When the upgrade fails to work properly, it is almost always one of:
1) Files uploaded incorrectly (bin instead of asc)
2) Old version has custom changes, such as base dir, which need to be made in new version
3) Files are not really in the place you think they are, ie, you're updating the wrong files (this happens way more often than you'd think   )
4) Permissions are not set correctly on files after they have been uploaded.

The debug.pl script should help, as should the server's error log. The files themselves are fine - they've been used by many hundreds of sites by now!

------------------
Scott
CalendarScript.com


Logged
Armature
New Member
*

Karma: 0
Offline Offline

Posts: 0


WWW
« Reply #9 on: August 17, 2004, 12:40:00 PM »

Actually I think it might have something to do with at item in the lib directory. A file name has changed.

The old version (3.0) contains:
require "Config.pm";

While the new version contains:
require "ConfigFile.pm";

------------------

Logged
Scott
Guest
« Reply #10 on: August 17, 2004, 12:51:00 PM »

If you're upgrading from version 3.0, then you need to apply the 3.1 patch, then the 3.2 patch, then the 3.21 patch. That would be the source of your problem.

------------------
Scott
CalendarScript.com


Logged
Armature
New Member
*

Karma: 0
Offline Offline

Posts: 0


WWW
« Reply #11 on: August 17, 2004, 01:16:00 PM »

If you're upgrading from version 3.0, then you need to apply the 3.1 patch, then the 3.2 patch, then the 3.21 patch. That would be the source of your problem.

Nah, that would be too easy!

But that's exactly what it was!

Sometimes the obvious escapes me....

Logged
DanO
Moderator
Full Member
*****

Karma: 13
Offline Offline

Posts: 230

Please don't PM me. Post in the open forum.


WWW
« Reply #12 on: August 17, 2004, 01:26:00 PM »

** If you're upgrading from version 3.0... **

It hadn't occured to me that they might be trying to upgrade from version 3.0 directly to the current version. That subject is covered in a previous forum message titled "upgrade from 3.0"

BTW Matt, have you corrected the CalendarScript321_Upgrade files recently to include the new feedback.html and messages.txt files which are needed to do a proper upgrade? The feedback.html file contains new version # and messages.txt file has an added error message.

Dan O.

------------------

Logged
Scott
Guest
« Reply #13 on: August 17, 2004, 01:38:00 PM »

I fixed the feedback file a while ago, but not the messages file yet. Been swamped with helping people upgrade, etc.

------------------
Scott
CalendarScript.com


Logged
Pages: [1]   Go Up
Print
Jump to: