<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="https://www.w3.org/2005/Atom" xmlns:sy="https://purl.org/rss/1.0/modules/syndication/" xmlns:dc="https://purl.org/dc/elements/1.1/" xmlns:content="https://purl.org/rss/1.0/modules/content/" xmlns:wfw="https://wellformedweb.org/CommentAPI/" xmlns:slash="https://purl.org/rss/1.0/modules/slash/"
  version="2.0">
  <channel>
    <title>Sharepoint 2010</title>
    <atom:link
      href="https://docs.microsoft.com/archive/blogs/sharepoint_2010/feed.xml"
      rel="self"
      type="application/rss+xml" />
    <link>https://docs.microsoft.com/archive/blogs/sharepoint_2010/feed.xml</link>
    <description />
    <lastBuildDate>Wed, 17 Apr 2019 03:51:47 GMT</lastBuildDate>
    <language>en-US</language>
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <item>
      <title>Unable to create a "Send to Connection"- verification failed -url is a not a valid routing destination</title>
      <link>https://docs.microsoft.com/archive/blogs/sharepoint_2010/unable-to-create-a-send-to-connection-verification-failed-url-is-a-not-a-valid-routing-destination</link>
      <pubDate>Mon, 13 Jun 2011 13:15:00 GMT</pubDate>
      <dc:creator><![CDATA[GMallya]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.msdn.microsoft.com/sharepoint_2010/2011/06/13/unable-to-create-a-send-to-connection-verification-failed-url-is-a-not-a-valid-routing-destination/</guid>
      <description><![CDATA[ISSUE:&nbsp;Unable to successfully create a send to connection.
&nbsp;When creating the Send to...]]></description>
      <content:encoded><![CDATA[<p><span style="text-decoration: underline;"><strong>ISSUE:</strong></span><br />&nbsp;<br />Unable to successfully create a send to connection.</p>
<p>&nbsp;When creating the Send to connection from Sharepoint 2010 Central Administration and click on Test URL for the Destination URL , we get the following error </p>
<p><strong>"verification failed -url is a not a valid routing destination"</strong></p>
<p>we see the following entry in the ULS logs </p>
<p>Url validation failed for <a href="https://pasrctemp.fmr.com/sites/pasrcrecordcenter/_vti_bin/OfficialFile.asmx">https://gmallya.test.com/sites/testrecordcenter/_vti_bin/OfficialFile.asmx</a>&nbsp; during Record and document center connection configuration with exception The request failed with <span style="background-color: #00ccff;">HTTP status 401: Unauthorized</span>.:&nbsp; at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)&nbsp;&nbsp;&nbsp;&nbsp; at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)&nbsp;&nbsp;&nbsp;&nbsp; at Microsoft.SharePoint.OfficialFileSoap.GetServerInfo()&nbsp;&nbsp;&nbsp;&nbsp; at Microsoft.SharePoint.ApplicationPages.OfficialFileAdminPage.&lt;&gt;c__DisplayClass2.&lt;IsValidUriToRouter&gt;b__0()&nbsp;&nbsp;&nbsp;&nbsp; at Microsoft.SharePoint.SPSecurity.&lt;&gt;c__DisplayClass4.&lt;RunWithElevatedPrivileges&gt;b__2()&nbsp;&nbsp;&nbsp;&nbsp; at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)&nbsp;&nbsp;&nbsp;&nbsp; at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param)&nbsp;&nbsp;&nbsp;&nbsp; at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode)&nbsp;&nbsp;&nbsp;&nbsp; at Microsoft.SharePoint.ApplicationPages.OfficialFileAdminPage.IsValidUriToRouter(Uri uriToValidate)</p>
<p><span style="text-decoration: underline;"><strong>CAUSE</strong></span></p>
<p>Loop Back Check registry value is Enabled </p>
<p><span style="text-decoration: underline;"><strong>RESOLUTION</strong></span></p>
<p><span style="text-decoration: underline;"><strong>Follow the article to disable the loop back check- ﻿﻿</strong></span></p>
<p><span style="text-decoration: underline;"><strong>﻿</strong></span>Click Start, click Run, type regedit, and then click OK.&nbsp;</p>
<ol>
<li style="text-align: left;">In Registry Editor, locate and then click the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa</li>
<li style="text-align: left;">Right-click Lsa, point to New, and then click DWORD Value. </li>
<li style="text-align: left;">Type DisableLoopbackCheck, and then press ENTER. </li>
<li style="text-align: left;">Right-click DisableLoopbackCheck, and then click Modify.&nbsp;</li>
<li style="text-align: left;">In the Value data box, type 1, and then click OK. </li>
<li style="text-align: left;">Quit Registry Editor, and then restart your computer.</li>
</ol>
<p style="text-align: left;">Now create a "Send To" connection successfully..!!</p>
<p style="text-align: left;">&nbsp;</p>
<p style="text-align: left;">﻿</p>
<p style="text-align: left;">&nbsp;</p>]]></content:encoded>
    </item>
    <item>
      <title>Enterprise Wiki site has categories webpart greyed out.</title>
      <link>https://docs.microsoft.com/archive/blogs/sharepoint_2010/enterprise-wiki-site-has-categories-webpart-greyed-out</link>
      <pubDate>Thu, 12 May 2011 19:57:30 GMT</pubDate>
      <dc:creator><![CDATA[GMallya]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.msdn.microsoft.com/sharepoint_2010/2011/05/12/enterprise-wiki-site-has-categories-webpart-greyed-out/</guid>
      <description><![CDATA[I was working on a case.. which took a while to figure out why the out of the box web part in the...]]></description>
      <content:encoded><![CDATA[<p>I was working on a case.. which took a while to figure out why the out of the box web part in the wiki site was greyed out. The site had zero customization and would happen on any new site created. Here is some details on the issue and the resolution for this behavior.</p>
<p>We have site created with the enterprise wiki template. you see the categories web part in the site by default but it greyed out and would not allow you to add any new items to the categories. </p>
<p><strong>Reason for this behavior&nbsp;is, </strong>When you create a wiki site a wiki category is added in the Managed metadata&nbsp; service application as a term set . Any new categories added in the wiki site would have a reference in the Managed metadata service application. </p>
<p>Now for some unknown reason,we end up in a situation to delete the current managed metadata service application. Although we create a brand new Managed metadata service application successfully, the reference to this wiki category is lost .we would not have it in the new Managed metatdata service application..</p>
<p><strong>How do we resolve this???</strong> we need to associate the Wiki site back to a category/group in the MMS application.</p>
<p><br />Here are the steps that if followed:</p>
<ol>
<li>Create a new term set in the MMS application.</li>
<li>Browse to the wiki site&nbsp; and then to the site settings.</li>
<li>Click on the site content types</li>
<li>we see a "Enterprise wiki page"&nbsp;content type under "Page layout content types"</li>
<li>Click on "Wiki Categories" which is a manage metadata column.</li>
<li>Click on "Edit site column" </li>
<li>In the&nbsp; MMS section we need to choose the term set and click ok</li>
</ol>
<p>We would not be able to see the default wiki categories because the MMS application which had the category created is deleted. So we would have to add new keywords explicitly.</p>
<p>... If you are seeing the categories web part greyed out in the wiki site, hopefully .. this would fix the issue..!!</p>
<p><b>&nbsp;</b></p>
<p><b>Gayathri Mallya&nbsp; </b></p>
<p><b>Microsoft Office Sharepoint Support</b></p>
<p>&nbsp;</p>
<p><br /><br /><br /><br />&nbsp;</p>]]></content:encoded>
    </item>
  </channel>
</rss>