This is a strange issue that happened only after we upgraded from FMP11 to FMP16.0.3. We also migrated the FMS to a new windows 2012 virtual server, with a updated version of SQL 2012 (previously 2008).

Most users (125+) can connect with no issues.

But we have a handful of users (5-10) that cannot open the database at all. They either run the launcher and never get a login screen, or after they login the initial scripts start to search for the users data and it never finishes. The FMP software eventually hangs up and they have to end task in windows. Of the users with problems, 1 can login to database with administrative privileges but not without. Several other users get stuck at the searching script and never make it past that.

Things we have tried so far:

- Reloading the users operating system, no change

- Adding the user to administrative group in Active Directory, no change

- Removing FMP16 and loading FMP15, then FMP14, no change

- Rebooting the server, no change

- Removing the startup scripts completely from the problem users, no change

I have found some articles about creating a new active directory organizational unit (OU) and adding the users to that group. Problem is we don't have direct server access so that process will take us several days to get the IT folks to test it with our network. 

Has anyone else ran into this issue upgrading to FMP16? Anyone have any ideas?

Any help is much appreciated!

Thank you 

I want to update this thread for other users that experience a similar issue.

For the problem users I ended up disabling the start-up scripts, then the users were able to login to the database but not get the main landing page layout. I spend several days debugging and re-writing the landing page scripts and I was able to solve the problem.