Wednesday, March 30, 2011
Issue:
After installing a SharePoint Update and running the Configuration Wizard you may notice that the User Profile Synchronization Service Application has stopped. Attempts to restart the User Profile Synchronization Service Application may prove unsuccessful.
Symptoms:
1) The User Profile Synchronization Service Application Fails is stopped and fails to restart
2) The following errors appear in the Event Viewer:
a. Detection of product '{90140000-104C-0000-1000-0000000FF1CE}', feature 'PeopleILM' failed during request for component '{1681AE41-ADA8-4B70-BC11-98A5A4EDD046}'
b. Detection of product '{90140000-104C-0000-1000-0000000FF1CE}', feature 'PeopleILM', component '{1C12B6E6-898C-4D58-9774-AAAFBDFE273C}' failed.
The resource 'C:\Program Files\Microsoft Office Servers\14.0\Service\Microsoft.ResourceManagement.Service.exe' does not exist.
Solution:
Give the Network Service account read/Execute permissions to the following folders:
\Program Files\Microsoft Office Servers\14.0\
\Service
\SQL
\Tools
Open Central Admin—>Application Management—>Manage Services on Farm—> Start the Profile Synchronization Service
Special Thanks to Greg Carter (HoganTaylor)
Saturday, March 26, 2011
Friday, March 25, 2011
Friday, November 19, 2010
Thanks to all those who attended.
Tuesday, October 26, 2010
While at the Tyson Developers Conference last week I attended a productivity session by Claudio Lassala. During the session he introduced us to a time management technique known as Pamadoro. Essentially, tasks are performed in 25 minute blocks with a five minute break between each work block. Today, I found a tool called Keep Focused on CodePlex.com. The tool allows a task to be entered then the 25 minute timer count down is started. I used Keep Focused all day and really felt quite productive.
Give Keep Focused a try and see if your productivity doesn’t improve.
Thursday, September 09, 2010
Overview:
Creating a custom master page provides the greatest flexibility for branding a SharePoint Implementation. However, there are many hidden traps to be aware of when creating a custom master page. For example, it is usually best not to start from scratch but to use a copy of the v4.master or starter master page http://startermasterpages.codeplex.com/ created by Randy Drisgill.
Lessons Learned:
The v4.master is the new default master used for SharePoint 2010 and creating a new custom master from a copy of the original v4.master will ensure the inclusion of expected SharePoint 2010 User Experience Functionality.
After deploying a custom master page based on the v4.master we began seeing a “You must specify a value for this required field” message box whenever trying to edit or add new list items and perform other routine tasks.
After much research the solution was found on this blog post: http://blogs.msdn.com/b/tmathis/archive/2010/03/18/you-must-specify-a-value-for-this-required-field-error-when-hidding-placeholderpagetitleintitlearea.aspx
It has always been a good practice to place unused content place holders within a hidden ASP.NET Panel Control. However, the message box error was caused by the PlaceHolderPageTitleInTitleArea content place holder being contained within an ASP.NET Panel Control with the hidden attribute set to false. The resolution was to remove the hidden=false attribute and hide the ASP.NET Panel using a CSS Style. The style can be simply added to the master page for easy deployment.
Over the weekend I spun up a new virtual machine for a practice TFS 2010 Installation. The TFS installation process is much improved. It can loosely be broken into two phases which are installation and configuration. The installation is the easy part which basically prepares the server and copies some bits to the drive. The configuration is a little more difficult but provides some guidance to help make the important decisions. During the configuration you make the following three key decisions.
- Install WSS 3.0 or use an existing SharePoint installation
- Install SQL Express or use an existing SQL Instance
- Install Reporting Services
During the configuration I received TF255275 Error during the Reporting Services portion of the configuration. My reporting services database was created and configured for SharePoint Mode.
Reference: http://www.sathishtk.com/blog/post/2009/10/15/TFS-2010-TF255275-Error.aspx
Despite referencing the TFS 2010 Beta the above blog post helped resolve the issue. Essentially, I had to change the database to Native Mode. However, as a commenter mentions I had to delete the Report Database and recreate it in Native Mode before the configuration wizard would complete.
Wednesday, August 18, 2010
After completing a MOSS 2007 SP2 to SharePoint 2010 (Enterprise) upgrade all seemed to go well. However, I soon began to notice some subtle differences between site collections. For example, the home site collection was missing the new Tag Cloud Web Part. So I seemed like perhaps a Feature wasn’t Activated. After a little digging I learned that there is a Feature called Portal Layouts which is responsible for provisioning artifacts like the new Tag Cloud Web Part.
Solution:
To Activate the Feature you can use either stsadm or PowerShell. The syntax for both is listed below:
STSADM:
stsadm -o activateFeature -name "PortalLayouts" -url "http://<SharepointServer>/sites/<SiteCollection>" –force
PowerShell
Enable-SPFeature FeatureFolderName -Url http://server/site/subsite
Monday, June 07, 2010
Issue:
A client was experiencing very strange behavior following an upgrade from MOSS 2007 to SharePoint 2010 Server. In a nutshell some documents such as Word (.doc and .docx) would open while others such as Excel (.xls and xlsx) and PDF documents would not open.
Note: By open I mean when clicking on an Excel document, stored within a document library, it would not open in Excel installed on Windows 7, Vista, XP, etc.
Furthermore, the file type icons that normally display next to familiar documents such as Excel were missing and a missing image red x was displayed.
Thoughts:
The behavior of unrecognized File Types and missing document icons seemed to indicate an issue with the docIcon.xml configuration which is commonly located here: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\XML.
However, after inspecting this file on each server I could find nothing apparently wrong. Finally, one last tedious inspection revealed the issue. Following the upgrade we had to reconfigure the Adobe PDF IFilter which meant adding the following key to the docIcon.xml file:
<Mapping Key="pdf" Value="pdficon_small.gif" />
After looking at this entry more closely I noticed that the double quotations marks looked italicized “. This meant the configuration contain extra characters and was most likely edit with an editor like word pad instead of note pad.
Tip: Never use Word Pad to edit configuration files because it will add additional characters and likely corrupt the configuration file.
Solution:
I removed the unsupported double quotes and replaced them with unformatted double quotes. Viola, we could now open Excel and PDF Files again! Even better the cute little document type icons came back! :)
Further Explanation:
The reason the Excel Documents types became unavailable is because these document type mappings were located after the pdf file mapping within the docIcon.xml. Essential the invalid PDF entry broke all entries below it.
Hope this helps someone else!!!
Saturday, May 22, 2010
Besides surviving countless beatings from my favorite two year old and a two hour crying fit from my 4 month old son I’ve attended several great community events. Thanks wifey :).
May 3rd: Oklahoma City Developers Group: Stop Drowning In Technical Debt! As the INETA Membership Mentor of Oklahoma I set a goal this year to try and encourage more collaboration between the strong communities existing in Tulsa and Oklahoma City. To accomplish this I have presented three times so far in OKC. On May 3rd I presented to a crowd of about 50 for the lunch meeting and 20 for the evening meeting. Both meetings were great.
May 4th: MSDN Events Launch 2010 Highlights – This event was well attend and provided overview demos of Windows 7, SharePoint 2010, SQL Server 2008 R2, Visual Studio 2010, Silverlight 4, etc.
May 13th: Tulsa SharePoint Interest Group: SharePoint 2010 Launch Event – For our May meeting we wanted to do something extra special. May 12th was the official launch of SharePoint 2010 and as a result we wanted to organize a Launch Event of our own. We held the event at Dave and Busters thanks to several general sponsors (K2, GDH Consulting, Metalogix, TEKSystems, The Rowland Group,
High Tech Resources). The event exceeded our expectations with about 50 people in attendance. We are also very thankful for Eric Shupps being our special guest speaker.
May 22nd: SQL Saturday 35 (Dallas) – I left Tulsa, OK at 3:30 in the morning to Drive down to Dallas where I met up with some friends including Shawn Weisfeld. I have never presented at a SQL Saturday before but the event is similar to other events such as code camps or SharePoint Saturdays which I regularly present at. I resented “SharePoint, A DBA’s Nightmare!” to a room of about 40 people. The session was very conversational with some great questions. The goal of the presentation was to help the audience understand SharePoint’s architecture a little better and know the pro/cons of certain decisions. We discussed such topics as database naming conventions, performance tips, and database maintenance.