Error at 1.3.0.4 setup - Step 1, creating Admin account

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Proceed through step 0 which creates the database tables
2. Attempt to create admin account in step 1

What is the expected output? What do you see instead?
I expect to advance to the next step of the installation process - perhaps 
configuration of the site? Instead, I'm redirected to a error 500 page.

What version of the product are you using? On what operating system?
1.3.0.4 - powweb web hosting

Please provide any additional information below.

I was able to proceed through step 0 of the setup process without issue, but 
when I try to go through step 1, the creation of the administrator account, the 
page processes the url 
/includes/process.inc.php?section=setup&action=add&dbTable=users and then 
results to //500.php?action=error and I get the error: 

>500 Error

>Oh, hey! Apparently, there was some sort of error...

>Please use the main navigation above to get where you want to go.

>Cheers!
>The Site Server

Is this some sort of error with the process.inc.php file?

How can I manually create a use in phpMyAdmin? 

Thanks

Original issue reported on code.google.com by inam...@gmail.com on 18 Feb 2014 at 1:54

Attachments:

• page1.jpg
• page2.jpg

[GoogleCodeExporter]

FYI, I had this same type of error.  I wasn't getting the "500 Error", the page 
was just refreshing and not adding the user or proceeding.  I validated all of 
my install steps according to the documentation, but then I started 
experimenting with settings.  Here's the fix I used to get it to work for me:

1.  Edit your config.php file.
2.  At the bottom where the $base_url variable is listed, type in your full 
site URL here.

I think my issue is partially because I haven't transferred my domain name yet, 
so the site I was using still lists my page as 
"http://ipaddress/~useraccount/bcoem/" and it wasn't translating that very well 
into the programming.

If this sounds like your situation too, give it a try, see if it fixes it.  I 
will probably have to make adjustments when I move my domain name, but I will 
just tackle one issue at a time :)

Original comment by mike.pem...@gmail.com on 4 Nov 2014 at 3:18