SharePoint 2013 Troubleshooting: Document Library documents with duplicate document ID

Issue

In a document library there are same document id for two documents. There should be unique Document Id for a document. But duplicate Id’s are generating for different documents as below example,

e.g. There is Sales File, Accounts File with same document id: Doc-10-100
If you click on ‘Sales File’ –> Sales File.docx file is opening.
If you click on ‘Sales File’  Doc id: ‘Doc-10-100’ –>opening ‘Account File.docx’. Actually it should open ‘Sales File’.

Solution

Getting duplicate document id was a product issue after moving document (using manage content and structure) to different library. After move operation, document gets attached with  Persist ID attribute which is root cause of the issue.

This has been resolved in August 2015 CU – Click here to download .

But for existing duplicate document D’s required to be take care by some cleanup process.

SharePoint Troubleshooting: Cumulative Update (CU) installation requires Post action

Applies to

  • SharePoint 2016
  • SharePoint 2013
  • SharePoint 2010

Issue

Many people report the common issue of SharePoint administrator that is about post action requirement on CU installation on your on prem SharePoint 2010 or SharePoint 2013.

Solution

You have to run the SharePoint Configuration Product wizard after any Cumulative Updates installation on SharePoint farm. It helps to update the configuration and content DB with CU updates.

References

Click here to find all latest SharePoint available Updates

Difference between SharePoint 2010 and SharePoint 2013 Workflow

Parameters SharePoint 2010 SharePoint 2013
.NET Framework SP2010 workflow framework is designed on to of .NET framework 3.5 SP2013 workflow framework is designed on top of .NET framework 4.5
Hosting Engine SP 2010 workflow are hosted on SharePoint workflow runtime which is using Windows workflow runtime.

SharePoint Workflow Manager 2010 Architecture

Workflows are hosted outside of SharePoint.

Can be hosted on an on-premise SharePoint farm as an tenant server or Windows Azure Workflow (WAW) is an installable product.

Workflow is run as a separate service. Communication of workflows with SharePoint will happen via REST / CSOM using OAuth. Workflow architecture is shown as below,

SharePoint Workflow Manager 2013 Archìtecture

Workflow Data Storage Stored in Content database. Workflow definitions reside within SharePoint and the actual workflow is stored on Databases of Workflow Manager services.

SharePoint Workflow Manager 2013 Storage Architecture

Execution Context Workflows executed in the context of super user. In SharePoint 2013 one thing called App Step and that it is a mechanism provided to developers of SharePoint 2013-platform workflows (Designer workflows or Visual Studio workflows) to elevate permission of the workflow. you have to do following steps.

Deployment On-Premise deployment.

To deploy in a sandbox environment we need to write a full trust proxy.

Can be deployed On-Premise or in a hosted environment.

You can have a dedicated workflow farm for large deployments.

Analytics Analysis on the number of instances of workflows running, last run by and last run date are hard to acquire.

Performance

Since workflows are decoupled from SharePoint runtime it provides better stability, scalability and transparency.

Analysis is very much improved for information related to workflows.
Performance Issues with scale up and large deployments. Since workflows are decoupled from SharePoint runtime it provides better stability, scalability and transparency.
Types of Workflows Workflow Foundation 3.5.1 hosted by SharePoint 2010 Two types of workflows,

  1. SharePoint 2010 (Workflows hosted by SharePoint)
  2. SharePoint 2013 (Workflows hosted by Workflow Manager or Windows Azure)

SPD

Changes for developers Need to write source code for,

  • Calling SharePoint API
  • Connect and Query Database
  • Consume ATOM/REST Feeds
  • Call Web Services/REST Services
Workflow Manager Client 1.0 is a redesigned workflow infrastructure that is built on Windows Workflow Foundation 4 and brings new power and flexibility to workflow authoring in SharePoint 2013. Developers can perform declaratively all of the actions as mentioned in the right hand for SharePoint 2010 by using services.

SharePoint designer is significantly improved and many features that makes a developer’s life easier like copy paste, undo, redo.

A new data type called DynamicValue is being introduced to capture run time dynamic values.

Visio Designer Create in Visio and Export to SharePoint Designer. Visio Designer is integrated into SharePoint designer.
What’s New?   General Improvements

  • Introduction of “Stages”,
    • Mitigates SharePoint Designer’s lack of loop support
    • Provides functionality of “state machine” workflows in WF 3.5
  • Declarative workflows have loops,
    •  Loop # times / with condition / with expression
  • Declarative workflows can call REST/SOAP services
Workflows for SharePoint Apps Workflows execute in SharePoint hence it is difficult to protect the intellectual rights that goes into building apps. Visual Studio can be used to build workflows for SharePoint Apps whereas SharePoint Designer workflows cannot be used to build Apps.

Since workflows execute in the cloud and not in SharePoint it provides enormous flexibility in designing workflow-based apps for SharePoint.

Packaging *.wsp *.wsp or *.app

Register for Machine Learning& Data Sciences Conference, 8-9 Aug, Bangalore

The Microsoft Machine Learning and Data Sciences Conference is the place to
discover how powerful machine learning technologies are helping build an
intelligent world.

Click here to Register

 

