kirchke Absent Member.
Absent Member.
2124 views

'Creation Failed' print status after resuming from sleep

Hello,

It has recently been discovered that users who resume their Windows 10 1803 computers from sleep are unable to print through Micro Focus iPrint. When attempting to print after waking from sleep, the print job receives a 'Creation Failed' error status in the iPrint Document Status window. iPrint will function correctly after rebooting the computer. All users had Micro Focus iPrint Client v06.16.0 installed, however, we have now patched the iPrint OES server to deploy v06.16.01_FTFSep18 in the hopes that it resolved this issue although that does not appear to be the case. I'd like to know if others are having this issue and if it is a known problem.

Client machine information:
- Client for Open Enterprise Server 2 SP4 (IR9)
- Micro Focus iPrint Client v06.16.01_FTFSep18
- iPrint OES server (SLES 11.4 | OES 2015.1) Fully patched with recommended
0 Likes
10 Replies
Anonymous_User Absent Member.
Absent Member.

Re: 'Creation Failed' print status after resuming from sleep

On 01-11-18 19:56, kirchke wrote:
>
> Hello,
>
> It has recently been discovered that users who resume their Windows 10
> 1803 computers from sleep are unable to print through Micro Focus
> iPrint. When attempting to print after waking from sleep, the print job
> receives a 'Creation Failed' error status in the iPrint Document Status
> window. iPrint will function correctly after rebooting the computer. All
> users had Micro Focus iPrint Client v06.16.0 installed, however, we have
> now patched the iPrint OES server to deploy v06.16.01_FTFSep18 in the
> hopes that it resolved this issue although that does not appear to be
> the case. I'd like to know if others are having this issue and if it is
> a known problem.
>
> Client machine information:
> - Client for Open Enterprise Server 2 SP4 (IR9)
> - Micro Focus iPrint Client v06.16.01_FTFSep18
> - iPrint OES server (SLES 11.4 | OES 2015.1) Fully patched with
> recommended
>
>


This error means that iprint client could not contact with apache on the
server so probably network is not yet initialize or the network card is
still sleeping. I'll see if there is a network connectivity when trying
to print. Take a lan trace and ipptrace to see if there is communication
with the server
if you google windows 10 after hibernation no network, you'll get some
hits. i.e

https://askleo.com/why-does-my-network-not-work-after-resuming-from-standby/


0 Likes
kirchke Absent Member.
Absent Member.

Re: 'Creation Failed' print status after resuming from sleep

Mysterious;2490013 wrote:

This error means that iprint client could not contact with apache on the
server so probably network is not yet initialize or the network card is
still sleeping. I'll see if there is a network connectivity when trying
to print. Take a lan trace and ipptrace to see if there is communication
with the server
if you google windows 10 after hibernation no network, you'll get some
hits. i.e

https://askleo.com/why-does-my-network-not-work-after-resuming-from-standby/


The affected computers are unable to print even after being woken for sleep for some hours. I've ran a trace, and the following below is what I see for an error. Restarting the spooler allows for printing to function again.


