Tag Info

New answers tagged

0

You can deactivate a feature with the following code: web.Site.Features.Remove(new Guid("GUID_OF_YOUR_FEATURE"), true); Add the code after adding the web part (line 38 in your code).


1

I did find a solution.. However I don't know how practical it is. This is what I did: Installed Visual Studio 2012 on my Staging. Updated it with 'Update 4'. Installed office tool for VS 2012. Got the work flow code and deployed it via Visual Studio. (And the deployment worked). Retracted the solution via Visual Studio. Added the .wsp files manually via ...


1

I did find a solution.. However I don't know how practical it is. This is what I did: Installed Visual Studio 2012 on my Staging. Updated it with 'Update 4'. Installed office tool for VS 2012. Got the work flow code and deployed it via Visual Studio. (And the deployment worked). Retracted the solution via Visual Studio. Added the .wsp files manually via ...


0

I also received this kind of error before while deploying webpart, so i used powershell to add solution, that time it shown the actual error that my SharePoint_Config log file was full. You can check below two scenario: 1) Your sharepoint_config log file is not full and you have diskspace on server. 2) The account you are using to deploy solution has ...


0

Try recreating State Service Application by executing following script: $serviceApp = New-SPStateServiceApplication -Name "State Service" New-SPStateServiceDatabase -Name "StateServiceDatabase" -ServiceApplication $serviceApp New-SPStateServiceApplicationProxy -Name "State Service Proxy" -ServiceApplication $serviceApp -DefaultProxyGroup


0

Try to Flush the BLOB cache. $webApp = Get-SPWebApplication "<WebApplicationURL>" [Microsoft.SharePoint.Publishing.PublishingCache]::FlushBlobCache($webApp) Write-Host "Flushed the BLOB cache for:" $webApp Flush the BLOB cache



Top 50 recent answers are included