New problem/bug printing to UNC path

General usage of the PDF Printer.

Moderator: jr

Post Reply
Dannysh
Posts: 1
Joined: Thu Jan 08, 2009 6:28 pm

New problem/bug printing to UNC path

Post by Dannysh »

I just upgraded from build 690 to build 728 and can no longer print to UNC paths as I used to do regularly. The save operation is interrupted with the following error:
An error occured.
Error 76: Error creating folder in function MkDirRecurse. Target=\\server\sharename\path\, Current=server\sharename\path\. Path not found

Copy output to destination.

I am kind of stuck now because I cannot find the setup package for any older builds. For now I have to print to local paths or map drives manually. Any information on this, or where I can find older builds?

Thanks!
doublee
Posts: 1
Joined: Fri Jan 09, 2009 11:00 am

Re: New problem/bug printing to UNC path

Post by doublee »

I have the same problem with build 728. On the other hand if I try to use the share's root it works fine (\\server\sharename\).
tugo0ew02
Posts: 15
Joined: Sat Jan 26, 2008 12:39 pm

Re: New problem/bug printing to UNC path

Post by tugo0ew02 »

[quote="Dannysh"]
Error 76: Error creating folder in function MkDirRecurse.

I am kind of stuck now because I cannot find the setup package for any older builds. For now I have to print to local paths or map drives manually. Any information on this, or where I can find older builds?
[/quote]

This condition will probably be corrected quickly.
I had similar with local files.
(See: http://www.bullzip.com/phpBB/viewtopic.php?f=6&t=6349 )

In the mean time, if you desire, I have these original setup versions archived:
BullzipPDFPrinter_6_0_0_695.zip
BullzipPDFPrinter_6_0_0_702.zip
jr
Site Admin
Posts: 500
Joined: Sun Mar 26, 2006 12:28 pm

Re: New problem/bug printing to UNC path

Post by jr »

Hi

A new version has just been released 6.0.0.741. This version should fix the problem.

Regards,
Jacob
notacc
Posts: 1
Joined: Tue Jan 13, 2009 10:18 pm

Re: New problem/bug printing to UNC path

Post by notacc »

The new version fixed this issue for me. Thanks.
Post Reply