|
 Posted 2/16/2007 9:44:46 AM |
| | | Would some one please provide a few pointers. What are the following exceptions associated with? Exception: c360.Toolkit.Common.FactoryException: Unable to create the specified component. Verify the entry for [SecurityPrincipal]. ---> c360.Toolkit.Common.FactoryException: Exception has been thrown by the target of an invocation. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: c360 products require that currently authenticated user is impersonated.
at c360.Toolkit.Security.CRMSecurityPrincipal..ctor()
--- End of inner exception stack trace ---
at System.RuntimeType.CreateInstanceImpl(Boolean publicOnly)
at System.Activator.CreateInstance(Type type, Boolean nonPublic)
at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
at c360.Toolkit.Common.Factory.ᜀ(Type A_0, Object[] A_1)
--- End of inner exception stack trace ---
at c360.Toolkit.Common.Factory.ᜀ(Type A_0, Object[] A_1)
at c360.Toolkit.Common.ComponentFactory.ᜀ(String A_0, Object[] A_1)
--- End of inner exception stack trace ---
at c360.Toolkit.Common.ComponentFactory.ᜀ(String A_0, Object[] A_1)
at c360.Toolkit.Common.ComponentFactory.Create(String componentKey)
at c360.Toolkit.Security.SecurityProvider.ᜀ()
at c360.Toolkit.Security.ImpersonationStrategy.ᜀ()
at c360.Toolkit.Security.ImpersonationStrategy.ᜁ()
at c360.Toolkit.Licensing.c360LicenseProvider.GetOrganization()
at c360.Toolkit.Licensing.c360LicenseProvider.get_Organization()
at c360.Toolkit.Licensing.c360LicenseProvider.ᜀ(LicenseContext A_0, Type A_1, Object A_2, Boolean A_3) |
| | Posted 2/16/2007 11:26:32 AM |
| | | | Posted 2/19/2007 10:25:29 AM |
| | | Thanks. However, that was one of the first things we tried. |
| | Posted 2/19/2007 11:01:21 PM |
| | | I know with 100% certainty that this problem is caused by incorrectly configured authentication (I know this because I helped our dev team to craft this error message when we detect that the authentication is not set correctly in the virtual directory where our SDK is installed). I know that authentication is controled by the two keys in your web.config as described in the article I linked. It is very common for people to confuse which web.config they need to edit so please make sure you are editing the config file in your application's root folder (please note that it's possible that you don't have one since our SDK does not include one. In this situation, you would need to create it manually or use the very convenient web.config editor bundled with VS.NET 2005). I am not aware of any other way to control the authentication in a virtual directory. Since you sound confident that you have already checked these two keys, you will need to investigate why these two keys appear to be ignored by IIS. Maybe "Anonymous connections" have been allowed on your virtual directory? Anonymous connections need to be disallowed in order for the user's credentials to be forwarded to the web server therefore, make sure this option is un-checked in your virtual directory settings.
|
| |
|