SHAREPOINT 2013 NEWSFEEDS NOT WORKING – Microsoft.Office.Server.Microfeed.MicrofeedException. Internal error code: 55.

Problem Statement

 MySites newsfeeds don’t work and SharePoint returned the following error: The operation failed because the server could not access the distributed cache. Internal type name: Microsoft.Office.Server.Microfeed.MicrofeedException. Internal error code: 55. Contact your system administrator for help in resolving this problem.

Solution

Find the account for the Feed Cache service that the application pool was running on.   Add this account to the User Profile service application and provide full control and that fixed the issue. 

SHAREPOINT 2013 HTTP/1.1 200 OK SERVER: MICROSOFT-IIS/8.0 CONNECTION: CLOSE ERROR

Problem Statement:

Open a site collection then I got error as

HTTP/1.1 200 OK

Server: Microsoft-IIS/7.5

Connection: close

Proposed Solutions

At first it appears to be a fairly minor error. So I performed an IISRESET to try and see if a restart of the web services would fix the problem. Unfortunately this did not fix the issue.

I did notice however that site collections within the Web Application were working fine for example if I went to http://sharepoint/sites/aka the site was functioning correctly and all the information was there. So what ever had happened had just affected the main site.

After a lot of researching about the error across the internet I found a large number of possible fixes including

• Creating a new site collection would fix the issue.
• Checking that the workstation service was running?!?
• Changing the authentication type.
• Removing and re-attaching the content database.
• If any managed path location which is modified

NINTEX FORM - CUSTOMIZE THE FORM FIELDS USING CSS/JS

Users can either use the default css provided by Nintex or create their own custom CSS add them at the end of "Custom CSS" section of "Form Settings" or create a .css file, add it to site assets and refer in "Advanced --> Custom CSS includes" section of "Form Settings".

In each forms control under the controls settings, click on Formatting section and there user can apply the CSS class

NOTE: No support for custom CSS and JS support to responsive forms, it is only available in classic forms

Reference

https://help.nintex.com/en-us/nintex2016/current/sp2016/Forms/Designer/FormLayoutSettings.htm

https://community.nintex.com/thread/18559-how-do-i-customized-the-form-fields-using-css

https://www.habaneroconsulting.com/stories/insights/2013/branding-nintex-forms

https://nintex.uservoice.com/forums/218293-4-nintex-forms-for-office-365/suggestions/31367023-add-

custom-css-and-js-support-to-responsive-forms

NINTEX FORMS - USING THE LOOKUP FUNCTION

      Nintex Forms offers many great features for designing and customizing your SharePoint forms. There are times when you need to pull in data to your forms from other sources, including other SharePoint lists.  One way to accomplish this is to use the Lookup function, which allows you to retrieve data from a column within a SharePoint list and display that data on a form or use it in a formula. The Lookup function can be utilized within a Calculated Value control, Form Variable, or Rule.

      Here’s the syntax for configuring the Lookup function:

lookup(List Title, Column to filter on, Value to filter on, Output column)

1.      List Title – The title of the list that contains the data you are retrieving.  The list can be in the current site or another site.  To configure with a list on another site, start by prepending the List Title with the server relative URL path of the site and then delimit the list title with a pipe (|) symbol.  For example, “/sites/siteCollection/siteName|ListTitle”.

2.      Column to filter on – The name of the column in the list that you want to filter on.  This column is used to filter which list items are returned as matches occur against the third parameter.

3.      Value to filter on – The specified value that is compared against each item in the list.  Be sure to use a Named Control instead of an item in the Item Properties tab for this value.

4.      Output column – The column name in the list from which the data is retrieved.

      References

      

      https://help.nintex.com/en-us/nintex2016/current/sp2016/Forms/Designer/LookupFunction.htm 

      

      https://help.nintex.com/en-US/nintex2013/help/#Forms/RootCategory/Designer/Nintex.Forms.LookupFunction.htm%3FTocPath%3DForms%7CUsing%2520the%2520Form%2520Designer%7C_____21

ADD MICROSOFT.SHAREPOINT.POWERSHELL SNAP-IN TO ALL POWERSHELL WINDOWS

