Download your free copy of “Installing and Configuring SharePoint Server 2019” Guide (Based on Public Preview)

Microsoft recently released the public preview of SharePoint Server 2019. SharePoint has become crucial in corporate environments, especially after the release of the latest cutting-edge functionalities in the SharePoint online. I have composed a book to cover the installation and configuration of SharePoint 2019 and it is freely available in TechNet gallery for you to download. 

Using this simple and easy to follow guidance, you will be able to get SharePoint 2019 server installed and configured in a physical or virtual environment. I have used Microsoft Azure VMs for my farm in this setup as it’s easy to provision and scale out. Azure is the most flexible way for dev/test environments and even for production for those who can’t invest massively on hardware. 

Click here to download your copy or go here – https://gallery.technet.microsoft.com/Installing-and-Configuring-bc8a1314?redir=0

Advertisement

InfoPath Error in SharePoint 2016: There has been an error while processing the form

Warning There has been an error while processing the form. click OK to resume filling out the form. You may want to check your form data for errors.

Let me guess, you have gone through all possible verifications on data sources and form fields and everything pretty well developed and verified ? same goes for me. one of my colleague was developing a form and she came up with this error on SharePoint 2016 recently.

She was using GetUserProfileByName SOAP Web Service to fetch current user’s group in to a field, and that’s where this error prompts. that was verified by removing the particular connection and rules filling up data.

After verifying form fields, Data connections and other basics, I decided to inspect the infrastructure step by step. SharePoint logs and Event Log did not had any relevant entry. Finally in the lonely boat, I took following steps one after one to sail towards an island.

1. Enabled all InfoPath services from CA (General Application Settings) – Everything is already set

1. Registered the HTMLCHKR – no luck

regsvr32 “C:\Program Files\Common Files\Microsoft Shared\OFFICE14\htmlchkr.dll”

1. 3. Added the target site to InfoPath application’s trusted Locations – no luck
3. 
5. 4. Restarted and recycled Security Token Service Application/pool for all WFEs – no luck
6. 
7. 5. Restarted Servers – no luck

Two last steps were able to shed some lights !

1. Disabled loopback check

What is Loopback check?. If you have been prompted continuously for credentials in a SharePoint server when you try to access your site within that server, that’s obviously because of loopback.

Microsoft: Windows Server 2003 SP1 introduced a loopback security check. This feature is obviously also present in Windows Server 2008/12. The feature prevents access to a web application using a fully qualified domain name (FQDN) if an attempt to access it takes place from a machine that hosts that application. The end result is a 401.1 Access Denied from the web server and a logon failure in the event log.
Unfortunately 401.1 is not really helpful as this error code means there is a problem with the user credentials. Of course, the HTTP spec doesn’t know about security features in a vendor’s implementation so there can’t be a HTTP error code for such a feature. This can lead to much banging of the head on the desk. It’s one of numerous causes of the 401.1 which are nothing to do with invalid credentials (e.g. attempting to use Kernel Mode Authentication with domain account in IIS7).

Option1 : Logged in to target SharePoint Server/s and launch PowerShell as administrator, then ran – New-ItemProperty HKLM:\System\CurrentControlSet\Control\Lsa -Name “DisableLoopbackCheck” -value “1” -PropertyType dword)

You don’t need to add it if its exists (means loopback is already disabled)

1. Option 2: You can also Add this registry entry manually
2. Click Start, click Run, type regedit, and then click OK
3. In Registry Editor, locate the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
4. Right-click Lsa, point to New, and then click DWORD Value. (In Win 2008, its DWORD 32bit)

Type DisableLoopbackCheck, and then press ENTER.

Right-click DisableLoopbackCheck, and then click Modify.

In the Value data box, type 1 and then click OK.

Quit Registry Editor.

1. Then I ran SharePoint Product Configuration wizard on SharePoint Server just to give it a refreshment.

After restarting Servers, added the form connection and rules back and InfoPath form loaded perfectly normally !

Sign in as Different User is gone in SP 2013

 

An another significant feature dropped in SharePoint 2013. Sign in as different user no more available by default. this is one of the most frequently used feature in early SharePoint versions for Demonstration and testing purposes. as per Experts around “It has been removed from OOTB feature based on security considerations, specially on production environments“

however still it’s as simple as editing and adding few lines on Welcome page. here I’m stepping you to get it back but I would say it shouldn’t be done in PROD environments as Microsoft has dropped it reasonably.

1. Direct to – C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\TEMPLATE\CONTROLTEMPLATES\

2. Keep Welcome.ascx file originally copied somewhere and edit the original one through notepad and save it.

3. Add the following element before the existing element with the id of “ID_RequestAccess”:

<SharePoint:MenuItemTemplate runat="server" ID="ID_LoginAsDifferentUser"

Text="<%$Resources:wss,personalactions_loginasdifferentuser%>"

Description="<%$Resources:wss,personalactions_loginasdifferentuserdescription%>"

MenuGroupId="100" Sequence="100"

UseShortId="true"

/>

so it’ll look like this once you edited

go open up your sites and see. yeah it’s back in there.. Enjoy !

Latest Cumulative Update February 2013 has been Released for SharePoint 2010

So it’s another update to consider about to have on your SP farm. As per my knowledge, this is the 20th CU release for SharePoint 2010. Massive number of releases isn’t it !

Download the package here – http://support.microsoft.com/kb/2767793

To install this hotfix, you must have SharePoint Server 2010 Service Pack 1 or SharePoint Foundation 2010 Service Pack 1 installed.

Note: Do not apply directly in to production without testing on Staging.

This Update Fixes Below Issues

• When you remove a hyperlink from a Hyperlink with formatting constraints for publishing column in SharePoint Server 2010, new hyperlinks cannot be added to the column.
• Assume that you have a document library named “Transfer” that has been recently accessed in SharePoint Server 2010. You run the Merge-SPLogFile cmdlet to return Unified Logging Service (ULS) log entries by using a correlation ID filter. In this situation, the cmdlet returns no results and you receive the following error message:
  WARNING: Cmdlet did not return any records in the log file. Check your time range or filters.

This cumulative update package also fixes the issues that are described in the following Microsoft Knowledge Base (KB) articles:

• 2760774
  Description of the SharePoint Foundation 2010 hotfix package (Wss-x-none.msp): February 12, 2013
• 2767795
  Description of the SharePoint Server 2010 hotfix package (Coreserver-x-none.msp): February 12, 2013
• 2589344
  Description of the PerformancePoint Services for SharePoint Server 2010 hotfix package (Ppsmawfe-x-none.msp): February 12, 2013