So I was working with my customer and suddenly in one of the environment with SharePoint 2010 we saw some weird webpart error on one of our Pages and further debugging revealed that only one Web Front End was having the issue and other Front ends were working fine.

The error we looked thru ULS and found that :

Error while
executing web part: System.Exception: ResolveToken returned unexpected object type.   

 at
Microsoft.Xslt.MethodCollection.MethodDescription.SetCode(DynamicILInfo ilInfo, Int32[] fixup, Byte[] ilCode, Byte[] ehTable, Int32 maxStackSize,
MethodCollection methodColl)   

 at
Microsoft.Xslt.MethodCollection.MethodDescription.DefineDynamicMethod(DynamicMethod dm, MethodCollection methodColl)   

 at
Microsoft.Xslt.MethodCollection.CreateDynamicMethods()   

 at Microsoft.Xslt.MethodCollection.GetMethodInfoInternal(Int32
methodNumber)   

 at
Microsoft.Xslt.MethodCollection.GetMethodInfo(Int32
methodNumber)   

 at
Microsoft.Xslt.STransform.GetCompiledTransform()   

 at
Microsoft.SharePoint.WebPartPages.BaseXsltListWebPart.LoadXslCompiledTransform(WSSXmlUrlResolver
someXmlResolver)   

 at
Microsoft.SharePoint.WebPartPages.DataFormWebPart.GetXslCompiledTransform()   

 at
Microsoft.SharePoint.WebPartPages.DataFormWebPart.PrepareAndPerformTransform(Boolean
bDeferExecuteTransform)

Tried to look around stuff and found nothing in the ULS log or even on the SQL Server permissioning, so finally out of curiosity just recycled the App-Pool for that web-application having the issue and that's it , it resolved the issue all WFEs now in good shape.

