Word crashes when opening Citation Source Manager

Anonymous
2020-03-17T03:33:58+00:00

(Updated post)

Hi.

Anybody knows how to solve this problem?

In Word when I select, References tab, Citations, bottom right options and Citation Source Manager, word just immediately crashes and the Microsoft Error Reporting window appears. 

  • I tried removing all of Office and  reinstalling but the problem is still there.
  • Previously I've been able to use citation manager with out any problems until recently when the error started.
  • In an empty new file citation manager works fine (the list is empty)
  • I've also tried using it in some older files with citations, but Word keeps crashing.

I'm using:

macOs Catalina version 10.15.3

Microsoft Word for Mac Version 16.35 (20030802)

Any suggestions?

Thanks

The error report:

Microsoft Error Reporting log version: 2.0

Error Signature:

Exception: EXC_CRASH (SIGABRT)

ExceptionEnumString: 805306368

Exception Code: 0x00000001 (0x00000001131b4000)

Date/Time: 2020-03-18 03:43:14 +0000

Application Name: Microsoft Word

Application Bundle ID: com.microsoft.Word

Application Signature: MSWD

Application Bitness: x64

Application Version: 16.35.0.20030802

Crashed Module Name: merp

Crashed Module Version: 16.35.0.200308

Crashed Module Offset: 0x0000000000005aa3

Blame Module Name: MSXML

Blame Module Version: 16.35.0.200308

UnsymbolicatedChecksum: 135E1661A83E6FD0B9AFE703627F81C9

Blame Module Offset: 0x00000000000e5ab1

StackHash: e71d84****ce0b85e-dm_805306368_main

Application LCID: 10**

Extra app info: Reg=en Loc=0x0409

Build Type: Release

Crashed thread Stack Pointer: 0x_00007ffeee98f158

Crashed thread: 0

......

Operating System Information

Operating System: Mac OS X 10.15.3 (Build 19D76)

CPU: Intel x86, Logical CPU Count: 4, Frequency: 2500 MHz

Physical Memory: 16384 MB

Device_model: MacBookPro14,1

Screen: 1440.000000 x 900.000000, bitsPerPixel = 24, frame = 0.000000, 0.000000, 1440.000000, 900.000000

Screen: 1920.000000 x 1080.000000, bitsPerPixel = 24, frame = 1440.000000, 763.000000, 1920.000000, 1080.000000

CrashedApp_Virtual_Memory_Size_MB: 5472.765

CrashedApp_Resident_Memory_Size_MB: 250.5820

ErrorReportingDeviceUUID: 9C58D398-40D1-5D8D-8387-7C9****

ErrorReportingUUID: 401992B7-2E61-4329-8F97-FDDE4****

ULS UUID: 1F7C6E31-C5AE-436E-A1FA-809195E****

CrashedLogSessionId: 1F7C6E31-C5AE-436E-A1FA-809****

TimeFromLaunch: 0 hours, 10 minutes, 46 seconds

CrashedSessionDuration: 646

Total errors on this client: 95

Microsoft Application Information:

Audience: Production

Tenant_Id: 5f282910-176f-459d-ab7d-b7****

AudienceChannel: CC

AudienceGroup: Production

Microsoft 365 and Office | Word | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

43 answers

