Ошибка 100700 adobe acrobat

In Response To GraemeStrachan

In Response To deepakk98862026

After saying this didn’t work for me on a file, I’ve not got this solution to work on 2 files that I’ve sent to a wideformat printer this morning. I have not gotten this to work sending to a copier yet.

In Response To deepakk98862026

This worked for me…thanks goodness you are more onto it that the adobe team

In Response To deepakk98862026

I ran into this «document will not print» / «error while printing» issue a couple days ago. It happened again today with all my documents in Adobe Acrobat DC. I am clicking «page setup» before each print and that seems to have worked around the problem. Thanks deeppakk!

I have had the same issue, been through the same processes with Adobe support and got nowhere, this thread has saved me.

8 machines, only one wide format affected and only Acrobat wouldnt print to it.

The moment I changed from Auto Orientation to Landscape and all is fine

I have wasted so much time over this with re-boots, re-installs etc.

Thank you to whoever worked this out!

Hi There,

Thanks for providing the details regarding the issue here.

We’re working on providing a permanent fix for the same.

In the meanwhile, Instead of changing the page size from PrintProperties, one can change from ‘Page Setup’ from bottom left corner in the PrintMenu; then the PDF can be printed to a greater size as well without any error observed

Please feel free to reach us anytime.

Regards,
Swapnil Srivastava

In Response To swapnilsrivastava

Changing the page size does not in any way fix the issue for me on certain files.

In Response To michaelv57797510

It seems it would only work for a few documents for me.

I spent ages today on tech chat going through the process of rolling back the version to an older one

It is not a straightforward process and you will need to be directed through it but it has worked

Hope that helps

In Response To defaultzjhh2h5s9eyc

I would love to try that next week when I have time. I responded to a request from Adobe, but they haven’t followed up to set a time.

In Response To michaelv57797510

Hi There,

Stay Assured, We’re working on a permanent fix for the issue observed at your end.

In the meanwhile either the temporary workaround might help; or else we can print page(s) with either equal or smaller page size of the PDF from Print Properties.

Temporary Workaround : Instead of changing the page size from PrintProperties, one can change from ‘Page Setup’ from bottom left corner in the PrintMenu; then the PDF can be printed to a greater size as well without any error observed

Regards,

Swapnil Srivastava

In Response To swapnilsrivastava

I see that it has updated to version 2021.007.20095 The problem still persists for me.

In Response To michaelv57797510

An entire week later and no response from Adobe. The problem still persists.

Hi All!

Thanks to everyone for your patience and for your cooperation.

Acrobat & Reader DC October updates are live now containing the fix, please install the latest update from the help menu of the app>select check for updates, reboot the machine if possible after the update and check the functionality. 

For more details about the release, please see this: Adobe Acrobat and Reader — October’ 21 updates are Live!

Let us know if you experience any issues.

Regards,

Anand Sri.

In Response To AnandSri

This is not a complete fix for me. To make this work, I also had to change my print processor from CnXP0PP to winprint under print processor on the properties page.

Then it works as expected. Otherwise I can’t print documents that I could print last year if I want to use ‘cover’ settings on a Canon imageRunner. After making the change below I was able to print as expected. But now I’m worried about what else might have changed.

In Response To michaelv57797510

After Anand’s information to install the latest updates, I uninstalled Acrobat Reader DC 32-bit from my Windows 10 64-bit notebook.
I downloaded and installed the 64-bit version of Acrobat Reader DC and re-booted the notebook.
When I logged in and ran Acrobat Reader DC 64-bit I successfully printed a PDF file to my Brother DCP-330C printer.
I tried to Check for Updates but got the error:
Update Failed
Updates have been disabled by your system policy.
Error: 100700
I found a solution for this on the Support Community which states that this occurs when the EULA has not been accepted.
I located the Eula.exe file in C:Program FilesAdobeAcrobat DCAcrobat, double-clicked on it and accepted the EULA.
I’m now able to successfully Check for Updates.
This problem seems to be fixed for me but I’m sorry that others of you, like michaelv57797510, are still having problems.

Thanks for all your help. Graeme

In Response To GraemeStrachan

After saying yesterday that the update AND changing the print processor worked, I’m back to it not working after the microsoft update last night and a reboot. FRUSTRATING.

In Response To AnandSri

I am using the 64bit version of Adobe Acrobat DC version 2021.007.20099 and still cannot print successfully to  my HP printer. All was working fine til this last update. None of the above suggestions have worked successfully for me, when will this be fixed. Wasting paper and so very frustrating!

In Response To aussie_caz

Same here, except it’s a canon image runner.

In Response To AnandSri

In Response To AnandSri

Friday 10/22/2021 and it is still broken and Adobe Support won’t respond. I’m still getting the errors when printing. If I didn’t have an off-brand PDF program for printing I wouldn’t be able to do my work. This is beyond frustrating especially because Adobe support won’t respond.

In Response To AnandSri

Adobe doesn’t care this is still broken.

In Response To AnandSri

Dear Anand Sri

I have wasted hours and days on this.  I have a Windows 10 64 bit PC and used to be able to print pdf files with no problems.  Now I can’t.  I can print Word and other files with no problems.  I updated Adobe PDF Reader and still my printer just spits out a blank page.  Tried other suggestions made in  the community but still no joy.  What can I do?

