Error in SDM-deploy Step

<h5>Good Morning Gentleman,</h5>
<h5>"When i'm trying to import a transport order to our productive system the import fails in step SDM-deploy with the following error:</h5>
<h5>20120228122646 Info   :Starting Step SDM-deploy at 2012-02-28 12:26:46.0143 +0:00
20120228122646 Info   :start deployment of archives:http://sapsps.sonaesierra.com:50004
20120228122646 Fatal :caused by Exception:com.sap.cms.tcs.beans.exception.TCSDeployException_Communication: The user 'j2ee_admin' could not be connected to the specified host 'sapsps.sonaesierra.com'and port '50004'.:The user 'j2ee_admin' could not be connected to the specified host 'sapsps.sonaesierra.com'and port '50004'.
com.sap.cms.tcs.beans.exception.TCSDeployException_Communication: The user 'j2ee_admin' could not be connected to the specified host 'sapsps.sonaesierra.com'and port '50004'.
     at com.sap.cms.tcs.beans.deployer.DeployConnector.openConnection(DeployConnector.java:160)
     at com.sap.cms.tcs.beans.TCSDeployBean.performDirectDeployment(TCSDeployBean.java:194)
     at com.sap.cms.tcs.beans.TCSDeployObjectImpl0_0.performDirectDeployment(TCSDeployObjectImpl0_0.java:1342)
     at com.sap.cms.tcs.beans.TCSDeploy_Stub.performDirectDeployment(TCSDeploy_Stub.java:1296)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:331)
     at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
     at $Proxy225.performDirectDeployment(Unknown Source)
     at com.sap.cms.tcs.core.SDMDeployTask.processImport(SDMDeployTask.java:302)
     at com.sap.cms.tcs.core.SDMDeployTask.process(SDMDeployTask.java:366)
     at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
     at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:206)
     at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:447)
     at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:176)
     at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:500)
     at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:113)
     at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:648)
     at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:620)
     at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0_0.startImport(LocalCmsTransportProxyLocalObjectImpl0_0.java:1640)
     at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1637)
     at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2817)
     at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:1042)
     at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2866)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
     at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:333)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
20120228122646 Info   :Step SDM-deploy ended with result 'fatal error' ,stopping execution at 2012-02-28 12:26:46.0306 +0:00"</h5>
<h5>I'm new to NWDI and related subjects. I've already checked:</h5>
<h5>1. Port 50004 is available in the productive system</h5>
<h5>2. J2EE Visual Administrator in productive is accessible by j2ee_admin</h5>
<h5>3. j2ee_admin isn't locked in productive system</h5>
<h5>What more should i check? What could be the reason behind this error?</h5>
<h5>Thank you.</h5>
<h5>Best Regards,</h5>
<h5>Pedro Gaspar</h5>

Good Morning Kumar,
If i tell you what happened you're going to laugh... But i'll tell you anyway.
After watching your post i went to the CMS Landscape Configurator in order to look into the configuration. I noticed that the Selected Tool for deployment in the Productive Runtime system was configured as Deploy Controller (this is a NW 7.01 and as far as i've read before... in this version it's advisable to configure it as you told me in your post - SDM Deploy, thanks for that).
So i tried to change it, but nothing happened, i've tried a second time, but the changes wouldn't take effect and no message was generated. I've spent a few hours trying to understand what was happening... So i told to myself, let me try it with another browser (was using Firefox 3.6.27, changed to IE 9.0.8112) and when trying to change the runtime system configuration a message outputs... "... More than one name server configured in SLD"
Immediately searched and got SAP note 1118009 - SLD name-server configuration error in CMS. After executing note steps i was able to change the runtime system tool for deployment, and i could finish the transport.
The difference a message and the browser version can do in your life
Thanks for your reply, which helped me solve the problem.
Best Regards,
Pedro Gaspar

Similar Messages

Error occurred in deployment step 'Add Solution': A timeout has occurred while invoking commands in SharePoint host process.

Hi,
I am deplyoing a solution which has custom web parts- vwp- appln pages, event receivers.
It was working fine till last week. I was able to deploy the solution and able to see the web parts and func. was working.
But now from the last 2 days onwards, when I tried to depoy this soution, I am getting the error
"Error occurred in deployment step 'Add Solution': A timeout has occurred while invoking commands in SharePoint host process "
may i know why am getting this error.
note: my dev machine- Win Srvr 2012 - VS 2012- SP 2013 - SP D 2013 was having soem issues with the space in C drive.
once i have done the index reset few months back and i started getting space in C:\ Drive is 0 bytes.
so what my infra. team has done is , increased the space in drive to 150 GB[ it was a VM ].
help is appreciated !

