FM 16.03 Client crashing on WTS (Windows Terminal Server on WIN 2008 R2) when selecting 'Open Remote'. Anybody experienced something similar?
We are trying to update from FM 14 where this was no problem at all.
is this related to Odd behavior - FM16 & MS RemoteApp (RDP) ?
I don't know how similar this can be, but I do experience something along this line. Easy to reproduce.
- I open a hosted version of our solution and at the same time I open a local file L.
- In layout mode, I copy a button from the hosted solution, file X, to the local file L - the button calls a script in another hosted file, say Y.
- File L says it can't find the file Y and opens a dialog asking me to locate it.
- I enter the path to the remote file Y (IP address, name) and Filemaker accepts it.
From that point onwards it's impossible to specify any script in any file, both in file X and in file L or in any other file: the dialog won't show up anymore. The only solution to this is to quit FMPA 16 and open it again.
Dont think so. We experience complete crash when trying to open dialog 'open remote'. Happens before seeing any database.
We've just spent today downgrading 2 Windows 2012R2 RemoteApp servers back to FMP v15 due to our client complaining of problems launching v16 and frequent crashes, which were not happening in v15.
We do use plug-ins (in both v15 and v16) and haven't had a chance to do much trouble shooting, but are getting frequent crashes using the Hosts in the Launch Center plus general crashing while the users are operating the system.
An example from the Event Viewer below:
Faulting application name: FileMaker Pro.exe, version: 220.127.116.112, time stamp: 0x59b9e834
Faulting module name: FileMaker Pro.exe, version: 18.104.22.1682, time stamp: 0x59b9e834
Exception code: 0xc000041d
Fault offset: 0x00000000004fdd47
Faulting process id: 0x2918
Faulting application start time: 0x01d352e994e30efd
Faulting application path: C:\Program Files\FileMaker\FileMaker Pro 16\FileMaker Pro.exe
Faulting module path: C:\Program Files\FileMaker\FileMaker Pro 16\FileMaker Pro.exe
Report Id: a4e6ec86-bf1d-11e7-8168-005056b9858b
Faulting package full name:
Faulting package-relative application ID:
This is a major problem for us as we need the SDI window handling of v16
no problems with WTS on 2008/2012/2016 Servers.But i start with an fmp://... link from the Desktop.
Did you install correctly ?On a WTS you should activate the installation mode.Start a command shell with Administrator rights and type:
change user /installafter the installation go back with:
change user /execute
if you don't do it, strange things will happen
Yup, 7 years of running within Citrix XenApp and RemoteApp. Still could be a v16 plug-in compatibility issue, but at the moment having to revert to v15 for stability.
Out of curiosity, can you open a file via a URL that bypasses the Open Remote? (fmp://[ip/domain]/[filename].fmp12 In other words keep it from trying to use Bonjour which may be the problem. Maybe you could uninstall Bonjour that comes with FM by default. If you could get past the first screen of Open Remote to the Favorites, that doesn't use Bonjour, but not sure how to get past it on first opening.
Bojour is not installed, on neither side. And it is possible to open files by clicking a direct link. Only 'open remote' crashes immediately.
I am quite sure that the installation was done correctly. This is a quite big IT consulting company which has very much experience with net installation and software on WTS.
To confirm, Bonjour never installed.
CICT wrote: Hi Taylor To confirm, Bonjour never installed. Kind regards Andy
Note that Bonjour is normally installed with FileMaker Server installs. If you followed the normal procedures, then it did get installed. You might want to go to the Task Manager and select the Services tab and look and see if it is there. It can be removed if you don't mind auto discovery not working.
We've never installed the Bonjour option in the 7 years we've been cloud hosting.
CICT wrote: Hi Taylor We've never installed the Bonjour option in the 7 years we've been cloud hosting. Kind regardsAndy
OK... just checking. I have had a number of clients tell me they had not because they did not realize the FileMaker Server install automatically included it. Its just like my client last week that swore they had made no changes to their machine and after hours or testing and installing and uninstalling, found out they had set Java to automatically update. Easy things to overlook.
Bonjour is a waste for Cloud hosting anyway. It is only for discovery on a local area network. I've seen similar problems that you describe fixed when bypassing Bonjour on severs several times is why I suggested to confirm.
Are you able to use a URL in a browser to connect and it go quickly such as fmp://someURL.com/filename.fmp12 or does it also go slowly?
Thanks for this, to my knowledge, and it has been some months since we did our last v16 install, on Windows Bonjour has always been a follow up option after the main installation. I've never seen it install automatically. But it definitely isn't on any of our Windows servers.
We don't have a speed problem, it is a stability problem with FMP v16 ceasing to work displaying the standard Windows error message offering to check for a solution (yeah right - LOL), end the program, etc. The same databases using the same plug-ins do not do this using v15.
Bonjour is still a second install, separate installer, called by the FM installer
CICT wrote: Hi Taylor Thanks for this, to my knowledge, and it has been some months since we did our last v16 install, on Windows Bonjour has always been a follow up option after the main installation. I've never seen it install automatically. But it definitely isn't on any of our Windows servers. We don't have a speed problem, it is a stability problem with FMP v16 ceasing to work displaying the standard Windows error message offering to check for a solution (yeah right - LOL), end the program, etc. The same databases using the same plug-ins do not do this using v15. Kind regardsAndy
Usually I would suspect a network issue (hence my questioning Bonjour). But if you use 15 on the same machine with same plugins and it works, then that indicates something different between 15 and 16. I know some plugins were updated when 16 came out. Maybe confirm you are on the latest plugin versions for 16. What plugins are you using and what versions? How about this, can you turn off the plugins and try it for a while without and see if things become stable?
Retrieving data ...