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

[jschwartz]

Joel,

Will consider the two box option.  Seems a shame to have to go that route for something so basic.

Regarding DevCon...

I stopped attending DevCon a couple of years back. I gave up on FMI delivering any useful content for the PHP Web Developer.  The last productive year was 2007, I believe, with the introduction of the API.  Or was it 2009? I also lost faith with the introduction of CWP 2.0.  What are they calling it now?  Web Direct?

Would love it hear other opinions.

Jonathan

On Jul 21, 2014, at 6:45 PM, Joel Shapiro <mail at jsfmp.com> wrote:

> Long time indeed.  See you at DevCon?
> 
> If you're having issues between IIS & FMS -- which I am on a FM13 setup right now -- one option could be to keep FMS off of the IIS machine.  Let the "Windows guy" do what he needs to on a plain ol' web server (w/ the FX pointed to the DB server), and you won't have to worry about him trampling on your FMS/WPE/ETC
> 
> -Joel
> 
> 
> On Jul 21, 2014, at 6:37 PM, jschwartz <jschwartz at exit445.com> wrote:
> 
>> Hi Joel,
>> 
>> Long time.
>> 
>> 
>> Answer is….
>> 
>> One Machine.
>> 
>> I suppose that I could ask them to spin up a separate virtual IIS web server, but why?  I haven’t been paying attention.  Is this a “known issue”?
>> 
>> Jonathan
>> 
>> 
>> On Jul 21, 2014, at 6:33 PM, Joel Shapiro <mail at jsfmp.com> wrote:
>> 
>>> Hey Jonathan
>>> 
>>> Is this a one- or two- machine config?
>>> 
>>> Could you, as people here have been commenting, have a vanilla web server on its own machine, and have all FMS components -- including the WPE -- on the non-PHP Database server?
>>> 
>>> -Joel
>>> 
>>> 
>>> On Jul 21, 2014, at 5:18 PM, jschwartz <jschwartz at exit445.com> wrote:
>>> 
>>>> 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
> 
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list