Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

VB Application crash accessing Excel DrWatson errorlog help needed! 1

Status
Not open for further replies.

fsteeman

Programmer
Jul 17, 2002
103
0
0
DK
Hello,

I was wondering if anyone who understands assembly language or machine code could help me what to do about this weird problem I have now.

We are running an application that I developed under VB and has always worked perfectly, but since a weeks or two it has been crashing everytime it accesses Excel files, but only on one particular computer, not on any other, and the same error does not occur when running the application in the VB environment.

I have been trying several things like getting the latest Windows and Office updates /service packs and what have ya, of no avail. I have looked at the errorlog that DrWatson generated, but have trouble figuring it out, so this is where you may help. I have copied excerpts of the errorlog in the hope that they may provide a clue as to what goes wrong exactly and whatI should do to prevent this problem from occuring. I was considering updating to Office 2003 to see if that helps, but really prefer not to. Any help on this is greatly appreciated!

Errorlog:

Application exception occurred:
App: (pid=1428)
When: 1/7/2004 @ 11:15:50.766
Exception number: c0000005 (access violation)

*----> System Information <----*
Number of Processors: 1
Processor Type: x86 Family 6 Model 8 Stepping 3
Windows 2000 Version: 5.0
Current Build: 2195
Service Pack: 3
Current Type: Uniprocessor Free

*----> Task List <----*
-omitted-

State Dump for Thread Id 0x260

eax=096ba43c ebx=0012f328 ecx=66008a00 edx=09692314 esi=0969e688 edi=096bab88
eip=00000000 esp=0012f24c ebp=0012f634 iopl=0 nv up ei pl nz na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202


function: <nosymbols>
FAULT ->00000000 ???
00000001 ???
00000002 ???
00000003 ???

*----> Stack Back Trace <----*

FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
0012F248 004A0035 096BA43C 09692314 0000000A 0118DAC4 !<nosymbols>
0012F634 0049F409 0969E688 0012F674 0012F744 00000001 !<nosymbols>
0012F668 6602AD73 0969E688 0012F684 00409FFB 0969E708 !<nosymbols>
0012F674 00409FFB 0969E708 00409BC0 0012F6D0 6602AD50 MSVBVM60!BASIC_CLASS_Invoke
0012F684 6602AD50 00409FFB 0012F740 00000002 00000000 !<nosymbols>
0012F6D0 66023023 0012F780 0012F740 00000002 0118D734 MSVBVM60!BASIC_CLASS_Invoke
0012F7A4 66022EB2 0118D734 0118C6F4 01165710 00000002 MSVBVM60!EVENT_SINK_AddRef
0012F7C8 660C21F2 0118D734 00000000 00000000 0118D734 MSVBVM60!EVENT_SINK_AddRef
0012F7F8 66021269 0118D734 000103CA 00002111 00000005 MSVBVM60!DllCanUnloadNow
0012F820 66020341 0118D734 000103CA 00002111 00000005 MSVBVM60!EVENT_SINK_AddRef
0012F87C 6607A250 000103CA 00002111 00000005 000103CA MSVBVM60!EVENT_SINK_AddRef
0012F8A0 66036323 0118CF0C 000203BE 00000111 00000005 MSVBVM60!IID_IVbaHost
0012F90C 660205BC 011671B8 000203BE 00000111 00000005 MSVBVM60!Zombie_QueryInterface
0012FA8C 66021269 0118CF0C 000203BE 00000111 00000005 MSVBVM60!EVENT_SINK_AddRef
0012FAB4 66020341 0118CF0C 000203BE 00000111 00000005 MSVBVM60!EVENT_SINK_AddRef
0012FB10 77E3A244 000203BE 00000111 00000005 000103CA MSVBVM60!EVENT_SINK_AddRef
0012FB30 77E16362 66020297 000203BE 00000111 00000005 user32!SetWindowPlacement
0012FB60 77E17341 0065CAB8 00000111 00000005 000103CA user32!IsWindowVisible
0012FB80 77E30879 000203BE 00000111 00000005 000103CA user32!SendMessageW
0012FC20 77E2DF90 000103CA 00000202 00000000 000B002D user32!CreatePopupMenu
0012FC44 77E3A244 000103CA 00000202 00000000 000B002D user32!LoadMenuA
0012FC64 77E16B21 77E2DF47 000103CA 00000202 00000000 user32!SetWindowPlacement
0012FC88 77E16B44 77E2DF47 000103CA 00000202 00000000 user32!ScreenToClient
0012FCA8 66035B47 77E2DF47 000103CA 00000202 00000000 user32!CallWindowProcA
0012FD14 660C24C8 01165710 000103CA 00000202 00000000 MSVBVM60!Zombie_QueryInterface
0012FD3C 66021269 0118D734 000103CA 00000202 00000000 MSVBVM60!DllCanUnloadNow
0012FD64 66020341 0118D734 000103CA 00000202 00000000 MSVBVM60!EVENT_SINK_AddRef
0012FDC0 77E3A244 000103CA 00000202 00000000 000B002D MSVBVM60!EVENT_SINK_AddRef
0012FDE0 77E145E5 66020297 000103CA 00000202 00000000 user32!SetWindowPlacement
0012FE6C 77E15B51 0012FE90 00000001 6601496C 0012FE90 user32!TranslateMessageEx
0012FEB8 660148A5 FFFFFFFF 0116374C 01160000 01163744 user32!DispatchMessageA
0012FEFC 66014783 0116381C FFFFFFFF 00000594 FFFFFFFF MSVBVM60!_vbaInStr
6601A340 66010E00 6601178A 660D40C8 660D40F3 66010E93 MSVBVM60!_vbaInStr
660D3416 0C2474FF FF0C408B 8B0C2474 11FF5008 8B000CC2 MSVBVM60!BASIC_CLASS_QueryInterface
0424448B 00000000 00000000 00000000 00000000 00000000 <nosymbols>

