Vince's Sharepoint blog

Bye Bye AutoHosted Apps

Vincent Runge — Tue, 27 May 2014 05:21:39 GMT

After June 30th 2014, we will not able to create new authosted apps in SharePoint. More at https://blogs.office.com/2014/05/16/update-on-autohosted-apps-preview-program/

Don't miss the TechDays 2014

Vincent Runge — Mon, 03 Feb 2014 14:02:26 GMT

Dedicated to new technologies, this event takes place 11th, 12th, 13th Feb 2014 in Paris.

I'll present the session on best practices for SharePoint and ADFS integration.

Execution times without Developer Dashboard?

Vincent Runge — Sun, 19 Jan 2014 14:08:00 GMT

While analyzing performance issues, I came across a situation where the developer dashboard is not available.

ULS logs actually contain the execution times, in events with tags b4ly. The b4ly events are only logged when the logging for the product SharePoint Foundation, category Monitoring is set to High or more.

I wrote a powershell script to extract execution times from ULS logs, for a given correlation ID. The goal is to understand quickly what took time when processing the request.I've published the script as on https://dumpexecutiontime.codeplex.com/ . Examples and parameter details are described at https://dumpexecutiontime.codeplex.com/documentation

To extract the execution times:

Set the logging level for the product SharePoint Foundation, category Monitoring to High or more.
Reproduce the issue
Retrieve the Dump-ExecutionTime.ps1 script from https://dumpexecutiontime.codeplex.com/ and save it locally
Start powershell & run Dump-ExecutionTime.ps1 , e.g.

dir v:*log | C:\Tests\Dump-ExecutionTime.ps1 -Threshold 500

The output is like below:

Extracting Execution Times above 500 ms from file V:\srs\Ignacio Verbose-c52663.log with correlation id matching *

ExecTime         Monitored Scope
----------       ------------------------------
   729.130       Leaving Monitored Scope (Directory Search).
   792.014       Leaving Monitored Scope (Directory Search).
   666.610       Leaving Monitored Scope (PortalSiteMapNode: Populating navigation children for web: /).
   722.340       Leaving Monitored Scope (Directory Search).
   659.460       Leaving Monitored Scope (Directory Search).
   675.208       Leaving Monitored Scope (Directory Search).
   510.887       Leaving Monitored Scope (Directory Search).
   616.288       Leaving Monitored Scope (Directory Search).
   603.682       Leaving Monitored Scope (Directory Search).
   523.035       Leaving Monitored Scope (Directory Search).
   592.420       Leaving Monitored Scope (Directory Search).
   507.795       Leaving Monitored Scope (Directory Search).
   620.947       Leaving Monitored Scope (Directory Search).
