Error_27_Error occurred in deployment step 'Activate Features': Operation is not valid due to the current state of the object.
I created a SharePoint 2013 farm solution project in Visual Studio 2013 (running on the same machine where SharePoint 2013 server is running) with
event receiver. I added web.config at project root level to store connection string (I'm working off external SQL DB) and got the following error during deployement:
Error 27
Error occurred in deployment step 'Activate Features': Operation is not valid due to the current state of the object.
When I commented out the ConfigurationManager.ConnectionStrings["MyConnectionString"].ConnectionString; the error went away. Am I missing something or not supposed to add my own App.config to SharePoint project solution?
Hi,
From your description, you might want to store your connection string in web.config and there is an error during deployment.
It is recommended to store the configuration data of SharePoint solution in either property bags or hierarchical object store.
The links below will provide more information about this:
http://blogs.msdn.com/b/zwsong/archive/2012/03/27/where-should-you-store-your-sharepoint-solution-s-configuration-data.aspx
http://msdn.microsoft.com/en-us/library/ff647766.aspx
Thanks
Patrick Liang
Forum Support
Please remember to mark the replies as answers if they
help and unmark them if they provide no help. If you have feedback for TechNet
Subscriber Support, contact [email protected]
Patrick Liang
TechNet Community Support
Similar Messages
-
I recently copied a solution from one dev box to another. After pushing through a handful of other errors I hit a wall with this one. Any hints as to the human translation would be appreciated. The solution works on the original box. Also if there's
a way to make the Forum Category list on this page smaller but with more items while making the icons and white space bigger, Microsoft would like to know. ThanksHi George Takei,
This is a common error message which is not easy to find the root cause directly.
Here are some general checking steps:
Check to make sure you haven’t change any objects like namespace, class name, that make feature cannot find specified class.
Deactivate the feature on the site, reset IIS, and redeploy the solution.
Kill the vssphost4.exe in Task Manager, to redeploy the feature.
If the issue persists, it would be better to share the solution here to help to do troubleshooting, what’s the solution used for, is it an event receiver, feature, workflow or other type?
Thanks,
Qiao Wei
TechNet Community Support -
hi,
when i was trying to deploy a SP solution from my vs 2012 solution. this error is displayed.
i tried many things like
1) get the wsp and apply power shell cmds to add and deploy, here also it failed:
Add-SPSolution -LiteralPath d:\mywsp.wsp
Install-SPSolution mywsp.wsp -GacDeployment -AllWebApplications -Local
2) restart the timer services and do iisreset and reboot the server. etc .as mentioned in one of the the below blogs:
http://sharepoint1on1.blogspot.in/2014/04/sharepoint-error-occurred-in-deployment.html
http://suehernandez.wordpress.com/2011/03/31/error-occurred-in-deployment-step-activate-features-operation-is-not-valid-due-to-the-current-state-of-the-object/
http://www.dotnetsharepoint.com/2014/04/error-occurred-in-deployment-step-add.html
http://social.msdn.microsoft.com/Forums/en-US/63adde23-03cf-4b65-923e-1219da94a780/error-occurred-in-deployment-step-add-solution-operation-is-not-valid-due-to-the-current-state-of?forum=sharepointdevelopmentprevious
http://www.shakirmajeed.com/error-occurred-in-deployment-step-activate-features-operation-is-not-valid-due-to-the-current-state-of-the-object/
but even after doing all these steps, the error still persists!. and am not deploying into a remote server, the dev env is in a VM, where sp 2013, vs 2012, sql 2012 are installed.
just wanna share one note: there is a isue in my search admin component. index was reset due to some reason. and from that time onwards my search full/incremental crawls were not working!
will this cause an issue in my wsp deployment ? i hope it wont, still asking...
can anyone help me how to resolve this error.because this is a show stopper for me for the last few days!
help is highly appreciated!This issue cause because of feature activation failure while WSP deployment.
when you create a WSP using visual studio, it creates WSP package with default deployment configuration settings.
Please restrict feature activation configuration, this will help you to troubleshoot this issue.
- Click on Project in WSP and press F4, it will open "Project Properties"
- set "Active deployment Configuration" - as "No Activation"
- you can activate this features in required sequence after deployment using Activate-SPFeature
If my contribution helps you, please click Mark As Answer on that post and Vote as Helpful
Thanks, ShankarSingh(MCP) -
Hi,
I'm unable to deploy a custom workflow/ visual web part or anything using Visual Studio.
Here is the Output trace:
------ Build started: Project: TestWorkflow, Configuration: Debug Any CPU ------
TestWorkflow -> E:\Codes\TestWorkflow\TestWorkflow\bin\Debug\TestWorkflow.dll
Successfully created package at: E:\Codes\TestWorkflow\TestWorkflow\bin\Debug\TestWorkflow.wsp
------ Deploy started: Project: TestWorkflow, Configuration: Debug Any CPU ------
Active Deployment Configuration: Default
Run Pre-Deployment Command:
Skipping deployment step because a pre-deployment command is not specified.
Recycle IIS Application Pool:
Recycling IIS application pool 'SharePoint - 1111'...
Retract Solution:
Retracting solution 'Testworkflow.wsp'...
Deleting solution 'Testworkflow.wsp'...
Add Solution:
Adding solution 'TestWorkflow.wsp'...
Deploying solution 'TestWorkflow.wsp'...
Activate Features:
Activating feature 'Feature1' ...
Error occurred in deployment step 'Activate Features': Attempted to perform an unauthorized operation.
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========
Points to be noted:
I have opened the visual studio using the System Account and "Run as Administrator".
I checked the User policy for the particular web app and it has Full read and Full control for the System account
I checked SharePoint administration under services and verified the system account credientials.
Can you please help me solving this.
Thanks,
SachinPlease try giving permissions
pen the SharePoint 2010 Central
Administration.
- Go to Application Management
–> Change site collection administrations
- Select the correct site
collection and type your windows account as the secondary site collection administrator.
- Try deploying now, it should work.
or
You can grante permissions in "SITE ACTIONS > SITE PERMISSIONS"
Ref :http://learnsharepointwithme.blogspot.in/2013/04/error-occurred-in-deployment-step.html
Please remember to click 'Mark as Answer' on the answer if it helps you -
Error occurred in deployment step 'Activate Features'
I have created an Empty SharePoint Project in Visual Studio 2010 and added a Web Part. The scope for my feature is set to "Site".
My "Active deployment configuration" is set to Default. When I click Deploy in the context menu of the project in Visual Studio i receive this output:
------ Build started: Project: SharePointProject1, Configuration: Debug Any CPU ------
SharePointProject1 -> C:\Users\udjeg\Documents\Visual Studio 2010\Projects\SharePointProject1\SharePointProject1\bin\Debug\SharePointProject1.dll
Successfully created package at: C:\Users\udjeg\Documents\Visual Studio 2010\Projects\SharePointProject1\SharePointProject1\bin\Debug\SharePointProject1.wsp
------ Deploy started: Project: SharePointProject1, Configuration: Debug Any CPU ------
Active Deployment Configuration: Default
Run Pre-Deployment Command:
Skipping deployment step because a pre-deployment command is not specified.
Recycle IIS Application Pool:
Recycling IIS application pool 'SharePoint - 80'...
Retract Solution:
Retracting solution 'sharepointproject1.wsp'...
Deleting solution 'sharepointproject1.wsp'...
Add Solution:
Adding solution 'SharePointProject1.wsp'...
Deploying solution 'SharePointProject1.wsp'...
Activate Features:
Activating feature 'Feature2' ...
Error occurred in deployment step 'Activate Features': Feature with Id '7991a8e8-ead6-4e94-8751-1076c3ed78df' is not installed in this farm, and cannot be added to this scope.
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========
The error tells me that my feature doesn't exist.
When I open Solution Management in Central Administration, I can see that the solution is added to the solution store:
Name: sharepointproject1.wsp
Type: Core Solution
Contains Web Application Resource: Yes
Contains Global Assembly: Yes
Contains Code Access Security Policy: No
Deployment Server Type: Front-end Web server
Deployment Status: Not Deployed
Deployed To: None
Last Operation Result: The solution was successfully deployed.
Last Operation Details: DKCPH-MOSSDEV2 : http://dkcph-mossdev2/ : The solution was successfully deployed.
Last Operation Time: 6/1/2010 1:58 PM
The strange thing is that Deployment status is "Not Deployed" but Last Operation Result is "The solution was successfully deployed".
When I check Site Collection Features on http://dkcph-mossdev2 the feature is not there.
If I deploy the solution manually through Central Administration the solution is deployed successfully and everything works.
It seems like there is a difference between deploying with visual studio and manually in Central Administration.
Can someone give me a hint on how to make it work in Visual Studio.
egholmRickee that is exactly what I found as well.
I would suggest scripting out your Solution / Feature deployments using PowerShell as Microsoft has said STSADM is going away. As you can see from my thread I had these same headaches -
http://social.technet.microsoft.com/Forums/en-US/sharepoint2010programming/thread/436a6463-77a7-467a-b9fd-422f5d569211
/* Reference Sohel's Blog - http://ranaictiu-technicalblog.blogspot.com/2010/05/sharepoint-2010-deployment-powershell.html
function WaitForJobToFinish([string]$SolutionFileName)
$JobName = "*solution-deployment*$SolutionFileName*"
$job = Get-SPTimerJob | ?{ $_.Name -like $JobName }
if ($job -eq $null)
Write-Host 'Timer job not found'
else
$JobFullName = $job.Name
Write-Host -NoNewLine "Waiting to finish job $JobFullName"
while ((Get-SPTimerJob $JobFullName) -ne $null)
Write-Host -NoNewLine .
Start-Sleep -Seconds 2
Write-Host "Finished waiting for job.."
#Used only if not launching powershell from SharePoint...
Add-PsSnapin Microsoft.SharePoint.PowerShell
$CurrentDir=$args[0]
#WebApplication Address
#$WebAddress = "http://ocibapp0t117v3:26678"
#Solution Name
$solutionName="Wells Fargo.wsp"
#Palth of solution
$SolutionPath="C:\VsProjects\RBDWebPart\RBDWebPart\bin\Debug" + "\"+$solutionName
Write-Host 'Going to disable feature'
Disable-SPFeature -identity WellsFargo_Feature1 -confirm:$false -url http://ocibapp0t117v3:26678 -force
Write-Host 'Going to uninstall feature'
Uninstall-SPFeature -identity WellsFargo_Feature1 -confirm:$false -force
Write-Host 'Going to uninstall solution'
Uninstall-SPSolution -identity $solutionName -confirm:$false
Write-Host 'Waiting for job to finish'
WaitForJobToFinish
Write-Host 'Going to remove solution'
Remove-SPSolution -identity $solutionName -confirm:$false -force
Write-Host 'Going to add solution'
Add-SPSolution $SolutionPath
Write-Host 'Going to install solution to all web applications'
Install-SPSolution -identity $solutionName -GACDeployment -AllWebApplications
#-WebApplication "SharePoint 2010 - Training"
Write-Host 'Waiting for job to finish'
WaitForJobToFinish
Write-Host 'Going to enable Feature'
Enable-SPFeature -identity WellsFargo_Feature1 -confirm:$false -url http://ocibapp0t117v3:26678
Write-Host 'Feature Installed all work complete'
#Uncomment below if you are not using the Powershell snapin from SharePoint.
Remove-PsSnapin Microsoft.SharePoint.PowerShell
#File: Myscript.ps1
Moojjoo MCP, MCTS
MCP Virtual Business Card
http://www.mmebs.com -
Error 1 Error occurred in deployment step 'Activate Features': A timeout has occurred while invoking commands in SharePoint host process.
0 0 myProjectAssetsLists
am getting the above error when i deploy my farm solution which is actually a "farm solution import package" template.
i am deploying this to a new site collection and once its features are activated this will provision few doc libs and splists in the targeted site.
any help is appreciated.try below link:
http://msdn.microsoft.com/en-us/library/ee471440.aspx
http://sujeetrec.blogspot.in/2013/12/sharepoint-2010-deployment-timing-out.html
Increase the timeout that Visual Studio waits for SharePoint to deploy a feature:
Create: [HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0\SharePointTools] ChannelOperationTimeout DWORD
The value is a timeout in seconds. The default is 120 (2 minutes).
Full details on this switch and others are here:
http://msdn.microsoft.com/en-us/library/ee471440.aspx -
Error occured in deployment step 'Activate Features': Timeout Expired
Hi all,
Today when I deploy SharePoint 2010 application using visual studio I faced the error.
"Error
18
Error occurred in deployment step 'Activate Features': Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections
were in use and max pool size was reached."
How to solve this
s.vijayone of the possible thing is may be their is SQL connection leak in your code.You can trace it using sql profile...check this post for more details:
http://social.technet.microsoft.com/Forums/en-US/7134eb37-621a-4be1-93b2-0f53ac2d912f/error-occurred-in-deployment-step-add-solution-timeout-expired?forum=sharepointgeneralprevious
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog -
Has anyone encountered this error.
I am developing on SP 2010 with VS 2010.
I was following an online tutorial: How to use custom form templates in NewForm.aspx/EditForm.aspx located at:
http://sharepointbox.blogspot.co.at/2010/11/how-to-use-custom-form-templates-in.html
The tutorial was a little lacking on some of the direction, but it included the working source code, and I managed to complete it.
Every time I try to deploy my version I get the error: Error 42 Error occurred in deployment step 'Activate Features': Field type MyCustomField is not installed properly. Go to the list settings page to delete this field.
I have gone through my code line by line and matched it to the working code from the tutorial, so I can only assume that I am missing something in the Procedure to properly deploy.
Any help is greatly Appreciated!It seems that something went wrong with your custom field type installation. Check below line in .xml file of your custom field type and correct it if needed.
<Field Name="FieldTypeClass">DocumentFieldType.DocumentFieldTypeClassName, DocumentFieldType, Version=1.0.0.0, Culture=neutral, PublicKeyToken=379382f3e8928835</Field>
Please recheck respective values of namespace.classname , dllname. and publickeytoken in your code
Thanks. Please mark it as an answer if it helps. -
I cretaed a Visual web part in SP 2013. It needs a SharePoint list. So wrote below code in web part feature receiver. When I deploy the solution I get error says Error occurred in deployment step 'Activate Features': Object reference not set to an instance
of an object. I set ActivateOnDefault="FALSE" and AlwaysForceInstall="TRUE" . Take a look on my feature manifest file.
I cretaed a Visual web part in SP 2013. It needs a SharePoint list. So wrote below code in web part feature receiver. When I deploy the solution I get error says Error occurred in deployment step 'Activate Features': Object reference not set to an instance
of an object. I set ActivateOnDefault="FALSE" and AlwaysForceInstall="TRUE" . Take a look on my feature manifest file.
<Feature xmlns="http://schemas.microsoft.com/sharepoint/" Title="SharePointProject1 Feature1" ActivateOnDefault="FALSE" AlwaysForceInstall="TRUE" Id="8f7163d5-6c65-40d8-9045-8f74192f07d7" ReceiverAssembly="SharePointProject1, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9c2f0c3a8e22f6a0" ReceiverClass="SharePointProject1.Features.Feature1.Feature1EventReceiver" Scope="Site">
<ElementManifests>
<ElementManifest Location="VisualWebPart1\Elements.xml" />
<ElementFile Location="VisualWebPart1\VisualWebPart1.webpart" />
</ElementManifests>
</Feature>
This is my Feature1EventReceiver code.
SPWeb spWeb = properties.Feature.Parent as SPWeb;
SPList laptopList = spWeb.Lists["Laptops"];
if (laptopList != null)
laptopList.Delete();
SPListCollection lists = spWeb.Lists;
lists.Add("Laptops", "The Laptops", SPListTemplateType.GenericList);
laptopList = spWeb.Lists["Laptops"];
laptopList.Fields.Add("Name", SPFieldType.Text, true);
laptopList.Fields.Add("Model", SPFieldType.Text, true);
laptopList.Fields.Add("Image", SPFieldType.URL, false);
I can deploy if I have only below code
SPWeb spWeb = properties.Feature.Parent as SPWeb;hi
features containing webparts must be site scoped, so you must get spweb as bellow:
SPSite spSite = properties.Feature.Parent as SPSite;
SPWeb spWeb = spSite.RootWeb;
yaşamak bir eylemdir -
Hi,
I have develeoped custom timer job using vs 2010 to deploy in sharepoint server.
While I right click on solution explorer and click on deploy then system throws an error "Error occurred in deployment step 'Activate Features': The type initializer for 'TestTimerJob.TestTimerJob' threw an exception."
Please suggest.
Thanks.
Knowledge is power.Debugger is not firing at all. SO not able t do debugging.
Knowledge is power.
Have you tried to set break point on feature activate? If not then set break point on feature activate and try to debug your code line by line.
See this mSDN article to debug timer job:
http://msdn.microsoft.com/en-us/library/ff798310.aspx
http://www.codeproject.com/Articles/70866/Debugging-Custom-SharePoint-Timer-Jobs
Also make sure that:
1. Once you deploy the time job, you need to reset the IIS
2. restart the window timer service from services.msc
Let us know your result
Hemendra: "Yesterday is just a memory,Tomorrow we may never see"
Whenever you see a reply and if you think is helpful, click "Vote As Helpful"! And whenever
you see a reply being an answer to the question of the thread, click "Mark As Answer -
I am trying to create a custom timer job and while deploying it getting the error as:
Error occurred in deployment step 'Activate Features': Object reference not set to an instance of an object.
where am i going wrong?please suggest...
Thanks
Suu30I am not able to get the errors.So attaching the error log files here.Please help
08/21/2012 17:35:03 1 INF Entering function PsconfigUserInterfaceMain.Main
08/21/2012 17:35:03 1 INF Entering function Common.SetCurrentThreadCultureToInstalledCulture
08/21/2012 17:35:03 1 INF Entering function Common.SetThreadCultureToInstalledCulture
08/21/2012 17:35:03 1 INF Current thread culture is English (United States), current thread ui culture is English (United States), installed culture is English (United States)
08/21/2012 17:35:03 1 INF Leaving function Common.SetThreadCultureToInstalledCulture
08/21/2012 17:35:03 1 INF The current ui culture English (United States) is NOT right to left
08/21/2012 17:35:03 1 INF Leaving function Common.SetCurrentThreadCultureToInstalledCulture
08/21/2012 17:35:03 1 INF Creating the psconfig application context
08/21/2012 17:35:03 1 INF Entering function PsconfigApplicationContext.PsconfigApplicationContext
08/21/2012 17:35:03 1 INF Entering function UserInterface.UserInterface
08/21/2012 17:35:03 1 INF Leaving function UserInterface.UserInterface
08/21/2012 17:35:03 1 INF Entering function TaskDriver.TaskDriver
08/21/2012 17:35:03 1 INF Entering function TaskDriver.BuildCommandCollection
08/21/2012 17:35:03 1 INF Entering function CommandCollectionBase.CommandCollectionBase
08/21/2012 17:35:03 1 INF Leaving function CommandCollectionBase.CommandCollectionBase
08/21/2012 17:35:03 1 INF Entering function CommandCollection.CommandCollection
08/21/2012 17:35:03 1 INF Leaving function CommandCollection.CommandCollection
08/21/2012 17:35:03 1 INF Entering function CommandCollectionBase.CommandCollectionBase
08/21/2012 17:35:03 1 INF Leaving function CommandCollectionBase.CommandCollectionBase
08/21/2012 17:35:03 1 INF Creating the APPLICATION bool exposed parameter
08/21/2012 17:35:03 1 INF Leaving function BoolExposedParameter.BoolExposedParameter
08/21/2012 17:35:03 1 INF Entering function BoolInternalParameter.BoolInternalParameter
08/21/2012 17:35:03 1 INF Creating the APPLICATION bool internal parameter
08/21/2012 17:35:03 1 INF Leaving function BoolInternalParameter.BoolInternalParameter
08/21/2012 17:35:03 1 INF Entering function Parameter.Parameter
08/21/2012 17:35:03 1 INF Entering function Parameter.Initialze
08/21/2012 17:35:03 1 INF Leaving function Parameter.Initialze
08/21/2012 17:35:03 1 INF Creating the SINGLESERVER bool exposed parameter
08/21/2012 17:35:03 1 INF Leaving function BoolExposedParameter.BoolExposedParameter
08/21/2012 17:35:03 1 INF Entering function BoolInternalParameter.BoolInternalParameter
08/21/2012 17:35:03 1 INF Creating the SINGLESERVER bool internal parameter
08/21/2012 17:35:03 1 INF Leaving function BoolInternalParameter.BoolInternalParameter
08/21/2012 17:35:03 1 INF Entering function Parameter.Parameter
08/21/2012 17:35:03 1 INF Entering function Parameter.Initialze
08/21/2012 17:35:03 1 INF Leaving function Parameter.Initialze
08/21/2012 17:35:03 1 INF Leaving function Parameter.Parameter
08/21/2012 17:35:03 1 INF Entering function BoolExposedParameter.BoolExposedParameter
08/21/2012 17:35:03 1 INF Creating the V2V_INPLACE_UPGRADE bool exposed parameter
08/21/2012 17:35:03 1 INF Leaving function BoolExposedParameter.BoolExposedParameter
08/21/2012 17:35:03 1 INF Entering function BoolInternalParameter.BoolInternalParameter
08/21/2012 17:35:03 1 INF Creating the V2V_INPLACE_UPGRADE bool internal parameter
08/21/2012 17:35:03 1 INF Leaving function BoolInternalParameter.BoolInternalParameter
08/21/2012 17:35:03 1 INF Entering function Parameter.Parameter
08/21/2012 17:35:03 1 INF Entering function Parameter.Initialze
08/21/2012 17:35:03 1 INF Leaving function Parameter.Initialze
08/21/2012 17:35:03 1 INF Leaving function Parameter.Parameter
08/21/2012 17:35:03 1 INF Entering function BoolExposedParameter.BoolExposedParameter
08/21/2012 17:35:03 1 INF Creating the CLEAN_INSTALL bool exposed parameter
08/21/2012 17:35:03 1 INF Leaving function BoolExposedParameter.BoolExposedParameter
08/21/2012 17:35:03 1 INF Entering function BoolInternalParameter.BoolInternalParameter
08/21/2012 17:35:03 1 INF Creating the CLEAN_INSTALL bool internal parameter
08/21/2012 17:35:03 1 INF Leaving function BoolInternalParameter.BoolInternalParameter
08/21/2012 17:35:03 1 INF Entering function Parameter.Parameter
08/21/2012 17:35:03 1 INF Entering function Parameter.Initialze
08/21/2012 17:35:03 1 INF Leaving function Parameter.Initialze
08/21/2012 17:35:03 1 INF Leaving function Parameter.Parameter
08/21/2012 17:35:03 1 INF Entering function BoolExposedParameter.BoolExposedParameter
08/21/2012 17:35:03 1 INF Creating the B2B_UPGRADE bool exposed parameter
08/21/2012 17:35:03 1 INF Leaving function BoolExposedParameter.BoolExposedParameter
08/21/2012 17:35:03 1 INF Entering function BoolInternalParameter.BoolInternalParameter
08/21/2012 17:35:03 1 INF Creating the B2B_UPGRADE bool internal parameter
08/21/2012 17:35:03 1 INF Leaving function BoolInternalParameter.BoolInternalParameter
08/21/2012 17:35:03 1 INF Entering function Parameter.Parameter
08/21/2012 17:35:03 1 INF Entering function Parameter.Initialze
08/21/2012 17:35:03 1 INF Leaving function Parameter.Initialze
08/21/2012 17:35:03 1 INF Leaving function Parameter.Parameter
08/21/2012 17:35:03 1 INF Entering function BoolExposedParameter.BoolExposedParameter
08/21/2012 17:35:03 1 INF Creating the SKU2SKU_UPGRADE bool exposed parameter
08/21/2012 17:35:03 1 INF Leaving function BoolExposedParameter.BoolExposedParameter
08/21/2012 17:35:03 1 INF Entering function BoolInternalParameter.BoolInternalParameter
08/21/2012 17:35:03 1 INF Creating the SKU2SKU_UPGRADE bool internal parameter
08/21/2012 17:35:03 1 INF Leaving function BoolInternalParameter.BoolInternalParameter
08/21/2012 17:35:03 1 INF Entering function Parameter.Parameter
08/21/2012 17:35:03 1 INF Entering function Parameter.Initialze
08/21/2012 17:35:03 1 INF Leaving function Parameter.Initialze
08/21/2012 17:35:03 1 INF Leaving function Parameter.Parameter
08/21/2012 17:35:03 1 INF Entering function BoolExposedParameter.BoolExposedParameter
08/21/2012 17:35:03 1 INF Creating the runningupgrade bool exposed parameter
08/21/2012 17:35:03 1 INF Leaving function BoolExposedParameter.BoolExposedParameter
08/21/2012 17:35:03 1 INF Entering function BoolInternalParameter.BoolInternalParameter
08/21/2012 17:35:03 1 INF Creating the runningupgrade bool internal parameter
08/21/2012 17:35:03 1 INF Leaving function BoolInternalParameter.BoolInternalParameter
08/21/2012 17:35:03 1 INF Entering function Parameter.Parameter
08/21/2012 17:35:03 1 INF Entering function Parameter.Initialze
08/21/2012 17:35:03 1 INF Leaving function Parameter.Initialze
08/21/2012 17:35:03 1 INF Leaving function Parameter.Parameter
08/21/2012 17:35:03 1 INF Entering function BoolExposedParameter.BoolExposedParameter
08/21/2012 17:35:03 1 INF Creating the LanguagePackInstalled bool exposed parameter
08/21/2012 17:35:03 1 INF Leaving function BoolExposedParameter.BoolExposedParameter
08/21/2012 17:35:03 1 INF Entering function BoolInternalParameter.BoolInternalParameter
08/21/2012 17:35:03 1 INF Creating the LanguagePackInstalled bool internal parameter
08/21/2012 17:35:03 1 INF Leaving function BoolInternalParameter.BoolInternalParameter
08/21/2012 17:35:03 1 INF Entering function Parameter.Parameter -
Error occurred in deployment step 'Activate Features': Feature 'e3d788e6-994d-446c-afbb-25ecf9907aeb' is Site-scoped, and cannot be added to the Web.
========== Build: 1 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========
Hi,
I have added a new eb part in my already existing SP solution. but when I added 2 new web parts into this solution and trying to depoy the same, am getting this error.
can anybody pls help what am missing.
the below is my feature manifest:
<Feature xmlns="http://schemas.microsoft.com/sharepoint/" Title="BApprove_Feature" Id="e3d788e6-994d-446c-afbb-25ecf9907aeb" Scope="Site"></Feature>
<?xml version="1.0" encoding="utf-8"?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/" >
<Module Name="BApprove" List="113" Url="_catalogs/wp">
<File Path="BApprove\BApprove.webpart" Url="BApprove.webpart" Type="GhostableInLibrary" >
<Property Name="Group" Value="Custom" />
</File>
</Module>
</Elements>Hi SamolPP,
Did you already have a look at following similar post?
https://social.technet.microsoft.com/Forums/sharepoint/en-US/a2af97c8-62db-4194-9fc5-cce6bc7e5d71/content-deployment-error-feature-is-site-scoped-and-cannot-be-added-to-the-web
Hope this helps -
Hi All,
While building event handler to call webservice facing "Error occurred in deployment step 'Activate Features':EXCEPTION HAS BEEN THROWN BY THE TARGET OF AN INVOCATION"; If comment webservice, then build successfully. How to fix this issue?
Thanks in advance!hi
if you call WCF service in feature event receiver you need to ensure that proxy is properly configured. In most cases proxy is configured via web.config file using <system.serviceModel> section, but if it is used in feature receiver it depends on how
you activate the feature:
1. if feature is added to onet.xml of custom web template which is used for creating site collection from Central Administration you will need to modify web.config file of CA
2. similar to previous but instead of site collection you try to create sub site using custom web template: in this case you will need to modify web.config of your Sharepoint web application
3. if you activate feature from timer job somehow, you will need to modify owstimer.exe.config
4. if you activate feature form powershell, most probably you will need to modify or create powershell.exe.config, but I didn't try it
The most simple way which will work in all cases is to configure WCF proxy programmatically. See the following forum thread for details:
How can I set an HTTP Proxy (WebProxy) on a WCF client-side Service proxy.
Blog - http://sadomovalex.blogspot.com
Dynamic CAML queries via C# - http://camlex.codeplex.com -
Really frustrated!!! Using SP 2010 with VS 2010. Created a simple project with just 1 elements.xml file for adding 2 columns. Scope of the feature is "Site". When I right click and deploy it gives below error.
Error occurred in deployment step 'Activate Features': Feature with Id 'GUID' is not installed in this farm, and cannot be added to this scope.
If I look at the CA, I see the wsp is installed but NOT deployed (Status = "Not Deployed", "Deployed To" = None). I have checked the GUID in the error and its my feature id.
Please let me know what is going wrong here! Thanks for your help.
Please mark as 'Propose as Answer' or 'Vote' as appropriate.Hi Sagir,
Try to check the GUID in error message to see if it’s in Feature1.Template.xml file.
For more information, please refer to
http://markviky.blogspot.com/2010/09/error-while-activating-feature.html
http://alltoft.wordpress.com/2011/06/13/sp2010-error-occurred-in-deployment-step-activate-features/
Best Regards.
Kelly Chen
TechNet Community Support -
Hi All,
When I'm deploying my project it showing above error. In my project I have created site columns, content type, List (by using vs 2013) and now my basic target is that i want to change newForm.aspx page to my new application page. For that I have tried to
change the path of newform.aspx in schema.xml page.
I have changed to.
<Form Type="NewForm" url="NewForm.aspx" SetupPath="Features\$SharePoint.Feature.DeploymentPath$\DList\ApplicationPage1.aspx" WebPartZoneID="Main"/>
My project solution is look like..
It seems all files and configurations are fine. I couldn't find any wrong.
and I'm deploying it into sharepoint 2013. why I'm choosing this vs list forms customization is that I need to use ajax controls in my list newForm.aspx.
Any solutions please..
Thank you in advance.Hi,
Please follow the steps below:
1. With "drag & drop" Move the ApplicationPage1.aspx to your List Definition and remove the "Layouts" folder.
2. Select "ApplicationPage1.aspx" in the Solution Explorer and change its property "DeploymentType" to "ElementFile".
3. Modify the page code:
ApplicationPage1.aspx file:
<%@ Assembly Name="$SharePoint.Project.AssemblyFullName$" %>
<%@ Import Namespace="Microsoft.SharePoint.ApplicationPages" %>
<%@ Register Tagprefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register Tagprefix="Utilities" Namespace="Microsoft.SharePoint.Utilities" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register Tagprefix="asp" Namespace="System.Web.UI" Assembly="System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" %>
<%@ Import Namespace="Microsoft.SharePoint" %>
<%@ Assembly Name="Microsoft.Web.CommandUI, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="ApplicationPage1.aspx.cs" Inherits="DList.Layouts.DList.ApplicationPage1" MasterPageFile="~masterurl/default.master" %>
<asp:Content ID="Main" ContentPlaceHolderID="PlaceHolderMain" runat="server">
<h1>Hello World!</h1>
</asp:Content>
ApplicationPage1.aspx.cs file:
using System;
using Microsoft.SharePoint;
using Microsoft.SharePoint.WebControls;
using Microsoft.SharePoint.WebPartPages;
namespace DList.Layouts.DList
public partial class ApplicationPage1 : WebPartPage
protected void Page_Load(object sender, EventArgs e)
4. In the Solution Explorer open “schema.xml” of your list definition, replace the "SetupPath"attribute of the Form node with type "NewForm"with this value:
<Form Type="NewForm" Url="NewForm.aspx" SetupPath="features\$SharePoint.Feature.DeploymentPath$\DList1\ApplicationPage1.aspx" WebPartZoneID="Main" />
5. Deploy the solution.
Best Regards
Dennis Guo
TechNet Community Support
Maybe you are looking for
-
Image viewed in Photoshop CC looks different when viewed in Elements 11 Organizer, why?
I'm viewing a Nikon raw file (.nef) in Bridge CC, Camera Raw, and then in Photoshop CC. In Camera Raw I've made some adjustments before viewing it in Photoshop. For cataloging I prefer to use Photoshop Elements 11 Organizer (there are several reaso
-
I transferred my itunes library using all the guided steps promepted on this topic, when I restarted iTunes in its new location on my xternal hard drive, iTunes did not have any of my ratings or playlists. I did have the hard drive running before i
-
Problems with Notes on my iphone
I love the Notes "app" that comes default with the iphone. However, I've been having problems with it, now that I use it a lot and am able to observe the smaller details. I see that there are two forms of Notes, those linked to my email and those "on
-
Problem in using sybase drivers with JDK 1.5
hi all, i have an app that is connecting to a sybase database. so far i have run it using jdk 1.4 using sybase jconn2.jar , it has workedf ine. Now, i haven't changed the code, i just recompiled it and re-run it using jdk 1.5 , and suddenly i am gett
-
Hi We have requirement that bank address from Bank application (ESS) should not get updated in info type 9. The reason behind this is country and region is taken from info type 6 by default. When user updates main bank details from portal, then bank