Whether you're troubleshooting issues on your own or with the guidance of Nintex Support, generating ULS logs for Nintex is one of the best methods to identifying underlying causes of issues that are occurring within your environment. Below is a step by step guide on how to configure and generate the most effective ULS logs to identify Nintex related issues.
1. Navigate to Central Administration > Monitoring > Configure diagnostic logging > Check box for all categories starting with 'Nintex'. For example:
Nintex External Connection Components
Nintex Workflow 2010/2013
Note: The 'Nintex' categories will vary between different versions of SharePoint.
2. Expand SharePoint Foundation and select the check box 'Legacy Workflow Infrastructure'.
3. Scroll to the bottom of the page and select 'Verbose' in the dropdown for "Least critical event to report to the trace log", click OK.
4. After the logging has been configured, replicate the error or behavior. Take note of the time of your replication.
5. On one of your SharePoint servers, open a SharePoint Management Shell as Administrator
6. Use the Merge-SPLogFile cmdlet in a SharePoint Management Shell window (or PowerShell with admin privileges and the proper PSsnapin 1). Modify the -StartTime and -EndTime parameters to capture the timeframe of the replication.
To collect log information for an error condition occurring at 4:00 p.m. (16:00) on October 14, 2019, enter the following:
Merge-SPLogFile -Path "C:\FarmMergedLog.log" -Overwrite -StartTime "10/14/2019 15:55" -EndTime "10/14/2019 16:05"
To use Merge-SPLogFile in PowerShell, run Add-PSsnapin Microsoft.SharePoint.PowerShell
If the request for ULS logs came from Nintex Support:
1. Please zip the files as this will compress the log file significantly.
2. If the file is less than 5MB, send it using normal email provided with your case.
3. If file is more than 5MB, please request an upload link from Nintex Support.
Download the ULS Viewer from Microsoft: