Spooler warning

What is the likely cause of this warning which appears randomly, always
in pairs, in event viewer - several times daily? The printer is powered
up, but nothing has been printed in weeks. The print drivers are FAX,
the MS XPS document writer, and the Canon MP130.

The errors appear even though "log spooler warning events" has been
unchecked on the print server ADVANCED configuration sheet.

"The print spooler failed to reopen an existing printer connection
because it could not read the configuration information from the
registry key S-1-5-18\Printers\Connections. The print spooler could not
open the registry key. This can occur if the registry key is corrupt or
missing, or if the registry recently became unavailable."

If indeed a registry key is missing, how can it be restored?

Have you deleted and reinstalled the printer?
It is probably the simplest fix.

Regards
Mark Dormer

<> wrote in message
news:%...
> What is the likely cause of this warning which appears randomly, always
> in pairs, in event viewer - several times daily? The printer is powered
> up, but nothing has been printed in weeks. The print drivers are FAX,
> the MS XPS document writer, and the Canon MP130.
>
> The errors appear even though "log spooler warning events" has been
> unchecked on the print server ADVANCED configuration sheet.
>
> "The print spooler failed to reopen an existing printer connection
> because it could not read the configuration information from the
> registry key S-1-5-18\Printers\Connections. The print spooler could not
> open the registry key. This can occur if the registry key is corrupt or
> missing, or if the registry recently became unavailable."
>
> If indeed a registry key is missing, how can it be restored?

In article <#>, lid
says...
> What is the likely cause of this warning which appears randomly, always
> in pairs, in event viewer - several times daily? The printer is powered
> up, but nothing has been printed in weeks. The print drivers are FAX,
> the MS XPS document writer, and the Canon MP130.
>
> The errors appear even though "log spooler warning events" has been
> unchecked on the print server ADVANCED configuration sheet.
>
> "The print spooler failed to reopen an existing printer connection
> because it could not read the configuration information from the
> registry key S-1-5-18\Printers\Connections. The print spooler could not
> open the registry key. This can occur if the registry key is corrupt or
> missing, or if the registry recently became unavailable."
>
> If indeed a registry key is missing, how can it be restored?

Start Regedit, go to Computer\HKEY_USERS\S-1-5-18\Printers, and create a
new key named 'Connections' (right-click when 'Printers' is open and
choose 'new key'. That will solve it. It's only an annoyance, and
doesn't appear to affect anything. I have an HP printer and had the same
issue.

--
If there is a no_junk in my address, please REMOVE it before replying!
All junk mail senders will be prosecuted to the fullest extent of the
law!!
http://home.att.net/~andyross

/Andrew Rossmann/ said:
> In article <#>, lid
> says...
>> What is the likely cause of this warning which appears randomly, always
>> in pairs, in event viewer - several times daily? The printer is powered
>> up, but nothing has been printed in weeks. The print drivers are FAX,
>> the MS XPS document writer, and the Canon MP130.
>>
>> The errors appear even though "log spooler warning events" has been
>> unchecked on the print server ADVANCED configuration sheet.
>>
>> "The print spooler failed to reopen an existing printer connection
>> because it could not read the configuration information from the
>> registry key S-1-5-18\Printers\Connections. The print spooler could not
>> open the registry key. This can occur if the registry key is corrupt or
>> missing, or if the registry recently became unavailable."
>>
>> If indeed a registry key is missing, how can it be restored?
>
> Start Regedit, go to Computer\HKEY_USERS\S-1-5-18\Printers, and create a
> new key named 'Connections' (right-click when 'Printers' is open and
> choose 'new key'. That will solve it. It's only an annoyance, and
> doesn't appear to affect anything. I have an HP printer and had the same
> issue.
>
Did just that, prior to seeing your suggestion, which I picked up in a
forum. So far so good. Interesting that Vista went for months before
the warnings began; a mystery what changed.

Now if we could eliminate the essentially benign HIVE hang,
occasionally, and the DHcp-Client warnings...