8,580.957       Leaving Monitored Scope (Render the Web part of the PII own documents).
8,581.096       Leaving Monitored Scope (Render the Web part- Main).
8,641.322       Leaving Monitored Scope (SharePointForm Control Render).
14,294.430       Leaving Monitored Scope (Request GET:https://server.domain.com/Forms/AllItems.aspx)).

17 monitored scopes matched, for a total of 48317.62 ms

In this example, the Directory Searches are responsible for most of the response time.

Enjoy!

Vincent Runge

Troubleshooting Actions for SharePoint 2013 Workflows

Vrunge — Tue, 07 Jan 2014 03:08:22 GMT

After delivering the internal Workflow trainings, I have compiled a list of troubleshooting actions for workflow support with SharePoint 2013. The actions below apply to the “new” workflows (workflows living in the Workflow Manager, based on Windows Workflow Foundation 4.0). These actions are not relevant for the “legacy” workflows (SharePoint 2010, using .NET Framework 3.5).

Workflow Execution Issues

1. Look in the Workflow History list, eg "https://sp2013/Lists/Workflow History". Do you find any errors in there?

2. Is the user account starting the workflow correctly synchronized in the user profile database?

3. Is the user account starting the workflow different from the Worflow Manager setup account? (more info at https://technet.microsoft.com/en-us/library/jj658588.aspx#section7)

4. Are the User Profile Service and App Management Service started? See the green frames in the screenshot below, taken from Central Administration \ Manage Services on Server:

5. Are the App Management Service Application and User Profile Service Application started? Their proxies should be started as well. See the green frames in the screenshot below, taken from Central Administration \ Manage Services on Server:

How to Retrieve an Exception in the Workflow Manager Database

Note that this is unsupported in a production environment, but very useful in a test environment!

In the SharePoint page workstat.aspx, copy the field requestor id

1. In the URL query parameter from the worsktat.aspx page, copy the instanceid field

2. Open the WFInstanceManagementDB database with SQLManagement Studio, then request from the DebugTrace table

3. The exception is in the WorkflowStatusDetail column

Is SharePoint 2013 server connected?

In Central Admin\ Service Applications \ Workflow Service Application Proxy: check the status. Does it read Workflow is Connected as in the below screenshot?

Is the Worflow Manager farm running?

On a server member of the Workflow Manager farm:

1. Start Workflow Manager PowerShell

2. Run the get-WFStatus command

3. Are the statuses Running, as on the screenshot below?

Is the Oauth Metadata information published and accessible from the SharePoint server?

On the SharePoint 2013 server, start Internet Explorer, and check whether the Oauth metadata is accessible. The url is like https://wfm1:12291/$SYSTEM/$Metadata/json/1 . Below an example:

Are the Scopes registered in the Workflow Manager farm?

It is possible to check from Internet Explorer that the scopes are registered. It is also possible to navigate the workflow data. The example URLs below allow to check these elements:

https://wfm1:12291/$ChildScopes

https://wfm1:12291/SharePoint/default/659f1e87-c228-420e-9eb6-c2ca4b5b7cf8/aa605c44-734b-4bd4-b961-2afd253d1c3d/$ChildScopes

https://wfm1:12291/SharePoint/default/659f1e87-c228-420e-9eb6-c2ca4b5b7cf8/aa605c44-734b-4bd4-b961-2afd253d1c3d/$Workflows

https://wfm1:12291/SharePoint/default/659f1e87-c228-420e-9eb6-c2ca4b5b7cf8/aa605c44-734b-4bd4-b961-2afd253d1c3d/$Workflows/0ce48b29-b821-4785-ab12-34564e7332a3/$Instances

Notes

The GUIDs in the above URLs are not static.

The tool below provides an easy navigation in the workflow manager data:

https://code.msdn.microsoft.com/windowsdesktop/Workflow-Resource-Browser-a67b1d27

On a Workflow Manager server, you have to run the Workflow-Resource-Browser as administrator.

Activate Workflow Manager Logs

1. Start Event Viewer

2. Expand Applications and Services Logs \ Microsoft-Workflow

3. In the menu View \ Show Analytical and Debug logs

4. Select the Debug log, then right-click enable Log

5. Reproduce

the issue

6. Select the Debug log, righ-click Disable Log. (The point is to avoid filling the platform with logs)

7. It is then possible to save the le log in the EVTX format

I hope this checklist will help you while setting up and troubleshooting workflow!

For French readers, the French version of this post is accessible at https://blogs.technet.com/b/french_sharepoint_gbs_blog/archive/2014/01/06/diagnostique-des-workflows-2013.aspx

User Profile Synchronization Architecture

Vrunge — Wed, 03 Jul 2013 06:39:14 GMT

While delivering our SharePoint 2013 User Profiles internal trainings, I realized how many components take part in synchronization, and how difficult it is for non-graphical learners to assimilate the architecture.

I sketched the diagrams below to help me remember the various components and their role. I hope this will help others understand the mechanisms of user profile synchronization.

The “System Job to Manage User Profile Synchronization” can also refered to as “ILMProfileSynchronizationJob”.

Name	{name of the UPA_} ProfileSynchronizationJob
DisplayName	{name of the UPA} - System Job to Manage User Profile Synchronization
Description	This timer job manages provisioning, run steps and additional tasks related to User Profile Synchronization. DO NOT CHANGE the information or frequency of this job. If you need to change how often incremental synchronization is done, access the user interface through the User Profile Service admin page, and click on the "Schedule Incremental User Profile Synchronization" link under the "Synchronization" category.

Provisioning of the ForeFront Identity Management synchronization

The first diagram is about the provisioning of the FIM.

The "System Job to Manage User Profile Synchronization" timer job starts the one-time ProfileSynchronizationSetupJob timer job.

Name	ProfileSynchronizationSetupJob
DisplayName	Provision User Profile Synchronization Service

Synchronizing

The second diagram is about the synchronization itself.

The " System Job to Manage User Profile Synchronization" timer job starts the “User Profile Incremental Synchronization” timer job.

Name	{name of the UPA_} ProfileImportJob
DisplayName	{name of the UPA} - User Profile Incremental Synchronization
Description	This timer job will run at the specified interval to synchronize user, group and group membership changes between the User Profile Application and specified directory source (such as Active Directory or LDAP). Synchronization will look for changes since the last time this job was run and only perform these

Note the User Profile Incremental Synchronization timer job uses WMI to communicate with MIIServer.exe. SharePoint’s Management Agent (MA) logic is in Microsoft.office.server.UserProfiles.ManagementAgent.dll.

The terminology could also be confusing for SharePoint engineers, as it is based on “FIM” point of view:

Import: getting data from connected directory to connector space
Export: getting data from the connector space to the connected directory.

Keep in mind it is not supported to modify the content of the databases. Doing so may corrupt your data!

Support answers on sandboxed solutions in SharePoint 2010

Vrunge — Wed, 12 May 2010 09:17:51 GMT

This article details some aspects of sandbox solution usage with Sharepoint 2010 RTM.

Detailed steps to setup sandbox solutions are available at https://technet.microsoft.com/en-us/library/ee704543(office.14).aspx

Process and SandBoxing

Q: In which process does a sandbox solution execute?

A: executable is C:\program files\Common Files\Microsoft Shared\Web Server Extensions\14\UserCode\SPUCWorkerProcess.exe

Q: In VisualStudio, I receive “Error occurred in deployment step 'Activate Features': Cannot start service SPUserCodeV4 on computer ''.

A: Verify that the service “Microsoft SharePoint Foundation Sandboxed Code Service” is running. Its status can be verified in Central Administration \ System Settings \ Manage Services on this server.

Q: How to check if a solution was sandboxed when an exception occurred?

A: if call stack contains

SPUCWorkerProcess.exe!Microsoft.SharePoint.UserCode.SPUserCodeApplicationHostAppDomainRef.ExecuteWrapper

The solution ran in a sandbox.

Q: How to recycle the sandbox process ?

A: the SPUCWorkerProcess.exe process is recycled when stopping & restarting the “Microsoft SharePoint Foundation Sandboxed Code Service” service.

Sandboxing and DLLs…

Q: How to visualize the object model available for a sandbox solution?

A: the object model is viewable with object explorer on c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\UserCode\assemblies\Microsoft.SharePoint.dll. Only available methods are displayed. For example, the non-authorized method Microsoft.SharePoint.Utilities.SPUtility.SendEmail() is not displayed. But the available Microsoft.SharePoint.Utilities.SPUtility.StringToUInt64() is displayed.

Q: From which folder is my DLL loaded when my solution runs in a sandbox?

A: the DLL is loaded from C:\ProgramData\Microsoft\SharePoint\UCCache\\.dll

Q: What happens when a non-authorized method is called ?

A: an exception is generated. For example, in a webpart, you see:

Web Part Error: Unhandled exception was thrown by the sandboxed code wrapper's Execute method in the partial trust app domain: An unexpected error has occurred.

Detailed error below (the exception is in maroon color) :

[SPUserCodeSolutionExecutionFailedException: Une exception non gérée a été générée par la méthode Execute du wrapper de code en mode bac à sable dans le domaine d’application de confiance partielle : Une erreur inattendue s'est produite.]
Server stack trace:
at Microsoft.SharePoint.UserCode.SPUserCodeApplicationHostAppDomainRef.Execute(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, Byte[] binaryUserCodeToken, Byte[] proxyOperationToken, SPUserCodeExecutionContext executionContext)
at Microsoft.SharePoint.UserCode.SPUserCodeApplicationHostAppDomainRef.Execute(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, Byte[] binaryUserCodeToken, Byte[] proxyOperationToken, SPUserCodeExecutionContext executionContext)
at Microsoft.SharePoint.UserCode.SPUserCodeAppDomain.Execute(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, Byte[] binaryUserCodeToken, Byte[] proxyOperationToken, SPUserCodeExecutionContext executionContext)
at Microsoft.SharePoint.UserCode.SPUserCodeWorkerProcessProxyForShim.ExecuteInternal(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, Byte[] binaryUserCodeToken, Byte[] proxyOperationToken, SPUserCodeExecutionContext executionContext)
at Microsoft.SharePoint.UserCode.SPUserCodeWorkerProcessProxy.Execute(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, Byte[] binaryUserCodeToken, Byte[] proxyOperationToken, SPUserCodeExecutionContext executionContext)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.SharePoint.UserCode.SPUserCodeWorkerProcess.ExecuteDelegate.EndInvoke(IAsyncResult result)
at Microsoft.SharePoint.UserCode.SPUserCodeWorkerProcess.Execute(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, SPUserToken userToken, String currentAffinity, SPUserCodeExecutionContext executionContext)
at Microsoft.SharePoint.UserCode.SPUserCodePoolableProcessConnection.Execute(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, SPUserToken userToken, String affinity, SPUserCodeExecutionContext executionContext)
at Microsoft.SharePoint.UserCode.SPUserCodeExecutionHost.Execute(Type userCodeWrapperType, Guid siteCollectionId, SPUserToken userToken, String affinity, SPUserCodeExecutionContext executionContext)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)
Exception rethrown at [1]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.SharePoint.Administration.ISPUserCodeExecutionHostProxy.Execute(Type userCodeWrapperType, Guid siteCollectionId, SPUserToken userToken, String affinityBucketName, SPUserCodeExecutionContext executionContext)
at Microsoft.SharePoint.UserCode.SPUserCodeExecutionManager.Execute(Type userCodeWrapperType, SPSite site, SPUserCodeExecutionContext executionContext)
at Microsoft.SharePoint.UserCode.SPUserCodeWebPartRemoteExecutionHelper.<>c__DisplayClassa.b__9()
at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)
at Microsoft.SharePoint.UserCode.SPUserCodeWebPartRemoteExecutionHelper.ExecuteRequestInSandBox(HttpContext context, SPWeb web, SPWebPartManager manager, SPUserCodeWebPart userCodeWebPart)
[HttpUnhandledException: Exception of type 'System.Web.HttpUnhandledException' was thrown.]
Server stack trace:
at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at Microsoft.SharePoint.UserCode.SPUserCodeWebPartWrapper.ExecuteHttpRequest(SPUserCodeWebPartHttpRequestContext webPartExecutionContext, SPUserCodeWebPartHttpResponse httpRequestResponse)
at Microsoft.SharePoint.UserCode.SPUserCodeWebPartWrapper.Execute(SPUserCodeExecutionContext executionContext)
at Microsoft.SharePoint.UserCode.SPUserCodeApplicationHostAppDomainRef.ExecuteWrapper(SPUserCodeWrapper wrapper, SPUserCodeExecutionContext executionContext)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)
at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)
at Microsoft.SharePoint.UserCode.SPUserCodeApplicationHostAppDomainRef.CodeToExecuteWrapper.EndInvoke(IAsyncResult result)
at Microsoft.SharePoint.UserCode.SPUserCodeApplicationHostAppDomainRef.Execute(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, Byte[] binaryUserCodeToken, Byte[] proxyOperationToken, SPUserCodeExecutionContext executionContext)
[MissingMethodException: Method not found: 'Void Microsoft.SharePoint.Utilities.SPUtility.GetNTFullNameandEmailfromLogin(Microsoft.SharePoint.SPWeb, System.String, System.String ByRef, System.String ByRef)'.]
at SBWebPArt5_Login_Sable.Login_WebPArt5_Sable.Login_WebPArt5_Sable.<>c__DisplayClass1.b__0(Object , EventArgs )
at System.Web.UI.WebControls.Button.OnClick(EventArgs e)
at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)
at System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

