Skip to main content

Navision 2013 Sharepoint Client Installation & Configuration Errors

Hi all,

While installing Sharepoint 2010 For Running Microsoft Dynamics 2013 Sharepoint client. During installation  Microsoft Sharepoint 2012 we get many errors.

I will be keep this post updated will all those errors and resolution for those errors. Currently i got below listed error so for now below is the error and resolution.



Error - Failed to Create Configuration Database



Cause of error -
The reason for the error is because our system don't have Windows Identity Foundation which is required for Sharepoint 2010.

Resolution-
Download and install Windows Identity Foundation from
http://www.microsoft.com/en-us/download/details.aspx?id=17331#filelist

After installtion Run the configuration wizard again.

Regards,
Saurav Dhyani
http://saurav-nav.blogspot.in/


Comments

Popular posts from this blog

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.