PC Review


Reply
Thread Tools Rate Thread

Crashed application pointing to IEFRAME.DLL and SHLWAPI.DLL

 
 
Peter
Guest
Posts: n/a
 
      7th Oct 2008
Hi,

I installed an application on my Vista (Business SP1, IE 7.0.6001.1800),
when I tried to run it, it crashed and there are two errors at Event Viewer
(Application).

The first one is as follow:

The VB Application identified by the event source logged this Application
eClaim Manager: Thread ID: 2020 ,Logged:
Error updating the Version table:
Time='10/07/08 14:17:05'
App='eClaim Manager:3.6.0'
Server='tt10920VISTA'
InTrans=No
Method: modGlobalFunctions::CheckInstallINI
Number: 101 = &H65 = vbObjectError + 2147221605 = emAppFirst + 2147216407
Source: CheckInstallINI
Description: Error updating the Version table:
Trace: modGlobalFunctions::CheckInstallINI()


The second is as follows:

The VB Application identified by the event source logged this Application
eClaim Manager: Thread ID: 2020 ,Logged:
Failed to load control 'MxctlListView' from mxListViewControl.ocx. Your
version of mxListViewControl.ocx may be outdated. Make sure you are using
the version of the control that was provided with your application.
Time='10/07/08 14:17:09'
App='eClaim Manager:3.6.0'
Server='tt10920VISTA'
InTrans=No
Method: modGlobalFunctions::Main
Number: 372 = &H174 = vbObjectError + 2147221876 = emAppFirst +
2147216678
Source: ECM_CM
Description: Failed to load control 'MxctlListView' from
mxListViewControl.ocx. Your version of mxListViewControl.ocx may be
outdated. Make sure you are using the version of the control that was
provided with your application.
Trace: modGlobalFunctions::Main()


When I open the installed mxListViewControl.ocx with Dependency Walker, it
showed warning on IEFRAME.DLL (function #160, #159, #141, and more) and
SHLWAPI.DLL (function #467 and more).

The weired thing is that the same application (package) works fine on the
other Vista (Business SP1 with same IE version).

Now I want to see what's wrong on my Vista, but the two files (.dll) have
exactly the same info on the two Vista systems, what else can I do?


Thanks,
Peter


 
Reply With Quote
 
 
 
 
Mark L. Ferguson
Guest
Posts: n/a
 
      8th Oct 2008
The install for the apps failed to install to a folder that they had
permission to write to. Probably, the INI file is in a folder with no
permissions for the user.

--
Please use the Communities guidelines when posting.
http://www.microsoft.com/wn3/locales...help_en-us.htm
Use the "Ratings" feature. It helps the new users.
Mark L. Ferguson MS-MVP
https://mvp.support.microsoft.com/profile/Mark.Ferguson

"Peter" <(E-Mail Removed)> wrote in message
news:9FA39755-A556-4CCF-B1F3-(E-Mail Removed)...
> Hi,
>
> I installed an application on my Vista (Business SP1, IE 7.0.6001.1800),
> when I tried to run it, it crashed and there are two errors at Event
> Viewer
> (Application).
>
> The first one is as follow:
>
> The VB Application identified by the event source logged this Application
> eClaim Manager: Thread ID: 2020 ,Logged:
> Error updating the Version table:
> Time='10/07/08 14:17:05'
> App='eClaim Manager:3.6.0'
> Server='tt10920VISTA'
> InTrans=No
> Method: modGlobalFunctions::CheckInstallINI
> Number: 101 = &H65 = vbObjectError + 2147221605 = emAppFirst +
> 2147216407
> Source: CheckInstallINI
> Description: Error updating the Version table:
> Trace: modGlobalFunctions::CheckInstallINI()
>
>
> The second is as follows:
>
> The VB Application identified by the event source logged this Application
> eClaim Manager: Thread ID: 2020 ,Logged:
> Failed to load control 'MxctlListView' from mxListViewControl.ocx. Your
> version of mxListViewControl.ocx may be outdated. Make sure you are using
> the version of the control that was provided with your application.
> Time='10/07/08 14:17:09'
> App='eClaim Manager:3.6.0'
> Server='tt10920VISTA'
> InTrans=No
> Method: modGlobalFunctions::Main
> Number: 372 = &H174 = vbObjectError + 2147221876 = emAppFirst +
> 2147216678
> Source: ECM_CM
> Description: Failed to load control 'MxctlListView' from
> mxListViewControl.ocx. Your version of mxListViewControl.ocx may be
> outdated. Make sure you are using the version of the control that was
> provided with your application.
> Trace: modGlobalFunctions::Main()
>
>
> When I open the installed mxListViewControl.ocx with Dependency Walker, it
> showed warning on IEFRAME.DLL (function #160, #159, #141, and more) and
> SHLWAPI.DLL (function #467 and more).
>
> The weired thing is that the same application (package) works fine on the
> other Vista (Business SP1 with same IE version).
>
> Now I want to see what's wrong on my Vista, but the two files (.dll) have
> exactly the same info on the two Vista systems, what else can I do?
>
>
> Thanks,
> Peter
>
>

 
Reply With Quote
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Creating a report after an application is crashed Robe Microsoft C# .NET 1 29th Dec 2009 04:41 PM
Application crashed on print dan dungan Microsoft Excel Programming 1 3rd Apr 2008 01:06 AM
deployment project - create virtual directory pointing to Application folder kplkumar Microsoft ASP .NET 0 2nd Jun 2006 05:55 PM
how to track an application that crashed without a message hag Windows XP General 1 6th Dec 2005 03:25 PM
PC Crashed After Uninstalling Application =?Utf-8?B?Sm9obiBBbmRyZXc=?= Windows XP General 2 21st Nov 2005 09:56 PM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 11:56 PM.