Is it possible to deploy a SharePoint WSP without causing an IIS Reset? - iis

I'm working in SharePoint 2010 and have been unable to deploy (or retract) my WSP without causing an IISReset. Here's my situation:
•The solution contains:
•Fields
•One content type
•A page layout based on the content type
•A bunch of images that go into the style library
•There is ZERO code in the solution
•I've manually edited the manifest.xml
•Removed the assembly, so nothing would get deployed to the GAC
•Set ResetWebServer="False" in the Solution tag
Still, every retract or deploy takes down ALL web applications on the server. Is there any way even to restrict it just to one web app? Thanks!
edit: additional info - I'm packaging up the WSP and deploying with powershell commands, but I get the same behavior even if I deploy through Central Admin.

try this in SP Admin console (with credential admin):
stsadm -o addsolution -filename "C:\yourwsp.wsp"
stsadm -o deploysolution -name yourwsp.wsp -url http://yourspsite -allowgacdeployment –immediate
stsadm -o execadmsvcjobs

Related

Receiving error when executing New-SPSite in PowerShell

I have two web applications in SharePoint 2010 that are both empty (and were created the same way through Central Admin). I have a PowerShell script that creates a new site collection and then automates various other tasks after the site collection is created. I can execute my script successfully in the first web application. Then, when executing the same script on the second web application, the following error is rendered:
"The system cannot find the file specified."
After some investigation, I have found that this command was breaking:
New-SPSite -url $newsite -name $newname -template "STS#0"
The specific error is happening because the site template (STS#0) cannot be found. I have also tried creating the site with different templates, but I get the same error. It is acting as if the second web application cannot find any of the site templates.
Thoughts?
Must have been an IIS issue. Rebooted the box and all is well.

How to force uninstall webpart from Sharepoint 2010

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.

Deploying SP2010 custom state machine workflows into a production site

I have a dev environment with VS2010 and SP2010 installed in and a production environment running SP2010. I have created a state machine workflow in VS2010 and deployed to my dev environment for testing. Now that I have things working the way I want I need to deploy the workflow into my production environment.
In VS2010 I have selected "Package" and taken the resulting .wsp file and attempted to deploy them on my production site by going to Site Settings -> Solutions and uploading. I have also activated the solution within the solution gallery and ensured that it is also activated in "Site collection features". However, the workflow does not show up in Site Settings -> Workflows and I can't seem to out what to do. I have also tried deploying the .wsp through stsadm addsolution.
What am I missing when deploying a custom built workflow packaged as a wsp?
Your first method of deploying solution by uploading it to Site Settings -> Solutions applies to only sandboxed solutions. Are you sure yours is a sandboxed solution ?
The second method which you tried is a global method of deployment through stsadm.
I would suggest, start from scratch i.e. clean up your local Solutions gallery. and use stsadm operations addsolution, deploysolution and activatefeature to deploy this workfow.
Note that deploysolution and activatefeature can also be done via UI.

How to deploy RSWebParts.cab manually?

I'm using the SSRS 2005 Web parts to display my reports in a MOSS 2007 SP1 Portal. I have successfully installed the Web parts in my development, testing, and UAT servers using the following command: stsadm -o addwppack -filename path/to/RSWebParts.cab. But when I tried running the same command in the production server, it will give me the following error:
This solution contains no resources scoped for a Web application and cannot be deployed to a particular Web application.
I know I usually will get this kind of error message when I tried to deploy my custom solutions having no Web application resources (such as web.config entries) to a specific Web application. But this is not my custom solution, it is an out-of-the-box SSRS Web part and it does have resources scoped to a Web application.
I tried to even use different combination of the command by providing the -url, -globalinstall, and -force switches but it still give the same error.
The configuration of the 4 servers are exactly the same, both from software and hardware perspectives. All other features are working properly on the production server.
I even tried to extract the cab file manually to the bin folder of my Web application, then modify the Web.config manually to include the SafeControl element (copied from the manifest.xml inside the cab file). But it gave me an error saying it couldn't find the resources file. Even though, I extracted the whole file, including the resource files in the bin folder.
Is there anyone who can help me resolve the problem? Thanks a lot.
I have resolved it with the following command and it worked successfully. Do not add any extra things. The following code copies RSwebparts.cab in C:\ directory.
C:\Program Files\Common Files\Microsoft Shared\web server extensions\14\BIN>
stsadm.exe -o addwppack -filename C:\RSWebParts.cab -globalinstall -force
Cheers & enjoy
Have you tried all possible combinations of the command?
The following combination works well for all of the web part packs we install:
stsadm -o addwppack -filename path/to/RSWebParts.cab -globalinstall -force -url ContentURL

Including Sharepoint /pages/ in Import/Export

My team and I are using multiple virtual machines on our local computers to develop a Sharepoint Site and, as this is really not supported, we are running into problems:
I am attempting to use the in-house import/export features with the following commands:
-- Export --
stsadm.exe -o export -url http://localhost/ -nologfile -haltonwarning -haltonfatalerror -overwrite -filename ClintonAWAS.sharepoint
-- Import --
stsadm.exe -o import -url http://localhost/ -nologfile -haltonwarning -haltonfatalerror -filename CoreyAWAS.sharepoint
Everything seems to have been brought over properly including the DB connections, with the exception of one important detail: the .aspx files in the /pages/ virtual directory. So far, we have had to export/import them manually, file-by-file in designer.
Am I doing something wrong? Is there another way to do this? Can anyone suggest anything? Thanks in advance.
I'd generally avoid doing this sort of site copying between developers - solution package projects with source control works much better - but if you are stuck with this sort of environment you may find the content deployment wizard quite useful.
Another thing to check is if the pages are published - copying a site with pages that have no published version can get you interesting results.

Resources