Saturday, February 26, 2011

How to Delete Unused (Orphaned) Service Application App Pool in SharePoint 2010

When you delete the Service applications, their Application Pools will not get deleted - They'll become orphan/unused. So later when you create a new service application with same application pool, SharePoint will throw an error message: Application pool is already in use!

"An object of the type Microsoft.SharePoint.Administration.SPIisWebServiceApplicationPool named "Excel Service Application Pool" already exists under the parent Microsoft.SharePoint.Administration.SPIisWebServiceSettings named "SharePoint Web Services". Rename your object or delete the existing object."how to delete application pools in sharepoint

In another case: An application pool already exists with the name specified
how to delete service application pool sharepoint 2010

So, How to delete the unused application pool? From IIS? Nope. IIS will not provide the interface for managing service application's application pools. But we can delete service application's application pool in SharePoint 2010 using powershell.

Use these below cmd-let to get list of service application's application pools.
Get-SPServiceApplicationPool

SharePoint 2010 delete orphaned application pool: To delete a application pool of service application, use the cmdlet:
Remove-SPServiceApplicationPool

E.g. Remove-SPServiceApplicationPool -Identity <Orphaned Application Pool Name> 
How to Delete Unused Service Application App Pool in SharePoint 2010
Or the One liner could be: Get-SPServiceApplicationPool -Identity "name of the app pool" | Remove-SPServiceApplicationPool

You might also like:
SharePoint Usage Reports
Usage reports, collaboration and audit for SharePoint.
Document SharePoint Farm
Automatically generate SharePoint documentation.
*Sponsored


Upload Multiple Documents, Explorer Views Disabled or Missing in SharePoint?

Found Upload multiple documents and Explorer views are disabled (in some cases, they are missing!) in a SharePoint 2010 site!
upload multiple documents, explorer view disabled or missing in SharePoint 2010

