Unable to find manifest signing certificate in the certificate store

September 11, 2014 Leave a comment

Hi All,

Today after getting latest for my project from Team Foundation Server I was not able to build the solution as the mentioned above error was appearing. After doing some googling finally I found a link which resolved my problem. If this is the case with you then just remove the following from your .csproj file.

<PropertyGroup>

<ManifestCertificateThumbprint>…………</ManifestCertificateThumbprint>

</PropertyGroup>

<PropertyGroup>

<ManifestKeyFile>xxxxxxxx.pfx</ManifestKeyFile>

</PropertyGroup>

<PropertyGroup>

<GenerateManifests>true</GenerateManifests>

</PropertyGroup>

<PropertyGroup>

<SignManifests>false</SignManifests>

</PropertyGroup>

 

After doing so it resolved my issue J.

Reff: stackoverflow.

Regards.

 

SharePoint Central Administration Database in Suspect Mode!

Assalam o Alikum / Hi,

How do you feel when you need to open SharePoint Central Administration and ‘Connection Close’ message appears and SharePoint_AdminContent database halts in suspect mode? Yes I know how it feels! So to reduce the pain and get your smiles back I am writing this block. After googling so much, well 90% of the blog says to restore the database and bla bla but Developers are not used to take backups of the databases for their development environment.

Let’s cut the crap and jump to solution. Few SQL queries will fix this issue. Following are the details.

When I opened central admin it displayed Connection: close, then I checked my Database for SharePoint Central Administration which is SharePoint_AdminContent_eba61c34-8fb2-4c18-badd-d50aacfb05a7

So to fix the issue I searched on internet but most of them said to restore the database from its backup, which was not the case for me. One blog helped me a lot and I got the following queries from that. Moreover there are some steps involved as precautionary measures.

  1. Go to your MSSQL\Data files that reside under: C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA and copy your SharePoint_AdminContent_xxxx … ‘.mdf’ and ‘.ldf’ file on saperate location for backup
  2. You might need to stop the SQL Service to copy those files, remember to Start SQL service after copying those files.

  1. Open you SQL using SQL Server Management Studio and click -> New Query and it opens up your SQL Query editor, copy and paste the query below and change the highlighted to your database name:Use master
  2. Paste the following Queries and make sure changing Name of the SharePoint Admin content database as I have specified my database name highlighted in query.

 

–Verify whether Database has any issues

EXEC
sp_resetstatus
SharePoint_AdminContent_eba61c34-8fb2-4c18-badd-d50aacfb05a7.mdf

 

—Alter database and put it on Emergency Mode

ALTER
DATABASESharePoint_AdminContent_eba61c34-8fb2-4c18-badd-d50aacfb05a7SET
EMERGENCY

DBCC checkdb(‘SharePoint_AdminContent_eba61c34-8fb2-4c18-badd-d50aacfb05a7)

 

–Set the database in the Single User mode

ALTER
DATABASESharePoint_AdminContent_eba61c34-8fb2-4c18-badd-d50aacfb05a7SET
SINGLE_USER
WITH
ROLLBACK
IMMEDIATE

 

–Repair the database and allow data loss

DBCC CheckDB(‘SharePoint_AdminContent_eba61c34-8fb2-4c18-badd-d50aacfb05a7,REPAIR_ALLOW_DATA_LOSS)

 

–Set the database back to Multi-User mode

ALTER
DATABASESharePoint_AdminContent_eba61c34-8fb2-4c18-badd-d50aacfb05a7SET
MULTI_USER

 

–Ensure Database is reset

EXEC
sp_resetstatus
‘SharePoint_AdminContent_eba61c34-8fb2-4c18-badd-d50aacfb05a7

 


Execute all the commands in your SQL Query Editor, it will take some time depending upon the size of database.
Go back to your SQL Management Studio and you will see the (Suspect) mode issue against the Content/Config database is fixed and the database got fully repaired and restored.

To verify reopen your SharePoint Central Administration. This also applies if your Web Application database halts in (Suspect) state.

Facebook is Down !

Hi Guys,

For the first time i am seeing this ‘Sorry, something went wrong.’ from Facebook, this really is big news , now lets wait to see what was wrong with it and what the BUG was ‘if they reviled’ !

Lets hope it will be back soon !

Facebook down

 

