login vsi company logo login vsi company logo 250x40
header-01.jpg

Login VSI Management Console.exe crashes on W2K2008 R2 SP1 after install

  • msturtz
  • msturtz's Avatar Topic Author
18 May 2013 02:33 #1029

LoginVSI version 4.0

Steps to reproduce
With an LoginVSI 4.0 share configured on File Share
Run Setup.exe on Windows 2008 R2 with all windows updates
After setup completes the attached dialog is displayed

The following text is displayed when click the View problem details down arrow on the dialog

Description:
Stopped working

Problem signature:
Problem Event Name: APPCRASH
Application Name: Login VSI Management Console.exe
Application Version: 4.0.42.1555
Application Timestamp: 517fc1c4
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7601.18015
Fault Module Timestamp: 50b8479b
Exception Code: e0434f4d
Exception Offset: 0000000000009e5d
OS Version: 6.1.7601.2.1.0.274.10
Locale ID: 1033

Read our privacy statement online:
go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflp


Unable to upload zip file because of error on your web site

Attachments:

Please Log in to join the conversation.

More
19 May 2013 17:13 #1030

Hi Mark,

Have you tried applying the 4.0.1 patch available at www.loginvsi.com/download ? (Make sure to scroll down a bit and download the patch only)

Let me know if this helps.

Please Log in to join the conversation.

  • msturtz
  • msturtz's Avatar Topic Author
20 May 2013 16:14 #1034

Hello,
I tried to install LoginVSI and I am still seeing the crash
The steps to reproduce are the same as in the previous posting



I am adding debugging information from when I saw this crash on LoginVSI 4.0



Process Architecture: x64
Exception Code: 0xE0434F4D
Exception Information: An exception came from the CLR
Heap Information: Not Present

System Information


OS Version: 6.1.7601
CLR Version(s): 2.0.50727.5466

Modules
Module Name Module Path Module Version


Login VSI Management Console.exe C:\vsi-4\_VSI_ManagementConsole\Login VSI Management Console.exe 4.0.42.1555
ntdll.dll C:\Windows\System32\ntdll.dll 6.1.7601.17725
mscoree.dll C:\Windows\System32\mscoree.dll 4.0.40305.0
kernel32.dll C:\Windows\System32\kernel32.dll 6.1.7601.18015
KERNELBASE.dll C:\Windows\System32\KERNELBASE.dll 6.1.7601.18015
apphelp.dll C:\Windows\System32\apphelp.dll 6.1.7601.17514
AcLayers.dll C:\Windows\AppPatch\AppPatch64\AcLayers.dll 6.1.7601.18128
user32.dll C:\Windows\System32\user32.dll 6.1.7601.17514
gdi32.dll C:\Windows\System32\gdi32.dll 6.1.7601.17514
lpk.dll C:\Windows\System32\lpk.dll 6.1.7600.16385
usp10.dll C:\Windows\System32\usp10.dll 1.626.7601.18009
msvcrt.dll C:\Windows\System32\msvcrt.dll 7.0.7601.17744
winspool.drv C:\Windows\System32\winspool.drv 6.1.7601.17514
mpr.dll C:\Windows\System32\mpr.dll 6.1.7600.16385
rpcrt4.dll C:\Windows\System32\rpcrt4.dll 6.1.7601.17514
imm32.dll C:\Windows\System32\imm32.dll 6.1.7600.16385
msctf.dll C:\Windows\System32\msctf.dll 6.1.7600.16385
AcXtrnal.dll C:\Windows\AppPatch\AppPatch64\AcXtrnal.dll 6.1.7601.18128
AcGenral.dll C:\Windows\AppPatch\AppPatch64\AcGenral.dll 6.1.7601.18128
sspicli.dll C:\Windows\System32\sspicli.dll 6.1.7601.17725
shlwapi.dll C:\Windows\System32\shlwapi.dll 6.1.7601.17514
ole32.dll C:\Windows\System32\ole32.dll 6.1.7601.17514
shell32.dll C:\Windows\System32\shell32.dll 6.1.7601.18103
sfc.dll C:\Windows\System32\sfc.dll 6.1.7600.16385
sfc_os.dll C:\Windows\System32\sfc_os.dll 6.1.7600.16385
userenv.dll C:\Windows\System32\userenv.dll 6.1.7601.17514
profapi.dll C:\Windows\System32\profapi.dll 6.1.7600.16385
dwmapi.dll C:\Windows\System32\dwmapi.dll 6.1.7600.16385
advapi32.dll C:\Windows\System32\advapi32.dll 6.1.7600.16385
sechost.dll C:\Windows\System32\sechost.dll 6.1.7600.16385
mscorwks.dll C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorwks.dll 2.0.50727.5466
msvcr80.dll C:\Windows\winsxs\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_88df89932faf0bf6\msvcr80.dll 8.0.50727.4940
mscorlib.ni.dll C:\Windows\assembly\NativeImages_v2.0.50727_64\mscorlib\51a23687fdafc32b697f5a719e364651\mscorlib.ni.dll 2.0.50727.5466
CRYPTBASE.dll C:\Windows\System32\CRYPTBASE.dll 6.1.7600.16385
mscorjit.dll C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorjit.dll 2.0.50727.5467
System.ni.dll C:\Windows\assembly\NativeImages_v2.0.50727_64\System\6be6efa1e2ffc9d46e99839edac5c5a8\System.ni.dll 2.0.50727.5467
System.Drawing.ni.dll C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Drawing\672fc9526d8954656bcb46e42082e09c\System.Drawing.ni.dll 2.0.50727.5467
System.Windows.Forms.ni.dll C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Windows.Forms\18f31a371a986b6f6b968530d8b89e25\System.Windows.Forms.ni.dll 2.0.50727.5468
version.dll C:\Windows\System32\version.dll 6.1.7600.16385



