Have been some issues & troubles at a client-side, with a SPS-2003 implementation, when adding users to the portal/site – with an error message simply stating “unable to validate data”.
Some fruitless searches & config checks centred around Active Directory permissions, etc. – and then some googling found the following Microsoft KB (Knowledge Base) article :
This described that ASP.NET 2.0 is not allowed for .NET 2.0 – and should actually uninstall .NET 2.0. BUT – we have some other pages/sites that NEED to use .NET 2.0 – and this should be OK – esp. following the installation of SPS-2003 SP2.
I did notice that the Sharepoint Virtual Directory in IIS was configured to use ASP.NET 2.0.
We do not support configurations in which a SharePoint Portal Server 2003 Web application runs under ASP.NET 2.x.
Further evidence that something is amiss – and could be cause for concern :
Running a SharePoint Portal Server 2003 Web application under ASP.NET 2.x is not supported. If you try to run a SharePoint Portal Server 2003 Web application under ASP.NET 2.x, you may experience unexpected consequences.
Ummm – yep ! That’s the problem then, eh ?
Back to IIS, and attempt to change the site to use “1.1” instead of “2.0” – and then re-load the site.
But – the dreaded Server Error in ‘/’ Application was shown – ie. something bad before even “starting”.
Change back to use “2.0” – and it works ! But, that blasted error when adding users. *hhhmmm*
It turns out, that the “someone” who had installed the SPS-2003 instance had done the “stsadm -upgrade” command – to ensure that it works with .NET 2.0 !
Aaarrrggghhh ! Nvermind that this relates to WSS – not SPS – which is not supported for .NET 2.0.
Not much happens really – just a few lines in the Web.Config file are changed.
The following article explains how to reverse the above – thereby restoring the SPS-2003 instance to be .NET 1.1’able – and all is happy again !
If you (need to) change the version of ASP.NET that the virtual server uses from ASP.NET 2.0 to ASP.NET 1.1, you must use the Stsadm.exe command-line tool to update the settings in the Web.config file.
After ensuring that the server was playing nicely, we recommended to the client to run the SharePoint Configuration Analyzer to see if any monkeys had broken anything else.