Here are the possible causes and solutions for upload multiple documents, explorer view disabled or missing in SharePoint 2010:
  1.  As of now, This feature is available only in IE 32 bit. (Not in 64-bit internet explorer, Google chrome, Firefox)
  2. Try adding the site in Trusted sites' list in IE
  3. Check whether You have not enable "Client Integration" in SharePoint
  4. IE security setting may blocked the STSSYNC ActiveX add on - Enable it from "Manage Addons" in IE (check for STSUpld UploadCtl Class.
  5. This feature depends on Ms-Office, Check whether you have Office installed on the client. If you have it installed, Try running the office diagnostics or even try re-installing office
  6. Disable the IE ESC if enabled!
  7. Check the path of the folder in which you are trying to upload. It should not exceed the 256 character limit.


You might also like:
SharePoint Usage Reports
Usage reports, collaboration and audit for SharePoint.
Document SharePoint Farm
Automatically generate SharePoint documentation.
*Sponsored


Monday, February 21, 2011

SharePoint 2010, MOSS 2007 CSS Reference Charts



You might also like:
SharePoint Usage Reports
Usage reports, collaboration and audit for SharePoint.
Document SharePoint Farm
Automatically generate SharePoint documentation.
*Sponsored


SharePoint Link list: Open in a New Window

In SharePoint, We can put any URLs in the Links list. Unfortunately, when clicking these links, the default behavior is for the page to open in the current browser window. That is, it does NOT open the page in a new instance of the browser. Often this is annoying, isn't it?

How to open SharePoint link list item in a new window? Well, There are many ways to solve this issue:

1. Simplest solution is, Enable publishing feature, Create a site column of "Hyperlink with formatting and constraints for publishing" type, Add this Site column in your new list. Now you will get an option to open in new window! Here is how:

Step 1: Create a Site column of type "Hyperlink with formatting and constraints for publishing"
(Site Actions >> Site settings >> Site columns >> Create )

Step 2: Add this Site column in your new list
(List Settings >>Add from Existing)

Now, You will get a option to specify whether it should open in New window.
sharepoint link list open in a new window

This can be used in SharePoint 2010 links list open link in new window and in SharePoint 2007 also.

2. You can use SPD to convert the link list to XSLT Data view and get in to the code, find the tag <A href> and add an attribute target="_blank".

3. You can edit the Schema file for the link list items to open in new window. Here is how:
  • Open the schema file for the links list feature.  usuall, it located at: C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES\LinksList\Links\schema.xml
In this file there should be two instances of the following:
 < Column Name ="URL" HTMLEncode ="TRUE" />< HTML ><! [CDATA[" > ]] ></ HTML >

Replace them both with this:
< Column Name ="URL" HTMLEncode ="TRUE" />< HTML ><! [CDATA[" target="_blank" > ]] ></ HTML >

  • Then do the IISReset, and now all the links in your links lists will open a new browser window!
4.  You can use jQuery to modify all links attribute, so that all links in SharePoint site, will open in new window.
<script src="http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js" type="text/javascript">
$('a[href$="/"]').attr("target", "_blank");
</script>

5. You can Make Selected Links in a Links List Open in a New Window with Little JavaScript and content editor web part. Here is how:
  • when creating links in the Links List, add #openinnewwindow on the end of each link that you would like to open in a new window.
  • Add the content editor webpart, and place the following code in it:
<script language="JavaScript">
_spBodyOnLoadFunctionNames.push("PrepareLinks");

function PrepareLinks()
{
  //create an array to store all the anchor elements in the page 
   var anchors = document.getElementsByTagName("a");
  //loop through the array
  
  for (var x=0; x<anchors.length; x++) 
   {
      //does this anchor element contain #openinnewwindow?
       if (anchors[x].outerHTML.indexOf('#openinnewwindow')>0)
        {
           //store the HTML for this anchor element
           oldText = anchors[x].outerHTML;
           //rewrite the URL to remove our test text and add a target instead
           newText = oldText.replace(/#openinnewwindow/,'" target="_blank');
           //write the HTML back to the browser
           anchors[x].outerHTML = newText;
         }
     }
 }
</script>

If you want all of your external links to open in the new window you can make use of the below code:
<script>
 
var thisDomain = window.location.hostname;
var theLinks = document.links;
 
 for (i=0; i < theLinks.length; i++)
   {
    var thisLink = theLinks(i);
   if (thisLink.href.indexOf(thisDomain) == -1 && thisLink.href.indexOf("javascript") == -1)
     {
       thisLink.target = "_blank";
      //alert(thisLink);
     }
   }
</script>

Or You can use the jQuery Equivalent to make SharePoint 2010 link list open in a new window:
<script src="http://code.jquery.com/jquery-1.8.0.min.js"></script>

<script>
$(function() {
     $('a').filter(function() {
          return this.hostname && this.hostname !== location.hostname;
          }).attr('target','_blank');
});
</script>

Similarly, To open SharePoint Top Navigation Links in a New window, Refer: SharePoint Top Navigation Link: Open in New Window

You might also like:
SharePoint Usage Reports
Usage reports, collaboration and audit for SharePoint.
Document SharePoint Farm
Automatically generate SharePoint documentation.
*Sponsored


Saturday, February 19, 2011

404 Page Not Found Error After Migrating from MOSS 2007 to SharePoint 2010

After migrating from MOSS 2007 to SharePoint 2010, All the Sub-sites scolded me with: 404 Page Not Found error! But still able to get into the inner pages/document/site settings.

Common causes for HTTP 404 Not Found issue: 
  • Verify the Host header in IIS and make sure its valid.
  • Managed Path which were present in old environment may not be there in New Environment.
  • Alternate access mapping - Make sure you have the Alternate access mapping set correctly and you are accessing using the right alternate access mapping, access your site with FQDN. If you are accessing the site using IP address, then update your DNS Entry/HOST file
But in this case, all above things were set to right. Looked at the event viewer, Logs files but could not figure out the cause of this problem.
sharepoint 2010 migration 404 error

Verified Welcome page settings, Confirmed that the Default.aspx exists in the site by Opening site in  SharePoint Designer. sharepoint 2010 migration 404
After scratching the head and with little trial and error figured out the solution: Check-out "Default.aspx" file and check-in back!!!

Wrote a Powershell script to do Check-out and Check-in. In my case, I wanted to apply this fix for all sub-sites, So the code goes like:
$SPsite = Get-SPSite <SITE-COLLECTION-URL>
foreach ($SPweb in $SPsite.AllWebs) 

{
   $SPFile = $SPWeb.GetFile("default.aspx");
    $SPFile.CheckOut("Online",$null);
    $SPFile.CheckIn(1);
    $SPweb.Dispose()
}
$SPsite.Dispose()

Another nifty Check-out, Check-in scripts:
http://sharepointandpowershell.com/wp-content/uploads/Invoke-SPFileCheckin.txt
http://sharepointandpowershell.com/wp-content/uploads/Invoke-SPFileCheckout.txt

You might also like:
SharePoint Usage Reports
Usage reports, collaboration and audit for SharePoint.
Document SharePoint Farm
Automatically generate SharePoint documentation.
*Sponsored


SharePoint 2010 InfoPath Form Error: The form cannot be rendered. This may be due to a misconfiguration of the Microsoft SharePoint Server State Service. For more information, contact your server administrator.

You may receive this error when trying to publish a InfoPath Form in SharePoint 2010:
"The form cannot be rendered. This may be due to a misconfiguration of the Microsoft SharePoint Server State Service. For more information, contact your server administrator."
The form cannot be rendered. This may be due to a misconfiguration of the Microsoft SharePoint Server State Service. For more information, contact your server administrator.
 Resolution: You need to install the ‘State Service’. Open the PowerShell for SharePoint, Run the below cmd-lets:

1. Create Session State service application:
$serviceApp = New-SPStateServiceApplication -Name "State Service"

2. Create a State Service database and associate it with a service application
New-SPStateServiceDatabase -Name "SP2010_State_Service" -ServiceApplication $serviceApp

3. Create a State Service Application Proxy and associate it with the service application
New-SPStateServiceApplicationProxy -Name "State Service" -ServiceApplication $serviceApp -DefaultProxyGroup

Other settings to verify:
  • Verify that the State Service Service Application is enabled: Go to "Application Management" >> "Manage service applications", Check whether the "State Service" is enabled. 
  • Verify that your web Application is associated with the State Service Service Application: In "Central Administration", Go to "Application Management" and select the "Configure service application associations" in "Service Applications" section.


You might also like:
SharePoint Usage Reports
Usage reports, collaboration and audit for SharePoint.
Document SharePoint Farm
Automatically generate SharePoint documentation.
*Sponsored


Sunday, February 13, 2011

Resize the Oracle Virtual Box VDI image

I was trying to setup a virtual environment for SharePoint 2010 in my 64 bit lap top running windows XP. So I downloaded the Oracle virtual Box,  created 20 GB image, installed windows server 2008, SQL Server 2008 and other things needed by SharePoint 2010. Finally i installed SharePoint 2010 on the virtual box.

Ah.. Here is the Big mistake I have committed. you know what? I allotted only 20 GB for the virtual box HDD image(VDI). I could not extend my hard disk. Now i'm running out of space..

So, Now I need additional space in my Virtual HDD badly. I tried many tools, like Norton ghost to back up and restore to a newly created image with 40 GB. but nothing worked for me.
Resize the Oracle Virtual Box VDI image

























Finally, I solved the issue.
1. Create a new image, say for eg. SharePoint2010.vdi with 40 GB space.
2. Now go to: C:\Program Files\Oracle\VirtualBox, and execute the below command.
VBoxManage clonehd --existing "D:\VirtualBox\Windows 2008.vdi" "D:\VirtualBox\SharePoint2010.vdi"
3. This will clone the existing image Windows 2008.vdi with 20 GB space to SharePoint2010.vdi which has 40 GB Space.
4. Attach the newly created VDI file to virutal box.
5. Thats all. you are done.

You might also like:
SharePoint Usage Reports
Usage reports, collaboration and audit for SharePoint.
Document SharePoint Farm
Automatically generate SharePoint documentation.
*Sponsored


Saturday, February 12, 2011

Export to Excel - From SharePoint user control based web part

My Requirement is to design a web part while pulls the data from SQL Server and display over the grid based on logged in user.

Yes, Its pretty straight forward. so I designed the below web part. Just a grid with with few lables and drop downs.

sharepoint user control export to excel


Now, the end users require Export to excel functionality. So, I placed a button at the bottom of the web part , and wrote the code for Exporting from Data grid to excel.

public void ExportToExcel()
{
try{
HttpContext.Current.Response.Clear();
HttpContext.Current.Response.AddHeader("content-disposition", string.Format("attachment; filename=Charge Report.xls"));
HttpContext.Current.Response.ContentType = "application/ms-excel";
using (StringWriter sw = new StringWriter())
{
using (HtmlTextWriter htw = new HtmlTextWriter(sw))
{
// Create a form to contain the gridTable table = new Table();
table.GridLines = GridView.GridLines;
// add the header row to the tableif (GridView.HeaderRow != null)
{
table.Rows.Add(GridView.HeaderRow);
}
// add each of the data rows to the tableforeach (GridViewRow row in GridView.Rows)
{
table.Rows.Add(row);
}
// add the footer row to the tableif (GridView.FooterRow != null)
{
table.Rows.Add(GridView.FooterRow);
}
// render the table into the htmlwritertable.RenderControl(htw);
// render the htmlwriter into the responseHttpContext.Current.Response.Write(sw.ToString());
HttpContext.Current.Response.End();
}
}
}
catch (Exception ex1)
{
System.Diagnostics.EventLog.WriteEntry("TeamApps Charge Report", ex1.Message);
}
}

Yeah, it worked well, But the problem is: the export to excel works ONLY for the first time. when i tried clicking on the Export to excel button again, Nothing happens.Hmmm..

After spending long time, I was able to figure out the issue and solution! All I've done is: added the OnClientClick to the button's event, and called the _spFormOnSubmitCalled = false;_spSuppressFormOnSubmitWrapper=true;.

<asp:Button ID="btnExportToExcel" runat="server" Text="Export to Excel" onclick="btnExportToExcel_Click" OnClientClick="_spFormOnSubmitCalled = false;_spSuppressFormOnSubmitWrapper=true;" />

This is because of the security settings of SharePoint. After placing this code every thing worked well.


You might also like:
SharePoint Usage Reports
Usage reports, collaboration and audit for SharePoint.
Document SharePoint Farm
Automatically generate SharePoint documentation.
*Sponsored


Friday, February 11, 2011

Looking for Copying content from dev Server to Prod server?

 SpContentDeployment Wizard is a excellent tool to copy content(Lists,Images,documents and the complete structure) from one server to another server.















Download URL: http://spdeploymentwizard.codeplex.com/

You might also like:
SharePoint Usage Reports
Usage reports, collaboration and audit for SharePoint.
Document SharePoint Farm
Automatically generate SharePoint documentation.
*Sponsored


Thursday, February 10, 2011

Deploy SharePoint Solution Packages (WSP) with PowerShell and STSADM

SharePoint solution packages (wsp) can be managed using either STSADM command line tool (in MOSS 2007) or with PowerShell cmdlets with SharePoint 2010 (such as deploy solution package with PowerShell). This article gives the reference for Managing SharePoint solutions using both of them with examples.
 

To add a solution package to the farm:
Add wsp with stsadm:
stsadm –o addsolution –filename mysolution.wsp

Add SharePoint solution using PowerShell:
Add-SPSolution "mysolution.wsp"

Add-SPSolution - MSDN Reference

Install/Deploy a Solution to the Farm:
STSADM command for wsp deployment:
stsadm –o deploysolution –name mysolution.wsp –url http://mysharepointsite –allowgacdeployment –immediate

SharePoint 2010 PowerShell to deploy/install wsp:
Install-spsolution -identity mysolution.wsp -webapplication http://mysharepointsite -gacdeployment -force
MSDN Reference

Upgrade an existing Solutions:
Update wsp solution with STSADM:
stsadm –o upgradesolution –name mySolution.wsp –filename "c:\MySolution.wsp" -immediate

PowerShell cmdlet to update solution in SharePoint 2010:
Update-SPSolution –Identity <solution file name>.wsp –LiteralPath C:\mysoln.wsp –GACDeployment
or
$solution = Get-SPSolution -Identity c0e31dec-294d-4f2d-9ae4-f2e637

Update-SPSolution $solution –LiteralPath "d:\newsolution.wsp" –Force -GACDeployment
MSDN Reference

Retract/un-install a Solutions from the Farm:
Retract solution with STSADM:
stsadm –o retractsolution –name mySolution.wsp –url http://mysharepointsite –immediate

Retract/uninstall SharePoint solution with PowerShell:
Uninstall-SPSolution –Identity <solution-file-name>.wsp –WebApplication http://mysharepointsite

or

$solution = Get-SPSolution -Identity c0e31dec-294d-4f2d-9ae4-f2e637
Uninstall-SPSolution $solution –WebApplication "SharePoint – 8080"

$solution = Get-SPSolution -Identity c0e31dec-294d-4f2d-9ae4-f2e637
Uninstall-SPSolution $solution –AllWebApplications


$solution = Get-SPSolution -Identity c0e31dec-294d-4f2d-9ae4-f2e637
Uninstall-SPSolution $solution
MSDN Reference

Remove/Delete a Solutions from the Farm:
Delete wsp solution with STSADM:
stsadm –o deletesolution –name mySolution.wsp  

Remove Farm solution in SharePoint 2010 with PowerShell:
Remove-SPSolution –Identity mySolution.wsp

If you don't know the Name, then Get the solution, and remove it:
$Solution = Get-SPSolution -Identity d0e11dec-293d-4c2d-9a24
Remove-SPSolution $solution
MSDN Reference

Get List of installed Solutions in the Farm:
Get-SPSolution

Export/Save Solution Packages to WSP with PowerShell:
$solution = Get-SPSolution -Identity c0e31dec-294d-4f2d-9ae4
$solution.SolutionFile.SaveAs("c:\Mysolution.wsp")


You might also like:
SharePoint Usage Reports
Usage reports, collaboration and audit for SharePoint.
Document SharePoint Farm
Automatically generate SharePoint documentation.
*Sponsored


Wednesday, February 9, 2011

Applying MOSS 2007 Service Packs/Patches - Steps and Best practices

Well, its inevitable in a SharePoint administrator's life, Applying service packs or patches to the environment.

Here are the steps, I've learned in my implementations.

First, its a good idea to have a maintenance page for your website, in order to avoid a typical "404 - page not found" to the end users. You can design a page and host in to any QA server or any other dedicated backup servers then place a redirect in ISA Server.

Here is the simple one I've done.  Maintenance Page for SharePoint - Quick way to Implement


OK, Maintenance page is ready! Let plan for patching.

Here are the steps:
1. Download the relevant service packs for both WSS and MOSS (doesn't matter, if you have MOSS only installed. You need to have both, because MOSS runs on top of WSS) from Microsoft site, say for e.g. I've downloaded August 2010-CU for 64 bit from Microsoft site.

2. Before start installing the patches, its a good idea to remove the content db's. This will prevent your content db's from being corrupted, in case your patching fails in middle.
How to do this? execute the below stsadm commands.

stsadm -o preparetomove -contentdb <Database server:Database Name> -site <URL>

stsadm -o deletecontentdb -url <URL> -databasename <Database Name>

Remember, this is ONLY dissociate your content db's with MOSS. This will not delete your conent db's. So dont panic.

3. Once, Databases are dissociated, the next step we need to do is: stopping the world wide web publishing service on our WFE's.
to do that, in command prompt, type:  Net stop w3svc

4. Ok, Now install the WSS patch in all the servers (WFE, APP, CA), once done, you may get a prompt to restart your machine, Do that so.

5. Once rebooted, install the MOSS Patch in all the servers.

6. once completed, you have to run the "SharePoint Products and Technologies configuration wizard".
There is a sequence you need to follow in running the products and technologies configuration wizard. We need to run the configuration wizard first in the CA server, next in the App servers, and then our WFEs.
So, Start the configuration wizard in CA Server. once you get the below screen, start the cofiguration wizard in others servers as per the sequence.


Once you get the above screen in the App, Web servers, Go back to complete the wizard in CA server, then app server, and then WFEs.

Now, configuration wizard has been completed. we need to add our content db's back. once added they'll be automatically upgraded to new version..
Execute: stsadm -o addcontentdb -url <URL> -databasename <Database Name>
 
Databases are added now. you can start the W3SVC service by typing: net start S3SVC

That's All. We are done!


You might also like:
SharePoint Usage Reports
Usage reports, collaboration and audit for SharePoint.
Document SharePoint Farm
Automatically generate SharePoint documentation.
*Sponsored


Tuesday, February 8, 2011

Object reference not set to an instance of an object - SharePoint 2007 Search Error

Today, I installed MOSS 2007 on a machine, which is not in the domain. Everything worked well, but when I tried search I got this error:

Object reference not set to an instance of an object.   at Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.OnLoad(EventArgs e)
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)


So, What is the resolution? Simple. just set the AAM Entry



You might also like:
SharePoint Usage Reports
Usage reports, collaboration and audit for SharePoint.
Document SharePoint Farm
Automatically generate SharePoint documentation.
*Sponsored


Install SharePoint 2007 in Windows Server 2008 R2 - This program is blocked due to compatibility issues

When I tried installing SharePoint 2007 in Windows server 2008 R2, I got this error "This program is blocked due to compatibility issues"

This is because: SharePoint 2007 is not compatible with Windows Sever 2008 R2. We need to download the service pack and merge with SharePoint Installers, then run the setup again!
Install SharePoint 2007 in Windows Server 2008 R2 - This program is blocked due to compatibility issues

Here is what you have to do to resolve this error:

Get the updates from this URL:
http://technet.microsoft.com/en-us/office/sharepointserver/bb735839.aspx

1. Download WSS and MOSS SP2 patches
Windows SharePoint Services 3.0 Service Pack 2 (SP2) - English
http://www.microsoft.com/downloads/details.aspx?FamilyId=79BADA82-C13F-44C1-BDC1-D0447337051B&displaylang=en

The 2007 Microsoft Office Servers Service Pack 2 (SP2)
http://www.microsoft.com/downloads/details.aspx?FamilyId=B7816D90-5FC6-4347-89B0-A80DEB27A082&displaylang=en

2. Extract both the SharePoint SP2 pack with this command and save in the “Updates” folder inside the MOSS binary location, like “c:\MOSS_setup\updates
c:\WSS-SP2\wssv3sp2-kb953338-x64-fullfile-en-us.exe /extract
c:\MOSS-SP2\officeserver2007sp2-kb953334-x64-fullfile-en-us.exe /extract


3. Delete Wsssetup.dll from the "Updates" folder, this is important. Otherwise only WSS SP2 will be installed. Now run the setup.exe

More details can be found on TechNet. http://technet.microsoft.com/en-us/library/cc261890.aspx 

KB article describes the issue with workaround: http://support.microsoft.com/kb/962935

You might also like:
SharePoint Usage Reports
Usage reports, collaboration and audit for SharePoint.
Document SharePoint Farm
Automatically generate SharePoint documentation.
*Sponsored


Wednesday, February 2, 2011

SharePoint Site Opens in Contributor mode for Site collection Admin, Farm Admin; Farm admin unable to Delete site

Today, I am running on a weird issue. for a particular site collection in my SharePoint environment, It opens in the contributor mode, and when I tried, I'm unable to delete that site collection, Even though I'm a Farm Admin!

Huh.. After spending considerable amount of time, I figured out the issue. You know what? The Problem is: Site was locked with Read-Only access!


Once I unlocked the site, I see "Site actions" shown up, and everything turned usual.

You might also like:
SharePoint Usage Reports
Usage reports, collaboration and audit for SharePoint.
Document SharePoint Farm
Automatically generate SharePoint documentation.
*Sponsored


Sharepoint Deployment Error: A deployment or retraction is already under way for the solution "abc.wsp" , and only one deployment or retraction at a time is supported

Sometime this error pops out from SharePoint Services Administration command when the user do retractsolution or deploysolution like the following

stsadm -o retractsolution -name "%PackageName%" -local -url %TargetWebUrl%
 
or

stsadm -o deploysolution -name "%PackageName%" -local -allowGacDeployment -url %TargetWebUrl%

Error:

"A deployment or retraction is already under way for the solution "xxx.wsp", and only one deployment or retraction at a time is supported"

it occurs if anomalies deployment is running for the same package in the back end due to some previous deployment has been crashed before for some reason.

check services and start the "Windows SharePoint Services Administration" service if it's stopped and then run the following command:

stsadm -o execadmsvcjobs

To avoid this problem do the followings:

  • Look for the deploy jobId to break the running by the following command: 
    • stsadm-o enumdeployments
  • Cancel the deploy typing the following command:
    • stsadm -o canceldeployment -id "GUID jobId"
  • Check that deploy has been canceled by typing the following command:
    • stsadm -o enumdeployments
Update: SharePoint2010 provides the user interface to cancel any existing deployments which is in stuck state. Go to Central Admin >> System Settings >> Manage farm solutions >> from here, you can pick the one which is in stuck state and cancel the deployment. Once done, you can do the deployment of your solution again!.

Related post: SharePoint WSP Solution Deployment Stuck at "Deploying" 


You might also like:
SharePoint Usage Reports
Usage reports, collaboration and audit for SharePoint.
Document SharePoint Farm
Automatically generate SharePoint documentation.
*Sponsored


You might also like:

Related Posts Plugin for WordPress, Blogger...