[FX.php List] ExecuteQuery Error

[Steve Bennett]

Sorry for the long message but not sure where to look to resolve  
things so I will give as much info as I can think of.

Trying to move a FileMaker File to a different server but we are  
getting the following FX error when trying to work with a multi-page  
fxphp form and not sure if it is the server configuration or something  
in the php code which has been working correctly for more than a year  
connecting to the current server.

ERROR: FX: ExecuteQuery XML error: Invalid document end at line 1  
(100) /

The pages have been working fine for the past year when connecting to  
the current server but something is wrong with configuration of the  
new server that seems to be causing errors. I did not set up the  
FileMaker servers and have little control over them but both the new  
and old server are running FMSA 8 but the new server is running  
Windows 2003 Small Business Server which I understand is not  
officially supported by FileMaker.

At first we were unable to connect to IWP or CWP on the new server but  
this seemed to be a problem with IIS not being able to access some of  
the FileMaker web publishing folder and the IT department modified  
some of the permissions and IWP seems to now be working.

CWP also appears to be working as some of the FXphp pages are working  
but the multi-page form errors when going from the first page to the  
second. When I look at the above error it indicates that it is line 1  
of my second page that is causing the error but I am not sure what the  
(100) indicates in the error message. The first line of the php page  
loads the connection information and is the same on all of the pages  
and has been working fine on the old server.

<?php require_once('../Connections/myconnection.php'); ?>

The pages also use sessions but I figure they would be using the web  
server which has not changed.

I am not sure if there are some other FileMaker web publishing folders  
that IT may need to alter permissions on or if there is a better way  
to track down specifically what is causing the error. I am also  
wondering if it could be the unsupported Windows 2003 Small Business  
Server, is anyone running FMSA on 2003 SBS?

Any thought would be appreciated.

Thanks,

Steve