SharePoint Madness

All about SharePoint and Office365

SharePoint 2016 IT Preview Prerequisite Installer Errors

Posted by Amit Bhatia on September 1, 2015


I was installing the prerequisites for SP 2016 IT preview on of the test HyperV machine (Windows Server 2012 R2) with no outside internet connection.

I manually downloaded the prerequisites in another machine and manually install the pre-requisites. Some of the SharePoint farms are developed with no internet access and so I tried this scenario to gain some experience. I got into few issues while installing the prerequisites.

First Error: Prerequisites fails with MSI installed error code 1603 while installing AppFabric 1.1

Cause: The path to the PowerShell executable that is needed for the AppFabric installation is incorrect.


  • Go to My Computer, right-click Properties
  • On the System’ page, click Advanced System Settings on the left-side pane.
  • If you receive a UAC prompt, click on Yes to launch the System Properties dialog box
  • From the Advanced tab, click Environment Variables
  • Within the System Variables section in the lower half, select PSModulePath and click on Edit (or double-click PSModulePath‘)
  • Remove ” from the end

I re-run the SP 2016 installer and now getting a 2nd error.

Second Error: “The process of installing the prerequisite failed” along with “Setup is unable to proceed due to the following error(s): Windows Server Appfabric is not correctly configured. You should uninstall Windows Server Appfabric and reinstall it using the SharePoint Products Preparation Too.”

Solution: Run the SharePoint 2016 Prerequisite Installer:  prerequisiteinstaller.exe /AppFabric:prerequisiteinstallerfiles\AppFabric1.1-RTM-KB2671763-x65-ENU.exe

Note: Please make sure you have this file “AppFabric1.1-RTM-KB2671763-x65-ENU.exe” downloaded.

The machine will be restarted and the issue will be resolved. Now, you can go ahead and install SP 2016 IT Preview.


Posted in SP2016 | Leave a Comment »

How Microsoft is reinventing Productivity and How Yammer fits into that strategy?

Posted by Amit Bhatia on August 26, 2015

Consider Microsoft Office 365 as a door that is open to organizations of all sizes to take advantage of enterprise-caliber productivity applications, social computing, and unified communications. And all these advantages happen without being trapped behind a firewall or constrained by the cost of implementation and maintenance as in the last decade.

Yammer has been an interesting proposition coming from Microsoft Stable. Microsoft slogan with Yammer is “Change the way you work”. It is a vital step in the path of “Reinventing Productivity” as Satya recently said in one of the forums. Before jumping on how Yammer will prove to be a great productivity asset, let us first dive into why Microsoft bought Yammer and continuing to invest in this product. What made Microsoft want to spend more than $1 billion for the social networking company? It could be because Yammer successfully marketed its business virally, offering a basic service for free and then convincing customers to pay for additional features. Before they bought Yammer, Microsoft’s social networking capabilities were weak relatively to its peers. Yammer was brought in to set it right and renewed focus on enterprise social networking. I think the answer is they will integrate Yammer with absolutely all their cloud offerings, and they will also social-enable their on-premise software with web-based components.

Gartner defines social software for the workplaces as software that is used principally for enterprise collaboration by putting individuals, teams, communities and networks in contact with each other. The principal gains in using this software and which Gartner sees as key includes:

  • Making professional contacts.
  • Accessing contact lists of those that can offer advice, reference and referrals.
  • Team formation and collaboration on tasks.

The current social and collaboration market is worth an estimated US$ 840 million (in Sep 2013) but, unlike some other software sectors, is growing strongly. Gartner estimates that between now and 2016, the market will grow 13.4% annually and will be worth US$ 1.4 billion.

That said, the business objectives of social enterprise software remain the same. Those that are responsible for developing enterprise strategies around social software are still looking to:

  • Enhance enterprise information sharing and increase productivity.
  • Support teams across the enterprise by offering learning possibilities and insights into best business practice.

Gartner recognizes Microsoft as a Leader positioned highest in ability to execute and furthest in completeness of vision for social software.

By integrating the components of Yammer with Office 365, Microsoft is uniquely positioned to deliver value to their customers. They also continue to help people get more done and collaborate more effectively with exciting new products like Office Delve, a new way to discover relevant information and connections from across your work life. Powered by the Office Graph, Delve shows you information based on what you’re working on and what’s trending around you. Delve is based on Machine learning and it could be labelled as “Flip-board” like service for Office 365. Delve displays information based on “the work they are doing and the people with whom they are engaging,” in a card-like user interface. With Delve, the idea is users won’t have to remember where their information is stored or who shared it. This information will be surfaced for users automatically, but only when the appropriate permissions are granted. This is going to redefine what I refer to as intelligent social collaboration. Delve uses Microsoft’s internally built Office Graph to ascertain relationship between people, content and activity across Office 365.



