0
Won't fix

Error when opening web console after upgrade to 4.0.4

Hayden Gray 1 week ago updated by Beau Harrison (Software Developer) 3 days ago 1

HI Guys,

I've recently upgrade UNIFYNow to 4.0.4. When i first did the upgrade the service started fine and the web console would open and I could interact with it. Coming back the next day, the service stops and starts fine but when trying to access the web console a get the following error:

Could not load file or assembly 'Unify.Framework.Collections, Version=5.2.0.0, Culture=neutral, PublicKeyToken=84b9288cb2633de4' or one of its dependencies. The system cannot find the file specified.

Server Error in '/' Application.

Could not load file or assembly 'Unify.Framework.Collections, Version=5.2.0.0, Culture=neutral, PublicKeyToken=84b9288cb2633de4' or one of its dependencies. The system cannot find the file specified.

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: System.IO.FileNotFoundException: Could not load file or assembly 'Unify.Framework.Collections, Version=5.2.0.0, Culture=neutral, PublicKeyToken=84b9288cb2633de4' or one of its dependencies. The system cannot find the file specified.

Source Error:

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL: 1. Add a "Debug=true" directive at the top of the file that generated the error. Example: <%@ Page Language="C#" Debug="true" %> or: 2) Add the following section to the configuration file of your application: <configuration> <system.web> <compilation debug="true"/> </system.web> </configuration> Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode. Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.


Assembly Load Trace: The following information can be helpful to determine why the assembly 'Unify.Framework.Collections, Version=5.2.0.0, Culture=neutral, PublicKeyToken=84b9288cb2633de4' could not be loaded.

<pre>WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. </pre>


Stack Trace:

<pre>[FileNotFoundException: Could not load file or assembly 'Unify.Framework.Collections, Version=5.2.0.0, Culture=neutral, PublicKeyToken=84b9288cb2633de4' or one of its dependencies. The system cannot find the file specified.] Unify.Framework.TimingGenerator..ctor() in C:\agent\_work\69\s\Source\Scheduling\Unify.Framework.Scheduling.Timing\TimingGenerator.cs:28 Unify.Framework.Logging.LoggingEngineClient..ctor(ILoggingEngineCollector collector) in C:\agent\_work\69\s\Source\Logging\Unify.Framework.Logging.Engine.Shared\LoggingEngineClient.cs:25 Unify.EventBroker.Web.EventServiceClientInstance.CreateComponent(EndpointAddress serviceEndpointAddress) in C:\agent\_work\86\s\Source\Unify.EventBroker.Web\Extensions\EventServiceClientInstance.cs:56 Unify.EventBroker.Web.EventServiceClientInstance..cctor() in C:\agent\_work\86\s\Source\Unify.EventBroker.Web\Extensions\EventServiceClientInstance.cs:32 [TypeInitializationException: The type initializer for 'Unify.EventBroker.Web.EventServiceClientInstance' threw an exception.] Unify.EventBroker.Web.MvcApplication..ctor() in C:\agent\_work\86\s\Source\Unify.EventBroker.Web\Global.asax.cs:36 ASP.global_asax..ctor() +9 [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) +159 System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark) +256 System.Activator.CreateInstance(Type type, Boolean nonPublic) +127 System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, StackCrawlMark& stackMark) +14316525 System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes) +198 System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture) +28 System.Web.HttpRuntime.CreateNonPublicInstance(Type type, Object[] args) +69 System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +296 System.Web.HttpApplicationFactory.EnsureAppStartCalled(HttpContext context) +240 System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext context) +184 System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +597 </pre>


Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.36480

Thanks

Won't fix

Hi Hayden,

This is a known issue with the self-hosted web UI, a feature which was depreciated in 4.0. Use IIS instead.