If the above steps don’t resolve your issue, then do a deep dive into tracing the error details.

#3: Does your in folder on the Server have another in folder inside? If so, you need to remove the extra one:Ībove are the most common resolutions for this infamous “Not Found” error. If they don’t match, uninstall it from the Server and reinstall the version matching with your Development machine. You can check the RIA component version via Control Panel: This is one of the most common scenarios that we usually see. #2: Is version of your RIA component on the Server “exactly” same as what you have in your Development machine? They MUST match otherwise you will get this “Not Found” error. Make sure the connection string is valid. #1: Check the database connection string that your Entity Model is using. (you may need to perform one or more of the following steps): To debug your application, set customErrors to Off so that you can see the detailed ASP.NET error from the client. By default, the customErrors element of a Web.config file is set to RemoteOnly, which means a remote client will not receive the detailed ASP.NET error information. The remote server returned an error: NotFoundįinding out the detailed underlying error would be your first step. Load operation failed for query 'MyQueryxxxx'. You will get a variation of an error message like this: So, if you are in a similar situation, here are few options that should resolve this issue. This is basically Silverlight’s way of telling that an exception occurred while the Silverlight runtime tried to make a service call. If you are trying to figure out why your WCF RIA Service's method calls(or just the regular WCF Service for that matter) throwing the infamous “

Silverlight error code 1618