https://click.email.microsoftemail.com/?qs=04902af8149e6bd0a592b10076f09527b19687cd627db62219d776ade46899e1ba61f5225f18f91c

Please join us along with 500 handpicked students, professors, developers, IT managers, CIOs, decision-makers and
entrepreneurs from the academia, industry and the government to connect, learn, build and discuss the future of
technology enabled by Machine Learning. The lineup includes keynotes, tech talks, tutorials, industry-academia
connect activities, demos from enterprises, startups and unicorns, and a Machine Learning based hackathon.

Participation in the event is limited and by invitation only. If you are interested, please pre-register at the earliest.

TECH TALKS BY MICROSOFT EXPERTS

  • Microsoft R Server & Applications
  • Building your end to end intelligent solution with Cortana Intelligence Suite
  • Extreme Classification: A New Paradigm for Tagging, Ranking & Recommendation
  • Text Mining using Azure ML
  • Leveraging Deep Learning for Applications
  • Moving Big Data Workloads to the Cloud
  • Scalable Data and Science using Azure Data Lake with U-SQL
  • Building Your Intelligent Applications in SQL Server R Services
  • Using the Microsoft Recommendations API
  • Sentiment Analysis & Text Mining using Cortana Intelligence Suite

If you are interested, please pre-register here.

SharePoint 2013 and SharePoint 2010: Workflow – Interview Question and Answer

Q: What are the namespaces used by SharePoint 2010 Workflow?

SharePoint

Microsoft.SharePoint.WorkflowActions
Microsoft.SharePoint.WorkflowServices
Microsoft.Sharepoint.Administration

Workflow Foundation

System.Workflow.Activities
Sytem.Workflow.ComponentModel
System.Workflow.Runtime

Q: What are the namespaces used by SharePoint 2013 Workflow?

SharePoint

Microsoft.SharePoint.WorkflowActions

Workflow Foundation

Namespace Description
System.Workflow.Activities Provides classes related to Windows Workflow Foundation activities.
System.Workflow.Activities.Configuration Provides classes that represent sections of the configuration file.
System.Workflow.Activities.Rules Contains a set of classes that define the conditions and actions that form a rule.
System.Workflow.Activities.Rules.Design Contains a set of classes that manage the Rule Set Editor and the Rule Condition Editor dialog boxes.
System.Workflow.ComponentModel Provides classes related to the Windows Workflow Foundation component model.
System.Workflow.ComponentModel.Compiler Provides classes related to the Windows Workflow Foundation component model compiler.
System.Workflow.ComponentModel.Design Provides classes related to the Windows Workflow Foundation component model designers.
System.Workflow.ComponentModel.Serialization Provides the infrastructure for managing the serialization of activities and workflows to and from extensible Application Markup Language (XAML) and CodeDOM.
System.Workflow.Runtime Provides classes related to workflow runtime.
System.Workflow.Runtime.Configuration Contains classes that are used to configure the workflow runtime engine.
System.Workflow.Runtime.DebugEngine Contains classes and interfaces for use in debugging workflow instances.
System.Workflow.Runtime.Hosting Provides classes related to Windows Workflow Foundation runtime hosting.
System.Workflow.Runtime.Tracking Contains classes and an interface related to tracking services.

Q: Give an example of Designer workflow of SharePoint 2010?

SharePoint 2010 Designer Workflow Step by Step example

Q: Give an example of Visual Studio workflow of SharePoint 2010?

SharePoint 2010 Visual Studio Workflow Step by Step example

Q: Give an example of Designer workflow of SharePoint 2013?

SharePoint 2013 Designer Workflow Step by Step example

Q: Give an example of Visual Studio workflow of SharePoint 2013?

SharePoint 2013 Visual Studio Workflow Step by Step example

Q: How do you install SharePoint 2013 Workflow?

Set up and configure SharePoint 2013 Workflow Manager

Consuming service on SP2013 from SP2016: Remote Connection – errors even after trusts are established

Issue

Below is environment details:

  • SP 2016 Publishing Server – Farm A
  • SP 2013 Consuming Server – Farm B

While trying to establish a Remote Connection between Farm A from Farm B by using HTTP connection even on establishing of trust facing below error,

Error

Unable to connect to the specified address. Verify the URL you entered and contact the service administrator for more details.

Error Description

An operation failed because the following certificate has validation errors:
Errors:SSL policy errors have been encountered.  Error code ‘0x6’..
<EventID>8311</EventID>
SSL policy errors have been encountered.  Error code ‘0x6’.

Solution

There are 3 steps to the resolution:

  • Step 1: Request Management must be enabled on the Publishing server
  • Step 2: The permissions must match on the service on BOTH of the farms
  • Step 3: Start and restart the service, via Powershell, that you want to connect too

SharePoint 2013 and Office 2016 : Issue of scroll bar

Issue

Right vertical scroll bar is missing while selecting office file save as option in SharePoint 2013 with  Office 2016 products.

If you are using version mentioned below for the SharePoint server.

moss-server  Update for Microsoft SharePoint Enterprise Server 2013 (KB3114497) 64-Bit Edition 15.0.4787.1000

IssueOfScrollBar

Solution

Install the latest CU (June 2016 CU or whichever latest available CU) for SharePoint 2013 environment would resolve this issue.