ULS log contains an entry for SPUCWorkerProcess.exe and also an entry for SPUCHostService.exe:

04/29/2010 16:47:46.22 SPUCWorkerProcess.exe (0x1530) 0x1780 SharePoint Foundation Sandboxed Code Service

fe8s Medium - - Unhandled exception was thrown by the sandboxed code wrapper's Execute method in the partial trust

app domain: An unexpected error has occurred. - userCodeWrapperType = "Microsoft.SharePoint.UserCode.SPUserCodeWebPartWrapper",

userAssemblyGroupId = "3F74E8EE99624C358005954B7BD10334-idjGV+/yzfqv3u+SsMvNh/QyrYW23cR2ErgVPMa+clc=", siteCollectionId = "22b46f56-a5c1-

47cc-b55f-fdb9b369ca19" - Inner Exception: Microsoft.SharePoint.UserCode.SPUserCodeSolutionProxiedException: Exception of type

'System.Web.HttpUnhandledException' was thrown. ---> Microsoft.SharePoint.UserCode.SPUserCodeSolutionProxiedException: Method not found:

'Void Microsoft.SharePoint.Utilities.SPUtility.GetNTFullNameandEmailfromLogin(Microsoft.SharePoint.SPWeb, System.String, System.String

ByRef, System.String ByRef)'.
at SBWebPArt5_Login_Sable.Login_WebPArt5_Sable.Login_WebPArt5_Sable.<>c__DisplayClass1.b__0(Object , EventArgs )

