macfan55 Posted May 3, 2018 Posted May 3, 2018 I have a problem with composing jobs since yesterday. The problem is that as soon as I compose a job (existing or new) I get an error saying: Graphic file ./correctiesticker maatschoenfolder.pdf missing The result is a pdf without the static background as if FusionPro can't find the very file itself from where I compose the job...??? This happend since yesterday and I can't figure out what has changes since then. In the job itself no graphic file is used; even no rules etc. just a simple job. It does however not happen if I copy the pdf-file to the desktop of my Mac computer and the composing the job instead of opening it from our workflow server... Quote
Dan Korn Posted May 3, 2018 Posted May 3, 2018 This happend since yesterday and I can't figure out what has changes since then. Maybe something was updated? What are your versions of FusionPro, macOS, and Acrobat? It does however not happen if I copy the pdf-file to the desktop of my Mac computer and the composing the job instead of opening it from our workflow server... Can you say more about this "workflow server"? What kind of server is it? How do you connect to it? What is the path to it as shown in the Finder? Quote
macfan55 Posted May 4, 2018 Author Posted May 4, 2018 Hi Dan; Thanks for your reply. I work with OSX 10.12.6 FusionPro VDP Creator 10.0.16 and Acrobat Pro DC 2018.0009.20044 Our workflow server was an xserve (Mac OSX 10.4 Tiger - worked for 9 years without any problem) but has recently changed by IT-guys to another Unix server with Helios software on it. (Don't know which brand etc) I connect with this server through afp://192.168.76.110/Var_Print and in the Finder it states exactly the same info about the volume. Yesterday - I tried to connect to the same server through the smb protocol and then I noticed that my pdf-file was gone... But when I copied the same pdf file from my desktop to that particular folder I got the message that the file could not be copied there because the file was already there as an invisible file??? So I changed the name a bit and copied it again through the smb protocol. Then opened this file from the server again and voila - The composed file was o.k. But as soon as I changed the connection back to afp protocol I got the same error again on composing the job from the server file. So my guess is that FusionPro itself works under the hood with the smb protocol? Or can You figure out what the real problem could be? The guys from IT can't help me with this strange problem. Greetings from the Netherlands Quote
Dan Korn Posted May 7, 2018 Posted May 7, 2018 Hi Dan; Thanks for your reply. I work with OSX 10.12.6 FusionPro VDP Creator 10.0.16 and Acrobat Pro DC 2018.0009.20044 Our workflow server was an xserve (Mac OSX 10.4 Tiger - worked for 9 years without any problem) but has recently changed by IT-guys to another Unix server with Helios software on it. (Don't know which brand etc) Okay, thanks. So something did change. I connect with this server through afp://192.168.76.110/Var_Print and in the Finder it states exactly the same info about the volume. Yesterday - I tried to connect to the same server through the smb protocol and then I noticed that my pdf-file was gone... But when I copied the same pdf file from my desktop to that particular folder I got the message that the file could not be copied there because the file was already there as an invisible file??? So I changed the name a bit and copied it again through the smb protocol. Then opened this file from the server again and voila - The composed file was o.k. But as soon as I changed the connection back to afp protocol I got the same error again on composing the job from the server file. If you have issues with the file in the Finder before you even get to FusionPro, then I'm not sure how it's a FusionPro issue. This all sounds like an issue with your network, or the file server, or the connection to it. It could be a permissions issue, but I have no way to know for sure. So my guess is that FusionPro itself works under the hood with the smb protocol? No, FusionPro just uses POSIX file paths and talks to macOS via system APIs. Unlike Windows, where you have UNC paths, on Mac, you need to first connect to a server in the Finder, then you can access files via POSIX paths. When the Finder is connected to a server via SMB or AFP or some other protocol, it's up to macOS to present a POSIX path for applications to access files and folders there. The path to your file on the server probably starts with "/Volumes/" and a share name. You need to figure out exactly what that path is when you're connected to the server. I would open up a Terminal window (from /Applications/Utilities/Terminal) and drag one of the files from the Finder to the Terminal, and it will show you the full path you need to use. Or can You figure out what the real problem could be? The guys from IT can't help me with this strange problem. Greetings from the Netherlands Groeten! But there's not much I can do to diagnose issues on your network. Quote
ScottHillock Posted May 7, 2018 Posted May 7, 2018 Rename your PDF to all lower case. I haven't tried all possible variables, but I know it happens when you connect to a netatalk or helios afp share, and the remote filesystem is case sensitive. Quote
lance Posted May 8, 2018 Posted May 8, 2018 We had the same issue when using a case-sensitive file system, and changing the template pdf name to all lowercase was the workaround. Quote
macfan55 Posted May 14, 2018 Author Posted May 14, 2018 Thanks; This solution (lower-case filenames, even for FPImposer-files) also works for me as a workaround. I never expected something like this in 2018 software... In the meantime I am connected through the smb-protocol with this Helios-share and that works too for me. Not sure however if I can expect other problems now. Anyone having experience with this protocol on a Mac with FusionPro? Greetings from the Netherlands:) Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.