[FX.php List] FMS 10 setting up XML returns sometimes empty record sets, and sometimes fields and data working

Tue Oct 20 04:20:32 MDT 2009

I now even tried to move the same files to my FMS 7 and the problem is
still the same, I also removed all restrictions on the account...

This setup looks alot like the FileMaker 7 problem where accounts and
privilegies that just did not make sence, make then...

ggt

2009/10/20 Gjermund Gusland Thorsen <ggt667 at gmail.com>:
> Hmm, now it is acting like Tom Bombadil in The Lord of the Rings; Now
> you see me now you dont...
>
> It works occasionally...
>
> How can I debug FileMaker Server?
>
> ggt
>
> 2009/10/19 Gjermund Gusland Thorsen <ggt667 at gmail.com>:
>> And the account is the same... webuser, in which has both fmphp and
>> fmxml enabled.
>>
>> ggt
>>
>> 2009/10/19 Gjermund Gusland Thorsen <ggt667 at gmail.com>:
>>> The problem is only for XML RPC( not FX.php in particular ), not for
>>> the fmphp... for now
>>>
>>> Yes, the query is the same the problem is only with XML RPC
>>>
>>> ggt
>>>
>>> 2009/10/19 Leo R. Lundgren <leo at finalresort.org>:
>>>> BTW, if I understand you correctly, you said that when the problem is
>>>> visible with FX.php, it's not a problem if you switch to FM PHP API? Have
>>>> you tried the exact same search with both these products, when there is a
>>>> problem? If so, does it work with one of them?
>>>>
>>>> I meant to ask whether you've had the chance to try the same search using
>>>> the Python version of FX, when the problem shows itself. If so, does that
>>>> work or not?
>>>>
>>>>
>>>> 19 okt 2009 kl. 16.05 skrev Gjermund Gusland Thorsen:
>>>>
>>>>> Well php I know somewhat well, FMS logs are not that easily accessible
>>>>> or debugable...
>>>>>
>>>>> Any clue to what might go wrong? Would sniffing the WPE reveal the
>>>>> actual problem? tshark and perhaps netcat to see what is going on?
>>>>>
>>>>> ggt
>>>>>
>>>>> 2009/10/19 Leo R. Lundgren <leo at finalresort.org>:
>>>>>>
>>>>>> Well, the times I've had these problems, it's been with FM PHP API, so I
>>>>>> don't think it's a problem with the PHP part.
>>>>>>
>>>>>> I recall checking the XML output from a problematic search, and indeed
>>>>>> the
>>>>>> actual data stream said that there were no record. This means the problem
>>>>>> is
>>>>>> upstreams and not on the PHP side of the solution.
>>>>>>
>>>>>>
>>>>>> 19 okt 2009 kl. 15.56 skrev Gjermund Gusland Thorsen:
>>>>>>
>>>>>>> The sad thing though... is that fmphp works :-(...
>>>>>>>
>>>>>>> ggt
>>>>>>>
>>>>>>> 2009/10/19 Gjermund Gusland Thorsen <ggt667 at gmail.com>:
>>>>>>>>
>>>>>>>> Yes, they are in FM, on the web I even try to use FMFindAny, in FX and
>>>>>>>> -findany using curl on commandline.
>>>>>>>>
>>>>>>>> This time around saving privs did not make a difference :-(
>>>>>>>>
>>>>>>>> ggt
>>>>>>>>
>>>>>>>> 2009/10/19 Leo R. Lundgren <leo at finalresort.org>:
>>>>>>>>>
>>>>>>>>> Have you looked in the database using the normal FM GUI, and seen
>>>>>>>>> whether
>>>>>>>>> the records that you cannot find via XML are visible in the database
>>>>>>>>> like
>>>>>>>>> they should?
>>>>>>>>>
>>>>>>>>> 19 okt 2009 kl. 15.51 skrev Gjermund Gusland Thorsen:
>>>>>>>>>
>>>>>>>>>> My experience with this on this one server is that it works for about
>>>>>>>>>> 50 queries then starts serving _ONE_ blank record.
>>>>>>>>>>
>>>>>>>>>> And it does not matter whether you set privs again or relaunching
>>>>>>>>>> WPE...
>>>>>>>>>>
>>>>>>>>>> ggt
>>>>>>>>>>
>>>>>>>>>> 19 okt 2009 kl. 15.44 skrev Leo R. Lundgren:
>>>>>>>>>>
>>>>>>>>>>> Do you mean that relaunching WPE (by disabling IWP for that database
>>>>>>>>>>> in
>>>>>>>>>>> the databases pane in FM Admin?) gives the same effect as "touching"
>>>>>>>>>>> the
>>>>>>>>>>> permissions, i.e that the records start being visible again, but
>>>>>>>>>>> only
>>>>>>>>>>> for a
>>>>>>>>>>> little while?
>>>>>>>>>>>
>>>>>>>>>>> The last time this happened for me was a while ago and before that
>>>>>>>>>>> it
>>>>>>>>>>> was
>>>>>>>>>>> a while ago as well. It doesn't happen very often, it's measured in
>>>>>>>>>>> a
>>>>>>>>>>> number
>>>>>>>>>>> of months between times. Overall I think it's happened only two
>>>>>>>>>>> times
>>>>>>>>>>> for
>>>>>>>>>>> something that's been running for a couple of years.
>>>>>>>>>>>
>>>>>>>>>>> That being said, it might still have happened at times when neither
>>>>>>>>>>> I
>>>>>>>>>>> nor
>>>>>>>>>>> the client was looking. But considering that I haven't been able to
>>>>>>>>>>> get rid
>>>>>>>>>>> of the problem without taking action, after a few hours of almost
>>>>>>>>>>> fruitless
>>>>>>>>>>> debugging, it feels more likely that it hasn't happened without us
>>>>>>>>>>> noticing
>>>>>>>>>>> it.
>>>>>>>>>>>
>>>>>>>>>>> 19 okt 2009 kl. 15.33 skrev Gjermund Gusland Thorsen:
>>>>>>>>>>>
>>>>>>>>>>>> You are right, this works.
>>>>>>>>>>>>
>>>>>>>>>>>> I will give you feed back on whether or not it stays like this, I
>>>>>>>>>>>> mean
>>>>>>>>>>>> relaunching WPE gives the same effect for a while.
>>>>>>>>>>>>
>>>>>>>>>>>> tia,
>>>>>>>>>>>> ggt
>>>>>>>>>>>>
>>>>>>>>>>>> 2009/10/19 Leo R. Lundgren <leo at finalresort.org>:
>>>>>>>>>>>>>
>>>>>>>>>>>>> 19 okt 2009 kl. 14.56 skrev Gjermund Gusland Thorsen:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Anyone experienced this?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> http://pastebin.com/f7d504cc4
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> foundCount = 0
>>>>>>>>>>>>>> ErrorCode = 0 and not 401...
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> all fields are supposedly empty.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Before I delve into explaining my similar experiences, do you
>>>>>>>>>>>>> still
>>>>>>>>>>>>> have the
>>>>>>>>>>>>> same problem? If so, does it help if you go into the permissions
>>>>>>>>>>>>> for
>>>>>>>>>>>>> the
>>>>>>>>>>>>> user/group that the user belongs to, and change something, so that
>>>>>>>>>>>>> the
>>>>>>>>>>>>> privileges are updated. Note that I don't mean you must change
>>>>>>>>>>>>> something
>>>>>>>>>>>>> that actually matters, do whatever little change is needed to be
>>>>>>>>>>>>> able
>>>>>>>>>>>>> to
>>>>>>>>>>>>> "OK" and save the new permissions, then change it back to what it
>>>>>>>>>>>>> originally
>>>>>>>>>>>>> was. Just to see if the problem goes away when the permissions are
>>>>>>>>>>>>> definately updated at least once.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> -|
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> 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
>>>>
>>>>
>>>>
>>>> -|
>>>>
>>>> _______________________________________________
>>>> FX.php_List mailing list
>>>> FX.php_List at mail.iviking.org
>>>> http://www.iviking.org/mailman/listinfo/fx.php_list
>>>>
>>>
>>
>