SmartCode Web Forum

6.10.1 Application Error Crash VNC Manager

https://www.s-code.com/forum/Topic4635.aspx

By hgtech - 19 Jan 2015

After the upgrade to 6.10.1 we have started randomly receiving an Application Error Crash with the following logged in the event log. This is happening on all of our Windows 7 and Windows 8 workstations running VNC Manager.

Faulting application name: VNCManager.exe, version: 6.10.1.0, time stamp: 0x54a5a2da
Faulting module name: RPCRT4.dll, version: 6.1.7601.22380, time stamp: 0x51dc2377
Exception code: 0xc00000fd
Fault offset: 0x00000000000640eb
Faulting process id: 0x98c
Faulting application start time: 0x01d034569f7d31f5
Faulting application path: C:\Program Files\SmartCode Solutions\VNC Manager (Enterprise Edition)\VNCManager.exe
Faulting module path: C:\Windows\system32\RPCRT4.dll
Report Id: 63268472-a04f-11e4-877f-002170c5afb0

By Yury Averkiev (s-code) - 19 Jan 2015

Hi,
can you pinpoint any potential cause of the crash? Like what heady been doing before the crash occurred? 
Also is there any background activity, like VNC or Hyper-V thumbnails? 
By hgtech - 19 Jan 2015

It has happened three times while I have been working tonight. There were a couple of Hyper-V thumbnails open on my computer when I checked however there were not on the other workstations.

Unfortunately, I don't have much more to go on than the event log error. The only thing I have had open tonight inside VNC Manager are VNC connections. Nothing out of the ordinary. Just basic remote control. No file transfers or anything like that. I've been playing around with it and have not found anything specific to trigger the crash.

We did not have this problem before the upgrade. I did try a patched version of the DLL from http://support.microsoft.com/kb/2734410 however the problem remains.
I'm more than willing to try / test anything I can.
By Yury Averkiev (s-code) - 19 Jan 2015

The component that changed the most in the 6.10.1 is the VNC Deployment Wizard. No changes related to Hyper-V were made. 
Indeed it could be a bug in the hotfix or compatibility problem with Rpcrt4.dll from the hotfoot.  I'll keep an eye on this problem and see if other customers report it.