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
Cloud Computing, Microsoft SharePoint, Microsoft .Net Technologies, K2 blackpearl Workflows, etc...
Friday, January 7, 2011
File not found error when you select New Webpart after installing SmartPart 1.3
We got this "File not found error....". The solution I found from one of a post somewhere, I have added the solution here:
Actual Error:
File Not Found. at System.Signature._GetSignature(SignatureStruct& signature, Void* pCorSig, Int32 cCorSig, IntPtr fieldHandle, IntPtr methodHandle, IntPtr declaringTypeHandle)
at System.Signature.GetSignature(SignatureStruct& signature, Void* pCorSig, Int32 cCorSig, RuntimeFieldHandle fieldHandle, RuntimeMethodHandle methodHandle, RuntimeTypeHandle declaringTypeHandle)
at System.Signature..ctor(RuntimeMethodHandle methodHandle, RuntimeTypeHandle declaringTypeHandle)
at System.Reflection.RuntimeMethodInfo.get_Signature()
at System.Reflection.RuntimeMethodInfo.GetParameters()
at Microsoft.SharePoint.WebPartPages.SPWebPartSerializer.GetPersonalizableProperties()
at Microsoft.SharePoint.WebPartPages.SPWebPartManager.GetEffectiveWebPartType(Type webPartType, SerializationTarget serializationTarget, Boolean ignoreSupportsAttributeMarkup)
at Microsoft.SharePoint.WebPartPages.SPWebPartManager.GetEffectiveWebPartType(Type aspWebPartType, SerializationTarget serializationTarget)
at Microsoft.SharePoint.ApplicationPages.NewDwp.Page_PreRender(Object sender, EventArgs e)
at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e)
at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)
at System.Web.UI.Control.OnPreRender(EventArgs e)
at Microsoft.SharePoint.WebControls.UnsecuredLayoutsPageBase.OnPreRender(EventArgs e)
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Solution from the below post:
http://www.codeplex.com/smartpart/WorkItem/View.aspx?WorkItemId=2708
SmartPart is binding to the older version of the System.Web.Extensions. If I had installed an earlier version of the framework and the separate AJAX extension 1.0, it may have worked.
The article does suggest a workaround.
1. Go the the web.config of your WSS.
2. Locate the section, and within that . There should be a list of entries.
3. Add the following entry
3. Add the following entry as shown below
What the entry does is redirect binding to the old version of System.Web.Extensions to the new version. The 3.5.0.0 version should have been installed to the GAC when you install Framework 3.5 SP1.
After this change, you will be able to create a new web part in the web part gallery again.
Actual Error:
File Not Found. at System.Signature._GetSignature(SignatureStruct& signature, Void* pCorSig, Int32 cCorSig, IntPtr fieldHandle, IntPtr methodHandle, IntPtr declaringTypeHandle)
at System.Signature.GetSignature(SignatureStruct& signature, Void* pCorSig, Int32 cCorSig, RuntimeFieldHandle fieldHandle, RuntimeMethodHandle methodHandle, RuntimeTypeHandle declaringTypeHandle)
at System.Signature..ctor(RuntimeMethodHandle methodHandle, RuntimeTypeHandle declaringTypeHandle)
at System.Reflection.RuntimeMethodInfo.get_Signature()
at System.Reflection.RuntimeMethodInfo.GetParameters()
at Microsoft.SharePoint.WebPartPages.SPWebPartSerializer.GetPersonalizableProperties()
at Microsoft.SharePoint.WebPartPages.SPWebPartManager.GetEffectiveWebPartType(Type webPartType, SerializationTarget serializationTarget, Boolean ignoreSupportsAttributeMarkup)
at Microsoft.SharePoint.WebPartPages.SPWebPartManager.GetEffectiveWebPartType(Type aspWebPartType, SerializationTarget serializationTarget)
at Microsoft.SharePoint.ApplicationPages.NewDwp.Page_PreRender(Object sender, EventArgs e)
at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e)
at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)
at System.Web.UI.Control.OnPreRender(EventArgs e)
at Microsoft.SharePoint.WebControls.UnsecuredLayoutsPageBase.OnPreRender(EventArgs e)
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Solution from the below post:
http://www.codeplex.com/smartpart/WorkItem/View.aspx?WorkItemId=2708
SmartPart is binding to the older version of the System.Web.Extensions. If I had installed an earlier version of the framework and the separate AJAX extension 1.0, it may have worked.
The article does suggest a workaround.
1. Go the the web.config of your WSS.
2. Locate the section
3. Add the following entry
3. Add the following entry as shown below
What the entry does is redirect binding to the old version of System.Web.Extensions to the new version. The 3.5.0.0 version should have been installed to the GAC when you install Framework 3.5 SP1.
After this change, you will be able to create a new web part in the web part gallery again.
Outlook: General failure. The URL was
Usually this issue happens if the IE browser is not the default browser in the local machine.
So please check the browser settings like below.
To make IE your default browser, follow the steps:
1. Click the “tools” menu at the top of Internet Explorer.
2. Then click “Internet Options” in the list.
3. Click on the “Programs” tab.
4. Look in the “Default web browser” section of the window.
If this section looks like this, then Internet Explorer is your default browser.After changing this setting, please try from outlook again.
Even after this, the issue is not resolved and if you have Mozilla Firefox in your system, please uninstall the browser and try.
Hopefully these options may help you!
K2 Blakpearl Installation Trouble Shooting
After installing all the components you may see lot of errors showing in configuration wizard. Few of the follwing steps will help you to solve the issues (esp. see if there are any Kerbero's issues).
1. To see System Stored userids, run the following line in Run window (delete if you find any, with caution)
To do: rundll32.exe keymgr.dll,KRShowKeyMgr
2. SPNs check
To do: setspn -l domain/service_account
ex: setspn -l gs/service_admin
3. Duplicate SPNs check
To do: 1. setspn -x
It lists out all the SPNs in the environment in DOS console
2. setspn -x > D:\test\log.txt
It writes all the SPNs list to a file specified in the directory path as shown above.
4. DelegConfig download (try in google)
To do: Search in google with the word DelegConfig you will get the links to download this app.
Here is one link:
http://www.iis.net/community/default.aspx?tabid=34&g=6&i=1887
Download it and createe a virtual directory under IIS. Open the site and that takes you through all the config settings, and shows the status of Kerberoes setup configuration.
5. Service Account Delegation Setup
To do: K2 Service account needs to be delegated with SharePoint App pool (identity) account in Active Directory. (This solves the 401 unauthorization Kerberos issue for Blakpearl– SharePoint communication, like through the smart objects).
You may not have all these issues but if you find that there is something going wrong with your installation, you can find this information helpful to trouble shoot.
1. To see System Stored userids, run the following line in Run window (delete if you find any, with caution)
To do: rundll32.exe keymgr.dll,KRShowKeyMgr
2. SPNs check
To do: setspn -l domain/service_account
ex: setspn -l gs/service_admin
3. Duplicate SPNs check
To do: 1. setspn -x
It lists out all the SPNs in the environment in DOS console
2. setspn -x > D:\test\log.txt
It writes all the SPNs list to a file specified in the directory path as shown above.
4. DelegConfig download (try in google)
To do: Search in google with the word DelegConfig you will get the links to download this app.
Here is one link:
http://www.iis.net/community/default.aspx?tabid=34&g=6&i=1887
Download it and createe a virtual directory under IIS. Open the site and that takes you through all the config settings, and shows the status of Kerberoes setup configuration.
5. Service Account Delegation Setup
To do: K2 Service account needs to be delegated with SharePoint App pool (identity) account in Active Directory. (This solves the 401 unauthorization Kerberos issue for Blakpearl– SharePoint communication, like through the smart objects).
You may not have all these issues but if you find that there is something going wrong with your installation, you can find this information helpful to trouble shoot.
K2.net Studio has encountered a problem and needs to close
When we were trying to open the K2 studio we got the follwing error.
"K2.net Studio has encountered a problem and needs to close. We are sorry for the inconevenience."
Error screen shot below:
Solution:
1. Login with your Id (if it is in server)
2. Go to RegEdit and Navigate to the path
3. HKEY_CURRENT_USER\Software\SourceCode
4. Delete the K2.net Studio Folder
Now open the K2 Studio, this may fix your issue. It worked fine for me.
"K2.net Studio has encountered a problem and needs to close. We are sorry for the inconevenience."
Error screen shot below:
Solution: 1. Login with your Id (if it is in server)
2. Go to RegEdit and Navigate to the path
3. HKEY_CURRENT_USER\Software\SourceCode
4. Delete the K2.net Studio Folder
Now open the K2 Studio, this may fix your issue. It worked fine for me.
Subscribe to:
Posts (Atom)