I've ran across this problem before, and have never found a solution, other
than reinstalling Windows operating system, and starting from scratch, so
any help on this would be extremely helpful!

At some point, the FPSE Check In / Check Out feature stops functioning
properly, for some UNKNOWN reason, and basically results in the following:

A file can be checked out, but doing so will basically lock the file, so
that it cannot be edited, or checked back in, even by the person that
checked out the file. It is extremely frustrating, especially since it
usually means trashing the current installation, and doing a complete
reinstall to get it working again properly, at least until the next time it
decides to happen.

I've tried uninstalling / reinstalling the FPSE, deleting the temp FrontPage
directories, removing check in check out, then reapplying it, editing the
permissions on all the files using windows security settings, to no avail...
and, I've spent countless hours searching through knowledge base articles,
and have yet to come across a solution. Considering this problem has
happened to me several times, on different machines, I am surprised the is
not more people having this problem, and thus a solution out there that I
could find.

Please help, as next step is jumping to another server, and reinstalling the
existing one (UGH!)

Thanks!

[ Post a follow-up to this message ]

I found this knowledge base article, and am going to try it... hopefully it
works, but it seems I've tried this in the past and it didn't... here goes
nothing!

[url]http://www.kbalertz.com/294421/Cannot.Check.After.Check.Using.Source.Control.aspx[
/url]


"AspDotNetDvlpr" <aspdotnetdeveloper@hotmail.com> wrote in message
news:eg8xXNESGHA.5808@TK2MSFTNGP12.phx.gbl...
> I've ran across this problem before, and have never found a solution,
> other than reinstalling Windows operating system, and starting from
> scratch, so any help on this would be extremely helpful!
>
> At some point, the FPSE Check In / Check Out feature stops functioning
> properly, for some UNKNOWN reason, and basically results in the following:
>
> A file can be checked out, but doing so will basically lock the file, so
> that it cannot be edited, or checked back in, even by the person that
> checked out the file. It is extremely frustrating, especially since it
> usually means trashing the current installation, and doing a complete
> reinstall to get it working again properly, at least until the next time
> it decides to happen.
>
> I've tried uninstalling / reinstalling the FPSE, deleting the temp
> FrontPage directories, removing check in check out, then reapplying it,
> editing the permissions on all the files using windows security settings,
> to no avail... and, I've spent countless hours searching through knowledge
> base articles, and have yet to come across a solution. Considering this
> problem has happened to me several times, on different machines, I am
> surprised the is not more people having this problem, and thus a solution
> out there that I could find.
>
> Please help, as next step is jumping to another server, and reinstalling
> the existing one (UGH!)
>
> Thanks!
>

[ Post a follow-up to this message ]