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.

clip_image001[6]

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

clip_image001[8]

clip_image002

clip_image003

2. 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
  2.  
  3. clip_image001[10]clip_image002[6]
  4. 4. Restarted and recycled Security Token Service Application/pool for all WFEs – no luck
  5. image
  6. 5. Restarted Servers – no luck

Two last steps were able to shed some lights !

6. 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)

clip_image001[4]

  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 !

Sorry Something Went Wrong: SharePoint 2016 Farm Configuration Wizard Failed with timeout during services provisioning

clip_image001

The Error says it all, SharePoint could not provision the farm configurations within the given timeframe and it pops up the timeout. End result is, no services or applications provisioned. Below is a result from the very first application server was trying to provision my SP2016 farm on production.

clip_image002

You may have successfully installed prerequisites and product but this error could occur during your next step which is product configuration and service app (farm configuration) provisioning if you have a weak bandwidth for inter server communication. No matter how robust your servers are, the network could screw it all with a low bandwidth.

Try to ping across the servers and ensure you have a steady line from WFE to Intranet and Database Servers. Below sample is from one of my deployment which was failed with above error due to lack of bandwidth from APP server to Database just because the customer was having legacy network equipment and cabling (It was lower than 50 mbps given for SharePoint VLAN).

clip_image003

clip_image004

This is also can affect during Product configuration. That means the connection between your Database server to Application Server is worst, not only for SharePoint but anything rely on network connectivity will surely not perform well.

clip_image005

Or even hangs on 3rd stage unusually (normally this stage takes 10 min max, at my case it was more than 30 which is hilariously abnormal)

clip_image006

Its mandatory to have a good (at least 1gbps, 10gbps is ideal) network connectivity across all SharePoint, OWA and Workflow Manager Servers.

Hardware requirements for SharePoint 2016 – https://technet.microsoft.com/en-us/library/cc262485(v=office.16).aspx

SharePoint 2016 Product Configuration Wizard Error: Configuration Failed with Unauthorized Access Exception

If you are going to deploy SharePoint 2016, this is a common error that encountered.

clip_image001[4]

The error pretty much pointing to a Access permission which you might doubtlessly think its database permission but no it’s not !

clip_image002[4]

If you expand the event log, It will have 100, 104 errors logged due to this.

clip_image003[4]

Resolution is to permit setup account to access Tasks folder (C:\Windows\Task). This is a critical folder which needs to be able to access by the setup account during the Product Configuration.

To take the ownership of this folder, log in to relevant SharePoint server using a local admin account and right click on the Tasks folder.

clip_image004[4]

Under Security tab, go to Advance

clip_image005[4]

Change the Owner from SYSTEM to your Setup account (the account will be used to run Product Config Wizard)

clip_image006[4]

Once changed, the new owner can be seen as showed below.

Error-SPSetup

Repeat the same for all SharePoint Servers in your farm if you planned to have multiple. Now run the Product Configuration Wizard again and you will notice its smoothly passing to task 5. within few minutes, the Wizard will be successfully complete.

clip_image008[4]

And here comes the winning moment !

image

If you are still accounting with any additional errors in the Wizard, these points are some basic ones to verify.

Ensure:

  1. 1. Antivirus Disabled for all SharePoint and Database Servers (If any)
  2. 2. Firewall
  3. 3. Named Pipes in SQL Services enabled (Sometimes this isn’t enabled by default)

And then:

  1. 1. Disable UAC (Never Notify)
  2. 2. Restart Server
  3. 3. Run the Product Config Wizard again as Administrator

Enjoy the all new SharePoint !

Configuring Calendar Overlay to Display Different Color for each Category in SharePoint Online-Make the SharePoint Calendar More Delightful and Useful

Calendar being one of the most significant feature in SharePoint. Most of the time to use it in a meaningful way, you need a little bit of customization. This article describes the way of customizing the color code of Calendar items based on a specific category.

Scenario: I need my calendar to show different colors for each category such as Meeting, Business, etc.…Once we complete all the steps, you will see a calendar like this which has different color for each category. The filtering option can be used to either default “Category” Field or you may create your own column with multiple choices as you need.

I have used SharePoint Online In this Scenario but it will be the same for On-Premise SharePoint as well.

clip_image001

So let’s get in to the scene. First to create Views on the Existing Calendar. Office 365 SharePoint will already have Calendar by default even for newly created sites.

