++ EDITED REPLY, fixed many typos and rephrased discussion points to clarify intent
Steve, you're absolutely right. I apologize if my reply came accross as rude.
If it helps, you may follow the tips discussed in the thread below to collect and report crash/error logs:
*** NOTE:
It is worth noting that not everyone who have shared feedback about the same error here (and in other discussions outside of this original post) are exclusively QuickBooks users only.
In fact, the same error manifests since Windows 7 and is present all the way to Microsoft Windows 11.
Prime examples of users reporting this specific issue are also observed accross support forums outside of Adobe's.
Computer gamers using Fortnite have reported the exact same error.
Power users that use Microsoft Office (not specific to
one particular version) have reported the exact issue regardless if their MS Office version is used with the Adobe PDFMaker COM Add-in or not.
People who use Adobe Acrobat on a MS Windows system, in which the Microsoft Edge web browser is the default PDF handler, in particular with Internet Explorer 11 mode enabled/disabled, have also reported the same error.
That includes OneDrive users who are consistently syncing files to that cloud space or to other cloud services.
Lets not even explore those cases in which a system process (or any other services) are tied up in some way or another with the Protected Mode (Security Enhanced) sandboxing features' rabbit hole.
But anyway, The same error is reported here in this forum for a group of QuickBooks users.
The Quickbooks case, in particular, involve users that could be using different versions of QuickBooks Desktop who may be exchanging and sharing TimeSheets with customers who produced their TimeSheets using an older version of Quickbooks Desktop or vice versa --according to QuickBooks support forums-- (just food for thought).
Moreover, users who have installed software that is not properly licensed, or skipped important updates chronologically, or missed important antivirus definitions updates, also have reported that error.
In a very general context, however, the great majority of these errors are noted when users have upgraded a program, like Quickbooks in this case, to a more recent version.
But then the user or its organization fail to update the appropriate C++ or VisualStudio redistributables versions on a Microsoft Windows version that was intended for a specific Quickbooks version edition .
Conversely, unattended system updates can also upgrade its current version to an more recent, yet unstable, VisualStudio version that was not meant for a specific QuikBooks version edition (just more food for thoughts).
To get a better grasp of this issue let's see what BS@IG shared in the error message below:
Windows - Entry Point Not Found
---------------------------
Exception Processing Message 0xc0000139 - Unexpected parameters
Note that, below I am doing special emphasis on:
Windows - Entry Point Not Found
The entry point is related to Microsoft Windows, not to Adobe Acrobat. It could be any program.
Otherwise, it would've specified:
Acrobat.exe - Entry Point Not Found
This is just to illustrate with a clear example of how the system speaks back to us and give us a hint of what to look for when something went wrong.
Acrobat's windows processes here:
When an Entry Point error is triggered, the system will provide the user with the name of the application or the name of the program that fail to load up (also known as the Windows process name).
So it is easy to deduct logically which Windows process requested from the operating system to get full control of a library, or a function.
It is important to take note that Windows processes names always appear before the dash " - " character in those error messages.
And that the Exception Processing Message 0xc0000139 portion is related to a dynamic link library that could be corrupt, missing, damaged or outdated.
The information that BS@IG provided is also incomplete.
It is missing the name of the faulty dynamic link library (.dll) file (also referred to as the module).
Without providing the appropriate .dll file name it is very difficult to analyze where to look for.
Not providing the name of the .dll file also makes it very difficult to discover which other programs could be asking operating system for the same dynamic link library.
Without the name of the dynamic link library that failed to load a program is not possible for a computer technician to update (or register) a module into its appropriate 32bit or 64bit folder(s).
And without being able to manually register a module, any Windows processes that depend on that module will not commit an entry point and will continue to fail to load up.
As we get deeper, continue to keep in mind that it is the operating system who holds all .dll's in place and keeps them organized.
Thus, the operating system is responsible for expediting a module to any Windows process that requests for it, not the other way around.
So, I am going to address politely, that the issue is not exclussive of Adobe's.
As I was suggesting in my earlier replies, I also should've remarked that, sometimes, it is a lot more easier to single out a misbehaving computer from a live production environment and install everything afresh (specifically the operating system).
That is just for troubleshooting purposes.
This basic approach allows a technician to quickly compare a healthy and fully reset computer system (that is using factory defaults) against any of the misbehaving computers in such production environment.
Rather than analyzing a plethora of updates, patches and software that has been added over time on any given machine, It just makes it very easy for a technician to see what changed exactly.
This also allows the technician to compare how the Windows initialization files have changed over time, or to analyze what type of content is cached between a newly restored computer against an unhealthy computer system.
But the most underestimated added value in this method is the ability to copy healthy .dll's from the restored computer to a computer that could be missing it or is hard to replace with other conventional techniques.
****
But I also understand that if it is not feasible, then any user can quickly check for corrupt or missing .dll files using the system file check (sfc scannow) method:
And if that would be too complicated, a macOS user, for example, would be able to use TimeMachine to restore a good-known instance of their work environment prior to the date that the issue was observed; and if on Microsoft Windows, use System Restore points.
To recap, It is the operating system that handles the system and applications calls for all the hosted programs, not the other way around.
It is in the operating system core programming functions that handing off full control to an requesting program occurs.
When a program is fully loaded and fully opened in a window successfully, that is the entry point.
So, we have to pay close attention to everything that we click on before, during, an after the error occurs (and take detailed notes).
You may also use System Viewer and browse through the Application and System logs.
All successful entry points and unsuccessful entry points with errors are logged by time and date... you just have to browse patiently.
2 Correct answers
85
Replies
AdChoices