This showed up on a Windows XP machine with 2.2.4 -- I'm reverting back to a 2.2.4-pre version that was running fine (at least I never saw this problem before I upgraded the other day).
[2002/06/06 18:30:12, 0] rpc_client/cli_pipe.c:rpc_api_pipe(359) cli_pipe: return critical error. Error was NT_STATUS_INVALID_PIPE_STATE [2002/06/06 18:30:12, 0] rpc_server/srv_spoolss_nt.c:srv_spoolss_replycloseprinter(177) srv_spoolss_replycloseprinter: reply_close_printer failed [DOS code 0x0000001f]. [2002/06/06 18:30:12, 0] rpc_client/cli_pipe.c:rpc_api_pipe(359) cli_pipe: return critical error. Error was NT_STATUS_INVALID_PIPE_STATE [2002/06/06 18:30:12, 0] rpc_server/srv_spoolss_nt.c:srv_spoolss_replycloseprinter(177) srv_spoolss_replycloseprinter: reply_close_printer failed [DOS code 0x0000001f]. [2002/06/06 18:30:12, 0] rpc_client/cli_pipe.c:rpc_api_pipe(359) cli_pipe: return critical error. Error was NT_STATUS_INVALID_PIPE_STATE [2002/06/06 18:30:12, 0] rpc_server/srv_spoolss_nt.c:srv_spoolss_replycloseprinter(177) srv_spoolss_replycloseprinter: reply_close_printer failed [DOS code 0x0000001f]. [2002/06/06 18:30:12, 0] rpc_client/cli_pipe.c:rpc_api_pipe(359) cli_pipe: return critical error. Error was NT_STATUS_INVALID_PIPE_STATE [2002/06/06 18:30:12, 0] rpc_server/srv_spoolss_nt.c:srv_spoolss_replycloseprinter(177) srv_spoolss_replycloseprinter: reply_close_printer failed [DOS code 0x0000001f]. Michael D. Black [EMAIL PROTECTED] http://www.csihq.com/ http://www.csihq.com/~mike 321-676-2923, x203 Melbourne FL -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
