1

Closed

Grouping issue on all lists and web applications

description

Hi there,
 
Sorry to be the only one logging these, it's because I really really like the work you have done and definitely can see some really good uses for this. It's just got a few teething issues and I would like to help feedback as much as possible :)
 
Anyway - when the solution is deployed (Which it does across ALL web apps so this affects everything in the farm) grouping fails with a correlation error:
 
Unable to display this Web Part. To troubleshoot the problem, open this Web page in a Microsoft SharePoint Foundation-compatible HTML editor such as Microsoft SharePoint Designer. If the problem persists, contact your Web server administrator.
 
 
Correlation ID:03f132b0-fd49-487c-baf7-5ccd0f24abd0
 
Only tested this on lists that use grouping in their views and the content types do not make use of the Image field. These are existing lists that were there before the solution was deployed and have had no changes made since.
 
Details from the correlation log will be included at the very end of this message.
 
When I uninstalled the solution via Powershell and restarted IIS the problem went away. To verify that it was deploying the solution I re-deployed it and tested and then the problem re-appeared.
 
Thanks again for a great product - if I can help in any way then give me a shout!!
 
Kind regards,
 
Rix
 
ULS Log:
 
08/11/2011 09:02:56.91 w3wp.exe (0x1544) 0x2950 SharePoint Foundation Web Parts 89a1 High Error while executing web part: System.Text.EncoderFallbackException: Unable to translate Unicode character \u200B at index 2026 to specified code page. at System.Text.EncoderExceptionFallbackBuffer.Fallback(Char charUnknown, Int32 index) at System.Xml.CharEntityEncoderFallbackBuffer.Fallback(Char charUnknown, Int32 index) at System.Text.EncoderFallbackBuffer.InternalFallback(Char ch, Char& chars) at System.Text.ASCIIEncoding.GetBytes(Char chars, Int32 charCount, Byte* bytes, Int32 byteCount, EncoderNLS encoder) at System.Text.EncoderNLS.Convert(Char* chars, Int32 charCount, Byte* bytes, Int32 byteCount, Boolean flush, Int32& charsUsed, Int32& bytesUsed, Boolean& completed) at System.Text.EncoderNLS.Convert(Char[] chars, Int32 charIndex, Int32 charCount, Byte[] by... 96a05bbe-f58c-4361-b53a-28c289e9a0c2
08/11/2011 09:02:56.91* w3wp.exe (0x1544) 0x2950 SharePoint Foundation Web Parts 89a1 High ...tes, Int32 byteIndex, Int32 byteCount, Boolean flush, Int32& charsUsed, Int32& bytesUsed, Boolean& completed) at System.Xml.XmlEncodedRawTextWriter.EncodeChars(Int32 startOffset, Int32 endOffset, Boolean writeAllToStream) at System.Xml.XmlEncodedRawTextWriter.FlushBuffer() at System.Xml.XmlEncodedRawTextWriter.WriteRawWithCharChecking(Char* pSrcBegin, Char* pSrcEnd) at System.Xml.XmlEncodedRawTextWriter.WriteRaw(String data) at System.Xml.Xsl.Runtime.XmlQueryOutput.WriteRawUnchecked(String text) at <xsl:template match="FieldRef" name="FieldRef_Note_body" mode="Note_body">(XmlQueryRuntime {urn:schemas-microsoft-com:xslt-debug}runtime, XPathNavigator {urn:schemas-microsoft-com:xslt-debug}current, XPathNavigator thisNode) at <xsl:template match="FieldRef" name="Fie... 96a05bbe-f58c-4361-b53a-28c289e9a0c2
08/11/2011 09:02:56.91* w3wp.exe (0x1544) 0x2950 SharePoint Foundation Web Parts 89a1 High ...ldRef_PrintField" mode="PrintField">(XmlQueryRuntime {urn:schemas-microsoft-com:xslt-debug}runtime, XPathNavigator {urn:schemas-microsoft-com:xslt-debug}current, XPathNavigator thisNode, Double Position, String folderUrlAdditionalQueryString) at <xsl:apply-templates mode="PrintFieldWithECB">(XmlQueryRuntime {urn:schemas-microsoft-com:xslt-debug}runtime, XPathNavigator , XPathNavigator ) at <xsl:template match="FieldRef" name="FieldRef_printTableCell_EcbAllowed" mode="printTableCellEcbAllowed">(XmlQueryRuntime {urn:schemas-microsoft-com:xslt-debug}runtime, XPathNavigator {urn:schemas-microsoft-com:xslt-debug}current, XPathNavigator thisNode, String class) at <xsl:template match="Row[../../@ViewStyleID='17']" mode="Item">(XmlQueryRuntime {urn:schemas-microsoft-com:xslt-debug}runt... 96a05bbe-f58c-4361-b53a-28c289e9a0c2
08/11/2011 09:02:56.91* w3wp.exe (0x1544) 0x2950 SharePoint Foundation Web Parts 89a1 High ...ime, XPathNavigator {urn:schemas-microsoft-com:xslt-debug}current, IList1 Fields, IList1 Collapse, Double Position, Double Last) at <xsl:template match="View" mode="RenderView">(XmlQueryRuntime {urn:schemas-microsoft-com:xslt-debug}runtime, XPathNavigator {urn:schemas-microsoft-com:xslt-debug}current) at <xsl:template match="View" mode="full">(XmlQueryRuntime {urn:schemas-microsoft-com:xslt-debug}runtime, XPathNavigator {urn:schemas-microsoft-com:xslt-debug}current, String ShowSelectAllCheckbox) at <xsl:template match="View" name="View_Default_RootTemplate" mode="RootTemplate">(XmlQueryRuntime {urn:schemas-microsoft-com:xslt-debug}runtime, XPathNavigator {urn:schemas-microsoft-com:xslt-debug}current, String ShowSelectAllCheckbox) at <xsl:template match="/">(XmlQueryRuntim... 96a05bbe-f58c-4361-b53a-28c289e9a0c2
08/11/2011 09:02:56.91* w3wp.exe (0x1544) 0x2950 SharePoint Foundation Web Parts 89a1 High ...e {urn:schemas-microsoft-com:xslt-debug}runtime) at Root(XmlQueryRuntime {urn:schemas-microsoft-com:xslt-debug}runtime) at System.Xml.Xsl.XmlILCommand.Execute(Object defaultDocument, XmlResolver dataSources, XsltArgumentList argumentList, XmlWriter writer, Boolean closeWriter) at System.Xml.Xsl.XmlILCommand.Execute(IXPathNavigable contextDocument, XmlResolver dataSources, XsltArgumentList argumentList, XmlWriter results) at System.Xml.Xsl.XslCompiledTransform.Transform(IXPathNavigable input, XsltArgumentList arguments, XmlWriter results) at Microsoft.SharePoint.WebPartPages.DataFormWebPart.ExecuteTransform(XslCompiledTransform xslCompiledTransform, XsltArgumentList xmlArguments, Boolean bDeferExecuteTransform) at Microsoft.SharePoint.WebPartPages.DataFormWebPart.Pre... 96a05bbe-f58c-4361-b53a-28c289e9a0c2
08/11/2011 09:02:56.91* w3wp.exe (0x1544) 0x2950 SharePoint Foundation Web Parts 89a1 High ...pareAndPerformTransform(Boolean bDeferExecuteTransform) 96a05bbe-f58c-4361-b53a-28c289e9a0c2
Closed Aug 12, 2011 at 8:52 PM by ssougnez
Fixed

