No Language-Neutral Solution Package

Today’s adventure in SharePoint went wrong in so many ways. We are trying to deploy Infowise into our Production 2016 farm like we have already done in QA. Lets just say the QA deployment went off without a hitch Prd should do the same. That’s not the case the deployment tool hung up for an hour before it failed with the error of Timeout and started to rollback which also hung up for about 45 minutes.

After looking through the Infowise site I follow their steps incase of a time out on my next attempt. This time it fails right off the bat with the error No Language-Neutral solution available. Like really what does this mean we deployed the langue packs when we set up our environments UGH. So begins the fun of trying to find out what this really means and how to fix it. I start by looking in Central Admin at the Farm solutions. You can find this by going to System Setting on the left Navigation, then Manage Farm Solutions under Farm Management. My next step was to go to our main application server and run get-spsolution from PowerShell. In doing this I see the solution it isn’t deployed but instead of saying false under that flag it is just blank. Oh snap I think this is going to be easy so I run remove-spsolution -id “ID of the solution” – force. Whoot this should be easy well guess again folks bam red text error “The language-neutral solution package was not found”.

The hunt is on for what this really is I take to Google to see if there is any trace of this error is and how to fix it. Then I quickly realize like anything else the problem has been seen before but no one updates how to fix the darn thing. Best answer I seen was go to the Config_DB and remove it from there really are you freaking kidding me that’s a no no. The next step through the standard trouble shooting reboot nothing, clear config cache nothing, and last time to open the ticket with Microsoft. Woohoo just like that the issue with the language-neutral solution package not being found is fixed. Microsoft called me back for my ticket and the issue was when it timed out it added the Solution as an object in the solution store but ever set the status this left it in a funky state. To fix this we ran the following commands in PowerShell.

Change the name to the solution you are looking for.

1. Get-SPsolution | select name Lists all the solutions in the farm.

2. Get-SPSolution infowisetrailhelper.wsp Lists the trail helper, ID and Deployment status.

3. $a=Get-SPsolution infowisetrialhelper.wsp $a.GetType() IsPublic IsSerial Name Base Type True False SPSolution Microsoft.SharePoint.Administration.SPPersistedObject

4. $a.Deployed()

5. $a.DeplomentState()

6. $Delete()

7. Then run Get-SPsolution again and the solution is not in the store.

Hopefully this will help some of y’all one day.