However, I wouldn't think that the crossdomain is actually
necessary because the application exists on the same domain and
directory as the webServices. But, I added one anyway because every
google lookup seems to say that the HTTP Request Error -
Server.Error.Request is a crossdomain.xml problem.
I was kind of thinking it could be a permission error.
However, I have the web page run as an 'application' and that
application's user account has permissions to the root directory
and all it's children files/directories (so it can read the
crossdomain.xml) and also the application idenity has access to run
all the selects.
Unfortunately I'm running this on IIS6 on the DEV/TEST
machine and IIS7 on my local machine. So, I'm unable to setup
failed request tracing to see if I can find the problem there.
Does anybody have any help they can share? I've spent the
complete day trying everything I can think of to get it to work
with no resolve.