[FX.php List] communication problem

Robert Janssen janssen_robert at hotmail.com
Thu Jun 12 09:43:03 MDT 2008


We finally solved the problem, however we cannot explain it.
 
In the dutch database there were 2 tables where the connection failed. Both layouts showed a related field (which was however not used in the FX-connection) and for some records the relation was empty. For the queries where there was an empty relation shown in the layout, the connection failed.
 
Just by removing this field from both layouts everything worked fine again. The strange thing is that in the belgian database these layouts are identical, showing the same fields, also with some empty relations, and here there is no problem.
 
if anyone can explain this ...
 
I'd still very much would like to hear it,
 
thanks!



> Date: Thu, 12 Jun 2008 10:29:49 -0400> From: dan.cynosure at dbmscan.com> To: fx.php_list at mail.iviking.org> Subject: Re: [FX.php List] communication problem> > also, xml parser can choke on corrupt data coming out of the database > fields (including high ascii chars).> > cheers,dan> > Dale Bengston wrote:> > Hi Robert,> > > > What happens if you do FMFindall() or FMView() queries against the Dutch > > database? Can you retrieve data at all?> > > > Can you confirm in the Web Publishing admin console that the Dutch > > database is available to the web? There is a page showing hosted > > databases. Are both the Dutch and Belgian versions showing?> > > > Another thing to check would be file access permissions (at the > > operating system level) after the transfer.> > > > Hope this helps,> > Dale> > > > > > --> > Dale Bengston> > Partner, The Whole Brain Group, LLC> > thewholebraingroup.com> > > > On Jun 12, 2008, at 8:29 AM, Robert Janssen wrote:> > > >> Hello people> >>> >> I have a rather puzzling problem with the FX module. I’ll try to be as > >> succinct as possible but that is proving difficult.> >>> >> I have two different timesheet programs, one for Dutch timesheets, one > >> for Belgian. These two programs are largely similar in> >> their communication ( databases ). Last week Filemaker was > >> transferred to another> >> server ( both windows 2003 servers ) (filemaker version 8.0.2.208 > >> advanced )> >>> >> After this migration the Dutch version failed to operate properly. > >> However the Belgian version works flawlessly.> >>> >> I’ve isolated the code where the problem occurs.> >>> >>> >> include_once($_SERVER['DOCUMENT_ROOT'] . "/FX/FX.php");> >> include_once($_SERVER['DOCUMENT_ROOT'] . > >> "/FX/server_data_urenstaat.php");> >>> >> $gekozen_week = 24;> >> $gekozen_jaar = 2008;> >> $filemaker_id = 1999001;> >>> >>> >>> >> $query = new FX($serverIP, $webCompanionPort, $dataSourceType, $scheme);> >> $query->SetDBUserPass ($webUN, $webPW);> >>> >>> >> $query->SetDBData($databaseName, "urenregistratie");> >> $query->AddDBParam('weeknummer', $gekozen_week);> >> $query->AddDBParam('weekjaar', (100*$gekozen_jaar+$gekozen_week));> >> $query->AddDBParam('medewerkernummer', $filemaker_id);> >> $query->AddSortParam('project_nr', 'ascend', 1);> >> $query->AddSortParam('activiteit_code', 'ascend', 2);> >> $query->AddSortParam('opmerking', 'ascend', 3);> >> $query->AddSortParam('datum', 'ascend', 4);> >> $data = $query->FMFind();> >>> >>> >> print_r($data);> >>> >>> >> if I run the code on the belgian database which for the > >> "urenregistratie" layout is the same as the Dutch version, I get results.> >> If I run the code on the dutch database an error occurs and the > >> print_r($data) returns the following code> >>> >> FX_Error Object ( [error_message_prefix] => [mode] => 1 [level] => > >> 1024 [code] => 100 [message] => FX: ExecuteQuery XML error: Invalid > >> document end at line 2 [userinfo] => [backtrace] => Array ( [0] => > >> Array ( [file] => c:\Inetpub\intranet-ace-eu\FX\FX.php [line] => 1473 > >> [function] => FX_Error [class] => FX_Error [type] => -> [args] => > >> Array ( [0] => ExecuteQuery XML error: Invalid document end at line 2 > >> ) ) [1] => Array ( [file] => c:\Inetpub\intranet-ace-eu\FX\FX.php > >> [line] => 1687 [function] => ExecuteQuery [class] => FX [type] => -> > >> [args] => Array ( [0] => -find ) ) [2] => Array ( [file] => > >> c:\Inetpub\intranet-ace-eu\FX\FX.php [line] => 1921 [function] => > >> FMAction [class] => FX [type] => -> [args] => Array ( [0] => -find [1] > >> => 1 [2] => full [3] => 1 ) ) [3] => Array ( [file] => > >> c:\Inetpub\intranet-ace-eu\gogo.php [line] => 23 [function] => FMFind > >> [class] => FX [type] => -> [args] => Array ( ) ) ) [callback] => )> >>> >> I observed a similar problem in the online fx trouble forum:> >> [FX.php List] FX: ExecuteQuery XML error> >> Steve Bennett (steve at bentechaps.com)> >> Sat Sep 8 09:57:39 MDT 2007> >>> >> however that never ended in a sollution,> >>> >> best regards,> >>> >> Robert Janssen> >>> >> Het beste van Windows, nu ook online. Deel jouw wereld met Windows > >> Live. Download nu._______________________________________________> >> 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
_________________________________________________________________
Probeer Live Search: de zoekmachine van de makers van MSN!
http://www.live.com/?searchOnly=true
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.iviking.org/pipermail/fx.php_list/attachments/20080612/d76c326b/attachment.html


More information about the FX.php_List mailing list