As long as you are using Java 5 or later you should be fine. It is possible that the installer may not work but you can install the server from the .zip file. Having said that, could you check the log files and post the errors that you see?
In the mean time I installed Java 5, but was not able to find any zip file othet then the nightly builds. Anyways, I tried to run the installer 3.1.1 again but had the same problem as before.
The popup message: Error opening media file. Please move this file to an ascii-only path like c:\
In addition I got an error log entry in the temp dir (copy / paste)
Started executable E:\wildfire_3_1_1.exe at Fri Jan 26 19:52:18 2007
Init
ERROR: Could not open
I even tried to copy / paste the directory from my XP install to NT and by starting \bin\wildfire.exe the popup message mentioned above comes up. By clicking Okay the little screens comes up and shortly after the ‘‘Launch Admin’’ button. Hitting this brings up the browser with an connection error. Port 9090 is NOT in use from another program.
On the server I run this on, I also had an admin equivalent ID when I installed it. I’'m also running MySQL ver 5 for the backend.
I didn’‘t experiance any issues with either the install or the running of the server. I did install 3.1.1 over 2.5.1 although I don’'t think that would matter asit detected the previous version and uninstalled it first.
The JDBC driver for MySQL is bundled with Wildfire, so you do not need to download and install a separate driver.
In the Wildfire setup tool, use the following values:
driver: com.mysql.jdbc.Driver
server: jdbc:mysql://[YOUR_HOST]/[DATABASE_NAME]
where and are the actual values for you server. In many cases localhost is a suitable value for when your database is running on the same server as your webserver.
Setup Instructions
Make sure that you are using MySQL 4.1.18 or later (5.x recommended) ¹.
Create a database for the Wildfire tables:
mysqladmin create
(note: “databaseName” can be something like ‘‘wildfire’’)
Import the schema file from the resources/database directory of the installation folder:
Unix/Linux: cat wildfire_mysql.sql | mysql ;
Windows: type wildfire_mysql.sql | mysql ;
Start the Wildfire setup tool, and use the appropriate JDBC connection settings.
¹ Character fields larger than 255 are not supported by versions prior to MySQL 4.1.18. If you cannot upgrade MySQL to the latest version, you will then need to change the database scripts. In particular, replace VARCHAR(1024) with VARCHAR(255) in the resources/database/wildfire_mysql.sql script
By vanilla, I mean it’‘s just a basic install from the boot CD plus AV S/W - could it be your AV is stopping the executable ? Are you sure the EXE you have isn’'t corrupt ?
it is the same install.exe with which I could install wildfire just fine onto the NT-WS. And AV is on the machine, but not scanning.
By the way, because you mentioned it worked on NT Server, as of writing here, I am able to install it on my NT server machine at the office. The installer wizard comes up …
So, I dicided yesterday already to make a fresh install on this particular machine and will see what happens. I hope to be done tomorrow and let you know what the result is. Croos the fingers !
The installer I downloaded the first time, it installed on XP, after that I tried on NT4 Server and didn’'t work, installed without any problem on NT4 WS. All mentioned in the other posts.
Did as mentioned a clean install of the server with NT4Server + Sp6a (nothing more) tried the installer, no luck > same error message as in the previous post. Couldn’'t believe it. !
Because I did a new download and test run with my other NT4 Server in the office, I did a download again (server is at another location at the office) and this time it went “like a piece of cake”
Any ideas ? Any clues ? I guess, a new downlaod would have done it, no need to makle e fresh install of the OS. For next time I know what to do. The question still remains: What can cause this odd behavior ? I can’'t think that the files for download are changed in between, or do they ?