Nintex for SharePoint Forum
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
I have 2 services that will not start after installing to our development setup for SharePoint 2016.
1. Nintex Workflow Start Service
Error
Error1: Incorrect Function
2. Nintex Connector Workflow Queue Service
3. At the site collection level activate the features fails..... I am guessing the services not starting are related to the site collections activate features fails for Nintex.
I corrected 2 and 3 however, This service will not start. It is by design?
Nintex Workflow Start Service
Looks what ever account is used for "Nintex Workflow Start Service" and "Nintex Connector Workflow Queue Service" require execute on the SharePoint Config DB for the following procedures. Bydefault the account is Local System.
- proc_putObjectTVP
- proc_putObject
- proc_putClass
- proc_putDependency
- proc_getNewObjects
I changed the accounts for the 2 services from Local System to the same account used for the "Nintex Connector Relay Service". Then gave the account execute permissions to run the stored procedures. Obviously change to suit your environments.
use [SharePoint_Config]
GO
GRANT EXECUTE ON [dbo].[proc_putObjectTVP] TO [Domain\SP_Services]
GRANT EXECUTE ON [dbo].[proc_putObject] TO [Domain\SP_Services]
GRANT EXECUTE ON [dbo].[proc_putClass] TO [Domain\SP_Services]
GRANT EXECUTE ON [dbo].[proc_putDependency] TO [Domain\SP_Services]
GRANT EXECUTE ON [dbo].[proc_getNewObjects] TO [Domain\SP_Services]
GO
The Services should then start fine. Also check out the following if changing your Nintex Connector Relay Service to something other than the Farm account which gets set on install.
https://community.nintex.com/thread/2734
Cheers,
Shane
Hi, did you ever find a solution to this error? I too am receiving "Error 1: Incorrect function." Thanks for any input.
I do not have any resolution as of yet. I logged a ticket and I was told the account needed access to the SharePoint Configuration database. I granted the rights which support told me and it still fails.
This is the response I received which if you use the farm account it complains in CA for heath rules.
You will need to use the farm service account for the Nintex Workflow Start Service and the Relay Service. This service account will need to be added to the dbcreator, securityadmin and db_owner security roles on the SharePoint content database.
So just a heads up, I just discovered that this issue must have something to do with enabling Nintex Live when installing Nintex. I just did a complete re-install of Nintex Workflows and did not install Nintex Live. In doing so I noticed that this service does not get installed. Not sure if you needed Nintex Live or not but I don't so I just removed it. Hope this helps.
Now I do not see a option not to install Live. Did you install manually each WSP file?
Let me know as I have removed Nintex from our development server at this time for 2016.
What I did was follow these instructions on how to remove Nintex Workflows ( ). Then I ran 'regedit.exe' and searched for any instance of 'Nintex' and deleted it. Once all instances were deleted I restarted the server. Once the server came back up I ran the Nintex Workflow installer and followed the prompts that appear on screen when I got to the page asking if I wanted to install Nintex Live, I unchecked it and continued on with the prompts.
I was then asked if I wanted to add the solutions to SharePoint now and I chose 'Yes'.
Once Nintex installed I noticed that I did not have the 'Nintex Workflow Start Service' listed under 'Services' and workflows seemed to work fine for me. Again, I unchecked install Nintex Live because I did not need it installed. So I do not know if you need it or not I am just letting you know what worked for me.
We are Using SharePoint 2016 which is different than the screen grabs above. We never see the message about not installing
Nintex Live on SharePoint 2016 with the new Installer for SharePoint 2016. Not sure what this service really does since I cannot get a straight answer from Nintex support. I set the service to manual for now as it never starts.
Workflows are working in 2016 fine.