SharePoint 2003 with SQL 2005 deployment woe!! - eForce - the elite force
Thursday, March 02, 2006 11:36 PM eforce

SharePoint 2003 with SQL 2005 deployment woe!!

Finally cleared the "Accesskey is too long" error when deploying SharePoint 2003 with SQL 2005.

In order for the sharepoint backup to work, we need to install SQL 2005 Workstation component on the Sharepoint server.

But, we had this "Accesskey is too long" error after this installation sequence:

  1. SQL 2005 server - workstation component
  2. Windows SharePoint Service with SP2
  3. SharePoint Server 2003
  4. SharePoint Server 2003 SP2
  5. "Accesskey is too long" error occur, when accessing the Central Admin page :(

Eventually, we learnt from Kit Kai and a Sharepoint newsgroup posting that the problem lies on Central Admin site is trying to run on ASP .Net 2.0 framework, which was installed when installing SQL 2005 component.

At this stage, we are not able to switch to ASP 1.01 framework from IIS.. as there is no such option. Instead, we literally went thr the entire installation process again.

So here is the working installation sequence:

  1. Windows SharePoint Service with SP2
  2. SharePoint Server 2003
  3. SharePoint Server 2003 SP2
  4. SQL 2005 server - workstation component

Spot the difference?

What a lesson learnt!

# re: SharePoint 2003 with SQL 2005 deployment woe!!

Tuesday, April 11, 2006 11:07 PM by cyberdrop

You can uninstall the ASP.NET 2.0 IIS Integration by calling aspnet_regiis -u (c:\windows\system32\microsoft.net\v2.0...)