Hi, We’re having all sorts of issues trying to get our dasp hosted Silverlight 4 application to work with the hosted SQL Server 2008 database. The application works fine with both a local SQL Server 2008 and application deployment… - The web deploy in Visual Studio 2010 seems to work fine. But when we launch the application we get the "The remote server returned an error. Notfound" as it tries to access items from the database. - We then tried to trace it with Fiddler but haven’t gained much insight. - We’ve also tried launching a local copy of our application and accessing the SQL Server 2008 hosted by dasp but its returning the same errors Its starting to look like there’s an issue where our application can’t seem to access/authenticate into the SQL server database so - We set the login to anonymous - Verified that we can log into the SQL Server Management Console in our DASP Control Panel successfully. Can anyone assist in telling us what we might be missing? Is there a user role permission that we don’t have setup correctly? If so what should it look like? We’ve also tried launching a Silverlight 4 application that doesn’t have a Connection String for the database and it also returns the same error: "The remote server returned an error. Notfound" Cheers
"Specified SQL Server not found" means that your requests not even reaching the specified server. Probably the name of SQL Server is incorrect. The name of our servers should follow the specific format: sql2kXXX.discountasp.net
Hi I'm getting the same results and can't figure it out. Here's what I have. Database is SQL 2008 R2 hosted at DASP. Trivial Silverlight 4 application to display 1 small table on a datagrid. Works fine in VS2010 connecting to the DASP so I know my connection string works. Publish to DASP website and make sure the System.ServiceModel.DomainServices dll's are all in the bin folder. App starts but does not show data and returns error from (wizard generated) DomainDataSource_LoadedData event handler. Help please, anyone. Ian
i would create a simple test page (not SL) that connect to the database and test. If that works, you can isolate the problem to the domain service.
I had a terrible time with this myself and I fiddled around with it for about a week before it suddenly worked. If you Google for this error, you'll find hundreds of people with the "same" problem, but they're actually all different. Any number of problems can cause this and all the combinations and permutations probably add up to thousands of different possible causes. What I did to finally break through to the solution was carefully read all the requirements for deployment (I used Matthew MacDonald's Silverlight 3 book as my reference) and made sure I was following them all religiously. I think I had three things wrong: The .xap file must be in the root of ClientBin. The Website.Web.dll must be in the root of bin. It must be a release build. Insuring those three items, and voila! My Website popped up. I still occasionally make the third mistake. I'm running with a debug build on my PC, trying to find a bug, then when I find it, I copy the .xap my Website, and wham: "Notfound." Quickly building "release" and deploying to ClientBin gets me up and running again. But I suspect you're not having any of these problems. Good luck finding out what's wrong in your particular case.
