We got the same error, I got the follwing solution from a blog and this solved our problem:
After checking the SolutionID GUID in the Setup.exe.config file with the SolutionId GUID in my project manifest.xml file, I realized that they were different. I created a new GUID (just for peace of mind) and updated both SolutionIds. Before I could run setup again, I had to delete the wsp from the Sharepoint solution store. I ran this bat file to do so
(taken from Ted Pattison's WSS401 lab)
@SET STSADM="c:\program files\common files\microsoft shared\web server extensions\12\bin\stsadm.exe"
%STSADM% -o retractsolution -name YourSilverlightApplication.wsp -immediate
%STSADM% -o execadmsvcjobs
%STSADM% -o deletesolution -name YourSilverlightApplication1.wsp
Feature Scope Error:
http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/dd328fce-6d16-434f-b4bf-a53deac8eaad/
Info:
http://arcadiaunlimited.com/blog/tag/sharepoint-solution-installer/
STSADM:
http://www.codebanking.com/articles/sharepoint/sharepoint-stsadm-command-for-deployment.asp
Subscribe to:
Post Comments (Atom)
Access to XMLHttpRequest at 'from origin has been blocked by CORS policy: Cross origin requests are only supported for protocol schemes: http, data, chrome, chrome-extension, https. .net core angular
Issue: The angular application was getting error from API that the origin has been blocked by CORS policy. Solution: Make sure that the...
-
We had an issue while updating the datafield values without executing the action in the application form. If we use ProcessInstance Updat...
-
Trying to use the Oracle Data Provider for .NET ( ODP.NET ) with Entity Framework (EF) results in the following error: System.Data.Pro...
-
Issue: LDAP Query not pulling all the Active Directory Groups (including subgroups) available in the given domain. Solution: To retriev...
No comments:
Post a Comment