Contents of XML FIle
<?xml version="1.0" encoding="UTF-16"?>
<WERReportMetadata>
<OSVersionInformation>
<WindowsNTVersion>6.1</WindowsNTVersion>
<Build>7601 Service Pack 1</Build>
<Product>(0xa): Windows Server 2008 R2 Enterprise</Product>
<Edition>ServerEnterprise</Edition>
<BuildString>7601.18113.amd64fre.win7sp1_gdr.130318-1533</BuildString>
<Revision>1130</Revision>
<Flavor>Multiprocessor Free</Flavor>
<Architecture>X64</Architecture>
<LCID>1033</LCID>
</OSVersionInformation>
<ParentProcessInformation>
<ParentProcessId>1968</ParentProcessId>
<ParentProcessPath>C:\Windows\explorer.exe</ParentProcessPath>
<ParentProcessCmdLine>C:\Windows\Explorer.EXE</ParentProcessCmdLine>
</ParentProcessInformation>
<ProblemSignatures>
<EventType>APPCRASH</EventType>
<Parameter0>Login VSI Management Console.exe</Parameter0>
<Parameter1>4.0.42.1555</Parameter1>
<Parameter2>517fc1c4</Parameter2>
<Parameter3>KERNELBASE.dll</Parameter3>
<Parameter4>6.1.7601.18015</Parameter4>
<Parameter5>50b8479b</Parameter5>
<Parameter6>e0434f4d</Parameter6>
<Parameter7>0000000000009e5d</Parameter7>
</ProblemSignatures>
<DynamicSignatures>
<Parameter1>6.1.7601.2.1.0.274.10</Parameter1>
<Parameter2>1033</Parameter2>
</DynamicSignatures>
<SystemInformation>
<MID>4EEA5862-E698-4776-AA0C-1B02D1098A9B</MID>
<SystemManufacturer>Microsoft Corporation</SystemManufacturer>
<SystemProductName>Virtual Machine</SystemProductName>
<BIOSVersion>090006</BIOSVersion>
</SystemInformation>
</WERReportMetadata>

Attachments:

Please Log in to join the conversation.

More
21 May 2013 21:54 #1039

Hi All,

