SharePoint For Developers

One of our project(SharePoint) requirements, we need to use the certificate to encrypt and decrypt the data by using the public and private key. So the code implemented on the DEV working fine, but issue comes when code deployed on the other servers. The error was “ Keyset does not exist ”. The base exception class of this error is “ CryptographicException ”. CryptographicException : Keyset does not exist 0(issue fixed) RSACryptoServiceProvider rsaEncryptor = ( RSACryptoServiceProvider )certificate.PrivateKey; This exception comes when the application pool account doesn’t have access to read the certificate private key. For this we would required to give the full access to the particular certificate. Followings are the required steps to fixing this issue. Solution Application Pool account doesn’t having an permission to access the private key value Steps 1.   Login to server Press Ctrl+R type to   MMC. 2.   File -> Add or remov...

I was working with showModalDialog function and everything working fine, the issue came with the code when I deployed the code on other servers(IT, UAT...). The URL was causing an issue and because of this I was getting "Page not found" message when function "showModeldailog" was called from the JS file. The location of the Page (Inside the layout folder). The Problem: We have a different-2 sever and each server has its own site collection with diff URL and Dev System In my development server I had created the URL without manage path.(http:severname/_layouts/15/testProj/MyPage.aspx) and it is working fine in my Development server. Other Servers Other servers like (IT, UAT & PROD) the URL was causing an issue.The URL : '/_layouts/15/testProj/MyPage.aspx'. I used  below for URL creation. (" Page Not Found " issue cause on these servers) URL creation method on Dev System function ShowModelDialog(listid, itemid) {     var fullUrl...

I am getting this error while build the SharePoint WSP in released mode. (debug wsp working fine). In this project, I was using the WEB service in to get the information form the userprofile web service. This web service reference is causing an issue.   To fix this issue I did the following step to fix it. Create the separate Class Project in Visual Studio, and take the user profiler web service in this separate project. Take the ref. of this dll in my existing WSP and rebuild the Solution in released mode. Problem Solved.

Following are the steps. Step 1. Open the Visual Studio Step 2. Open the ribbon feature that causing the problem. Step 3. Go the feature manager window by double click the feature. Step 4. Press F4, It will opens the property window. Step 5. You will see the Version property empty. Step 6. Give the Feature Version number and save the feature. Step 7. Deploy the WSP.

Open the visual Studio and navigate to the feature XML file and add the bellow attribute. AlwaysForceInstall = " TRUE " The <FeatureName>.Template.Xml output would be some think link this. <? xml version = " 1.0 " encoding = " utf-8 " ?> < Feature xmlns = " http://schemas.microsoft.com/sharepoint/ " AlwaysForceInstall = " TRUE " > </ Feature > After doing the above step the problem solved.

This issue comes when we are deploying WSP solution to our SharePoint Farm. When we activated the solution timer job created with future time. We waited for the timer job to complete but nothing happen still showing deploying. In our farm we have 4 WFE servers we have check many blogs related to this type of issue like mentioned below. http://social.technet.microsoft.com/Forums/office/en-US/93f4cac5-2a9f-4715-8505-62f20f203846/wsp-deployment-status-shows-deployingscheduled-at-date-time-but-even-though-its-already-deployed We check the all WFE servers and found the most of the servers following two services was stopped.  SharePoint Timer  service SharePoint Administration   So I stated both two services in all my WFE servers and the problem solved.

Problem: I am deploying the layout pages using the module. Inside the zones I am adding the default web parts. The problem is one of my content editor web part contains the CSS and HTML tags. When I am deploying it the web part comes properly but html not rendered properly.   I have tried the following method to solve the problem. 1.        I have placed the html in the web part then export the content editor web part and place inside the Element.xml file. The problem is still there content not rendered property.   (Not Worked) 2.        Place the html content inside the <![CDATA[]]. I am getting the red swing line. It shows that the xml not well formatted.   Please see the bellow image.   (Not Worked)   3.        Encode the Html then placed it inside the content. Now the html rendered inside the content editor web part. I used the Html Encode tool an...

Common mistakes Both SharePoint Site and SSO Site NOT running on the same application pool. Application pool identity user doesn’t have permission to access the certification.  Solution to this problem Set the same identity pool to  : 2. Be sure to grant rights to the certificate for the App Pool running the web service Start -> Run -> MMC File -> Add/Remove Snapin Add the Certificates Snap In Select Computer Account, then hit next Select Local Computer (the default), then click Finish On the left panel from Console Root, navigate to Certificates (Local Computer) -> Personal -> Certificates You're certificate will most likely be here. Right click on your certificate -> All Tasks -> Manage Private Keys Set you're private key settings here. Add app pool account Reset iis

Problem : The root of the certificate chain is not a trusted root authority. Event Log Error An operation failed because the following certificate has validation errors:\n\nSubject Name: CN=<Certificate URL>, OU=Domain Control Validated, O=<Certificate URL>\nIssuer Name: SERIALNUMBER=07969287, CN=Go Daddy Secure Certification Authority, OU=http://certificates.godaddy.com/repository, O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona, C=US\nThumbprint: xxxxxxxxxxxxxxxxxxxxxx\n\nErrors:\n\n The root of the certificate chain is not a trusted root authority. Main problem is your SSO Application unable to make a trust with SharePoint 2010 Site. Common mistake: Most of developer while implementing the SSL on SharePoint Site they only include the main Certificate to SharePoint Security "Manage Trust"  i.e. (<Site URL> ). SharePoint Site unable to make the trust between the SSO Site. Solution : You need to first see the hierarchy of the certificate. ...