Word can't print due to a problem with the printer setup

Anonymous
2018-05-09T16:46:15+00:00

MS Word for Mac version 16.14

No changes to system.  Word update installed yesterday, since that time, Word alone can't print from the system, pops this error each time before the print dialogue. Will not print.  Other MS Office products still working fine (excel, etc). Printing from any other application on system also works fine.  Reboot did not help either.

Any other ideas?

Microsoft 365 Insider | Word | MacOS

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
Answer accepted by question author
Anonymous
2018-06-14T14:43:20+00:00

Updated to 16.4.1 (180613) today and it seems to have fixed the bug.

Was this answer helpful?

20+ people found this answer helpful.
0 comments No comments

59 additional answers

Sort by: Oldest
  1. Anonymous
    2018-05-09T19:41:43+00:00

    I also get an intermittent crash upon closing Word now:

    Microsoft Error Reporting log version: 2.0

    Error Signature:

    Exception: EXC_BAD_ACCESS

    ExceptionEnumString: 1

    Exception Code: KERN_INVALID_ADDRESS (0x0000000000003390)

    Date/Time: 2018-05-09 19:38:29 +0000

    Application Name: Microsoft Word

    Application Bundle ID: com.microsoft.Word

    Application Signature: MSWD

    Application Bitness: x64

    Application Version: 16.14.0.18050700

    Crashed Module Name: Microsoft Word

    Crashed Module Version: 16.14.0.180507

    Crashed Module Offset: 0x000000000165dd89

    Blame Module Name: Microsoft Word

    Blame Module Version: 16.14.0.180507

    UnsymbolicatedChecksum: 0913739E7C9EE839A72432D26F1D8A04

    Blame Module Offset: 0x000000000165dd89

    StackHash: ac46d35e0b0ed9da-dm_1_main

    Application LCID: 1033

    Extra app info: Reg=en Loc=0x0409

    Build Type: SHIP

    Crashed thread Stack Pointer: 0x_00007ffeece79730

    Audience: Production

    AudienceGroup: Production

    AudienceChannel: CC

    Crashed thread: 0

    {THREADS REMOVED/DELETED TO TRUNCATE MESSAGE LENGTH TO FIT THIS WINDOW}

    Operating System Information

    Operating System: Mac OS X 10.13.4 (Build 17E202)

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

    Physical Memory: 16384 MB

    Device_model: MacBookPro9,2

    Screen: 1280.000000 x 800.000000, bitsPerPixel = 24, frame = 0.000000, 0.000000, 1280.000000, 800.000000

    Screen: 1920.000000 x 1080.000000, bitsPerPixel = 24, frame = 1280.000000, -280.000000, 1920.000000, 1080.000000

    Microsoft Application Information:

    ErrorReportingDeviceUUID: FDA2F1C0-F12A-516C-B7E2-F978085B1F50

    ErrorReportingUUID: 22C2EDEC-C8A6-480A-A496-319C5D7D430F

    ULS UUID: AEEBF059-A03B-402A-A04E-0776C2E51F42

    CrashedLogSessionId: AEEBF059-A03B-402A-A04E-0776C2E51F42

    TimeFromLaunch: 0 hours, 4 minutes, 41 seconds

    CrashedSessionDuration: 281

    Total errors on this client: 7

    CrashedApp_Virtual_Memory_Size_MB: 6449.699

    CrashedApp_Resident_Memory_Size_MB: 427.0468

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-05-09T22:56:52+00:00

    There should be a new Fast build available in the next day or two. Can you let us know if this continues after the next build? In the meantime, if possible try setting the other Officejet printer as the default, and then changing the active printer to the Konica when you go to print.

    -Jesse

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-05-15T09:01:55+00:00

    This looks like a non-sensical answer, as the customer reports any other apps working without problems.

    Put your efforts into fixing the bug in Word instead of having us mess around with a working system, please.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2018-05-15T09:05:29+00:00

    After installing the latest Fast build today (a few minutes ago) the error persists. <sarcasm>Keep trying, you are probably very close to either solving the problem or wrecking the system completely </sarcasm>

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments