We found that there is a Nintex timer job which did not complete as given below. It is stuck at 0% and it did not start as it shows. We also tried to run another job for the said web application and it did not run or complete.
Restarted and cleared timer service cache, still no go. The job would not complete.
Enabled verbose for Nintex and found the following error:
Checked the uls logs after verbose and found the following error, but could not find the site collection related information, will check with sql team. Got some workflow termination related errors whereby the parent workflow instance was not found in the database, doing further investigation.:
07.15.2020 04:30:47.47 OWSTIMER.EXE (servername:0x3160) 0x52C8 SharePoint Foundation Workflow Infrastructure 88xr Unexpected WinWF Internal Error, terminating workflow Id# "Workflow id"
07.15.2020 04:30:47.47 OWSTIMER.EXE 0x52C8 SharePoint Foundation Workflow Infrastructure 98d4 Unexpected System.InvalidOperationException: Parent workflow instance "instance guid" was not found in database <database name> on server <sql server>. ---> System.Data.SqlClient.SqlException: Cannot insert the value NULL into column 'InstanceID', table '<dbname>.dbo.WorkflowProgress'; column does not allow nulls. INSERT fails. The statement has been terminated. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
Ran the Sql query to be done is as below:
SELECT * FROM dbo.WorkflowInstance
WHERE WorkflowInstanceID = guid
Current understanding and roadbloack:
1. The timer job is not stuck and not completing, seems the cause of the issue. Timer service refresh did not help.
2. We are not sure of the uls logs as it is pointing to a different web application, then in question here. However I feel it is Nintex workflow issue as whole.
3. Sql query for the uls logs error for workflow instance does not show any listing on the said database or even if run directly with no database reference.
4. Checked the Nintex community for suggestions and found this, however we did not get the exact errors as listed. Still we are not able to reach the workflow instance as to which site it belongs to: