Macro works in Excel 2002, but Dr Watson's in Excel 2000

[Deb]

Hi

We have a VBA macro that contains a 'calculate' button, some database calls via ADO 2.1, pulls data from more than one spreadsheet in the workbook, and is on the default worksheet when the workbook is launched.

When a user with Excel 2000 launches the workbook, if they do not have any VBA add-ins in their Excel configuration, they consistently get an error that reads 'The instruction at 0x308d03a5 referenced memory at '0x0014b000". The memory could not be "read".

I've tried upgrading excel to service pack 3 and have applied all known security patches. I cannot find anything in the knowlege base about this particular memory address in a fatal Excel error.

Any help would be appreciated

 

[Wei-Dong Xu [MSFT]]

Hi,

Thanks for participating the community!

From my understanding to this issue, when you open one workbook in Excel
2000 and the Excel doesn't load any vba xla add-in, Excel 2000 will always
report memory access error. This is to say, if you enable some vba xla
add-in in the Excel, the workbook will work very well. If my understanding
doesn't locate your scenario, please feel free to let me know.

Based on my experience, you can perform several troubleshootings for this
issue:
a) start Excel in Safe mode
1. Click Start, and then click Run.
2. Click Browse, and locate the folder where Microsoft Excel is installed,
as specified earlier in this article.
3. After you locate the Excel.exe file, click the file to select it, and
then click Open.
4. At the end of the path in the Open box, type a space and then type "/s"
(without the quotation mark) so that the entire line appears similar to the
following:
""C:\Program Files\Microsoft Office\Office\Excel.exe" /s" (without the
quotation mark)

b) Remove the following registry keys.
Please note before removing, back up the registry. Furthermore, removing
the following registry keys may reset customized user settings for Excel.
HKEY_CURRENT_USER\Software\Microsoft\Office\9.0
HKEY_LOCAL_MACHINE\Software\Microsoft\Office\9.0

c) check whether there is any com add-in selected
On the Tools menu, click Add-Ins. Click to clear the check boxes for any
add-ins that are selected, and then click OK.

d) please use the listDll utility from sysinternals.com to see whether
there is any 3rd party dll is loaded into the Excel process which may be
the culprit for this error. The listdll utility is available from the link:
http://www.sysinternals.com/ntw2k/freeware/listdlls.shtml
The listdll utility is one console type application. you can type the
command below in the command window to run this utility and export the
result into one text file.
"listdlls "excel.exe" > result.txt" (without the quotation mark)

It will be appreciated you tell me all the results. I look forward to your
reply.

Enjoy a nice weekend!

Wei-Dong Xu
Microsoft Product Support Services
Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Deb]

Hi,

I tried to post this two days ago, but it did not go
through.

I tried all of the steps you advised, and running Excel in
safe mode also caused the same exception. I still had to
enable a VBA add-in in order to run the workbook.

here is the trace from listdll's:


ListDLLs V2.23 - DLL lister for Win9x/NT
Copyright (C) 1997-2000 Mark Russinovich
http://www.sysinternals.com

-----------------------------------------------------------
-------------------
EXCEL.EXE pid: 246
Command line: "C:\Program Files\Microsoft
Office\Office\EXCEL.EXE"

Base Size Version Path
0x30000000 0x6d7000 9.00.0000.3822 C:\Program
Files\Microsoft Office\Office\EXCEL.EXE
0x77f60000 0x5e000 4.00.1381.0298 C:\WINNT\System32
\ntdll.dll
0x77dc0000 0x3f000 4.00.1381.0281 C:\WINNT\system32
\ADVAPI32.dll
0x77f00000 0x5e000 4.00.1381.0300 C:\WINNT\system32
\KERNEL32.dll
0x77e70000 0x52000 4.00.1381.7229 C:\WINNT\system32
\USER32.dll
0x77ed0000 0x2c000 4.00.1381.7177 C:\WINNT\system32
\GDI32.dll
0x77e10000 0x57000 4.00.1381.7230 C:\WINNT\system32
\RPCRT4.dll
0x308c0000 0x55c000 9.00.0000.3821 C:\Program
Files\Microsoft Office\Office\MSO9.DLL
0x77b20000 0xb1000 4.00.1381.7230 C:\WINNT\system32
\ole32.dll
0x770f0000 0x1fd000 2.00.2600.0002 C:\WINNT\System32
\msi.dll
0x77bf0000 0x7000 4.00.1381.0319 C:\WINNT\System32
\rpcltc1.dll
0x71280000 0x6000 5.50.4807.2300 C:\WINNT\system32
\MSIDLE.DLL
0x77c40000 0x13c000 4.00.1381.0332 C:\WINNT\System32
\shell32.dll
0x716f0000 0x8a000 5.81.4807.2300 C:\WINNT\system32
\COMCTL32.dll
0x65340000 0x95000 2.40.4514.0001 C:\WINNT\System32
\oleaut32.dll

 

[Wei-Dong Xu [MSFT]]

Hi Deb,

Thank you for replying and the log for the troubleshooting!

You can create one new workbook and then add one marco code with the
button, for example a "hello world" macro for the button click event. Then
disable all the com add-in to open the new workbook to see whether the
error will appear again.

If appear, I'd suggest you can perform one repair installation for Excel
2000.
If doesn't appear, the original workbook may have some error. You can
follow the kb article to try to repair this file.
179871 Methods for recovering data from damaged Excel 2000 workbooks
http://support.microsoft.com/?id=179871

Please feel free to let me know if you have any question. Look forward to
hearing from you.

Enjoy a nice weekend!

Wei-Dong Xu
Microsoft Product Support Services
Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.