at System.Web.UI.WebControls.Button.OnClick(EventArgs e) at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)

at System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

--- End of inner exception stack trace ---

Server stack trace:      at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at Microsoft.SharePoint.UserCode.SPUserCodeWebPartWrapper.ExecuteHttpRequest(SPUserCodeWebPartHttpRequestContext webPartExecutionContext,

SPUserCodeWebPartHttpResponse httpRequestResponse)
at Microsoft.SharePoint.UserCode.SPUserCodeWebPartWrapper.Execute(SPUserCodeExecutionContext executionContext)
at Microsoft.SharePoint.UserCode.SPUserCodeApplicationHostAppDomainRef.ExecuteWrapper(SPUserCodeWrapper wrapper, SPUserCodeExecutionContext

executionContext)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr,

Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)
at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)
at Microsoft.SharePoint.UserCode.SPUserCodeApplicationHostAppDomainRef.CodeToExecuteWrapper.EndInvoke(IAsyncResult result)
at Microsoft.SharePoint.UserCode.SPUserCodeApplicationHostAppDomainRef.Execute(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup

userAssemblyGroup, Guid siteCollectionId, Byte[] binaryUserCodeToken, Byte[] proxyOperationToken, SPUserCodeExecutionContext

executionContext)

04/29/2010 16:47:46.29 SPUCHostService.exe (0x0548) 0x13B8 SharePoint Foundation Sandboxed Code Service

