Initdb Failed during the windows 2000 installation

Ashar,

I typed a "quick reply" but it left the thread, so I'm reposting here.

I ran the 8.3 install both ways and got the same results. Passwords. Is the ENtpriseDB installer incompatible with Windows 2003 strong passwords?

Bill

Ashar,

I typed a "quick reply" but it left the thread, so I'm reposting here.

I ran the 8.3 install both ways and got the same results. Passwords. Is the ENtpriseDB installer incompatible with Windows 2003 strong passwords?

Bill

Bill,

Windows 2003 strong passwords shouldn't cause a problem as long as the password you set for the 'enterprisedb' user complies to the strong passwords policy.

Ashaar

Bill,

Can you also try this installer on a windows xp machine?

Thanks

Ashaar,

I actually tried the XP install last night before seeing this message from you, so we're on the same page! The XP install worked without any issues. I used the command line option and it worked fine. I used the exact same install set that I have been using for the Windows 2003 Server install.

While this is a step forward, it is imperative that I host the database on a Server asset. So, here are some particulars regarding the install so far.

1) I am running the Win2003 Server as the Primary Domain Controller in my lab. My intent is to run this system in an environment isolated from the rest of the company's network (except for Internet access). Not sure if this makes any difference, but thought I'd add the information.

2) When I look at the account that EDB is setting up in AD, I've noticed that, in the "Log on as a service" section of the "Domain Security Settings" panel, an account is referenced as "*S-1-5-21-998401285-416900288-3195713710-1122" as part of the EDB set up. Nothing is established in the "Domain Controller Security Settings" panel. Should not this service reference the "entepriseDB" lggon instead?

3) When running the install directly from windows, I get:

initdb_stderr.txt

The program "edb-postgres" is needed by initdb but was not found in the
same directory as "C:/EnterpriseDB/8.2/dbserver/bin/initdb".
Check your installation.

initout.txt

Adjusting rights for current user to impersonate(required for Windows 2000 based systems)...
Granting SeTcbPrivilege to BSITERPSERVER\Administrator ... successful
Calling initdb as user enterprisedb...
Process Created...

The command completed successfully.

Done!

Then, is stops, with the 1332 diaglog as the final output.These are somewhat different than when run from the commandline, where the process addressed in initout fails (see previous post for details).

Anything you can do to help me out is appreciated. I am under the gun to complete the establishment of the test environment by Friday, so that the project's evaluation team can begin to review "Compiere" and I am of the opinion that using EDB is a superior choice to Oracle.

Thanks for your help

Bill S

Hi Bill,

Please try this...

- Create the enterprisedb user manually and allow "Log on Locally" and "Log on as a service" for 'enterprisedb' user. This can be done from control panel-> Administrative Tools -> Local Security Policy
- Run the installer using -use_local_logon

Please let me know how it goes.

Thanks

Ashaar,

Well, I tried this also, but, no soap. Sorry, but I'm going to have to jump ship. I've installed the Oracle 10.g without a hitch. I am also a veteran of MS Sql, MySql, Sybase, DB2, IMS, etc. and can tell you that this issue with your installer is going to be a problem for you going forward for Windows installs. There is an obvious issue with the way you handle security/permissions in your install script that is not very intuitive in the Windows realm.

However as an open source guy, I am looking forward to demo'ing your product as a replacement for MySql in my current LAMP development environment. Your developers desktop is looks great.

Anyway, sorry, but also thanks for the help.

Bill