…. 12:37 : Its up again🙂

Exporting Web / App parts (Content Editor, App, and Visual Web Part).

August 21, 2013 3 comments

I would not be wrong if i call web part as vital part of SharePoint. Today we will be discussing to export and use the exported web parts in Visual Studio.

  • Web part.
  • Content Editor Web part.
  • App 2013 (List view web part).

So let’s get started, but before doing things we need to make sure following this are also properly settled.

  • Export Mode from ‘Edit Web part’ Options should have ‘Export all Data’. Through this we will be able to export the web part and that will be exported as .dwp  or .wp
  • If not set before then set ‘Export all data’ and apply/ok.

Web Part:

  • Select Edit Page option then select Edit Web part from the web part zone on which your required web part is placed.
  • Select ‘Export’ Option.
  • On selecting ‘Export’, dialogue to save the web part will open, save it to you required destination.


  • Open that file with Note Pad or Note Pad ++.
  • On opening you would have the following

    <webParts>

    <webPart xmlns=”http://schemas.microsoft.com/WebPart/v3″&gt;

    <metaData>

    <type name=”xxxxxxxxxxxxxxxxxxxxxxx, xxxxxxxxxxxxx, Version=1.0.0.0, Culture=neutral, PublicKeyToken=xxxxxxxxxxxxx” />

    <importErrorMessage>Cannot import this Web Part.</importErrorMessage>

    </metaData>

    <data>

    <properties>

    <property name=”numberOfItemsToDisplay” type=”int”>10</property>

    <property name=”ExportMode” type=”exportmode”>All</property>

    <property name=”HelpUrl” type=”string” />

    <property name=”Hidden” type=”bool”>False</property>

    <property name=”Description” type=”string”>My Visual Web Part</property>

    <property name=”CatalogIconImageUrl” type=”string” />

    <property name=”Title” type=”string”>Custom Webpart</property>

    <property name=”AllowHide” type=”bool”>True</property>

    <property name=”AllowMinimize” type=”bool”>True</property>

    <property name=”AllowZoneChange” type=”bool”>True</property>

    <property name=”TitleUrl” type=”string” />

    <property name=”ChromeType” type=”chrometype”>None</property>

    <property name=”AllowConnect” type=”bool”>True</property>

    <property name=”Width” type=”unit” />

    <property name=”Height” type=”unit” />

    <property name=”HelpMode” type=”helpmode”>Navigate</property>

    <property name=”AllowEdit” type=”bool”>True</property>

    <property name=”TitleIconImageUrl” type=”string” />

    <property name=”Direction” type=”direction”>NotSet</property>

    <property name=”SharePointWebURL” type=”string” null=”true” />

    <property name=”AllowClose” type=”bool”>True</property>

    <property name=”ChromeState” type=”chromestate”>Normal</property>

    </properties>

    </data>

    </webPart>

    </webParts>

  • Copy all from <webParts> … </webParts>, in nutshell copy all.
  • That is your required xml which is to be added in Visual studio under web part zone in

    <AllUsersWebPart
    WebPartZoneID=xc…
    WebPartOrder=1>

    <![CDATA[

    ‘Your Copied XML’
    ]]>

    </AllUsersWebPart>

    Content Editor:

Exporting web part is same for all, there are some tweaks to do in Content Editor Web part’s exported XML. So let’s jump to it. Content Editor Web part’s exported xml would look like the following

<?xml version=”1.0″ encoding=”utf-8″?>

<WebPart xmlns:xsd=”http://www.w3.org/2001/XMLSchema&#8221; xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance&#8221; xmlns=”http://schemas.microsoft.com/WebPart/v2″&gt;

<Title>Content Editor</Title>

<FrameType>None</FrameType>

<Description>Allows authors to enter rich text content.</Description>

<IsIncluded>true</IsIncluded>

<ZoneID>x917ee352abe847918eefcb35fd02bf0f</ZoneID>

<PartOrder>0</PartOrder>

<FrameState>Normal</FrameState>

<Height />

<Width />

<AllowRemove>true</AllowRemove>

<AllowZoneChange>true</AllowZoneChange>

<AllowMinimize>true</AllowMinimize>

<AllowConnect>true</AllowConnect>

<AllowEdit>true</AllowEdit>

<AllowHide>true</AllowHide>

<IsVisible>true</IsVisible>

