KB45186: Deploying Web Parts on SharePoint 2013 Causes the Warning "Solutions no longer support deploying Code Access Security (CAS) policy so any CAS policy specified in solution "MSTRWebParts.wsp" was skipped and not deployed" using MicroStrategy Web 9.

• Strategy

MicroStrategy Web Parts does not utilize Code Access Security (CAS), so this error message is irrelevant. It can be effectively ignored.

SYMPTOM:
Step #1 for deploying the Strategy Web Parts for SharePoint 2013 instructs for the following command to be executed:
stsadm -o deploysolution -name MSTRWebParts.wsp -immediate -allcontenturls -allowcaspolicies -allowGacDeployment –force
However, this running this command causes the following warning to appear:


Warning:

Solutions no longer support deploying Code Access Security (CAS) policy so any CAS policy specified in solution "MSTRWebParts.wsp" was skipped and not deployed. Deploy this solution without the -allowCasPolicies flag to suppress this warning.


The timer job for this operation has been created, but it will fail because the administrative service for this server is not enabled. If the timer job is scheduled to run at a later time, you can run the jobs all at once using stsadm.exe -o execadmsvgjobs. To avoid this problem in the future, enable the Microsoft SharePoint Foundation administrative service, or run your operation through the STSADM.exe command line utility.

CAUSE:
Strategy Web Parts does not utilize Code Access Security (CAS), so this error message is irrelevant. It can be effectively ignored.
ACTION:
There are two possible actions:
(1) Ignore the warning and proceed forward with the deployment process
(2) Remove "-allowcaspolicies" from the aforementioned command, as such:
stsadm -o deploysolution -name MSTRWebParts.wsp -immediate -allcontenturls -allowGacDeployment –force

Comment

0 comments

Details

Knowledge Article

Published:

June 22, 2017

Last Updated:

June 22, 2017

Warning: Solutions no longer support deploying Code Access Security (CAS) policy so any CAS policy specified in solution "MSTRWebParts.wsp" was skipped and not deployed. Deploy this solution without the -allowCasPolicies flag to suppress this warning. The timer job for this operation has been created, but it will fail because the administrative service for this server is not enabled. If the timer job is scheduled to run at a later time, you can run the jobs all at once using stsadm.exe -o execadmsvgjobs. To avoid this problem in the future, enable the Microsoft SharePoint Foundation administrative service, or run your operation through the STSADM.exe command line utility.