Online Help System

www.screenconnect.com

PRB-0003: Web Server service unable to start under Windows Vista

Modified: 2012/01/20 11:15 by Kat Palacios - Categorized as: Knowledge Base

Edit

1 Symptoms

The Web Server service does not start under Windows Vista. An error message similar to the following will appear in the Windows Application Log:

Failed to restart service. System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.IO.FileNotFoundException: Could not load file or assembly 'Elsinore.ScreenConnect.Service, Version=1.0.0.0, Culture=neutral, PublicKeyToken=4b14c015c87c1ad8' or one of its dependencies. The system cannot find the file specified.
File name: 'Elsinore.ScreenConnect.Service, Version=1.0.0.0, Culture=neutral, PublicKeyToken=4b14c015c87c1ad8'
   at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
   at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
   at System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
   at System.Reflection.Assembly.Load(String assemblyString)
   at System.UnitySerializationHolder.GetRealObject(StreamingContext context)
   at System.Web.Hosting.HostingEnvironment.CreateInstance(Type type)
   at System.Web.Hosting.ApplicationHost.CreateApplicationHost(Type hostType, String virtualDir, String physicalDir)
   at Elsinore.ScreenConnect.WebServer.EnsureRuntimeHost() in C:\ScreenConnect\trunk\Product\Service\WebServer.cs:line 110
   at Elsinore.ScreenConnect.WebServer..ctor() in C:\ScreenConnect\trunk\Product\Service\WebServer.cs:line 33

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].

   --- End of inner exception stack trace ---
   at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor, Boolean& bNeedSecurityCheck)
   at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean fillCache)
   at System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean fillCache)
   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(String assemblyName, String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, Evidence securityInfo, StackCrawlMark& stackMark)
   at System.Activator.CreateInstance(String assemblyName, String typeName)
   at System.AppDomain.CreateInstance(String assemblyName, String typeName)
   at Elsinore.ScreenConnect.AppDomainServiceBase.StartServiceInternal() in C:\ScreenConnect\trunk\Product\Service\AppDomainService.cs:line 198
   at Elsinore.ScreenConnect.ServiceBaseEx.OnTimerTick(Object state) in C:\ScreenConnect\trunk\Product\Service\AppDomainService.cs:line 104

Edit

2 Cause

ScreenConnect was not able to start ASP.NET correctly. This occurs when the "Temporary ASP.NET Files" directory does not previously exist under your .NET installation folder.

Edit

3 Resolution

Version 1.1 and above resolve this issue by creating the directory before attempting to start ASP.NET.

Edit

4 References