We are testing an upgrade from 2013 to 2016 SharePoint. One of our WF Content databases was accidentally set to be the WF Config database. We need to remove it but there is no documentation on this.
We retracted Nintex solutions, and removed the database from SQL Server. We cannot now deploy the Nintex solutions. Does anyone have any ideas. We are thinking of uninstalling Nintex entirely and re-installing it. Any ideas would be most appreciated.
Difficult one. If this is a new installation I'd suggest you roll back the whole installations and start over.
If this is not an option I'd suggest you contact Nintex support and check if they can help you. Maybe you can use Nintex' PowerShell component to remap the configuration database but never did this on my own.
We did open a ticket. Apparently, this should do the trick
$farm = Get-SPFarm;
$farm.properties["NW2007ConfigurationDatabase"] = “”; $farm.Update();
...unfortunately, we found other documentation on uninstalling the products, which indicated that
$farm.properties.Remove("NW2007ConfigurationDatabase") would clear the instance. It did, but now we cannot get the NintexWorkflow2016 feature to deploy.
Fools rush in, where angels fear to tread.
I think that only Nintex support can help you with this one. However, once they solved the ticket with you it would surely be helpful for others to post what the final solution to this problem was.
Hope you get that problem fixed quick.