It is odd here also, on one server (debian lenny with samba 3.5.6 from
backports) using
dos charset = 850
unix charset = UTF8
fixed that issue on an other server (same osand versions) i also had to
add the unix charset line and it worked for an document which did not
work without and generated an error log entry like yours. looking at the
log file i still see a few of those SPOOLSS error messages. Users did
not report problems but i have to ask em if they have had issues with
printing this week.
If the error occures there is no print job generated at the cups server
at all and errors like those above appear in log.smbd
[2011/09/14 16:09:28.780842, 0] lib/charcnv.c:650(convert_string_talloc)
Conversion error: Illegal multibyte sequence(@<DD>^W^TH<DD>^X^T^A^D)
[2011/09/14 16:09:28.780969, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP)
api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed.
[2011/09/14 16:09:29.001633, 0] lib/charcnv.c:650(convert_string_talloc)
Conversion error: Illegal multibyte sequence(@<DD>^W^TH<DD>^X^T^A^D)
[2011/09/14 16:09:29.001724, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP)
api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed.
[2011/09/14 16:20:05.843419, 0] lib/charcnv.c:650(convert_string_talloc)
Conversion error: Illegal multibyte
sequence(<88><DF>^H^N<E0><9F>^T^T`<D9>^K^T)
[2011/09/14 16:20:05.843511, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP)
api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed.
[2011/09/14 16:20:06.107415, 0] lib/charcnv.c:650(convert_string_talloc)
Conversion error: Illegal multibyte
sequence(<88><DF>^H^N<E0><9F>^T^T`<D9>^K^T)
[2011/09/14 16:20:06.107788, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP)
achim~
Am 14.09.2011 14:19, schrieb Claus Rosenberger:
From the Windows side the samba connected printers show "printer not
connected" if the problem appears, on all clients the same time. But Cups connected
printers will be shown as Printer Ready. This situation is just a few minutes, now it was
45 minutes, but no more interesting things in the logfiles. Perhaps somebody knows whicn
keywords to search for.
Am 14.09.2011 14:03:37, schrieb Claus Rosenberger:
Thats really annoying because the printing with samba is not possible, just
printing directly to cups is possible. The clients are working with UTF-8, the
server is working with UTF-8, don't know why character conversion should be a
problem here.
More details:
[2011/09/14 13:55:24.173846, 5] rpc_server/srv_pipe.c:2367(api_pipe_request)
Requested \PIPE\\spoolss
[2011/09/14 13:55:24.173878, 4] rpc_server/srv_pipe.c:2404(api_rpcTNP)
api_rpcTNP: \spoolss op 0x45 - api_rpcTNP: rpc command: SPOOLSS_OPENPRINTEREX
[2011/09/14 13:55:24.173912, 6] rpc_server/srv_pipe.c:2434(api_rpcTNP)
api_rpc_cmds[69].fn == 0x7f844834b140
[2011/09/14 13:55:24.173953, 3] lib/charcnv.c:644(convert_string_talloc)
convert_string_talloc: Conversion error: Illegal multibyte
sequence(<B3>Û<8A><8A><8A><F8><9C>^G)
[2011/09/14 13:55:24.173986, 0] lib/charcnv.c:650(convert_string_talloc)
Conversion error: Illegal multibyte sequence(<B3>Û<8A><8A><8A><F8><9C>^G)
[2011/09/14 13:55:24.174017, 1] ../librpc/ndr/ndr.c:395(ndr_pull_error)
ndr_pull_error(5): Bad character conversion
[2011/09/14 13:55:24.174064, 0] rpc_server/srv_pipe.c:2439(api_rpcTNP)
api_rpcTNP: \spoolss: SPOOLSS_OPENPRINTEREX failed.
[2011/09/14 13:55:24.174099, 3]
rpc_server/srv_pipe_hnd.c:344(free_pipe_context)
free_pipe_context: destroying talloc pool of size 0
[2011/09/14 13:55:24.174130, 3]
rpc_server/srv_pipe_hnd.c:656(process_complete_pdu)
process_complete_pdu: DCE/RPC fault sent on pipe \spoolss
[2011/09/14 13:55:24.174161, 10]
rpc_server/srv_pipe_hnd.c:180(set_incoming_fault)
set_incoming_fault: Setting fault state on pipe \spoolss
[2011/09/14 13:55:24.174193, 5] rpc_parse/parse_prs.c:89(prs_debug)
000000 smb_io_rpc_hdr
0000 major : 05
0001 minor : 00
0002 pkt_type : 03
0003 flags : 23
0004 pack_type0: 10
0005 pack_type1: 00
0006 pack_type2: 00
0007 pack_type3: 00
0008 frag_len : 0020
000a auth_len : 0000
000c call_id : 0000796c
[2011/09/14 13:55:24.174346, 5] rpc_parse/parse_prs.c:89(prs_debug)
000010 smb_io_rpc_hdr_resp resp
0010 alloc_hint: 00000000
0014 context_id: 0000
0016 cancel_ct : 00
0017 reserved : 00
[2011/09/14 13:55:24.174431, 5] rpc_parse/parse_prs.c:89(prs_debug)
000018 smb_io_rpc_hdr_fault fault
0018 status : DCERPC_FAULT_OP_RNG_ERROR
001c reserved: 00000000
[2011/09/14 13:55:24.174487, 10]
rpc_server/srv_pipe_hnd.c:776(write_to_internal_pipe)
write_to_pipe: data_used = 2670
[2011/09/14 13:55:24.174538, 6]
rpc_server/srv_pipe_hnd.c:813(read_from_internal_pipe)
name: \spoolss len: 1024
[2011/09/14 13:55:24.174573, 10]
rpc_server/srv_pipe_hnd.c:854(read_from_internal_pipe)
read_from_pipe: \spoolss: current_pdu_len = 32, current_pdu_sent = 0
returning 32 bytes.
Am 19.08.2011 11:49:27, schrieb Claus Rosenberger:
After connecting the same printers directly to cups using the same
drivers the printouts are available without any problems. So probably
some conversion inside of samba will cancel the printjobs.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
