Steve - these loook OK to me.  Regards, Tim G

Steve - my guess is that Tomcat is not running and my second guess is that there is a a 32/64 bit problem and my third guess is that it is my fault.

Step 1 - go to Control Panel then Administrative Tools then Services - you should find Apache Tomcat and look at the Status column - it should show Started as below

If it does say Started then I am wrong about what is the problem.
If it is not there then Tomcat has not installed.
If it says Stopped (or perhaps the status is blank) then it did not start and my Guess 1 was correct.

My cockup was to install the 32 bit version of java, and the 64 bit version of Tomcat (and Tomcat would not start because of the wrong java version).  I managed to do this by not following the instructions in the readme.txt file about using the the 32-bit/64-bit Windows Service Installer and instead direnting installing the 64 bit version.

In your case, I suspect what happened was that you initially installed Java 8 - and this comes only in a 64 bit version.  You then installed Tomcat (using the 32/64 bit installer) and it saw the 64-bit Java and installed the 64 bit Tomcat.

You then (following what I suggested) uninstalled java 8 and installed java 7 - but happened to get the 32 bit version because the java 7 installer matches the browser you use to install it and that will be 32 bit.

However, you did not uninstall Tomcat, and then reinstall it so you ended up with 32 bit Java and 64 bit Tomcat.

As you probably know, 32 bit stuff is installed in C:\Program Files (x86) and 64 bit stuff in C:\Program Files.  So if your Tomcat is in the latter and your java in the former then the problem is as I suspected.

Fix:  uninstall Apache Tomcat, and reinstall from where it says in the readme.txt, ie

http://tomcat.apache.org/download-60.cgi, selecting the 32-bit/64-bit Windows Service Installer

and your Tomcat should then match your java.

Regards, Tim G

Courage my boy - I bet its just another path issue (one I hit about 10 days ago installing an early test version of 1.8 on a new machine). [I just checked Uri's instructions and as far as I can see in step 4 where he is installing MySQL he did not explicitly set the path.]

When I did my MySql install,  go the your step 13 where you do "mysql -u admin -p < createdb.sql" and it said "'mysql' is not recognized as an operable program or batch file.".

The fix is as follows: first find where MySql was installed - in my case it went into C:\Program Files\MySQL\MySQL Server 5.5 - and all its programs live in the bin folder - so we need to add C:\Program Files\MySQL\MySQL Server 5.5\bin into the path.

"mysql -u admin -p < createdb.sql"

When I used the MySQL installer, it didn't ask me anything about the mysql config, so I needed to fix this. It says in the OpenVPMS readme.txt file at the bottom of section 1.1

  - include the following lines in my.ini
    max_allowed_packet=16M
    innodb_file_per_table

So where is the my.ini file? In my case it is in C:\ProgramData\MySQL\MySQL Server 5.5\my.ini

This is a plain text file, so you can edit it with Notepad - so start Notepad and open the my.ini file. [In the open fiile diaglog you have to change the file type selection (bottom right) from Test Documents (*.txt) to All Files (*.*) to see the my.ini file.

You will find that it contains lots of stuff. Ignore it all and go to the bottom and add the two lines above. [It wont matter if you did in fact set these during the install and they are set elsewhere in the file - but if you want you can check by searching for (with Edit|Find) 'innodb_file_per_table'. Save the file and restart MySQL. [Either simply restart the machine or use Control Panel|Administrative Tool|Services, click on the MySql line and then the Restart link.]

Re your note:  Also I couldn't follow ben's instructions above "6. Unzip the openvpms download navigate to /openvpms/conf and make sure the hibernate.properties file has the right settings for you (if you go with the instructions it should be right."

I think that you can probably ignore this (for some background see http://www.openvpms.org/documentation/csh/1.7/reference/setup/multiple-s... ).  That is by default the name of the MySQL database is 'openvpms', the name and password of the mysql user that the  OpenVPMS application used to talk to the database are also both 'openvpms. It is possible to change these by adjusting the <OPENVPMS_HOME>/conf/hibernate.properties file.

The readme.txt file says:

1.4 Database setup

  To create the OpenVPMS MySQL database, run the following in a shell prompt
  > cd <OPENVPMS_HOME>/db
  > mysql -u admin -p < createdb.sql
  > mysql -u admin -p openvpms < db.sql

  NOTES:
  * replace 'admin' with a user that has administrator privileges in MySQL.
  * the createdb.sql script creates an 'openvpms' user that only has
    privileges to connect from localhost.

so when you run the "mysql -u admin -p < createdb.sql" it will create the mysql user as required.

[Ben runs a tight ship and hence runs his system with a different setup so that the mysql user on his system is different to the standard openvpms/openvpms.]

Regards, Tim G