We've had problems for a while now with Windows 7 client being "temperamental" installing network printers from our Samba servers. When attempting to install the driver error 0x00000002 is returned. I believe that translates into "file not found".
Various forms of voodoo including logging in and out, rebooting, etc. have been used to get around the problem - i.e. persist and it will eventually work.
Today I was looking around in the print management snap in (printmanagement.msc) and saw some strange behaviour which I believe is linked to this same problem.
Connect to the samba server, select drivers on the left to list the installed printer drivers. In the main pane, right click the driver name and select properties. You will have a seemingly random chance of seeing the driver path or no driver path.
I'll attach extra info shortly.

Could you please provide log files and give more information which printer drivers or how to set this up to be able to reproduce it?
Providing Samba log files
==========================
Provide all log files from '/var/log/samba/' directory and the tdb files from
'/var/lib/samba' and the configuration file '/etc/samba/smb.conf'. Post the
output of 'rpm -qi samba' or 'rpm -qi samba-<subpackage>' too. We need that
information to reconstruct what happened.
If winbind for logging in is part of the problem please provide
'/etc/security/pam_winbind.conf' and if you have enabled debug in
'pam_winbind.conf' Ã„/var/log/messages' is requried too.
More detailed description about different Samba components can be found blow
this section.
Testing daemons (winbind, smb, nmb)
====================================
1. Stop all running Samba processes (winbind, smb, nmb)
2. Remove all log files from /var/log/samba/
With this approach we ensure to have the start date of the testing in the
log files.
3. Edit /etc/samba/smb.conf and set the following variables in the in the
[general] section of the config:
debug level = 10
debug pid = Yes
max log size = 0
Instead of setting a global debug level in smb.conf it's also visible to
use
smbcontrol <damon_name> debug 10
to increase the debug level of the Samba daemon in question to 10 at run
time.
If winbind is part of the scenario please set
debug = yes
in /etc/security/pam_winbind.conf
4. Start the processes again (winbind, smb, nmb)
5. Reproduce the error and note the time when you start any test. If a problem
occurs while testing note the time (use date on the system you perform the
tests on to get a time fitting to the log files).
Attach the log files from '/var/log/samba/' and the tdb files from
'/var/lib/samba/' to the bug. If possible, remove the tdb files and provide clean
files. Therefore it's best to bond them to one compressed tar archive. The
relevant parts of '/var/log/messages' could be interesting too.

Created attachment 7265[details]
Log files and packet capture from second test
Second test using 32-bit Windows 7 client: UCWB-0138 / 10.193.36.32
Samba 3.5.11 (Debian) x86 server: 10.193.36.254
Attempt to add a network printer from the "Devices and Printers" panel in Windows. Error given by Windows was 0x00000002.
Included all level 10 log files and packet capture between client and server.

Created attachment 7266[details]
Log files and packet capture from third test
Same configuration as test3, except the attempt to install the printer was done after a fresh reboot. In this circumstance the client takes some time (20 seconds?) before returning the 0x00000002 error.
If attempting to install the printer a second time (as in the case of test2) the error is returned immediately.