fe3r Medium - - Unhandled exception was thrown by the sandboxed code wrapper's Execute method in the partial trust

app domain: An unexpected error has occurred. - Monitored process "ipc://ef45c9b0-c020-4920-a200-434242116856:7000" has encountered an

unhandled exception while executing user code. - Inner Exception: Microsoft.SharePoint.UserCode.SPUserCodeSolutionProxiedException:

Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> Microsoft.SharePoint.UserCode.SPUserCodeSolutionProxiedException:

Method not found: 'Void Microsoft.SharePoint.Utilities.SPUtility.GetNTFullNameandEmailfromLogin(Microsoft.SharePoint.SPWeb, System.String,

System.String ByRef, System.String ByRef)'.
at SBWebPArt5_Login_Sable.Login_WebPArt5_Sable.Login_WebPArt5_Sable.<>c__DisplayClass1.b__0(Object , EventArgs )

at System.Web.UI.WebControls.Button.OnClick(EventArgs e)
at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)
at System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
--- End of inner exception stack trace ---

Server stack trace:
at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at Microsoft.SharePoint.UserCode.SPUserCodeWebPartWrapper.ExecuteHttpRequest(SPUserCodeWebPartHttpRequestContext webPartExecutionContext,

executionContext) at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server,

Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink) Exception rethrown at

