Excel 2013 crashes deleting tabs

what can be done? in many files

To connect to a Visual FoxPro database or table in Excel
Open an Excel worksheet.
From the Data menu, point to Import External Data, and click
Import Data.
In the Select Data Source dialog box, click New Source Data Connection.
In the Data Connection Wizard, select Other/Advanced.
In the Provider tab, select Microsoft OLE DB Provider for Visual FoxPro.
The Connection tab in the Data Link Properties dialog box appears.
To connect to a Visual FoxPro database or table in Word
Open a Word document.
From the View menu, point to Toolbars, and click
Database.
On the Database toolbar, click the Insert Database icon.
In the Database dialog box, click Get Data.
In the Select Data Source dialog box, click New Source Data Connection.
In the Data Connection Wizard, select Other/Advanced.
In the Provider tab, select Microsoft OLE DB Provider for Visual FoxPro.
The Connection tab in the Data Link Properties dialog box appears.
To add a Visual FoxPro database or table folder
On the Connection tab and in the Select or enter a database name box, type path and name of the database or table folder you want. 
-or- 
To browse for a Visual FoxPro database or table folder, click the ellipsis (...) button to the right of the
Select or enter a database name box to open the Configure Connection dialog box.
Specify a different collating sequence if desired.
To test the connection, click Test Connection. If connection is successful, click
OK.

