[FX.php List] Can't connect with manually installed php on Windows 2008 Server

Fitzgerald, Theodore C ted-fitzgerald at uiowa.edu
Tue Jul 22 17:30:32 MDT 2014


Jonathan,

You can use the following URL format to test if the XML portion of FileMaker's WPE is working (fx.php uses this behind the scenes):

http://<<server hostname or IP address here>>/fmi/xml/FMPXMLRESULT.xml?–db=<<database name here>>&–lay=<<layoutname here>>&–findall

Of you course, you'd want to use the address of your WPE server, and specify an appropriate database and layout.


Ted
________________________________________
From: fx.php_list-bounces at mail.iviking.org [fx.php_list-bounces at mail.iviking.org] on behalf of jschwartz [jschwartz at exit445.com]
Sent: Tuesday, July 22, 2014 5:05 PM
To: FX.php List
Subject: Re: [FX.php List] Can't connect with manually installed php on Windows 2008 Server

Back to the original problem….

The Windows guy is going to restore the php functionality for the third time after the CWP deploy trashed it….twice.

Please remind me…what tests can I run to tell if I’m reaching FMS (the XML URL you mentioned) and to isolate the problem? As I mentioned, It’s been a long time since I worked under the hood with fx.php.

Thanks

Jonathan




On Jul 21, 2014, at 7:56 PM, Fitzgerald, Theodore C <ted-fitzgerald at uiowa.edu> wrote:

> Jonathan,
>
> What is "the cURL error"?  Not able to reach the IIS server?  Could it be a firewall issue?  What happens if you try the XML url directly?  You're sure cURL is installed and enabled?
>
> Ted
> ________________________________________
> From: fx.php_list-bounces at mail.iviking.org [fx.php_list-bounces at mail.iviking.org] on behalf of jschwartz [jschwartz at exit445.com]
> Sent: Monday, July 21, 2014 7:18 PM
> To: FX.php List
> Subject: [FX.php List] Can't connect with manually installed php on Windows     2008 Server
>
> Hi Folks,
>
> I had a perfectly fine fx.php system working under OS X 10.6.8, but the system would not pass a PCI security scan, so I agreed to move it to Windows 2008. Another guy is handling the Windows side. When I first installed the system under FMS 11, all was good the Web Publishing side.  The Windows guy had to continue plugging security holes to pass the PCI scan.  His last step was to replace PHP because the PCI scan complained about the embedded PHP version inside FMS 11.
>
> That’s when fx.php stopped talking to FileMaker.  I got the cURL error, although password and connect info was correct..  I redeployed the Web Publishing Engine…twice. Each time, the deploy whacked IIS to the point that IIS stopped recognizing php files.
>
> The Windows gut isn’t too happy.  We’re both wasting a huge amount for time just to to placate the credit card guys.
>
> Are there any secrets I should know?
>
> Thanks
>
> Jonathan_______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list

_______________________________________________
FX.php_List mailing list
FX.php_List at mail.iviking.org
http://www.iviking.org/mailman/listinfo/fx.php_list


More information about the FX.php_List mailing list