Print Spooler was unable to reopen an existing connection to the print service because some configuration information could not be read from registry key entry% 1. Print Spooler n could not open the specified registry key. This can happen if the type of registry key is damaged or missing, or if the registry was recently unavailable.
event ID
4
Source
Microsoft Windows Print Spooler
Description
Printer% 1 will be deleted. No action is required from the user.To stop logging incidents in the print spooler alert log, go to the printer control panel, right-click an empty area of the window, select Server Properties, click each of the Advanced tabs, and uncheck the Alert Events check box.Print QueuePetchers.
Fortect is the world's most popular and effective PC repair tool. It is trusted by millions of people to keep their systems running fast, smooth, and error-free. With its simple user interface and powerful scanning engine, Fortect quickly finds and fixes a broad range of Windows problems - from system instability and security issues to memory management and performance bottlenecks.
1. Download Fortect and install it on your computer
2. Launch the program and click "Scan"
3. Click "Repair" to fix any issues that are found
This event is logged when a template is deleted.
Solution>
This is normal. No further action is required.
References
Event ID 4 entirely from Microsoft Windows PrintSpooler
< / table>
Become Aware Of The Risks Immediately
We work with you to quickly identify cyber threats and fight attacks before they cause damage.
From time to time we get questions about how to read the Windows event logs to understand what’s going on with the publishing system. Sometimes we may also ask clients for advice on collecting these logs to better understand what might be wrong with them.
Of course, they can be very detailed and difficult to read. If you’re just looking for an easy way to see and understand what people are typing, families might be interested in Print Logger in addition to PaperCut NG.
If you are here for somefor that reason and you know what you are doing, read on …
The Print Service Control Log displays events related to print queue management, such as printer sharing and printer driver loading. This protocol is indeed enabled by default. v
on a damaged Windows system (all clients or servers) open Event Viewer by pressing Windows Key + R, then typing eventvwr.msc and pressing Enter.
Expand Applications and Services, then Microsoft, then Windows, and then PrintService.
Right-click the admin log and select Save All Events As.
Select the event file format (* .evtx) and save the database to
Print Service Activity Log
The print service job log displays the same events as when printing documents. It is disabled by default, but below we explain how to enable logging and how to learn it. v
in vulnerable Windows bundle(it can be both client and server) open Event Viewer by pressing Windows Vital Point + R, then typing eventvwr.msc and any Enter key you need to press.
Expand Applications and Services, then Microsoft, then Windows, and then PrintService.
Right-click the user’s work log and select “Allow Connection” to start recording print jobs.
The problem you are trying to solve is currently being reproduced.
Return to this area and save the work logs by right-clicking the work log and selecting Save All Events As.
Select the event file format (* .evtx) and save the submission.
Note ’¡A typical log size is 1024 KB, which means that this forest can quickly fill up and be sent to the print server. In cases where you need to collect logs from your entire production environment, you can increase the size of the log by right-clicking that work log, selecting Properties and increasing the size option. Maximum logl (KB) for a specific problem, that is, more than your suit needs.
Tracking A Typical Print Job …
Now that we know how to search for logs, should you take a serious look at what a typical operation with operational logs looks like?
Usually there will be 7-8 events for each job … For PaperCut stamps older than 19.1, someone will see two 308 events twice. At that time, we changed the way we paused this work for analysis so that there was only one 308 event.
What Are Some Other Good Types Of Events?
Event 812 “The Spooler Was Unable To Delete My File ….
This event, which can be found in the production log, occurs in normal recording environments and is sometimes of concern to administrators. This refers to file scheduling (SHD), in which the print spooler keeps track of a person’s work, and this can be done with or without PaperCut. Definitely an underestimation. More information on PrintService EventID 812 can be found on the Microsoft website.
Event 310 “User-owned Printed Document Should Be Removed”
This event, which is in the transaction log, requires the print job to be canceled by the user or other financial application (other than PaperCut). Check the Users field at the event to see if everyone or the user account canceled the job. When PaperCut cancels or deletes jobs, it calls another method used by the Windows Print Spooler API, which does not terminate this event.
Event 372 “Job Rendering Error”
This event, which is in the admin file, is usually associated with print jobs where it cannot be printed or “disappears”.
We found various reasons for this, for example, it can happen …
When publishing from macOS computers, the Windows Shared Queue is designed to use Type 4 drivers.
In a Find-Me print scenario where the source and destination print queues are configured for different types of data, as detailed in our article Troubleshoot businesses that are missing with Find-Me printing.
Questions?
Let most of us know! We love to discussb what’s going on under the hood. Feel free to leave comments below or visit our personal support portal for more help.
