jamiebowden
asked on
problem with visual sourcesafe integration
Hi
When I install a web application and web project on the server and enable source control from machine this works fine.
When i then go to another users machine and create a project I first get the message .
unable to get file 'global.asa' server error: The frontpage server extensions on this web do not support getting previous versions
when i then try to check out a file i get the following message
unable to check out file "anyfile.asp" server error: there is a problem with source control integration on your server.
i am using windows 2000
When I install a web application and web project on the server and enable source control from machine this works fine.
When i then go to another users machine and create a project I first get the message .
unable to get file 'global.asa' server error: The frontpage server extensions on this web do not support getting previous versions
when i then try to check out a file i get the following message
unable to check out file "anyfile.asp" server error: there is a problem with source control integration on your server.
i am using windows 2000
i've run into the same problem. uninstall the webserver and frontpage extensions. copy your files out from the wwwroot directory and delete that directory. now go thru the folder youve copied your web project into and delete every file created by frontpage extensions (_vti_inf and things like that)... make sure can view hidden files. then reinstall the webserver and frontpage extensions and copy your web project (which you're SURE has no more autogenerated files in it) into the wwwroot directory and it'll load just fine. the problem is actually with the webserver's sourcesafe. its only trying to help :) best of luck!
Also make sure that the folder for the web does not have execute permissions. If it does you will not be able to place anything in it via interdev or sourcesafe.
Most likely the problem is with the frontpage extentsions.
Most likely the problem is with the frontpage extentsions.
I have another solution for you.
Try this instead.
Go to the Computer Managment MMC.
Into Services & Applications.
Open up IIS then
right click on the faultive web application.
In all task, click on Permission wizard.
Follow the permission wizard choosing
Using: Inherit all security setting,
then "replace all directory and file permission (recommended)
This should do the trick... well it did for us.
Good luck
Try this instead.
Go to the Computer Managment MMC.
Into Services & Applications.
Open up IIS then
right click on the faultive web application.
In all task, click on Permission wizard.
Follow the permission wizard choosing
Using: Inherit all security setting,
then "replace all directory and file permission (recommended)
This should do the trick... well it did for us.
Good luck
I just ran into the same problem, but the answers listed here didn't do the trick.
This did:
Go into MMC for IIS, find your flawed webdirectory,
right click > All Tasks > Check Server Extentions,
if any errors occur, simply choose to fix them
in my case the wizard suggested to "Tighten FrontPage security", and after doing that I could connect from InterDev to my application again.
This did:
Go into MMC for IIS, find your flawed webdirectory,
right click > All Tasks > Check Server Extentions,
if any errors occur, simply choose to fix them
in my case the wizard suggested to "Tighten FrontPage security", and after doing that I could connect from InterDev to my application again.
Make sure your application or website isn't using anonymous access as well,
I just noticed some source where being checked in/out by the user IUSR_machinename, and when I deleted that user from the SS database I got that server extention error again.
After setting the site to NT authentification in the security settings, files could be checked in/out again, and they where registered for the correct network users.
I just noticed some source where being checked in/out by the user IUSR_machinename, and when I deleted that user from the SS database I got that server extention error again.
After setting the site to NT authentification in the security settings, files could be checked in/out again, and they where registered for the correct network users.
Well I think Jamie has forgoten us?
Hey jamie... you should post a comment at least!
Tell us if our answer were right... or if you
found the solution by yourself!!
Hey jamie... you should post a comment at least!
Tell us if our answer were right... or if you
found the solution by yourself!!
ASKER
Hi All
I haven't forgotten you all, I have just been caught up with other issues. However I will be coming back to this problem within the month (developers have been using SourceSafe independantly for the time being), so I will let you know how I get on.
Thanks for your help
Jamie
I haven't forgotten you all, I have just been caught up with other issues. However I will be coming back to this problem within the month (developers have been using SourceSafe independantly for the time being), so I will let you know how I get on.
Thanks for your help
Jamie
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Cheers saved me a lot of hassle