|
Home > Archive > FrontPage Server Extensions for Windows > January 2005 > Source Control problem
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Source Control problem
|
|
|
| We're running into a problem with a FrontPage enabled web site. Running
FrontPage server extensions on a Windows 2000 server with IIS,
authenication is turned on (have tried both basic and Windows
integrated), and VSS is enabled as the backend source control
mechanism. We have an in-house application that creates an xml file and
writes it to a FP web site. It currently works fine in production, but
not on the new development server. Basically the application fails
attempting to check the file out after it has created it on the web
site. It appears to be using the anonymous account to write the file,
even though valid credentials are passed to the application, and check
it out. The credentials match an id in the VSS db. I've checked the
extensions version and they match between the broken dev server and
another machine I have this working on. The .Net Framework is version
1.1. Anyone have an idea on this one? Thanks in advance.
-dd
| |
|
| I knew I'd forget to mention something. An error keeps coming up when I
attempt to open the web site using the FrontPage client running on the
server ( I have not been able to try opening the web from a client
yet). When Windows integrated authentication is removed and basic
authenication is used FP cannot open the sub web. It reports a 'Server
Error: client closed the connection.' It works fine on a development
machine I have running with an identical setup from a security pov.
I've searched for help on this error but have found nothing. Thanks.
|
|
|
|
|