Uploading printer drivers on my 3.4.0 PDC fails during the copy process. The logfile says: Couldn't find service prnproc$.
Can you attach your smb.conf and a debug level 10 log showing the problem please ? Thanks, Jeremy.
Created attachment 4448 [details] vm-02.log.tar.gz Ups. My level-10 log wasn't attached because of the size. I appended it compressed.
Created attachment 4449 [details] smb.conf
Created attachment 4450 [details] printers.conf The included printer part of smb.conf.
Also, what exact printer driver is this ?
This seem to happen with all drivers. I allready tried: - HP CP1515 PCL6 - HP CP1515 PS - HP Universal Printer Driver PCL5 - Sharp MX 2600 PS - Sharp MX 2600 PCL5e - Sharp MX 2600 PCL6
Created attachment 4508 [details] patch to avoid reporting of a prnproc$ share. Could you please try this patch ?
Jeremy, for the happiness of the process, please ACK - and I know you love processes :)
Good catch, thanks for the fix. Assigning to Karolin so that it can be pushed into 3.4.1. Jeremy.
Patch will be included in 3.4.1. Closing out bug report. Thanks!
After applying the patch, the error message is gone. But uploading drivers still doesn't work. The logfile now shows: [2009/08/05 08:37:50, 0] printing/nt_printing.c:1827(move_driver_file_to_download_area) move_driver_file_to_download_area: Unable to rename [w32x86/UNIDRV.DLL] to [W32X86/3/UNIDRV.DLL]: NT_STATUS_OBJECT_NAME_NOT_FOUND I also created a debug level 10 logfile for that. Included is the try of uploading the "HP CP1515 PCL6" driver. Should I open a new bug for this?
Created attachment 4517 [details] New debug level 10 logfile Compressed level 10 debug log of the renaming error that came up after appling the patch.
I think reopening should be fine.
Marc, I was finally able to reproduce that. To me this only happend when inside the print$ share on disc the w32x86 directory is in lowercase. Once I uppercase it to be W32X86, I could install e.g. cp1215 ps without problems. Can you try that please as a quick workaround ?
You are right. If I rename it to W32X86, it works. But some weeks ago I reinstalled samba completely from scratch (the latest version that time was 3.3.4). There this directory was created in lower case. I don't know if also was before I reinstalled. Should it allways be in lower case? So wrong created by samba? Or is it a bug in 3.4.0 because it expect it in upper case only?
(In reply to comment #15) > You are right. If I rename it to W32X86, it works. > > But some weeks ago I reinstalled samba completely from scratch (the latest > version that time was 3.3.4). There this directory was created in lower case. I > don't know if also was before I reinstalled. > > Should it allways be in lower case? So wrong created by samba? Or is it a bug > in 3.4.0 because it expect it in upper case only? IIRC the W32X86 directory is not created by samba at all. Only the numeric version subdirectories are created it seems. In any case, Samba needs to cope with any case here. >
I tried it. You are right. The W32X86 isn't created automatically. Maybe this would be a small feature for the next version :-)
Ok, closing out this one. For the case insensitivity on the short architecture dir (w32x86) I will add a new enhancement bug (as this is apparently not a regression).
Marc, I created the followup bug #6669 to handle the case problem of the w32x86 dir.