« Previous Next »

Thread: lock violation

Last post 11-27-2009 3:08 PM by bpsintl. 35 replies.

Average Rating Rate It (5)

RSS

Page 3 of 3 (36 items) < Previous 1 2 3

Sort Posts:

Shortcuts

Search | Active Posts | Unanswered Posts | View all users

  • 10-10-2009, 6:06 AM In reply to

    • bpsintl
    • Top 500 Contributor
    • Joined on 05-19-2009, 4:11 AM
    • Posts 22

    Re: lock violation

    Reply Contact

     Has no one got any more suggestions on this?

  • 10-28-2009, 6:37 PM In reply to

    • Nosik
    • Not Ranked
    • Joined on 10-28-2009, 10:33 PM
    • Posts 2

    Re: lock violation

    Reply Contact

     Hi, I've been getting the same pop-up and has just fixed the problem. All you need to do is to remove defaultPath from the following line in applicationHost:

     <httpErrors lockAttributes="allowAbsolutePathsWhenDelegated,defaultPath">

     I left lockItem="true" for httpErrors, and still this is working. Hope it helps.

  • 10-29-2009, 2:20 AM In reply to

    • bpsintl
    • Top 500 Contributor
    • Joined on 05-19-2009, 4:11 AM
    • Posts 22

    Re: lock violation

    Reply Contact

     You are a star!! Thank you, this has solved the problem. I can't believe it was that simple.

     Does anyone know why this fixed it, and will it be ok to leave this "defaultPath" setting off?

  • 10-29-2009, 4:28 AM In reply to

    • Nosik
    • Not Ranked
    • Joined on 10-28-2009, 10:33 PM
    • Posts 2

    Re: lock violation

    Reply Contact

     That's cool.

    Well, when you were editing Feature Settings, you were setting the Default Page path (the section is name Default Page, as you can see). And in applicationHost it was among locked attributes of httpErrors module. So, what I did was to unlock that specific attribute.

     I don't know how safe is it, to leave it like this, you might want to check with others, but obviously, after setting your custom path, you can lock the attribute once again, if that's a problem.

     Cheers.

  • 11-10-2009, 1:49 PM In reply to

    • bpsintl
    • Top 500 Contributor
    • Joined on 05-19-2009, 4:11 AM
    • Posts 22

    Re: lock violation

    Reply Contact

    Nosik:

    I don't know how safe is it, to leave it like this, you might want to check with others, but obviously, after setting your custom path, you can lock the attribute once again, if that's a problem.

     

    Anyone else have any comments on this, can I leave it as it is?

  • 11-27-2009, 3:08 PM In reply to

    • bpsintl
    • Top 500 Contributor
    • Joined on 05-19-2009, 4:11 AM
    • Posts 22

    Re: lock violation

    Reply Contact

     Anyone?
Page 3 of 3 (36 items) < Previous 1 2 3
Microsoft Communities