<DetailLink />

<HelpLink />

<HelpMode>Modeless</HelpMode>

<Dir>Default</Dir>

<PartImageSmall />

<MissingAssembly>Cannot import this Web Part.</MissingAssembly>

<PartImageLarge>/_layouts/15/images/mscontl.gif</PartImageLarge>

<IsIncludedFilter />

<Assembly>Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c</Assembly>

<TypeName>Microsoft.SharePoint.WebPartPages.ContentEditorWebPart</TypeName>

<ContentLink xmlns=”http://schemas.microsoft.com/WebPart/v2/ContentEditor&#8221; />


<Content xmlns=”http://schemas.microsoft.com/WebPart/v2/ContentEditor”&gt;<![CDATA[<div class=”block”>

<h3>Related Pages</h3>

<div class=”rlinks”>

<ul>

<li>

<a href=”/Pages/ABC.aspx”> ABC</a></li>

</ul>

</div>

</div>

<div class=”block”>

<h3>By Telephone </h3>

<div class=”rlinks”>

<ul>

<li>Tel : +92 336 335 334 6</li>

<li>Fax : +92 336 335 334 6</li>

</ul>

</div>

</div>

<div class=”block”>

<h3>

<a href=”#”>By Email </a></h3>

<div class=”rlinks”>

<ul>

<li>

<a href=”#”> ABC @ ABC.com</a></li>

</ul>

</div>

</div> ]]></Content>

<PartStorage xmlns=”http://schemas.microsoft.com/WebPart/v2/ContentEditor&#8221; />

</WebPart>

  • Everything added in content editor would come under <Content> tag.
  • You will notice there is already <![CDATA[ tag into it, Change this Tad to <Value> and its closing ]]> to </Value> too.
  • Moreover Copy all the text between <![CDATA[ and its closing ]]> highlighted.
  • Content editor web part needs encoded HTML so we need to encode it. This can be encoded from HTML Encode.
  • Paste all the encoded HTML between <Value> encoded HTML </Value>.
  • The final exported web part XML should look like

     

    <? xml version=”1.0″ encoding=”utf-8″?>

    <WebPart xmlns:xsd=”http://www.w3.org/2001/XMLSchema&#8221; xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance&#8221; xmlns=”http://schemas.microsoft.com/WebPart/v2″&gt;

    <Title>Content Editor</Title>

    <FrameType>None</FrameType>

    <Description>Allows authors to enter rich text content.</Description>

    <IsIncluded>true</IsIncluded>

    <ZoneID>x917ee352abe847918eefcb35fd02bf0f</ZoneID>

    <PartOrder>0</PartOrder>

    <FrameState>Normal</FrameState>

    <Height />

    <Width />

    <AllowRemove>true</AllowRemove>

    <AllowZoneChange>true</AllowZoneChange>

    <AllowMinimize>true</AllowMinimize>

    <AllowConnect>true</AllowConnect>

    <AllowEdit>true</AllowEdit>

    <AllowHide>true</AllowHide>

    <IsVisible>true</IsVisible>

    <DetailLink />

    <HelpLink />

    <HelpMode>Modeless</HelpMode>

    <Dir>Default</Dir>

    <PartImageSmall />

    <MissingAssembly>Cannot import this Web Part.</MissingAssembly>

    <PartImageLarge>/_layouts/15/images/mscontl.gif</PartImageLarge>

    <IsIncludedFilter />

    <Assembly>Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c</Assembly>

    <TypeName>Microsoft.SharePoint.WebPartPages.ContentEditorWebPart</TypeName>

    <ContentLink xmlns=”http://schemas.microsoft.com/WebPart/v2/ContentEditor&#8221; />


    <Content xmlns=”http://schemas.microsoft.com/WebPart/v2/ContentEditor”&gt;<Value>&lt;div class=&quot;block&quot;&gt;

    &lt;h3&gt;Related Pages&lt;/h3&gt;

    &lt;div class=&quot;rlinks&quot;&gt;

    &lt;ul&gt;

    &lt;li&gt;

    &lt;a href=&quot;/Pages/ABC.aspx&quot;&gt; ABC&lt;/a&gt;&lt;/li&gt;

    &lt;/ul&gt;

    &lt;/div&gt;

    &lt;/div&gt;

    &lt;div class=&quot;block&quot;&gt;

    &lt;h3&gt;By Telephone &lt;/h3&gt;

    &lt;div class=&quot;rlinks&quot;&gt;

    &lt;ul&gt;

    &lt;li&gt;Tel : +92 336 335 334 6&lt;/li&gt;

    &lt;li&gt;Fax : +92 336 335 334 6&lt;/li&gt;

    &lt;/ul&gt;

    &lt;/div&gt;

    &lt;/div&gt;

    &lt;div class=&quot;block&quot;&gt;

    &lt;h3&gt;

    &lt;a href=&quot;#&quot;&gt;By Email &lt;/a&gt;&lt;/h3&gt;

    &lt;div class=&quot;rlinks&quot;&gt;

    &lt;ul&gt;

    &lt;li&gt;

    &lt;a href=&quot;#&quot;&gt; ABC @ ABC.com&lt;/a&gt;&lt;/li&gt;

    &lt;/ul&gt;

    &lt;/div&gt;

    &lt;/div&gt;

    </Value></Content>

    <PartStorage xmlns=”http://schemas.microsoft.com/WebPart/v2/ContentEditor&#8221; />

    </WebPart>

  • Paste the tweaked web part XML

    <AllUsersWebPart
    WebPartZoneID=xc…
    WebPartOrder=1>

    <![CDATA[

    ‘Your tweaked XML’
    ]]>

    </AllUsersWebPart>

     