Now, coming to the critical part on how Office 365 plays a crucial rule in reinventing productivity. Here are the top 10 upcoming features that will play a crucial role in evolving that strategy.

  • External Groups In coming releases for Office 365 you may invite customers, partners, and vendors to join your internal groups, so they can quickly access the information they need.
  • Discovery feed surfaces conversations users might miss from relevant groups, Updates in the Discovery feed clearly identify which groups the conversations come from and provide the ability to quickly navigate to and join the groups users are not already a member of straight from the feed.
  • User activity reports will allow you to audit SharePoint and OneDrive for Business user actions such as views, edits, deletes, downloaded files, and sharing of files. These reports will be available in the Compliance Centre. This will be great for metric perspective and evaluating ROI.
  • Yammer’s Group Updates feed for Mobile Apps provides a simple workflow through relevant group content to help users catch up on urgent conversations and discover what others are working on. Users can navigate easily between the feed and their groups, as well as join groups they’re not already a part of, from the feed itself. The Group Updates feed will come to Android first with iOS following shortly after.
  • Yammer integration with the Office 365 Group service managed by Azure Active Directory enables standard membership across Office 365.
  • Office 365 Groups Mobile Apps A mobile app that surfaces Outlook Group conversations and files across iOS, Android and Windows Phone by the end of 2015.
  • Office Online multi-user co-authoring in Yammer Office Online provides an immersive document collaboration experience inside Yammer. Co-author Word, PowerPoint, and Excel files uploaded to Yammer with other people using the immersive Office Online experience. Changes are automatically saved in Yammer where you have the ability to review the version history of each file and mark documents “Official.”
  • Skype for Business for iOS and Android The current Lync mobile applications with Skype for Business mobile in the Google app store will be replaced with Skype for Business.
  • Skype Meeting Broadcast allows up to 10,000 people to view a broadcast of a Skype for Business meeting on the Internet.  This capability is useful for a variety of scenarios, including internal, organization-wide “Town Hall” style meetings and public webinars.  Broadcasts may be viewed live, or after the event.
  • Save to OneDrive for Business in Outlook for iOS & Android Outlook for iOS & Android will be able to view, send files from and save attachments to OneDrive for Business in the Files tab. Today, Outlook works with OneDrive, Dropbox, Box, Google Drive & iCloud.

As a core part of Office 365, Yammer is committed to leveraging the Office 365 Groups membership service, which will significantly improve and expand the Yammer experience.

Some of you have asked how Yammer and Office 365 Groups co-exists together. Office 365 Groups is an architectural element of Azure Active Directory—not an Office 365 app or experience—whereas Yammer is the immersive social experience within Office 365. Together with identity, Office 365 Groups and Office Graph comprise a shared intelligent fabric across Office 365 that’s also extensible.

Yammer is a critical product in fulfilling this strategy but enterprise now looks to chain Yammer with other products from office 365 stable to see what fits best in their enterprise scenarios and business strategy.



As you can see, every app in Office 365 and beyond will hook into the intelligent fabric. Your enterprise strategy would be incomplete without the above intelligent fabric. Each Office 365 app is suitable to hook into certain scenarios and it is up to the Microsoft partners and businesses to find that right product fit for the right business scenario. From Microsoft perspective, it is fitting into their Cloud-First Mobile-First Strategy.


Posted in Office365, Productivity, SharePoint Online, Yammer | Tagged: , , , | Leave a Comment »

SharePoint 2013 Workflow – GOOD TO KNOW

Posted by Amit Bhatia on November 7, 2013


It’s been some time since I wrote my last blog post on “Missing Feature ID error while doing SharePoint 2010 CU patching”.

I have been working on SharePoint 2013 Workflows and found them to be an interesting tool to map the business process of organisations. In my analysis, I found that lot of developers and Tech Leads make wrong assumptions during the architecture, design and development of these workflow. Therefore, I am here to write on the best practices, similarity/dissimilarity between SharePoint 2010 and SharePoint 2013 workflows.

