locked
Update and delete dont work but Insert work in https but all work in http RRS feed

  • Question

  • So I developed a simple wcf data service using the Entity Framework for single table using VS2012. I deployed it directly from VS2012 to our test server which is on our network and it works fine. I added service reference to a client application and was able to insert/update and delete records.

    When I created a deploy package and deployed it on a server which is under https and has a valid certificate, I can add service reference as usual and insert works fine but update and delete fail. I add verboseerrors=true to see what error was happening but all I see is error 500 invalid index. Is there anything special to do with services under https that wont allow modifying a record?

    Monday, September 9, 2013 1:34 PM

All replies

  • So I developed a simple wcf data service using the Entity Framework for single table using VS2012. I deployed it directly from VS2012 to our test server which is on our network and it works fine. I added service reference to a client application and was able to insert/update and delete records.

    When I created a deploy package and deployed it on a server which is under https and has a valid certificate, I can add service reference as usual and insert works fine but update and delete fail. I add verboseerrors=true to see what error was happening but all I see is error 500 invalid index. Is there anything special to do with services under https that wont allow modifying a record?

    The 500 Error occurs because ASP.NET Integrated mode is unable to impersonate the request identity in the BeginRequest and AuthenticateRequest pipeline stages. 500.24 is thrown if your application is running in integrated mode, validateIntegratedModeConfiguration is not declared or set to true, and your application has identity impersonate set to true.

    Workaround

    A. If your application does not rely on impersonating the requesting user in the BeginRequest and AuthenticateRequest stages (the only stages where impersonation is not possible in Integrated mode), ignore this error by adding the following to your application’s web.config:

      <system.webServer>
              <validation validateIntegratedModeConfiguration="false" />
      </system.webServer>

    B. If your application does rely on impersonation in BeginRequest and AuthenticateRequest, or you are not sure, move to Classic mode.

    C. remove from web.config which won't be effective in integrated mode anyway

    ______________________________________________________________
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers


    • Proposed as answer by Neno farid Wednesday, September 11, 2013 5:16 PM
    • Unproposed as answer by Arunnayar Wednesday, October 9, 2013 12:14 AM
    Monday, September 9, 2013 1:43 PM
  • This didn't work. Any other ideas?
    Wednesday, October 9, 2013 12:14 AM