|
Ok, so I start with a brand new project using the Dev-Force Business template so it includes aspnet authentication.
I update the Config files so it includesa a "LocalSQLServer" line for the aspnetdb. I then run the app and log in successfully.
I then deploy to my hosted website. I get the No Endpoint is listening error.
To debug, I create a new project using the Ria Services Business Template, update the config file as above and deploy. I can successfully log in - no errors. This means it is not the hosting that is the problem.
As another debug attempt, I created another test project using the DevForce template that does not inlcude authentication. I add an Entity Model, and then set up a query and execute it. I deploy and it works no problem. So this means it is not DevForce itself.
The issue seems to be not with Dev-Force, but with the ASPNetDb.
The Entity Service is running.
The Debug file is empty.
All bin files are marked copy local and uploaded to the site.
The Config file looks like this:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<configSections>
<section name="ideablade.configuration" type="IdeaBlade.Core.Configuration.IdeaBladeSection, IdeaBlade.Core" />
</configSections>
<connectionStrings >
<remove name="LocalSqlServer" />
<add name="LocalSqlServer" connectionString="Data Source=tcp:sql2k803.discountasp.net;Initial Catalog=SQL2008_717577_jet;User ID=SQL2008_717577_jet_user;Password=*;" />
</connectionStrings>
<ideablade.configuration version="6.00" xmlns="http://schemas.ideablade.com/2010/IdeaBladeConfig">
<logging logFile="DebugLog.xml" />
<objectServer>
<serverSettings useAspNetSecurityServices="true" />
</objectServer>
</ideablade.configuration>
<system.serviceModel>
<serviceHostingEnvironment aspNetCompatibilityEnabled="true" multipleSiteBindingsEnabled="true" />
</system.serviceModel>
<system.web>
<authentication mode="Forms">
<forms name=".SilverlightApplication97_ASPXAUTH" />
</authentication>
<roleManager enabled="true" />
<profile>
<properties>
<add name="FriendlyName" />
</properties>
</profile>
<compilation debug="true" targetFramework="4.0">
<assemblies>
<add assembly="System.Data.Entity, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
</assemblies>
</compilation>
</system.web>
</configuration> If you want to see the error, go to JetCM.net. You don't even have to log in, it just pops up the error after the xap loads.
I am not sure what else to do to debug this. This same error happened when I first deployed the site, but then it went away for awhile and came back. I don't know what the changes were that made it happen.
If you want to log onto the site via FTP, I can email you the password. It's just a test site so there is nothing of value to mess up.
Greg
|