Best Practices to be followed for SP 2013 workflows:-

  • Workflow Design: Better to model a business process in a single workflow than to break the workflow logic into smaller workflows
  • Workflow Approval Action: Use “Stages” feature in the Approval action instead of creating multiple Approval actions
  • Reusable workflows should use Association Columns:  If you create a reusable workflow that relies on its list having a specific field,  you make the field an association column.
  • DO NOT use a user account for elevated privileges for impersonation : Use a generic account or neutral account for workflow impersonation actions
  • Variable Check: Check variables for non- null, correct data type and expected values to prevent errors
  • Use Trace Log for debugging: Use Trace Log effectively before the beginning and ending of a step to log into Trace logs for effective debugging
  • Write strings and variables to the history list by using the Log to History List action for debugging purposes

Things to remember:-

  • Workflow execution: Workflow execution engine now lives outside of SharePoint and resides in Windows Azure. The new workflow infrastructure introduces Workflow Manager Client 1.0 as the new workflow execution host. Whereas in previous versions workflow execution was hosted in SharePoint itself, this has changed in SharePoint 2013. Workflow Manager Client 1.0 is external to SharePoint and communicates using common protocols over the Windows Azure service bus, mediated by OAuth
  • Fully declarative Workflows: Workflow in 2013 is based on Windows Workflow foundation WF4 platform and is fully declarative. Workflows are no longer compiled into managed assemblies and deployed to an assembly cache. Instead, XAML files define your workflows and schedule their execution
  • Addition to the Workflow Object Model : Workflow Service Manager allow you to manage and control your workflows and their execution. The primary zones of interaction for the services manager are deployment, messaging, instance control, and interoperability with SharePoint 2010 workflows
  • Improved SharePoint Designer: SharePoint Designer can now create and deploy both SharePoint 2010 and SharePoint 2013 workflows. Visual Studio 2012 not only provides a designer surface for creating declarative workflows, but it can also create apps for SharePoint and solutions that fully integrate Workflow Manager Client 1.0 functionality
  • Workflow associations: Workflow associations (which are built on the WF concept of subscriptions) are the SharePoint infrastructure pieces that support Windows Azure to connect the infrastructure to customer data
  • Default Scope for SharePoint workflows:  SPList (list workflows) and SPWeb (Site Wirkflows) are the default scope supported by messaging infrastructure.  SharePoint 2013 does not support workflows that are scoped to a content type SPContentType
  • If a Workflow starts automatically on a repeatable event, it cannot start workflow of a given association until the existing instance of workflow association has completed running
  • SharePoint workflow Interop: SharePoint workflow interop enables SharePoint 2010 workflows (which are built on Windows Workflow Foundation 3) to be called from SharePoint 2013 workflows, which are based on Windows Workflow Foundation 4. This allows you to execute 2010 workflows from within 2013 workflows

I hope you would take the above points into consideration while designing and developing SharePoint 2013 workflows.

See you later.

Posted in SP2013, Workflows | 1 Comment »

Missing feature Id throws exception while installing SharePoint Patch/CU

Posted by Amit Bhatia on June 19, 2013

Hello friends!

I am writing this piece of blog to help the SharePoint administrator/developer understand one of the exceptions which comes up during CU installation on the SharePoint farm.

Exception information:

