tag:blogger.com,1999:blog-31559629023352592162024-02-07T16:14:24.501-05:00Musings on MicrosoftInformation about Microsoft SharePoint and Microsoft Dynamics CRMMatthew Churillahttp://www.blogger.com/profile/06699782042171994247noreply@blogger.comBlogger14125tag:blogger.com,1999:blog-3155962902335259216.post-38253601825644024132013-06-28T09:52:00.000-04:002013-06-28T10:08:21.121-04:00Change Site DefinitionWhen an upgrade is performed on a SharePoint environment chances are some items will get lost in the upgrade. This is especially true if your 2007 environment took advantage of the FAB40 template set or someone went crazy downloading free site templates from the internet. These items do not block a successful upgrade and sites may even continue to work as expected after the upgrade has been performed. However these do leave your content databases in a weird state and central administration does warn about these missing items so it is best to cleanup your content databases to remove these broken references. There are a number of possible errors that can be presented and for most of them the way to resolve the problem is straight forward. For reference I have included these here.<br />
<br />
<a href="http://get-spscripts.com/2011/08/diagnose-missingwebpart-and.html">MissingWebPart and Missing Assembly</a><br />
<a href="http://get-spscripts.com/2011/06/removing-features-from-content-database.html">MissingFeature</a><br />
<a href="http://get-spscripts.com/2011/06/diagnosing-missingsetupfile-issues-from.html">MissingSetupFile</a><br />
<br />
However there is no well known process for dealing with MissingSiteDefinition references which look like this message:<br />
<br />
[MissingSiteDefinition] 1 Sites in database [] has reference(s) to a
missing site definition, Id = [75820], Lcid = [1033]. The site
definitions with Id 75820 is referenced in the database [], but is not
installed on the current farm. The missing site definition may cause
upgrade to fail. Please install any solution which contains the site
definition and restart upgrade if necessary.<br />
<br />
The site definition does not seem to be used or depended on anywhere inside of SharePoint, it only seems to be used for loading resources from the 14 hive. However there is no way through stsadm or powershell to change the site definition for an existing site which means once a site is created there is no way to change the site definition. This can be very troublesome because a lot of backup / restore and import / export commands require an existing site with the same site definition as the original, making these processes impossible to execute on sites with a missing site definition. If you find yourself in this situation I have developed this process for changing the site definition of a site back to a blank site.<br />
<br />
<b>NOTE: </b>This process involves editing files that Microsoft does not support editing for, so this process is use at your own risk. Make sure to implementing extensive testing before deleting the original content.<br />
<br />
<ol>
<li>Create a new blank site that will be used for testing. </li>
<li>In powershell export original site: Export-SPWeb http://site.url/ -IncludeVersions 4 -IncludeUserSecurity -path \\put\files\here -<b>NoFileCompression</b> (Exporting with no file compression is the key make sure to include it)</li>
<li>Edit Manifest.xml change the Configuration attribute to 1 if it is another number. </li>
<li>In the Manifest.xml file change the attribute WebTemplate to "STS" </li>
<li>Edit Requirements.xml change the attribute WebTemplate ID to STS#1 </li>
<li>In powershell import into the previously created blank site: Import-SPWeb https://blank.url/ -path \\put\files\here -NoFileCompression -IncludeUserSecurity </li>
<li>Verify test site! </li>
<li>Delete original site </li>
<li>Create new blank site with original site's url and site collection administrators</li>
<li>Import into the just created blank site using same command and files as in step #5 </li>
<li>Verify new site</li>
<li>Empty recycle bins</li>
</ol>
<br />Matthew Churillahttp://www.blogger.com/profile/06699782042171994247noreply@blogger.com1tag:blogger.com,1999:blog-3155962902335259216.post-22630490100052682422013-02-14T14:47:00.001-05:002013-02-14T14:47:11.340-05:00Refreshing Email Enabled Lists after MigrationAnytime you move your content databases to a farm using the database
attach method in SharePoint 2010 (and i'm guessing SharePoint 2013) you
need will need to refresh all of your email enabled lists. The reason
for this is because SharePoint stores the email enabled lists inside of
the Farm Configuration Database and since the Farm Configuration
database doesn't move during a database attach migration you need to
refresh all of your email enabled lists back into the Farm Configuration
Database. The best way to do this is with a short script that will
iterate through all sites and perform this function. Here is the code to perform this action:<br />
<br />
<div class="container">
<div class="line number1 index0 alt2">
<code class="ps keyword">Add-PSSnapin</code> <code class="ps plain">Microsoft.SharePoint.PowerShell </code><code class="ps keyword">-ea</code> <code class="ps plain">0</code></div>
<div class="line number2 index1 alt1">
</div>
<div class="line number3 index2 alt2">
<code class="ps value">$sites</code> <code class="ps plain">= Get</code><code class="ps keyword">-SPSite -LIMIT all</code></div>
<div class="line number4 index3 alt1">
</div>
<div class="line number5 index4 alt2">
<code class="ps keyword">foreach</code> <code class="ps plain">(</code><code class="ps value">$site</code> <code class="ps plain">in </code><code class="ps value">$sites</code><code class="ps plain">) { </code></div>
<div class="line number6 index5 alt1">
<code class="ps spaces"> </code><code class="ps value">$site</code><code class="ps plain">.RefreshEmailEnabledObjects() </code></div>
<div class="line number7 index6 alt2">
<code class="ps spaces"> </code><code class="ps value">$site</code><code class="ps plain">.Dispose() </code></div>
<div class="line number8 index7 alt1">
<code class="ps plain">}</code></div>
</div>
<br />
I found this code on this blog and he has a very good write on this issue: <a href="http://get-spchopps.com/post/2012/08/23/Fixing-Incoming-Email-after-Migration-to-SharePoint-2010.aspx">http://get-spchopps.com/post/2012/08/23/Fixing-Incoming-Email-after-Migration-to-SharePoint-2010.aspx.</a><br />
<br />I made a slight modification to the script that enables it to enurmate all sites in your farm and not just using a limited result set. Matthew Churillahttp://www.blogger.com/profile/06699782042171994247noreply@blogger.com0tag:blogger.com,1999:blog-3155962902335259216.post-34002641576481828892013-02-14T09:43:00.002-05:002013-02-14T10:09:17.895-05:00Setting a Custom Color Palette on Chart Web PartsThe Chart Web Part is a SharePoint 2010 component that lets users generate charts from SharePoint lists or from BDC data. This chart is great for providing simple data visualization that is embedded in SharePoint web part pages. I had to do a project using this web part so I had to dig a little deeper into how to use the web part effectively.<br />
<br />
The chart web part seems to just be an extension of the Microsoft .NET Chart class that allows you to specify the properties of the class via XML that is embedded in your SharePoint Web Part Page. There are wizards and an advanced interface available on the web part pages to configure this underlying XML, but there are more options available to you if you are willing to dig in and edit your page via SharePoint Designer. Using SharePoint designer I was able to overcome what seems like a simple problem, how do I use a custom color palette on my chart?<br />
<br />
I am going to outline the steps you need to take in order to add custom colors to a chart. You can skip some of these steps and go straight to editing the XML, but I find that by completing my charts first and then editing the XML there is a lower chance of me accidentally blowing away my custom settings by going through a wizard.<br />
<br />
<ol>
<li>Add a chart web part to your page.</li>
<li>Connect the chart to your data source using the data connection wizard. </li>
<li>Start the chart customization wizard to format your chart.</li>
<li>Select your chart type (type doesn't matter for custom palettes)</li>
<li>On the Appearance Themes tab:</li>
<ol>
<li>Set the Theme to "Custom"</li>
<li>Set the Transparency to "Custom"</li>
</ol>
<li>Finish the wizard setting any values other than the two above.</li>
<li> Launch SharePoint Designer and open the source of your page.</li>
<li>Search for the String "PaletteCustomColors" this will take you to the embedded XML element for the custom palette.</li>
<li>The palette is ten semicolon(;) delimited values that you can set to whatever colors you want. For how to specify color values in this section see the paragraph below. </li>
<li>Save your page source and refresh the page, you should now see your custom colors!</li>
</ol>
There is a little trick to defining custom colors through this method and it will become appearant as soon as you open the file. All colors have a four number format ex. (204, 255, 227, 130) this really threw me for a loop at first because everyone knows that colors are usually specified with three numbers in an RGB format. It seems that Microsoft is starting to encourage the use of a four digit color specification where the extra number (the first in this case) is the transparency of the object. Transparency is based on the percentage equal to the first number divided by 255, so 0 would be transparent and 255 would be solid. In this situation a solid red would be 255, 255, 0, 0 and a half transparent blue would be 127, 0, 0 255.<br />
<br />
Now that you know how to define colors you can go in and set your own palette of ten colors for use on your chart! The chart web part will assign colors to your series based on when the values occur so the first series value will map to the first color and the next to the second, etc...<br />
<br />
You must be careful when you use this editing XML method for changing charts because if you later use the wizards to edit your charts they may remove your customized values. I have found that color is pretty stable and your settings will not be deleted unless you go into the wizard and change the color palette, transparency, or chart type. But if you use this method to edit other values they may be wiped out by using the wizard. <br />
<br />
For reference you can find the documentation for the chart class here: <a href="http://technet.microsoft.com/en-us/system.web.ui.datavisualization.charting">http://technet.microsoft.com/en-us/system.web.ui.datavisualization.charting</a> this documentation will show you the properties that are available on the chart class and that may be usable via the editing XML method. <br />
<br />
Good luck and happy charting! Matthew Churillahttp://www.blogger.com/profile/06699782042171994247noreply@blogger.com2tag:blogger.com,1999:blog-3155962902335259216.post-19923442506561672392013-02-08T11:30:00.003-05:002013-02-08T11:36:00.409-05:00Long time no post, hopefully things coming soonSorry for no posts in a while but work has been a little crazy over the past year and I haven't had a lot of time to focus on SharePoint and CRM. On a good note we have now finished our upgrade from SharePoint 2007 to SharePoint 2010 successfully. Some items have crept up lately that I think need to be documented to help others overcome the problems we have encountered. Here is a list of things you will hopefully see from me over the next couple weeks.<br />
<ul>
<li>How to successfully send out an email merge campaign from word as an email address other than the one that owns the primary outlook profile on a machine. </li>
<li>How to create a custom color palette for use with SharePoint charts. </li>
<li>Problems with re-provisioning the User Profile Synchronization Service</li>
<li>Refreshing email enabled lists after performing an upgrade. </li>
<li>Possibly a post about migration from 2007 to 2010 if I think I can add more value outside of what is already documented on the internet. </li>
</ul>
If there is anything in this list people would like to hear first let me know! <br />
<ul>
</ul>
Matthew Churillahttp://www.blogger.com/profile/06699782042171994247noreply@blogger.com0tag:blogger.com,1999:blog-3155962902335259216.post-42810444540603325712012-03-24T12:12:00.003-04:002012-03-24T12:14:39.998-04:00Testing Access Services<div class="separator" style="clear: both; text-align: center;">
</div>
This is part of my series on testing SharePoint service applications: <a href="http://matthewchurilla.blogspot.com/2012/02/testing-service-applications-in.html">http://matthewchurilla.blogspot.com/2012/02/testing-service-applications-in.html</a><br />
<br />
There is a good article on MSDN for setting up a basic web database using Microsoft Access: <a href="http://msdn.microsoft.com/en-us/library/ff402351.aspx">http://msdn.microsoft.com/en-us/library/ff402351.aspx</a>. This article will walk you through the basics of creating a few access tables, publishing your database to SharePoint and then adding data into the database. The site even has a sample database you can use to do your testing(<a href="http://archive.msdn.microsoft.com/Release/ProjectReleases.aspx?ProjectName=odcac2010h2&ReleaseId=3921">http://archive.msdn.microsoft.com/Release/ProjectReleases.aspx?ProjectName=odcac2010h2&ReleaseId=3921</a>). I like to use this sample database as a starting point for my testing once I have started with this database I like to perform the following actions on the stock database just to get a better test of the available functionality.<br />
<br />
<br />
<ol><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiDFqsetHFO-0VOTvliSvkZqYdTFriKbdUpesUAnEQn15OKpvoXPuMexEHojkPxHTQj690Q1fkHYryJX8Xh7Leptqnk62CH63e9Pyl40AM4L3_AvWFFBQbrakaUmpKCEMCTZ-9It9cZP02W/s1600/12.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"></a><div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiDFqsetHFO-0VOTvliSvkZqYdTFriKbdUpesUAnEQn15OKpvoXPuMexEHojkPxHTQj690Q1fkHYryJX8Xh7Leptqnk62CH63e9Pyl40AM4L3_AvWFFBQbrakaUmpKCEMCTZ-9It9cZP02W/s1600/12.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" height="204" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiDFqsetHFO-0VOTvliSvkZqYdTFriKbdUpesUAnEQn15OKpvoXPuMexEHojkPxHTQj690Q1fkHYryJX8Xh7Leptqnk62CH63e9Pyl40AM4L3_AvWFFBQbrakaUmpKCEMCTZ-9It9cZP02W/s320/12.png" width="320" /></a><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiDFqsetHFO-0VOTvliSvkZqYdTFriKbdUpesUAnEQn15OKpvoXPuMexEHojkPxHTQj690Q1fkHYryJX8Xh7Leptqnk62CH63e9Pyl40AM4L3_AvWFFBQbrakaUmpKCEMCTZ-9It9cZP02W/s1600/12.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"></a></div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhS9G998E4zCsdasSDkcjiiBUXEt1Ph-otAJtqT-YmFKgI6EI4our7OfDKVPJVfjqVQIwwnhUbdlakE7QiWjNDdJPRCUiQZguou54LsJn7laINpuW_Vo2efyURsfjoYYEdbyd9q4NQmvCad/s1600/13.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" height="203" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhS9G998E4zCsdasSDkcjiiBUXEt1Ph-otAJtqT-YmFKgI6EI4our7OfDKVPJVfjqVQIwwnhUbdlakE7QiWjNDdJPRCUiQZguou54LsJn7laINpuW_Vo2efyURsfjoYYEdbyd9q4NQmvCad/s320/13.png" width="320" /></a></div>
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhPtKu1b-JiBb_8UL5zV6Vj5nfUCPXNSs67efpE5n16b1HN7jnOqD5XJpd1ifkFW-_9xAT4l1h5sBvSiSCi2hVPb1ZhQiv3ed8jq9g-_l4YaX6zWg7zM1vMyeEM4mMkzVLId-Q4FYCoVApa/s1600/13-6.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" height="202" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhPtKu1b-JiBb_8UL5zV6Vj5nfUCPXNSs67efpE5n16b1HN7jnOqD5XJpd1ifkFW-_9xAT4l1h5sBvSiSCi2hVPb1ZhQiv3ed8jq9g-_l4YaX6zWg7zM1vMyeEM4mMkzVLId-Q4FYCoVApa/s320/13-6.png" width="320" /></a>
<li>Use web form to add a supplier: Microsoft</li>
<li>Use web form to add a supplier: Apple</li>
<li>Use web form to add a supplier: Google</li>
<li>Use web form to add a part for supplier: SharePoint, Microsoft</li>
<li>Use web form to add a part for supplier: Office, Microsoft</li>
<li>Use web form to add a part for supplier: Windows, Microsoft</li>
<li>Use web form to add a part for supplier: iPhone, Apple</li>
<li>Use web form to add a part for supplier: iPad, Apple</li>
<li>Use web form to add a part for supplier: GSA, Google</li>
<li>Use web form to add a part for supplier: AdSense, Google</li>
<li>Use web form to add a part for supplier: Blogger, Google</li>
<li>Switch back to Access and ensure that data is populated back into the database.</li>
<li>Create a new report to test reporting.</li>
<ol><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiP_gC02AqCx3ceQG0TINroUOP7wr5XFm0rehawfiSFZNKbslm-r8y9mqU7921ZYieh6JEdnqZsRZp-ZM9FggPAzsoi1sAvd9_LD9vQ8bn6muJ6apNRUKemie6UX2iqocOlI5xoSBy69Jmn/s1600/14.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" height="216" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiP_gC02AqCx3ceQG0TINroUOP7wr5XFm0rehawfiSFZNKbslm-r8y9mqU7921ZYieh6JEdnqZsRZp-ZM9FggPAzsoi1sAvd9_LD9vQ8bn6muJ6apNRUKemie6UX2iqocOlI5xoSBy69Jmn/s320/14.png" style="cursor: move;" width="320" /></a>
<li>Show all fields from all tables</li>
<li>Add "Supplier Name" to the report</li>
<li>Remove Column "Supplier"</li>
<li>Remove Column "ID"</li>
<li>Add a Group on "Supplier Name"</li>
<li>Your final report should look like this.</li>
<li>Synchronize the report back to the web</li>
</ol>
<li>View the report in SharePoint</li>
</ol>
<br />
<br />
<br />
<br />
<br />
<div class="separator" style="clear: both; text-align: left;">
At this point you have performed a basic test of Access Services. If everything outlined here worked you can be fairly confident your service is installed and working properly. We will keep the database site published for now we might use it in future articles. </div>
<div>
<br /></div>Matthew Churillahttp://www.blogger.com/profile/06699782042171994247noreply@blogger.com0tag:blogger.com,1999:blog-3155962902335259216.post-53747262467131839042012-03-13T15:58:00.002-04:002012-03-13T16:00:50.144-04:00Document Management with SharePoint and CRM<span style="font-family: Calibri;">Microsoft Dynamics CRM is a great application for managing
customer, sales, and marketing data but it is not a very good document
management system.<span style="mso-spacerun: yes;"> </span>Fortunately Microsoft
has another product named SharePoint that is a great document management and
storage system and now with the new version of CRM you can link entities to
SharePoint so you can store related documents in SharePoint and utilize the
great document management features provided by that software platform.<span style="mso-spacerun: yes;"> </span>In this blog posting I am going to give an overview
of the integration possibilities between Microsoft Dynamics CRM and Microsoft
SharePoint.</span><br />
<br />
<span style="font-family: Calibri;">First off let us take a brief look at the Document
Management section of the Microsoft Dynamics CRM Settings to see what is
available to us.<span style="mso-spacerun: yes;"> </span><o:p></o:p></span><br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiPkFaPE2pbz9aMPQFUiWQoiDoIyEIdkOwH_AFFucnZzcq_1R6FunAV3bIHO8NvgTrEwqP0JfcicxgDAwLMLns6cfLdBs1D8aEpaeIYQ873ZcCkM_MoS-ME4CrOXoFdAsMEsv_Epo_Lo1vh/s1600/Untitled.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="171" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiPkFaPE2pbz9aMPQFUiWQoiDoIyEIdkOwH_AFFucnZzcq_1R6FunAV3bIHO8NvgTrEwqP0JfcicxgDAwLMLns6cfLdBs1D8aEpaeIYQ873ZcCkM_MoS-ME4CrOXoFdAsMEsv_Epo_Lo1vh/s640/Untitled.png" width="640" /></a></div>
<br />
<ol>
<li><div class="separator" style="clear: both; text-align: justify;">
<span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;"><span style="font-size-adjust: none; font-stretch: normal; font: 7pt/normal "Times New Roman";">
</span></span></span><span style="font-family: Calibri;">Document Management Settings – This option
allows you to do the base configuration for Document Management.<span style="mso-spacerun: yes;"> </span>This is where you go to configure which
entities in the system document management is enabled for and where you can
specify the primary document management location if you choose to have
one.<span style="mso-spacerun: yes;"> </span><o:p></o:p></span></div>
</li>
<li><span style="font-family: Calibri;">Install List Component – This option points you
to instructions for downloading and installing the SharePoint list component
that you can install as a sandboxed solution for sites that you wish to enable
enhanced document management on.<o:p></o:p></span></li>
<li>
<span style="font-family: Calibri;">SharePoint Sites – This section lists all of the
sites that are linked to CRM but unfortunately it is only useful for sites that
have the SharePoint List Component installed on them.<span style="mso-spacerun: yes;"> </span>If you are not using the list component adding
sites to this section will not have any effect in other parts of the system.<o:p></o:p></span></li>
<li>
<span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;"><span style="font-size-adjust: none; font-stretch: normal; font: 7pt/normal "Times New Roman";">
</span></span></span><span style="font-family: Calibri;">SharePoint Document Locations – This choice is a
great place for administrators to reference.<span style="mso-spacerun: yes;">
</span>Listed in this section you will find every location that is linked to
from CRM.</span></li>
</ol>
<br />
<span style="font-family: Calibri;"></span><br />
<span style="font-family: Calibri;"></span><br />
<span style="font-family: Calibri;"><div class="MsoNormal" style="margin: 0in 0in 10pt;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEisT6utXr_Gs4Tqb-wfdLlcxsQgyTA9ZpZt8zW8UqmTmwTNktrppX5y58E-Q2gEs04M-6akFs8a5MonJyzWdTyU52zHbqo_6Vz-IIiNgsfSVx7HNEu7r72Gf_RY-bTGw9Y-lEk1RZVD4r8x/s1600/Untitled.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEisT6utXr_Gs4Tqb-wfdLlcxsQgyTA9ZpZt8zW8UqmTmwTNktrppX5y58E-Q2gEs04M-6akFs8a5MonJyzWdTyU52zHbqo_6Vz-IIiNgsfSVx7HNEu7r72Gf_RY-bTGw9Y-lEk1RZVD4r8x/s400/Untitled.png" width="367" /></a>Starting at the top let’s examine the document management
settings section.<span style="mso-spacerun: yes;"> </span>The primary listing
on this page allows you specify which entities you would like to enable
document management on.<span style="mso-spacerun: yes;"> </span>A number of
these are enabled by default however you can enable document management for any
stock or custom entity that exists in the system.<span style="mso-spacerun: yes;"> </span>There is a second option present on this
screen and that is an option that lets you specify a SharePoint 2010 site URL
to enable automatic folder creation; this provides you the capability to automate
your document management with a SharePoint 2010 site that has the List
Component installed on it.<span style="mso-spacerun: yes;"> </span>We will
re-visit this later when we review the 2010 only features.<span style="mso-spacerun: yes;"> </span></div>
<div class="MsoNormal" style="margin: 0in 0in 10pt;">
<br /></div>
<div class="MsoNormal" style="margin: 0in 0in 10pt;">
<span style="mso-spacerun: yes;"><span style="font-family: Times New Roman;">
</span>Next we are going to take a quick look at how things look
once you have document management enabled so you have a good feel for how
linked document libraries will behave.<span style="mso-spacerun: yes;">
</span>So without further ado...</span></div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiW7OUBhLGdAyC5R-2EbOadWUsShHQw4IF4eNDpNFKEt1V3tO27dpjB4WTpNyNulxElzsrVEJdQZtAyQd1vvJErOZ-KJuHJRCaYRBoYM-NjYFnbgdX-RY3M3k_QSqgLxkLWtCWCyJqqpI7a/s1600/Untitled.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" height="320" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiW7OUBhLGdAyC5R-2EbOadWUsShHQw4IF4eNDpNFKEt1V3tO27dpjB4WTpNyNulxElzsrVEJdQZtAyQd1vvJErOZ-KJuHJRCaYRBoYM-NjYFnbgdX-RY3M3k_QSqgLxkLWtCWCyJqqpI7a/s320/Untitled.png" width="294" /></a></div>
<div class="MsoNormal" style="margin: 0in 0in 10pt;">
Here is a sample view of how a site will look when linked
via an absolute URL. <span style="mso-spacerun: yes;"> </span>Notice how this is
just an embedded view of the SharePoint Document Library, because of this, you
are capable of doing anything in this embedded view you could do normally in
SharePoint.<span style="mso-spacerun: yes;"> </span>The downside is it makes for
a busy screen because there is a lot going on visually and the two different UI
styles clash a little bit.<o:p></o:p></div>
<div class="MsoNormal" style="margin: 0in 0in 10pt;">
<span style="font-family: Times New Roman;">
</span></div>
<div class="MsoNormal" style="margin: 0in 0in 10pt;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi23rplNpz42rovfeezeDZQw65J2N0aw-pPsroa8iKyscyKOCEXEYUoiLOWYdzIQX7KjZLaV2nuC8iShsQUstw_2Ua52H5ejCuC78EDo98ICW4aPDWrQ3sYR31X0UAF1SJQcmVHUInvNJgb/s1600/Untitled.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" height="320" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi23rplNpz42rovfeezeDZQw65J2N0aw-pPsroa8iKyscyKOCEXEYUoiLOWYdzIQX7KjZLaV2nuC8iShsQUstw_2Ua52H5ejCuC78EDo98ICW4aPDWrQ3sYR31X0UAF1SJQcmVHUInvNJgb/s320/Untitled.png" width="294" /></a></div>
<div class="MsoNormal" style="margin: 0in 0in 10pt;">
<br /></div>
<div class="MsoNormal" style="margin: 0in 0in 10pt;">
<br /></div>
<div class="MsoNormal" style="margin: 0in 0in 10pt;">
<br /></div>
<div class="MsoNormal" style="margin: 0in 0in 10pt;">
<br /></div>
<div class="MsoNormal" style="margin: 0in 0in 10pt;">
And here is a sample screenshot of how linked document
libraries look for sites that have the SharePoint List Component installed on
them, notice how the document library has a more integrated look and feel
to it this exposes all of the document management capabilities of SharePoint to the user
through a more seamless CRM user interface.</div>
<div class="MsoNormal" style="margin: 0in 0in 10pt;">
<span style="font-family: Times New Roman;">
</span></div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiTGHT8PCQk8ekgJSb6fQvIvW0l2eU1_vspDRNo4G8ogZvBTKpVt4BoXUuHUq2atFj6nuS6j_j8kWW5YS82anIBH9jrh6ZDtjOiX4zbPbwlEP2fWK99r8tQh15TK4cUjKlC1riZqYZdUJmz/s1600/Untitled.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" height="320" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiTGHT8PCQk8ekgJSb6fQvIvW0l2eU1_vspDRNo4G8ogZvBTKpVt4BoXUuHUq2atFj6nuS6j_j8kWW5YS82anIBH9jrh6ZDtjOiX4zbPbwlEP2fWK99r8tQh15TK4cUjKlC1riZqYZdUJmz/s320/Untitled.png" width="294" /></a></div>
<div class="MsoNormal" style="margin: 0in 0in 10pt;">
The last thing I want to point out is that you are able to
link more than one document location to each entity.<span style="mso-spacerun: yes;"> </span>You are capable of having many locations
which will allows you to separate documents into different
locations based on similar properties.</div>
<div class="separator" style="clear: both; text-align: center;">
<br /></div>
<div class="MsoNormal" style="margin: 0in 0in 10pt;">
<span style="font-family: Times New Roman;">
<span style="font-family: Calibri;">Next let’s move on to linking CRM entities to SharePoint
document libraries.<span style="mso-spacerun: yes;"> </span>For those of you
with SharePoint 2007 this will be the only integration option available to
you.<span style="mso-spacerun: yes;"> </span>However this functionality is not
only available to just 2007 users; if you are operating in an environment where
you cannot install the SharePoint 2010 List Component you can still use Document
Locations to connect SharePoint 2010 and CRM.<span style="mso-spacerun: yes;">
</span>Document Locations are rather primitive because they just embed an HTML
viewer in the CRM page that simulates browsing the linked document library in a
web browser.<o:p></o:p></span></span></div>
<span style="font-family: Times New Roman;"><div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhE2Z8m8ewh1SjO9DzxDeJenRWxO1tBrhpyx0AsOXYv0Hy21xZjEdPPJB9BmqQAv0jud2rS9iL6Re-WUdIV9kZmvK8AbwIpIAwDPEhX2srq4MIdpZ_UCS2f9NNsHOlVKazVbo-x1e86nBTb/s1600/Untitled.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" height="185" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhE2Z8m8ewh1SjO9DzxDeJenRWxO1tBrhpyx0AsOXYv0Hy21xZjEdPPJB9BmqQAv0jud2rS9iL6Re-WUdIV9kZmvK8AbwIpIAwDPEhX2srq4MIdpZ_UCS2f9NNsHOlVKazVbo-x1e86nBTb/s400/Untitled.png" style="cursor: move;" unselectable="on" width="400" /></a></div>
<div class="MsoNormal" style="margin: 0in 0in 10pt;">
<span style="font-family: Calibri;">When you add a Document Location and don’t have any Site
Locations defined that have the SharePoint 2010 List Component installed you
will be presented with an “Add Document Location” dialog box that will only be
capable of linked via an absolute URL to a target document location.<span style="mso-spacerun: yes;"> </span>In order to do these just give your document
location a name and enter the full SharePoint URL you wish to link as a
document location.<span style="mso-spacerun: yes;"> </span><o:p></o:p></span></div>
<div class="MsoNormal" style="margin: 0in 0in 10pt;">
</div>
<div class="MsoNormal" style="margin: 0in 0in 10pt;">
<span style="font-family: Calibri;">Now let’s look at the SharePoint 2010 List Component; this
item allows you to directly link document libraries from SharePoint 2010 into
CRM.<span style="mso-spacerun: yes;"> </span>I will not go over installing this
component on a SharePoint site because this process is well documented
elsewhere (</span><a href="http://www.microsoft.com/download/en/details.aspx?id=5283"><span style="color: blue; font-family: Calibri;">http://www.microsoft.com/download/en/details.aspx?id=5283</span></a><span style="font-family: Calibri;">).<span style="mso-spacerun: yes;"> </span>Once you have installed the list component on
a site you will have a few new capabilities available to you.<span style="mso-spacerun: yes;"> </span><o:p></o:p></span></div>
<div class="MsoNormal" style="margin: 0in 0in 10pt;">
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgiGOXt2EJtxPwqY9tNNKNWWVIZwjwap-vASu7vmlG3agVbvn4fQOw3T3uUHPQ2yRZPb8wySz8JKIfrAEM1DsVh6Ay_JfXucYXAKVEYmhk-Wq_4thVRtOygsGUBCM3EqhReTbyIvEwN6QNK/s1600/Untitled.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="347" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgiGOXt2EJtxPwqY9tNNKNWWVIZwjwap-vASu7vmlG3agVbvn4fQOw3T3uUHPQ2yRZPb8wySz8JKIfrAEM1DsVh6Ay_JfXucYXAKVEYmhk-Wq_4thVRtOygsGUBCM3EqhReTbyIvEwN6QNK/s640/Untitled.png" width="640" /></a></div>
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj796ZzIRqCW2G9MvFhgTtalMSEGMIfoRKtr1n6Ie2rpqViidVnRkV0WCBneBDD51H38vdCakQhUxutsX4PtCN6ixpq11yRaLGNAjurJyT9j7eJvH7eq2PTH3vEoHH84CEndbbbxX-i1Aez/s1600/Untitled.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" height="135" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj796ZzIRqCW2G9MvFhgTtalMSEGMIfoRKtr1n6Ie2rpqViidVnRkV0WCBneBDD51H38vdCakQhUxutsX4PtCN6ixpq11yRaLGNAjurJyT9j7eJvH7eq2PTH3vEoHH84CEndbbbxX-i1Aez/s320/Untitled.png" width="320" /></a><span style="font-family: Calibri;">First you will now be able to set an automatic folder creation
site.<span style="mso-spacerun: yes;"> </span>When you enable this feature you
will be prompted on whether you want to structure your folders by accounts or
contacts.<span style="mso-spacerun: yes;"> </span>Whenever you enable this feature entities
that are related to the based on entity will have all of their documentation
consolidated in the same folder structure within SharePoint.<span style="mso-spacerun: yes;"> </span>For
example if you had an account named Account 1 that had an opportunity named
Opportunity 1 then you would end up with a folder structure that was something
like “Account 1\opportunity\Opportunity 1” similarly if there was a quote named
Quote 1 the folder would be named “Account 1\quote\Quote 1”.<span style="mso-spacerun: yes;"> </span>If you don’t select to group items based on
entity it will group everything within a new document library named after the
entities that are contained within it.<span style="mso-spacerun: yes;">
</span>Once you have enabled automatic folder creation the first time someone
visits the document section of an entity they will be prompted to create a new
folder in the appropriate location. Personally I don't like to enable automatic document library creation, I feel that this removes some of the flexability of the system but this could be very convient for some organizations. Below are some screen shots of how this appears in the CRM interface.</span></div>
<div class="MsoNormal" style="margin: 0in 0in 10pt;">
</div>
<div class="MsoNormal" style="margin: 0in 0in 10pt;">
<br /></div>
<div class="MsoNormal" style="margin: 0in 0in 10pt;">
</div>
<div class="MsoNormal" style="margin: 0in 0in 10pt;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh5ZKm_4v5Oh44YH-4whcNwK5luG-9RxXex07BkcmZ_mq8oKMOZm2awarpyxCmbZrdZP3vdL5gxS1J9IdL1-6V4g7slFcSp8NlYwNnm6OOpT1QfmjHaICXeDov1LvM_Unc0H_2yc8k0tMX8/s1600/Untitled.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="260" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh5ZKm_4v5Oh44YH-4whcNwK5luG-9RxXex07BkcmZ_mq8oKMOZm2awarpyxCmbZrdZP3vdL5gxS1J9IdL1-6V4g7slFcSp8NlYwNnm6OOpT1QfmjHaICXeDov1LvM_Unc0H_2yc8k0tMX8/s400/Untitled.png" width="400" /></a><span style="font-family: Calibri;">The second thing you will now be able to do is add sites
into the SharePoint sites list.<span style="mso-spacerun: yes;"> </span>Adding
sites here is a good way to allow users to create folders.<span style="mso-spacerun: yes;"> </span>When you have sites listed in the SharePoint
Sites list users will now have a second option when adding a new document
location.<span style="mso-spacerun: yes;"> </span>This option allows the user
creating a new document location to specifiy a new folder under an existing
site that you have added to the SharePoint Sites List.<span style="mso-spacerun: yes;"> </span><o:p></o:p></span></div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgaHHRF8EuzDlwVbmGDoqeahEhOtlx2y4RaLx2VJoEkOz0xa5dBlMmdr0X6hRURYB5OCLqKOBJ3N34XGoDilUNtq5vH0_TreRqoONBDQbIe32lbAxbKH75dwAq2JdKfn9lk2uVdBkJWgPch/s1600/Untitled.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" height="285" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgaHHRF8EuzDlwVbmGDoqeahEhOtlx2y4RaLx2VJoEkOz0xa5dBlMmdr0X6hRURYB5OCLqKOBJ3N34XGoDilUNtq5vH0_TreRqoONBDQbIe32lbAxbKH75dwAq2JdKfn9lk2uVdBkJWgPch/s400/Untitled.png" width="400" /></a></div>
</span><div class="separator" style="clear: both; text-align: center;">
</div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjLTl5lv6YySs_qBjdWumiKpX5KwoBSGTKg5dpLaiity65dVOH3Qe0QmfieaHr75pmoO1IVTt19WzUDb28YnbfVTJfyGmog68yXIToJZkushmzhfDRQXmiXCPQhQkh9zR6yIccudDMtHNAx/s1600/Untitled.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" height="210" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjLTl5lv6YySs_qBjdWumiKpX5KwoBSGTKg5dpLaiity65dVOH3Qe0QmfieaHr75pmoO1IVTt19WzUDb28YnbfVTJfyGmog68yXIToJZkushmzhfDRQXmiXCPQhQkh9zR6yIccudDMtHNAx/s400/Untitled.png" width="400" /></a></div>
<div class="MsoNormal" style="margin: 0in 0in 10pt;">
The last section we need to visit is Document Locations and
it is a very good section.<span style="mso-spacerun: yes;"> </span>The Document
Locations option enables you to view every link between CRM and SharePoint so
it is a great place to review for duplicate connections and to ensure that the
integration is being used properly.<span style="mso-spacerun: yes;"> </span>You
will notice in this final screen shot the difference between how absolute URL
links are displayed compared to Document Locations that are setup based on a
base SharePoint Site and relative references from there.</div>
<div class="MsoNormal" style="margin: 0in 0in 10pt;">
And that completes this posting on Document Management for Microsoft Dynamics CRM. I hope you are a little more informed now. </div>
<div class="MsoNormal" style="margin: 0in 0in 10pt;">
<br /></div>
<div class="MsoNormal" style="margin: 0in 0in 10pt;">
<span style="font-family: Times New Roman;">
</span></div>
<div class="MsoNormal" style="margin: 0in 0in 10pt;">
<br /></div>
<div class="MsoListParagraphCxSpLast" style="margin: 0in 0in 10pt 0.5in; mso-list: l0 level1 lfo1; text-align: left; text-indent: -0.25in;">
<span style="font-family: Times New Roman;">
</span></div>
</span><br />
<div class="MsoListParagraphCxSpLast" style="margin: 0in 0in 10pt 0.5in; mso-list: l0 level1 lfo1; text-align: left; text-indent: -0.25in;">
<span style="font-family: Times New Roman;">
</span></div>
<div class="MsoListParagraphCxSpLast" style="margin: 0in 0in 10pt 0.5in; mso-list: l0 level1 lfo1; text-indent: -0.25in;">
<br /></div>
<br />
<img height="44" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhE2Z8m8ewh1SjO9DzxDeJenRWxO1tBrhpyx0AsOXYv0Hy21xZjEdPPJB9BmqQAv0jud2rS9iL6Re-WUdIV9kZmvK8AbwIpIAwDPEhX2srq4MIdpZ_UCS2f9NNsHOlVKazVbo-x1e86nBTb/s400/Untitled.png" style="filter: alpha(opacity=30); left: 569px; opacity: 0.3; position: absolute; top: 2855px;" width="96" />Matthew Churillahttp://www.blogger.com/profile/06699782042171994247noreply@blogger.com3tag:blogger.com,1999:blog-3155962902335259216.post-14389498246545663332012-03-05T04:29:00.000-05:002012-03-24T12:15:04.472-04:00Configuring Secure StoreThis is part of my series on testing service applications: <a href="http://matthewchurilla.blogspot.com/2012/02/testing-service-applications-in.html">http://matthewchurilla.blogspot.com/2012/02/testing-service-applications-in.html</a><br />
<br />
We will be working on testing service applications and in order to do this properly we will need to configure the secure store service. We are configuring this service to test the ability of service applications to access external data sources. If you don't care about accessing external data sources from your service applications then you can skip configuring the secure store service and any future tests that involve it. <br />
<br />
In order to not reinvent the wheel Microsoft already has some documentation on configuring most service applications and I will link to it when possible. Here is the document for configuring the secure store service application: <a href="http://technet.microsoft.com/en-us/library/ee806866.aspx">http://technet.microsoft.com/en-us/library/ee806866.aspx</a>. The steps you will want to perform in order to have a properly configured service application.<br />
<br />
<ol><div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhKW_pRYKMiSPWq-VWV1zpdX5mvcOypASUYGrq8Wz0ZzwK9kOQjclO7ecLibfwFSNXcao12it0XnJF4neVVJ9xu1vibRkrL_H1sK_USnNEXo_DCWs6ygqR8eGD3Vbi75_gIDKTDK4J7pOLT/s1600/Target+Application.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" height="297" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhKW_pRYKMiSPWq-VWV1zpdX5mvcOypASUYGrq8Wz0ZzwK9kOQjclO7ecLibfwFSNXcao12it0XnJF4neVVJ9xu1vibRkrL_H1sK_USnNEXo_DCWs6ygqR8eGD3Vbi75_gIDKTDK4J7pOLT/s320/Target+Application.png" width="320" /></a></div>
<div class="separator" style="clear: both; text-align: center;">
</div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj5ZcyYj4EKkTUUsalIaJL4UxPbLfVr_Gw7raKPCqfLReObquOqhDzsfV3byWIftkYB5u_058MTyJfnKCaxXqYM_zhX3LXMXrZv2of5VzFR4k9zTh3hdLose5rFhMkLXPjRFkT0FMk2RbER/s1600/fields.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" height="82" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj5ZcyYj4EKkTUUsalIaJL4UxPbLfVr_Gw7raKPCqfLReObquOqhDzsfV3byWIftkYB5u_058MTyJfnKCaxXqYM_zhX3LXMXrZv2of5VzFR4k9zTh3hdLose5rFhMkLXPjRFkT0FMk2RbER/s320/fields.png" width="320" /></a></div>
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiAasetUe-EHzUNCUHpARw5He0Rb9ykchUJ4YXM-qxgKCcjqJipUilpoXWTRfZ-jQv8vGwBo_NeYzj6lRYYsaFBmJ-Y7eiF_heYl1l0nLIn3027w3qop50dNLgGjDFVbg_LY09LTSvm8w5R/s1600/people.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" height="130" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiAasetUe-EHzUNCUHpARw5He0Rb9ykchUJ4YXM-qxgKCcjqJipUilpoXWTRfZ-jQv8vGwBo_NeYzj6lRYYsaFBmJ-Y7eiF_heYl1l0nLIn3027w3qop50dNLgGjDFVbg_LY09LTSvm8w5R/s320/people.png" width="320" /></a>
<li>Generate a New Key</li>
<li>Create a new Target Application. I used the parameters to the right. Be aware setting the members to All Authenticated Users is not recommended this will allow any user to authenticate to external data sources that use the target application ID. But since this is for testing purposes we are going to use it to make things easy.</li>
<li>Set credentials on the target application.</li>
</ol>
<div>
<br /></div>
<div>
<br /></div>
<div>
Once you have a target application setup you will be able to use this application in other service applications to test data access to external data sources.</div>Matthew Churillahttp://www.blogger.com/profile/06699782042171994247noreply@blogger.com0tag:blogger.com,1999:blog-3155962902335259216.post-47687109272534258992012-02-21T20:38:00.000-05:002012-03-24T12:13:34.993-04:00Testing Service Applications in SharePoint 2010So you've taken time and built a farm, but you still wonder how do I test all of this? Well stay tuned this week I am going begin writing a series on how to test each and every service application that ships with SharePoint 2010. I hope that this will become a good resource for those of you, who like myself, would like to be able to test their farm and ensure it is running properly before releasing it to end users. I will update this post as I release new articles in this series with links to each article.<br />
<br />
Before testing applications setup a secure store: <a href="http://matthewchurilla.blogspot.com/2012/03/configuring-secure-store.html">http://matthewchurilla.blogspot.com/2012/03/configuring-secure-store.html</a><br />
Testing Access Services: <a href="http://matthewchurilla.blogspot.com/2012/03/testing-access-services.html">http://matthewchurilla.blogspot.com/2012/03/testing-access-services.html</a><br />
<br />Matthew Churillahttp://www.blogger.com/profile/06699782042171994247noreply@blogger.com2tag:blogger.com,1999:blog-3155962902335259216.post-62993207476638017102012-02-09T10:11:00.001-05:002012-03-13T11:28:31.929-04:00Central Administration Prompts for Credentials<span style="font-family: "Times New Roman","serif"; font-size: 12pt; mso-fareast-font-family: "Times New Roman";">I stumbled across a quirky
authentication issue when we enabled Kerberos on our Central Administration Web
Applications for SharePoint 2010. Every time we launched Central Administration
using the link provided on the start menu we would be prompted for credential
entry, and everytime credentials were entered they would fail even if they were entered correctly. After double checking the SPNs it was obvious they were setup properly
and Kerberos authentication should have been logging us in automatically. <o:p></o:p></span><br />
<br />
<div class="MsoNormal" style="line-height: normal; margin: 0in 0in 0pt;">
<span style="font-family: "Times New Roman","serif"; font-size: 12pt; mso-fareast-font-family: "Times New Roman";"><o:p> </o:p></span><span style="font-family: "Times New Roman","serif"; font-size: 12pt; mso-fareast-font-family: "Times New Roman";">It turns out the problem here is
somewhat related to another issue I posted about with our CRM environment (<a href="http://matthewchurilla.blogspot.com/2012/01/outlook-plugin-is-nice-feature-of.html"><span style="color: blue;">http://matthewchurilla.blogspot.com/2012/01/outlook-plugin-is-nice-feature-of.html</span></a>).
At first I looked at the command that was getting executed by the menu link and
it was pointing to psconfigui.exe so it was hard to tell what was happening
there. Next I opened internet explorer and found the Central
Administration URL had been added to trusted sites and trusted sites does not
automatically login users, only the intranet zone does this. It occured to me that psconfigui.exe must do something similar to what I discovered the CRM Outlook
plugin doing. In an attempt to be helpful it is adding the Central
Administration URL to trusted sites but unfortunately when the URL is in trusted
sites kerberos integrated authentication does not work. The solution to this problem is
as simple as it was for CRM you just need to follow this process:<o:p></o:p></span></div>
<br />
<ul>
<li>Find the URL that got added to trusted sites and remove it. </li>
<ul>
<li><em>Internet Options -> Security -> Trusted Sites -> Sites </em></li>
</ul>
<li>Open Local Intranet configuration and add the URL you just removed from trusted sites. Make sure the URL matches exactly. If you removed <a href="http://machine/">http://machine</a> from trusted sites then add <a href="http://machine/">http://machine</a> to local intranet sites. If you removed <a href="http://machine.fqdn/">http://machine.fqdn</a> from trusted sites than add <a href="http://machine.fqdn/">http://machine.fqdn</a> to local intranet sites.</li>
<ul>
<li><em>Internet Options -> Security -> Local Intranet -> Sites ->
Advanced </em></li>
</ul>
<li>Launch Central Administration using the start menu link; everything should work fine.</li>
</ul>
<br />Matthew Churillahttp://www.blogger.com/profile/06699782042171994247noreply@blogger.com2tag:blogger.com,1999:blog-3155962902335259216.post-51763239292703789732012-01-26T09:20:00.001-05:002012-02-15T09:44:59.927-05:00Error Installing KB976462 during SharePoint Pre-Requisites InstallerI was running the SharePoint Pre-Requisites installer this week. Upon competition
it failed to install KB976462 and then skipped the rest of the installers. It
turns out a second running of the installer then successfully installed the
rest of the pre-requisites. I could have just continued on my merry way, but
having a weird issue like this hanging out there can usually lead to some very
strange issues further along in the install process so I dug in to figure out what was wrong.<br />
<br />
The first step was to figure out what the KB was and this lead me to the Microsoft
kb article for it: <o:p></o:p><br />
<a href="http://support.microsoft.com/kb/976462"><span style="color: blue;">http://support.microsoft.com/kb/976462</span></a>.
It turns out this is a patch to the .NET framework 3.5 SP1, this seems like a
crucial thing to have installed properly. Next I logged into one of the other
servers provided to me and checked to see what versions of .NET was installed.
In order to determine the .NET versions I navigated to the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\ upon viewing the versions installed in this key I noticed that
only version 2 or .NET was installed. <br />
<br />
On this other machine I then used the proper method to activate .NET v3.5.1
by adding the windows feature from the server management console. After the
feature was activated windows update was run to make sure that all of the
current patches for .NET were downloaded and installed. After the feature was
activated and windows update was run the pre-requisite installer was executed
and it ran without any errors.<br />
<br />
To be on the safe side I had the first server rebuilt because installing
SharePoint on a server with an improperly installed .NET v3.5.1 did not seem
like a good path to go down. <o:p></o:p>Matthew Churillahttp://www.blogger.com/profile/06699782042171994247noreply@blogger.com1tag:blogger.com,1999:blog-3155962902335259216.post-22356840117150632142012-01-26T08:58:00.002-05:002012-02-11T14:53:51.969-05:00The username is invalid. The account must be a valid domain accountToday while configuring a farm I stumbled across a weird error I have never
seen before. Upon entering the credentials for our farm account and error
message popped up stating: "The username is invalid. The account must be a
valid domain account." <o:p></o:p><br />
<br />
As part of our deployment we wanted to make our account names very
descriptive of what they were used for. This policy led us to use a very
descriptive and lengthy account name that was similar to
SP2010_ServerFarmAccount. This seemed like a great idea at the time because it
is very obvious what this account was used for. But as it turns out lengthy
user names might be a bad idea in a Windows environment.<o:p></o:p><br />
<br />
Those people out there who are Active Directory administrators might already
know what is coming up as the root of this problem. It turns out that Active
Directory will let you make very lengthy user names; unfortunately there is a
second field that is kept around for legacy purposes that truncates the user
name to 20 characters. So using domain\SP2010_ServerFarmAccount was not the
proper thing to do because the account gets truncated for authentication
purposes to domain\SP2010_ServerFarmAcc. <o:p></o:p><br />
<br />
The solution to this problem is pretty easy. Login using either the legacy
form domain\SP2010_ServerFarmAcc or if you prefer to use the whole user name
you can use the more modern format SP2010_ServerFarmAccount@domain.fqdn.<o:p></o:p><br />
<br />Matthew Churillahttp://www.blogger.com/profile/06699782042171994247noreply@blogger.com1tag:blogger.com,1999:blog-3155962902335259216.post-27493608995881227952012-01-26T08:58:00.001-05:002012-01-26T08:58:35.522-05:00Couple Installation Issues This WeekLately I have been doing a lot of SharePoint 2010 installs and this has lead to a couple of unusual problems that others might run into so I will document them in the next few posts so if anyone else runs into these issues they can be a little bit closer to fixing them.<br />
<br />Matthew Churillahttp://www.blogger.com/profile/06699782042171994247noreply@blogger.com0tag:blogger.com,1999:blog-3155962902335259216.post-79114434449841254662012-01-16T09:18:00.001-05:002012-01-16T13:00:00.115-05:00Authentication issues with the Microsoft CRM Outlook Plugin<br />
The outlook plugin is a nice feature of Microsoft Dynamics CRM that enables
users to view CRM information from within outlook. I have been a longtime user
of the plugin but came across a significant problem with authentication once
CRM Online became popular. The problem was that when running in IE everything
seemed to work fine for the users but once they switched to the outlook plugin
they will constantly get asked for a username and password. The root cause of
this is because in some Rollup Microsoft decided that the plugin would add the
URL it uses to access CRM to the trusted sites list upon startup and this is
the root of the problem.<o:p></o:p><br />
<br />
Adding the URL automatically to the trusted sites list is great for users of
CRM Online or other third party hosted CRM. Back in the early days of CRM
Online one of the most asked questions was why is CRM not loading properly in
my environment and the most common answer was that CRM was not in the trusted
sites list of IE. Unfortunately for those of us who use the on-premise version
having CRM in the trusted sites list is a little less than convenient. One
downside of having the site in the trusted sites list is that integrated
authentication does not happen in the trusted sites zone, I don't condone
enabling integrated authentication in the trusted sites zone just to get this
working there is a better solution below. As you may know integrated
authentication only happens in the Intranet zone with the IE default settings.
So in order to get the plugin to stop asking for a username and password you
will need to add the site to the Local Intranet Sites list. <o:p></o:p><br />
<br />
<em>Internet Options -> Security -> Local Intranet -> Sites ->
Advanced </em><o:p></o:p><br />
<br />
Be aware when adding your site to this list that adding a wildcard will not
work in this case it needs to be the exact URL that you use to access CRM. So
if I work at foo.com having *.foo.com in the local intranet list will not work,
if this is done the plugin will still add the specific site to the trusted
hosts and authentication will still be broken. You need to add the exact CRM
host ex. <a href="https://crm.foo.com/"><span style="color: blue;">https://crm.foo.com/</span></a> when the
outlook plugin sees this in the local intranet list it will skip the step of
adding the URL to the trusted sites list and authentication will work successfully.
As an easy solution I suggest just pushing this change out to all hosts via
group policy, if you do not use group policy then you will need to manually go
and add this URL to the local intranet sites. <br />
<br />
If you have yet to install the outlook plugin then you should be good and everything should work fine. However if the outlook plugin is installed on the machine you need to uninstall (and double check to make sure the site is still in the local intranet zone) and then re-install the plugin.<br />
<br />
I wish there was a better solution to not have the plugin add its URL to the
trusted sites list but unfortunately this is the only solution I have been able
to find that works. <o:p></o:p>Matthew Churillahttp://www.blogger.com/profile/06699782042171994247noreply@blogger.com3tag:blogger.com,1999:blog-3155962902335259216.post-47103008281002213052012-01-12T14:18:00.001-05:002012-01-16T08:47:45.175-05:00HTTP 503: Service Unavailable message from SharePoint 2010<span style="font-family: "Times New Roman","serif"; font-size: 12pt; mso-fareast-font-family: "Times New Roman";">I have been upgrading a number of
SharePoint 2010 farms to the December 2012 cumulative update. During the
install process I have experienced repetitive failures when running the
SharePoint 2010 Products Configuration Tool. The tool would advance to some percentage
of step 9/10 and then it will just mysteriously fail with no reason given in
the dialog box or in the configuration log files. Fortunately recovering from
this failure is easy, all you need to do is just re-run the configuration
wizard. While I have yet to confirm this, and I'm not sure I can confirm it in
any way, I believe this issue might be related to us running SharePoint 2010 on
servers that only meet the minimum suggested requirements for memory and
processor. <o:p></o:p></span><br />
<br />
<div class="MsoNormal" style="line-height: normal; margin: 0in 0in 0pt;">
<span style="font-family: "Times New Roman","serif"; font-size: 12pt; mso-fareast-font-family: "Times New Roman";">Unfortunately after successfully
running the SharePoint 2010 Productions Configuration Wizard and starting
Central Administration I was presented with an HTTP Error 503 Service
Unavailable. Thinking that this might have just been an issue that affected our
Central Administration site I next attempted to browse to a normal site and
still got a 503 Service Unavailable message. So I started to scour the internet
looking for an answer but couldn't seem to find any reported problems that
matched the problems we were having, and there were no signs of a solution that
seemed to make sense given the symptoms of our problem. So I began the task of
trying to figure out the problem myself. <o:p></o:p></span></div>
<br />
<div class="MsoNormal" style="line-height: normal; margin: 0in 0in 0pt;">
<span style="font-family: "Times New Roman","serif"; font-size: 12pt; mso-fareast-font-family: "Times New Roman";">I started my search at the bottom
and opened up the windows service console. Checking the related IIS services they
all seemed to be started and running without errors. This lead me to start up
the IIS Manager and search for something within it that would suggest it was
the cause of these issues. Eventually I was looking at our Application Pools
for SharePoint and noticed that the Application Pool for our Central
Administration was stopped and in addition a number of other Application Pools
related to SharePoint were stopped (You can see this next to #1 in the image
below). I started up all of the stopped application pools and then went back
and tried the Central Administration site and it was there and working. Just to
ensure that this problem did not arise after a reboot I double checked the
advanced settings for each Application Pool (#2 below) and ensured that the
Start Automatically property was set to true (Pictured below). <o:p></o:p></span></div>
<br />
<br />
<strong>The short version of the above for people like me to who hate reading and are just here for the solution:</strong><br />
<br />
<div class="MsoNormal" style="line-height: normal; margin: 0in 0in 0pt;">
<span style="font-family: "Times New Roman","serif"; font-size: 12pt; mso-fareast-font-family: "Times New Roman";">Received HTTP Error 503 Service Unavailable
when accessing SharePoint Central Administration and other sites after a failed
execution of the SharePoint 2010 Products Configuration Wizard. <o:p></o:p></span></div>
<br />
<div class="MsoNormal" style="line-height: normal; margin: 0in 0in 0pt;">
<span style="font-family: "Times New Roman","serif"; font-size: 12pt; mso-fareast-font-family: "Times New Roman";">Found the problem was because our
SharePoint IIS application pools were not started (1).<o:p></o:p></span></div>
<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi4oY_N5EZ_ihPVjh8dsUIBZRik9judmobVwcKJy2WLmOb6g03LF2tpe9oOcSxPhyphenhyphenKeg2gG26mqsZZ4hj9eBbatk5Fd_5R2-Jm2yfnAABME47hlo_I4zSeawJlq8kk6PCPD7r7v85N3g6nT/s1600/Application+Pools.bmp" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="286" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi4oY_N5EZ_ihPVjh8dsUIBZRik9judmobVwcKJy2WLmOb6g03LF2tpe9oOcSxPhyphenhyphenKeg2gG26mqsZZ4hj9eBbatk5Fd_5R2-Jm2yfnAABME47hlo_I4zSeawJlq8kk6PCPD7r7v85N3g6nT/s640/Application+Pools.bmp" width="640" /></a></div>
<br />
Started the application pools and double checked the advanced settings (2) to ensure that the application pool was set to automatically start. <br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjIjrDOGWA5qLckNKkwtnCs0zT1KxHDul0UO_C3W4BTC_NQPo8T6y6za26FkivasKTXNwPBcYRHvStKFfxwTQ2cS-GEY14kvLhVm23nnuI57ezaBkxX2iJr0AXZ0FB-NwljO_sfhspbe1Xl/s1600/Advanced+Settings.bmp" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="320" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjIjrDOGWA5qLckNKkwtnCs0zT1KxHDul0UO_C3W4BTC_NQPo8T6y6za26FkivasKTXNwPBcYRHvStKFfxwTQ2cS-GEY14kvLhVm23nnuI57ezaBkxX2iJr0AXZ0FB-NwljO_sfhspbe1Xl/s320/Advanced+Settings.bmp" width="261" /></a></div>
<br />
<br />
<div class="MsoNormal" style="line-height: normal; margin: 0in 0in 6pt;">
<span style="font-family: "Times New Roman","serif"; font-size: 12pt; mso-fareast-font-family: "Times New Roman";">SharePoint was running fine after the application pools were
started and all SharePoint requests were processed successfully. <o:p></o:p></span></div>Matthew Churillahttp://www.blogger.com/profile/06699782042171994247noreply@blogger.com4