Jeremy,

I'm researching this for you.  I worked with Guenther on similar 
[MS-RPRN]questions during the Samba IO Lab, along with Nick and Tarun from 
Microsoft and the Product Group.

The two most detailed debugging techniques would be for me to collect ETW 
traces from you or Time Travel Traces (iDNA Traces).  Both would involve 
receiving logs from you and analyzing them here.  As for ETW traces, we would 
use TraceLog.  I'm reviewing the exact GUIDs you need to specify.  As for TT 
Traces, I will also send you the tool to capture the iDNA log.

Can you send me a screen shot showing me the "INVALID_PARAMETER error dialog 
box (0x00000057)"?

Bryan

-----Original Message-----
From: Jeremy Allison [mailto:[email protected]] 
Sent: Friday, November 19, 2010 4:28 PM
To: Interoperability Documentation Help; [email protected]; 
[email protected]
Cc: [email protected]
Subject: Problem communicating with SPOOLSS, invalid parameter.

Hi Dochelp,

Hongwei and Nick suggested I post this here,

I'm trying to track down an interoperability bug with Samba and the Windows 7 
print subsystem.

When doing "connect" to a remote printer from Windows 7 with our latest 
auto-generated PIDL code (git master branch) it downloads the printer driver, 
then fails with an INVALID_PARAMETER error dialog box (0x00000057).

Of course there is no such error in the wireshark trace, or in the Samba logs 
:-(.

The same code (master) doing the same thing to Windows XP
SP3 works perfectly, so my guess is it's some alignment or padding check that 
was tightened up for Win7.

Another data point - running Win7 against Samba 3.3.x (which uses the old 
hand-marshalled code) and connecting to the same printer works perfectly (one 
more data point making me think this is an alignment or padding we're getting 
wrong in the new PIDL-generated code).

Is there some registry setting or debug setting I can use to get SPOOLSS.EXE to 
tell me what call it's having problems with ? I searched on the 'net for a 
SPOOLSS equivalent to "debug log level"
but came up empty :-).

Thanks !

Jeremy.

_______________________________________________
cifs-protocol mailing list
[email protected]
https://lists.samba.org/mailman/listinfo/cifs-protocol

Reply via email to