I continue to get this error message "Cannot uninstall Language Pack 0 because it is not deployed" when running the uninstall-spsolution cmdlet. I've attempted a number of alternate syntaxes to no avail. (tried add -language 1033 for example) I see a few other similar issues on the web, but nothing specifically addressing my issue. I know the solution exists. not sure why the Language Pack issue is arising. (by the way...i can see my solution using Sharepoint manager 2010). I've tried a number of anyway, any help would be appreciated. thanks.
(Note: was unable to upload image of error from powershell command shell due to site restriction).
I'm also seeing this error in one of our farms when I run the Update-SPSolution commandlet. Recently, we updated the farm with foundation and server Service Pack 1, the associated server language packs and the June Cumulative update. By chance, is this the patch level of your farm? Interestingly, I have no trouble running Update-SPSolution in another farm patched to the same level. The bottom-line is that I don't think this is limited to Uninstall-SPSolution or Update-SPSolution.
I just resolved the issue by doing the following:
Checked the solution store and saw that the solution I was updating was not deployed
I attempted to deploy the solution and saw that it was stuck in the deployment stage
From services.msc I stopped and restarted the SharePoint 2010 Timer service and the SharePoint 2010 Administration service. I don't normally stop and start SharePoint services from Services, but that seemed to do the trick. I also don't know whether it's necessary to recycle both of these services.
I then returned to the command line and was able to successfully update the solution.
Please let me know if this works for you.
While I like the answer above and I think it would work some of the time, in my case I had to remove the Errored out WSP from the solution store and then re-add it and then install/deploy it again. After that my updates were working fine again.
I had the same issue, I opened the manage solutions in central admin and there was an error message next to my solution. The error message was actually helpful, it directed me to solve the issue. I have added -force while installing the solution using power shell command then it worked fine.
After that I deactivated and reactivated the feature just in case.
I've got the same problem and restarting the services was not enough for me.
Then, I solved doing:
Retract and then Remove of the wsp from: Central Administration–>System Settings–> Manage farm solutions.
Then, from Powershell, I have canceled the Features with null scope (which were preventing me to install again the package succesfully):
Get-SPFeature | ? { $_.Scope -eq $null }
$feature = Get-SPFeature | ? { $_.Scope -eq $null }
$feature.Delete()
And at the end I have installed again the wsp:
Add-SPSolution -LiteralPath Path
Install-SPSolution -Identity Name.wsp -WebApplication WebApplicationPath –GACDeployment
Then it worked :)
Update: I've just got this problem again, but this time there weren't features with null scope, so it has been enough just to add -Force while installing the wsp.
I had the same issue and after redeploying solution it's gone.
Related
Trying to deploy some software that uses AppFabric in IIS. Yes, I already know AppFabric is deprecated; I didn't architect this software, so don't look at me! I also have the CU7 update for AppFabric installed.
I'm on Windows Server 2016 with IIS 10. No matter what I click on involving AppFabric in IIS, I get an error: The method or operation is not implemented.
Opening up the Event logs, I see that the method in question is a PowerShell commandlet: error running cmdlet 'out-lineoutput'. The method or operation is not implemented.
Out-LineOutput allegedly was introduced in PowerShell 5, and I've read that it only exists in regular PowerShell (not ISE). Beyond that, I haven't found any reference to that commandlet in regards to AppFabric.
What's driving me extra nuts is that I have a sandbox machine, also running Server 2016, where everything is working OK. I have confirmed that:
the PSModulePath environment variable is the same on both; and
running Get-Module at a Powershell prompt shows the same modules installed on both.
I've tried uninstalling/reinstalling AppFabric and the CU7 patch, adding my Application Pool Identity(ies) to the AS_Administrators group . . . nothing is working. Help me, Stack Overflow!
It turned out this was due to a registry key entry setting logging. In regedit, go to
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\PowerShell\Transcription
Check out the EnableTranscripting property. If this is a 1, change it to a 0.
I have been working diligently to get Dynamics Installed on Azure, I have made it a good way through the Example-1VM.ps1 before encountering a failure to 'Install-AzureWinRMCertificate' error message indicating access denied. The error is coming while running the PowerShell script 'New-NAVAdminSession.ps1' I can see from looking in Azure, much of the work has been done properly from the Example-1VM.ps1 file, but I'm not sure what is next, Can I manually install the certificate and if so may I know how? If not, how do I correct this so I can re-run the Example-1VM.ps1 script.
Thanks to Walter slapping me upside the head (kindly of course) to double check if I was running PowerShell ISE as Administrator I was able to get this resolved.
Once I exited PowerShell ISE and re-entered the desktop application with the option 'run as Administrator' all worked fine.
Just goes to show sometimes we are too close to our own problems.
Cheers Walter
According to your error log, it seems a permission issue. Please close your PowerShell and run PowerShell Run as Administrator.
I have recently followed the steps of upgrading Service Bus 1.0 to Service Bus 1.1. I am at the step were I am using PowerShell to run "Invoke-SBFarmUpgrade" and the commandlet is failing with:
Invoke-SBFarmUpgrade : Upgrade encountered an exception in upgrade_GatewayDatabase_2.13.0.0_1.7.81.0: Online index operations can only be
performed in Enterprise edition of SQL Server.
I don't see an option in the common parameters to be able to set the rebuild option to offline. How can I get over this hurdle?
If this isn't possible, can I create a new Service Bus Farm using the configuration wizard and reattach the Workflow manager to the new farm?
Any help would be appreciated. I'm stuck
Open C:\Program Files\Service Bus\1.1\CommonGatewayStoreUpgrade.sql and replace ONLINE = ON with ONLINE = OFF.
Now you can run Invoke-SBFarmUpgrade and it will work.
(It's probably a good idea to undo your changes to the *.sql script afterwards)
In my installer I have a component that installs an NT service. I have a problem that during minor upgrade the service is not stopped. I observed the log generate by installshield during upgrade and it reports it is doing the action StopServices and its return code is 1. I have also started process hacker to log for services start/stop events but the service is never stopped during upgrade. I have also verified that during uninstall the service in stopped and then removed. Any idea why this is happening?
I am using installshield 2008, but any installshield related answer will be really helpful.
Eventually I was not able to overcome this issue. Spent several days trying to figure out what exactly is going on and was not able to figure out why the service is neither stopped nor started during minor upgrade. I was forced to write custom actions that perform this operations and used sc.exe for them. This is not the first unsolvable issue in installshield that I was forced to fix with a custom action. Hope this answer will save several days to someone.
It can be done by install script and a custom action that executes it.
An example for stopping/starting a service (i used it in IS2016):
#include "ifx.h"
//Function to stop the service
export prototype stopService(HWND);
function stopService(hMSI)
begin
ServiceStopService ( "my service name" );
end;
//Function to start the service
export prototype startService(HWND);
function startService(hMSI)
begin
ServiceStartService ( "my service name" ,"");
end;
In order to run the custom action during minor upgrade only, set its condition to:
REINSTALLMODE=vomus
I have a PowerShell script that deploys about 12 web parts. They have all been created in the manner through visual studio 2010 and are being deployed to SharePoint 2010.
I am getting the following error when running Install-SPSolution for one of my web parts:
Install-SPSolution : This solution contains no resources scoped for a Web application and cannot be deployed to a particular Web application.
Can someone help me debug this? Every other Install-SPSolution command uses -AllWebApplications, and I do not want to specify the web application directly using -URL. Here is the command that is breaking (this is the same command used to successfully deploy all 11 other web parts):
Install-SPSolution –Identity PortalSelector.wsp -AllWebApplications -GACDeployment
Wow, this is old. You're probably a PS guru by now.
For the archives / next visitor give the following a try:
Install-SPSolution –Identity PortalSelector.wsp -GACDeployment
or
Install-SPSolution –Identity PortalSelector.wsp -GACDeployment -Confirm:$false
The latter prevents the confirmation dialog from popping up.
Event i found the same issue when im started working on sharepoint 2010. This is the solution i found and sharing it may helps to others
http://programming.cmsstores.com/this-solution-contains-no-resources-scoped-for-a-web-application-sharepoint-wsp-exception/