I'm attempting to upgrade a client from v13 to v16 (or even v15 ). I have tried each version and have been able to install them - but with each, every time I try to connect to the host the whole thing crashes.
When I select File > Open Remote - crash.
When I select the host in "Hosts" - crash.
I do have startup scripts but those are at a database level. I'm not even able to see the list of databases before the crash.
My work around is to re-install v13 which is working just fine.
Any ideas?
What OS on the client machine and the server? What version of FMS on the server?
Hi
could you inform what platform and versions you are running?
have you updated operating systems and the app.
Fm13, for example does not run on Mojave 10.14 ... but since you tried 15 and 16 that might not be the “problem” :-)
Client OS: Win 10 Pro (completely up to date)
FMS version: 15.0.3.308
If you have Pro Advanced open the file with Script Debugger window open.
This will allow you to bypass and/or troubleshoot any startup scripts which might be at play in your crashes.
Try this first:
install FM 16 (no need to uninstall 13), reboot the machine
create a new OS account on the machine and try to connect to FMS from that new account
If it does not crash then there is something in the original account's profile that makes FM crash but at least you will have verified that FM can connect just fine.
So I did that, and when I login with the new username and create a new profile - before I can do anything the installation dialog to choose setup language pops back up
What folder is the installer located in?
Is this a completely standalone machine or part of an AD infrastructure?
Default location - the C drive (is that what you mean?)
I believe the second answer is Yes, its a pc on a network with AD.
So I clicked through that prompted install (the ss in my previous comment).
16 DOES work on that profile - I can open remote without issues (once I bypass the "not encrypted" warning as is usual). When I log back in as the original user the issue is back - attempt to open remote and crash.
What do you think this means? Corrupt Windows user profile?
Something there clearly is interfering. Any plugins in use in the solution? If so, find all references to .fmx in the folders for that profile and delete them,, clear out the temp folders, ...
No plug ins. I originally cleared out all temp folders (disk cleanup, cc cleaner & manually...)
It's not the profile's only issue and now I'm thinking it may all be related. The profile is also having an issue with Outlook blocking images despite the correct settings.. and there are a couple of user profiles with .0 and .000 labels... issues with the FM versions showing up in the installed programs list on this profile...
I think it's pretty safe to say it's not a FileMaker issue and likely profile related. We'll keep him on v13 until we can rebuild the profile. Thanks for the profile test - that helped.
Try this first:
install FM 16 (no need to uninstall 13), reboot the machine
create a new OS account on the machine and try to connect to FMS from that new account
If it does not crash then there is something in the original account's profile that makes FM crash but at least you will have verified that FM can connect just fine.