[0]:      at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)
at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)
at Microsoft.SharePoint.UserCode.SPUserCodeApplicationHostAppDomainRef.CodeToExecuteWrapper.EndInvoke(IAsyncResult result)
at Microsoft.SharePoint.UserCode.SPUserCodeApplicationHostAppDomainRef.Execute(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup

userAssemblyGroup, Guid siteCollectionId, Byte[] binaryUserCodeToken, Byte[] proxyOperationToken, SPUserCodeExecutionContext

executionContext)

Note: GetNTFullNameandEmailfromLogin is the method called in this example.

Vincent Runge, Escalation Engineer

Content Deployment with MOSS2007: Remote Upload Request failed - Http 502 Proxy Error

Vrunge — Wed, 28 Jan 2009 04:39:00 GMT

This post is about a specific situation that may happen when doing Content Deployment with MOSS2007: Remote Upload Request failed - Http 502 (aka bad gateway)

The HTTP 502 Proxy Error

The content deployment job fails with: Content deployment job '' failed.The remote upload Web request failed.

The ULS log shows an entry

01/28/2009 09:58:09.07 OWSTIMER.EXE (0x0984) 0x0500 CMS Content Deployment 6p00 Critical

Failed to communicate with destination server for Content Deployment job ''. Exception was: 'System.Net.WebException: The request failed with HTTP status 502: Proxy Error ( The host was not found. ). at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)

at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)

at Microsoft.SharePoint.Publishing.Internal.Administration.ContentDeploymentRemoteImportSoapClient.CreateJob(String description, String sourceId, String destinationServerUrl, String destinationSiteCollection, SPIncludeSecurity includeSecurity, SPImportUserInfoDateTimeOption includeUserInfoDateTime, Boolean enableEventReceivers, Boolean fileCompression)

at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.DoServerToServer()'

How I could resolve it ?

On the server:

1. net stop sptimerv3

2. Interactively log-on as the Service Account.

3. Launched Internet Explorer, menu Tools \ Internet Options \ Connections \ LAN Settings : clear all check-boxes, including the “Automatically detect settings”

4. Logoff

5. Logon on as Admin

6. Net start sptimerv3

7. Start the Content Deployment job again

Blog4_IEProxySettings.jpg

Configuring the LDAP membership provider and role provider to integrate with an LDAP server that uses “ “ (a space) as root.

Vrunge — Fri, 19 Dec 2008 05:16:00 GMT

1 – Problem description

I’ve seen cases where is used as rootDSE by IBM Lotus Domino™ version 8.x.

But beware that setting the userContainer in the web.config like this:

userContainer=” “

does not provide the expected results.

2 - How to specify an empty space in the configuration file?

You need to use " to represent the double quote. For example:

userContainer="" ""

and

groupContainer="" ""

I provide below the configuration files I used – maybe they’ll help you set up your environment.

2-a) Example configuration file for the Admin WebApp

This configuration file is provided “as is” (without any warranties, not supported, use it at your own risk). You need to adapt it to your own needs.

mio PeoplePickerWildcards>

And

<add name="LdapMembership" type="Microsoft.Office.Server.Security.LDAPMembershipProvider, Microsoft.Office.Server, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71E9BCE111E9429C" server=""

port="389"

useSSL="false"

userDNAttribute="uid"

userNameAttribute="uid"

userContainer="" ""

userObjectClass="dominoPerson"

userFilter="(|(ObjectCategory=dominoGroup)(ObjectClass=dominoPerson))"

scope="Subtree"

