<?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>chez</title>
    <atom:link
      href="https://docs.microsoft.com/archive/blogs/chez/feed.xml"
      rel="self"
      type="application/rss+xml" />
    <link>https://docs.microsoft.com/archive/blogs/chez/feed.xml</link>
    <description />
    <lastBuildDate>Wed, 17 Apr 2019 04:09:29 GMT</lastBuildDate>
    <language>en-US</language>
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <item>
      <title>"There was a problem retrieving data for this field. Updating values in this field is disabled temporarily. You can still update values in other fields."</title>
      <link>https://docs.microsoft.com/archive/blogs/chez/there-was-a-problem-retrieving-data-for-this-field-updating-values-in-this-field-is-disabled-temporarily-you-can-still-update-values-in-other-fields</link>
      <pubDate>Wed, 16 May 2012 05:25:27 GMT</pubDate>
      <dc:creator><![CDATA[Aravind Cheziyan]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.msdn.microsoft.com/chez/2012/05/16/there-was-a-problem-retrieving-data-for-this-field-updating-values-in-this-field-is-disabled-temporarily-you-can-still-update-values-in-other-fields/</guid>
      <description><![CDATA[While trying to update user profile of a user&nbsp;in SharePoint 2010 I got&nbsp;this error&nbsp;...]]></description>
      <content:encoded><![CDATA[<p>While trying to update user profile of a user&nbsp;in SharePoint 2010 I got&nbsp;this error&nbsp; "<em>There was a problem retrieving data for this field. Updating values in this field is disabled temporarily. You can still update values in other fields.</em>". <a href="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/52/19/8420.Untitled.png" original-url="https://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-52-19/8420.Untitled.png"><img border="0" alt="" src="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/52/19/8420.Untitled.png" original-url="https://blogs.msdn.com/resized-image.ashx/__size/550x0/__key/communityserver-blogs-components-weblogfiles/00-00-01-52-19/8420.Untitled.png" /></a></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>The SharePoint farm was using cross-farm services. The "Managed Metadata Web Service" was shared&nbsp;between the farms. This issue can be resolved by enabling "<em>This service application is the default storage location for Keywords</em>." option for the <em>"&nbsp;Managed Metadata Web Service Proxy". </em></p>
<p><a href="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/52/19/1884.Untitled.png" original-url="https://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-52-19/1884.Untitled.png"><img border="0" alt="" src="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/52/19/1884.Untitled.png" original-url="https://blogs.msdn.com/resized-image.ashx/__size/550x0/__key/communityserver-blogs-components-weblogfiles/00-00-01-52-19/1884.Untitled.png" /></a></p>
<p><em></em></p>]]></content:encoded>
    </item>
    <item>
      <title>Newly created Custom Active Directory Attributes Missing From SharePoint 2010 User Properties</title>
      <link>https://docs.microsoft.com/archive/blogs/chez/newly-created-custom-active-directory-attributes-missing-from-sharepoint-2010-user-properties</link>
      <pubDate>Wed, 16 May 2012 05:08:00 GMT</pubDate>
      <dc:creator><![CDATA[Aravind Cheziyan]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.msdn.microsoft.com/chez/2012/05/16/newly-created-custom-active-directory-attributes-missing-from-sharepoint-2010-user-properties/</guid>
      <description><![CDATA[I created&nbsp;few new custom active directory attributes to my User Object. But this newly created...]]></description>
      <content:encoded><![CDATA[<p>I created&nbsp;few new custom active directory attributes to my User Object. But this newly created attributes were not appearing in my "User Profile Properties" under "User Profile Service Application". I tried to sync up my user profile using both "Start Incremental Synchronization/Start Full Synchronization". But still it didnt appear. So, I did few steps after which the new attributes showed up in my "User Profile Properties". The steps are below:</p>
<p>1) Open "ForeFront Identify Manager". This is located at "C:\Program Files\Microsoft Office Servers\14.0\Synchronization Service\UIShell\miisclient.exe"</p>
<p>2) Go to "Management Agents" tab. <a href="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/52/19/0458.Untitled.png" original-url="https://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-52-19/0458.Untitled.png"><img border="0" alt="" src="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/52/19/0458.Untitled.png" original-url="https://blogs.msdn.com/resized-image.ashx/__size/550x0/__key/communityserver-blogs-components-weblogfiles/00-00-01-52-19/0458.Untitled.png" /></a></p>
<p>3) Select the "Active Directory Domain Services" Type.</p>
<p>4) Then click on the "Refresh Schema" on the right right of the screen.</p>
<p>5) This will prompt you to continue. Click "ok"</p>
<p>6) Then it will prompt for for crendentials of the Administrator. Provide the credentials.</p>
<p>7) Then it will update all the Schema between the Active Directory and SharePoint User Properties.</p>
<p>&nbsp;</p>]]></content:encoded>
    </item>
    <item>
      <title>Prerequisites for creating sharepoint 2010 apps in Visual Studio Console Application</title>
      <link>https://docs.microsoft.com/archive/blogs/chez/prerequisites-for-creating-sharepoint-2010-apps-in-visual-studio-console-application</link>
      <pubDate>Wed, 16 May 2012 04:48:00 GMT</pubDate>
      <dc:creator><![CDATA[Aravind Cheziyan]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.msdn.microsoft.com/chez/2012/05/16/prerequisites-for-creating-sharepoint-2010-apps-in-visual-studio-console-application/</guid>
      <description><![CDATA[I wanted to test my sharepoint application using console application using VisualStudio 2010. I was...]]></description>
      <content:encoded><![CDATA[<p><span style="color: black; font-family: 'Arial','sans-serif'; font-size: 9pt;">I wanted to test my sharepoint application using console application using VisualStudio 2010. </span><span style="color: black; font-family: 'Arial','sans-serif'; font-size: 9pt;">I was able to add the reference to "Microsoft.SharePoint" dll. But while compling the code, the compiler was throwing error. To resolve this issue<br />make the followinf changes:<o:p></o:p></span></p>
<p><span style="color: black; font-family: 'Arial','sans-serif'; font-size: 9pt;">1) Select ".Net Framework 3.5" in the New Project Dialog Window while creating a new project.<o:p></o:p></span></p>
<p><span style="color: black; font-family: 'Arial','sans-serif'; font-size: 9pt;">2) For existing project follow this: Go to the Application tab of project properties and verify that .NET Framework Version 3.5 is select as the Target Framework.<o:p></o:p></span></p>
<p><span style="color: black; font-family: 'Arial','sans-serif'; font-size: 9pt;">3) Change the configuration manager to "x64". This can be done by: Go to Configuration Manager, Select x64. <o:p></o:p></span></p>
<p><span style="color: black; font-family: 'Arial','sans-serif'; font-size: 9pt;">4) If x64 is not available select &lt;New&hellip;&gt; and in the New Solution Platform dialog box select x64 as the new platform copying settings from x86 and checking the Create new project platforms check box.</span></p>
<p><span style="color: black; font-family: 'Arial','sans-serif'; font-size: 9pt;"></span>&nbsp;</p>
<p><span style="color: black; font-family: 'Arial','sans-serif'; font-size: 9pt;">hope this helps!</span></p>]]></content:encoded>
    </item>
    <item>
      <title>How to copy files from a machine in different domain through Task Scheduler in Windows</title>
      <link>https://docs.microsoft.com/archive/blogs/chez/how-to-copy-files-from-a-machine-in-different-domain-through-task-scheduler-in-windows</link>
      <pubDate>Mon, 09 Apr 2012 07:13:31 GMT</pubDate>
      <dc:creator><![CDATA[Aravind Cheziyan]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.msdn.microsoft.com/chez/2012/04/09/how-to-copy-files-from-a-machine-in-different-domain-through-task-scheduler-in-windows/</guid>
      <description><![CDATA[I had a&nbsp;requirement to copy&nbsp;files(build output files)&nbsp;from my remote build machine to...]]></description>
      <content:encoded><![CDATA[<p>I had a&nbsp;requirement to copy&nbsp;files(build output files)&nbsp;from my remote build machine to a SharePoint Virtual Machine automatically&nbsp;. These two machines were in two different domains. To get this task done, I created a batch file which will&nbsp;copy the files from build machine to SharePoint Virtual Machine.</p>
<p>The batch file code is simple as shown below :</p>
<p><strong>&nbsp;xcopy \\buildmachine\BuildDrops \\sharepointvm\BuildDrop\Packages /S</strong></p>
<p>But the issue here is I had to provide my credential to access the build machine every time. I was not ready hard code my credentials in the batch file code(since the machine will be accessed by different resources). Then I thought why not use <strong>"Credential Manager"</strong> which is available in <strong>"Control Panel"</strong> in <strong>Windows Server 2008</strong>. Once my credentials are stored here then I need not provide credentials every time the Scheduler Task tries to copy the files from build machine.</p>
<p>The credentials can be stored in the <strong>"Credentials Manager"</strong> permanently using the below command :</p>
<p><strong>net use \\buildmachine\BuildDrops /savecred</strong></p>
<p>This will prompt for user name and password. On successfully validation the user name will be stored in the <strong>"Credentials Manager".</strong></p>
<p><strong></strong></p>]]></content:encoded>
    </item>
  </channel>
</rss>