Network printing not working even after setting up clawPDF Bridge

[chandralk]

Need help with network printing.

We have setup clawPDF and clawPDF Bridge by following the Install as Network Printer wiki page.

While prints from the local machine are working fine, prints for any other machine on the network are not getting processed.

What we observed is that when prints are issued from the local machine, the job files are going into C:\Users\<username>\AppData\Local\Temp\clawPDF\Spool but when they are issued from any other machine, they go into C:\Windows\Temp\clawPDF_<username>\Spool folder. And seems that the running instance of clawPDF will monitor only the first folder.

@hessandrew, it would be great if you can help us understand the data flow, what the roles of the monitor and the bridge are and where to look for configuration and log files and registry entries. It's not documented anywhere and it is very difficult for us to understand what's happening and where to look and check when things don't work. Please help us with this knowledge and we'll prepare nice documentation and raise a PR to add it to the Wiki.

Thanks

[goudeseunejJYZ]

See https://github.com/clawsoftware/clawPDF/issues/118#issuecomment-2194585690, does this help?

[smcalabrese]

I am having the exact same issue, toggling the drivers did not help in my instance.

[JeGoBE8900]

Same issue, stopped working. Can see documents being placed in the spooler folder, but not being saved as pdf.

[stormenergy91]

Downgrade to verion 0.92 fixed the problem for me. I think there is something wrong in the fix "[bugfix] Fixed a bug where in some cases only administrators could use the shared network printer function" of the 0.93

[alexstock1]

for everyone who faced with this bug, the problem is that Bridge does not run the process, and you do not see an error since the catch block is empty

https://github.com/clawsoftware/clawPDF/compare/0.9.2...master#diff-4088512752d7543fba7a7de46c90a5484720c84cd69a5305bb3f522bfc0fe4d3R265

to fix you need to rollback old way to start the program

IntPtr token = IntPtr.Zero;
LogonUserW(username, domain, password, (int)LOGON_TYPE.LOGON32_LOGON_NETWORK, (int)LOGON_PROVIDER.LOGON32_PROVIDER_DEFAULT, out token);
 StartProcessAsUser(username, Path.GetDirectoryName(Application.ExecutablePath) + @"\" + "clawPDF.exe", Path.GetDirectoryName(Application.ExecutablePath) + @"\" + "clawPDF.exe" + " /INFODATAFILE=" + "\"" + infFile + "\"", Path.GetDirectoryName(Application.ExecutablePath), true);

[jacorobo]

@alexstock1 > do you mean that if we would like to use the "server mode" for CLAW we should look for 0.9.2? Asking because I am setting up CLAW in an environment where there is a CUPS server to manage the printers and we are facing the issue that PDF is sent to server but there remains stuck and printer output is not sent then to the physical printer. Just to understand if the problem could be in the way CLAW was configured (including the correct version for this feature) or this could be on CUPS server Thanks a lot