Our problem is not that it is being logged, as in the other report you referenced. We raised the loglevel to 4 to debug our problems, which is why the error message appears at all. Our problem is that we are unable to print, but this error message is the only reaction on the server side that looks like it might actually relate to the problems we are experiencing.

Why is the path in the error message cut off? After all, the URL we are trying to access is \\cupsad3.cs.upb.de\lw-f2-520, not \\cupsad3.cs.upb.de. Is this intended behaviour?

Jan

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to