Category Archives: SQL Server

Windows, SharePoint, and IPv6

Leave a reply

I often see talk about administrators disabling IPv6 for one reason or another.  A lot of that comes down to “I don’t use it, so I don’t leave it enabled”.  Always makes sense from an administrator perspective… except when it comes to IPv6.

Microsoft has made sure, since Windows Vista and Server 2008, that IPv6 was a first-class citizen in Windows.  In fact, so first-class that Windows will leverage IPv6 before attempting to leverage IPv4.  If there is an IPv6 path available, IPv6 will be used.

Microsoft has an FAQ on IPv6 which specifically states while they understand that some administrators do disable IPv6 in Windows, IPv6 is a mandatory part of Windows and do not test disabling IPv6 during the development and testing process for Windows (this means leave IPv6 enabled!).

SharePoint 2010 fully supports IPv6 in an IPv6-only or a mixed IPv4 and IPv6 environment.  All supported editions of SQL Server for SharePoint 2010 also support IPv6.  The only restriction with IPv6 for SharePoint is that you cannot browse directly to the IP address over the HTTP protocol (e.g. browsing to http://[fe80::bc95:be32:cc03:845b%2511] would not work) and all DNS records must be using quad-A (AAAA) records for IPv6 addressing.  Any farm element that otherwise can take an IP address will accept an IPv6 address, given it is enclosed in brackets “[IPv6-Address]”.

The world is out of IPv4 address.  It is time to start testing that IPv6 rollout!

Managed Metadata Item Term Limit

Leave a reply

It looks like there is a limit to the number of Managed Metadata terms a particular item can have.  In my experimenting, it was 192.  The 193 would generate a SQL Server exception and limitation.  SQL Server has a limit of 2,100 parameters per stored procedure and per user-defined function.  While walking through the code with 192 terms, the SharePoint List item was saved successfully.  When adding the 193rd item, the query fails:

Capture[5]

The managed metadata terms used on this item were:

Adding another term to that list, in my case, “81”, would generate the above error upon saving the document.  SharePoint will report the following in the Application Event Log:


Log Name: Application
Source: Microsoft-SharePoint Products-SharePoint Foundation
Date: 7/22/2012 10:34:23 AM
Event ID: 5586
Task Category: Database
Level: Error
Keywords:
User: NAUPLIUS\trevor
Computer: SHAREPOINT.nauplius.local
Description:
Unknown SQL Exception 8003 occurred. Additional error information from SQL Server is included below.

The incoming request has too many parameters. The server supports a maximum of 2100 parameters. Reduce the number of parameters and resend the request.

Additionally, the ULS log will report the same error under SharePoint Foundation –> Database at both High and Critical levels.  Unfortunately, there is nothing about this type of limitation on the SharePoint Software Boundaries and Limits page.

To view the query generated by attempting to update the item with more than 2,100 parameters, take a look at the following SQL script.