Similar Messages

  • Excel 2013 crashes when creating VFP OLE DB Data connection

    Hi all,
    I don't know how often the DBF format is used in Office but it seems some demand still exists because Microsoft created 64 bit version of dBase ODBC and OLE DB driver (in Access data engine). Then I don't understand why Microsoft ignores its own FoxPro
    DBF data format because FoxPro ODBC driver is not supported already and no 64 bit version of VFP OLE DB driver is planned...
    I am testing DBF file import to Excel 2013 (32 bit) but it crashes instantly. I have VFP OLE DB driver (the last version), some small DBF file, and I am trying to read it as external data in Excel.
    Steps to reproduce (menu prompts are translated, so some differences may occur):
    Open empty worksheet
    Click "Other data sources" on Data ribbon
    Select Data Connection Wizard and from the list of available drivers select "Other" and click "Next"
    A list of OLE DB providers installed appears, select Microsoft OLE DB Provider for Visual FoxPro and click "Next >>"
    Excel 2013 crashes...
    This process works in Excel 2010 and 2007 so the problem must be in Excel 2013...
    The question is how to read DBF data in FoxPro format when there is no older Office version available?

    To connect to a Visual FoxPro database or table in Excel
    Open an Excel worksheet.
    From the Data menu, point to Import External Data, and click
    Import Data.
    In the Select Data Source dialog box, click New Source Data Connection.
    In the Data Connection Wizard, select Other/Advanced.
    In the Provider tab, select Microsoft OLE DB Provider for Visual FoxPro.
    The Connection tab in the Data Link Properties dialog box appears.
    To connect to a Visual FoxPro database or table in Word
    Open a Word document.
    From the View menu, point to Toolbars, and click
    Database.
    On the Database toolbar, click the Insert Database icon.
    In the Database dialog box, click Get Data.
    In the Select Data Source dialog box, click New Source Data Connection.
    In the Data Connection Wizard, select Other/Advanced.
    In the Provider tab, select Microsoft OLE DB Provider for Visual FoxPro.
    The Connection tab in the Data Link Properties dialog box appears.
    To add a Visual FoxPro database or table folder
    On the Connection tab and in the Select or enter a database name box, type path and name of the database or table folder you want. 
    -or- 
    To browse for a Visual FoxPro database or table folder, click the ellipsis (...) button to the right of the
    Select or enter a database name box to open the Configure Connection dialog box.
    Specify a different collating sequence if desired.
    To test the connection, click Test Connection. If connection is successful, click
    OK.

  • Excel 2013 crash - related to digital signature?

    This is a cross-posting of a thread originally started in Microsoft Answers (Office- Excel) forum, advised to post in this forum by MS support engineer Mohan Suryanarayan (link to other forum: here).
    I have a VB macro in file A (which otherwise contains only several Excel Tables with named ranges). My digital signature (for signing code) is attached to file A.
    As the macro executes, the Open file dialog is called up so that the User can select a secondary file to open (file B or C).
    Files B and C contain several sheets with formulas and Excel Tables, and also their own extensive VB macros. My digital signature is also attached to files B & C.
    The remainder of the macro in file A simply executes an update of the Excel Tables in the secondary file, before saving & closing it.
    I have been finding that during execution of the file A macro, Excel crashes and closes all open Excel files.
    If I remove the digital signature from the secondary files then the macro in file A executes with no problem.
    The macro was written in Excel 2007 and on a different laptop, with different digital signature, and used to have no problem at all. When a new laptop was purchased a new digital signature was obtained and placed into all of the files.
    Execution of file A is a critical process - I need help with stopping the crash, while maintaining a digital signature in the secondary files (so that their own macros can execute).
    Event Viewer error shows the following:
    Faulting application name: EXCEL.EXE, version: 15.0.4667.1000, time stamp: 0x543d366c
    Faulting module name: mso.dll, version: 0.0.0.0, time stamp: 0x5447696f
    Exception code: 0xc0000602
    Fault offset: 0x011aafdd
    Faulting process id: 0x2d58
    Faulting application start time: 0x01d01e17eafcd0bb
    Faulting application path: C:\Program Files\Microsoft Office 15\root\office15\EXCEL.EXE
    Faulting module path: C:\Program Files (x86)\Common Files\Microsoft Shared\Office15\mso.dll
    JL Latham replied:
    Tom, all I can give you is relatively non-information.  I haven't experienced that type of behavior even in Excel 2013 with digitally signed macros in multiple workbooks.  But my digital signature is a commercial one from DigiCert, not
    self-cert.  I'm not even sure what piece of Excel or Office processes the digital signature (that is, whether it is mso.dll or not).  But your whole process has more moving parts than most of mine involving multiple workbooks do - I quite often turn
    off .EnableEvents when doing things like that just so event driven macros in the other workbook(s) do not execute.
    Do the macros in the 'B files' have to execute during all of this processing in file A?  If not, have you tried turning interrupts off:
    Application.EnableEvents = False
    before starting to work with the B-files?  Maybe something in them, such as a Worksheet_Change() or other event triggered process is messing things up?
    If you do use  Application.EnableEvents=False, remember that you MUST re-enable that later in the code with Application.EnableEvents=True to get responses to things like button clicks, changes in a worksheet or other event driven processes
    to run 'normally' again.
    Have you looked at this discussion:
    http://answers.microsoft.com/en-us/office/forum/office_2013_release-excel/excel-2013-crashing-immediately-when-attempting-to/ea2ab100-5525-4a0d-a3cf-6977319f954f
    Sounds very similar to yours - original signature created in 2007, and crashing in 2013.  Some suggestions were made, but whether they fixed the issue or not is unknown: OP never came back and said "fixed it" or "didn't fix it".
    I replied:
    In answer, the secondary B files don't execute any part of their macros during the A file process, and I hadn't included an EnableEvents = False within the file A code. However, I have just tried it to check if it made any difference and unfortunately it didn't.
    I had read the thread you gave a link to before posting, and also the sub threads given within that one, but didn't see anything I thought of immediate parallel other than an Excel 2013 crash.
    The way I read the linked thread was that a User added a signature in Excel 2007 and when they tried to open the file Excel (2007?) crashes, although other people using Excel 2013 can open it (not clear whether it means others can open the one with
    the 2007 signature or without it).
    Anyway, the differences in my situation are that:
    (1) my B-files were originally created in Excel 2007 on a different laptop to current and had their own signature attached. I maintain a 'stock' of B-file versions, some of which have the old signature and some the new. If I run the A-file macro
    on one of the B-files with the old signature then it executes ok;
    (2) I am able to open the B-files ok, no matter whether the signature in them derives from the old laptop with Excel 2007 or the new laptop with Excel 2013;
    (3) the macros within the B-files execute ok (this includes any versions of the B-files which still have an old signature attached, by removing the old signature and replacing with the new and executing on the new laptop);
    (4) the offending operation which triggers the crash (when the B-files have the new signature attached) is a Resize of the Excel Tables within the B-file. I understand that I may eventually have to find a workaround for this operation but initially
    I want to sort out the signature issue (I'm reasonably sure the signature issue is not a red herring where the Resize is the 'real' problem).
    Regards, Tom

    Hi,
    According to your description, this issue occurred with some particular files that stored in SharePoint site. Did the user  download the file to local disk to print?
    Based on the event log >>Faulting module name: EXCEL.EXE<<, it does not show the root Faulting module. Thus, please try to follow this KB to do general troubleshooting:
    https://support.microsoft.com/en-us/kb/2758592
    Then, if you have used "printer status application", please go to Device settings -> Installable options -> Printer Status notification and select disable.
    If this issue still exists, we may need to collect the App crash dump file:
    https://technet.microsoft.com/en-us/sysinternals/dd996900.aspx
    You can try to analyze dump by yourself if you would like to:
    How to analyze app crash dump file:
    http://blogs.technet.com/b/askperf/archive/2007/05/29/basic-debugging-of-an-application-crash.aspx
    Regards,
    George Zhao
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs.
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Excel 2013 crashes every single time I click on Power Query Tab and try anything

    I have Windows 7 Professional 64 bit. I installed Office 2013 Professional Plus 64 bit. I dont have any older versions of office. I downloaded and installed power query 64 bit. I start excel, click on power query tab and select any option, excel crashes
    and closes, every single time. 
    The event viewer says "Excel is running into problems with "microsoft power query for excel" add-in If it keeps happening disable this add in and check for updates. 
    P1: 700160
    P2: 15.0.4420.1017
    Event ID: 300
    Task Category : None
    Level: Information
    User: N/A
    Keywords: Classic
    Excruciatingly frustrating to have such an unintuitive message. What should I do to get power query working in excel 2013 and most importantly for excel to function ?

    Hi,
    It should be the latest version of Power Query. Make sure there is no old version of power Query installed in your computer.And what happens if you reinstall Power Query add-in or repair your office program?
    Also Microsoft Power Query for Excel requires Internet Explorer 9 or greater.
    Wind Zhang
    TechNet Community Support

  • PowerPivot Excel 2013 crashes after column rename in source datatabase

    Hello,
    Using Windows 8.1, Excel 2013 64Bits, PowerPivot Add-In :
    Not using a SQL Server TabularModel just a local Excel Model.
    Having 32MB Ram  memory.
    Readed a table from a SQL Source that contains 13.000.000 records. After loading I discoverd that in the Source one of the columnn names is incorrect. It's name ExecudingProvider and should be ExecutingProvider, so I changed the SQL Server source table and
    added the "t" to ExecutingProvider...
    Back in PowerPivot I do go to the PowerPivot Data model > Design > Table Properties (not sure of translation using dutch edition but you should be able to find it)
    It mentions that it is missing the ExecudingProvider. It;s indeed gone from the Columns that are listed, in place I do see the ExecutingProvider column which is not selected, clicked the checkbox to select the new column name. When clicking Save PowerPivot
    starts loading. On reach of 13.000.000 records PowerPivot crashes saying an error has occurred, no real specification on what error and restarts excel automatically.
    My work arround for know is to remove the table from the model and add it again, causing to recreate all relation ships. This should not be the case I think.
    Do other have this same problem and did you figure out what is going wrong?
    Regards,
    Arjan

    In the event view of the Notebook I can only see the following related errors:
    Faulting application name: EXCEL.EXE, version: 15.0.4603.1000, time stamp: 0x53162a3a
    Faulting module name: EXCEL.EXE, version: 15.0.4603.1000, time stamp: 0x53162a3a
    Exception code: 0xc0000005
    Fault offset: 0x000000000070c3eb
    Faulting process id: 0x1f9c
    Faulting application start time: 0x01cf84820bcf4ee4
    Faulting application path: C:\Program Files\Microsoft Office\Office15\EXCEL.EXE
    Faulting module path: C:\Program Files\Microsoft Office\Office15\EXCEL.EXE
    Report Id: cb310f11-f094-11e3-9cbd-6c626d373f9c
    Faulting package full name:
    Faulting package-relative application ID:
    And
    The program EXCEL.EXE version 15.0.4603.1000 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
    Process ID: 1cc0
    Start Time: 01cf84a1a42cd29e
    Termination Time: 0
    Application Path: C:\Program Files\Microsoft Office\Office15\EXCEL.EXE
    Report Id: ffbd693c-f099-11e3-9cbd-6c626d373f9c
    Faulting package full name:
    Faulting package-relative application ID:

  • Excel 2013 crashes after I install Power Query add-in

    Excel 2013 Professional 64 Bit crashes while opening after installing PowerQuery 64 bit add-in. 
    Power Query File version: 
    PowerQuery_2.17.3850.242 (64-bit) [en-us].msi
    Excel Version: Microsoft Excel 2013 (15.0.4675.1000) MSO (15.0.4675.1002) 64-bit
    Office Version: 15.0.4569.1506
    Excel just opens fine after I uninstall the add-in

    Interesting. Any suggestions for Sunny?
    Thanks!
    Ed Price, Azure & Power BI Customer Program Manager (Blog,
    Small Basic,
    Wiki Ninjas,
    Wiki)
    Answer an interesting question?
    Create a wiki article about it!

  • Excel 2013 crashes when trying to open existing worksheets from previous versions of Excel

    Hello
    I have windows 8 and Excel 2013 on my system. I need to access previously created worksheets (in older versions of Excel), however, when I attempt to open them the Excel crashes.
    The is not what I expected from getting the latest version. I telephoned Microsoft who advised that there was a compatabilty problem with no work around at this stage.
    I found that the only way round it was to use an (download free) alternative non-Microsoft program
    http://www.openoffice.org/ and copy into the 2013 Excel as a new worksheet. A little disappointing after purchasing the Excel .
    Have I got this wrong or is there a Microsoft solution to this issue???

    Hi,
    Try the following steps:
    Open Excel 2013, and go to
    File –> Options –> Trust Center.
    Under
    Trust Center settings, select Protected View and
    uncheck all options under it.
    Restart the Excel 2013 to check the issue.
    Jaynet Zhang
    TechNet Community Support

  • Problem with Excel 2013, crashing unexpectedly

    I have problem with Office, it's crashing without any specific reason. I can't describe what exactly triggers crashing, but there is lots of copy and pasting on that workstation between excel worksheets. RAM has been tested, Office suite has been reinstated
    and even all of hardware has been changed.
    If there any suggestion, I would really appreciate them.
    If you need additional information please ask.
    Faulting application name: EXCEL.EXE, version: 15.0.4701.1001, time stamp: 0x54e30a7b
    Faulting module name: mso.dll, version: 0.0.0.0, time stamp: 0x54d9bfd6
    Exception code: 0xc0000602
    Fault offset: 0x011aee88
    Faulting process id: 0x1990
    Faulting application start time: 0x01d0773e764ce473
    Faulting application path: C:\Program Files\Microsoft Office 15\Root\Office15\EXCEL.EXE
    Faulting module path: C:\Program Files\Common Files\Microsoft Shared\Office15\mso.dll
    Report Id: 66154c61-e40f-11e4-afd6-d43d7eb40d36
    Faulting package full name: 
    Faulting package-relative application ID: 
    System
    Provider
    [ Name]
    Application Error
    EventID
    1000
    [ Qualifiers]
    0
    Level
    2
    Task
    100
    Keywords
    0x80000000000000
    TimeCreated
    [ SystemTime]
    2015-04-16T08:05:52.000000000Z
    EventRecordID
    35372
    Channel
    Application
    Computer
    Security
    EventData
    EXCEL.EXE
    15.0.4701.1001
    54e30a7b
    mso.dll
    0.0.0.0
    54d9bfd6
    c0000602
    011aee88
    1990
    01d0773e764ce473
    C:\Program Files\Microsoft Office 15\Root\Office15\EXCEL.EXE
    C:\Program Files\Common Files\Microsoft Shared\Office15\mso.dll
    66154c61-e40f-11e4-afd6-d43d7eb40d36

    Hi,
    According to your description, >>RAM has been tested, Office suite has been reinstated and even all of hardware has been changed.<< I noticed that you have tired several methods. Then, based on the log,>>Faulting module path: C:\Program
    Files\Common Files\Microsoft Shared\Office15\mso.dll<<, please try the following steps:
    Renamed the MSO.DLL in C:\Program Files\Microsoft Office 15\root\vfs\ProgramFilesCommonX86\Microsoft Shared\OFFICE15
    The copied the MSO.DLL from C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE15
    to C:\Program Files\Microsoft Office 15\root\vfs\ProgramFilesCommonX86\Microsoft Shared\OFFICE15
    Hope it's helpful.
    Regards,
    George Zhao
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs.
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Excel 2013 Constantly Crashes: Event 1000, Application Error 'Exception Code: 0xc0000005 Fault offset: 0x00ac6660

    Hello Microsoft Gurus!
    One of the employees in my office is constantly having problems with Excel 2013 crashing while doing work. We even made him use the safe mode version of excel, but he still was getting crashes. I'll try to provide as much information as I can, and if there's
    anything I need to do on my end, please let me know. 
    This is the message that pops up when his computer crashes:
    "Do you want to send more information about the problem? Additonal details about what went wrong can help Microsoft create a solution"
    Files that help describe the problem:
      C:\Users\user\AppData\Local\Temp\29422974.cvr
      C:\Users\user\AppData\Local\Temp\CVRFA9B.tmp.cvr
      C:\Users\user\AppData\Local\Temp\WERF771.tmp.WERInternalMetadata.xml
      C:\Users\user\AppData\Local\Temp\WERCA7.tmp.appcompat.txt
      C:\Users\user\AppData\Local\Temp\WERCF6.tmp.mdmp
    Upon looking at the Windows App Error Logs, this is what shows up.
    Faulting application name: EXCEL.EXE, version: 15.0.4701.1001, time stamp: 0x54e3066c
    Faulting module name: EXCEL.EXE, version: 15.0.4701.1001, time stamp: 0x54e3066c
    Exception code: 0xc0000005
    Fault offset: 0x00ac6660
    Faulting process id: 0x21d4
    Faulting application start time: 0x01d06c01fa2c79fe
    Faulting application path: C:\Program Files (x86)\Microsoft Office\Office15\EXCEL.EXE
    Faulting module path: C:\Program Files (x86)\Microsoft Office\Office15\EXCEL.EXE
    Report Id: cb0a8ef3-d7f9-11e4-a4d2-80000b62e6e7
    Log Name: Application
    Source: Application Error
    Event ID: 1000
    Level: Error
    User: N/A
    Taks Category (100)
    What additional information is needed to decipher what is causing this to break? I have already tried suggestions from other technet articles (disabling hardware acceleration, using only 2013 files, safe mode excel, repairing office 2013, uninstalling/reinstalling
    office 2013, etc.). I even tried using Procmon to try to find what 'function' was causing excel to crash but it was way beyond my expertise level. Can someone please advise what to do?
    Also (not sure if this is related or not) Excel opens up 'blank' when he opens any type of model (.xls, .xlsx) that no other user is experiencing (exactly same computer model, same install, etc.). All the toolbars are there, but no data can be seen. Only when
    he double clicks the top to shrink/maximize the excel window does the data appear.  
    Thanks!
    btw, this verification thing is pretty stupid, i now have to manually type in the messages instead of just putting a picture. ugh.

    Hi Bob,
    As I said, with your event log messages the faulting module is EXCEL.EXE, I can get less useful information about your constantly crashes problem. Thus, I need you to collecting the app crash dump file.This articles teach you how to collect app crash dump
    file:
    http://blogs.technet.com/b/askperf/archive/2007/06/15/capturing-application-crash-dumps.aspx
    https://support.microsoft.com/en-us/kb/927069/en-us
    Enable app crash dump collection by copying following words into notepad, saving it as dump.reg and importing
    it:
    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\localdumps\EXCEL.EXE]
    "DumpFolder"=hex(2):63,00,3a,00,5c,00,63,00,72,00,61,00,73,00,68,00,64,00,75,\
      00,6d,00,70,00,73,00,00,00
    "DumpCount"=dword:00000010
    "DumpType"=dword:00000001
    "CustomDumpFlags"=dword:00000000
    Then, open Excel to
    repro the issue. If crash issue appeared, please find the crashdump file under c:\.
    You can try to analyze dump by yourself if you would like to:
    How to analyze app crash dump file:
    http://blogs.technet.com/b/askperf/archive/2007/05/29/basic-debugging-of-an-application-crash.aspx
    Regard,

  • MS Office 2013 crashes no matter what I've tried. Been going on for a year HELP!!!

    I have been having an issue with Excel 2013 crashing for over a year now, I place post after post after post, I have spoken to
    numerous times, escalated 6 times and finally spoke to a person who wants money to fix THEIR ISSUE!!!!!   What a way to treat your customers.....needless to say , after being in the phone this last time for 2 1/2 hours I did not pay him a dime. 
    Microsoft KNOWS they have an issue with 2013 crashing.  I am so so SO upset, another FULL day on the phone with Toshiba and Microsoft , I mean since 8:00 a.m. AGAIN this morning and still NO RESOLUTION. 
    When I do a simple cut and paste of ONE CELL, it crashes.  OMG, how ridiculous is this.  It may work for a week and then forget it, it will crash for a week  I can not get ay work done like this.  Perhaps another
    is the way to go if they cant resolve THEIR issue
    Is there ANYONE that has the knowledge to help to fix this?  If not, IMHO....Microsoft needs to STOP selling
    .  At least, get it right, get out all the bugs before you let us determine if it works or not.  I have brought it up in safe mode, I have repaired, I have reloaded video drivers, I have taken off all 3rd party software, deleted all *.exd files
    to name a few things.  Here are some of the event views
    Log Name: Application
    Source: Application Error
    Date: 1/30/2015 10:58:04 AM
    Event ID: 1000
    Task Category: (100)
    Level: Error
    Keywords: Classic
    User: N/A
    Larry
    Description:
    Faulting application name: EXCEL.EXE, version: 15.0.4675.1001, time stamp: 0x546b4f33
    Faulting module name: VBE7.DLL, version: 0.0.0.0, time stamp: 0x5339bedf
    Exception code: 0xc0000005
    Fault offset: 0x00000000000b8419
    Faulting process id: 0x1d5c
    Faulting application start time: 0x01d03c862e9a7156
    Faulting application path: C:\
    Files\
    15\Root\Office15\EXCEL.EXE
    Faulting module path: C:\Program Files\Common Files\Microsoft Shared\VBA\VBA7.1\VBE7.DLL
    Report Id: 27509c44-a8a1-11e4-bf03-b888e31e9527
    Faulting package full name:
    Faulting package-relative application ID:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/ev​ent">
    - <System>
      <Provider Name="Schannel" Guid="{1F678132-5938-4686-9FDC-C8FF68F15C85}" />
      <EventID>36888</EventID>
      <Version>0</Version>
      <Level>2</Level>
      <Task>0</Task>
      <Opcode>0</Opcode>
      <Keywords>0x8000000000000000</Keywords>
      <TimeCreated SystemTime="2015-02-23T10:14:23.035567100Z" />
      <EventRecordID>1201188</EventRecordID>
      <Correlation />
      <Execution ProcessID="764" ThreadID="6844" />
      <Channel>System</Channel>
      <>Larry</Computer>
      <
    UserID="S-1-5-18" />
      </System>
    - <EventData>
      <Data Name="AlertDesc">40</Data>
      <Data Name="ErrorState">107</Data>
      </EventData>
      </Event>
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/ev​ent">
    - <System>
      <Provider Name="Schannel" Guid="{1F678132-5938-4686-9FDC-C8FF68F15C85}" />
      <EventID>36874</EventID>
      <Version>0</Version>
      <Level>2</Level>
      <Task>0</Task>
      <Opcode>0</Opcode>
      <Keywords>0x8000000000000000</Keywords>
      <TimeCreated SystemTime="2015-02-23T10:14:23.043571600Z" />
      <EventRecordID>1201189</EventRecordID>
      <Correlation />
      <Execution ProcessID="764" ThreadID="6844" />
      <Channel>System</Channel>
      <Computer>Larry</Computer>
      <Security UserID="S-1-5-18" />
      </System>
    - <EventData>
      <Data Name="Protocol">TLS 1.0</Data>
      </EventData>
      </Event>
    xmlns="http://schemas.microsoft.com/win/2004/08/events/ev​ent">
    - <System>
      <Provider Name="Schannel" Guid="{1F678132-5938-4686-9FDC-C8FF68F15C85}" />
      <EventID>36888</EventID>
      <Version>0</Version>
      <Level>2</Level>
      <Task>0</Task>
      <Opcode>0</Opcode>
      <Keywords>0x8000000000000000</Keywords>
      <TimeCreated SystemTime="2015-02-23T10:14:23.043571600Z" />
      <EventRecordID>1201190</EventRecordID>
      <Correlation />
      <Execution ProcessID="764" ThreadID="6844" />
      <Channel>System</Channel>
      <Computer>Larry</Computer>
      <Security UserID="S-1-5-18" />
      </System>
    - <EventData>
      <Data Name="AlertDesc">40</Data>
      <Data Name="ErrorState">107</Data>
      </EventData>
      </Event>
    Event xmlns="http://schemas.microsoft.com/win/2004/08/events/ev​ent">
    - <System>
      <Provider Name="Microsoft-Windows-GroupPolicy" Guid="{AEA1B4FA-97D1-45F2-A64C-4D69FFFD92C9}" />
      <EventID>1501</EventID>
      <Version>0</Version>
      <Level>4</Level>
      <Task>0</Task>
      <Opcode>1</Opcode>
      <Keywords>0x8000000000000000</Keywords>
      <TimeCreated SystemTime="2015-02-23T12:13:14.235195500Z" />
      <EventRecordID>1201194</EventRecordID>
      <Correlation ActivityID="{DC67441C-F0EB-47CB-B169-BD98023BF930}" />
      <Execution ProcessID="344" ThreadID="12048" />
      <Channel>System</Channel>
      <Computer>Larry</Computer>
      <Security UserID="S-1-5-21-71391616-1131922306-3719273214-1006" />
      </System>
    - <EventData>
      <Data Name="SupportInfo1">1</Data>
      <Data Name="SupportInfo2">3664</Data>
      <Data Name="ProcessingMode">1</Data>
      <Data Name="ProcessingTimeInMilliseconds">266</Data>
      <Data Name="DCName" />
      </EventData>
      </Event>
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/ev​ent">
    - <System>
      <Provider Name="Schannel" Guid="{1F678132-5938-4686-9FDC-C8FF68F15C85}" />
      <EventID>36888</EventID>
      <Version>0</Version>
      <Level>2</Level>
      <Task>0</Task>
      <Opcode>0</Opcode>
      <Keywords>0x8000000000000000</Keywords>
      <TimeCreated SystemTime="2015-02-23T12:46:22.244167500Z" />
      <EventRecordID>1201250</EventRecordID>
      <Correlation />
      <Execution ProcessID="764" ThreadID="9456" />
      <Channel>System</Channel>
      <Computer>Larry</Computer>
      <Security UserID="S-1-5-18" />
      </System>
    - <EventData>
      <Data Name="AlertDesc">20</Data>
      <Data Name="ErrorState">960</Data>
      </EventData>
      </Event>

    I noticed the Faulting module VBE7.DLL in your logs, definitely you were using VBA in Excel.
    Well, does the issue occur if working without VBA?
    For this VBE7.DLL issue, I have two suggestions:
    Method1 - Recompile the Project
    1. Open the workbook in Excel. Normally Excel will disable macros in a worksheet until you click a button to enable the macros. Do not enable the macros just yet.
    2. Open the VBA editor. You can hit ALT+F11 or on the ribbon click Developer > Visual Basic
    3.  In the VBA editor double click your module or first module that contains your project. Add a commented line of code such as:
    ‘ This is a comment
    Then click on the Debug menu at the top and click Compile VBA Project.
    Repeat this step for each module in your workbook and then save the workbook.
    4. Close the workbook and re-open it and enable the macros and test it. 
    Method 2 - Disable Compile on Demand
    In the VBE Editor in Excel, click on Tools > Options > General tab and click to uncheck
    “Compile on Demand”.
    Alternatively you can set the following registry key:
    HKEY_CURRENT_USER\Software\Microsoft\VBA\7.0\Common
    Type:  DWORD
    Name:  CompileOnDemand
    Value:  0
    -Jeff

  • Ctrl+Tab and Ctrl+F6 still not working in Excel 2013?

    I am using Windows 7 64-bit. I just switched to Office Home & Business 2013 (32-bit), and I discovered that ctrl+tab behavior in Excel 2013 is incredibly broken.
    If you are using any other programs concurrently with Excel, then it makes switching tasks through ctrl+tab impossible. Switching workbooks in this way has unpredictable behavior: often, Excel will switch to a workbook that is hidden behind other windows
    (fails to foreground the window correctly). Even when it appears to be switching appropriately between windows, the order of switching is wrong: rather than cycling through all windows, it seems to switch between workbooks somewhat randomly.
    See similar issues discussed here: https://social.technet.microsoft.com/Forums/office/en-US/f288d91d-835a-48c4-a39c-738ca05002c4/ctrltab-and-ctrlf6-not-working-properly-in-excel-2013?forum=officeitpro
    and here: http://answers.microsoft.com/en-us/office/forum/office_2013_release-excel/cycling-between-open-windows-using-ctrlf6-or/7314b632-7f48-44f1-8e96-7d7000ac86d8
    There does not appear to be any solution to this issue so far. I have attempted to repair my installation of Microsoft Office, but it did not correct the problem.

    Hi Dlup12345,
    Based on my testes with local environment (Windows 8.1 and Excel 2013:15.0.4675.1000), the two Keyboard shortcuts worked as expected. In my view, this issue might be occur with Keyboard shortcuts, because you said the issue occurred intermittently. If we
    only open multiple Excel files without other program, the shortcuts should worked fine. Please check if other program affected Excel shortcuts.
    If you have any update, please feel free let us know.
    Regards,
    George Zhao
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs.

  • Every time I press the delete tab in Safari it either returns to my previous web page or crashes? Drivinh me nuts!

    Every time I press the delete tab in Safari it either returns to my previous web page or crashes?

    Launch the Console application by entering the first few letters of its name into a Spotlight search. If that doesn’t work, then in the Finder, press the key combination shift-command-U. The application is in the folder that opens.
    Look under User Diagnostic Reports for crash logs related to Safari, WebProcess, or PluginProcess. Select the most recent one of each and post the contents -- the text, please, not a screenshot. For privacy’s sake, I suggest you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if present (it may not be.)

  • Excel 2013 installed through 365 crashes when small row is in spreadsheet

    Hi,
    I have major issue with Excel files that makes Excel stop working when trying to print.
    Excel crashes already at the preview pane and it has nothing todo with print driver, it crashes if using the XPS driver as well.
    Using Excel installed locally through 365 (All patches applied)
    By searching for formatting error in the spread sheet I found out that there were a couple of rows that had very small height and removing those (or increasing them) made Excel not crashing when trying to print.
    This excel file is actually working on other installations of Exel 2013 but it seemes to only cause problems on the Excel 2013 installed through 365.
    When I found the problem and that it seemes only to be on the 365 Excel I also found another user with same problem but no solution. (community.office365.com/en-us/forums/172/t/168863.aspx)
    In my case I have several hundred Excel files and most of them are password protected which makes it impossible to fix the rows manually.
    It is not a problem on traditional installed Excel 2013 or earlier versions... So I would say it is a bug with the 365 version of Excel.
    Anyone out there with a solution or how to report this to Microsoft?

    I would escalate the issue and someone who is more familiar with this kind of issue to deal with this problem.
    Thank you for your feedback.
    Tony Chen
    TechNet Community Support

  • Excel 2013 keeps crashing

    I have a new Toshiba P855 with 16GIGS of memory and Office 2013. I have been on the phone with Microsoft for 6 months complaining about how Excel 2013 Office Pro keeps crashing randomly. At first they told me my macro was corrupt. I knew it wasn't because it runs all day long on office 2010 on my desktop which has Windows 7 it was on and off with them for weeks and hours and they finally said that it has to be something wrong with my laptop. It will crash sometimes when I go to copy and paste simple task on a new spreadsheet without any Macros or no conditional formatting and it is real pain in the butt. When it does crash I can load that same file to my memory stick, open it on my desktop, close it, re open on my Toshiba Office 2013 and it runs for a while.
    Is there ANYTHING that can be causing this from the laptop drivers or other programs. I'm at a lost and feel Microsoft once again is giving me the run around. It gives me different crash reports within excel too so they are not always for the same reason it crashes but when it crashes anything I have open within excel crashes too. It's ONLY excel that crashes. No other programs and my lap top is fine
    Thanks for any suggestions and your help

    No. We just need to know when it's not going to crash, but we need to know within a minute or so. Therefore we need to be able to produce the crash on demand.
    It's unproductive to make experiments if one must longer for the result. Understand?
    Come to think of it, after six months of talking with Microsoft all the experiments have probably been made by now.
    -Jerry

  • I am trying to Add In to my excel 2013 a tab on the tool bar  that would allow me to make a PDF from my spread sheet

    I am trying to Add In to my excel 2013 a tab on the tool bar  that would allow me to make a PDF from my spread sheet
    I went to add ins in the excel options ,& it shows the add in however the tab does not appear

    am trying to Add In to my excel 2013 a tab on the tool bar  that would allow me to make a PDF from my spread sheet
    I went to add ins in the excel options ,& it shows the add in however the tab does not appear

Maybe you are looking for