Monday, August 22, 2016


Error: Invalid or unsupported credentials. Please contact your administrator or Credentials was not found for the current user within the target application. Please set the credentials for the current user


If you face this error on deploying external content types in SharePoint or if you faced one of below error on creating external lists.
Invalid or unsupported credentials. Please contact your administrator
Credentials was not found for the current user within the target application. Please set the credentials for the current user

Resolution 1 

            At first you have to double check that you set credentials for secured store target application, go to central administration -> application management -> manage service applications -> select your target secure store application, in my case it is SAMAIntranetSSApp.


Figure 1
      Enter database user and password, and credentials manager in case of individual application type.


Figure 2

Resolution 2

This error may be caused from application type, individual type for secure store application works in standalone environment (One server), and if you are working with farms that consists of apps and front-end servers then you have to consider creating secure store application with Group type.
In below figure, the application will be created with “Group” application type instead of Individual to resolve the problem, once you selected group as application type then none will be selected as target application page URL.




Figure 3

You can set hints for type of username and password that should be entered and click Next,





Figure 5
Check your target secure store application and click on set



Figure 6

Enter credentials required to access external data source.


Figure 7

Database Connector has throttled the response. The response from database contains more than '2000' rows. The maximum number of rows that can be read through Database Connector


Resolution 1

You can set filter parameters to your external content type as below figure.

Figure 8

Resolution 2

By default 2,000 with a maximum of 1,000,000 items if using Visual Studio so you can change the default values using the commands below. In this example we have increase the default limit to 20,000 items and maximum
 $bcs = Get-SPServiceApplicationProxy | where{$_.GetType().FullName -eq (‘Microsoft.SharePoint.BusinessData.SharedService.’ + ‘BdcServiceApplicationProxy’)}
$BCSThrottle = Get-SPBusinessDataCatalogThrottleConfig -Scope database -ThrottleType items -ServiceApplicationProxy $bcs
Set-SPBusinessDataCatalogThrottleConfig -Identity $BCSThrottle -Maximum 1000000 -Default 20000


Wednesday, July 27, 2016

Customize Display, Add and Edit Forms for SharePoint Custom Lists Errors

Column “Publishing Page Layout” does not exist, it may have been deleted by another user.


For developers who are working on custom solution on top of SharePoint server, this error that you may face if you wanted to customize display, edit and new forms for custom content types in SharePoint, in my scenario I created a publishing page and I am adding custom webparts to this page by using page module.

At first when you create custom content types that will be bound to list, and these content types have default edit, display and new forms then you have to create an event receiver to update the forms as below sample code.


Then when you create a new task, you will be redirected to the custom form page url, and the below error will be thrown.
System.ArgumentException: Column 'PublishingPageLayout' does not exist. It may have been deleted by another user


To fix this error, you need to add custom document properties to the aspx page html as below,
<html xmlns:mso="urn:schemas-microsoft-com:office:office" xmlns:msdt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882"><head> 
<!–[if gte mso 9]><SharePoint:CTFieldRefs runat=server Prefix="mso:" FieldList="FileLeafRef,Comments,PublishingStartDate,PublishingExpirationDate,PublishingContactEmail, 
PublishingContactName,PublishingContactPicture,PublishingPageLayout,PublishingVariationGroupID, 
PublishingVariationRelationshipLinkFieldID, 
PublishingRollupImage,Audience,PublishingIsFurlPage,SeoBrowserTitle,SeoMetaDescription, 
SeoKeywords,RobotsNoIndex,eRebEntity"><xml> 
<mso:CustomDocumentProperties> 
<mso:PublishingContact msdt:dt="string">1073741823</mso:PublishingContact> 
<mso:PublishingIsFurlPage msdt:dt="string">0</mso:PublishingIsFurlPage> 
<mso:display_urn_x003a_schemas-microsoft-com_x003a_office_x003a_office_x0023_PublishingContact msdt:dt="string">System Account</mso:display_urn_x003a_schemas-microsoft-com_x003a_office_x003a_office_x0023_PublishingContact> 
<mso:PublishingContactPicture msdt:dt="string"></mso:PublishingContactPicture> 
<mso:RobotsNoIndex msdt:dt="string">0</mso:RobotsNoIndex> 
<mso:PublishingContactName msdt:dt="string"></mso:PublishingContactName> 
<mso:ContentTypeId msdt:dt="string"> 
0x010100C568DB52D9D0A14D9B2FDCC96666E9F2007948130EC3DB064584E219954237AF3900 
B3313EDD2C4B4EAC9D8A2EA8C0F6CF1D00BE9190263CAA2946A1A8D14D4C5EBD43</mso:ContentTypeId> 
<mso:PublishingPageLayoutName msdt:dt="string">eREBStudyPage.aspx</mso:PublishingPageLayoutName> 
<mso:Comments msdt:dt="string"></mso:Comments> 
<mso:PublishingContactEmail msdt:dt="string"></mso:PublishingContactEmail> 
<mso:PublishingPageLayout msdt:dt="string"> 
http://dev.erebportal.com/_catalogs/masterpage/eREBStudyPage.aspx, /_catalogs/masterpage/eREBStudyPage.aspx 
</mso:PublishingPageLayout> 
<mso:RequiresRouting msdt:dt="string">False</mso:RequiresRouting> 
</mso:CustomDocumentProperties> 
</xml></SharePoint:CTFieldRefs><![endif]–> 
<title>Access Denied</title></head>