Go ahead and Create a New View by Clicking on “Create View

clip_image002

To Select the Calendar View, Click on it

clip_image003

Give it a name and drag to bottom of the page. In this case its “Meeting” so I will see this name when I’m configuring the Overlay at next levels.

clip_image004

Choose the Filtering Option as you need it to be. In this case I will use the Category Filed to Color up the events so each Category will have a different color. First lets create a View for the Meeting category. Once selected the field and given the Value which you want to filter, hit “ok” to save.

clip_image005

Now to configure the Calendar Overlay. Simply Click on “Calendar Overlay” Icon on the Ribbon

clip_image006

It will bring you up to this page. Hit on new Calendar here (Not to be confused. This doesn’t mean you need to have multiple calendars here. It simply means you can have multiple calendars as well. also you can have multiple views in a single Calendar too) so in this scenario, we will have multiple views in a single calendar in order to define different colors for each category.

clip_image007

Let’s create the first Overlay for the Meeting Category first. URL will be automatically inserted. If your calendar on the root site, simply click Resolve to retrieve the List and View otherwise define the path for your calendar.

This is where you define the View you created earlier. From now on, All items created under Meeting Category will be shown in Purple Color.

clip_image008

If you have many categories, repeat the same process for other category items as well (e.g.- Birthday, Business). When you complete everything, the final Calendar will look like this.

clip_image009

Control/Hide SharePoint Top Ribbon to an Specific Audience

Mostly in SharePoint Public Sites Scenarios, You will look for a solution where to hide the Admin Ribbon of the SharePoint Site. Basically the site itself should not have the Admin panel shown to anonymous users accessing from outside which can be only shown up on the level of permissions of the user logged in to the Site (Mostly Internal Domain Users)

clip_image001

If you have developed you own Masterpage, this has to be done there.

To do this, Simply open the Site using SharePoint Designer. Locate your Master Page (which has been set as the Default) Find below two Controls in MasterPage.

Dont forget to Keep a Copy of the Master page before you start editing.

Master

Then Edit the PermissionString from its defined value (ManageWeb) to the new value based on your permission requirements. In this sceanrio it defined to “AddListItems” Value which is the new permission Level. from now on, the Ribbon will be only Visible for thoese who has AddListItems permision Level. To any other level it will be hidden.

In Below sceanrio, Anonymous User wont be able to see the Ribbon as it defined to hide for everyone does not have “AddListItems” Permission level. However you have to carefully look at the list of permission levels supported in “SecurityTrimControl” which has been listed below.

———————————————— Grey Bar (Ribbon Row)

clip_image003

<SharePoint:SPSecurityTrimmedControl ID=”HideRibbonRow” runat=”server” PermissionsString=”ManageWeb”>

document.getElementById(“s4-ribbonrow”).style.display = “block”;

</SharePoint:SPSecurityTrimmedControl>

clip_image004

———————————————— Blue Bar (Suit bar)

clip_image005

<SharePoint:SPSecurityTrimmedControl ID=”HideSuiteBar” runat=”server” PermissionsString=”ManageWeb”>

document.getElementById(“suiteBar”).style.display = “block”;

clip_image006

Once edited the Permission, simply save and Publish the MasterPage and test it out. if you have defined permission peroperly to your users, it will work perfectly.

Below are the full list of permission levels suported by the “SecurityTrimControl”

EmptyMask – Has no permissions on the Web site. Not available through the user interface.

ViewListItems – View items in lists, documents in document libraries, and view Web discussion comments.

AddListItems – Add items to lists, add documents to document libraries, and add Web discussion comments.

EditListItems – Edit items in lists, edit documents in document libraries, edit Web discussion comments in documents, and customize Web Part Pages in document libraries.

DeleteListItems – Delete items from a list, documents from a document library, and Web discussion comments in documents.

ApproveItems – Approve a minor version of a list item or document.

OpenItems – View the source of documents with server-side file handlers.
ViewVersions – View past versions of a list item or document.
DeleteVersions – Delete past versions of a list item or document.
CancelCheckout – Discard or check in a document which is checked out to another user.
ManagePersonalViews – Create, change, and delete personal views of lists.
ManageLists – Create and delete lists, add or remove columns in a list, and add or remove public views of a list.