otherRequiredUserAttributes="sn,givenname,cn" />

providers>

membership>

<add name="LdapRole"

type="Microsoft.Office.Server.Security.LDAPRoleProvider, Microsoft.Office.Server,Version=12.0.0.0,Culture=neutral,PublicKeyToken=71E9BCE111E9429C"

server=""

port="389"

useSSL="false"

groupContainer="" ""

groupNameAttribute="cn"

groupMemberAttribute="member"

userNameAttribute="uid"

dnAttribute="fullname"

groupFilter="(ObjectClass=dominoGroup)"

scope="Subtree" />

providers>

roleManager>

2-b) Example configuration file for the extended WebApp

This configuration file is provided “as is” (without any warranty, not supported, use it at your own risk). You need to adapt it to your own needs.

Note the setting of the default Provider : <roleManager defaultProvider="LdapRole"

PeoplePickerWildcards>

AND

<add name="LdapMembership" type="Microsoft.Office.Server.Security.LDAPMembershipProvider, Microsoft.Office.Server, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71E9BCE111E9429C"

server=""

port="389"

useSSL="false"

userDNAttribute="uid"

userNameAttribute="uid"

userContainer="" ""

userObjectClass="dominoPerson"

userFilter="(|(ObjectCategory=dominoGroup)(ObjectClass=dominoPerson))"

scope="Subtree"

otherRequiredUserAttributes="sn,givenname,mail,cn" />

providers>

membership>

<add name="LdapRole" type="Microsoft.Office.Server.Security.LDAPRoleProvider, Microsoft.Office.Server, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71E9BCE111E9429C"

server=""

port="389"

useSSL="false"

groupContainer="" ""

groupNameAttribute="cn"

groupMemberAttribute="member"

userNameAttribute="uid"

dnAttribute="fullname"

groupFilter="(ObjectClass=dominoGroup)" scope="Subtree" />

providers>

roleManager>

3) Example configuration the Profile Import connection

Edit your SSP’s profile connection (Shared Services Administration: Your_SSP > User Profile and Properties > Manage Connections > Edit Connection) with suggested parameters:

Provider name: LdapMembership

Username attribute: uid

Search base: “ “ (no specific encoding needed here)

User filter: (&(objectClass=inetorgperson))

4) Summary

As I explained above, it is quite usual to find a used as Root for LDAP server in Domino configuration. Setting directly “ “ in the config files without specifically escaping the double-quotes does not work correctly. The examples provided above illustrate clearly how to properly configure the web.config & Profile import connection for this to work.

Tasks staying locked by a running workflow, and never unlocking.

Vrunge — Wed, 24 Sep 2008 05:03:00 GMT

This post discusses one of the possible cause of the error "This task is currently locked by a running workflow and cannot be edited", when tasks are part of a workflow. This message is expected when a workflow is running on the task, and has events to process. After processing the events, the task will be unlocked.

However, there might also be situations where tasks will stay locked forever.

How does this happen?

This behavior can typically happen when there is an issue while committing a workflow batch. Multiple workflow results are grouped together to be committed to the database in a single transaction. If an exception occurs while committing the transaction, the whole transaction will be cancelled. None of the results will be committed.

To verify if there was an error while committing the workflow results:

1) Increase the diagnostic level for the category “Workflow Infrastructure” to either High, Medium or Verbose

2) check the ULS logs for :

Windows SharePoint Services Workflow Infrastructure 72fe High

Error in commiting pending workflow batch items: Microsoft.SharePoint.SP

Exception: …

The 72fe does not necessarily mean tasks will stay locked, it just indicates a transaction did not succeed. Tasks can stay locked if this transaction contained the “unlocking” of the task (e.g. set the WorkflowVersion field back to 1).

So what shall I do next ?

Ideally, find the root cause of the 72fe tag, and eliminate them….

In case you do not want to investigate further, the safest might be to cancel the workflow on the item, and then restart it.

Note : in French, the error is: "Cette tâche est actuellement verrouillée par un flux de travail en cours d'exécution et ne peut pas être modifiée".