[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [6/18/2013 7:40:05 PM]: Found a missing feature Id = [065c78be-5231-477e-a972-14177cc5b3c7]
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [6/18/2013 7:40:05 PM]: The feature with Id 065c78be-5231-477e-a972-14177cc5b3c7 is referenced in the database [WSS_Content_Lam_cn], but is not installed on the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [6/18/2013 7:40:05 PM]: Found a missing feature Id = [0806d127-06e6-447a-980e-2e90b03101b8]


There are some of the health rules which are absolutely critical to maintain the consistency of the farm environment. One such health rule is missing server dependencies. You need to remove unreferenced or old objects which do not have a reference within SharePoint in order to install the patch successfully.


  1. Go to SharePoint Central Administration site –> Monitoring –> Review problems and solutions
  2. Run the Missing Server dependencies rule in the SharePoint Health Analyzer rule to identify all the missing server dependencies.
  3. Once you identified all the missing server objects such features using feature id as identifier you may use the Feature admin tool or sharepoint admin tool from codeplex to remove them from SharePoint farm.
  4. You may use the below tool from codeplex to remove the faulty features >>
  5. Once removed, you can run the health rules again using the health analyzer to ensure the rule run successfully without any errors.
  6. Try to install the patch again and run PSConfig using command line (advisable).

I hope this may help you to get around one of the frustrating exceptions while installing CU 🙂

Posted in SharePoint 2010, SharePoint 2010 CU | Leave a Comment »

16 Key facts on User Authentication methods in SharePoint 2013

Posted by Amit Bhatia on February 7, 2013

I have been working on planning the user authentication methods on SP 2013 and came across few facts which may prevent few headaches later while implementing the user authentication in SP 2013.

  1. Office Web Apps can be used only by SharePoint 2013 web applications that use claims-based authentication –  Office Web Apps rendering and editing will not work on SharePoint 2013 web applications that use classic mode authentication. If you migrate SharePoint 2010 web applications that use classic mode authentication to SharePoint 2013, you must migrate them to claims-based authentication to allow them to work with Office Web Apps.
  2. SharePoint 2013 also supports anonymous authentication – Users can access SharePoint content without validating their credentials. Anonymous authentication is disabled by default. You typically use anonymous authentication when you use SharePoint 2013 to publish content that does not require security and is available for all users, such as a public Internet website. In addition to enabling anonymous authentication, you must also configure anonymous access (permissions) on sites and site resources.
  3. In Forms based authentication, credentials are sent in plain-text format – You should not use forms based authentication unless you are using Secure Socket Layer (SSL) to encrypt the traffic.
  4. Active Directory Federation Services (AD FS) 2.0 is a SAML token-based authentication environment
  5. Kerberos authentication improves performance and page latency – Kerberos requires the least amount of network traffic to AD DS domain controllers. Kerberos can reduce page latency in certain scenarios, or increase the number of pages that a front-end web server can serve in certain scenarios. Kerberos can also reduce the load on domain controllers.
  6. Kerberos should not be used in internet facing deployments – Kerberos authentication requires client computer connectivity to a KDC and to an AD DS domain controller.
  7. In mutiple SAML based authentication providers scenario you can only use one token signing certificate in a farm – This is the certificate that you export from an IP-STS and then copy to one server in the farm and add it to the farm’s Trusted Root Authority list. Once you use this certificate to create an SPTrustedIdentityTokenIssuer, you cannot use it to create another one. To use the certificate to create a different SPTrustedIdentityTokenIssuer, you must delete the existing one first. Before you delete an existing one, you must disassociate it from all web applications that may be using it.
  8. No need for Single affinity in Load balanced Scenarios in SP 2013 – You no longer have to set network load balancing to single affinity when you are using claims-based authentication in SharePoint 2013
  9. People Picker search functionality does not work if the web application uses SAML based authentication – When a web application is configured to use SAML token-based authentication, the SPTrustedClaimProvider class does not provide search functionality to the People Picker control. Any text entered in the People Picker control will automatically be displayed as if it resolves, regardless of whether it is a valid user, group, or claim. If your SharePoint 2013 solution uses SAML token-based authentication, plan to create a custom claims provider that implements custom search and name resolution.
  10. Claims based authentication can have multiple authentication providers in a single zone
  11. Webapplication can only be created with Powershell for Classic mode in SP 2013
  12. Classic Mode authentication can only support one type of authentication per zone – Classic Mode only uses Windows authentication mode.
  13. Forms based and Windows based  authentication can only be used once in a multiple authentication method in a single zone
  14. Atleast one zone must be configured to use Crawl – Crawl component can only use NTLM based authentication. If NTLM authentication is not configured on the default zone, the crawl component can use a different zone that is configured to use NTLM authentication.
  15. Default zone should always be used for most secured settings –  The most secure authentication settings are designed for end-user access. End-users are most likely to access the default zone.
  16. Keep the zones to a minimum – Each zone requires an IIS website and adds overhead.

Posted in Authentication, SP2013 | Tagged: , , | 2 Comments »

Content Enrichment Service – For finer SharePoint 2013 Customization Search experience

Posted by Amit Bhatia on February 6, 2013

There has been some new features in SharePoint 2013 Search . So, this time I come up with a new topic on Content Enrichment Service and how it makes SharePoint 2013 search a pleasent experience.

What is a Content Enrichment web service?

Content enrichment web service callout in SharePoint 2013 enables developers to create an external web service to modify managed properties for crawled items during content processing. The ability to modify managed properties for items during content processing is helpful when performing tasks such as data cleansing, entity extraction, classification, and tagging.

Here are some examples of what you could do:

  • Create new refiners by extracting data.
  • Calculate new refiners based on managed property values.
  • Set the correct case for refinable managed properties.

Content Processing Engine

The content enrichment web service is a SOAP-based service that you can create to receive a callout from the web service client inside the content processing component. The content processing component receives crawled Properties from the crawler component and outputs managed properties to the index component. it is important to note that the web service callout can only read managed properties. Any crawled property value that the web service needs as input must first be mapped to a managed property. The web service callout can only access managed properties that exist before the web service callout, and not managed properties that are set further down in the flow. The web service callout can pass managed properties back to the flow, but only if they are a part of the Search schema.

In our example we have list of books with fields such as book title, author, written year, Publisher and other fields. The book title are not in proper casing as some of the items in the list have lower case titles and some titles have upper case titles.

Step 1: Create the web service

Here is a web service that read the books list and create some manged properties as refiners.

For a basic implementation, do the following:

  1. Include the Microsoft.Office.Server.Search.ContentProcessingEnrichment.dll located in C:\Program Files\Microsoft Office Servers\15.0\Search\Applications\External in your project as a reference.
  2. Implement IContentProcessingEnrichmentService as a web service.

using System;
using System.Collections.Generic;
using System.IO;
using Microsoft.Office.Server.Search.ContentProcessingEnrichment;
using Microsoft.Office.Server.Search.ContentProcessingEnrichment.PropertyTypes;
using System.Globalization;
using System.Threading;

namespace BookService

    public class BookService : IContentProcessingEnrichmentService
        // Define variables to hold the managed properties 

        private Property<string> newBookType = new Property<string>();
        private Property<DateTime> NewDateTimeBookModified= new Property<DateTime>();
        private readonly ProcessedItem processedItemHolder =
            new ProcessedItem
            ItemProperties = new List<AbstractProperty>()

        public ProcessedItem ProcessItem(Item item)
            // Iterate over all managed properties passed to the web service.
            foreach (var property in item.ItemProperties)
                var s = property as Property<string>;
                if (s != null)
                    CultureInfo cultureInfo =
                    TextInfo textInfo = cultureInfo.TextInfo;
                    string normalizedString = textInfo.ToTitleCase(s.Value.ToUpper());
                    s.Value = normalizedString;

                var l = property as Property<string>;
                if (l != null)
                    // The value of the new string managed property the
                    //  type of book.
                  newBookType.Name = “BookType”;
                 newBookType.value = “”; //get the book type value


                // Set the time for when the properties where added by the
                //  web service.
                NewDateTimeBookModified.Name = “ModifiedByBookType”;
                NewDateTimeBookModified.Value = DateTime.Now;
            return processedItemHolder;


Step 2:  Create new Managed properties that the web service populates

$mp = New-SPEnterpriseSearchMetadataManagedProperty
-SearchApplication $ssa
–Name “ModifiedByBookType”
–Type 1
–Queryable $True
$mp.Refinable = $True
$mp = New-SPEnterpriseSearchMetadataManagedProperty
-SearchApplication $ssa
–Name “BookType”
–Type 1
–Queryable $True
$mp.Refinable = $True

Step 2:  Crawl and Search the content.

Enable and configure the web service callout.

$config = New-SPEnterpriseSearchContentEnrichmentConfiguration

$config.Endpoint = “” //Add the endpoint for ex as http://localhost:712/BookService.svc for your web service.

$config.InputProperties = “Author”, “Title”, “Publisher”

$config.OutputProperties =  “Author”, “Title”, “Publisher”,

“ModifiedByBookType, “BookType”


-SearchApplication $ssa

-ContentEnrichmentConfiguration $config

Start a full crawl now of the Books List. In the refinement panel in the search center, enter the new managed properties and enter them as refiners. Save, Checkin and Publish the changes to the Refinement web part.

Now, you can set the filter for book type such as Book is “Fiction” and see the results:)

