| AspDotNetDeveloper 2005-08-17, 5:57 pm |
| I am having a check-out / check-in problem for some reason now, where
whenever a file is checked-out under source control, the file is checked-out
as SERVER\Administrator, therefore locking the file to the actual person
checking-out the file, and making it unable to check-in, or unable to be
modified.
I am running Win 2K3 Server, and did install SP1, but did not notice the
problem until recently, so I do not think it coincided with the SP1 install.
I have tried pretty much everything I can think of, including:
Removing and re-installing the FPSE
Re-installing SP1
Unextending the FPSE, removing manually all FPSE _private, _derived folders,
then re-extending the site
Disabling source-control, then re-enabling it
Changing all the folder file settings manually to not read-only, then
enabling source control again
Nothing has worked so far, so I am going to have to remove the extensions,
and use the File Share access method, as that seems to work, and does allow
source control, which seems to work also, but the File Share method does not
seem to have the same capabilites as far as remembering changes as the FPSE
do, so I will have to do manual updates from test server to production
server. That's the one feature I love about FPSE is how it just publishes the
changed files only when publishing, and the source-control, but I need
source-control, so I will have to take what I can get.
Only thing left to try would be an operating system re-install, or trashing
the existing webs, and starting all over with all the virtual folder setups.
I did try to create a new web, and inport the configuration from the previous
web, but that resulted in the same problem on the new web....
Any suggestions would be appreciated!
|