Skip to main content

Posts

Showing posts from 2015

Share Point 2013 is really slow in Production Farm after some times

We had a problem in the Share Point farm and It came really slow suddenly. It's just 44KB and it took around 13s to load. So when dinging the problem it has took quite a time to figure out App Fabric Caching Service is not running which is related to Distributed Cache Service . When i run the service server performance was make to normal.

Reporting server web part not working in SharePoint 2013

These was situation in my server farm , reporting server web part is not worked. Literally I can add the reporting server web part to the server but when I give the report path report is showing but when I click Apply Button nothing is showing in the page. While playing with the web part I found that If I unchecked the Asynchronous Rendering report will be loaded in the web part.  But after that none of operations are working (as an example , Expand , Apply new filter) because we disabled the Ajax request from the web part. By digging through found that we have put “SPWebpartManager” tag in the header section in the master page which actually should be in the body; when the time of custom master page creation. < WebPartPages:SPWebPartManager runat ="Server" /> We could have found this one more easily if we change the master page to default. Lesson Learnt If some web parts are miss behave , change the Master Page to the default and check whet

Request failed. The method "GetItems" of the type "List" with id is blocked by the administrator on the server. SharePoint 2013

I have encountered this issue with my SharePoint 2013 server farm. Code was working fine with the development machine but once it deployed to Share Point 2013 production environment; found this error on Chrome console. function somefunc() { listItems = '' ; var context = SP.ClientContext.get_current(); var web = context.get_web(); var currentList = web.get_lists().getById(_spPageContextInfo.pageListId); var query = new SP.CamlQuery(); listItems = currentList.getItems(); context.load(listItems); context.executeQueryAsync(onQuerySucceeded, onQueryFailed); } Message was straight forward so I thought it is a permission issue. When I logged using my credentials It was fine and worked but when I logged out and view as a Anonymous user it didn’t work. Then I tried to give permission to EveryOne to  the list , web even for the site collection and it didn’t work either. then I found out it’s a property in web applicat

Microsoft.SharePoint.ApplicationRuntime.SafeControlsList.GetSafeControlsListFromPath

  I had this error appearing in event viewer when I tried to run a tool which is doing updates on SharePoint pages. But this was working very fine in my Dev environment and it is not working on my SharePoint production servers. Surprised isn’t It … I tried to figure out the error nothing was successful. But ones I tried to run the same tool of web front end servers it worked . My server farm contains 2 application servers and 2 web front end servers. And I figured it out this error is not appearing and working fine in WFEs not App servers.

SharePoint 2013 List Operations in REST– Retrieve List Fields Basics

How to make a REST call in SharePoint App and SharePoint Provider Hosted App – Part 1 SharePoint 2013 List Operations in REST– Retrieve List  Fields Basics – Part 2 You can use the function specified in the first post to call the REST URLs. You can use the appropriate function depending on the App type you are developing. Get selected fields in SharePoint List using SELECT REST operation. Getting single value fields /* List Name : listname Columns: Title => Text , ID => Number */   var url = "/_api/web/lists/getbytitle('listname')/items?$select=Title,ID" ;   function s(data){   // get the data and convert to JSON Objects var d = JSON.parse(data.body).d.results[0]; alert(d.ID); alert(d.Title); }   function f(data){ alert(data); }   getREST(url,s,f); Getting Single value Lookup fields /* List Name : listname Columns: ID => Number , CountryLookup => List LooukUp */   var url = "/_api/web/lists/getbytitle(

[Microsoft][ODBC Driver 11 for SQL Server]Named Pipes Provider: Could not open a connection to SQL Server [53].

SQLState = 08001, NativeError = 53 Error = [Microsoft][ODBC Driver 11 for SQL Server]Named Pipes Provider: Could not open a connection to SQL Server [53]. SQLState = 08001, NativeError = 53 Error = [Microsoft][ODBC Driver 11 for SQL Server]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. SQLState = S1T00, NativeError = 0 Error = [Microsoft][ODBC Driver 11 for SQL Server]Login timeout expired This is a error i have got when my program is trying to connect to a SQL Server 2012 using named pipe. I did a little google and found below article and followed it very carefully and still i got the error. https://www.mssqltips.com/sqlservertip/2340/resolving-could-not-open-a-connection-to-sql-server-errors/ Futhur digging my syl server is in different act

REST operations in SharePoint 2013

REST operations are essential in any SharePoint development. This series explain available REST endpoints in SharePoint 2013. First article shows how we can made a REST call in both SharePoint Hosted and Provider Hosted app. How to make a REST call in SharePoint App and SharePoint Provider Hosted App – Part One SharePoint 2013 List Operations in REST– Retrieve List  Fields Basics – Part 2 Executing a REST GET call from SharePoint Provider Hosted App First you need to refer related JavaScript related. <script src= "http://ajax.googleapis.com/ajax/libs/jquery/1.11.2/jquery.min.js" ></script> <script type= "text/javascript" src= "#SPWeb/_layouts/15/MicrosoftAjax.js" ></script> <script type= "text/javascript" src= "#SPWeb/_layouts/1033/init.js" ></script> <script type= "text/javascript" src= "#SPWeb/_layouts/15/sp.core.js" ></script> <script type= "text/j

Melick’s Guide To

Configure outgoing e-mail settings SharePoint 2013 and Office365 Configure Outgoing e-mail settings in SharePoint 2013 Central Administration - part 1 Configure Outgoing e-mail settings with existing email sever in SharePoint Server 2013 - part 2 Configure Outgoing e-mail settings with Gmail/Google SMTP server with SharePoint Server 2013 - part 3 Configure Outgoing e-mail settings with Office 365  SMTP server with SharePoint Server 2013 - part 4

Configure outgoing e-mail settings with Office 365 SMTP server in SharePoint Server 2013 – Part 4

Configure Outgoing e-mail settings in SharePoint 2013 Central Administration - part 1 Configure Outgoing e-mail settings with existing email sever in SharePoint Server 2013 - part 2 Configure Outgoing e-mail settings with Gmail/Google SMTP server with SharePoint Server 2013 - part 3 Configure Outgoing e-mail settings with Office 365  SMTP server with SharePoint Server 2013 - part 4 First check the SMTP server is installed in the server. You can check that on Server Manger and Features section. If it is not installed first you need to install the SMTP in the server. SMTP server needs port 25 opens in the firewall in default. After setting up the SMTP server you need to open the IIS Manger. before stating the SMTP Virtual server need to configure some properties. Right click the SMTP virtual Server and click on the Access Tab . Click on Relay.. button on the Relay restrictions . This section specified which server can use the SMTP for mail relay. So either you need to sel

Configure outgoing e-mail settings with Gmail/Google SMTP server in SharePoint Server 2013 – Part 3

Configure Outgoing e-mail settings in SharePoint 2013 Central Administration - part 1 Configure Outgoing e-mail settings with existing email sever in SharePoint Server 2013 - part 2 Configure Outgoing e-mail settings with Gmail/Google SMTP server with SharePoint Server 2013 - part 3 Configure Outgoing e-mail settings with Office 365  SMTP server with SharePoint Server 2013 - part 4 First check the SMTP server is installed in the server. You can check that on Server Manger and Features section. If it is not installed first you need to install the SMTP in the server. SMTP server needs port 25 opens in the firewall in default. After setting up the SMTP server you need to open the IIS Manger. before stating the SMTP Virtual server need to configure some properties. Right click the SMTP virtual Server and click on the Access Tab . Click on Relay.. button on the Relay restrictions . This section specified which server can use the SMTP for mail relay. So either you need to sel