Thanks to Gyorgy Homolya for his help in writing this post.

About the “workflow-eventdelivery-throttle” parameter

Vrunge — Tue, 16 Sep 2008 07:17:00 GMT

The WorkflowEventDeliveryThrottle parameter is used to throttle the workflow events processing in WSS 3.0 / MOSS2007.

Understanding the Workflow Events processing

Where can a workflow event be processed? Events can be processed by either the worker process (W3WP.exe) or in SPTimerv3 (OWSTimer.exe).

To prevent web front ends (w3wp) from getting overrun by running too many workflows instances, there is a throttle limit. If more events than the throttle are already being processed, the newer events are enqueued as work items – they will be picked up by OWSTimer.

You can figure out if you’re in this situation by increasing the diagnostic level for the category "Workflow Infrastructure" to Verbose. Then, you'll have to check up the ULS logs for entries like:

08/19/2008 16:06:29.87 w3wp.exe (0x16E8) 0x1C7C

Windows SharePoint Services Workflow Infrastructure 936r Verbose

RunWorkflow: No pending events - possibly targeted for async delivery: List:/Site/MyList Item:

You can also check the performance counters :

Ø Windows Workflow Foundation\Workflows Loaded

Ø Windows Workflow Foundation\Workflows Completed

for the processes W3WP and OWSTimer.

When is the throttle used?

The WorkflowEventDeliveryThrottle is used to decide where to process workflow events:

Ø Synchronously in W3WP

Ø Asynchronously in OWSTimer

How to set the throttle?

The throttle can be changed either:

Ø Manually, by running “stsadm -o setproperty -propertyname workflow-eventdelivery-throttle” without the “–url” parameter ( https://technet.microsoft.com/en-us/library/cc287939.aspx ).

Ø Programmatically by modifying SPWebService.WorkflowEventDeliveryThrottle (cf https://msdn.microsoft.com/en-us/library/microsoft.sharepoint.administration.spwebservice.workfloweventdeliverythrottle.aspx ).

Which value to set in the throttle?

There is no definite answer to this question… The answer should be based upon your configuration, number of FrontEnd servers, load, requirements, etc…

Consider the following scenario:

Ø a workflow, associated to a list, is set to be run each time a document is created.

Ø the event processing consumes resources and therefore takes some time to accomplish

Ø many users are simultaneously creating documents/items

What could happen in this scenario? At first, the throttle value may be quickly reached. At this point, w3wp will not process any new workflow events, instead they will be queued and will wait to be run by OWSTimer. So far so good, but what if OWSTimer cannot process events as fast as they arrive? The number of throttled items will increase continuously… Eventually, we may end up in a vicious circle: all events are throttled, hence increasing the load on OWSTimer, hence preventing OWSTimer to handle all events, etc… Users will report that the workflows are very slow to process: “I completed my task, and I have to wait until tomorrow for the next step”, “processing only happens overnight”…

Of course, some factors will mitigate this:

Ø when users stop working (e.g. during the night), OWSTimer will dequeue the throttled events,

Ø you could add other servers to your farm to have more OWSTimer

Ø you could change the throttle value to process more events in the W3WP (providing your W3WPs can afford it)

On heavy loaded systems, you could perform the subquery below to compare with the throttle:

DECLARE @Now datetime

SET @Now = dbo.fn_RoundDateToNearestSecond(GETUTCDATE())

SELECT

COUNT(DISTINCT BatchId)

FROM

dbo.ScheduledWorkItems WITH (NOLOCK)

WHERE

Type = 'BDEADF09-C265-11D0-BCED-00A0C90AB50F'

AND

DeliveryDate <= @Now

AND

(InternalState & (1 | 16)) = (1 | 16)

The idea behind this query is to get an indication for the possible throttle values. If the value returned by query is superior to the throttle (15 by default), any new workflow event will not be processed immediately, instead it will be enqueued and will wait to be run by OWSTimer.

Thanks to Yvan Duhamel for his help in writing this post.

More Info

can be found at https://msdn.microsoft.com/en-us/library/dd441390.aspx