Revit asks to Update Keynote file when printing

[hubbardFJXGT]

Why does Revit ask to update the keynote file when printing even though it was recently updated> This is causing issues with our batch printing to PDF, as it stops every sheet. 
Just prior to starting the batch or print function I reload the file using the Manage Keynotes. No one else is in the file currently and the Modified date is current. How do we get Revit to stop displaying this dialog when the file is up to date?

[barthbradley]

https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/The-following-reso...

[hubbardFJXGT]

DC is up to date, I have reloaded the Keynote file before sending the PDF. Still getting the dialog

I even copied the file to Desktop, reloaded saved and still get the dialog. 

[EBlackburnDMS7X]

Same issue

[EBlackburnDMS7X]

More info: Seems to be related to file path names being too long, especially when hosted in ACC. If I move the keynote file into the root project folder in Docs, it works. If it's buried in subfolders, it doesn't. Users with longer names cause it to not work, even in the root folder. Users with short names, it works. Desktop Connector and Revit are updated to latest versions. Happens using any print driver/method. The way that Revit is pairing the keynote file path with the Revit file path is creating a combined file name that is too long.

Hope this helps and is seen by the right people to fix it!

[hubbardFJXGT]

Strange, our keynote file is 1 folder deep in Docs. So overall only 94 characters. Moving it to the root will only remove 9 characters so not sure if that will help. 

[EBlackburnDMS7X]

I think it's a cumulative revit filename + keynote filename somehow. I don't know of any way to verify this - perhaps looking at the journal file immediately after the warning message would reveal another clue. I just have anecdotal evidence that changing the file location so the path wasn't as long fixed it for me, but not for another user with a longer user name.

[EBlackburnDMS7X]

Have heard from other users that it is NOT recommended to host keynote text files in ACC. Something about the way that it is processed or pathed causes issues that are not consistent. It does not happen if the keynote file is referenced from a local/shared server instead of through ACC.