Had the same problem. The fix for me was to set the properties for the
Flashremoting directory in IIS Manager to allow Scripts and Executables to run,
that option is under Executable Permissions in IIS Manager. Hope that helps
Can also try enabling parent paths, possibly anonomous access as well, if
running ntfs allowing the aspnet or web applications account to have write
access to the bin directory, install .net 1.1 sdk. Still, didn't manage to get
the example web services to work (with flash remoting). Would definetely
recomend flashorb though, seems to be currently better supported than flash
remoting and has more functionality at present. Although sure macromedia will
update the .net support when they release flex for .net. Got my webservices
working with flashorb quickly, and now passing custom objects a lot easier than
in flash remoting. http://www.flashorb.com/docs/introduction/comparison.htm