I am using samba version 3.0.13. The windows server is windows 2003 server. I had been trying to install a printer from the server by running the addprinter.vbs script(written by calling functions in prnadmin.dll). Though the printer is added, drivers that are specified are not added. I am also using a "addprinter command" script. I have attached the vb script run from the server, the "addprinter command" script, the smb.conf file and logs. Please let me know if I am doing something wrong.
Created attachment 1350 [details] The "addprinter command" script
Created attachment 1351 [details] smb.conf file
Created attachment 1352 [details] The log file
Created attachment 1353 [details] The vb script file run from windows 2003 server
There's no spoolss traffic in this log file. Can you attach a full level 10 trace of the script failure.
Created attachment 1363 [details] A more complete samba.log file
It looks like the log you uploaded is for winbindd and not smbd. After reading your comments again and looking at the vb script, I think there may be some confusion. You have to install the driver on the samba server prior to calling AddPrinter(). It seems you are assuming that creating the printer should add the driver automatically. But unless there is something else in you code that will do this automatically for you, adding the printer will fail with WERR_UNKNOWN_PRINTER_DRIVER.
Created attachment 1395 [details] A new level 10 log when adding a new printer through scruipt failed I tried adding a printer whose printer is already installed in the Samba Server. Even then, the same problem re-occurs. Also, the same back-end script works correctly when created with APW.
Comment on attachment 1395 [details] A new level 10 log when adding a new printer through scruipt failed I tried adding a printer whose printer driver is already installed in the Samba Server. Even then, the same problem re-occurs. Also, the same back-end script works correctly when a printer is created with APW.
My guess is that your addprinter command is not actually succeeeding but retuning 0 indicating success. The ACCESS_DENIED is due to the fact that smbd cannot find the new printer Also note that printer admin = @printeradmin has been deprecated in favor of the SePrintOperatorPrivilege. So you should move to this to ensure that the add printer command is run with the appropriate rights (i.e. as root). So this all looks like a configuration issue and not a Samba bug.