Here is the link to MSDN documentation on Content Enrichment Web Service for SP 2013.

Posted in SP2013 | Tagged: , , , | Leave a Comment »

Backup Strategy for SharePoint 2010

Posted by Amit Bhatia on February 5, 2013

We were asked to develop the backup strategy on SharePoint 2010 for one of our client. There were two web applications with 3 site collections. Please note that this article does not give steps on how to write backup powershell commands. Instead this talks about the backup strategy being adopted in an enterprise environment.

Web Application 1 hosts 2 Site Collection

Web Application 2 hosts 1 site collection

The SP 2010 Farm backup requires different strategies for Database backup and Farm/web/site collection backup. Here I give you an example of one Site collection. You may backup multiple site collection as well.

SQL Server Backup (Created by the SQL DBA)

The backups are broken up into Full Backups and Transaction log backups.

  1. Full Backup

The database backups are run via a SQL Server job named UserDatabases.Full Backups.  The Full backup job runs each night at 8:45pm in the evening.  They are written to the directory U:\SQL Backup\<dbname>\.  The naming convention is <dbname>_backup_yyyy_mm_dd_hhmmss_<uniquenumber>.bak.

The database backup files are kept for three days and are then deleted.

2.        Transaction Logs

The transaction log backups are run via a SQL Server job that runs every 30 minutes on the half hour and the hour throughout the day.  The SQL Server job is named UserDatabases.Log Backups.  The logs are written to the directory U:\SQL Backups\<dbname>\. The naming convention is <dbname_yyyy_mm_dd_hhmmss_<lognumber>.trn.  The log files are kept for two days then deleted.