App / List View:    

In SharePoint 2013 you won’t find List view web part, as lists are given a new name and that is App. So how to add an app part and how to export it.

  • For that we will be using SharePoint
    Designer as there is no option to export App
    J.
  • Open SharePoint designer.
  • Navigate to your site on which you need to add a web part, moreover site should have that list too for which we are going to export the web part.
  • App an aspx page in that site from SharePoint designer.
  • Edit that added page in advance mode.
  • Add web part zone as shown below


 

  • Then into added web part zone.
    • Select Data View from the ribbon and select your list , Mine is LegalDocuments


 

  • After List been added to you zone. Click Web part from ribbon on top of the page and select ‘To File’.


  • You will be prompted to save the web part at your desired location and name.
  • Save it and open the saved file with Note Pad or Note Pad ++.
  • It will look like the following

    <?xml version=”1.0″ encoding=”utf-8″ ?>

    <webParts>

        <webPart xmlns=”http://schemas.microsoft.com/WebPart/v3″&gt;

            <metaData>

                <type name=”Microsoft.SharePoint.WebPartPages.XsltListViewWebPart, Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” />

                <importErrorMessage>Cannot import this Web Part.</importErrorMessage>

            </metaData>

            <data>

                <properties>

                    …

                    <property name=”ListName” type=”string”>LegalDocuments<property>

                    <property name=”ListDisplayName” type=”string” null=”true” />

                    <property name=”AllowZoneChange” type=”bool”>True</property>

                    <property name=”ChromeState” type=”chromestate”>Normal</property>

                    <property name=”DisableSaveAsNewViewButton” type=”bool”>False</property>

                    <property name=”ViewFlag” type=”string” />

                    <property name=”DataSourceID” type=”string” />

                    <property name=”ExportMode”

                    <property name=”Title” type=”string” />

                    <property name=”PageType” type=”Microsoft.SharePoint.PAGETYPE, Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c”>PAGE_NORMALVIEW</property>

                    <property name=”DataSourcesString” type=”string” />

                    <property name=”AllowClose” type=”bool”>True</property>

                    <property name=”InplaceSearchEnabled” type=”bool”>True</property>

                    <property name=”WebId” type=”System.Guid, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″>b369b8ef-fb3b-4a8e-ba1e-ae04fd57441c</property>

                    <property name=”Height” type=”string” />

                    <property name=”GhostedXslLink” type=”string”>main.xsl</property>

                    <property name=”DisableViewSelectorMenu” type=”bool”>False</property>

                    <property name=”DisplayName” type=”string”>LegalDocuments</property>

                    <property name=”IsClientRender” type=”bool”>False</property>

                    <property name=”XmlDefinition” type=”string”>

        &lt;View Name=”{807234E4-D763-435E-A84A-A5E20727A5FA}” MobileView=”TRUE” Type=”HTML” DisplayName=”All Documents” Url=”/LegalDocuments/Forms/AllItems.aspx” Level=”1″ BaseViewID=”1″ ContentTypeID=”0x” ImageUrl=”/_layouts/15/images/dlicon.png?rev=23″&gt;

            &lt;Query/&gt;

            &lt;ViewFields&gt;

                &lt;FieldRef Name=”DocIcon”/&gt;

                &lt;FieldRef Name=”LinkFilename”/&gt;

                &lt;FieldRef Name=”Modified”/&gt;

                &lt;FieldRef Name=”Editor”/&gt;

                &lt;FieldRef Name=”_ModerationStatus”/&gt;

            &lt;/ViewFields&gt;

            &lt;RowLimit Paged=”TRUE”&gt;30&lt;/RowLimit&gt;

            &lt;JSLink&gt;clienttemplates.js&lt;/JSLink&gt;

            &lt;XslLink Default=”TRUE”&gt;main.xsl&lt;/XslLink&gt;

            &lt;Toolbar Type=”Standard”/&gt;

        &lt;/View&gt;

    </property>…

        &lt;ParameterBinding Name=”NoAnnouncements” Location=”Resource(wss,noXinviewofY_LIST)” /&gt;

        &lt;ParameterBinding Name=”NoAnnouncementsHowTo” Location=”Resource(core,noXinviewofY_DEFAULT)” /&gt;

        &lt;ParameterBinding Name=”AddNewAnnouncement” Location=”Resource(wss,addnewitem)” /&gt;

        &lt;ParameterBinding Name=”MoreAnnouncements” Location=”Resource(wss,moreItemsParen)” /&gt;

    </property>

                    <property name=”DataSourceMode” type=”Microsoft.SharePoint.WebControls.SPDataSourceMode, Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c”>List</property>

                    <property name=”AutoRefreshInterval” type=”int”>60</property>

                    <property name=”AsyncRefresh” type=”bool”>False</property>

                    <property name=”HelpUrl” type=”string” />

                    <property name=”MissingAssembly” type=”string”>Cannot import this Web Part.</property>

                    <property name=”XslLink” type=”string” null=”true” />

                    <property name=”SelectParameters” type=”string” />

                </properties>

            </data>

        </webPart>

    </webParts>

  • Important things to tweak in App / List view are highlighted.
  • Make sure List name is proper.
  • Make sure URL of view is proper.
  • Final thing to do is , This will be added under <View ….</View>
    instead of <AllUsersWebPart … so delete AllUsersWebPart

    Tag and place View tag.

     

    <View
    List=LegalDocuments
    BaseViewID=1
    WebPartZoneID=xb…………
    WebPartOrder=1 >

    <![CDATA[

    ‘Copy Tweaked XML here’
    ]]>

    </View>

    Happy CodingJ.


 