comments

rixabix wrote Aug 11, 2011 at 10:11 AM

P.s - I am running SharePoint Server 2010 with Enterprise features turned on, Service pack 1 installed and running the June 2011 CU's

Want any more info then let me know :D

Rix

ssougnez wrote Aug 11, 2011 at 10:43 AM

Hello,

thanks for your feedback, I'll work on ASAP but, prior, I have another bug to fix ;-)

ssougnez wrote Aug 11, 2011 at 7:01 PM

Working on it...

ssougnez wrote Aug 11, 2011 at 7:10 PM

Hello,

can you clarify your issue because I'm quite lost... If I understand well, you said that when ImageField solution is deployed, every view that uses grouping fails ? Even view contained in list that does not contains the Image Field ? this issue sounds a bit weird... I tried to reproduce the problem but I haven't success.. I also tried to group view by Image Field and it does not fail...

Furthermore, the logs does not speak about Image FIeld. It is also impossible that a field that is not contained in a view make this view crashing... Can you retest and be more precise in your report ?

I'm not saying that you're wrong, I just try to understand the issue ;-)

rixabix wrote Aug 11, 2011 at 7:35 PM

Hi - yes thats pretty much exactly whats happening.

I will try it on another one of our SharePoint farms today to see if it's related to some configuration we have.

