As I use my sharepoint system very rarely I had not noticed that there was an error when trying to access http://companyweb. I have an SBS 2003 server that deals with all my mail etc and recent updates seem to have killed off the sharepoint service.
This is the full error that I get
This Windows SharePoint Services virtual server has not been configured for use with ASP.NET 2.0.50727.3603. For more information, please refer to Knowledge Base article 894903 at http://go.microsoft.com/fwlink/?LinkId=42660.
The article the link refers to is a good starting point, but it fails to actually tell you where the stsadm file is, and running the command as microsoft have put it will just result in a file not found error. I had to go hunting for the file myself, and as the search function failed it was a manual hunt.
I finally found the file, so here is the command that actually works
“c:\Program Files\Common Files\Microsoft Shared\web server extensions\60\BIN\stsadm” -o upgrade -forceupgrade -url http://companyweb
That command obviously depends on the virtual sharepoint site actually being called companyweb. If you have changed it you will need to amend the end of the command.
Once it finished running I was asked to login to the sharepoint service on the server itself. After trying multiple combinations of usernames/domains and passwords it failed. I jumped onto my desktop and logged into sharepoint without issue and all is now working again. My guess (as I have not fully investigated it and won’t be on my home system as it’s not really needed) is that the DNS is either out or logging into sharepoint on the server itself is just not cricket.


by Soddengecko @ 12:49

No one has opened their mouth about
“Sharepoint Services not configured for use with ASP.NET 2.xxxxx”