Page 1 of 2 12 LastLast
Results 1 to 15 of 18
  1. #1
    Lounger
    Join Date
    Mar 2002
    Posts
    33
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Crash with Macros (Word XP)

    Whenever I attempt to run a macro, either by clicking on the macro in Tools | Macros or using a keyboard shortcut, Word crashes. I have deleted Normal.dot, opened a clean version and copied the old macros over; same problem. I used Detect and Repair. Same problem. I even "updated" W2K to WXP. Same problem.

    Anyone have any ideas?

    Brett

  2. #2
    BAM
    Guest

    Re: Crash with Macros (Word XP)

    Hi Brett,

    What is the exact error message you recieve?

    Have you eliminated the possibilty of one of your macros containing an error? Compile your module(s) in the VBA Editior and see if any errors are indicated.
    ~~~~~~~~~~~
    Cheers! <img src=/S/smile.gif border=0 alt=smile width=15 height=15>

  3. #3
    Lounger
    Join Date
    Mar 2002
    Posts
    33
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Crash with Macros (Word XP)

    When I tried to compile it, I received the same error I got when I tried to run the macro:

    "Microsoft Word has encountered a problem and needs to close. We are sorry for the invonvenience."

    The Error signature is:

    AppName: winword.exe
    AppVer: 10.0.2627.0
    ModName: oleaut32.dll
    ModVer: 3.50.5011.0
    Offset: 00015a79

    Any idea what I might be able to do to identify/fix the problem?

    Brett

  4. #4
    BAM
    Guest

    Re: Crash with Macros (Word XP)

    Hi Brett,

    Just to verify that the DLL is the correct version, locate these files:
    Oleaut32.dll
    Olepro32.dll
    Stdole2.tlb

    Right-click each one and select Properties. The last four digits of the version number should match. If oleaut32.dll is different then close all Office apps, rename oleaut32.dll, start Word and see if it automatically goes through a Detect and Repair. If it doesn't then manually use Detect and Repair located under Help.

    Otherwise, what does the macro do exactly?

  5. #5
    Lounger
    Join Date
    Mar 2002
    Posts
    33
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Crash with Macros (Word XP)

    They all have the same version numbers--5011.0.

    The macros are very benign--they just insert text in a document. Nothing low level at all; in fact, they all were recorded.

    Brett

  6. #6
    Platinum Lounger
    Join Date
    Feb 2001
    Location
    Yilgarn region of Toronto, Ontario
    Posts
    5,453
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Crash with Macros (Word XP)

    I started getting this message a couple of weeks ago. (win95/Office97SR2)

    Run-time error '59201'
    Application-defined or object-defined error


    I thought it was because I'd installed Corel over MSoft, so re-built my system (starting with Format C <img src=/S/smile.gif border=0 alt=smile width=15 height=15>.

    Then I started getting this message:

    Can't find DLL entry point OleLoadPictureFieEx in oleaut32.dll


    Yesterday I rebuilt my system (Format c <img src=/S/smile.gif border=0 alt=smile width=15 height=15> with only Wind5 and Office97SR2, default options all around. I still get the errors.


    I have about 30 templates, password protected, which have been working - except for known bugs - for anything from a ferw months to a few years.

    I now find that SOME templates can be opened and inspected with no trouble. Some cause the red-x error as soon as I offer the password.


    It's *as if* some false DLL was in force at the time I had some templates open (for example, maybe the last six templates I'd modified), and that this false DLL corrupted those templates.



    I'm at my wit's end, and he doesn't have much of a clue either.

  7. #7
    BAM
    Guest

    Re: Crash with Macros (Word XP)

    Hi Chris,

    Since you are using Windows 95 see if this article applies:
    <A target="_blank" HREF=http://support.microsoft.com/support/kb/articles/Q139/4/32.asp>http://support.microsoft.com/support/kb/ar...s/Q139/4/32.asp</A>
    ~~~~~~~~~~
    Cheers! <img src=/S/flags/USA.gif border=0 alt=USA width=30 height=18>

  8. #8
    Platinum Lounger
    Join Date
    Feb 2001
    Location
    Yilgarn region of Toronto, Ontario
    Posts
    5,453
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Crash with Macros (Word XP)

    Thanks BAM. Installed it, rebooted as told, and I still get problems. I now experiment with different templates ( I counted 36 subdirectories, each with a template "product") each time.


    Just tried my ProcedureClipper. From Explorer I double-click on PClip136.dot and sure 'nuff Word fires up. I elect to Enable Macros, then choose Tools, Macro, VBE.

    In the project(?) window I double-click on the PClip136 item and am prompted for the password, which I give, and click OK, generating the red-x special message (details pasted below)


    WINWORD caused an invalid page fault in
    module VBA332.DLL at 0217:6517dabe.
    Registers:
    EAX=01230018 CS=0217 EIP=6517dabe EFLGS=00210286
    EBX=ffff0009 SS=021f ESP=0062f004 EBP=0000004c
    ECX=7fffffff DS=021f ESI=01255e98 FS=1daf
    EDX=00000130 ES=021f EDI=01255e94 GS=0000
    Bytes at CS:EIP:
    39 6b 04 0f 87 c6 c0 06 00 85 db 0f 84 ce c0 06
    Stack dump:
    0062f038 7fffffff 01255e98 012308a0 651a339d 01255e94 00000000 00000005 012308a0 0000002e 004663a4 00433a18 0043452c 0062f09c 651a356e 012308a0


    I am convinced that some software I had downloaded a few weeks ago, but who knows what, had replaced a DLL, and that DLL had caused corruption in some templates, which Word97/SR2 original DLL cannot handle.


    Reformatting c:, re-installing Win97/Office97 and nothing else, and still getting the problems seems to indicate some sort of corruption in my password-protected templates.


    You're going to ask me why I don't try opening a previous version of any template, right? Well, each morning I make my backups to a removable disk, and yesterday, while re-installing a clean C: on THAT unit (so that my backup drive is immediately bootable), I inadvertently used the MSDOS 6.22 Format command (instead of the Win95Command Format command), which did its little FDisk number on the Win95 format FAT. Bye Bye backups and archives from several years (sob!)

  9. #9
    BAM
    Guest

    Re: Crash with Macros (Word XP)

    Hi Chris,

    VBA332.DLL was replaced in SR1. Right-click the DLL and select Properties and take a look at the Version number.

    3.0.0.6908: unpatched Office 97
    3.0.0.7019: patched Office 97

    You may need to reinstall SR1 along with all of the patches for Office 97.
    ~~~~~~~~~~~~
    Cheers! <img src=/S/flags/USA.gif border=0 alt=USA width=30 height=18>

  10. #10
    Platinum Lounger
    Join Date
    Feb 2001
    Location
    Yilgarn region of Toronto, Ontario
    Posts
    5,453
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Crash with Macros (Word XP)

    I have the later version.

    I don't believe this is an Office97 problem, honest. I posted more to record the problem than expecting a solution.

    About every nine months I rebuild my system, starting with "Format C:". I have a list of about 50 steps i take to get it back into shape, installing Win95, three office suites from CD, faxing, dial-up connection etc. I've been doing this since 1996.

    When I start to get major problems with my system, I figure that it's on account of something corrupting the 5MB registry, or a cruddy DLL etc, and i reformat drive C: and start over.

    This technique has worked for five years.

    Suddenly a rebuild does NOT solve the problem, which suggests that the trigger is in the template files. That suggests some form of corruption, possibly by a stand-in DLL that Word97 used, not knowing it was a corrupt/unsuitable DLL, which DLL then corrupted my templates.

    When I rebuild the system and go back to the good DLLs from the installation CDs, they can't handle the corruption that the rogue DLL installed.


    It's trite to say "Ive installed like this before and never had a problem", but it's true. I'm using the original Win95 upgrade CD and the SR2 CD I was sent back around 1998.



    Please don't agonise too much over this; I have a decrepit old system. I think I would have been acting more kindly if I'd included a "for information only" tag on my earlier posting. i wanted to add data to the original thread in case this happened to some other schnuck.


    OTOH if you agree with my logic (about rogue DLLs corrupting my template), confirmation of my thinking would make me feel good.

  11. #11
    BAM
    Guest

    Re: Crash with Macros (Word XP)

    Hi Chris,

    I don't think a DLL is corrupting your template. A Dynamic Link Library is an application extension - they just provide information.

    In this case you have a problem with a VBA library. <img src=/S/grin.gif border=0 alt=grin width=15 height=15> So I'd say this is a problem that needs rectified.

    Open a template that has a problem and in the VBA editor go to Tools/References. Are there any missing references listed?

    Do a search for VBA332.DLL and see if more than one is found.

    Since this DLL doesn't register itself, try re-registering it. Go to Start/Run and run the following:

    regsvr32.exe "C:...vba332.dll"

    (Of course you need to change the path to the correct location of the DLL. It should be your Microsoft SharedVBA Folder)

    Also, did you change the default path on any of your installs?

    btw, taking drastic measures to rectify what could be a simple problem eliminates a perfect situation to learn something new! <img src=/S/laugh.gif border=0 alt=laugh width=15 height=15>

    On that same note, typically most problems aren't the fault of a DLL, *.exe, Registry (unless you've been tinkering <img src=/S/grin.gif border=0 alt=grin width=15 height=15> ), etc. and formatting/rebuilding is usually just a band-aid fix. In most cases the problems usually return at some point. <img src=/S/smile.gif border=0 alt=smile width=15 height=15>
    ~~~~~~~~~~~~~~~
    Cheers! <img src=/S/flags/USA.gif border=0 alt=USA width=30 height=18>

  12. #12
    Platinum Lounger
    Join Date
    Feb 2001
    Location
    Yilgarn region of Toronto, Ontario
    Posts
    5,453
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Crash with Macros (Word XP)

    Sorry for the delay in replying. Amongst other news, my new case, MBoard, CPU arrives later today (Wednesday). Also i have managed to work out how to connect again to my ISP ......

    > I don't think a DLL is corrupting your template. A Dynamic Link Library is an application extension - they just provide information.

    Hmmm. I thought a DLL has executable code; my theory is that a rogue DLL corrupted Under142.dot. I managed to get a copy of Under140.dot from a web site and am using that (it is, of course, stripped of all comments and white space a la Payne Consulting). Most other templates don't seem to be corrupted.

    > Open a template that has a problem and in the VBA editor go to Tools/References.

    Ah! Therein lies the problem. In Word97SR2 I go to open Under142.dot and it opens. Not a problem. In VBE I double-click on the project, am prompted for the password, type in the password and click OK, whereupon I get the "has performed an illegal operation" with the red cross. Word/VBE shuts down. I can't open the Under142 to check references. If I open ye olde Under140 everything is fine - password accepted via VBE. If I then Word-open Under142 and try to supply its password - red-cross.

  13. #13
    BAM
    Guest

    Re: Crash with Macros (Word XP)

    > I don't think a DLL is corrupting your template. A Dynamic Link Library is an application extension - they just provide information.

    >>Hmmm. I thought a DLL has executable code; my theory is that a rogue DLL corrupted Under142.dot. I managed to get a copy of Under140.dot from a web site and am using that (it is, of course, stripped of all comments and white space a la Payne Consulting). Most other templates don't seem to be corrupted.<<

    Yes a DLL can contain modular program routines, but I have never heard of a DLL causing corruption to a file. I guess to me this is like saying "the FilePrintDefault command corrupted my document". <img src=/S/smile.gif border=0 alt=smile width=15 height=15> Now the DLL itself may be corrupt or there could be corruption in the reference to the DLL...

    <<I go to open Under142.dot and it opens. Not a problem. In VBE I double-click on the project, am prompted for the password, type in the password and click OK, whereupon I get the "has performed an illegal operation>>

    If it were a missing reference then you should be able to open it so I would agree that the project itself contains corruption of some sort (now what caused it - who knows <img src=/S/grin.gif border=0 alt=grin width=15 height=15>)

    Are you able to copy the modules via the Organizer to another template?

    btw, what does the Under142.dot template do?

  14. #14
    Platinum Lounger
    Join Date
    Feb 2001
    Location
    Yilgarn region of Toronto, Ontario
    Posts
    5,453
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Crash with Macros (Word XP)

    How about if I'd d/l a shareware application that had installed a DLL over an existing copy. I'd have an out-of-date, or at least, incompatible DLL. It would LOOK as if I had a corrupted DLL; I'd have a substitute. Then when I reinstalled Office97 I'd get the "good" DLL back, which might then get confused by what the BAD DLL had left in my template?


    (Still struggling with machine faults with the new MBoard/CPU/RAM/OS ....)

  15. #15
    JustCallMeAl
    Guest

    Re: Crash with Macros (Word XP)

    Chris, I noticed that your first post on this topic was September 20. Did you happen to get hit with the NIMDA virus?

    Our office did. Four hours after its release! Came down on us like a Boeing 757--if you get what I mean. Like to have shut down the office for a good week. Everytime IS would get the system clean, someone would reinfect the system.

    Anyway, since then, we have been having some real rogue problems. Nothing anyone can place their fingers on, but many point to September 18. In fact, on September 18, 9:20 am PDT, I was demonstrating a new procedure. Everything worked fine. The next day, the procedure didn't work. It wasn't the procedure per se, but printing and print preview quit working properly. We think that the printer driver or some common DLL or OCX (?) all of a sudden corrupted. And it has caused 8 printers to stop working properly--but only on some computers.

    From that circumstantial evidence, I am convinced that more happened because of NIMDA than we initially thought.

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •