Troubleshooting and tips
Click an issue below to see the solution or workaround.
By default, ASP.NET grants 110 seconds to convert a document. However, in some cases, this time may not be sufficient. If this is the case, you can extend the timeout to any number you want. In this example, we'll show how to extend timeout to 600 seconds (10 minutes).
- Open Web.config file in the WorkZone PDF Engine directory. Its default location is the following:
C:\Program Files (x86)\KMD\WorkZone\IIS\WorkZone\Render\Web.config
. - Add the following parameter
executionTimeout="600"
to <httpRuntime>, for example: - Save the changes.
<configuration>
<system.web>
<httpRuntime maxRequestLength="2097152" executionTimeout="600" />
If the installation fails with the message “DSN is invalid. Installation cannot be performed”, you must ensure that the ODBC Data Source Name has the same name as the Transparent Network Substrate (TNS) Service name of the WorkZone Content Server Oracle database. For a solution to this problem, see The installation uses different names for DSN and TNS.
All ODBC DSN names are listed in the registry under:
HKLM\SOFTWARE\(Wow3264Node\)ODBC\ODBC.INI
.
If your installation does not use the same name for ODBC (DSN name) and Oracle (TNS name) access to your database, you need to create a duplicate TNS name which is identical to the DNS name before running the WorkZone PDF Crawler installation. This extra TNS name is required only during installation, and can be removed after installation.
If your database uses the TNS name <TNS>
, you can expose it as <DSN>
from the database server by following the steps below:
- On the WorkZone Content Server Agent Server, open the file
<OracleHome>\Network\Admin\tnsnames.ora
where<OracleHome>
is the location where you have installed Oracle. You can use, for example, Notepad for editing this file. - Find the definition of the TNS name of your database:
<TNS> = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = scjora04.scanjour.dk)(PORT = 1521))
(CONNECT_DATA = (SERVER = DEDICATED)
(SERVICE_NAME = UV006.scanjour.dk)))
Where <TNS>
is the Oracle TNS name of your database.
- Copy the lines above.
- In the copy, change the Oracle TNS name to be the same as the DSN name you use with ODBC. The new entry will look like this:
<DSN> = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = scjora04.scanjour.dk)(PORT = 1521))
(CONNECT_DATA = (SERVER = DEDICATED)
(SERVICE_NAME = UV006.scanjour.dk))
Where <DSN>
is the new name.
Do not change the old entry.
- Save and exit
tnsnames.ora
. - Verify that both TNS names work. Open a command prompt on the agent server and enter:
tnsping <TSN>
tnsping <DSN>
In both cases, the command should reply with a copy of the entry in tnsnames.ora
followed by OK (20 msec) or similar.
This is due to the fact that the sent date and time of an email is the date and time of the Exchange Server time zone. So, if the sender of the email is in a different time zone than that of the Exchange Server, the sent date and time of the email is not the date and time where the sender sent the email. This is Outlook default behavior. The conversion of an email to a PDF document does not affect the date and time.
The format of the sent date in the PDF document is the default format, which is the format defined on the server. The timestamp format is UTC with time zone offset.
Note that UTC does not observe daylight saving time.
When converting documents with custom fonts to PDF, the documents will be converted but they may not use the custom font and therefore not display correctly.
To make the documents convert correctly, install the custom font on the server where WorkZone PDF Engine is running.
After installing custom fonts on the server, recycle the PDF Engine App Pool.
Alternatively, set up the fallback font, which will be used instead of missing custom font.
Dates are displayed in the format that is defined in WorkZone Configurator by default, unless you have defined another date format in the document. If the document does not display the expected date format, you can manually define the desired date format in the document, which will then be used instead of the standard date format from WorkZone Configurator.
See also
Troubleshooting in the Installation Guide.