Many organisations, taking SharePoint on for the first time, opt to go for a single server instance deployment of SharePoint. However, they find it easy to forget in the heat of getting a single SharePoint production environment deployed, that without defining a fully available topology that one may be creating a single point of failure scenario.
You may come across this error when attempting to carry out a PSConfig upgrade using office2010-kb2597014-fullfile-x64-glb: An exception of type Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException was thrown. Additional exception information: An update conflict has occurred, and you must re-try this action. The object SPUpgradeSession Name=Upgradexxxx was updated by Domain\UserID, in the PSCONFIG (xxxx) process, on machine SharePointServer01. View the tracing log for more information about the conflict.
People have been requesting me do a shortened article to cover SharePoint Implementation from a higher level; a kind of whats my the key steps required to deliver SharePoint to a client. Please note there’s a whole bunch of webcasts coming soon to go into some more detail on each of the steps, so watch this space. If you need further information go ahead and give me a shout! Happy Reading!
Had issues when configuring FAST on SharePoint 2010, specifically with resolving unexpected errors occurred while communicating with Administration Service. Needed to configure FAST Search Keywords.
