To add to the details, here is the call stack that is captured when it fails:
System.Web.HttpUnhandledException: Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> ceTe.DynamicPDF.ReportWriter.DplxParseException: Invalid variable in a connection string.
at zz93.av.a(StringBuilder A_0)
at zz93.av.b()
at zz93.et.u()
at zz93.j.a(et A_0)
at zz93.fb.a(et A_0)
at ceTe.DynamicPDF.ReportWriter.DplxFile.a(et A_0)
at ceTe.DynamicPDF.ReportWriter.DplxFile..ctor(String filePath)
at ceTe.DynamicPDF.ReportWriter.DocumentLayout..ctor(String filePath)
at Print1234.Page_Load(Object sender, EventArgs e) in C:\websites\www_1234_com\Leave\Print1234.aspx.vb:line 22
at System.Web.UI.Control.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
--- End of inner exception stack trace ---
at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context)
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at ASP.leave_print3065_aspx.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)