Saturday, May 7, 2016

K2 Blackpearl 4.6.10 Installation and Configuration with SharePoint 2013



1 Installation of K2

K2 Blackpearl Installation


-          Run K2 package Installer.
K2 Installation

Make sure MSMQ Feature from Server Features and Roles are installed as below.

-          Run K2 Blackpearl Setup Manager from the Path K2 Installation Package 4.6.10 -> k2 Blackpearl 4.6.10 (4.0…..) -> installation.
K2 blackpearl Setup Manager




-          Next -> Custom Installation





-          Please make sure that all are checked expect visual studio features
Check features

-          Set dB creator permission for the service account
-          Set administrator permission for the service account in SQL server configuration wizard and for the folder too.







-          Change smpt server settings.




          Now the configuration wizard will be running


g





-          Create new web application and a root site collection to activate k2 features on
                      -      Go to Central administration -> Apps -> manager app catalog -> create new app catalog site



Smart Forms Installation

Go to K2 Installation package 4.6.10 -> K2 SmartForms 4.6.10 -> Intallation -> setup.exe





-          Next -> next -> next -> finish
-          The configuration wizard will be running automatically



Control Pack Installation



-          Complete the same steps of configuration wizard as in SmartForms installation

K2 for SharePoint Installation

-          Go to K2 Installation Package 4.6.10 -> k2 for SharePoint 4.6.10 -> installation.
Start the Subscription Settings in Central Administration
To begin, open the SharePoint 2013 Central Administration page and click on System Settings.
On the System Settings page, in the Servers section, click on Manage services on server
Go to the Services on Server page.  Make sure that the status of Microsoft SharePoint Foundation Subscription Settings Service is listed as Started.
Configure the Subscription Settings service application by using Windows PowerShell
Before you begin, make sure that the user running the Windows PowerShell cmdlets has the following memberships on all databases that you will be using:
  • db_securityadmin
  • db_owner


Next, go to Start > All Programs.  Expand the folder MS SharePoint 2013 Products to reveal the SharePoint 2013 Management Shell program. 
Select SharePoint 2013 Management Shell with the Run as administrator option.



Run the following commands:
  • Get and set the name of the managed account in the SharePoint farm to the $account for later use.
$account = Get-SPManagedAccount "<AccountName>"
Please note that "<AccountName>" is the name of the managed account in the SharePoint farm.
For example: $account = Get-SPManagedAccount domain\spFarmAccount

  • Create an application pool for the Subscription Settings service application:
$appPoolSubSvc = New-SPServiceApplicationPool -Name SettingsServiceAppPool -Account $account

  • Create the Subscription Settings service application:
$appSubSvc = New-SPSubscriptionSettingsServiceApplication -ApplicationPool $appPoolSubSvc -Name SettingsServiceApp -DatabaseName <SettingsServiceDB>
Please note that <SettingsServiceDB> should be the name of the Subscription Settings service database.
For example: $appSubSvc = New-SPSubscriptionSettingsServiceApplication -ApplicationPool $appPoolSubSvc -Name SettingsServiceApp -DatabaseName SettingsServiceChauTeamDB
  • Create a proxy for the Subscription Settings service application:
$proxySubSvc = New-SPSubscriptionSettingsServiceApplicationProxy -ServiceApplication $appSubSvc
Next, after running the command lines above, you will need to verify that the Subscription Settings Service was successfully created on the server.
To do this, go to the SharePoint 2013 Central Administration page and click Application Management.
On the Application Management page, select the Manage service applications hyperlink.

On the Manage service applications page, make sure that the status of SettingsServiceApp is listed as Started
Next, you will need to go to the MS SQL Server to verify that, after running the command lines above, the database name was successfully created.
Finally, set permission from K2 WORKSPACE