VisualBasic Editor Error: "Could not open macro storage"
|
|
Thread rating:  |
McMaster.Michael@gmail.com - 05 Nov 2006 21:41 GMT Running OS 10.4.8, Office 2004; all updated on a G4 powerbook....
When I try and open the visual basic editor, I get the error: "Could not open macro storage" I have found some suggestions on how to fix the problem in older versions, but they aren't working for me: http://groups.google.com/group/microsoft.public.mac.office/browse_thread/thread/ 1116fe9bf6c2bc15/d3d59120467d8566?lnk=gst&q=macro+storage&rnum=1#d3d59120467d856 6
It also seems like others have had the same problem, but no solution was found: http://groups.google.com/group/microsoft.public.mac.office.word/browse_thread/th read/ee2a9879eb4970f3/3f91173e8c1117c9?lnk=gst&q=macro+storage&rnum=6#3f91173e8c 1117c9
I have done a complete removal of Office and reinstalled it (including hunting down left over pref files and MS user data folder). And I get the same problem.
Throughout the whole process, I've run disk utility and all my permission are good.
I'm at my wit's end. Please help.
Mike
John McGhie [MVP - Word and Word Macintosh] - 06 Nov 2006 11:58 GMT Hi Michael:
"Macro storage" is a partition within the file or template in use.
Check that the document you have open is a Word document, and is in Word 2004 format.
Check to see which template is attached to it, using Tools>Templates and Add-ins
Uninstalling/re-installing and trashing preferences have nothing to do with this problem. This is either the VBA editor is trying to open the macro storage in a file type that does not have any, or the template is protected and won't let the editor open it . That can happen if you have a PC template with protected code in it -- Mac Word can't decrypt the protected code, and so it can't open the macro storage. If that's what has happened, you need to open the VBA project in PC Word and remove the protection from the VBA project.
Check that the template is a .dot file (unless it's normal). Check that it is a Template file type, not a .Doc file type. And check that it is not read-only. If you get confused, use File>Open to open the template, then attempt a Save As. If Word sets the Format in that dialog to Template and changes the location to My Templates, you're good. Otherwise, it's not a template regardless of what the file name says, and that's the problem.
This can be caused by PC Macro code that fails on the Macintosh. And it may not be in the attached template: if you have somehow installed a global add-in written for the PC it will cause this condition. So check in Tools>Templates and Add-Ins to see if there are any.
Cheers
On 6/11/06 8:41 AM, in article 1162762893.634436.198800@m7g2000cwm.googlegroups.com,
> Running OS 10.4.8, Office 2004; all updated on a G4 powerbook.... > [quoted text clipped - 22 lines] > > Mike
 Signature Please reply to the newsgroup to maintain the thread. Please do not email me unless I ask you to.
John McGhie <john@mcghie.name> Microsoft MVP, Word and Word for Macintosh. Business Analyst, Consultant Technical Writer. Sydney, Australia +61 (0) 4 1209 1410
McMaster.Michael@gmail.com - 06 Nov 2006 16:47 GMT John -
I have the same problem regardless of what document or template I use. Even when I open a blank document (using the 'Normal' template), I am unable to open the VBE. There is nothing listed under the "Templates and Add-Ins..." so I don't think it's a conflict with another/bad macro.
I discovered this problem when I tried to install Endnote X. None of the commands work from with Word. Their documentation seemed to suggested that the problem is with Word and I need to fix it before Endnote will work properly. This does seem to be the case, since I have uninstalled Endnote, then reinstalled Word (w/o Endnote) and still can't open the VBE. I don't have any other add-in installed, in fact this is my first run in with macros at all.
Any other suggestions?
Thanks, Mike
Paul Berkowitz - 06 Nov 2006 18:08 GMT On 11/6/06 8:47 AM, in article 1162831637.685441.220230@k70g2000cwa.googlegroups.com,
> I have the same problem regardless of what document or template I use. > Even when I open a blank document (using the 'Normal' template), I am [quoted text clipped - 11 lines] > > Any other suggestions? I think it's possible that some part of VBA itself or OLE Automation did not get installed. Did you do a "Custom Install" of Office - for example just Word, not the other apps - rather than the "Easy Install"? If so, you may not have been aware of all the files in Office that all the apps, including Word, need for full use, and may have excluded some of them.
The simplest thing to do at this point is to run the Remove Office utility in /Applications/Microsoft Office 2004/Additional Tools, to remove all Office apps, preferences, etc. (It won't touch your data, including any Entourage data.) Also remove or rename Normal from ~/Documents/Microsoft User Data/ folder, since it's still possible that the problem is actually in your Normal template, and you want Office to generate a new one. (In fact you could try this first, before removing Office, to check.) Then **empty the Trash**. Then install Office 2004 again from the CD. This time, do an Easy Install and install everything.
Then see how things work.
 Signature Paul Berkowitz MVP MacOffice Entourage FAQ Page: <http://www.entourage.mvps.org/faq/index.html> AppleScripts for Entourage: <http://macscripter.net/scriptbuilders/>
Please "Reply To Newsgroup" to reply to this message. Emails will be ignored.
PLEASE always state which version of Microsoft Office you are using - **2004**, X or 2001. It's often impossible to answer your questions otherwise.
miike - 08 Nov 2006 02:51 GMT Paul -
I had done this before, excluding only MSN messenger. But for the sake of argument, I tried it again. This time installing everything. I also made sure to get rid of the Normal template before starting.
Unfortunately, this did not work either. I still get the same error: Could not open macro storage.
I have read that low memory can cause this problem. I have 256MB of RAM and plenty of hard disk space--this seems like it should be enough, especially when Word is all that I am running. Could this be the source of the problem?
Thanks for your help.
Mike
> On 11/6/06 8:47 AM, in article > 1162831637.685441.220230@k70g2000cwa.googlegroups.com, [quoted text clipped - 45 lines] > **2004**, X or 2001. It's often impossible to answer your questions > otherwise. John McGhie [MVP - Word and Word Macintosh] - 08 Nov 2006 08:20 GMT Hi Mike:
It "could" be the problem. Serious work in Word on Mac OS X needs about a gig of RAM.
However, it's unlikely to be the problem. Lack of RAM will usually make Word deathly slow, but it won't emit error messages. If you were out of disk space, you would get a message saying so. If you have disk space, OS X will spill over from RAM to the Hard Disk as necessary.
*I* think you have a partial installation of EndNote there attempting to load a version of Cite While You Write that is not compatible with your version of Word.
I think you need to look for and expunge all remnants of EndNote :-)
Cheers
On 8/11/06 1:51 PM, in article 1162954312.451634.320270@b28g2000cwb.googlegroups.com, "miike" <McMaster.Michael@gmail.com> wrote:
> Paul - > [quoted text clipped - 63 lines] >> **2004**, X or 2001. It's often impossible to answer your questions >> otherwise.
 Signature Please reply to the newsgroup to maintain the thread. Please do not email me unless I ask you to.
John McGhie <john@mcghie.name> Microsoft MVP, Word and Word for Macintosh. Business Analyst, Consultant Technical Writer. Sydney, Australia +61 (0) 4 1209 1410
miike - 13 Nov 2006 17:26 GMT John -
I've removed as much of EndNote as I can find. Even when I do this and do a full reinstall of Office (without EndNote), I still cannot open the VBE. None of the Cite while you write add-ins are showing up in the menus.
How can I make sure I got all remnants of EndNote? If it is not a problem with EndNote, what else could it be?
Thanks, Mike
> Hi Mike: > [quoted text clipped - 95 lines] > Technical Writer. > Sydney, Australia +61 (0) 4 1209 1410 John McGhie [MVP - Word and Word Macintosh] - 15 Nov 2006 09:28 GMT Hi Mike:
If you have done everything suggested so far, then I am afraid I have run out of ideas.
Create a new user-ID on your Mac, and try Word in that.
I want to know whether this problem is system-wide, or particular to your User ID. I suspect it might be system-wide, in which case the problem will persist in the new user ID.
Cheers
On 14/11/06 4:26 AM, in article 1163438819.460780.48680@m73g2000cwd.googlegroups.com, "miike" <McMaster.Michael@gmail.com> wrote:
> John - > [quoted text clipped - 110 lines] >> Technical Writer. >> Sydney, Australia +61 (0) 4 1209 1410
 Signature Please reply to the newsgroup to maintain the thread. Please do not email me unless I ask you to.
John McGhie <john@mcghie.name> Microsoft MVP, Word and Word for Macintosh. Business Analyst, Consultant Technical Writer. Sydney, Australia +61 (0) 4 1209 1410
miike - 15 Nov 2006 19:38 GMT John -
Thanks very much for your help.
Creating a new user doesn't fix the problem. It is the same regardless of who is logged in.
Any thoughts on where I can go to get this figured out?
Regards, Mike
> Hi Mike: > [quoted text clipped - 137 lines] > Technical Writer. > Sydney, Australia +61 (0) 4 1209 1410 John McGhie [MVP - Word and Word Macintosh] - 16 Nov 2006 08:05 GMT Hi Mike:
You have done a Remove Office and a Reinstall? If not, do that. Make sure you run the Remove Office tool: deleting stuff will only make the problem worse.
I am pretty sure the issue is ONE file that is incompatible. Office is a collection of components, and one of them is not at the right version. Alternatively, some other application is preventing access to one of the components of the VBA Editor. The error you are seeing indicates a fatal "The file is not there" kind of error. But it can also mean "The entry point I expected in this module of program code is not there."
If you have already done a Remove Office and re-installed, the only thing I can think of is that one of the files that should have been removed is corrupted so that the file system cannot remove it.
The only thing left is a complete reinstallation of the system and all its applications.
Maybe someone else has a better idea (he said desperately...)
On 16/11/06 6:38 AM, in article 1163619539.904460.290180@m73g2000cwd.googlegroups.com, "miike" <McMaster.Michael@gmail.com> wrote:
> John - > [quoted text clipped - 152 lines] >> Technical Writer. >> Sydney, Australia +61 (0) 4 1209 1410
 Signature Please reply to the newsgroup to maintain the thread. Please do not email me unless I ask you to.
John McGhie <john@mcghie.name> Microsoft MVP, Word and Word for Macintosh. Business Analyst, Consultant Technical Writer. Sydney, Australia +61 (0) 4 1209 1410
miike - 16 Nov 2006 19:55 GMT John -
I have actually Removed Office (using the Remove Office tool) and reinstalled several different times, in several different ways (i.e. removing it, creating a new user, installing it on that user, etc)
It does seems to me that all I can do now is a complete reinstallation of the system. Which does not make me happy.
Thanks for your help. If I figure it out, I'll post my solution here.
Mike
> Hi Mike: > [quoted text clipped - 188 lines] > Technical Writer. > Sydney, Australia +61 (0) 4 1209 1410 John McGhie [MVP - Word and Word Macintosh] - 17 Nov 2006 08:26 GMT Thanks Mike:
Sorry: I just have nothing else to offer.
Please do let us know if you find a cure...
Cheers
On 17/11/06 6:55 AM, in article 1163706943.461263.135970@f16g2000cwb.googlegroups.com, "miike" <McMaster.Michael@gmail.com> wrote:
> John - > [quoted text clipped - 213 lines] >> Technical Writer. >> Sydney, Australia +61 (0) 4 1209 1410
 Signature Please reply to the newsgroup to maintain the thread. Please do not email me unless I ask you to.
John McGhie <john@mcghie.name> Microsoft MVP, Word and Word for Macintosh. Business Analyst, Consultant Technical Writer. Sydney, Australia +61 (0) 4 1209 1410
miike - 25 Dec 2006 19:36 GMT UPDATE: I did a clean install of OS 10.4, then I did a software update. Then I installed Office 2004, did autoupdate. So everthing is up-to-date and the system is totally clean and set to defults.
I still get "Could not open macro storage" (twice) when I try and open VBA editor!!
Is it possible that disc I have is corrupt? I can't think of anything else it could be. If this is that case, what can I do?
Any help would be great, thanks Mike
miike - 25 Dec 2006 22:02 GMT I take back my previous suggestion... Using the same Office install disc, VBA works on a different machine (iBook, 10.4), so I know install disc is fine. (no worries, it's a Student version with 3 licenses) My powerbook is one of the many PB the suffers from the lower memory slot failure. Could this be the problem?
Thanks, Mike
> UPDATE: > I did a clean install of OS 10.4, then I did a software update. Then I [quoted text clipped - 9 lines] > Any help would be great, thanks > Mike Barry Wainwright [MVP] - 26 Dec 2006 09:31 GMT Possibly, but more likely is that permissions have become corrupt on some key files or directories.
Run 'repair permissions' in Disk First Aid
 Signature Barry Wainwright Microsoft MVP (see http://mvp.support.microsoft.com for details) The Entourage User's WebLog has moved! For hints, tips and troubleshooting go to <http://www.barryw.net/weblog/>
> From: miike <McMaster.Michael@gmail.com> > Organization: http://groups.google.com [quoted text clipped - 25 lines] >> Any help would be great, thanks >> Mike miike - 26 Dec 2006 18:27 GMT I had repaired permissions after the OS install and Office install, so I don't think it is a permissions issue.
I've also tried doing a clean install of 10.3 (which came with my machine). No luck either.
-- Mike
> Possibly, but more likely is that permissions have become corrupt on some > key files or directories. [quoted text clipped - 36 lines] > >> Any help would be great, thanks > >> Mike miike - 26 Dec 2006 18:27 GMT I had repaired permissions after the OS install and Office install, so I don't think it is a permissions issue.
I've also tried doing a clean install of 10.3 (which came with my machine). No luck either.
-- Mike
> Possibly, but more likely is that permissions have become corrupt on some > key files or directories. [quoted text clipped - 36 lines] > >> Any help would be great, thanks > >> Mike Beth Rosengard - 26 Dec 2006 19:56 GMT So just how much functioning memory do you have?
Beth
On 12/25/06 2:02 PM, in article 1167084176.753198.30270@i12g2000cwa.googlegroups.com, "miike" <McMaster.Michael@gmail.com> wrote:
> My powerbook is one of the many PB the suffers from the lower memory > slot failure. Could this be the problem? miike - 26 Dec 2006 21:14 GMT I have 1GB of RAM. The lower slot has a 256MB chip, but it shows as empty. The upper slot has a 1GB chip. Even thought the lower slot doesn't recognize the chip, I still have to keep it in there. The computer won't boot if the lower slot is empty.
> So just how much functioning memory do you have? > [quoted text clipped - 6 lines] > > My powerbook is one of the many PB the suffers from the lower memory > > slot failure. Could this be the problem? John McGhie [MVP - Word and Word Macintosh] - 26 Dec 2006 21:27 GMT Have you replaced your templates with blank new ones?
That error is normally an indication of a corrupt file. And it's very specific.
A Microsoft Word document is like a set of shelves in a warehouse: a large collection of containers, each of which may store a specific type of object. A document or template that contains a macro has one extra container that doesn't exist in a normal document: the "Macro Storage".
That error results when Word cannot read or write the content of the container. If the container is not there at all, the Macro Editor will add it. If it's there but can't be read, you get that error.
One way to produce it is to attempt to open a template that has been edited on a later version of Word (Word 2002, Word 2003, Word 2007) and has had the macro container "Digitally Signed".
If that is what has happened, Word can see the container, but it's encrypted so it can't read it.
If you take the template concerned back to Word 2003 an remove the digital signature, Word 2004 can then work with the content. If it's the Normal template, simply re-name the file. Word will create a new default template into which it will be able to add a blank Macro Storage container.
Hope this helps
On 27/12/06 8:14 AM, in article 1167167671.658782.117330@48g2000cwx.googlegroups.com, "miike" <McMaster.Michael@gmail.com> wrote:
> I have 1GB of RAM. > The lower slot has a 256MB chip, but it shows as empty. The upper slot [quoted text clipped - 11 lines] >>> My powerbook is one of the many PB the suffers from the lower memory >>> slot failure. Could this be the problem?
 Signature Please reply to the newsgroup to maintain the thread. Please do not email me unless I ask you to.
John McGhie <john@mcghie.name> Microsoft MVP, Word and Word for Macintosh. Business Analyst, Consultant Technical Writer. Sydney, Australia +61 (0) 4 1209 1410
miike - 27 Dec 2006 06:03 GMT John -
It doesn't matter what template I use, I still get the same error. Even if with a newly created Normal template, I am unable to open the VBE.
I am getting this error "out of the box." I've erased the hard drive, did a complete reinstall of the OS as well as a full install of Office. After installing, I will repair permissions, do an update, repair permissions again, then I will try to open the VBE. It's the first and only thing I will do in word. I'm not using any templates generated on other machines, platforms or versions of Office. I know that the my install disk is good because I've used it on a different machine and the VBE works on a different.
Any other thoughts? Mike
> Have you replaced your templates with blank new ones? > [quoted text clipped - 53 lines] > Technical Writer. > Sydney, Australia +61 (0) 4 1209 1410 John McGhie [MVP - Word and Word Macintosh] - 27 Dec 2006 12:41 GMT Hi Mike:
No other thoughts -- we've been through everything pretty exhaustively.
This error can come from Word, Excel or Powerpoint (only). They share the VBE.
The error very specifically means "Cannot get read/write access to the Visual Basic OLE container in one of the documents or templates in play."
This means the Normal template, the attached template, or any add-ins, global or otherwise.
It's possible that a PC Office virus is pre-loading or re-loading a template you haven't spotted that contains encrypted code. It's possible that the templates folder in which your templates reside does not provide read/write access to the logged-in user. It is possible that a macro has a reference set to a template you do not know about.
I forget: What happened when you tried this from a different user-ID on that machine?
I simply can't think of any other suggestions :-)
On 27/12/06 5:03 PM, in article 1167199389.955468.104410@a3g2000cwd.googlegroups.com, "miike" <McMaster.Michael@gmail.com> wrote:
> John - > [quoted text clipped - 71 lines] >> Technical Writer. >> Sydney, Australia +61 (0) 4 1209 1410
 Signature Please reply to the newsgroup to maintain the thread. Please do not email me unless I ask you to.
John McGhie <john@mcghie.name> Microsoft MVP, Word and Word for Macintosh. Business Analyst, Consultant Technical Writer. Sydney, Australia +61 (0) 4 1209 1410
jenniferb - 31 Mar 2008 19:48 GMT Hi all,
We had the same problem on several macbook pros and spent probably 1 or 2 weeks fighting with this issue. We tried: -removing preferences -different users -removing/reinstalling office and endnote (and then installing only office) -archive install -wiping the drives (several times, including zeroing the drive and installing fresh from original disks that came with the machine)
At one point, it worked and then later stopped. I realized that I had made one change from the time it was working until the time it stopped: the hard drive name. I changed the hard drive name to it's original "mac," and it worked! I named it to Mac123 and it still worked. The name that had caused it to stop working had 28 characters (which follows our hard drive naming convention).
Your mileage may vary, but this seems to help us and I just wanted to post in hopes that it will help others.
Thanks, Jennifer
>Hi Mike: > [quoted text clipped - 29 lines] >>> Technical Writer. >>> Sydney, Australia +61 (0) 4 1209 1410
|
|
|