Latest News

Our cyber team is testing implementation of NTLMv2 and it's creating a problem.  Users are unable to authenticate with their active directory login to FMSA12.  Does anyone have some guidance on this issue?  Really need help.  We have 100's of FM db's and users.

Hi,  This might be a silly question but I've looked high and low and can't seem to figure it out.

I have a text field that gets its value from a value list via a drop down box.

In Browse mode, when the user chooses a value it automatically tabs to the next field. However, I want it to stay on the field until the user chooses another. I can't figure out how to make it stop moving to the next field on its own.

Thanks!

Hi all, I've scoured the web but all I've found were a handful of unanswered pleas for help. Hopefully one of you fine folk has dealt with this before!

In trying to connect to a database via PHP, I'm getting this error:

Communication Error: (22) The requested URL returned error: 403 - This can be due to an invalid username or password, or if the FMPHP privilege is not enabled for that user.

Now, to describe the situation further, I am 100% sure that:

- PHP is installed properly (phpinfo() works fine, and I can connect to other FM databases on other servers, from the same PHP pages)

- PHP is enabled on FMSA

- The username and password I'm sending are correct

- The username and password I'm sending DO have FMPHP privileges enabled

Possible complications:

- We are using a 2-server configuration, with the files hosted on server F, and the web server hosted on server W

- The PHP pages are hosted on server W, behind an SSL (accessed via https://Wdomain/phppage.php)

- IWP also currently goes through the SSL (and works fine)

I've used many variations for the hostspec IP address, including localhost, 127.0.0.1, https://127.0.0.1, the private IP, the public IP, Wdomain, https://Wdomain, all with and without ports 80 and 443 (SSL). The https addresses throw a different error:

Communication Error: (60) SSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed

I know it is at least finding the right location, because if I change the hostpec to any other invalid IP, it will throw the usual 

Communication Error: (7) couldn't connect to host

Even if I set it to the IP address for F, it gives the same 7 error.

The servers both run Windows Server 2008. The only major differences between these servers (production) and my other servers that work (test), is the 2-server configuration, and the SSL.

I'd be more than happy to provide any other information, if it helps.

Thanks so much!