We are having similar problems, we upgraded from version 2.2 to 2.3
everything works fine except manage.cgi giving the 500 server error.
Sven van Heerden
SnAkebrothers Web Enterprise
>From: WTrachtman To: [EMAIL PROTECTED] Subject: Manage.cgi Script
>failure following Full Access authorization Date: Tue, 09 Jan 2001 19:17:21
>-0500
>
>
>I am a new OpenSRS RSP, who just installed and successfully ran both the
>reg_system.cgi and manage.cgi scripts well enough to execute and pass the
>"full access" test on Sunday. Shortly following the submission of the test
>results, about the same time as I received the "Full Access Complete"
>message from the folks at "Team OpenSRS", the manage.cgi script has stopped
>working properly. The "reg_system" script still works just fine, but the
>"manage.cgi" script gives a "500-server error" if and only if the correct
>domain name, userID and Password are supplied for domains successfully
>registered in the test-server environment. If any of these three items are
>entered incorrectly, the manage script gives the proper error message
>rather than the 500-server error. Because this is a virtually hosted
>account installation, I can't access the system error logs, so it is
>difficult to get complete error message info. Setting the "debug" flag to 1
>for the manage script in the config file does not seem to have any effect.
>Otherwise redirecting error output to the browser gives a large list of
>errors similar to :
>
>Undefined value assigned to typeglob at /mydirectory/lib/cgi-lib.pl line
>57.
>
>and
>
>/mydirectory/lib/OpenSRS/XML_Client.pm line 795, line 1.
>
>FYI, I am using the new version 2.3 client script package.
>
>Although I have created a new "private-key", both in the "live" and "test"
>environments, this does not seem to cure the problem. Everything was
>working just fine on Sunday prior to my OpenSRS account status changing
>from "TEST" to "LIVE" (terminology per the congratulation message from
>Opensrs).
>
>I am still pointing to, and using, the test system, since I want to get
>this resolved prior to really going "live".
>
>Is there anything special associated with the passing of the "full access"
>test and changing to "live" status at the OpenSRS side which might be
>causing the problem with the manage.cgi script? I am in the process of
>trying to "reverse-engineer" the manage.cgi and related scripts to see what
>may be causing the problem, but if there is something simple I am
>overlooking, I would appreciate any pointers.
>
>If the IP address for the server access (which is one of the things
>presumably added when going "live") were incorrect, would this not simply
>give an authorization failure, or other error message rather than the
>500-server error? Is this parameter even used in the test-system
>environment?
>
>Is there anything simple which I am supposed to reconfigure once I have
>been approved for full access which would make the manage.cgi script stop
>functioning while the reg_system.cgi script continues to work just fine?
>
>I did review the message list archives, and it seems that others are having
>difficulties with the manage.cgi script, but I saw no resolutions posted.
>
>Any insights from those who may already have gone through this would be
>greatly appreciated.
>
>Thanks in advance for any help. Warren Trachtman http://www.wstco.com
>[EMAIL PROTECTED]
>
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