Thank you for reporting the errors. I will try to reproduce the errors and will contact you with updates and/or if I need more information. Thanks,

Regards,

Omar

Please Log in to join the conversation.

  • AJParry
  • AJParry's Avatar
05 Jun 2013 07:47 #1069

Hi,

I am experiencing the same issue? with a virtual [ESX vmware] server running Windows 2008 R2 SP1. After the install the console crashes...It also crashes if you apply the patch.

Strangely though if you connect to the console from a different location, ie no the server the install was performed on, browsing to the console through the share - it doesnt crash and it will load.

Cheers,

Andy

Please Log in to join the conversation.

More
05 Jun 2013 08:01 #1071

Hi Andy,

Could you also provide us the debugging information.
This will help us resolving the issue. Thank you!

Kind regards,
Ryan Bijkerk

Please Log in to join the conversation.

  • AJParry
  • AJParry's Avatar
05 Jun 2013 09:25 #1079

Hi Ryan.

Rolled back the server and reran the install [Ran as administrator] with run console ticked. Following error generated when trying to launch VSI Management Console after the base install:

Description: Stopped working

Problem signature:
Problem Event Name: APPCRASH
Application Name: Login VSI Management Console.exe
Application Version: 4.0.1.1590
Application Timestamp: 518a0e7f
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7601.18015
Fault Module Timestamp: 50b83c8a
Exception Code: e0434f4d
Exception Offset: 0000c41f
OS Version: 6.1.7601.2.1.0.272.7
Locale ID: 2057

The item written to the Application event log is as follows:
Faulting application name: Login VSI Management Console.exe, version: 4.0.1.1590, time stamp: 0x518a0e7f
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18015, time stamp: 0x50b83c8a
Exception code: 0xe0434f4d
Fault offset: 0x0000c41f
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13


I then performed the Patch install [ran as administrator] with run console ticked.

Description:
Stopped working

Problem signature:
Problem Event Name: APPCRASH
Application Name: Login VSI Management Console.exe
Application Version: 4.0.1.1590
Application Timestamp: 518a0e7f
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7601.18015
Fault Module Timestamp: 50b83c8a
Exception Code: e0434f4d
Exception Offset: 0000c41f
OS Version: 6.1.7601.2.1.0.272.7
Locale ID: 2057

The item written to the event log is as follows:

Faulting application name: Login VSI Management Console.exe, version: 4.0.1.1590, time stamp: 0x518a0e7f
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18015, time stamp: 0x50b83c8a
Exception code: 0xe0434f4d
Fault offset: 0x0000c41f
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13

However if I browse from a different machine to the actual console UNC path:
\\<servername>\VSIShare\_VSI_ManagementConsole\Login VSI Management Console.exe

The console will load and you will see the screen , see attachment.

Another point - the install doesnt create any start menu icons? I presume this is by design as the product can be accessed remotely?

However I also notice that it isnt listed within the Add / Remove Programs on the server - so how do you uninstall the application?

Andy

Attachments:

Please Log in to join the conversation.

More
05 Jun 2013 11:25 #1080

Andy,

Can you upload the installation log found at %Temp%\VSI\log\VSI_Installer.log. If the forum doesn't allow .log files, the file is too large or if you are not comfortable sharing the information over the internet, you can also send it to This email address is being protected from spambots. You need JavaScript enabled to view it.

Please Log in to join the conversation.

  • AJParry
  • AJParry's Avatar
05 Jun 2013 11:53 #1081

Hi,

no temp directory on the server. I have found the logfile you mentioned though. It is written to
%USERPROFILE%\AppData\Local\Temp\VSI\log\VSI_Installer.log

I will email the logfile to support.

It has now stopped working though from a remote system, after I applied the patch.

Cheers,

Andy

Please Log in to join the conversation.

More
05 Jun 2013 12:41 #1082

Thank you for the logfile. I have investigated the log file and didn't find any issues. I have forwarded the issue to our developers. I will keep you updated on the resolution.

In the mean time you can run the management console from a different machine.

