Search This Blog

Friday, August 22, 2014

Difference between ODBC and OLE DB data sources

In this post I want to explain the difference between ODBC and OLE DB.This is what I found based on my reading on the web and my understanding.

1) ODBC provides access only to relational databases

2) OLE DB provides the following features:
a) Access to data regardless of its format or location
b) Full access to ODBC data sources and ODBC drivers

In simple words, ODBC is used only for SQL based data sources whereas OLE DB is used for both SQL and non SQL data sources.I have put in a diagram also below. That might explain it better.


Connection strings for Analysis Services (SSAS) or OLAP

When you work with SharePoint and you want to establish connection with Analysis Services (SSAS) or Cubes you would need to generate connection strings to connect to the Data Source. Some sample connection strings are below: 

Standard

Data Source=myServerAddress;Catalog=myDataBase;

Encrypted Connection
This one authenticates the user and encrypts the communication. This is the highest level of security.

Data Source=myServerAddress;Catalog=myDataBase;ProtectionLevel=PktPrivacy;

Signed Connection
This one authenticates the user and prevents the content in the communication to be modified.

Data Source=myServerAddress;Catalog=myDataBase;ProtectionLevel=PktIntegrity;

Authenticated Connection
This one authenticates the user but does not secure the communication.

Data Source=myServerAddress;Catalog=myDataBase;ProtectionLevel=Connect;




Tuesday, August 5, 2014

Hiding SharePoint Search Center Title and Description

1. Browse to the Page -> Edit Page -> Add Web Part -> Media and Content -> Content Editor -> Click here to add content-> On the ribbon -> HTML -> Edit HTML Source

2. Paste the below code :

<style>
.s4-mini-header {
            VISIBILITY: hidden
}</style><style>
.s4-mini-titlesep {
            VISIBILITY: hidden
}</style>


3. Content Editor Web Part ->Edit Web Part properties -> Appearance -> Chrome Type -> None


4. Page -> Publish 

Downloading/Extracting WSP (Solution) from SharePoint

Background
Last week I was working on a SharePoint project where I had to get all the wsp�s deployed in the farm and I was not able to find few .wsp files anywhere in the Central Administration server. In the Central Administration Solution Properties screen, there is an option to Retract the solution but no option to Download the solution

Solution
I am not sure if there is a way to do this using stsadm. But definitely we can do this using SharePoint PowerShell.To run this command, you need to be a member of the Farm Administrators group and have permission to the configuration database

$farm = Get-SPFarm
$file = $farm.Solutions.Item("deployedsolutionname.wsp").SolutionFile
$file.SaveAs("c:\temp\deployedsolutionname.wsp")

Hiding Title Column in a SharePoint list

1. Navigate to the SharePoint list page that contains the Title data you want to hide.

2. Go to the Settings menu at the top of the page and select List Settings.

3. Click on the link labeled Advanced Settings.

4. Select the Yes radio button next to Allow the Management of Content Types. Then click OK.



5. Click on Item from the Content Types section of the page.



6. Click on the item labeled Title.



7. Scroll down to the Column Settings section and choose the Hidden radio button.



8. Click OK to save the settings.

Wednesday, July 16, 2014

SharePoint Compatibility with Internet Explorer

SharePoint 2010 and IE

Browser
Supported
Supported with limitations
Not supported
Internet Explorer 1132-bit64-bit
Internet Explorer 10 32-bit64-bit
Internet Explorer 9 32-bit64-bit
Internet Explorer 8 32-bit64-bit

SharePoint 2013 and IE

Browser
Supported
Not supported
Internet Explorer 11X
Internet Explorer 10X
Internet Explorer 9 X
Internet Explorer 8 X

Tuesday, March 4, 2014

Retrieving the COM class factory for component with CLSID {BDEADEE2-C265-11D0-BCED-00A0C90AB50F} failed due to the following error: 800703fa.

Issue Description

I was getting the above error while browsing to Central Administration




Server Error in �/� Application.
Retrieving the COM class factory for component with CLSID (BDEADEE2- C265- .11 DO- SCED- OOAOC9OAB5OFJ failed due to the following error: 800703 fa.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where �t originated in the code.
Exception Details: System.Runtime.lnteropservices.COMException: Retrieving the COM class factory for component wh CLSID (ODEADEE2-C265-1 I DO-BCED-OOAOC9OAOSOF)failed due to the following error: 800703fa.
Source Error:
An unhandled exception was generated during the execution of the current web request. Inforniation regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[COMException (0x800703fa): Retrieving the C0M class factory for component with CLSID {BDEADEE2-C265-llDO-BCED-OOAOC9OABSOF} failed due to the following error: 800703f a.]
Microsoft.SharePoint.Library.SPRequest. .ctorO tiO4
Microsoft.SharePoint.SPGlobal.CreatesPRequestAndSetldentity(Boolean bNotGlobalAdminCode, String strUrl , Sedean bNotAddToContext, Byte[] UserToken, String userName, Soolean blgnoreTokenTimeout, Soolean bAsAnonyntus) �238
Microsoft.SharePoint.SPWeb.InitializeSPRequest() .455
Microsoft. SharePoi nt. SPWeb. EnsureSPRequestQ �75
Microsoft. SharePoi nt. SPWeb. get_Request() �74
Microsoft.SharePoint.WebControls.SPControl .SPwebEnsureSPControl(HttpContext context) +613
Microsoft.Sharepoint.WebControls.SPControl .c5etContextweb(HttpContext context) .41
Microsoft.SharePoint.ApplicationRuntime.SPRequestModule.PostResolveRequestCacheHandler(Object osender, EventArgs ea) �595
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +80
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) �171
Version Informdtion: Microsoft NET Framework Version:2.O.50727.4234; ASP.NET Yersion:2.U.5U727.4223

Resolution

Perform an IISRESET on all the web servers in the farm.
Propellerads