3.     Mirroring

The following Sharepoint databases are mirrored to the DR server  continuously.

  • WSS_Content (content database)

4.    Networker backups

The database files and the transaction logs are backed up by Networker daily at 9:00pm.

SharePoint Farm, Site Collection and Content Database Backup

We have three scheduled tasks running on the SharePoint Production Application Server.

  1. Full SP Farm Backup – It takes complete backup of the SharePoint Farm on which the SharePoint sites are hosted. The complete Farm backup includes backup of the farm configuration, Web Applications, IIS Configurations, Site Collections, Service Application databases, Content databases, and Configuration databases. This scheduled task calls the backup script to perform the backup and runs at 11:59 PM every Saturday (once in a week).
  2. RunDifferentialSPFarmBackup – It takes differential backup of the SharePoint Farm on which the SharePoint sites are hosted. It runs at 8:00 PM daily.
  3. HourlyContentDBBackup – It takes hourly backup of Content Database in order to ensure we have the latest Content database available in case of any disaster.

The Networker runs daily at 9:00 PM to copy these files over to the backup media tapes or devices.

The backups are run by powershell command tied to the Windows task scheduler.

Hope this simple strategy would help you in deciding your backup and Disaster recovery process in your enterprise.

Posted in SharePoint 2010 | Tagged: , | 1 Comment »

Install SharePoint 2010 Cumulative Updates

Posted by Amit Bhatia on February 5, 2013

This guide will explain the process to apply CU from Microsoft belonging to SharePoint 2010 Farm Servers. You need to patch the Farm servers which include “Software updates, update rollup, service pack, feature pack, critical update, security update, or hotfix”.

Refer to the below link for SharePoint Products latest available updates.

 For exact steps to install CU on SP 2010 refer to the document attached below.

SharePoint 2010 CU Steps <—- SharePoint 2010 CU Install steps document

I hope the above document and the steps mentioned in it would be of use to all the readers 🙂

Posted in Uncategorized | Tagged: , | Leave a Comment »

PSConfig fails System.InvalidOperationException, “Cannot start service SPAdminv4 on computer ‘.'” after CU install

Posted by Amit Bhatia on October 3, 2012

If you’ve experienced this error (System.InvalidOperationException, “Cannot start service SPAdminv4 on computer ‘.’) after installing SharePoint 2010 and failing consistently at the SharePoint 2010 Products Configuration Wizard, then this is likely to help:

(1) Browse to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN

(2) In this directory Create a file called “WSSADMIN.EXE.CONFIG”

(3) Populate it with the following:

<generatePublisherEvidence enabled=”false”/>

This disables checking for CAS publisher policy. MSDN article,

Posted in SharePoint 2010 CU | Tagged: , , | 7 Comments »

Searching For Value

"Helping You Master the Game of Investing"

Ideas with Conviction

The best thing about investing is the ease with which you can move your capital across different businesses, helping you capitalize on every opportunity..

CFA Institute Enterprising Investor

Practical analysis for investment professionals

Journeys of a Bumbling Trader

Learnings and Thoughts on Trading, Macroeconomics, Value Investing, Quantitative Finance, and Accounting

Flirting with Models

Research Library of Newfound Research

Alpha Ideas

Investment Blog for the Indian Markets

Fundoo Professor

Thoughts of a teacher & practitioner of value investing and behavioral economics