I have installed dbman and when I go to the URL
http://ah.web2dave/cgi-bin/dbman/db.cgi
I get both the login screen and the following msg:
DBMan encountered an internal error.
CGI ERROR
=====================================Error Message : Debug Information
Script Location : /home/davln/public_html/ah/cgi-bin/dbman/db.cgi
Perl Version : 5.006001
Setup File : default.cfg
Form Variables
-------------------------------------------
Environment Variables
-------------------------------------------
DOCUMENT_ROOT : /home/davln/public_html/ah
GATEWAY_INTERFACE : CGI/1.1
HTTP_ACCEPT : */*
HTTP_ACCEPT_ENCODING: gzip, deflate
HTTP_ACCEPT_LANGUAGE: en-us
HTTP_CONNECTION : Keep-Alive
HTTP_COOKIE : cprelogin=yes
HTTP_HOST : ah.web2dave.com
HTTP_USER_AGENT : Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)
PATH : /sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin:/usr/local/bin
QUERY_STRING :
I have looked through a _lot_ of posts in the forum
and have not found one with this exact situation.
I can't tell what is wrong, based on the debug msg.
Is there a resource available for figuring out what
to do when this debug msg is displayed?
http://ah.web2dave/cgi-bin/dbman/db.cgi
I get both the login screen and the following msg:
DBMan encountered an internal error.
CGI ERROR
=====================================Error Message : Debug Information
Script Location : /home/davln/public_html/ah/cgi-bin/dbman/db.cgi
Perl Version : 5.006001
Setup File : default.cfg
Form Variables
-------------------------------------------
Environment Variables
-------------------------------------------
DOCUMENT_ROOT : /home/davln/public_html/ah
GATEWAY_INTERFACE : CGI/1.1
HTTP_ACCEPT : */*
HTTP_ACCEPT_ENCODING: gzip, deflate
HTTP_ACCEPT_LANGUAGE: en-us
HTTP_CONNECTION : Keep-Alive
HTTP_COOKIE : cprelogin=yes
HTTP_HOST : ah.web2dave.com
HTTP_USER_AGENT : Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)
PATH : /sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin:/usr/local/bin
QUERY_STRING :
I have looked through a _lot_ of posts in the forum
and have not found one with this exact situation.
I can't tell what is wrong, based on the debug msg.
Is there a resource available for figuring out what
to do when this debug msg is displayed?