What is current disk space on your drives
Delete ULS logs and other log files from server id not needed
could be related to ChannelOperationTimeout
http://msdn.microsoft.com/en-us/library/ee471440(v=vs.100).aspx
Also, don't forget to restart Visual Studio
Goto the following regustry key: HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0\SharePointTools
Add the following as a DWORD (wont be there by default)
ChannelOperationTimeout
REG_DWORD that specifies the time, in seconds, that Visual Studio waits for a SharePoint command to execute. If the command does not execute in time, a SharePointConnectionException is thrown.
The default is 120 seconds.
http://social.technet.microsoft.com/wiki/contents/articles/21052.como-resolver-o-erro-error-occurred-in-deployment-step-activate-features-a-timeout-has-occurred-while-invoking-commands-in-sharepoint-host-process-pt-br.aspx
If this helped you resolve your issue, please mark it Answered

Error occurred in deployment step 'Activate Features': A timeout has occurred while invoking commands in SharePoint host process.

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 occurred in deployment step 'Add Solution': A feature with ID '' has already been installed in this farm. Use the force attribute to explicitly re-install the feature.

Hi I am getting the error
Error occurred in deployment step 'Add Solution': A feature with ID 10495515-2482-41fd-98eb-3c87f739f54b has already been installed in this farm. Use the force attribute to explicitly re-install the feature.
when trying to deploy web parts
question 1 - how do i use the force attribute when deploying from visual studio
question 2 - am i deplying it to the right place, if i deply it to the
url:port that points to my central admin tool it deploys but i cant seem to see it in any of my webs in my site collection, if i deploy it to the
url:port that points to my site collection I get this error.
im new to all this by the way :)
thanks in advance

If you are deploying from Visual Studio then please follow this post:
http://sharepointfordeveloper.blogspot.com/2014/03/solved-visual-studio-issue-error.html
Open the visual Studio and navigate to the feature XML file and add the bellow attribute.
AlwaysForceInstall="TRUE"
The <FeatureName>.Template.Xml output would be some think link this.
<?xml
version="1.0"
encoding="utf-8"
?><Feature
xmlns="http://schemas.microsoft.com/sharepoint/"
AlwaysForceInstall="TRUE"></Feature>

Error occurred in deployment step 'Uninstall app for SharePoint': The remote server returned an error: (502) Bad Gateway.

Installed SP 2013 Foundation in my Hyper-V machine
Created and done all the steps mentioned here http://blogs.msdn.com/b/shariq/archive/2013/05/07/how-to-set-up-high-trust-apps-for-sharepoint-2013-amp-troubleshooting-tips.aspx && http://msdn.microsoft.com/en-us/library/office/fp179901%28v=office.15%29.aspx
for self signed certificate
copied those two certificates in my local machine(base machine) D drive
(D:\Cert)
Both VM and base machine are in same domain
Installed VS 2013 in my base machine and create a Provided hosted app with the copied certificates, (For creation i followed the above mentioned URL)
Just created and hit F5 to run in my base machine, but getting this error
Error occurred in deployment step 'Uninstall app for SharePoint': The remote server returned an error: (502) Bad Gateway.
Please help me to resolve this issue, trying to figure out from last 2 days
Thanks in Advance
Arun

Hi Harminder,
This happens because an app has already been deployed and you are deploying it again using the same version.
Resolution:
Open the AppManifest.xml file and change the version.
Vivek Jagga - MCTS SharePoint
SharePointExcellence

Deploying simple SharePoint 2013 feature causing error: "Error occurred in deployment step 'Add Solution': An unknown exception occurred while executing a sandboxed code solution request in the worker process."

When trying to deploy a sandboxed solution containing only a feature with a simple associated event receiver from VS 2013, I'm getting the following error:
Error occurred in deployment step 'Add Solution': An unknown exception occurred while executing a sandboxed code solution request in the worker process.\r\n|0
I'm working in Visual Studio 2013, deploying to SharePoint 2013.
The SharePoint project is very basic. I've only added a feature and an associated event receiver. It works without the event receiver. Then after I simply add the event receiver I get the error.
I've tried deploying directly from VS 2013 as well as publishing to a .WSP and uploading via web interface. Same error reported using both methods. I'm doing this using an Administrator account that I've confirmed is a site collection administrator.
Additionally, I've found that if I change Sandboxed Solution to False, deploy it, retract it, then change Sandboxed Solution back to True, then I can successfully deploy it. But this doesn't seem to be a permanent solution as the error will resurface a day
or two later...

