Terminal Server 2012

kirk329 · June 27, 2017, 6:37pm

Have a Server 2012 R2 Running TS. Have a POS application built in Access.
I was able to run save to file, and email before using the microsoft to pdf function with 2008.

Since that feature wasnt in 2012, i had to purchase this program. But now when using the POS 1/10 it locks up the POS system when using either save to or email function. 9/10 it does work. Is there a specific call of code that needs to be put in the Access program to reflect the difference between the two? For example, if the code is PDF in access does it need to have PDFCreator or its all the same. I hope this makes sense. Please help

Robin.W · June 28, 2017, 2:50pm

Hi,

I am not sure if I understand the problem completely.
Are you using VBA to interact with the PDFCreator, or are you directly printing from the POS application to the PDFCreator printer?
You can enable advanced logging by setting the logging level to “trace” in the debug section of the PDFCreator application settings, which might help to track down the problem (you can send it to support(at)pdfforge.org and we will have a look at it, if you like).

Best regards,

Robin

kirk329 · June 29, 2017, 1:11am

I appreciate your response. It is directly printing from the POS system to the PDFCreator printer.

I enabled debug and after 5 tries it did fail. Below is the log file:

2017-06-28 18:00:43.6277 [Debug] pdfforge.PDFCreator.UI.ViewModels.SettingsLoader.SaveSettingsInRegistry: Saving settings
2017-06-28 18:00:48.1747 [Debug] pdfforge.PDFCreator.Core.Startup.AppStarts.MaybePipedApplicationStarter.Shutdown: All synchronized threads have ended
2017-06-28 18:00:48.1747 [Debug] pdfforge.PDFCreator.Core.Communication.PipeServerManager.PrepareShutdown: Preparing PipeServer for ShutDown
2017-06-28 18:00:48.1903 [Debug] pdfforge.PDFCreator.Utilities.Threading.ThreadManager.Shutdown: Shutting down the application
2017-06-28 18:00:48.1903 [Debug] pdfforge.PDFCreator.Utilities.Threading.ThreadManager.Shutdown: Exiting…
2017-06-28 18:00:48.1903 [Debug] pdfforge.PDFCreator.UI.ViewModels.SettingsLoader.SaveSettingsInRegistry: Saving settings
2017-06-28 18:00:48.2528 [Debug] pdfforge.PDFCreator.Core.Communication.PipeServerManager.Shutdown: Stopping pipe server
2017-06-28 18:00:48.2685 [Debug] pdfforge.PDFCreator.Editions.EditionBase.ProgramBase.Main: Ending PDFCreator
2017-06-28 18:09:27.8620 [Debug] pdfforge.PDFCreator.Core.Startup.AppStarts.MaybePipedApplicationStarter.SendMessageOrStartApplication: Starting attempt 1:
2017-06-28 18:09:27.8933 [Debug] pdfforge.PDFCreator.Core.Startup.AppStarts.MaybePipedApplicationStarter.TryStartApplication: Starting pipe server
2017-06-28 18:09:27.8933 [Debug] pdfforge.PDFCreator.Core.Communication.PipeServerManager.StartServer: Starting pipe server thread
2017-06-28 18:09:27.9089 [Debug] pdfforge.PDFCreator.Core.Startup.AppStarts.MaybePipedApplicationStarter.TryStartApplication: Reloading settings
2017-06-28 18:09:28.1433 [Debug] pdfforge.PDFCreator.Core.Startup.AppStarts.MaybePipedApplicationStarter.TryStartApplication: Finding spooled jobs
2017-06-28 18:09:28.1433 [Debug] pdfforge.PDFCreator.Conversion.Jobs.SpooledJobFinder.GetJobs: Looking for spooled jobs in ‘C:\Users\SalesAQ\AppData\Local\Temp\2\PDFCreator\Spool’
2017-06-28 18:09:28.1433 [Debug] pdfforge.PDFCreator.Core.Startup.AppStarts.MainWindowStart.StartApplication: Starting main window
2017-06-28 18:09:28.1433 [Debug] pdfforge.PDFCreator.Utilities.Threading.ThreadManager.StartSynchronizedThread: Starting MainWindowThread thread
2017-06-28 18:09:28.1433 [Debug] pdfforge.PDFCreator.Utilities.Threading.ThreadManager.StartSynchronizedThread: Adding thread MainWindowThread
2017-06-28 18:09:28.1589 [Debug] pdfforge.PDFCreator.Utilities.Threading.ThreadManager.StartSynchronizedThread: Adding thread
2017-06-28 18:09:28.1589 [Debug] pdfforge.PDFCreator.Core.Startup.AppStarts.MaybePipedApplicationStarter.SendMessageOrStartApplication: TryStartApplication: True
2017-06-28 18:09:28.1589 [Debug] pdfforge.PDFCreator.Core.Startup.AppStarts.MaybePipedApplicationStarter.SendMessageOrStartApplication: Starting update check thread
2017-06-28 18:09:28.1589 [Debug] pdfforge.PDFCreator.Utilities.Threading.ThreadManager.StartSynchronizedThread: Adding thread UpdateThread
2017-06-28 18:09:28.1589 [Debug] pdfforge.PDFCreator.Core.Startup.AppStarts.MaybePipedApplicationStarter.SendMessageOrStartApplication: Starting Cleanup thread
2017-06-28 18:09:28.1589 [Debug] pdfforge.PDFCreator.Utilities.Threading.ThreadManager.StartSynchronizedThread: Starting CleanUpThread thread
2017-06-28 18:09:28.1589 [Debug] pdfforge.PDFCreator.Utilities.Threading.ThreadManager.StartSynchronizedThread: Adding thread CleanUpThread
2017-06-28 18:09:28.1589 [Debug] pdfforge.PDFCreator.UI.ViewModels.Assistants.Update.UpdateAssistant.UpdateThread: Launched UpdateThread
2017-06-28 18:09:28.1589 [Debug] pdfforge.PDFCreator.UI.ViewModels.Assistants.Update.UpdateAssistant.Update: Automatic UpdateCheck is disabled
2017-06-28 18:09:28.1745 [Debug] pdfforge.PDFCreator.Core.Startup.AppStarts.MaybePipedApplicationStarter.Shutdown: Waiting for all threads to finish
2017-06-28 18:09:28.1745 [Debug] pdfforge.PDFCreator.Utilities.Threading.ThreadManager.WaitForThreads: Waiting for all synchronized threads to end
2017-06-28 18:09:28.1745 [Debug] pdfforge.PDFCreator.Utilities.Threading.ThreadManager.WaitForThreads: 1 Threads remaining
2017-06-28 18:09:30.1433 [Info] pdfforge.LicenseValidator.Core.ActivationParser.DoParse: Parsing response string: [License]
ACTIVATED_TILL=1499266017
ACTIVATION_COUNT=1
ACTIVATION_MAX_COUNT=1
DATE=1498661217
EXPIRES=1528594715
ID=e4e609cd1b03e76284abceb68dbe60c60c18472a
LATEST_VERSION=2.5.3
LICENSE=K6L8W5V2QBC2VI1QHAZ5VOS13ON0UC
LICENSING=non_perpetual
METHOD=online_v2
PRODUCT_NAME=pdfcreator_terminal_server
RESULT=OK
VERSION=2.5.3
MESSAGE=OK
LICENSEE=KDL Consulting
HASH=597e3abb038d34ec3a77aa3ab6aa9b84e941d5d0

Robin.W · July 3, 2017, 1:27pm

Hi,

unfortunately the log doesn’t contain any errors and doesn’t really show what is going on, please set the logging level to “trace” instead of debug, which will record almost every step and might indicate the problem even if there is no actual error in the log.

Best regards,

Robin