Easiest way to create SharePoint List Definition

April 11, 2013 6 comments

Playing with SharePoint is always a bit of time consuming but worthy a lot J . Today we will learn the quickest way to create SharePoint list definition.

STEP 1:

  • Open SharePoint UI.
  • Create SharePoint List.
  • Name it.

STEP 2:

  • Create some columns using UI of SharePoint list.
  • Country and City columns are created and can be seen while adding an item in List created from UI.
  • Country is of type Single line of Text, whereas City is of Choice field with some choices in it.

STEP 3:

  • Go to List settings and Save this list as Template.

  • Give it a proper name, in my case, it’s been named as ‘DemoList’.
  • It will be saved in Template Gallery of Site Collection, Navigate to it.
  • Click on it and it will ask to download, save it on the desktop or any location from which you can access it easily.

STEP 4:

  • Access that saved .stp file as it will be saved with extention .stp , in my case it’s DemoList.stp
  • Rename it’s .stp to .cab
  • Extract it and open its manifest.xml in Visual Studio.
  • Press ctrl+f and find ‘UserLists’, under that node you will see <List
    Name … </List>

  • This is the actual SCMEA for the list which is to be used for creating list definition, copy it in notepad and close the manifest.xml

STEP 5:

  • Create New Project of SharePoint 2010 from here we will be using VS2010 and doing some tweaks in the SCHEMA.

  • Select Deploy as Farm Solution

  • Then Add ‘New Item’ and Select List Definition, Moreover name is properly, in my case I named it DemoList.

  • Provide the name of List Definition, I named it SPDemoListDefinition.
  • Select the type of List definition, Remember we created Custom List from UI and we are going to use its SCHEMA so select Custom List and press ‘Finish’

  • If Add a list Instance is clicked then an Instance from the List Definition will be created after the solution is being deployed.