Hi Steve,
Are you running your SharePoint 2013 on domain controller?
http://www.learningsharepoint.com/2013/08/09/sharepoint-2013-error-an-unknown-exception-occurred-while-executing-a-sandboxed-code-solution-request-in-the-worker-process-rn0/
http://social.technet.microsoft.com/Forums/sharepoint/en-US/b7408608-c21b-45d9-bc16-e6afff510cd2/installed-sharepoint-2013-foundation-on-window-2010-server-issues-activating-sandbox-solutions?forum=sharepointadmin
My Blog- http://www.sharepoint-journey.com|
If a post answers your question, please click Mark As Answer on that post and Vote as Helpful

"Error occurred in deployment step 'Retract Solution': The solution does not have a WSP file associated with it." occurs while deploying from Visual studio

HI,
I get this error "Error occurred in deployment step 'Retract Solution': The solution does not have a WSP file associated with it. " when deploying my project from visual studio 2010 to
SharePoint 2010 site. I tried restarting IIS, but it didn't help. This application used to work fine until the server crashed during the deployment process. All the other applications on the same server works fine also. Any ideas how to fix this issue?
Thanks in advance,
AM

Hi
AM ,
Thank you for your posting!
According to your error message, it says your solution does not have a WSP file associated with it. Take a look at the file system. After you Right Click -> Deploy Solution on the VS Solution, there
should be a .wsp file at <Solution Directory>\bin\<debug|release>.
Also the error can be occurring when the developer try to deploy solutions over pre-existing solutions with material changed in the solution. Go to your Central Administration Site and then
Operations and then Solution Management. Make sure that there not already a solution with the same name deployed or installed there. If there is, remove it and try deploying again.
And you could look in logs and find if there is a below error in ULS log (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS).
Thank you for your understanding and support.
Best Regards,
Eric
Eric Tao
TechNet Community Support

Error occurred in deployment step 'Add Solution': Attempted to perform an unauthorized operation.

Hello,
I'm new to SharePoint development. I just created a empty sharepoing app in VS2010, added a webpart and in .cs file of this webpart, add hello inside RenderContents. Its compiling fine. but giving following error while deploying
Error occurred in deployment step 'Add Solution': Attempted to perform an unauthorized operation.
My VS 2010 is running under Administrator privileges & I'm admin to this machine.
Comments?

Hi, just had the same problem (on a 2013 enviroment) and was able to solve it partly by this post.
Also experience a problem with dublicate ports, see here: http://technicaltrix.blogspot.dk/2014/11/error-occurred-in-deployment-step-add.html
http://technicaltrix.blogspot.dk/

Sharepoint 2010 - Visual studio 2010 error - Error occurred in deployment step 'Add Solution': Failed to load receiver assembly

Hello,
I get the following error when trying to attach an event reciver ->
Error occurred in deployment step 'Add Solution': Failed to load receiver assembly . The system cannot find the file specified.
This happens only when i try to change the deployment target from "GlobalAssemblyCache" to "WebApplication".
Steps to reproduce->
1. Create a new feature and add an event receiver. Deploy the solution. Everything works fine.(Since deployment target is GlobalAssemblyCache). If you now change the deployment target to "WebApplication" , it works too.
2. Now, restart visual studio. Change Deployment target to "WebApplication" without deploying the solution. And you get the above error.
3. Every time you restart your visual studio with deployment target as "WebApplication", you will receive this error.
Any idea?? Manual deployment of the solution works fine too.
When i go to virutal path bin directory, the dll is missing because of which the error occurs. Dont know why, it doesnt copy the dll to bin?
Thanks in advance,

Hi,
Feature receivers must be deployed in the GAC & cannot be deployed to private bin of the WebApplication.
Link: http://msdn.microsoft.com/en-us/library/ms469501.aspx
HTH !!!
AnjaliCH-MSFT

Error occurred in deployment step 'Add Solution': Failed to load receiver assembly

Guys,
I've created a VS2010 sharepoint project and added a feature event receiver to my site definition. When I try to deploy it show me the error bellow:
Error 1 Error occurred in deployment step 'Add Solution': Failed to load receiver assembly "SiteDefinitionProject2, Version=1.0.0.0, Culture=neutral, PublicKeyToken=a693a58979940483" for feature "SiteDefinitionProject2_Feature1" (ID: 9dce3ed9-5eb0-4bea-b42d-4dad84559a36).:
System.IO.FileNotFoundException: Could not load file or assembly 'SiteDefinitionProject2, Version=1.0.0.0, Culture=neutral, PublicKeyToken=a693a58979940483' or one of its dependencies. The system cannot find the file specified.
File name: 'SiteDefinitionProject2, Version=1.0.0.0, Culture=neutral, PublicKeyToken=a693a58979940483'
   at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
   at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
   at System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
   at System.Reflection.Assembly.Load(String assemblyString)
   at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject()
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
  0 0 SiteDefinitionProject2
