Print Page | Close Window

Server not responding

Printed From: IdeaBlade
Category: DevForce
Forum Name: DevForce 2010
Forum Discription: For .NET 4.0
URL: http://www.ideablade.com/forum/forum_posts.asp?TID=1874
Printed Date: 21-Apr-2026 at 3:49pm


Topic: Server not responding
Posted By: jmpinchot
Subject: Server not responding
Date Posted: 09-Jun-2010 at 12:55pm
I switched from 6.0.1.0 to 6.0.3.0 this afternoon and now my silverlight application is unable to talk to the BOS. Now when I attempt to call LoginAsync I get the following error.

The Login could not be completed because the server did not respond.  Check that the server is available and contains a clientApplicationType='Silverlight' configuration setting.


My Web.Config is shown below. My custom login manager is in the web project itself and it never had a problem being found before. I've tried copying this configuration over to the App.Config in my equivalent of the DomainModel assembly, but the error persists. What exactly am I missing?

The application itself is being deployed to my local IIS server.

<configuration>
 
  <configSections>
    <section name="ideablade.configuration" type="IdeaBlade.Core.Configuration.IdeaBladeSection, IdeaBlade.Core"/>
  </configSections>
 
  <connectionStrings>
    <add name="CoreEntities" connectionString="..." /> 
  </connectionStrings>

  <ideablade.configuration version="6.00" xmlns="http://schemas.ideablade.com/2010/IdeaBladeConfig" >

    <logging logFile="log\DebugLog.xml"/>

    <!-- Additional configuration can be added to override defaults.
         See the sample config files in the Learning Resources for more information.
    -->

    <objectServer>
      <serverSettings supportedClientApplicationType="Silverlight"/>
    </objectServer>
  </ideablade.configuration>
 
  <system.web>
    <compilation debug="true" targetFramework="4.0" />
    <authentication mode="Forms"/>
  </system.web>

  <system.webServer>
    <modules>
      <add name="RequestDBModule" type="TradePMR.eCustody.Web.RequestDBModule"/>
    </modules>
  </system.webServer>
 
  <system.serviceModel>
    <serviceHostingEnvironment aspNetCompatibilityEnabled="true" multipleSiteBindingsEnabled="true" />
  </system.serviceModel>
</configuration>


Replies:
Posted By: jmpinchot
Date Posted: 10-Jun-2010 at 6:30am
This morning I've tried to start from scratch and created a new separate model project. This project does not make use of a login manager at all. Everything works fine when I run within Visual Studio. The problem starts when I attempt to run from my Local IIS web server.

To that end here's my ServiceReferences.ClientConfig file. Maybe I'm missing something here?

<configuration>
  <system.serviceModel>
    <client>
      <endpoint name="EntityService"
                address="http://localhost/eCustody/EntityService.svc/sl"
                binding="customBinding" bindingConfiguration="customBinaryBinding"
                contract="IdeaBlade.EntityModel.IEntityServiceContractAsync"
                />
      <endpoint name="EntityServer"
                address="http://localhost/eCustody/EntityService.svc/sl"
                binding="customBinding" bindingConfiguration="customBinaryBinding"
                contract="IdeaBlade.EntityModel.IEntityServerContractAsync"
                />
    </client>
    <bindings>
      <customBinding>
        <!-- Custom binding using http, binary encoding, no security -->
        <binding name="customBinaryBinding">
          <binaryMessageEncoding/>
          <httpTransport maxReceivedMessageSize="2147483647" maxBufferSize="2147483647" />
        </binding>
      </customBinding>
    </bindings>
  </system.serviceModel>
</configuration>

Posted By: kimj
Date Posted: 10-Jun-2010 at 8:26am
First, the Login problem - If everything was working in 6.0.1 and started failing after the 6.0.3 upgrade the most likely problem is that the assemblies have somehow gotten out-of-sync, or are cached by IIS.  When making the upgrade you should re-save your entity models to ensure the generated code is current, then clean and re-build all projects, then publish/deploy to IIS.  If the error recurs, check the debuglog generated by DevForce -- if the EntityServer couldn't be started the log should contain an error message.
 
The second issue - the ServiceReferences.ClientConfig file is not a requirement, since DevForce defaults may be sufficient.  In your file the address for the EntityServer is incorrect, it's pointing to EntityService.svc and not EntityServer.svc.  If you were using this ClientConfig in your original app with the Login problem, then this is the problem there too.
 

Posted By: jmpinchot
Date Posted: 10-Jun-2010 at 10:09am
Fixing the clientconfig file seems to have done the trick. Thanks for the help. It's always something stupid :)


Print Page | Close Window