He moved the site collection from a top level site collection (https://test-moss:6001) to a path based site (https://portal.test.ca/ipo/) using powershell Restore-SPSite command. After the restore we are experience ‘File not found’ error although we can see all files using Sharepoint Designer and also don’t get error message in
the log.  

Note: 
following thread also talk about similar issues, where I posted the answer as well but thought I will blog it in case if someone needs it:

https://social.technet.microsoft.com/Forums/en/sharepoint2010setup/thread/949c9bfd-be03-470e-832f-a415962b7248

 
Answer:

1. 
   Check in the ULS log when you try to browse to the newly restored site collection, check if there is anything in ULS (enable verbose logging).
2. 
   Open the site in SPD and open the _cts under All Files, open the Document set content type folder and then open the docsethomepage.aspx page (should be inside it). Now open this page in Advanced edit mode and check if you have any such tags “/_controltemplates/” strings with “~/_controltemplates “ (Note: the difference “~”difference. So for e.g.:

                             <%@ Register TagPrefix="wssuc"TagName="LinksTable" src="https://blogs.msdn.com/_controltemplates/LinksTable.ascx" %>

Should now look like      <%@ Register TagPrefix="wssuc" TagName="LinksTable" src="~/_controltemplates/LinksTable.ascx" %>

You should fine multiple such controltemplate entries replace all of them wth “~” before it and then save that page

3. Once you have done that go to the site content types gallery and select the “Document Set” content type and go to its setting and then check the “Update the Welcome Page of Document Sets inheriting from this content type” checkbox  and make sure to check the yes option for the Update all content types inheriting from this type. 

Hopefully this should get you back in shape on the site collection, other thing you can check is the Master Page for that site collection as well.

When we browse to that List again to my surpirse the default View disappears and is not even visible in the list of default views (List settings). But when I open the list in SharePoint Designer I can see the list for (AllItems.aspx) there. So after some rumbling with powershell and List Object model I found that whenever we save the default view by changing the Listview to XSLT Listview webpart (to get the checkbox and ECB to work) the AllItems.aspx form is marked hidden. So to solve this issue I used a very simply powershell and got this one to work (now the List view shows up in the List settings as default view and also it is visible)

I don’t know why but as soon as
we modify the view using SPD it just marks the view as hidden, I used following
powershell to fix it and get the view back:

$sitecoll = get-SpSite (https://mysitecollectioname.company.com);

//Make sure the List name is correct

$list =$sitecoll.RootWeb.Lists["MyListName"]       
 

// Make sure the View Name is correct some lists might have a different
view name and sometimes the view name is “All Items” with a space
not “AllItems”

$view2 = $list.Views["AllItems"]                          
               

$view2.DefaultView =
$True       

$view2.Hidden = $False

$view2.Update()

Hope this helps someone in future in case if you dont see the checkboxes or you dont see the ECB menu working and giving you javascript error.

Question:-

We have deployed a content type to Content Type Hub (CT1) thru a wsp and now we have 2 more content types which are derived from that content type (CT1). Content type hub is in different farm so wsp is deployed there and the consuming Farm doesn't have that wsp but the other 2 content types (CT2 and CT3) are deployed thru wsp to the Content Farm. 

So basically

1. Content Type Hub Farm contains one wsp with CT1

2. Content Farm contains one wsp with CT2 and CT3 (so no wsp for CT1 on this farm) 

Now whenever the CT2 and CT3 wsp is deployed to the content Farm all the Publishing content type (out of the box) are not displayed in the content type gallery. But when I deploy the wsp for CT1 to the Content Farm everything comes back to normalcy, so I am not sure if the CT1 wsp needs to be deployed to the Content Farm as well?

 Answer:-

CT1 wsp has to be deployed to the content farm, as the Content Type Hub-Subscriber thing uses the content deployment (API) behind the scene, so any custom stuffs has to be there in the target.  Exceptions can be visible in the ULS Logs (for the Subscriber Timer Job) in your Content Farm.

Hello All,

I have been struggling with the FULL Sync for USer Profile Application for last 2-3 weeks and all the time the Memory on the Server was peaking out, we added RAM to the Servers thinking we were running low on the RAM for App Server we went from 8GB to 32GB RAM the max on the Windows Server 2008 R2 Standard box. I tried to find all possible causes and was really not able to find out things yes there were few things on the planning side which also went wrong and hence I decided to write this blog. Let me get to the core things:-

What you should advance plan:-

1. Make sure All the Active Directory connections and EXCLUSION Filters for those are correct. PLEASE EXECUTE ADSI QUERIES to find the exact number of accounts returned. THIS IS VERY IMPORTANT planning phase. Work with you AD team to get this done, make sure the Filters to be applied are with correct AND or OR condition as the results change vastly.

2. Make sure Hardware planning is done properly and you have planned for enough resources for the UPA Sync. I would recommend minimum of 16GB of RAM for UPA Sync server. Yes you can run the UPA service on more than one box and UPA Sync on only one box.

3. Make sure the DOP (Degree of Parallelism) on SQL Server for SharePoint value is set to 1 this is important guidance from MICROSOFT and should be followed.

4. PLEASE PLEASE PLEASE while planning for UPA start in advance way in advance and start running POCs I would say atleast a month before your PROD go live, the FULL Sync is improved in SP 2010 and it takes a little longer than in SharePoint 2007 and you might hit road blocks so please plan in advance.

5. PLEASE rely 100% on ULS logs... yes it contains everything and it is your torch light for everything... it has helped me a lot.

Now coming to my Memory Leak issue, where the Memory was spiking up to the max available on the server (32GB) in my case, all the other phases in the Full Sync job go well i.e. DS_FullImport, DS_FullSync, MOSS_FullSync all go well it is only the last stage which is MOSS_Export which is putting the Profiles in SharePoint 2010 is the one getting affected.  So after spending almost 2-3 weeks on this I couldn't find the reason, yes I worked with the Microsoft Premier support and they took the Memory dump during the Memory spike up and told me that somehow the MMS store was getting pulled into the Memory and the cache was building up.

So finally l opened the ULS logs (LIVE) when the MOSS_Export was going on and found lots of these exceptions:

Exception while updating properties for ''northamerica\kanyadas': Property: SPS-ProxyAddresses, Exception System.ArgumentException: The value 'X400:c=US;a= ;p=SCHP;o=Hub-Americas;s=srvdasilcla;g=CustomNamed;' is invalid. It probably contains invalid characters or is too long. Parameter name: termLabel

at Microsoft.SharePoint.Taxonomy.Internal.CommonValidator.ValidateName(String name, String parameterName)

at Microsoft.SharePoint.Taxonomy.TermSet.GetTerms(String termLabel, Boolean trimUnavailable)

at Microsoft.Office.Server.UserProfiles.UserProfileGlobal.ValidatedTaxonomicValue(CoreProperty prop, Object value)

at Microsoft.Office.Server.UserProfiles.UserProfileGlobal.ValidatedSingleValue(Object value, ProfileSubtypeProperty prop, PropertyDataType propDataType, UserFormat userFormat, UserProfileApplicationProxy userProfileApplicationProxy, Guid partitionID, SiteContext si)

at Microsoft.Office.Server.UserProfiles.UserProfile.BulkPropertiesUpdate(Int64 importExportId, Hashtable properties, String strAccountName).

Note the highlighting (yellow) yes the SPS-ProxyAddresses is a multi-value string and we had mapped it to ProxyAddresses field (As the way it was in 2010) and because it is multivalue string it was trying to validate things with TermStore (Enterprise Keywords) before adding and that was causing the Memory cache to be build (we had 5 AD connections so 5 mappings for each Profile Property). One of my colleagues helped me understand the Importance of this field (SPS-ProxyAddreses) w.r.t. SharePoint 2010 and following was it:- SharePoint only imports proxyAddresses to extract the SIP address and not to actually use the proxyAddresses. But in our case we had already mapped our SIP Address feild to AD field EMAIL ADDRESS so we really didnt rely on it much. So we went ahead and removed the SPS-ProxyAddresses mapping that we had done to ProxyAddresses Feild and we re-ran the Full Sync and viola after 3 days of running into Full Sync MOSS Export stage started and THANK GOD the MEMORY SPIKES WERE GONE :-) :-).

My only BIG Adivce to you all is please please rely on the ULS Logs to show you the path and also please plan ahead for UPA Sync way way way ahead I would say. Check your mappings try to compare it with the out of the box UPA mappings and make sure all are in inline. This will help you save a lot of time and lot of customers would appreciate that. In the end please don't forget to read Spencer's blogs about UPA they are concise and very helpful. Also I would like to thank Spencer Harbar as all along he helped me a lot with some good advice so thank you buddy!!!.

Whenever we try to load a Edit Profile Page it gives an error:

Error:

“The server method ‘ValidateTerms’ failed”
“The server method “GetMatches” failed

This error seems to be like coming from Javascript (out of the box) and when I tried to trace it with Fiddler I see Following requests which go as 404 but when you take a look at the Inspector section of the Fidller I could see the data was making it thru but was not showing up on the Page:-

 Solution:

To keep everyone updated the issue was resolved, the JSON handler entry in the web.config (of our Mysite web-app as we were accessing EditProfile page from mysite) was missing and hence the errors.

After adding that entry everything started showing up.

 <add name="JSONHandlerFactory" path="*.json" verb="*" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" resourceType="Unspecified" preCondition="integratedMode" />

           Page.ClientScript.RegisterStartupScript(GetType(), "MyuniqueGUID", xml, true);

 ScriptManager.RegisterStartupScript(this, GetType(), Guid.NewGuid().ToString()  , "alert('hello baby');", true); 

Code that is not working in SANDBOX:

protected void Page_Load(object sender, EventArgs e)

        {

            _nodeSelection.EnableViewState = false;

            _publish.Click += HandlePublishClick;

            // TODO: Do validation here and write out error if no values for the key fields.

            int itemID = int.Parse(HttpContext.Current.Request.QueryString["ItemID"]);

            Guid listID = new Guid(HttpContext.Current.Request.QueryString["ListId"]);

            _document = new Document(Convert.ToInt32(itemID), listID);

            _documentName.Text = _document.Name;

            string xml = string.Format(@"var __xml = ""<root><item id='n1' parent_id='0' state='open'><content><name>1 TITLE PAGE </name></content></item><item id='n2' parent_id='0' state='open'><content><name>TRIAL DESIGN</name></content></item><item id='n2-1' parent_id='n2' state='closed'><content><name>Trial Design</name></content></item></root>"";");

           Page.ClientScript.RegisterStartupScript(GetType(), "MyuniqueGUID", xml, true);

        }

So after some debugging and talking to some folks internally @ Microsoft we found following two things:

1. The Page class is not available in a sandbox solution.

2. System.Web.UI.ClientScriptManager is not supported In the sandbox.

So then Paul Stubb provided a sample on how this can be worked around and Sowmyan was kind enough to share it with us, following is the sample code:

namespace ClientOMProject.ListOperationsVisualWebPart {

    using System.Web;

    using System.Text.RegularExpressions;

    using Microsoft.SharePoint.WebPartPages;

    using Microsoft.SharePoint.WebControls;

    using System.Web.Security;

    using Microsoft.SharePoint.Utilities;

    using System;

    using System.Collections;

    using System.Collections.Specialized;

    using Microsoft.SharePoint;

    using System.Web.UI;

    using System.Web.Profile;

    using System.Text;

    using System.Web.Caching;

    using System.Web.UI.WebControls;

    using System.Configuration;

    using System.Web.UI.WebControls.WebParts;

    using System.Web.SessionState;

    using System.Web.UI.HtmlControls;

    public partial class ListOperationsVisualWebPart {

        public static implicit operator global::System.Web.UI.TemplateControl(ListOperationsVisualWebPart target)

        {

            return target == null ? null : target.TemplateControl;

        }

        [global::System.ComponentModel.EditorBrowsableAttribute(global::System.ComponentModel.EditorBrowsableState.Never)]

        private void @__BuildControlTree(global::ClientOMProject.ListOperationsVisualWebPart.ListOperationsVisualWebPart @__ctrl) {

            System.Web.UI.IParserAccessor @__parser = ((System.Web.UI.IParserAccessor)(@__ctrl));

            @__parser.AddParsedSubObject(new System.Web.UI.LiteralControl(@"

<script src=""/SiteAssets/ListOperations.js"" type=""text/javascript""></script>

<script language=""javascript"" type=""text/javascript"">

// <![CDATA[

    function CreateButton_onclick() {

        CreateList();

    }

    function AddButton_onclick() {

        AddListItem();

    }

    function ReadButton_onclick() {

        ReadListItem();

    }

    function UpdateButton_onclick() {

        UpdateListItem();

    }

    function DeleteButton_onclick() {

        DeleteListItems();

    }

    // ]]>

</script>

<p><input id=""CreateButton"" type=""button"" value=""Create List""

        style=""width: 150px"" onclick=""CreateButton_onclick()"" /></p>

<p><input id=""AddButton"" type=""button"" value=""Add List Item""

        style=""width: 150px"" onclick=""AddButton_onclick()"" /></p>

<p><input id=""ReadButton"" type=""button"" value=""Read List Item""

        style=""width: 150px"" onclick=""return ReadButton_onclick()"" /></p>

<p><input id=""UpdateButton"" type=""button"" value=""Update List Item""

        style=""width: 150px"" onclick=""return UpdateButton_onclick()"" /></p>

<p><input id=""DeleteButton"" type=""button"" value=""Delete List Item""

        style=""width: 150px"" onclick=""return DeleteButton_onclick()"" /></p>

"));

        }

        private void InitializeControl() {

            this.@__BuildControlTree(this);

            this.Load += new global::System.EventHandler(this.Page_Load);

        }

       //CALL THE InitializeControl() above method in the onInit() of the webpart code

        [global::System.ComponentModel.EditorBrowsableAttribute(global::System.ComponentModel.EditorBrowsableState.Never)]

        protected virtual object Eval(string expression) {

            return global::System.Web.UI.DataBinder.Eval(this.Page.GetDataItem(), expression);

        }

        [global::System.ComponentModel.EditorBrowsableAttribute(global::System.ComponentModel.EditorBrowsableState.Never)]

        protected virtual string Eval(string expression, string format) {

            return global::System.Web.UI.DataBinder.Eval(this.Page.GetDataItem(), expression, format);

        }

    }

}

Hope that helps someone save some time. 

File Not Found.   at Microsoft.SharePoint.Library.SPRequestInternalClass.OpenWeb(String bstrUrl, String& pbstrServerRelativeUrl, String& pbstrTitle, String& pbstrDescription, Guid& pguidID, String& pbstrRequestAccessEmail, UInt32& pwebVersion, Guid& pguidScopeId, UInt32& pnAuthorID, UInt32& pnLanguage, UInt32& pnLocale, UInt16& pnTimeZone, Boolean& bTime24, Int16& pnCollation, UInt32& pnCollationLCID, Int16& pnCalendarType, Int16& pnAdjustHijriDays, Int16& pnAltCalendarType, Boolean& pbShowWeeks, Int16& pnFirstWeekOfYear, UInt32& pnFirstDayOfWeek, Int16& pnWorkDays, Int16& pnWorkDayStartHour, Int16& pnWorkDayEndHour, Int16& pnMeetingCount, Int32& plFlags, Boolean& bConnectedToPortal, String& pbstrPortalUrl, String& pbstrPortalName, Int32& plWebTemplateId, Int16& pnProvisionConfig, String& pbstrDefaultTheme, String& pbstrDefaultThemeCSSUrl, String& pbstrAlternateCSSUrl, String& pbstrCustomizedCssFileList, String& pbstrCustomJSUrl, String& pbstrAlternateHeaderUrl, String& pbstrMasterUrl, String& pbstrCustomMasterUrl, String& pbstrSiteLogoUrl, String& pbstrSiteLogoDescription, Object& pvarUser, Boolean& pvarIsAuditor, UInt64& ppermMask, Boolean& bUserIsSiteAdmin, Boolean& bHasUniquePerm, Guid& pguidUserInfoListID, Guid& pguidUniqueNavParent, Int32& plSiteFlags, DateTime& pdtLastContentChange, DateTime& pdtLastSecurityChange, String& pbstrWelcomePage)

 OR

System.IO.DirectoryNotFoundException: Could not find a part of the path 'D:\Usage
Analysis Logs'.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.Directory.InternalCreateDirectory(String fullPath, String path,
DirectorySecurity dirSecurity)
at System.IO.DirectoryInfo.Create(DirectorySecurity directorySecurity)
at
Microsoft.SharePoint.Administration.SPProvisioningAssistant.CreateDirectory(Director
yInfo di, Boolean secureAdminAccess)
at Microsoft.SharePoint.Administration.SPServer.CreateDirectory(String path,
Boolean secureAdminAccess)
at Microsoft.SharePoint.Administration.SPServer.CreateDirectory(String path)
at
Microsoft.SharePoint.Administration.SPUsageSettings.EnsureLogFileDirectories(SPFarm
farm)
at Microsoft.SharePoint.Administration.SPWebApplication.Provision()
at Microsoft.SharePoint.Administration.SPWebServiceInstance.Provision()
at Microsoft.SharePoint.Administration.SPFarm.Join()
at
Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.CreateOrConnec
tConfigDb()
at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.Run()
at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

To resolve this error we tried following things:

1.We removed and added the same contentdb (restored the backup), but you i.e. basically we tried removing the original contentdb, and then re-added it n the web-app level using the Central Admin=>Application  Management=>Content Databases. That also didnt help.

2. Tried accessing /_layouts/viewlsts.aspx work. That also threw the same error.

3. Tried accessing the/_layouts/settings.aspx work. That also threw the same error.

4. Checked all the solution files and they were also deployed properly and all artifacts were present on the file system.

Then after carefully looking at the error file not found appeared a file system error rather than a contentdb missing file error, so as Suggested by my colleague Andres Montenergo we checked if:

- There is a missing site definition or file, you might want to try running process monitor (procmon) while the problem happens and look for 'file not found' errors (filter the w3wp.exe process name).

- The contentdb is corrupt. Using SQL Analyzer, try to see how the tables looks like (for instance if you see data in alldocs, etc).

- The configdb has a reference (an id) to an old site collection but the same path.

And Finally it turned out that the GLOBAL.asax was missing and our site collection used some of the session used in that file, after fixing the Global.asax file our site collection was back up.

Hope this helps someone in case if you see any error like DirectoryNotFoundException or FileNotFound. Also A Big Thank you to Andres Montenegro as he sparked the idea to check the file system artifacts again.

Your Web browser will have problems displaying this web page. Changes to the site may not function properly. For a better  experience, please update your browser to its latest version.

In case if you would like to remove this warning, just remov the following element from the Master Page:

<SharePoint:WarnOnUnsupportedBrowsers runat="server"/>

But all said you should try to upgrade the browsers to IE 8.0, its good and always better for rendering other stuff. Although this solutionis only to supress/remove the warning. Thanks to Jie Li for pointing this solution.