1 Reply by TonyP

  • TonyP
  • TonyP
  • Veteran
  • Offline
  • From: Somerset
  • Registered: 15-05-2006
  • Posts: 306

Re: Excel Importing: Access violation at address 004045A4 in module..

Another crash report from Excel imports. Open the sheet and choose the import format, press next and the 'file is of the wrong type'. This often occurs and subsequently the same file imports without error after an R6 restart. Any thoughts?

date/time         : 2012-06-12, 12:54:33, 595ms
computer name     : SERC-EMMAKOBLIZ
user name         : tony.price
operating system  : Windows XP Service Pack 3 build 2600
system language   : English
system up time    : 20 minutes 29 seconds
program up time   : 2 minutes 13 seconds
processors        : 3x AMD Athlon(tm) II X3 435 Processor
physical memory   : 1229/1791 MB (free/total)
free disk space   : (C:) 596.81 MB (U:) 210.72 GB
display mode      : 1152x864, 32 bit
process id        : $c50
allocated memory  : 22.93 MB
command line      : RecorderApp.exe /131746
executable        : RecorderApp.exe
exec. date/time   : 2011-01-18 14:50
version           : 6.16.2.241
madExcept version : 2.7k
exception class   : EAccessViolation
exception message : Access violation at address 004045A4 in module 'RecorderApp.exe'. Read of address 0000006F.

main thread ($f2c):
004045a4 RecorderApp.exe System              TObject.Free
004c3b1c RecorderApp.exe Menus               TMenuItem.Destroy
004514fa RecorderApp.exe Classes             TComponent.DestroyComponents
004512ff RecorderApp.exe Classes             TComponent.Destroy
004b1fdb RecorderApp.exe Controls            TControl.Destroy
004b5629 RecorderApp.exe Controls            TWinControl.Destroy
004ccc9c RecorderApp.exe Forms               TScrollingWinControl.Destroy
004cdc97 RecorderApp.exe Forms               TCustomForm.Destroy
009a1815 RecorderApp.exe Maintbar    634 +15 TfrmMain.Destroy
004514fa RecorderApp.exe Classes             TComponent.DestroyComponents
004cbb47 RecorderApp.exe Forms               DoneApplication
0042e7c9 RecorderApp.exe SysUtils            DoExitProc
00405373 RecorderApp.exe System              @Halt0
00a32a59 RecorderApp.exe RecorderApp 435 +96 initialization

thread $c54:
7c90e514 ntdll.dll                 KiFastSystemCallRet
7c90df48 ntdll.dll                 NtWaitForMultipleObjects
7c80958a kernel32.dll              WaitForMultipleObjectsEx
7e4195f3 user32.dll                MsgWaitForMultipleObjectsEx
7e4196a3 user32.dll                MsgWaitForMultipleObjects
0042b939 RecorderApp.exe madExcept CallThreadProc
0042b97b RecorderApp.exe madExcept ThreadExceptFrame
>> created by main thread ($f2c) at:
4ec67f66 gdiplus.dll               

thread $c70:
7c90e514 ntdll.dll                 KiFastSystemCallRet
7c90daa8 ntdll.dll                 NtReplyWaitReceivePortEx
0042b939 RecorderApp.exe madExcept CallThreadProc
0042b97b RecorderApp.exe madExcept ThreadExceptFrame
>> created by main thread ($f2c) at:
77e7d10d RPCRT4.dll               

thread $c78:
7c90e514 ntdll.dll                 KiFastSystemCallRet
7c90d218 ntdll.dll                 NtDelayExecution
7c8023eb kernel32.dll              SleepEx
7c802450 kernel32.dll              Sleep
0042b939 RecorderApp.exe madExcept CallThreadProc
0042b97b RecorderApp.exe madExcept ThreadExceptFrame
>> created by main thread ($f2c) at:
775309d3 ole32.dll                 

thread $c74:
7c90e514 ntdll.dll  KiFastSystemCallRet
7c90df48 ntdll.dll  NtWaitForMultipleObjects

thread $c8c:
7c90e514 ntdll.dll     KiFastSystemCallRet
7c90df58 ntdll.dll     NtWaitForSingleObject
7c8025d5 kernel32.dll  WaitForSingleObjectEx
7c80253d kernel32.dll  WaitForSingleObject

thread $e3c:
7c90e514 ntdll.dll  KiFastSystemCallRet
7c90d218 ntdll.dll  NtDelayExecution

thread $e68:
7c90e514 ntdll.dll                 KiFastSystemCallRet
7c90df48 ntdll.dll                 NtWaitForMultipleObjects
7c80958a kernel32.dll              WaitForMultipleObjectsEx
0042b939 RecorderApp.exe madExcept CallThreadProc
0042b97b RecorderApp.exe madExcept ThreadExceptFrame
>> created by main thread ($f2c) at:
77df8c8c advapi32.dll             

thread $e60:
7c90e514 ntdll.dll                 KiFastSystemCallRet
7c90daa8 ntdll.dll                 NtReplyWaitReceivePortEx
0042b939 RecorderApp.exe madExcept CallThreadProc
0042b97b RecorderApp.exe madExcept ThreadExceptFrame
>> created by thread $c70 at:
77e7d10d RPCRT4.dll               

thread $f0c:
7c90e514 ntdll.dll  KiFastSystemCallRet
7c90da48 ntdll.dll  NtRemoveIoCompletion

thread $f10:
7c90e514 ntdll.dll  KiFastSystemCallRet
7c90da48 ntdll.dll  NtRemoveIoCompletion

Data Manger
Somerset Environmental Records Centre

TonyP's Website

2 Reply by Paul Leonard

  • Paul Leonard
  • Member
  • Offline
  • From: Rotherham BRC
  • Registered: 22-01-2010
  • Posts: 36

Re: Excel Importing: Access violation at address 004045A4 in module..

Hi Tony,
My knowledge of potential - and actual - problems with R6 is very limited and this may be total nonsense but, could it have anything to do with the formatting of the individual cells of the spreadsheet, and nothing to do with the records per se contained within it?

I have experienced broadly similar issues in the past when importing from Excel files and have been able to trace some of them back to formatting 'issues', sometimes involving just one cell!

Paul

Biological Records Officer
Rotherham MBC
Rotherham Biological Records Centre

3 Reply by Gordon Barker

  • Gordon Barker
  • Veteran
  • Offline
  • Registered: 15-05-2006
  • Posts: 344

Re: Excel Importing: Access violation at address 004045A4 in module..

The other one that I think has affected me occasionally is if the XL file is open at the same time. This seems similar to that error, but can't remember exactly.

Gordon Barker
Biological Survey Data Manager
National Trust