Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 4174 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

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!

Posted

Are you using the PHP interface, or the XML interface for communication with the databases? Try enabling XML on those databases as well...

Posted

I'm using the PHP interface, though on the server in question (the production server), XML is NOT enabled. I will try enabling it this weekend, but I am not sure it will work, because while XML IS enabled on my test server (which does work), I tested it just now by turning it off. PHP continued to work, regardless. So while I'm willing to give it a shot anyways, because I'm at my wits end and can't afford not to, I'm not confident it will have any effect, and therefore am still happy to hear any other suggestions.

 

Additionally, no databases on either the functioning test server OR the non-functioning production server have XML access configured on any user, so that's not it either.

 

Thanks all the same, though, I'll let you know how it went on Monday...

Posted

No luck...now I'm back to square one. This is, of course, complicated by the fact that it's our Production server, and needs to be working at all times of day and night, meaning regular restarting and experimentation is not feasible.

 

Is there any way IIS could be the problem?

This topic is 4174 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.