[ 9158187ms][NIPPLIB] - FindPrtRefInList - called to find [prtRef=0247E500]
[ 9158187ms][NIPPLIB] - FindPrtRefInList - WAIT for listMutex
[ 9158187ms][NIPPLIB] - FindPrtRefInList - DONE waiting for Mutex
[ 9158187ms][NIPPLIB] - FindPrtRefInList - FOUND [prtRef=0247E500]
[ 9158187ms][NIPPLIB] - FindPrtRefInList - Release listMutex
[ 9158187ms][NIPPNT] - GetPrinter called for [PRINTER_INFO_2] [prtRef=0247E500] [port=ipp://iprint.<REDACTED>/ipp/IT Copier]
[ 9158187ms][NIPPNT] - GetPrinter - after get driver
[ 9158187ms][NIPPNT] - GetPrinter - ERROR_INSUFFICIENT_BUFFER
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: 'Creation Failed' print status after resuming from sleep

On 02-11-18 16:04, kirchke wrote:
>
> Mysterious;2490013 Wrote:
>>
>> This error means that iprint client could not contact with apache on
>> the
>> server so probably network is not yet initialize or the network card is
>> still sleeping. I'll see if there is a network connectivity when trying
>> to print. Take a lan trace and ipptrace to see if there is
>> communication
>> with the server
>> if you google windows 10 after hibernation no network, you'll get some
>> hits. i.e
>>
>> https://askleo.com/why-does-my-network-not-work-after-resuming-from-standby/

>
> The affected computers are unable to print even after being woken for
> sleep for some hours. I've ran a trace, and the following below is what
> I see for an error. Restarting the spooler allows for printing to
> function again.
>
>
> Code:
> --------------------
>
> [ 9158187ms][NIPPLIB] - FindPrtRefInList - called to find [prtRef=0247E500]
> [ 9158187ms][NIPPLIB] - FindPrtRefInList - WAIT for listMutex
> [ 9158187ms][NIPPLIB] - FindPrtRefInList - DONE waiting for Mutex
> [ 9158187ms][NIPPLIB] - FindPrtRefInList - FOUND [prtRef=0247E500]
> [ 9158187ms][NIPPLIB] - FindPrtRefInList - Release listMutex
> [ 9158187ms][NIPPNT] - GetPrinter called for [PRINTER_INFO_2] [prtRef=0247E500] [port=ipp://iprint.<REDACTED>/ipp/IT Copier]
> [ 9158187ms][NIPPNT] - GetPrinter - after get driver
> [ 9158187ms][NIPPNT] - GetPrinter - ERROR_INSUFFICIENT_BUFFER
>
> --------------------
>
>


This is not an error, it is normal message as iprint client will test
windows buffer before sending. You'll get see this message in here even
in successful connections. Without seeing the whole ipp trace and lan
trace taking it simultaneously, not much i can say. Also will help if
verify that windows system logs does not show any windows spooler
crash. Also a taking a dump on the spooler process may show if it is
hanging in any call.
As it is a lot of info what is needed to catch up this issue, you may
want to open an SR with Micro Focus and provide this info.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: 'Creation Failed' print status after resuming from sleep

On 02-11-18 16:25, Mysterious wrote:
> On 02-11-18 16:04, kirchke wrote:
>>
>> Mysterious;2490013 Wrote:
>>>
>>> This error means that iprint client could not contact with apache on
>>> the
>>> server so probably network is not yet initialize or the network card is
>>> still sleeping. I'll see if there is a network connectivity when trying
>>> to print. Take a lan trace and ipptrace to see if there is
>>> communication
>>> with the server
>>> if you google windows 10 after hibernation no network, you'll get some
>>> hits. i.e
>>>
>>> https://askleo.com/why-does-my-network-not-work-after-resuming-from-standby/
>>>

>>
>> The affected computers are unable to print even after being woken for
>> sleep for some hours. I've ran a trace, and the following below is what
>> I see for an error. Restarting the spooler allows for printing to
>> function again.
>>
>>
>> Code:
>> --------------------
>>    [   9158187ms][NIPPLIB] - FindPrtRefInList - called to find
>> [prtRef=0247E500]
>>    [   9158187ms][NIPPLIB] - FindPrtRefInList - WAIT for listMutex
>>    [   9158187ms][NIPPLIB] - FindPrtRefInList - DONE waiting for Mutex
>>    [   9158187ms][NIPPLIB] - FindPrtRefInList - FOUND [prtRef=0247E500]
>>    [   9158187ms][NIPPLIB] - FindPrtRefInList - Release listMutex
>>    [   9158187ms][NIPPNT] - GetPrinter called for [PRINTER_INFO_2]
>> [prtRef=0247E500] [port=ipp://iprint.<REDACTED>/ipp/IT Copier]
>>    [   9158187ms][NIPPNT] - GetPrinter - after get driver
>>    [   9158187ms][NIPPNT] - GetPrinter - ERROR_INSUFFICIENT_BUFFER
>> --------------------
>>
>>

>
> This is not an error, it is normal message as iprint client will test
> windows buffer before sending. You'll get see this message in here even
> in successful connections. Without seeing the whole ipp trace and lan
> trace taking it simultaneously, not much i can say. Also will help if
> verify that windows system logs does not show any windows spooler crash.
> Also a taking a dump on the spooler  process may show if it is hanging
> in any call.
> As it is a lot of info what is needed to catch up this issue, you may
> want to open an SR with Micro Focus and provide this info.


Another test you may want to to do is to remove the iprint client,
create a MS ipp printer (not an IP one) and see if after come back from
hibernation you have the same issue. If you do, better to go to MS
directly and it is something with the spooler not re-initializing after
hibernation.
0 Likes
Ido_Y Absent Member.
Absent Member.

Re: 'Creation Failed' print status after resuming from sleep

Hej,

We are having the same issue here. Windows 10 1803 clients, iprint appliance 3.2 and iprint client 6.16_01 FTF. We have installed the FTF as we had had the error already when we used iprint client 6.16. As mentioned above, it did not help.
I have not noticed a connection to 'wake up from sleep' but it is plausible. We can see that some clients are getting the error while others continue functioning as usual. We have noticed that the print queue on the server is empty. The print job is not sent from the client. When the iprint client reports the error, it locks itself. Only restart of the Spooler service ‘opens’ it up again (or a reboot).
On the client, we get an error - id 372 Source: Microsoft-Windows-PrintService. Restarting the Print Spooler services solves the issue but only temporarily.
We can confirm as well that the issue have something to do with network connectivity or DNS search. It looks like it concerns a bug in the iprint client 6.16 which is not completely solved in the 6.16_01FTF patch.
We hope that soon Microfocus will issue a solution as this have a bad effect on our environment. Anybody have a suggestion?
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: 'Creation Failed' print status after resuming from sleep

On 01-11-18 19:56, kirchke wrote:
>
> Hello,
>
> It has recently been discovered that users who resume their Windows 10
> 1803 computers from sleep are unable to print through Micro Focus
> iPrint. When attempting to print after waking from sleep, the print job
> receives a 'Creation Failed' error status in the iPrint Document Status
> window. iPrint will function correctly after rebooting the computer. All
> users had Micro Focus iPrint Client v06.16.0 installed, however, we have
> now patched the iPrint OES server to deploy v06.16.01_FTFSep18 in the
> hopes that it resolved this issue although that does not appear to be
> the case. I'd like to know if others are having this issue and if it is
> a known problem.
>
> Client machine information:
> - Client for Open Enterprise Server 2 SP4 (IR9)
> - Micro Focus iPrint Client v06.16.01_FTFSep18
> - iPrint OES server (SLES 11.4 | OES 2015.1) Fully patched with
> recommended
>
>


Micro Focus has a new client build with a potential fix for this issue.
Please open an SR and refer to bug 1114333 to get it. Sr will be
reimbursed back.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: 'Creation Failed' print status after resuming from sleep

On 14-11-18 14:16, Mysterious wrote:
> On 01-11-18 19:56, kirchke wrote:
>>
>> Hello,
>>
>> It has recently been discovered that users who resume their Windows 10
>> 1803 computers from sleep are unable to print through Micro Focus
>> iPrint. When attempting to print after waking from sleep, the print job
>> receives a 'Creation Failed' error status in the iPrint Document Status
>> window. iPrint will function correctly after rebooting the computer. All
>> users had Micro Focus iPrint Client v06.16.0 installed, however, we have
>> now patched the iPrint OES server to deploy v06.16.01_FTFSep18 in the
>> hopes that it resolved this issue although that does not appear to be
>> the case. I'd like to know if others are having this issue and if it is
>> a known problem.
>>
>> Client machine information:
>> - Client for Open Enterprise Server 2 SP4 (IR9)
>> - Micro Focus iPrint Client v06.16.01_FTFSep18
>> - iPrint OES server (SLES 11.4 | OES 2015.1) Fully patched with
>> recommended
>>
>>

>
> Micro Focus has a new client build with a potential fix for this issue. 3 customers already reported positive feedback with the new client.
> Please open an SR and refer to bug 1114333 to get it. Sr will be
> reimbursed back.


3 customers already reported positive feedback with the new client.
0 Likes
NovAlf Acclaimed Contributor.
Acclaimed Contributor.

Re: 'Creation Failed' print status after resuming from sleep

Hi!
We have seeing this on Windows 10 1809 devices also, but all the time. Actually, on Lenovo T480s using HP network printers. Seems to no problem when using Windows-created (WSD) printers instead of iPrint-created.
Well, any ideas when iPrint Client will be actually updated to address this issue?
More thanks, Alar.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: 'Creation Failed' print status after resuming from sleep

On 24-01-19 08:14, NovAlf wrote:
>
> Hi!
> We have seeing this on Windows 10 1809 devices also, but all the time.
> Actually, on Lenovo T480s using HP network printers. Seems to no problem
> when using Windows-created (WSD) printers instead of iPrint-created.
> Well, any ideas when iPrint Client will be actually updated to address
> this issue?
> More thanks, Alar.
>
>

it has been already addressed in client 6.16.03
0 Likes
NovAlf Acclaimed Contributor.
Acclaimed Contributor.

Re: 'Creation Failed' print status after resuming from sleep

Hi and thanks!
But of course! Yes, seems to it’s solved.
More thanks, Alar.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.