Now you would have ‘SPDemoList’ List definition added in your solution.

Note: – We will be mainly updating the SCHEMA of ‘SPDemoList’.

  • Open Schema.xml and paste the Schema which as extracted earlier and pasted in notepad to Schema.xml of SPDemoList schema.xml


There are many things which are to be modified now, so don’t panic and focus on the modifications.

  • List
    Name={C560CF03-D855-4FD7-89E1-CBE3370ED0F8} : Change it to proper name of list
    which
    exists in Element.xml i.e SPDemoList
  • FeatureId={00BFEA71-DE22-43B2-A848-C05709900100} : Change it to the featureId into which list definition is being wrapped. Rename the feature properly as

    It will be shown in web features and on its activation List Definition will be created. You need to rename its title

Renamed:

  • Url=Lists/DemoList : Change the Url attribute to the proper name of list , We named it SPDemoList to it will be Url=Lists/SPDemoList
  • Find the “Views” section and add WebPartZoneID=”Main”, SetupPath=”pages\viewpage.aspx” attributes to the each View. Change Url attribute to Url=”AllItems.aspx”.
    • <View Name=”{352071D0-7C1E-4AD6-8875-8A11125CCBCF}” BaseViewID=”1″ WebPartZoneID=”Main” SetupPath=”pages\viewpage.aspx” Url=”AllItems.aspx” …>
  • Find the “<Forms>” section and replace three inner “Form” tags with the following.
    • <Form
      Type=DisplayForm
      Url=DisplayForm.aspx
      SetupPath=pages\form.aspx
      WebPartZoneID=Main/>
    • <Form
      Type=EditForm
      Url=EditForm.aspx
      SetupPath=pages\form.aspx
      WebPartZoneID=Main/>
    • <Form
      Type=NewForm
      Url=NewForm.aspx
      SetupPath=pages\form.aspx
      WebPartZoneID=Main/>

Now build and deploy the solution.

  • Create SharePoint List from SPDemoListDefinition and you would have all the fields available in that list which were in the list created with UI. Moreover fields from schema can be added too.
  • Make sure the Feature is active.

  • Now go to Lists à Create and create list from SPDemoListDefiniton

  • Here we Go J

Hope this will help you.

Exception while creating Web Application : Failed to call GetTypes on assembly Microsoft.Office.InfoPath.Server

March 11, 2013 2 comments

I have SharePoint Server 2010 and Office 2013 Installed on my machine , I installed office after SharePoint Server 2010 installation but after Installation of Office 2013, Creation of web application in SharePoint Server 2010 starts throwing exception : Provisioning of the web application ‘Web app – Port’  has encountered the following error: Microsoft.SharePoint.Upgrade.SPUpgradeException: Failed to call GetTypes on assembly Microsoft.Office.InfoPath.Server, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c. Could not load file or assembly ‘Microsoft.Office.InfoPath, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c’ or one of its dependencies. The system cannot find the file specified.

After some searching on Internet ‘Googling’  , i got the solution , The solution to the problem is to Downgrade ‘Info Path’ or to remove Info Path. Perhaps this is not the desired way to come up with some proper solution but lets hope Microsoft will come up with appropriate fix to this.

I uninstalled Info Path and it worked for me. Now SharePoint 2010 is working as expected.

SharePoint 2010 and SQL Server 2012, Error occurred while creating Content Databases : Could not find stored procedure ‘sp_dboption’.

February 15, 2013 1 comment

I was deploying SharePoint 2010 with SQL 2012 on Windows Server 2012 and got error while create Content Databases during Configuration Wizard.

An exception of type System.Data.SqlClient.SqlException was thrown.  Additional exception information: Could not find stored procedure ‘sp_dboption’.
System.Data.SqlClient.SqlException: Could not find stored procedure ‘sp_dboption’.

Just relax and take a chill pill as i got a solution to it and now SharePoint is running like a charm.

Solution : Install Service Pack 1 of SharePoint Server 2010 before running SharePoint configuration wizard🙂 .

Follow

Get every new post delivered to your Inbox.