Hi,

I have a Windows 2003 server with SQL Server 2005, Postgres 8.3 and MySQL 5.0 installed.

I turned off the Postgres service and tried to install Mingle. the wizard ran but there had been no Web site created at all.

the logs show these errors:

2008-08-05 19:30:21,906 [/] Could not reconnect because there is no C:/Documents and Settings/kjohnson/Mingle/config/database.yml file

2008-08-05 19:30:21,906 [/] Need install: could not connect to database: ActiveRecord::ConnectionNotEstablished

any ideas?

Thanks,

Kimball Johnson

Hello Kimball. Did you start your browser and point it to http://localhost:8080? On Windows, wait a minute or two after the installer finishes installing, and then point your browser to that URL. You will then be taken through the installer steps which will create the required configuration files based on the information you enter.

You can find more information on installing Mingle here on the help page -> http://studios.thoughtworks.com/mingle/2.0.1/help/installing_mingle.html

You will need to have your database service running, before you start the configuration steps. So it would be a good idea to start your database service of choice, and then proceed with the configuration steps in Mingle.

Badri, thank you for your reply.

I tried a number of different installation scenarios, all with the same results.

However then I looked at the IIS log – saw nothing.

Then the IE7 settinings for intranet and proxy – saw nothing.

Then I turned off Windows Firewall and tried the page again. – the wizard came up immediately.

Then I turned windows firewall on again and tried the page yet again – it came up ok again.

So whatever mingle is doing doesn’t seem to involve IIS at all.

And the first time the page opened it looks like it completed whatever configuration was necessary. Now there is a config file in the ‘data base’ folder with the three .yml files.

Therefore, the step after installation where you open the web wizard page for the first time must be performed with Windows Firewall (any firewall) open or at least open to the necessary port (8080?).

Now I need to understand how to point a DNS entry at that port???

Thanks again,

Kimball

Hello Kimball – thanks for your detailed response. Firstly, in order to eliminate variables, I would like to mention that Mingle does not use IIS in any form. Mingle ships with an embedded web-server, which listens by default, on port 8080, or if that is not available, the first available port after 8080.

This does mean that if you have a firewall turned on, either port 8080 (by default) or the port that your Mingle server is running at would need to be open for access over the appropriate protocol (http by default).

Also, the machine name for a web server running on your machine would be dependent on your network. You can contact your network administrator to find out how to access the machine on which the Mingle server is running. If the port on which Mingle is listening is open – you can access the Mingle instance using ip address and port till such time as you can figure out the DNS name for the machine on your network.

As regards Mingle’s configuration files being present without you having to run through the setup screens; that sounds unexpected. The person setting up Mingle must run through the configuration sequence for the three yml files to be created. I would advise you to check the contents of those files, and make sure the data in them looks fine. They are plain text files, so you should have no problems there. If they do not look correct, you can

a) stop the Mingle service
b) delete the files
c) start the Mingle service
d) point your browser at http://your_server:port/

and that should run you through the configuration pages again.

If you have any further problems, you can contact our support team.

Hope that helps.

Badri,

Thanks again for your response.

To be precise, the 3 yml files were not created until I was able to successfull access the configuration wizard web page.

To do this I had to to turn the windows firewall off (open on all ports) although perhaps I could have just opened 8080. As soon as I accessed the page I turned the firewall back on (closed on all ports – at least closed on 8080).

When I checked at this point, the yml files had been created.

After that first access, I was able to open a new browser and access the default page and config wizard as normal. The process then followed the description in the on-line installation instructions and Mingle is working fine.

And I found out how to get a DNS entry to point at the 8080 port. I’ll put that in a separate post named, “Redirecting an IIS Host Header to a Mingle installation port’.

Thanks,

Kimball