<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><br class=""></div><div class="">PDF printing from the frontend/staff webapp is a three step process:</div><div class="">[1] exports the resource to EAD </div><div class="">[2] XSLT processes EAD with stylesheets/as-ead-pdf.xsl to produce a FOP xml file. </div><div class="">[3] Runs that output thru the FOP processor to create final PDF. </div><div class=""><br class=""></div><div class="">So it would be good to find out in which step it is failing. </div><div class="">( In my experience, the most frequent problem has been the initial step exporting invalid EAD. ) </div><div class=""><br class=""></div><div class="">Try checking to see if there is any more specific trace of what is failing in either the application log file </div><div class="">( logs/archivesspace.out ) or in the log files for the batch jobs ( displayed in the batch job console and also in files data/shared/job_files/print_to_pdf_job_*/output.log ). </div><div class=""><br class=""></div><div class="">You can also try each of the steps manually: </div><div class="">[1] export resource to EAD — validate EAD against ead schema with xmllint ( or Oxygen XML Editor or whatever else available. ) </div><div class="">[2] process EAD against stylesheets/as-ead-pdf.xsl with SAXON </div><div class="">[3] process fop xml with fop processor. </div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">I have seen invalid EAD sometimes produced if a mix of published and unpublished components can produce EAD with a missing required element. ( I can’t recall the exact combination at the moment — it was an obvious mistake where a note was supposed to be published. ) I have never tried to export EAD with include unpublished unckecked where the top level resource is unpublished. I don’t know if that is a use case that is tested. </div><div class=""><br class=""></div><div class="">— Steve Majewski</div><div class=""><br class=""></div><br class=""><div><blockquote type="cite" class=""><div class="">On Apr 27, 2018, at 12:45 PM, Daniel Sprouse <<a href="mailto:dsprouse@tsl.texas.gov" class="">dsprouse@tsl.texas.gov</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div id="divtagdefaultwrapper" dir="ltr" style="font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; font-size: 12pt; font-family: Calibri, Helvetica, sans-serif;" class=""><p style="margin-top: 0px; margin-bottom: 0px;" class=""></p><div class="">We have an implementation of AS at Texas State Library and Archives Commission, although I am very new to this application. I have not seen this topic in a search of recent lyralist emails or the user manual, it may be a bug. If it is a feature it isn't a great one. When printing an unpublished resource to pdf AS crashes. If anyone has any insight into this, help would be appreciated.<br class=""><br class="">What follows is from my users and myself, synopsized.<br class=""><br class="">"As my user, I went to Create=〉Background Job=〉Print to PDF. I typed in (a redacted last name,) then selected the (a redacted name) finding aid and chose to print to pdf. The "Resource" is unpublished and I did not click on the "include unpublished". It showed an error message in the generic dialog box which looks that it is an unpublished Resource, took its time and then crashed."<span class="Apple-converted-space"> </span><br class=""> <br class="">"It could be that this error is related to the fact the item is "unpublished" and I didn't check on the "print unpublished". If you reset again I can try to see if checking that box still causes a crash"<br class=""><br class="">additional tests, all of which result in crashing archivesspace app:<br class="">Test 1: Resource has no "published" elements and include unpublished was not checked. Error message stated that this is an unpublished resource.<br class="">Test 2: Resource has no published elements and include unpublished was checked. Error message regarding some of the content and export failed<br class="">Test 3: Published top-most level of the Resource and checked including unpublished. Received a proxy error stating an invalid response from an upstream server and could not handle the GET request (Error reading from remote server). Refreshing the page after allowing time for the process does not help<br class=""><br class="">We are continuing to test ways that this kills AS at this time.<br class=""><br class="">Thanks, Daniel Sprouse,<span class="Apple-converted-space"> </span><a href="mailto:dsprouse@tsl.texas.gov" class="">dsprouse@tsl.texas.gov</a><br class=""><br class=""></div><div id="Signature" class=""><div id="divtagdefaultwrapper" dir="ltr" style="font-size: 12pt; font-family: Calibri, Helvetica, sans-serif, EmojiFont, 'Apple Color Emoji', 'Segoe UI Emoji', NotoColorEmoji, 'Segoe UI Symbol', 'Android Emoji', EmojiSymbols;" class=""><div class=""></div><br class=""><p style="margin-top: 0px; margin-bottom: 0px;" class=""></p></div></div></div><span style="font-family: Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">_______________________________________________</span><br style="font-family: Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">Archivesspace_Users_Group mailing list</span><br style="font-family: Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org" style="font-family: Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br style="font-family: Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" style="font-family: Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a></div></blockquote></div><br class=""></body></html>