Unable to deploy wsp pacakage - Timer job and cache issue

 Sometime back in my project , I couldn't deploy wsp packages anymore. After some analysis found there are lot of one time job were running and it was blocking wsp deplopyment. Here I have provided the steps to resolve it,

-  In Central Admin checked in Farm Solution Management the status was stuck on Deploying​

-  Stopped the SharePoint Admin and SharePoint Timer services

      - Checked and found multiple One-time jobs​, deleted those using the scripts below:

-          Get-SPTimerJob | where{$_.DisplayName -eq $null} | foreach-object {$_.Delete()}Get-SPTimerJob | where{$_.schedule.description -eq "One-time"} | ForEach-Object{$_.Delete()}

-          Checked if the timer service is ON using the script

-          $farm  = Get-SPFarm

-          $disabledTimers = $farm.TimerService.Instances | where {$_.Status -ne "Online"}

-          if ($disabledTimers -ne $null)

-          {

-          foreach ($timer in $disabledTimers)

-          {

-          Write-Host "Timer service instance on server " $timer.Server.Name " is not Online. Current status:" $timer.Status

-                 Write-Host "Attempting to set the status of the service instance to online"

-                 $timer.Status = [Microsoft.SharePoint.Administration.SPObjectStatus]::Online

-                 $timer.Update()

-             }

-          }

 

Cleared the timer Cache on all the servers:

-          Stop the SharePoinnt timer service

-          %SystemDrive%\ProgramData\Microsoft\SharePoint\Config

-          Inside this folder you will find lots of files. Your goal is to delete all the files, except the cache.ini. First make a backup of the cache.ini file. You can either copy and paste it in the same folder. The cache – Copy.ini will become your backup file.

-          Delete all the files. This will leave you with only the cache.ini file in this folder. DO NOT delete the folder. Your goal is to rebuild the cache in the same folder that was created by the system.

-          Open the cache.ini file. You are probably expecting tons of information in the file but all it has is a 5 or 6-digit number, e.g. 356867. Replace this number with 1 so the only data in the file is the number 1. Now save the file. Changing this number to 1 resets the cache and it will be rebuild after the SharePoint Timer Service is restarted.

-          Rebooted the SharePoint servers and ran IISreset

-          So ran the below commands and solution was deployed

-          Add-SPSolution -LiteralPath E:\ExampleProject\bin\Debug\SharePointProject.wsp

-          Install-SPSolution -Identity SharePointProject1.wsp -GACDeployment -ForceAdd-SPSolution -LiteralPath "E:\ExampleProject\bin\Debug\SharePointProject.wsp"

 


Comments

Post a Comment

Popular posts from this blog

Power BI Refresh Issue: unable to convert the value '' from the source data type 'VT_BSTR' to the expected data type 'VT_I8.

Image
While scheduling refresh in Power BI, you might get below error . Issue: Unable to convert the value '<pii></pii>' from the source data type 'VT_BSTR' to the expected data type 'VT_I8 .     Cause/Reason Behind: Column datatype mismatch between power bi desktop and power bi cloud report. Solution: Edit query in power bi desktop and change the data type so it’s in sync with Power BI service/cloud. Example: In my case, I have modified a column’s datatype from decimal to whole number (to display no. of days). Now power bi desktop and power bi service synced up and I could perform automatic data refresh.
Read more

Run Powershell script on Remote Computer/Server

Image
PowerShell Remoting allows you to run individual PowerShell commands or access full PowerShell sessions on remote Windows systems.   PowerShell is locked-down by default, so you’ll have to enable PowerShell Remoting before using it. This setup process is a bit more complex if you’re using a workgroup – for example, on a home network — instead of a domain.   Enabling PowerShell Remoting On the computer you want to access remotely, open a PowerShell window as Administrator – right click the PowerShell shortcut and select Run as Administrator.   To enable PowerShell Remoting, run the following command (known as a cmdlet in PowerShell):  Enable-PSRemoting -Force This command starts the WinRM service, sets it to start automatically with your system, and creates a firewall rule that allows incoming connections. The -Force part of the command tells PowerShell to perform these actions without prompting you for each step     Workgroup Setup If your computers aren
Read more

SPDActivities - DP.SharePoint.Workflow - Workflow failed to run

Image
One of my SP 2016 application is using SPDActivities of Email extended feature of DP.SharePoint.Workflow to provide custom "From" address. But customers started to complain that they are not getting reminder emails anymore. Find below my STAR analysis, Situation : Recently I was facing an issue - Approval workflow failed to run. Customers not getting reminder emails anymore. Task : - Planned to look into SharePoint services, IIS site, web.config files (WFE and App Server), Latest patch/MS update/CU, Users permission. Analysis : Started looking into each below items,  - SharePoint Timer Service and Administration services were running and good - Account which is running the workflow got required permission - DP.SharePoint.Workflow got activated for the web application - Checked into web.config file in WFE server and App Server for below sections Under <SafeControls> below 3 lines need to added both in WFE and App server web.config files,
Read more