Problem Statement:

 Whenever I wrote Sharepoint reIated powershell script I had to constantly add the line Add-PSSnapin 

"Microsoft.SharePoint.PowerShell" at the top of every script I wrote, and I wanted it to just already be there like it is when I run the SharePoint Management Shell. 

Solution:

Add the snap-in code to the PowerShell profile.

Open up PowerShell ISE and run the following to create a profile script if one doesn’t exist and edit it in the ISE:

if (!(test-path $profile.AllUsersAllHosts)) {new-item -type file -path $profile.AllUsersAllHosts –force} powershell_ise $profile.AllUsersAllHosts

That will open a new tab in PowerShell ISE allowing you to edit profile.ps1.  If you simply execute $profile.AllUsersAllHosts, you will see the path where this file is stored (be default it is C:\Windows\System32\WindowsPowerShell\v1.0).

In PowerShell ISE, you will now have a new tab where you can edit this file.  In that new tab, add the following code and then save the file.

$ver = $host | select version if ($ver.Version.Major -gt 1) {$host.Runspace.ThreadOptions = "ReuseThread"} if ((Get-PSSnapin "Microsoft.SharePoint.PowerShell" -ErrorAction SilentlyContinue) -eq $null) {     Add-PSSnapin "Microsoft.SharePoint.PowerShell" }

Now, close PowerShell ISE and then open it again.  It will take a little longer than usual to open the window because it is executing the code from Profile.ps1 and adding the Microsoft.SharePoint.PowerShell snap-in.  To test it, run a command such as Get-SPFarm.

NINTEX ERROR "AN OBJECT OF THE TYPE MICROSOFT.SHAREPOINT.ADMINISTRATION.SPWEBCONFIGJOBDEFINITION...ALREADY EXISTS"

ISSUE

When performing Nintex Web Application Activation in Nintex Workflow or Activating the Web Application Feature In Nintex Forms the following error occurs:

Object of the type Microsoft.SharePoint.Administration.SPWebConfigJobDefinition named "job-webconfig-modification" already exists under parent Microsoft.Sharepoint.Administration.SPWebService named "".  Rename your object or delete the existing object.



RESOLUTION

Option 1
Restart the SharePoint timer service on all Web and App servers.
Find the job-webconfig-modification timer job running in Central Admin and cancel it.

Option 2
Use the PowerShell scripts below to find and delete the job(s).
SHAREPOINT 2010, SHAREPOINT 2013
DO NOT RUN THE FOLLOWING SCRIPT IN SHAREPOINT2016 FARMS.

Get-SPTimerJob -Identity "job-webconfig-modification" | Format-Table -Property DisplayName, Id, LastRunTime
$job = Get-SPTimerJob -identity "GUID" -WebApplication webApplicationName
$job.Delete()

Reference :

https://support.nintex.com/SharePoint/Forms/Error_%22An_object_of_the_type_Microsoft.SharePoint.Administration.SPWebConfigJobDefinition...already_exists%22

NINTEX FORM ERROR: "THE EXPRESSION PREFIX 'NFRESOURCES' WAS NOT RECOGNIZED."

Problem Statement

The following error appears when loading up Nintex Forms Designer and is logged in ULS logs:

The Expression prefix 'NFResources' was not recognized. Please correct the prefix or register the prefix in the <expressionBuilders> section of configuration.

Cause

The issue occurs when the Web Application Feature for Nintex Forms needs to be activated.

Resolution

Use the following procedure to resolve this issue.

1. On the Central Administration Home page, click Application Management.

2. In the Web Applications section, click Manage web applications.

3. In the Name column, select the web application on which you want to activate Nintex Forms. For example, select SharePoint -80.

4. In the Web Applications ribbon, click Manage Features. The Manage Web Application Features dialog box appears.

5. In the Nintex Forms section, click Activate. After a short delay, the dialog box refreshes and the status is "Active."

6. Click OK

Please do check, If you have the correct entries in application Web Config file.

SAFE CONTROL ENTRIES

<SafeControl Assembly="Nintex.Forms.SharePoint, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c52d764dcf7ec883" Namespace="Nintex.Forms.SharePoint.WebControls" TypeName="*" Safe="True" SafeAgainstScript="False" />