We have kept our environment out of the box as much as possible (only have a couple of 3rd party solutions) and it's reporting in good health.

If required I will take a screen recording of the issue in action and get it to you.

rixabix wrote Aug 11, 2011 at 8:36 PM

OK, I tried recreating this on another farm and it seemed fine so I investigated further and I can now recreate this on a brand new SharePoint installation every time.

Steps:

Add and deploy the solution including the custom field dll into the GAC
Open any site/create a new one
create a custom list
add a "multiple lines of text" column, leave all defaults <-- I think this is the cause?!
Turn on grouping to any column
add some content (text and numbers) to the title and the multiple lines of text colums
do this a few times
expand one of the items in the view - this is when you get the web part error.

Hope that helps.

Kind regards,

Rix

rixabix wrote Aug 11, 2011 at 8:39 PM

p.s. if you recreate the steps I said and you see it not working next retract the solution and you will see that the view now works. Thats why I believe there is some issue/conflict with this solution and something out of the box.

If you need any more testing or anything then just let me know :)

Cheers,

Rix

ssougnez wrote Aug 11, 2011 at 9:12 PM

Wow... I just reproduced the bug... It's definitely weird. I will investigate on that an keep you aware. Currently, I don't have any idea on the bug origin... The grouping option and my custom field are not related at all... Weird... I'll let you know.

ssougnez wrote Aug 11, 2011 at 9:29 PM

Seems to be related to the XSL file. I check that tomorrow

rixabix wrote Aug 11, 2011 at 9:33 PM

Haha yes it is a weird one! Is there any way to get this solution to not deploy globally so that I can enable it on certain web applications and not others?

I know I am probably pushing my luck here and I appriciate your super speedy responses.

Speak soon!

Rich

ssougnez wrote Aug 11, 2011 at 10:00 PM

No it's not possible. Actually, this field rely on a XSL file that has to be deploy in the XSL folder of SharePoint. This file is merged when you do an IISreset and it becomes globally, so you're not able to exclude it from any web application. I recommend you to uninstall it if you need grouping on view. I'll check tomorrow in the early morning to solve this weird bug ;-)

ssougnez wrote Aug 12, 2011 at 6:20 AM

Hello,

it seems that I found the bug. It was an XSL encoding error. Can you please test it and give me a feedback. I'm also waiting for the feedback of your first issue ;-)

Thanks

wrote Aug 12, 2011 at 6:20 AM

rixabix wrote Aug 12, 2011 at 10:39 AM

Just to confirm that both of the issues are now resolved. That was mega quick so thank you for sparing your personal time to do this :)

Rix

wrote Aug 12, 2011 at 8:52 PM

wrote Feb 13, 2013 at 11:49 PM

wrote May 15, 2013 at 5:01 AM