If you'd like some help with this, I suggest answering more of the questions asked when you fill out an issue report. We can't even tell if you are using Mac or Windows so this leaves us unable to even begin to figure out why it didn't work. (Installed 12v2 on my xp box today with no issues...)
I've seen that message as well. (Mac OSX) Tells nothing more, when finishing the update, a message box appears saying that there is no FM12 (btw: Would be better, when the updater brings that message at the beginning of the update...) - could it be, that You started the updater twice? - when starting FM: What versionnumber shows?
ouch... sorry for the unreadable Text. All formatting will be lost, when posting from an iPad :-(
If this is a Mac OS, past updates to Mac systems have triggered issue reports with regards to whether or not "spotlight" was enabled. Apparently, this utility was used by the updator to search out the original application for updating. In past cases with older updaters, enabling spotlight fixed the issue.
I do not know if this is the case here, but if you are a mac user and have this problem, check it out and let us know.
I just filed a bug report before seeing this thread. On OS 10.6.8 the FileMaker update 12v02 claims that a valid copy of FileMaker 12v01 cannot be found and stops installation but you can continue the installation by selecting FIleMaker 12v01 manually in the file browser.
Hello W. A. Wilson:
Thank you for posting.
As stated in other threads ensure that spotlight is indexing the applications folder. FileMaker does rely on spotlight to find the application.
With that said, I did go ahead and report this issue to Development and Testing.
FileMaker does rely on spotlight to find the application.
Hmmm, just nit picking here... shouldn't that read the Installer does rely on spotlight...?
Given how frequently we get a set of reports on this issue with each bug fix release, I suspect the phone support staff get a good sized "rash" of calls on this to. Can't help but think that if the techs at FileMaker can find a way to change their installer configuration/code/whatever to either not need spot light or to detect that it is not enabled/set up right and then tell the user what's wrong and what they need to do, they wouldn't get this issue coming back each time...