Data Techniques Forums

faxman 4.4.40, vista business, domainuser logged in

any printjob to faxman4 (e.g. via faxdlg) is silently ignored, but the eventlog contains one entry per printjob:

protocol: system
Source: print
EventID: 6161
level: error
The document <document> owned by <username> failed to print on printer faxdlg. Data type: NT EMF 1.008. Size of the spool file in bytes: 964. Number of bytes printed: 0. Total number of pages in the document: 1. Number of pages printed: 0. Client machine: <computername>. Win32 error code returned by the print processor: 123. The filename, directory name, or volume label syntax is incorrect.

The problem apears only with users; when logged in as administrator the fax is handled correctly. Even if the user has (local) admin rights the error happens.

Martin

 Hi,

Make sure  when running under the limited user accounts that they have read/write/modify permissions to the directory where you are specifying the fax files should be created.

That was my first idea. I have checked this. Even with local admin rights the error apears.

Martin

 Hi,

Where are the fax files supposed to be created ? 

Hi,

support:

Where are the fax files supposed to be created ? 

that doesn't matter: Normaly a pathname (C:\fax\SomeDir) is set, but it makes no difference to an empty pathname.

Martin

Hi,

Actually where the files are supposed to be created is important as the user must have read/write/modify priviliges to that directory. And as the error message indicates a problem with the file path I would suggest setting the print files path to a simple dir which all users have permissions to and see if that helps.

hi,

as I said, the print path is set to a simple dir that exists. The user has full permissions to that path. Also the user hat local admin rights. I have verified that the user can create files in that directory.

Martin

I have had the exact same problem with Faxman JR 2.03. I have tried several different location of files settings to no avail. I might be mistaken, but I thought it worked with version 2.00 of FaxMan Jr. Any ideas are appreciated.

 Hi Ray,

What version of Vista are they running and is it a standalone PC or part of a domain ? 

with the help of a tools that traces all file- and registry-related systemcalls (sysinternals procmon) and hours of comparing positive and negative traces (why doesn't data technique provide a version that does some logging?) I finally found the circumstance and the condition that leads to the error:
The "documents" folder (normally set to c:\users\%username%\documents) is redirected by GPO to \\<Servername>\redirected$\%username%\Dokumente>. The traces show that the driver tries to access a path "c:\windows\CSC\v2.0.6\namespace\<servername>\redirected$\<username>\dokumente". When the folder redirection is not in place the paths c:\users\<username>\documents and c:\users\<username>\documents\faxman is opened instead.
I don't know what the printerdriver is looking for in that directory and how the path to the documents-folder gets messed up, but it seems to be reproducible. Activate the folder-redirection: Error in systemlog, printjob is lost. Deactivate the folder redirection: No error, fax is delivered as expected.

Martin

 Hi Martin,

Thanks for the info on whats happening. What exactly are you setting the  fax files path to then ?

Hi Sean,

as I said, it doesn't matter. I've tried "C:\FAX\Temp" and an empty path. Both possibilities will not work when the redirection is in place and will work when the redirection is disabled.

Martin

We are running Vista Business, and are part of a domain. I have tried the fax path on both a network share and on the local machine. Both as a standard user and adding the user to the administrators group.

Ray

 Hello Ray,

Do you have Folder Redirection enabled ? Earlier in this thread Martin has determined that its the cause of this error. We're setting up a test scenario so we can duplicate this but in the meantime it appears that resolves the issue. Can you pls confirm that it works for you too ? 

Hi Ray,

you may find it helpful to verify the staus of folder redirection. Go to the documents folder (C:\users\yourName\documents), right click on "documents", and activate the page labeled something like "Path". There you can verify and reset the folder redirection.

Martin