fndimarco

Thanks, Steven -- I have reported the WebDirect/v2 problems to FM this morning. Along with some other problems we've discovered while testing.

I installed the server update yesterday and our WebDirect project became almost instantly inoperable. When only three users attempted to access the file via browsers, the connections became impossibly slow. On the server, I noticed that doing anything on the desktop was almost impossible. Via Task Manager, I noticed the fmscwpc.exe process had spiked the CPU usage to 100% and even after breaking the browser connections, I couldn't get that process to let go. I forced quit it and the computer began to work again. Reboot, repeat -- same thing several times. I spun up a clean Windows 2008 server (on Amazon Web Services), installed only FMS13 and the updater and began to work on the FMServer_Sample file via web direct. All these problems recurred -- with only a handful of users connecting via Web Direct, we saw "Communication Error" warnings, broken connections, frozen pages, and (on the server) the fmscwpc.exe spiking. We also noticed that the sample file was generally rendering slowly or incorrectly -- on the first page, graphics on the layout that displayed in the v1 of server do not display, for instance. And some of the tabbing and data entry problems seem aggravated rather than improved. The closest I have to a clue is script triggers -- we were on layouts with OnLayoutEnter triggers when things seemed to blow up. Even though on one layout, all the trigger did was "Show All Records." Anyone else seeing this kind of misbehavior in Web Direct after the update?

Hi Matt: Thanks for you feedback on this -- I'm particularly happy to hear I am not alone and/or hallucinating these problems. I have tried to fix this issue in various ways, including spinning up new, clean servers (on Amazon Web Services). Same behavior: if I have "Require Secure Connections" checked, I can not access via Go or FM13. Also: If I turn off Require Secure Connections and connect via Web Direct using https://, I don't get the certificate error. However, I added a step (to the FMServer_Sample.fmp12 file's login script that shows a dialog box with the results of Get (ConnectionAttributes) and Get (ConnectionState) -- and even though I see a lock in my browser's address bar, the results of those functions is blank for ConnectionAttributes and "1" (that is, not secure) for ConnectionState.

A followup regarding a two-server configuration, and a problem: I followed the directions here and successfully installed a wildcard SSL certificate from GoDaddy on my database server. Then, I copied the contents of the CStore folder and placed them in the web server's CStore folder. I used the fmsadmin certificate import command to install the .crt file from GoDaddy and restarted the server. This was a qualified success. Now, when I log in via WebDirect, I get a valid HTTPS connection. Success! However, on the server configuration (Console:Datebase Server: Security: Secure Connections), the require secure connections checkbox is off. Turn that checkbox ON, and my connections all break -- web direct can't connect and if I try to open the file via FileMaker Open Remote... the files no longer show up. Did all the restart/reboot stuff. No change. So, if the secure connection is OFF but my web direct connections are secure, are my FileMaker/Go connections secure (my clients will access the solution via all these methods) as well because of my certificate? Or am I having some other problem? FileMaker Server 13v1, Win2008 Server -- everything was working fine before installing the certificate. I, too, was trying to get rid of the annoying self-signed certificate for Web Direct connections.