Some strange issue is popping up while trying to deploy a solution in sharepoint.
Error occurred in deployment step 'Retract Solution': Feature 'GUID' is not activated at this scope.
I am able to build and rebuild, but when trying to deploy, the above shown error is raised.
while trying to retract, the error raised is
Feature 'GUID' is not activated at this scope.
It all happend suddenly.....
It was working perfectly till yesterday!!!....
How do i find out whether the feature with ID is activated? also
How do i activate the feature?
Thanks in advance....
Retract and then install the solution again using 'SharePoint 2010 Management Shell' Install-SPSolution –Identity SharePointProject2.wsp –WebApplication -GACDeployment.
Follow http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/2009/12/02/adding-and-deploying-solutions-with-powershell-in-sharepoint-2010.aspx for proper syntax.
Once it run without error confirm that the required features are activated in the site collection.
Please ensure Features are activated. please follow
Go to site setting.Then select manage site features in site action. Then activate that particular feature
hopes it works .
I had the same issue, the account I was using to deploy from visual studio wasn't a site ower. Once I added the account as site owner, It deployed fine.
Related
I'm trying to deploy a InfoPath form to Sharepoint via Visual Studio, but I'm getting this error:
Error occurred in deployment step ‘Add Solution': The XSN cannot be used on the server.
I’m publishing the form to a network location. Any ideas?
In most cases this error relates to the InfoPath form not being on the network share prior to deploying your solution
So in order to get rid of this error deploy the InfoPath form to your network share. After this replace the form in your Project file with the one from your network share.
Make sure you run an elevated instance of Visual Studio or Powershell (run as Administrator) and then deploy your solution again. The error should not occur again.
I figured it out, the field Access Path in the Publishing Window must be blank, even if InfoPath suggests to keep it as the same as the Publish Path.
Locally the project works perfectly.
It is executing and there are proper entries in database.
But when I am deploying it to cloud at staging it is giving me this error as object reference not set to an instance.
My project requires 2 instances of each web and worker role but since I have a limited edition to free instances I am using only 2. one each. Can that be a problem ?
I am using SDK 1.8
It is ASP.Net project.
Can anyone suggest me how to resolve this issue ?
I had a similar issue where I was getting the following when publishing from Visual Studio 2013 to my Azure Cloud Service with a web role and a worker role. This occurred after upgrading the project from Azure SDK v2.4 to v2.5:
2:41:59 PM - Applying Diagnostics extension.
2:42:01 PM - Object reference not set to an instance of an object.
Even after working with a Microsoft Developer I could not get it to show me any kind of stack trace to indicate where the null was coming from. He just happened to notice something funny in my cloud configuration under the "Roles" folder that looked strange.
The problem was that the diagnostics.wadcfgx is needed for an SDK 2.5 project, whereas before that version the diagnostics.wadcfg is needed. (Note the "x" in the file extension.) Apparently the worker role did not have this file automatically created when the project was upgraded.
In order to fix this particular issue, just right click on the role (in the roles folder under cloud configuration) and select "Add Diagnostic Configuration", then Build the solution and attempt to publish. These diagnostics files are ONLY needed when publishing directly from Visual Studio.
I haved same error today, after upgrading Azure SDK to version 2.5
I'm add configuration diagnostics to each role in service and the error disappeared
Had this with MS Azure Tool 2.9. Turned out that it needed the following in diagnostics.wadcfgx :
<PrivateConfig xmlns="http://schemas.microsoft.com/ServiceHosting/2010/10/DiagnosticsConfiguration">
<StorageAccount endpoint="" />
</PrivateConfig>
Hope it helps someone!
I ran into the same issue when upgrading to 2.5. It created the .wadcfgx files and they looked sensible but deployment via Visual Studio would still fail with the same error.
Applying Diagnostics extension.
Object reference not set to an instance of an object.
Package deployment would still work. I was able to get past it via the following steps.
Delete the generated .wadcfgx files
Have Visual Studio regenerate them via the context menu option on the role.
Doing a clean build and redeploying.
I'd love to know what the actual error was and how to get more details. The messaging is pretty terrible.
I am attempting to migrate to VSO from TFS and receiving the following errors:
I have administrative rights in both VSO and TFS.
Please help me figure out what the problem is.
Thank you!
Here you find answers to your all queries.
Administrative Right(s):
The OpsHub Visual Studio Online Migration Utility requires that the user that is used to create the Visual Studio Online End Point is a member of the Project Collection Administrator Group.
To grant the user that particular right, follow the following link.
http://www.opshub.com/ohrel/Resources/TFS/permissions.php?page=admin
Template Customization:
You are facing template customization error due to you have configured custom field(s) at your source end.
& such field(s) are not exist on your target VSO.
Solution for this is to delete the custom field(s) at your source end & revalidate again to processed further using migration utility. Migration on customized process templates are not supported through free utility.
You can revert customization incase you want to continue your migration with free utility with the help of following article.
http://msdn.microsoft.com/en-us/library/dd236909.aspx
You can use power tools for quick configuration of custom fields
http://visualstudiogallery.msdn.microsoft.com/f017b10c-02b4-4d6d-9845-58a06545627f
Missing Link Type(s) Warning:
You are seeing link type warning because your target VSO instance is not having Affects and Affected by link types. Still you can continue the migration with warning, in this case your Affects & Affected by link type(s) will migrated as “Related” link type.
Alternative solution is to create new project with CMMI template in your target end. This will automatically add the missing Affects & Affected By link type(s) in target VSO. After doing this revalidate again and proceed further without warning. You can remove newly created CMMI project once you are able to see Affects, Affected by link types in you project.
Our Sharepoint 2013 Application failed to install and is stuck in a odd state. I followed the recommended approach for deleting the application using powershell commands on the hosted Sharepoint server, but it doesn't execute properly.
Visual Studio Deployment/Retract Reports:
Skipping the uninstall step because the app for SharePoint is in an invalid state and cannot be uninstalled.
PowerShell Commands
$instances = Get-SPAppInstance -Web http://mysite/sites/collection
$instance = $instances | where {$_.Title -eq 'Application.Title'}
Uninstall-SPAppInstance -Identity $instance
Executing this PS command throws...
The System Account cannot perform this action.
There is no option from the Sharepoint UI to remove the application, and retrying the install also fails. I've tried other user accounts to execute this powershell command (other than the system account), but no dice. I will have to delete the developer site collection if there is no other solution.
I'm faced this problem before on my Office 365 SharePoint Online when deploy SharePoint Hosted App. Then I submit Microsoft Service request and work with MS Technical Support Team on this issue. This problem seem to be something error in SharePoint backend database by itself (I'm not sure to consider it is SharePoint defect).
Did you check the app details installation error report? If you get the message:
"The content database on the server is temporarily unavailable."
Need help: Error 'Install App for SharePoint': An instance of this App already exists at the specified location., I'm quite not understand the answer but there is one comment from Jeremy Thake which seem to be deleted on this thread, he said that:
"…so I actually just restarted the whole environment and when Windows
came back up and I went to the SharePoint Site…the App was gone ;-)"
So here is my advice before you commit to delete your site collection:
Try to deploy your to the another developer site collection and check whether this problem still occur as the same.
Try to increase your app version or change app name/title/id and deploy to the same site collection and check whether this problem still occur as the same to your new app instance.
For SharePoint Server, try to restart IIS/Window Server if you're able to do that. Also install any latest SharePoint Update/CU.
For Office365 - SharePoint and have you have license account, you should submit the service request, if not you should wait about several day and try to remove this app instance again through UI.
Hope you can remove your app and know the root cause exactly.
I have faced this issue some times in on-premises SharePoint.
But for solving this I gave another account (or you can use 1 that you have) shell admin rights.
Note this account CAN'T be marked as a System account on SharePoint!!
Then with this different shell admin account you execute the same script. That always worked for me (I also got some strange installation behavior and needed do remove the app).
I'm trying to delete a webpart in Sharepoint Server 2010 going at
administration->system settings->manage farm solutions..
And the Webpart shows this message "Deployment Status: Error"
I'm trying "retract solution" and seems work, but when I'm trying to re-deploy the webpart I get the message "Error in the implementation step 'Add Solution': Already installed a feature with ID XXX-XXX - XXX in this set of servers. Use the force attribute to re-add the feature explicitly."
How can I absolute delete this webpart?
It sounds like you need to force uninstall the feature. Here is the command you can run from stsadm.
stsadm -o uninstallfeature -id "yourGUID" -force
Once this is done you can redeploy your solution.
I think you are mixing some terminologies here. In the central administration you only have solutions (i.e. WSP files). Inside this solution you might have a webpart or anything else you want to deploy.
You now state that the solution you want to deploy has the status "deployment error" and you are able to retract the solution.
What you didn't state: After retracting the solution, did you delete it? This needs to be done! Try to delete the solution after retracting, then upload it again and try to deploy again.
If you want to force a deletion there are several possibilities, e.g. using Powershell or stsadm.