0
Answered

Issue installing 5.3 over the top of 5.2

Hayden Gray 6 years ago updated by Adam van Vliet 6 years ago 6

I'm having an issue after installing 5.3 over 5.2. 

The details are as follows:

"

After installing 5.3 over the top of 5.2 I get a sitemap issue.
================
The site map provider was of type System.Web.XmlSiteMapProvider. The web.config should be configured to use type="Unify.Connect.Web.IdentityBrokerSiteMapProvider".
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 

Exception Details: Unify.Framework.UnifyConfigurationException: The site map provider was of type System.Web.XmlSiteMapProvider. The web.config should be configured to use type="Unify.Connect.Web.IdentityBrokerSiteMapProvider".

================
Broker is set up to use IIS for the web interface

"

The stack trace is as follows:

"

[UnifyConfigurationException: The site map provider was of type System.Web.XmlSiteMapProvider. The web.config should be configured to use type="Unify.Connect.Web.IdentityBrokerSiteMapProvider".]

   Unify.Connect.Web.MvcApplication..cctor() +4876

[TypeInitializationException: The type initializer for 'Unify.Connect.Web.MvcApplication' threw an exception.]

   ASP.global_asax..ctor() +28

[TargetInvocationException: Exception has been thrown by the target of an invocation.]

   System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck) +0

   System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark) +197

   System.Activator.CreateInstance(Type type, Boolean nonPublic) +105

   System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, StackCrawlMark& stackMark) +1484

   System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes) +289

   System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture) +27

   System.Web.HttpRuntime.CreateNonPublicInstance(Type type, Object[] args) +79

   System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +294

   System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +333

[HttpException (0x80004005): Exception has been thrown by the target of an invocation.]

   System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +525

   System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +124

   System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +719

"

Let me know if you need any further information.


Thanks,

Hayden

Answer

Answer
Answered

There can be client specific things in there, but the default should be fine (especially if you're running without one). If the client decides to configure more settings they can (e.g. OIDC for the UI and AAD bearer auth for the API).

Web.config

Under review

Have you compared the upgrade install with a fresh install? Did a fresh install work? What were the differences in files between the installs? There's no difference in web.config for v5.2 and v5.3, so this is a little strange that it's occurring, so could you please attach the web.config.?

Thanks.

Web.config

Sorry for the delayed upload, but please find attached the web.config. In regards to the other question this has not been compared with a fresh install for differences as only the upgrade install has been done.

Thanks.

That appears to be the web.config from the Views subdirectory. Could you please attach the on from the root directory?

Also, the attached file appears to be outdated (from v4.1). You may wish to update it to Web.config. I've added an item to our backlog to see why this file wasn't upgrade during the installation.

The web.config in the root directory isn't there, I'll need to investigate further why this is the case and whether this is the only missing file. 

Is it possible if you could send through a default Web.config to this directory or are there settings which are client specific in the file?

Thanks

Answer
Answered

There can be client specific things in there, but the default should be fine (especially if you're running without one). If the client decides to configure more settings they can (e.g. OIDC for the UI and AAD bearer auth for the API).

Web.config

Adding the default Web.config appears to have fixed the issue.


Thanks Adam