Hi,
I've scanned through the forums for remoting issues and I've seen a lot of good explanations on how to set it up properly. But one area that doesn't seem to be addressed is what to do if you do not get the proper XML response when testing remoting. That is what is happening to me. I get the "Page not found" error. I'm not sure where to start as far as troubleshooting goes - I'm pretty much an IIS novice.
For my setup, I created a web application with reference to the CSLA assembly and my BO assembly. I then set up a virtual directory on the target server and copied my web app's bin directory and web.xml to that VD. I have checked that my web.xml looks like it's supposed to and I believe it is correct. I have tried setting the website as an application (as well removing that setup) and get the same error both ways.
If anyone can provide any help on this it would be greatly appreciated. Let me know if any more info is needed.
Thanks, Dennis
Aha - I remember the problem well, since I hit it each time I tried to set things up and I couldn't find the answer either. And I've forgotten again!
However, I think you should check your Windows Firewall settings and make sure that the Web Server can be accessed. Try ControlPanel -> WindowsFirewall -> Advanced Tab ->NetworkConnectionSettings-Settings.
Good luck!
This is a good thread
OK, I still can't seem to figure out what's wrong here. I'm pretty sure by now that my web.config file is right. I have Csla.dll and CompanyLibrary.dll in my bin directory within my vdir. I checked my mapping extensions to make sure the ASP.net and SOAP mappings were in the list. The ASP.NET version in the vdir properties says 2.0.50727 (which - it is my understanding - is correct for ASP.NET 3.5). If I put a simple test index.html in my vdir, I can bring it up in my browser no problem. But my remoting URL:
http://MyServer/CompanyRemoteHost/RemotingPortal.rem
is still giving me a "Page Not Found" error. I'm sure it's probably some configuration or security issue in IIS but I am not IIS-savvy and I can't find anything on the web that answers my issue. Here is my web.xml, just in case I did miss something::
<?xml version="1.0"?>
<configuration>
<appSettings>
<add key="CslaAuthentication" value="Csla"/>
</appSettings>
<system.runtime.remoting>
<application>
<service>
<wellknown mode="SingleCall" objectUri="RemotingPortal.rem" type="Csla.Server.Hosts.RemotingPortal, Csla"/>
</service>
<channels>
<channel ref="http">
<serverProviders>
<provider ref="wsdl"/>
<formatter ref="soap" typeFilterLevel="Full"/>
<formatter ref="binary" typeFilterLevel="Full"/>
</serverProviders>
</channel>
</channels>
</application>
</system.runtime.remoting>
<connectionStrings/>
<system.web>
<!--
Set compilation debug="true" to insert debugging
symbols into the compiled page. Because this
affects performance, set this value to true only
during development.
-->
<compilation debug="false">
</compilation>
<!--
The <authentication> section enables configuration
of the security authentication mode used by
ASP.NET to identify an incoming user.
-->
<authentication mode="Windows"/>
<!--
The <customErrors> section enables configuration
of what to do if/when an unhandled error occurs
during the execution of a request. Specifically,
it enables developers to configure html error pages
to be displayed in place of a error stack trace.
<customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">
<error statusCode="403" redirect="NoAccess.htm" />
<error statusCode="404" redirect="FileNotFound.htm" />
</customErrors>
-->
</system.web>
<system.codedom>
</system.codedom>
<!--
The system.webServer section is required for running ASP.NET AJAX under Internet
Information Services 7.0. It is not necessary for previous version of IIS.
-->
<system.webServer>
</system.webServer>
</configuration>
Copyright (c) Marimer LLC