PDF XChange Forum

I've given the latest version of the Lite driver to one of our customers and he is having issues with the merge/append option. It seems to lock the target file and the merge doesn't happen. I remoted in and saw it happen with printing from Excel and he just reported it doing the same thing with QuickBooks.

I've tried and tried on my end to replicate the freeze but cannot.

Would you like to somehow see this. He seems to be able to consistently reproduce it with Excel.

Let me know how to proceed. I could email you his contact info. He'd be more than open to having you remote in and debug.

--Jeff

Hi Jeff,

Thanks for the post - Can you ask the user to send a screen-shot of the error message (if there is one)?

Also, please have them use Process Explorer to search for the name of the file that they're trying to append to, as the append fails (make sure that they leave the error message open while searching) and send a screen-shot of what's returned:
https://technet.microsoft.com/en-us/sys ... lorer.aspx

They can search in Process Explorer using Ctrl + F, then simply type/copy and paste the filename into the Find bar.

Cheers,

There is no error message. Once you click Save after selecting the Merge/Append option, the dialog just closes and that's it.

You don't know that there is an issue until you try opening the file you are appending to. Once you do this, you get the "can't open/file in use" message.

Then once you kill the Lite driver process from task manager the file opens but nothing got appended. I already checked to see if another process had a hold on the file before appending and nothing does. It's the Lite driver that locks the file. It's as if the Lite driver gets frozen or stuck in a loop or something trying to read the stream of data.

--Jeff

Hi Jeff,

Sorry for not realizing before, but this is actually an error that was caught the other day. Please see here:
https://forum.pdf-xchange.com/ ... 39&t=27966

Thanks,

Ok. Then are you saying it will be fixed in the next build? If so, when is it scheduled to be posted?

--Jeff

Hi Jeff,

I'm not sure when at the moment, as the bug was only recently caught and we're due to release a new build fairly soon, so I'm not sure if it's possible to include in the next release.

Thanks,

Ok. But that bug is a pretty big one.

Understood - I'll try to get this seen to as a priority, but I cannot make any guarantees.

Understood. Thanks.

Will,

Any update on when build .320 will be out?

Hi Jeff,

No word yet. We haven't had a support meeting for a few weeks, due to some absences, so I haven't been able to ask.

Thanks,

Hi Jeff,

grab this exe and replace the installed one:
http://www.docu-track.co.uk/pdfSaver5L_319patch.zip
That should work until the next release.

Let me know how it goes?

regards

Are you sure that is the right Lite Driver exe?

The last one I had was named

PDFXLite6.exe

Also, am I to use PNAME or PNAMELITE to rename to print driver to my choosing?

--Jeff

Thanks for that Jeff,

can you check the file properties of the exe? It should show 6.0.319.0 like this:


PDFXLite6.exe is an installer, this is just the exe from the already installed Lite driver. A fresh install of V6 Lite will in fact install the executable named pdfSaver5L.exe



I do believe this is the right file.

Regards PNAME or PNAMELITE - I need to consult Ivan - he's away today. Sorry. I'll post as soon as I hear from him regards that.

That's just it. I need the installer to make the PNAME thing work. That was one of the issues.

Maybe you are saying the exe you sent me fixes the merge/append issue?

Either way, I'd prefer just to drop in a new install file that handles both.

--Jeff

oooh - sorry Jeff,- I missed the point of the PNAME thing. I was thinking specifically for the append issue.

I am trying to get a hold of Ivan now but it may not be possible until tomorrow. Can you wait or should I see if I can track that answer down through someone else?

No rush. I can wait.

Thanks for looking into this.

Also, if .320 is just a week or so out, I can wait for the official build.

--Jeff

Thanks Jeff,

.320 is looks like being ready for the end of the month, closer to two weeks than one.

I got a hold of Ivan. In .320 PNAME when used with the Lite installer will set a default Printer name that you specify.

Looks like .320 is out.

Can you confirm if PNAME or PNAMELITE is the param to use to rename the driver when I install it.

I just tried both

/quiet /norestart /log "C:\ProgramData\FileCenter\PDFPrinterLog6.txt" ORGANIZATION="FileCenter" PNAME="FileCenter PDF Printer 6" KEYDATA="..."

and

/quiet /norestart /log "C:\ProgramData\FileCenter\PDFPrinterLog6.txt" ORGANIZATION="FileCenter" PNAMELITE="FileCenter PDF Printer 6" KEYDATA="..."

and neither renamed the driver.

Am I doing something wrong with the params above?

Again, I'm using the PDFXLite6.exe installer from your download page, not the .msi. Do I need a special exe installer for the params work?

--Jeff

Hi Jeff,

Thanks for the post - Can you email the log to support@pdf-xchange.com? Please don't post here as it may contain your license key.

Thanks,

Just emailed it to you.

Thanks Jeff - I've passed that along and asked for confirmation on whether or not this was implemented. I'll let you know when I hear back.

Cheers,

Hi Jeff,

Thanks for waiting - Ivan has mentioned that a second log, from the MSI's inside the EXE, should be present. Can you please send that too?

Also, from what we can see, in the log file it lists the command as "PNAME=FileCenter PDF Printer 6" instead of PNAME="FileCenter PDF Printer 6" - can you confirm which was actually used?

Thanks,

I'm most definitely using

PNAME="FileCenter PDF Printer 6"

I just emailed the other log to support@pdf-xchange.com.

Are you able to make this work on a test machine on your end?

--Jeff

I think something may be wrong with how you parse the commandline or how I'm entering it again.

I just did another attempt where I rearragned the parameters. Here's what I passed.

/quiet /norestart PNAME="FileCenter PDF Printer 6" ORGANIZATION="FileCenter" /log "C:\ProgramData\FileCenter\PDFPrinterLog6.txt" KEYDATA="..."

But here's what the log said.

Command Line: '"-burn.clean.room=C:\Program Files (x86)\FileCenter\Drivers\PDFXLite6.exe" -burn.filehandle.attached=508 -burn.filehandle.self=520 /quiet /norestart "PNAME=FileCenter PDF Printer 6" ORGANIZATION=FileCenter /log C:\ProgramData\FileCenter\PDFPrinterLog6.txt KEYDATA=...

I'll keep trying a few more things.

Go figure. The following commandline works now.

/quiet /norestart /log "C:\ProgramData\FileCenter\PDFPrinterLog6.txt" PNAME="FileCenter PDF Printer 6" ORGANIZATION="FileCenter" KEYDATA="..."

Hi Jeff,

So everything's working correctly now? If so, then we'll see if we can reproduce the issue. But if not, we'll have to wait and see if you're able to reproduce it again.

Thanks,

Yes. It is working for me now.

Perfect