@DougHiggs - I had just come to the conclusion that this is a bug because I have it happening to 2 people on 2013 but one in AR and one in AP but the error is the EXACT same error. Hadn't called Sage yet, but I'm guessing there might not be a way out of this until they fix it. Appears to be the PDF files, but that could be one of those misleading things, too.