Test Web Services Error: underlying connection was closed:

[rnrstar]

This problem just started and I'm not sure why. When I try to test the
web services I get the following error:

The underlying connection was closed: The connection was closed
unexpectedly.

I'm pointing to the x.WS.Ix.php file and even selected the default
list method I get the above error. The x.DB...php files are working
and I'm now trying to test the web service and AJAX implementations so
as a sanity check and to get a feel for what data was returned I used
the Test Web Services. I was able to test successfully earlier on but
I have made several changes to the database since then. The main
things I have changed is adding "datDateAdded DESC" to some of the
"Order by" fields when editing the method. I tried removing them and
regenerating the MySQL code and php code but I still get this error.

The other thing I noticed is that while it doesn't work with two of
the interfaces I have, it does work with one particular interface. I
also added an interface to a table I hadn't planned on needing one but
for testing purposes and to make something really simple to try, that
also failed. So now I have three out of four interfaces that generate
the above error.

Might it have something to do with the recent changes to the php code
generator?

Any ideas?

Thanks in advance,

[HOlsen]

The web services use the x.DB...php files when communicating with the
database. If the x.DB files work and the x.WS files do not, I can only
think of two possibilities.
1: You do not use the same connection parameters in the two cases (the
WS files use the connection parameters in the config file).
2: You have updated DB files and not the WS files (or vice versa).

You should probably update all your generated code, i.e.
1. Right click on the interfaces in the model and select refresh.
2. Update the database
3. Update all the generated application code.

If this does not work you can try the following: (However, if the x.DB
files really do work for you, this should not be needed)
If you are in a development phase and nobody is dependent of the
deployed solution you can try refactoring you model, see
http://www.risetobloome.com/PageItem.aspx?item=763 for more
information. A RISE model contains the entire model evolution, unless
it has been refactored. If you remodel, you will need to either:
1. Clear your current database before generating the refactored
version.
2. Generate into a new database
3. Change the name and prefix of your model. In this case your
database will contain tables etc. for both your old and your
refactored model.

If you send me a copy of your model, I can have a look at it. Please
send it to sales[at]risetobloome

Best regards,
RISE to Bloome Software