CreativePro Forum

Return to Member Forum

• Author
  Posts
• • October 24, 2018 at 8:38 am #111118
    Thiago Ribeiro Nogueira

    Member

    I get a error message when I try to export a PDF or make other package from a file that I packaged from company network server. Is like I can’t access the links files anymore.

    https://www.dropbox.com/s/zoo0ifm2skhfow8/tentando-fazer-pacote-ou-pdf.jpg?dl=0

    And I even can’t delete them!

    https://www.dropbox.com/s/indyt0vegv6qoeu/tentando-excluir-arquivos.jpg?dl=0

    I used the Indesign 13.1 and macOS High Sierra 10.13.6 and happens with macOS Mojave and Indesign 2019 too

  • October 24, 2018 at 8:42 am #111120
    David Blatner

    Keymaster

    Are the images showing up as OK in the Links panel? If you right-click on one of the images in the Links panel, can you choose “Reveal in Finder” or “Reveal in Explorer” from the menu?

  • October 24, 2018 at 8:53 am #111121
    Thiago Ribeiro Nogueira

    Member

    Yes David. All OK. The indesign file opens normally, the links are there, but I can’t export PDF or a new package, shows the error… and I can’t copy, delete and do nothing with the files in the folder “Links” and “Document Fonts”.

    This happening only in macOS. The same indesign file, packaging from the same network in Windows PC is normal. :(

  • October 24, 2018 at 9:15 am #111122
    David Blatner

    Keymaster

    I wonder if it is a “permissions” problem.
    Have you tried: Rebuilding InDesign’s Preferences? Restarting the computer? Launching the computer into a different user account (such as a Guest account) and trying from there?

  • October 24, 2018 at 9:53 am #111123
    Tim Murray

    Member

    Could you please list the steps? For example (and these are completely made up):
    1. Worked on InDesign file on server A. Links okay. Made PDF okay. Made a package there.
    2. Move package from server A to server B. Unpackage, no error.
    3. Work on file on server B. Can open but can’t make PDF, can’t delete content.
    . . . that kind of thing.

    And of course, there is the question of what happens if you do everything on your local disk.

  • October 24, 2018 at 11:04 am #111129
    Thiago Ribeiro Nogueira

    Member

    I went to try to do the steps to make a list and now the package don’t works by no means… shows only the message to wait the links packing but Indesign freezes… Oh my god..

  • October 24, 2018 at 11:09 am #111130
    Thiago Ribeiro Nogueira

    Member

    I need to force quit Indesign everytime and even restart the computer to open the program again.. I don’t know what do do anymore

  • October 24, 2018 at 11:21 am #111131
    David Blatner

    Keymaster

    Have you tried: Rebuilding InDesign’s Preferences?
    https://creativepro.com/rebuilding-indesign-preferences.php

    Launching the computer into a different user account (such as a Guest account) and trying from there?
    https://creativepro.com/lynda-10-tips-troubleshoot-indesign-files.php

  • October 24, 2018 at 11:29 am #111132
    Thiago Ribeiro Nogueira

    Member

    Yes, David. I even reinstalled Indesign.. the problem get worse with Mojave

  • October 25, 2018 at 12:43 pm #111168
    Thiago Ribeiro Nogueira

    Member

    David, with the same user and same access all works fine in a Windows computer.

  • January 31, 2019 at 4:13 am #114040
    Thiago Ribeiro Nogueira

    Member

    Hi!

    I’ve updated to Indesign 2019 and Mojave but continued with same problem, can’t package or open a file in my network server.

    But with so many tries, I found that I can’t package from server with Indesign 2019 and Mojave because the “Documents fonts” folder is in there! When you uncheck this in the package option works! I even can open files normally when there is not that folder in my Indesign file root folder. It’s a font problem! What can I do now? Theres a way to send this information direct to Adobe?

    Thank you.

  • January 31, 2019 at 4:49 am #114044
    Masood Ahmad

    Participant

    I would suggest, try creating a package on your Desktop. If you got success, then it’s a Domain User Access issue as David said, Permission issue. In that case you have to contact your IT team.

    I also don’t see any issues with the Document Fonts folder.

  • January 31, 2019 at 6:12 am #114048
    Thiago Ribeiro Nogueira

    Member

    My main problem is that I can not open some files on our server with Indesign. When we make the package, one of these steps is “Open document”, and that’s where Indesign stops working. On the desktop I can open any file so it will work.

    Now, I’m using a script that renames the Documents fonts folder to xDocuments fonts, overriding it when I open a file, because that’s the only way I can open it on our server and when I make a package I disable the “Copy fonts” option. Because of this I know the problem is when the program will read this folder for some reason.

    I already talked to my IT team and everything is set up right and I am the administrator of the machine.

  • January 31, 2019 at 6:52 am #114049
    Masood Ahmad

    Participant

    Can’t say what exactly is causing this. To my experience, there can’t be any problem with the Document Fonts folder. Being an IT person in the past, I can say there might be some policies in place or even a back-end script that is not allowing a person to open the file from the server. There’s something that is creating this behaviour.

    Being an Administrator of the machine doesn’t mean that you can override the Server policies and permissions. Please check it thoroughly.

    PS: try accessing a file from different server or locations.

  • January 31, 2019 at 8:52 am #114054
    Thiago Ribeiro Nogueira

    Member

    Like you said, I tried to open from a different server and got the same error. The spinning ball last forever, I need to Force Quit Indesign and open it again, and the file open.

    That issue is not only for me, that’s a lot of people complaining about the same bug:

    https://indesign.uservoice.com/forums/601180-adobe-indesign-bugs/suggestions/35527912-unable-to-package-a-file-to-a-server-after-upgradi

    This is weird.

  • January 31, 2019 at 9:08 am #114055
    Masood Ahmad

    Participant

    That’s very strange. We too work on servers and we have all versions of Mac OS and InDesign (CS5 to CC 2019) but didn’t found anyone complaining such thing. I’ll also alert my IT team regarding this issue, just in case.

  • January 31, 2019 at 10:22 am #114063
    Thiago Ribeiro Nogueira

    Member

    Thank you for your attention Masood.

    One more thing. Servers polices and permissions in a Windows server can be applied only for a Mac computer? Because I use a virtual machine with Windows using the same network server and everything works fine with Indesign. The issue is really only on my Mac OS.

  • January 31, 2019 at 11:05 am #114065
    Tim Murray

    Member

    You mentioned “renames the Documents fonts folder to xDocuments fonts”. Do you mean it is “xDocuments – space – fonts”? I have a friend who, in his server environment, finds that if his FrameMaker acts up, as soon as any space is removed from the path, it works. Not the same, but this brings it to mind. If it were a policy at the folder level, I’d be surprised the server let you rename the folder at all.

• Author
  Posts