9dce3ed9-5eb0-4bea-b42d-4dad84559a36
Someone can hepl!?
André Rentes

I also just encountered this error while trying to deploy my feature from Visual Studio 2010. I found the solution for my situation. Perhaps it may help others as well.
To see if your problem has the same cause as I encountered, open up the 14 hive and go to 14/template/features/<your-project-name_your-feature-name>. In this folder you will find a file Feature.xml. Open it up with notepad. On the second line
you will find the XML node Feature. Scroll to the right untill you see the XML attribute ReceiverClass. This
should show you a namespace, i.e. KoenZomers.MyProject.Branding.Features.Web.BrandingEventReceiver. In my situation it didn't show a namespace, but instead the following: $SharePoint.Type.<some-guid>.FullName$. If this is the same for
you, read on as this might be the solution to your problem. If it does already show a namespace, this probably won't help you.
This problem is caused because of a bug in Visual Studio 2010. It should replace the guid to match the guid found above the class declaration of your event receiver. For example:
[Guid("ff9717e0-05c4-4e7e-9349-3f31d3919b9c")]
public
class
BrandingEventReceiver
: SPFeatureReceiver
Probably because I recreated the event receiver class, it did generate a new Guid tag with a new Guid above my class declaration, but it did not update the feature file to reference this new guid. To do this manually, open up the folder on your development
machine where your Visual Studio project files reside. In it you will find a subfolder named Features. Open it. In that folder you fill find subfolders with the names of your features as given in Visual Studio. Open up the one containing the non functional
event receiver. In that folder you will find a file called <feature-name>.feature. Right click on it and choose Open with. Select to open it with notepad. On the second line you will find the XML node feature. Scroll to the right until you see the XML
attribute receiverClass in the same line. Make sure the value of this XML node is built up using the following syntax: $SharePoint.Type.<guid-from-event-receiver-class-declaration>.FullName$. So in the above example it would be $SharePoint.Type.ff9717e0-05c4-4e7e-9349-3f31d3919b9c.FullName$.
Save the file, close notepad. Close the solution in Visual Studio. Once closed, reopen the solution. Do a deploy of your solution. It should work this time. If you check the feature.xml file in the 14 hive now, it does display a namespace. This
made it work for me.

Error occurred in deployment step 'add solution' value cannot be null Parameter name: g

Hi!
I have a SharePoint Server 2013 with latest updates. Worflow Manager 1.0 installed and configured correctly. The server has a website, site temblate is Reacods Center. This site is default. On the site I created a blank Document library "TestLib"
If I create workflow in SharePoint Designer 2013, workflow works normally. Workflow set Title of element to "MyCustomTitle" and Write to History string "Done!".
If I create Empty Solution in Visual Studio 2013, insert into solution Workflow and make same actions, my solution at deployment step fails with error:
"error occurred in deployment step 'add solution' value cannot be null Parameter name: g"
Please, help me to resolve this problem?
Thanks!

Hi,
What if stop this service, then start it again, perform an iisreset? It will make the change applied to the whole farm.
Also, you can check the ULS logs to see if there is any unexpected error occurs when deploying this solution.
About how to check the ULS logs:
http://blogs.technet.com/b/fesiro/archive/2013/11/11/sharepoint-logging-and-troubleshooting-using-ulsviewer.aspx
Thanks
Patrick Liang
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Error occurred in deployment step 'Add Solution': The definition specifies a claim provider with a name already in use.

Hi,
When i am trying to deploy sharepoint 2010 application in VS 2010, i am getting the below error:
"Error occurred in deployment step 'Add Solution': The definition specifies a claim provider with a name already in use."
How to fix this?
Thank you

You can use:
$provider = Get-SPClaimProvider | where {$_.DisplayName -eq "Provider DisplayName"}
$mgr = Get-SPClaimProviderManager
$mgr.ClaimProviders.Remove($prov)
$mgr.Update()
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Error occurred in deployment step 'Add Solution': Operation is not valid due to the current state of the object

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)

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.vijay

one 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

Error occurred in deployment step 'Activate Features': Attempted to perform an unauthorized operation.

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,
Sachin

Please 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 in SDM-deploy Step

Similar Messages

Maybe you are looking for