Please Log in to join the conversation.

  • AJParry
  • AJParry's Avatar
05 Jun 2013 12:57 #1083

Well I have a problem now running it from another machine, it fails. This also creates a logfile so I will send that to support also.Entry in the event log is as follows:


Fault bucket , type 0
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: login vsi management console.exe
P2: 4.0.1.1590
P3: 518a0e7f
P4: mscorlib
P5: 2.0.0.0
P6: 503f01b1
P7: 3452
P8: 119
P9: System.IO.DirectoryNotFound
P10:

Attached files:
%USERPROFLE%\AppData\Local\Temp\WER7A3D.tmp.WERInternalMetadata.xml

These files may be available here:
%USERPROFLE%\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_login vsi manage_9654c8ddadd4de72da9dcfb456f7c0df8a1b8932_0d6c82e5

Analysis symbol:
Rechecking for solution: 0
Report Id: 26e4475f-cddf-11e2-a41b-001e8cf14fb7
Report Status: 1

This is trying to access it from a 64 bit windows 7 SP1 machine - the server as mentioned earlier is a windows 2008 R2 Sp1 machines.

Please Log in to join the conversation.

  • AJParry
  • AJParry's Avatar
05 Jun 2013 13:05 #1084

Hi

I resolved this issue, well I think I did, accessing from a remote machine..I had created a shortcut and hadnt specified a startin directory which I presume is why there was an error in the log called:

System.IO.DirectoryNotFound

I specified the target for exe "\\<servername>\VSIShare\_VSI_ManagementConsole\Login VSI Management Console.exe"

AND added the path to the start in directory

"\\<servername>\VSIShare\_VSI_ManagementConsole\"

And it is working from a remote machine again now.

Still generates the fault in the KERNELBASE.dll if I run it locally on the server

Please Log in to join the conversation.

  • Sridhar_bu
  • Sridhar_bu's Avatar
10 Jun 2013 06:42 #1105

Hi,

I had the same issue when trying to configure the tool. I got the error as attached below.




Problem signature:
Problem Event Name: APPCRASH
Application Name: Login VSI Management Console.exe
Application Version: 4.0.1.1590
Application Timestamp: 518a0e7f
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7601.18015
Fault Module Timestamp: 50b83c8a
Exception Code: e0434f4d
Exception Offset: 0000c41f
OS Version: 6.1.7601.2.1.0.272.7
Locale ID: 2057


Resolution : Enable .net framework 3.5 on the W2K2008 R2. This resolved my issue of application crashing.

Attachments:

Please Log in to join the conversation.

More
11 Jun 2013 07:33 #1107

Hi Sridhar_bu,

Thanks for sharing the resolution :).

Please Log in to join the conversation.

  • AJParry
  • AJParry's Avatar
12 Jun 2013 07:11 #1117

Hi just to expand on the solution, you can check what versions of .Net you have installed from looking at this registry hive:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP

The default is v2.0.50727 , and you will probably also have V4 installed depending on what else is on the server.

To enable .Net Framework with SP1 [Might be worth taking a snapshot or backing the server up before doing this so you can role back]

Server Manager --> Features --> Add Features --> Tick .Net Framework 3.5.1 Features

This will then ask you to Add Required Role Services [Web IIS]

You may wish to check other functionality on the server if it is running other systems but the console will now load without crashing.

And you will see versions 3.0 and 3.5 now listed within the registry hive.
I would advise running Windows Updates as I think there are at least 3 .Net 3.51 security updates to install [KB2656411, KB2736422 and KB2756921].

Thanks for the solution Sridhar_bu

Please Log in to join the conversation.

Start Delivering the Best End User Experience Today

Request a Demo

Login VSI, Inc.

3945 Freedom Circle
Suite 670
Santa Clara, CA 95054

Phone: +1 408 899 7418

300 Tradecenter
Suite 3460
Woburn, MA 01801

Phone: +1 408 899 7418

Login VSI B.V.

De Entree 85
1101 BH Amsterdam
The Netherlands

Phone: +31 20 705 1200