1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

[Microsoft Office Excel] Startup error message

Discussion in 'Other PC Software' started by bananaball, 2006/12/20.

  1. 2006/12/20
    bananaball

    bananaball Inactive Thread Starter

    Joined:
    2003/11/05
    Messages:
    94
    Likes Received:
    0
    I can find no reference to Excel in any of the startup functions and yet every start or restart I get the following message :

    Microsoft Office Excel has encountered a problem and needs to close. We are sorry for the inconvenience.

    Clicking on the link "What data does this error report contain?" shows :

    AppName: excel.exe AppVer: 11.0.5612.0 AppStamp:3f39ff9d
    ModName: mso.dll ModVer: 11.0.5606.0 ModStamp:3f334cce
    fDebug: 0 Offset: 000c5c8d

    Not a huge problem - but a constant aggravation - any ideas?
     
  2. 2006/12/20
    surferdude2

    surferdude2 Inactive

    Joined:
    2004/07/04
    Messages:
    4,009
    Likes Received:
    23

  3. to hide this advert.

  4. 2006/12/20
    charlesvar

    charlesvar Inactive Alumni

    Joined:
    2002/02/18
    Messages:
    7,024
    Likes Received:
    0
    Hello bananaball,

    I've edited your thread title to indicate that its an Excel problem.

    Regards - Charles
     
  5. 2006/12/20
    bananaball

    bananaball Inactive Thread Starter

    Joined:
    2003/11/05
    Messages:
    94
    Likes Received:
    0
    Well that didn't work - I removed and reinstalled office 2003 and all did all the updates but alas the error message continues
     
  6. 2006/12/20
    mailman Lifetime Subscription

    mailman Geek Member

    Joined:
    2004/01/17
    Messages:
    1,901
    Likes Received:
    11
    Hi, bananaball.

    I also have Office 2003 installed. I compared my versions of excel.exe and mso.dll to yours and it appears my versions are newer.

    excel.exe
    • my version: 11.0.8105.0
    • your version: 11.0.5612.0

    mso.dll
    • my version: 11.0.8107.0
    • your version: 11.0.5606.0

    Perhaps you need to install the latest Microsoft Office 2003 service pack.
     
  7. 2006/12/21
    bananaball

    bananaball Inactive Thread Starter

    Joined:
    2003/11/05
    Messages:
    94
    Likes Received:
    0
    OK - After updating with the latest service pack I now get :

    AppName: excel.exe AppVer: 11.0.8105.0 AppStamp:44ed0d35
    ModName: mso.dll ModVer: 11.0.8107.0 ModStamp:4500cb64
    fDebug: 0 Offset: 000c6e7a

    Any more ideas?
     
  8. 2006/12/21
    mailman Lifetime Subscription

    mailman Geek Member

    Joined:
    2004/01/17
    Messages:
    1,901
    Likes Received:
    11
    Hi, bananaball.

    Shucks! I was hoping that would fix it for you.

    Let's make sure all your Windows Protected Files are in their proper locations and you have the correct versions.

    Assuming you're running Windows XP (I don't know if these steps work for other versions of Windows.):
    Perhaps Windows XP's System File Checker (SFC) will help you resolve your issue.

    • Have your Windows XP CD handy because you may be prompted to insert it into your CD drive during this process.
    • Click Start > Run...
    • Type [FONT= "Courier New"][SIZE= "3"]sfc /scannow[/SIZE][/FONT] in the "Open:" field.
    • Click the OK button.
    A "Windows File Protection" window will open and display its progress. If SFC runs successfully without any intervention from you, it will take approximately 15-25 minutes to complete. When SFC completes, the "Windows File Protection" window will simply disappear.

    To see any changes that may have been made by SFC after it completes:
    • Click Start > Run...
    • Type [FONT= "Courier New"][SIZE= "3"]eventvwr.msc[/SIZE][/FONT] in the "Open:" field.
    • Click the OK button.
    • Click the "System" item on the left side of the "Event Viewer" window.
    Any changes made by SFC will be displayed (in reverse order) as "Windows File Protection" events between Event ID 64016 (Windows File Protection started) and 64017 (Windows File Protection completed).

    Double-click on an event (or right-click on the event and select "Properties ") to view details about the event. You can use the up/down arrow buttons on the right side of the event's "Properties" window to view details about adjacent events without having to close the event's "Properties" window.

    If you want to copy event details to your clipboard (for pasting into Notepad or a forum message, for example), use the button immediately below the up/down arrow buttons in the event's "Properties" window.
     
    Last edited: 2006/12/21
  9. 2006/12/21
    bananaball

    bananaball Inactive Thread Starter

    Joined:
    2003/11/05
    Messages:
    94
    Likes Received:
    0
    OK - I ran the system file checker and it completed OK and the event viewer contained no messages between 64016 and 64017 other than a pop-up saying I inserted the wrong CD ( I had stuffed in a Home instead of the pro initially)
    So - now where do we go ?
     
  10. 2006/12/21
    mailman Lifetime Subscription

    mailman Geek Member

    Joined:
    2004/01/17
    Messages:
    1,901
    Likes Received:
    11
    Hi, bananaball.

    I appreciate your patience. I don't claim to be an expert. :( I'm just offering ideas until someone else who might have more knowledge about your issue can offer suggestions.

    Since Office 2003 is a Microsoft product, perhaps Event Viewer's "Application" section will help. Look for errors (indicated by a white X on red background) that might be related to Office and double-click on the error event to pull up the details about the error. There should be a clickable link in that "Event Properties" window stating, "For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp." Perhaps Microsoft's online "Help and Support Center" information will provide helpful suggestions about the error.

    Another possible route for resolving your issue is to use DebugWiz to create a program crash dump analysis of the Excel crash after carefully following the instructions in this link. The program crash dump will probably located in
    C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\user.dmp
    Please paste that DebugWiz-generated crash dump information here in this thread for us to look at. (Although not absolutely necessary, if you wrap that information in
    Code:
     tags using the appropriate button in the message editing window, that will reduce the size of your post so users won't have to scroll so much to review this thread discussion.)
    
    I do [B]not[/B] claim to be a crash dump analysis expert but perhaps it will provide information we can Google and find suggestions.  Perhaps someone else more familiar with program crash dumps can understand your dump information.
     
    Last edited: 2006/12/21
  11. 2006/12/22
    bananaball

    bananaball Inactive Thread Starter

    Joined:
    2003/11/05
    Messages:
    94
    Likes Received:
    0
    Thanks mailman - I got the following message from the Microsoft Help & support:

    Event ID: 1000
    Source: Microsoft Office 11

    We're sorry
    There is no additional information about this issue in the Error and Event Log Messages or Knowledge Base databases at this time. You can use the links in the Support area to determine whether any additional information might be available elsewhere.

    I don't believe there is any "crash dump" since Excel never even started but I'll look around ans see if I can find one.

    --- There is no dump from Excel
     
    Last edited: 2006/12/22
  12. 2006/12/22
    mailman Lifetime Subscription

    mailman Geek Member

    Joined:
    2004/01/17
    Messages:
    1,901
    Likes Received:
    11
    Hi, bananaball.

    The Debugging Tools for Windows might have to be installed before a program crash dump is created. If not, I hope someone will correct me. :)

    I used EventID.net to look up user-supplied comments about Event ID: 1000, Source: Microsoft Office 11 and got some links that might be helpful. Some of the items in that list also have links to user-supplied comments about Microsoft Office 10 which might also be helpful.

    Here's a link to EventID.net user-supplied comments about Event ID: 1000, Source: Microsoft Office 11.

    If you click EventID.net links displayed as Mxxxxxx (x's are numerical digits), you will be taken to a page that says you have to subscribe to EventID.net to view that information. A way around that which seems to work often is to search Microsoft's Knowledge Base for KBxxxxxx (with the x's being the same digits as EventID.net's "Mxxxxxx" links).

    If you discover a fix for your problem, please let us know what works.

    EDIT: BTW, you might check to be sure you have Dr Watson installed. I do not know if it is installed by default when one installs Windows XP. Dr Watson might have to be installed in order for program crash dumps to be created when programs crash.
     
    Last edited: 2006/12/22
  13. 2006/12/22
    bananaball

    bananaball Inactive Thread Starter

    Joined:
    2003/11/05
    Messages:
    94
    Likes Received:
    0
    Well I did a system restore back a couple of weeks and had to download and run a windows install cleanup and reinstall office and things seem to be back to normal - at least I don't get the error message any longer. Thanks for your help.
     
  14. 2006/12/22
    mailman Lifetime Subscription

    mailman Geek Member

    Joined:
    2004/01/17
    Messages:
    1,901
    Likes Received:
    11
    You're welcome, bananaball. :)

    Thanks for following up with your resolution. System Restore is nice when it works. :) I dunno why I didn't think of that option. Sometimes, that's the first thing I think of. Sometimes (as in this case), it completely escapes me.

    Anyway, good luck and Happy Holidays to you and yours!
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.