Help! Deployment Problems with Hosted App - SL4 + SQL2008R2

Hello,

We've been able to successfully launch our application locally but have been banging our heads against the wall when it comes to deploying it on DASP. We're running a SL4 application on MS SQL 2008 R2 (also hosted on DASP). We've set our application up to use ASP.net Membership services and when we try and log in after deploying, we get the following (unhelpful) error message:

"Error Logging In:System.ServiceModel.CommunicationException: The remote server returned an error: NotFound. ---> System.Net.WebException: The remote server returned an error: NotFound. ---> System.Net.WebException: The remote server returned an error"

I have a feeling its somehow linked to Membership Services but aren't entirely sure. I've gone through these steps: http://support.discountasp.net/KB/a...rshiproles-provider-to.aspx?KBSearchID=274307 and the video here http://iis7test.com/MembershipProvider/Default.aspx but to no avail (I see ids in the db but don't know how to bring up the website admin tool).
Any help would be greatly appreciated as I've done tons of troubleshooting but have probably missed something along the way. If there's something related to ASP membership services that I need to run please let me know.

Note: - I set our (3) RIA DomainServices references to Copy Local=True.
- I added a Clientdomain and crossdomain policy to Root directory of our webserver (even though we've deployed into a subdirectory)
- I marked the subdirectory as a web application using IIS 7
- I've setup authentication to only be Forms and Anonymous
- I tried using Fiddler but only get this message:
"<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body><s:Fault><faultcode xmlns:a="http://schemas.microsoft.com/net/2005/12/windowscommunicationfoundation/dispatcher">a:InternalServiceFault</faultcode><faultstring xml:lang="en-US">The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the &lt;serviceDebug&gt; configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.</faultstring></s:Fault></s:Body></s:Envelope>"

Thanks so much in advance to anyone that can offer some help.

 

Thanks Bruce, I enabled the trace through IIS - is there anything in particular I should look for? I glanced over the files it generated but didn't see anything that stood out - should I post them here?

If it is related to the membership services the strange thing is that I can browse to the membership services by typing in the url where I get a help page.

I was also thinking it may be related to the Services so here's a question, in the ServiceReferences.ClientConfig, should the client endpoint addresses be the domain name or the server ip address? ie where should I get this from?

Let me know if there's any data I should post on here that would help...