<SafeControl Assembly="Nintex.Forms.SharePoint, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c52d764dcf7ec883" Namespace="Nintex.Forms.SharePoint.WebParts.InitiateWorkflow" TypeName="*" Safe="True" SafeAgainstScript="False" />

<SafeControl Assembly="Nintex.Forms.SharePoint, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c52d764dcf7ec883" Namespace="Nintex.Forms.SharePoint.WebParts.NFListFormWebpart" TypeName="*" Safe="True" SafeAgainstScript="False" />

      

Expression Builders

<add expressionPrefix="NFResources" type="Nintex.Forms.SharePoint.NFResourceExpressionBuilder, Nintex.Forms.SharePoint, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c52d764dcf7ec883" />

     

Reference : 

https://community.nintex.com/community/support/blog/2015/01/16/error-the-expression-prefix-nfresources-was-not-recognized

SHAREPOINT 2013 FARM TOPOLOGIES

SharePoint 2013 has been out for some time now, and most of the new SharePoint engagements use SharePoint 2013. However, when it comes topology planning and which services component  should be run on each server, there isn't enough information available. Let discuss the two approaches Microsoft recommends.

SharePoint 2013 topologies

There are two type of approaches available for the SharePoint application topology as in the following:

• Streamlined topologies: the distribution of services and other components in a farm is intended to maximize system resources of server hardware. Streamlined architectures include front-end servers, batch-processing servers, and database servers
• Traditional topologies: Topologies are based on traditional approaches to building architectures with Web servers, application servers, and database servers.

Traditional topologies:

The traditional three-tier roles of a Microsoft SharePoint 2013 farm can be deployed on a single server for evaluation or development, or on many servers. The three-tier roles include the following

Web server role

Hosts web pages, Web services, and Web Parts that are necessary to process requests served by the farm. Directs requests to the appropriate application servers. In dedicated services farms, this role is not necessary because web servers at remote farms contact application servers directly.

Application server role

Provides the service features of SharePoint products and technologies. An application server often provides all or a subset of service features. Multiple redundant application servers can be load balanced.

Database server role

Stores content and service data. All databases can be assigned to one database server. Or databases can be spread across multiple servers. 

Service applications and Services on Server for traditional topologies

SERVICE APPLICATION	SERVICES ON SERVER	RECOMMENDATION
Access Services 2010	Access Database Service 2010	Application Server
Access Services	Access Services	Application Server
App Management Service	App Management Service	Application Server
Business Data Connectivity	Business Data Connectivity	Application Server
Excel Calculation Services	Excel Calculation Services	Application Server
Machine Translation Service	Machine Translation Service	Application Server
Managed Metadata Service	Managed Metadata Service	Application Server
Microsoft SharePoint Foundation Subscription Settings Service	Microsoft SharePoint Foundation Subscription Settings Service	Web server or application server
PerformancePoint	PerformancePoint	Application Serve
PowerPoint Conversion	PowerPoint Conversion Service	Application Server
Lotus Notes Connector	Lotus Notes Connector	Application Server
Search	Search Host Controller Service	Application Server
Search	Search Query and Site Settings Service	Application Server
Search	SharePoint Server Search	Application Server
Secure Store Service	Secure Store Service	Application server
Usage and Health Data Collection	NA	NA
User Profile	User Profile Service	Application server
User Profile	User Profile Synchronization Service	Application Server
Visio Graphics Service	Visio Graphics Service	Application Server
Word Automation Service	Word Automation Service	Application Server
Work Management	Work Management Service	Application Server
Central Administration	Central Administration	Application Server
Claims to Windows Token Service	Claims to Windows Token Service	Web and application servers
Distributed Cache	Distributed Cache	Web and application servers
Document Conversions Launcher Service	Document Conversions Launcher Service	Application Server
Document Conversions Load Balancer Service	Document Conversions Load Balancer Service	Application Server
Microsoft SharePoint Foundation Incoming E-Mail	Microsoft SharePoint Foundation Incoming E-Mail	Web server or application server
Microsoft SharePoint Foundation Sandboxed Code Service	Microsoft SharePoint Foundation Sandboxed Code Service	Web server or application server
Microsoft SharePoint Foundation Web Application	Microsoft SharePoint Foundation Web Application	Web server
Microsoft SharePoint Foundation Workflow Timer Service	Microsoft SharePoint Foundation Workflow Timer Service	Web server
Request Management	Request Management	Web server or dedicated servers

