Any other webserver active on this machine?
Did you do a full UNinstall of FMS 11 ?
If not, uninstall both FMS11 and FMS13, reboot and try again to install FMS13
Did you try accessing the admin console from another machine?
YEs - a first try to resolve would be a complete de-install (all FMS..) and then let FMS do a full install, deactivate all Anti-Virus, make sure that all of the needed ports are open (if in a protected LAN, deactivate the firewall)
in addition to uninstalling, after the reboot, check the Program Files\FileMaker\ folder and manually delete anything that is left. For good measure reboot again then.
the spinning wheel on top right is not Windows' own hourglass. I am wondering if it's Java's one. I would suggest to check the version of Java you have installed and compare to FMS requirements.
For full uninstall of FMS13, add these IIS components to be removed.
IIS URL Rewrite Module
Microsoft Application Request Routing
Microsoft External Cache for IIS
Microsoft Web Farm Framework
and if you've used the machine for FMS11, it is worth to disable IIS once and reboot.
Thanks for the responses, everyone!
This is a brand new VM, so FileMaker Server 11 was not installed previously.
I've removed FileMaker Server 13, as well as the suggested IIS components that user19752 suggested. I deleted the FileMaker folder and all of it's contents from the Program Files directory.
After a restart, and a fresh install of FMS 13, I'm still having the problem of the Deployment Assistant hanging. As planteg mentioned, the spinner I see is not from Windows itself, but from Java.
So, I'm guessing it's time for a call to FileMaker Techincal Support.
Any sharepoint settings when VM was installed ?
Try Chrome as browser ?
What are the specs of the VM server?
FMSAT v13 is no longer dependent on Java, as far as I know.
SAT on the client no longer requires Java; however, Java is very much required for FileMaker Sever 13 installations.
in that case we keep fingers crossed... I thought we were passed this.
Thanks for clarifying this.
So, the problem seems to have been resolved, though none of us know exactly how. A coworker was able to complete the deployment wizard and then launch the admin console. He claims he didn't do anything different than I did.
I have another new VM to set up in another week or so, so I guess I'll see if the same issue comes up there.
Thanks again, everyone.
If you go to all the trouble to get your installation 'just right', don't
'start over' with another deployment. Clone your existing VM, change the IP
and licensing info and take advantage of the work that you've already put
into the first deployment. A well tested, stable, template is a wonderful
On Tue, Mar 10, 2015 at 11:42 AM, ByteTheBullet <email@example.com>
Unfortunately, I don't have the access to clone the VM. Our corp IT infrastructure group sets up the initial VMs, and then it's up to the VM owners to get any 3rd party party installed and configured.
I think I'm going to see if I can get a copy of the Windows image they used, though, and see if I can figure out why I was unable to complete the Deployment Wizard, but my coworker was able to.