VNC Manager Enterprise on Vista Ultimate SP1


http://www.s-code.com/forum/Topic2024.aspx
Print Topic | Close Window

By JamesC - Monday, April 21, 2008
Hi,

Just installed 04.00.07.00 and when we try and connect to an XP machine using VNC quick connect it crashes with a memory exception...

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
at System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
at System.Reflection.Assembly.InternalGetSatelliteAssembly(CultureInfo culture, Version version, Boolean throwOnFileNotFound)
at System.Resources.ResourceManager.GetSatelliteAssembly(CultureInfo lookForCulture)
at System.Resources.ResourceManager.InternalGetResourceSet(CultureInfo culture, Boolean createIfNotExists, Boolean tryParents)
at System.Resources.ResourceManager.GetObject(String name, CultureInfo culture, Boolean wrapUnmanagedMemStream)
at System.Resources.ResourceManager.GetObject(String name, CultureInfo culture)
at SmartCodeVnc.Properties.Resources.a0()
at SmartCodeVnc.Controls.BrowseableTextBox.a()
at SmartCodeVnc.Controls.BrowseableTextBox..ctor()
at SmartCodeVnc.Controls.LookupCredentialEditor..ctor()
at c9.a()
at c9..ctor(dq A_0, b9 A_1, String A_2, fa A_3)
at dm.a(a A_0)
at dm.a(String A_0, fd A_1)
at au.a(Object A_0, ToolClickEventArgs A_1)


Its a fairly clean install and we can connect to the machine in question from XP ok.

JC

By Yury Averkiev (s-code) - Monday, April 21, 2008
Hi James,
I couldn't reproduce this bug using 4.0.7.0 build. By any chance, could you install this build on another computer and try to reproduce the bug?