Deployed Nintex WF to all Web applications but only appears under CA site collection admin

[jonathanbordoli]

I just deployed Nintex WF to a SharePoint 2013 farm. No errors in installation. I deployed the solution to all Web apps. Used central admin > Nintex WF management to activate on all Web apps.

The only site settings > site collection features that the Nintex WF item appears under is for central admin site collection (portalca.xxx.com:2222).

None of the other web applications/site settings/site collection features shows it. There are several Web apps all on port 80 so portal.xxx.com, portaldev.xxx.com, portalqa.xxx.com.

The CA as indicated is portalca.xxx.com:2222.

I just logged a support case but the community might have seen this sort of problem before too. 

Thanks,

Jonathan

[praios81]

Missing site collection features indicate that there was a problem while installing the features during installation although no error was yielded during installation.

Did the user that ran the installer have sufficient permissions to install the features on your site collection?

You could try to rerun the installation and see if it works. Otherwise I think it's best to work this out with Nintex support and see where the missing piece is.

Anyway, once you got it working it would be awesome to post the solution here.

best regards

Enrico

[jonathanbordoli]

I tried the installation several times over now and also resorted to the manual install on the WFE. This throws a powershell  error

>> Cannot uninstall the LanguagePack 0 because it is not deployed

This is from the Nintex script NintexWorkflow2013WfeCore.wsp - the offending powershell commandlet is

Update-SPSolution. I can recreate this as the commandlet the script runs comes down to 

> Update-SPSolution -Identity "2f699e2e-23ff-41d1-9a1a-5a32e1f59886" -LiteralPath "C:\Nintex\manuaWFE\NintexWorkflow2013WfeCore.wsp"  -GACDeployment -Force -Local

If I run the ps command get-spsolution it shows it as there but not deployed even though CA says it is deployed!

Get-SPSolution -Identity "NintexWorkflow2013WfeCore.wsp"

Name                           SolutionId                           Deployed   

----                           ----------                           --------   

nintexworkflow2013wfecore.wsp  2f699e2e-23ff-41d1-9a1a-5a32e1f59886 False 

I created a case with Nintex 15th March and despite an initial standard response on the 16th have heard no more. 

[jonathanbordoli · Accepted solution]

Right, after many hours diagnosis I finally got Nintex Workflow installed. The problem was that the Microsoft SharePoint Foundation Web Application service was not running on  the WFE server. I finally spotted this after an exhaustive search. It's status on CA was 'Error starting'.
I think from what I understand from some research is that this services needs to be running to deploy solutions. 

The Microsoft SharePoint Foundation Web Application service is running on the App server.

Why no errors checking in the Nintex installer is beyond me especially as it indicates it has deployed the solution to the APP & WFE server.  

Hope this helps others with diagnosing possible problems.

Still no luck with getting Nintex Forms installed and that has some strange errors too.

What is everyone experience with installation. I installed on one farm last year and there were some hiccups but only if I forgot to do something like map databases. My experience this time around is of almost a day or diagnosing problems.