ViewFormPages – View forms, views, and application pages, and enumerate lists.
Open – Allow users to open a Web site, list, or folder to access items inside that container.
ViewPages – View pages in a Web site.

AddAndCustomizePages – Add, change, or delete HTML pages or Web Part Pages, and edit the Web site using a SharePoint Foundation compatible editor.

ApplyThemeAndBorder – Apply a theme or borders to the entire Web site.
ApplyStyleSheets – Apply a style sheet (.css file) to the Web site.
ViewUsageData – View reports on Web site usage.
CreateSSCSite – Create a Web site using Self-Service Site Creation.
ManageSubwebs – Create subsites such as team sites, Meeting Workspace sites, and Document Workspace sites.

CreateGroups – Create a group of users that can be used anywhere within the site collection.

ManagePermissions – Create and change permission levels on the Web site and assign permissions to users and groups.

BrowseDirectories – Enumerate files and folders in a Web site using Microsoft Office SharePoint Designer 2007 and WebDAV interfaces.

BrowseUserInfo – View information about users of the Web site.
AddDelPrivateWebParts – Add or remove personal Web Parts on a Web Part Page.
UpdatePersonalWebParts – Update Web Parts to display personalized information.
ManageWeb – Grant the ability to perform all administration tasks for the Web site as well as manage content. Activate, deactivate, or edit properties of Web site scoped Features through the object model or through the user interface (UI). When granted on the root Web site of a site collection, activate, deactivate, or edit properties of site collection scoped Features through the object model. To browse to the Site Collection Features page and activate or deactivate site collection scoped Features through the UI, you must be a site collection administrator.

UseClientIntegration – Use features that launch client applications; otherwise, users must work on documents locally and upload changes.

UseRemoteAPIs – Use SOAP, WebDAV, or Microsoft Office SharePoint Designer 2007 interfaces to access the Web site.

ManageAlerts – Manage alerts for all users of the Web site.
CreateAlerts – Create e-mail alerts.
EditMyUserInfo – Allows a user to change his or her user information, such as adding a picture.
EnumeratePermissions – Enumerate permissions on the Web site, list, folder, document, or list item.

<

p align=”justify”>FullMask – Has all permissions on the Web site. Not available through the user interface.

Sorry Something went wrong, An Unexpected Error Occurred After Migrating SharePoint 2010 Site to 2013

The error itself describes nothing related as it is a common error. there will be scenarios where the SharePoint farms that you are planning to migrate having bunch of custmizations and third-party integrations. this is one example i’ve been facing recently.

The Site was migrated using DB attached method and whatever the Custom Solutions were sitting on the source farm wrere migrated to destination (2013) Farm too. there were many Web applications and many of them worked perfectly but not this one.

Prompts “Sorry Something went wrong, An Unexpected Error Occurred” when accessing the destination site URL.

clip_image001

ULS Log is the god at this point.

Searching ULS through this correlation ID won’t give you the exact point here. Instead search through URL. At this point the error was occurred due to the Nintex Workflow Solution which is a third party WSP deployed and not configured. Retracting the two WSPs related to Nintex from this particular web Application resolved the error.

Nintex

This is the ultimate reason behind this error. This Home page has been using a Task list associated to a third-Party Solution. Web Part remains fulty unless the connection and licensing configured properly.

clip_image003

Wrap-up: Any Cutom Solution used (only the ones used within your target Web application) in the Source Farm has to be deployed to the Destination farm. not only deployed and enabled but conigured for Connections and Licensing. in above scenario, the third-party solution was not licensed and neither configured as required which cuased the error in destination.

Anonymous Users getting authentication prompt for SharePoint List and Library access

Public facing sites hosted in SharePoint commonly needs anonymous access and that’s been there for quite long now.

Generic configurations are done from Central Administration and Site Permission Level but these steps will not allow anonymous users to have read access to all the content unless you specify.

  • Enable anonymous access in “Authentication Providers” (Central Administration –> Application Management –> Select the target Web Application) – All Scenarios
  • Grant rights to anonymous users in “Site permissions” -All Scenarios
  • Grant rights to specific library (in some scenarios)

but you will get authentication prompted when anonymously accessing lists, libraries or items stored in.

To have read access to all lists and libraries across the site, you also need to Disable the “Limited-access user permission lockdown mode” Site Collection Features. Deactivating this feature will grant anonymous users to access all resources across the site (which are granted for anonymous access)

anonymous-lockdown