Drew -- ?
Update: I will obtain the FULL installer rather than the updater (supposedly I should be able to via my maintainence agreement) and see what happens.
As far as I understand it, the 'updater' you already have is the correct installer to use.
The point I'm trying make is that you must not only shut down FMServer's processes (the web publishing and database publishing from the Admin Console), but also shut down Apache/IIS, remove all previous components of FMServer (via the FMS 12.0v1 Installer of Add/Remove Programs ), and then use the updater...at least that's how I read the instructions. I'm doing one this afternoon, so I'd be happy to let you know what I see after the upgrade is completed.
Can you give the specific code you use to get the XML engine to return the version numbers?
-- Drew Tenenholz
Drew, when I used the updater I did follow the instructions, but I am using the Mac version, which did not instruct the user to uninstall.
The full install did produce different results, though not the one I really wanted. For the full install, I first shut down the WPE, disconnected all clients, closed all databases and saved the schedules. Then I used the uninstaller to entirely remove FMS 12, and rebooted. Then I used the full installer to install FMS 12.0.2. I restored the settings and schedules, and reuploaded the databases.
The WPE now reports:
<PRODUCT BUILD="06/21/2012" NAME="FileMaker Web Publishing Engine" VERSION="188.8.131.52"/>
... so it would appear the the updater in fact did not update the WPE, while the full-install did.
Unfortunately, the FMPXMLRESULT is still broken, the number of <FIELD> tags does not match the number of <COL> tags.
Sorry ... here is the way to see the XML output using a web browser:
You get the idea.
I did a complete install and get the same result as you:
PRODUCT BUILD="06/21/2012" NAME="FileMaker Web Publishing Engine" VERSION="184.108.40.206"/
product build="06/21/2012" name="FileMaker Web Publishing Engine" version="220.127.116.11"/
Sorry to hear that it doesn't actually resolve the problem. Since this is actively being followed in another thread, I think this is all the help I can offer.
-- Drew Tenenholz