Streamlined topologies:

A new approach to design farm and as an alternative to the traditional farm design, Microsoft SharePoint 2013 topologies can be designed to optimize system resources and to maximize performance for users.

Front-end servers: Service applications, services, and components that serve user requests directly are placed on front-end servers. These servers are optimized for fast performance. The following services can be run on the web front-end servers:

• Access Services
• Business Data Connectivity
• Managed Metadata
• User Profile

Batch-processing servers: optimized for load, the following services can be run on the application servers

• User Profile Synchronization
• Workflow
• Machine Translation
• Work Management

Specialized BI workloads

some services applications can cause spikes in performance, such as Excel Calculation Services or PerformancePoint. If an organization uses these service applications heavily then the recommendation is to place these on dedicated servers.

Search

The search workload uses many resources. When scaling beyond two batch-processing servers, place this role on dedicated servers.

Distributed Cache and Request Management

For small and medium-size architectures, a Distributed Cache can remain on the front-end servers. Beyond 10,000 users this service is expected to work better on dedicated servers. At this scale, Request Management can be added and shared on the same servers with the Distributed Cache. The Request Manager is CPU-intensive. The Distributed Cache is memory-intensive.

Service applications and Services on Server for streamlined topologies

SERVICE APPLICATION	SERVICES ON SERVER	RECOMMENDATION
Access Services 2010	Access Database Service 2010	Web Front End (WFE ) Server
Access Services	Access Services	WFE Server
App Management Service	App Management Service	WFE Server
Business Data Connectivity	Business Data Connectivity	WFE Server
Excel Calculation Services	Excel Calculation Services	WFE  or Dedicated Application Server
Machine Translation Service	Machine Translation Service	Batch-processing server
Managed Metadata Service	Managed Metadata Service	WFE Server
Microsoft SharePoint Foundation Subscription Settings Service	Microsoft SharePoint Foundation Subscription Settings Service	WFE Server
PerformancePoint	PerformancePoint	Batch-processing server or specialized server
PowerPoint Conversion	PowerPoint Conversion Service	Batch-processing server
Lotus Notes Connector	Lotus Notes Connector	Batch-processing server or specialized server
Search	Search Host Controller Service	Specialized server for Search
Search	Search Query and Site Settings Service	Specialized server
Search	SharePoint Server Search	Specialized server
Secure Store Service	Secure Store Service	WFE Server
Usage and Health Data Collection	NA	NA
User Profile	User Profile Service	WFE server
User Profile	User Profile Synchronization Service	Application / Batch-processing server
Visio Graphics Service	Visio Graphics Service	WFE Server
Word Automation Service	Word Automation Service	Application / Batch-processing Server
Work Management	Work Management Service	Application / Batch-processing Server
Central Administration	Central Administration	Application / Batch-processing Server
Claims to Windows Token Service	Claims to Windows Token Service	Web and application servers
Distributed Cache	Distributed Cache	Web and application / Batch-processing Server
Document Conversions Launcher Service	Document Conversions Launcher Service	Application / Batch-processing Server
Document Conversions Load Balancer Service	Document Conversions Load Balancer Service	Application / Batch-processing server
Microsoft SharePoint Foundation Incoming E-Mail	Microsoft SharePoint Foundation Incoming E-Mail	WFE server
Microsoft SharePoint Foundation Sandboxed Code Service	Microsoft SharePoint Foundation Sandboxed Code Service	WFE server
Microsoft SharePoint Foundation Web Application	Microsoft SharePoint Foundation Web Application	WFE server
Microsoft SharePoint Foundation Workflow Timer Service	Microsoft SharePoint Foundation Workflow Timer Service	WFE and Batch-processing server
Request Management	Request Management	Distributed Cache and Request Management tie