State Dump for Thread Id 0x29c

eax=00000158 ebx=77f87f20 ecx=00144768 edx=00000000 esi=00144768 edi=00000100
eip=77f88a97 esp=0225fe28 ebp=0225ff74 iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000206


function: ZwReplyWaitReceivePortEx
77f88a8c b8ac000000 mov eax,0xac
77f88a91 8d542404 lea edx,[esp+0x4] ss:032bd3fb=????????
77f88a95 cd2e int 2e
77f88a97 c21400 ret 0x14
77f88a9a 8bff mov edi,edi

*----> Stack Back Trace <----*

FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
0225FF74 77D56D5E 77D39AD0 00144768 40144234 00000070 ntdll!ZwReplyWaitReceivePortEx
0225FFA8 77D41C6D 0013E158 0225FFEC 77E8B2D8 00142FF8 rpcrt4!TowerConstruct
0225FFB4 77E8B2D8 00142FF8 40144234 00000070 00142FF8 rpcrt4!I_RpcServerInqTransportType
0225FFEC 00000000 00000000 00000000 00000000 00000000 kernel32!lstrcmpiW

State Dump for Thread Id 0x230

eax=77ab464e ebx=00000102 ecx=001435b0 edx=00000000 esi=77f882f8 edi=0235ff74
eip=77f88303 esp=0235ff60 ebp=0235ff7c iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000206


function: NtDelayExecution
77f882f8 b832000000 mov eax,0x32
77f882fd 8d542404 lea edx,[esp+0x4] ss:033bd533=????????
77f88301 cd2e int 2e
77f88303 c20800 ret 0x8
77f88306 8bff mov edi,edi

*----> Stack Back Trace <----*

FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
0235FF7C 77EA9D5F 0000EA60 00000000 77AB862F 0000EA60 ntdll!NtDelayExecution
00007530 00000000 00000000 00000000 00000000 00000000 kernel32!Sleep

*----> Raw Stack Dump <----*
-omitted-

The list goes on, but perhaps this is enough data?
 
Hi fsteeman,

The error log from DrWatson sometimes doesn't helps, especially when you said it happened only on one computer! The offended lines of code, may be causing by bad installation (such as corrupt / bad CRC files). So it might not because of a bad instruction

If I were you, I would try to cleanup the installation first. Remove all offended application and cleanup the registry. Then start to reinstall one by one.

The same thing happened to me either, where from about 25 machine, one machine always crash when my apps try to open Excel. Later on I found out that because the person already opened Excel (multiple instances) also had opened some other software (such as IE, OE). The faults is the machine running out of windows resources :)

I can't help much in this case, but I hope it will be some information.

Regards

-- AirCon --
 
Thanks, I will see what I can do. Any tips on cleaning the registry?
 
You can use RegEdit then search any key that you think belong to the apps. Delete it (yes I did this).
If you have tools like Norton RegEdit, you can use it. It's a lot easier :)

When you start the installation again, make sure you don't have any AntiVirus running. I had experienced that this software sometimes can causing the corruption (CRC error). And as always, BACKUP your registry and other important data

-- AirCon --
 
Thanks. Once I have uninstalled Office. I will deleting all (remaining) Excel-keys from HKEY_CLASSES_ROOT and then install Office again. I hope this helps...

Cheers, Fedor
 
Alas, this did not work! :-( I may now need to have Office 2003 installed. Maybe that'll do the trick...
 
I'm sorry to hear that :-(
I can't offer any help other than that. Hope you get lucky trying the new one.

-- AirCon --
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top