Computerwhiz01 / superputty

Automatically exported from code.google.com/p/superputty
MIT License
1 stars 0 forks source link

Crash on 2008 R2 #450

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Extracted ZIP to a folder
tried launching the EXE but it fails.

ERROR

Faulting application name: SuperPutty.exe, version: 1.4.0.5, time stamp: 
0x53a4692c
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18015, time stamp: 
0x50b8479b
Exception code: 0xe0434f4d
Fault offset: 0x0000000000009e5d

Original issue reported on code.google.com by ja...@jaredjennings.org on 14 Aug 2014 at 8:28

Attachments:

GoogleCodeExporter commented 9 years ago
I too getting same error ...

Original comment by uday8...@gmail.com on 7 Oct 2014 at 6:16

GoogleCodeExporter commented 9 years ago
I'm having this issue as well, but only on one server in my environment. It 
works on a Windows 7 box, it works on another 2008 R2 box, but the box I need 
it to run on always gets a kernelbase.dll error when I try running the 
executable. Will update if I find a solution.

Original comment by lintzeri...@gmail.com on 11 Nov 2014 at 3:53

GoogleCodeExporter commented 9 years ago
any solution for this Superputty not able to run on  Windows 2008 R2

Original comment by ephraimm...@gmail.com on 14 Nov 2014 at 5:35

GoogleCodeExporter commented 9 years ago
When this happens for anyone else, are you RDP'd into the server? Does it 
matter if you are not.

Original comment by ja...@jaredjennings.org on 17 Nov 2014 at 10:02

GoogleCodeExporter commented 9 years ago
also experiencing this issue.

Original comment by jordanmo...@gmail.com on 25 Nov 2014 at 3:01

GoogleCodeExporter commented 9 years ago
Same error, Win 2008 R2.
RDP into the server, don't have console access.

After googling similar errors, I have tried the following:
Tried disabling SEHOP, as described here: http://support.microsoft.com/kb/956607
Tried 'sfc /scannow' without errors.

Original comment by rlex...@gmail.com on 9 Dec 2014 at 1:27

GoogleCodeExporter commented 9 years ago
Same issue here on same OS - had to switch to another connection manager due to 
this, could not find workarounds. Was using RDP as well

Original comment by omni1...@gmail.com on 4 Apr 2015 at 7:17