Product and version - FMPA 188.8.131.52
OS and version - Windows Server 2012 R2
Leased Windows 2012 R2 server
When FMPA is run on the same machine as the database to which one is connecting is being hosted by FMS 184.108.40.206, changes cannot be made to the schema (Manage Database) and FMPA crashes often and typically after just a minute or two of connectivity. Editing scripts almost always causes FMPA to crash.
How to replicate
Hopefully this is obvious ...
Workaround (if any)
Don't run FMPA 15 on same machine as FMS 15. This is not satisfactory, as our development team sometimes needs to access the server machine via Remote Desktop to make updates to the schema (Manage Database). We do this on the host so that should we lose the connection, the schema update will continue to run to completion (preventing corruption of the database).