Sort by: Oldest
  1. Anonymous
    2020-03-27T15:31:30+00:00

    Hi Bob,

    This is also a nasty problem for me.

    • What version of which program was used to create/edit the problem documents?

            Word 16.35.0.20030802

    • Was any sort of custom reference/citation style used in those documents?

             No

    • Have you worked with these documents in Mac Word previously? If so, which version?

            Yes, same version

    • Has any sort of 3rd party Add-in or citation manager been used?

             No

    • What else can you provide regarding the history of the problem documents?

            This happens with any document. Documents where it worked fine when they were written no longer function correctly. Same happens on a new blank document. It also happens on another Mac that I use, exactly the same way.

    Here are the log files excerpts:

    Microsoft Error Reporting log version: 2.0

    Error Signature:

    Exception: EXC_CRASH (SIGABRT)

    ExceptionEnumString: 805306368

    Exception Code: 0x00000001 (0x0000000111cfd000)

    Date/Time: 2020-03-27 15:11:11 +0000

    Application Name: Microsoft Word

    Application Bundle ID: com.microsoft.Word

    Application Signature: MSWD

    Application Bitness: x64

    Application Version: 16.35.0.20030802

    Crashed Module Name: merp

    Crashed Module Version: 16.35.0.200308

    Crashed Module Offset: 0x0000000000005aa3

    Blame Module Name: MSXML

    Blame Module Version: 16.35.0.200308

    UnsymbolicatedChecksum: 135E1661A83E6FD0B9AFE703627F81C9

    Blame Module Offset: 0x00000000000e5ab1

    StackHash: e71d84888ce0b85e-dm_80530****

    Application LCID: 10338***

    Extra app info: Reg=en Loc=0x0409

    Build Type: Release

    Crashed thread Stack Pointer: 0x_00007ffeebc61158

    Crashed thread: 0

    Operating System Information

    Operating System: Mac OS X 10.15.3 (Build 19D76)

    CPU: Intel x86, Logical CPU Count: 4, Frequency: 3000 MHz

    Physical Memory: 16384 MB

    Device_model: Macmini7,1

    Screen: 3840.000000 x 2160.000000, bitsPerPixel = 24, frame = 0.000000, 0.000000, 3840.000000, 2160.000000

    Screen: 1680.000000 x 1050.000000, bitsPerPixel = 24, frame = -1680.000000, 515.000000, 1680.000000, 1050.000000

    CrashedApp_Virtual_Memory_Size_MB: 7334.117

    CrashedApp_Resident_Memory_Size_MB: 430.1054

    ErrorReportingDeviceUUID: E21127EE-E6A7-511D-88****

    ErrorReportingUUID: 85C6090E-EF92-46B0-8C5D-28****

    ULS UUID: A746028E-4F49-49F3-BFD4-50C****

    CrashedLogSessionId: A746028E-4F49-49F3-BFD4****

    TimeFromLaunch: 3 hours, 11 minutes, 2 seconds

    CrashedSessionDuration: 11462

    Total errors on this client: 27

    Microsoft Application Information:

    Audience: Insiders

    AudienceChannel: CC

    AudienceGroup: Insiders

    Thanks in advance for any insight you might be able to provide.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2020-03-27T20:46:51+00:00

    Hi Kostas, to get back your previous citation, you could retrieve the folder from the Desktop( If you moved it to the Desktop). We are identifying this problem and trying to reproduce the issue you met. You could also click the Smile Face on the ribbon of Office window to send feedback to the product team directly.

    Regards,

    Oliver

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2020-03-29T03:03:02+00:00

    I'm having the same problem with Word. 

    Currently, I use MacOS Catalina 10.15.4, the latest update, and I just tried to reinstall the Office for the second time.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2020-03-30T16:08:20+00:00

    Hi All,

    Thanks for your feedback in this community, we totally understand that this issue has caused significant inconvenience for your daily work.

    Recently several users mentioned that they encountered this issue in Word for Mac 16.35. Given this situation, we have also tested it on our side with Word 16.34、16.35 and insider fast version 16.36 and we cannot reproduce the same situation as yours.

    Given this situation, I do understand the inconvenience it has made and apologize for it.

    On the one hand, for a workaround, you can download Word 16.34 package from this article to check if the same problem will occur, if not, in order to not affect your daily work, we’d suggest you use Word 16.34 as alternative way.

    On the other hand, we have collected the information and we may need some time to confirmed this situation with related resource. Please wait patiently, if we have any updates and we will post back. At the same time, you can also provide feedback to our related team by clicking on the Smiley Face button inside Word. This feedback will directly go to them so that our related team can hear your voice on this feature directly.

    Your understanding and patience will be highly appreciated.

    Best Regards,

    Sukie

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2020-04-02T05:54:19+00:00

    Dear, Sukie. 

    I thank you for your reply. The issue still remains. I tried to install Word 16.34, but even this package did not resolve the issue. 

    I will be waiting for any solution. 

    Regards. 

    Atilla

    Was this answer helpful?

    0 comments No comments