I've installed DBMan a few times before, and even have a test copy running somewhere now.
The problem is on the new installation (same host)
I keep getting "DBMan encountered an internal error. Please enable debugging to view." then no matter if I turn on Debug or not, I get the same error message.

I've tried a new installation in a sub-folder, as werll as copying my other running version into this folder and then changing the paths.

I'm dying over here, please help
-Jim

One thing you can try is moving :

$db_debug = 0;

to above the section in your .cfg file:

# File and URL's

this will help to catch errors within the .cfg file.

Also you might want to view the source code of the error page as it sometimes will display if there is a missing sub it's looking for.

Another thing I use when I can't get error messages from a host's server is to use this snippet of code in the top of my files:

#!/usr/bin/perl
BEGIN {
open (STDERR, ">/fullserverpath/error.txt");
}

changing fullserverpath to the path (not url) to where a new file called error.txt has been uploaded to your server. This should be in your root directory and not within the cgi-bin directory.

If those tips don't help you to locate the error, perhaps you could make a .txt copy of your .cfg and html.pl and provide a url to where they can be viewed so we can see if we can spot any problems which may be causing your error message.

Unoffical DBMan FAQ

http://creativecomputingweb.com/dbman/index.shtml/

It does not seem to be reaching the default.cfg file.

I ties moving the DEBUG up to the top, but it makes no difference.

Now get this.
I have a full copy at www.amaprostar.com/store/db.cgi

It runs fine.
I copied the files, and moved them to
www.amaprostar.com/dbman/db.cgi

I changed the URL line in the cfg.

The program has the same error I get elsewhere.

The good running version still runs like a clock.

NOTE.
On the good running version, I needed to change the extentions of the auth.pl and html.pl files both to .cgi. Don't ask why, but it works that way.
I had to alter the code and cfg to permit this.

-Jim
'

The only other thing i can think of is that the permissions were not set correctly on the files, that they weren't uploaded in ASCII mode. or perhaps you forgot to also copy the /auth directory into the new /dbman directory?

Unoffical DBMan FAQ

http://creativecomputingweb.com/dbman/index.shtml/

Keep in mind that this is a Windows server, running at least Windows Server 2002.
It is obvious that db.cgi does not see the .cfg file.

What is the binary code here? (from db.cgi) And why do I not see default.cfg anywhere in it?

CODE SNIPPED FROM DB.CGI

# Load the form information and set the config file and userid.
local(%in) = &parse_form;
$in{'db'} ? ($db_setup = $in{'db'}) : ($db_setup = 'default');
$in{'uid'} ? ($db_uid = $in{'uid'}): ($db_uid = '');
# Required Librariers
# --------------------------------------------------------
# Make sure we are using perl 5.003, load the config file, and load the auth file.
eval {
unshift (@INC, $db_script_path);
require 5.003; # We need at least Perl 5.003
unless ($db_setup =~ /^[A-Za-z0-9]+$/) { die "Invalid config file name: $db_setup"; }
require "$db_setup.cfg"; # Database Definition File
require "auth.pl"; # Authorization Routines

Do you need to change this line:

require "auth.pl"; # Authorization Routines

to

require "auth.cgi"; # Authorization Routines

?

already changed those lines
-jim

Hmm... one last shot: Did you change the name of the default.cfg file perhaps? Several times I've had to change this line of db.cgi:

$in{'db'} ? ($db_setup = $in{'db'}) : ($db_setup = 'default');

to

$in{'db'} ? ($db_setup = $in{'db'}) : ($db_setup = 'bob');

when renaming default.cfg to bob.cfg (for example).

Others have not had to do this, but I have had to.