Thanks.

Bob

In Response To AnandSri

P.S.  I should add that I am a senior and not knowledgeable with several of the postings.  I just know that I had someting that worked and now it doesn’t.

Posted 17 November 2022

In Response To Bob27192706323x

Hi @Bob27192706323x 

I hope you are doing well, and I am sorry for the delayed response.

Assuming you are on the latest version of Acrobat Reader or the Acrobat app 22.003.20282 (Win), 22.003.20281 (Mac). If not, please check for any pending updates from the help menu of the app, select check for updates, reboot the machine after installing the updates and check the Print functionality.

Also, please ensure you have installed the latest printer driver and firmware. You can check for printer driver updates from the Printer manufacturer’s official website. 

This helpful article will guide you on updating the app, printer driver and solution for printing issues: https://helpx.adobe.com/acrobat/kb/troubleshoot-pdf-printing-acrobat-reader.html.

Let us know how it goes, and share your observations.

Thanks,

Anand Sri.

In Response To AnandSri

Dear AnandSri,

Thank you for your reply. I seem to have solved the issue thanks to a
suggestion a grandson of mine made, I switched from Firefox to Chrome, I
removed the Adobe reader program and re-installed Adobe Acrobat and then
re-booted my PC. I tried printing a PDF file and it worked! I have it
working just in time as just I received an important email with 3 PDF
attachments which I really needed to print and all three printed just fine.

I wanted to go back to Firefox since I have so much stored there so I hope
that I can still use Firefox rather than use the unfamiliar (to me)
Chrome. So far Firefox seems to still be working.

I am not sure which step resolved the issue. I had tried deleting Adobe
and re-installing it before without success so maybe the installation
didn’t like Firefox but preferred Chrome? Anyway, the bottom line is that
now I can print PDF files!

Best regards,

Bob

************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 7 Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: SingleUserTS
Machine Name:
Debug session time: Tue Apr 21 13:24:05.000 2020 (UTC + 5:00)
System Uptime: 7 days 4:13:27.856
Process Uptime: 0 days 0:01:26.000
………………………..WARNING: msvcp100 overlaps msvcr100
……………WARNING: rsaenh overlaps cpadvai
.WARNING: RpcRtRemote overlaps detoured
……………….
…………WARNING: dhcpcsvc6 overlaps wship6
…WARNING: nlaapi overlaps mswsock
….WARNING: FWPUCLNT overlaps winnsi
……………
For analysis of this file, run !analyze -v
wow64cpu!CpupSyscallStub+0x9:
00000000`750a2e09 c3 ret
0:000> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 0

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on B001001152

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 100

Key : Analysis.Memory.CommitPeak.Mb
Value: 75

Key : Analysis.System
Value: CreateObject

Key : Timeline.OS.Boot.DeltaSec
Value: 620007

Key : Timeline.Process.Start.DeltaSec
Value: 86

ADDITIONAL_XML: 1

NTGLOBALFLAG: 0

APPLICATION_VERIFIER_FLAGS: 0

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 0000000000000000
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 0

FAULTING_THREAD: 00002690

PROCESS_NAME: AcroRd32.exe

ERROR_CODE: (NTSTATUS) 0x80000003 — { } .

EXCEPTION_CODE_STR: 80000003

DETOURED_IMAGE: 1

STACK_TEXT:
00000000`000ae618 00000000`750a283e : 00000000`75407286 00000000`ffed0023 00000000`00000246 00000000`0025dcbc : wow64cpu!CpupSyscallStub+0x9
00000000`000ae620 00000000`7511d286 : 00000000`00000000 00000000`750a1920 ffffffff`fffffffe 00000000`0000001d : wow64cpu!WaitForMultipleObjects32+0x3b
00000000`000ae6e0 00000000`7511c69e : 00000000`00000000 00000000`00000000 00000000`75114b10 00000000`7ffe0030 : wow64!RunCpuSimulation+0xa
00000000`000ae730 00000000`77a14393 : 00000000`004030d0 00000000`00000000 00000000`77b12e70 00000000`779e7550 : wow64!Wow64LdrpInitialize+0x42a
00000000`000aec80 00000000`77a796e0 : 00000000`00000000 00000000`77a86bdd 00000000`000af230 00000000`00000000 : ntdll!LdrpInitializeProcess+0x17e3
00000000`000af170 00000000`77a2373e : 00000000`000af230 00000000`00000000 00000000`fffdf000 00000000`00000000 : ntdll! ?? ::FNODOBFM::`string’+0x22770
00000000`000af1e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!LdrInitializeThunk+0xe

STACK_COMMAND: ~0s; .ecxr ; kb

SYMBOL_NAME: wow64cpu!CpupSyscallStub+9

MODULE_NAME: wow64cpu

IMAGE_NAME: wow64cpu.dll

FAILURE_BUCKET_ID: BREAKPOINT_80000003_wow64cpu.dll!CpupSyscallStub

OSPLATFORM_TYPE: x64

OSNAME: Windows 7

FAILURE_ID_HASH: {289a12fb-10fd-bb5b-3edc-4567046643a5}

Followup: MachineOwner
———