This section provides troubleshooting information for common DocumentBursterâ„¢ difficulties.
If you are experiencing problems using DocumentBursterâ„¢ make sure that you have read and properly installed the software prerequisites, as described in DocumentBursterâ„¢ in 5 Minutes tutorial guide.
If you need to contact
DocumentBursterâ„¢
support, you can get help by sending an email to
<support@pdfburst.com>
The free version of DocumentBursterâ„¢ has a restriction of maximum 25 burst output reports being generated and/or being distributed.
For bursting and generating an unlimited number of reports please purchase DocumentBursterâ„¢
If you don’t know from where to start or you have problems running the basic features of the program, read DocumentBurster™ in 5 Minutes tutorial guide.
If on the console or log file there is an exception similar with
"java.lang.UnsupportedClassVersionError:test (unsupported major.minor version 49.0)
This is happening when the program runs with an ancient java
version
(<Java v1.8).
Read
DocumentBursterâ„¢
in 5 Minutes
document and double
check the version of
java
which
is installed on your computer.
DocumentBursterâ„¢ requires Java v1.8 (or greater) version in order to run.
Sometimes the exception is still coming even after the latest Java is installed. This is happening because the old java is still installed and active on your computer.
The solution is to edit
documentburster.bat
and do the following
change
java -Djava.endorsed.dirs=./lib/endorsed -cp ./lib/burst/ant-launcher.jar org.apache.tools.ant.launch.Launcher -buildfile ./config/burst/documentburster.xml -Darg1=%1 -Darg2=%2 -Darg3=%3 -Darg4=%4 -Darg5=%5 -Darg6=%6
Do the bold change
"C:/Program Files/Java/jre8/bin/java.exe" -Djava.endorsed.dirs=./lib/endorsed -cp ./lib/burst/ant-launcher.jar org.apache.tools.ant.launch.Launcher -buildfile ./config/burst/documentburster.xml -Darg1=%1 -Darg2=%2 -Darg3=%3 -Darg4=%4 -Darg5=%5 -Darg6=%6
The proper path to the location where the latest java is installed should be provided. This change will force DocumentBursterâ„¢ to run with the latest java.
As a general rule, it is advisable to have a single Java installation on the machine where DocumentBursterâ„¢ is executed. Even if (theoretically) it is possible to have multiple java versions installed on the same computer, in practice this will only leave room for strange issues and will complicate the installation.
If you have bursting problems, check that you have configured the burst tokens in-between brackets. For example {alfreda.waldback@northridgehealth.org} is a valid token.
If you configured all the tokens properly and still the program is not working as expected, you can enable detailed logging. By checking the detailed log file you can understand what is going wrong.
In order to enable detailed logging, read Chapter 7, Quality Assurance .
Sometimes variables defined like <0>some value</0> and up to <9>some other value</9> might fail in getting parsed the proper values. Following is an example of the issue coming with Microsoft Access, while similar behavior might be observed with other report writers too.
The Problem - Example of the problem coming with Microsoft Access
I am using various MS Access reports to grab variable data using <0> text </0> . If I use a label for the text and key it into the text box as <0> report id 100 </0> it works fine but if I drop a field onto the report and then put the <0> and </0> in front and back of the field, it does not work.
The Solution - And here is the solution for the previous MS Access behavior
When you drop the fields into an MS Access report you need to define any field you use as a variable as a single field by concatenation. For example, let's say I have a field named "date" and place it on the report with a text box of <0> in front and then place a text box of </0> at the end. This will not work. You need to create one field (object) as follows: =" <0> "text" </0> ". Now it will work.
More Details
If the start and end tags (e.g. <0> and </0> ) are statically defined, while the content inside is a dynamic field /report formula (string value which can grow in length), the dynamic content will grow and will start to overlap with the static tags (e.g. <0> and </0>). This might cause problems when DocumentBursterâ„¢ is parsing the variable values. See the following screenshot in which "Tuesday" hidden text was generated by a date field/formula which expanded its length and started to overlap the start <1> tag. In this case the text which is extracted by DocumentBursterâ„¢ is a messy Tues<da1>y and as a result the variable value is not properly parsed. The solution to this problem was described in the previous paragraph.
When
server/startServer.bat
script is executed
it is flashing up the cmd box and then it
disappears.
Solution
Are all the prerequisites in place? Read DocumentBursterâ„¢ in 5 Minutes tutorial guide and check all the prerequisites required for running DocumentBursterâ„¢ .
java -version
MS-DOS
command should return v1.8 or greater)
server/shutServer.bat
script?
Solution
Are all the prerequisites in place? Read the DocumentBursterâ„¢ in 5 Minutes tutorial guide and check all the required prerequisites.
java -version
MS-DOS
command should return v1.8 or greater)
The link
http://localhost:8080/burst
is not working on the local machine.
When
web-console/startConsole.bat
script is executed
it is flashing up the cmd box then it disappears.
Solution
Are all the prerequisites in place? Read DocumentBursterâ„¢ in 5 Minutes tutorial guide and check all the required prerequisites.
java -version
MS-DOS
command should return v1.8 or greater)
server/startServer.bat
script?
DocumentBursterâ„¢
Server
console
should be started before the web console is started.
Before starting the web console JRE_HOME environment variable should be properly defined on your system. The echo %JRE_HOME% command executed in the DOS command prompt should return an existing JRE 1.8 (or greater) installation path.
If
required, on Windows,
JRE_HOME
environment variable can be manually defined in
→ → →
i.e.
C:/Program Files/Java/jre8
The following problem is happening only on Windows Server 2003.
The system was tested and everything works fine on Windows Server 2008 or Windows 7.
The Problem - DocumentBursterâ„¢ Server service always stops when the system is logged off.
Solution
This is required only for Windows Server 2003.
Before doing any change make sure that
shutConsole.bat
and
shutServer.bat
scripts
-Xrs
switch should be added in two (2) places
server/startServer.bat
server/config/burst/internal/documentburster.properties
Change 1
server/startServer.bat
java -DDOCUMENTBURSTER_HOME=%CD% -Djava.endorsed.dirs=lib/endorsed -cp lib/batch/ant-launcher.jar org.apache.tools.ant.launch.Launcher -buildfile config/burst/internal/startServer.xml –emacs
Do the bold change
java -Xrs -DDOCUMENTBURSTER_HOME=%CD% -Djava.endorsed.dirs=lib/endorsed -cp lib/batch/ant-launcher.jar org.apache.tools.ant.launch.Launcher -buildfile config/burst/internal/startServer.xml –emacs
Save the file.
Change 2
server/config/burst/internal/documentburster.properties
SERVER_JVM_OPTS=-XX:MaxPermSize=256m -Xms512m -Xmx512m
Do the bold change
SERVER_JVM_OPTS= -Xrs -XX:MaxPermSize=256m -Xms512m -Xmx512m
Save the file.
Restart both DocumentBursterâ„¢ Windows services and check that DocumentBursterâ„¢ works properly when the machine is logged off.
If you have problems in getting the email working
Are you running Anti-Virus software?
If your organization has any firewall and/or antivirus software (e.g. Symantec, McAfee, etc.) which is configured in between DocumentBursterâ„¢ software and the email server software (e.g. Microsoft Exchange), in this case, the antivirus and/or firewall might need to be properly configured to allow DocumentBursterâ„¢ sending emails as a good and trustable citizen.
Ask for Help
A network or IT administrator from your organization should be able to assist if you find further difficulties in configuring the email settings.
Check the logs on the email server side. If your organization is using Microsoft Exchange as an email server, check the Microsoft Exchange log entries to see if the email server was reached and what problem was encountered.
If on the console or log file there is an exception similar with
Caused by: javax.mail.MessagingException: Could not connect to SMTP host: host-here, port: port-here, response: 421
This represents Email SMTP Error 421 (see the SMTP error code 421 in the exception) and you will need to work together with your IT Network or Microsoft Exchange administrator which should further read and interpret the email server log entries (e.g. Microsoft Exchange logs).
Possible ISP limitation
In addition, you might need to let your ISP know that you have a legitimate reason for sending many emails.
More details about Email SMTP Error 421
SMTP Error 421: The Mail transfer service is unavailable because of a transient event. SMTP reply 421 can be caused by many things but generally indicates that the mail server which returns this status code is currently unavailable but may be available later. For example, the server administrator may have stopped the mail service to troubleshoot a problem, or the mail server is right in the middle of rebooting, or the mail server is currently processing too many incoming messages or incoming requests, etc.... Note : Mail Server in this case can be any of the mail servers on the message’s route – the sending server (your server), the ISP SMTP server, or the recipient’s mail server. Clearly, if you repeatedly receive an SMTP status 421 then the problem is no longer of a transient nature and you need to investigate or inform the relevant network administrator, ISP tech support, or the recipient.
SMTP Response 421 can also be received as a result of your message server sending an email where the total number of TO, CC, and BCC users results in a number of simultaneous SMTP connections that is in excess of the number of connections your ISP or SMTP service allows. A typical error message for this situation would be : 421 Too many concurrent SMTP connections from this IP address; please try again later. Typically, when this happens your server will have sent some of the messages (note that for all servers, each email sent by a user always gets broken down into individual separate emails to each of the recipients in the TO, CC, and BCC fields), and will automatically retry a little later to send the remaining messages.
This is how people will usually describe this issue
We are able to burst reports to colleagues with internal email addresses successfully. Our problem is that when we try to send TO or CC to external clients / emails the burst email always fails.
If on the console or log file there is an exception similar with
com.sun.mail.smtp.SMTPAddressFailedException: 550 5.7.1 Unable to relay
In DocumentBurster™ main window select → → →
User name field should not be empty. It should be a valid Exchange/NT user name and the user name should be complete, including the network prefix (e.g. EHNET\cjohn).
When sending emails to external addresses, for security/spam reasons, Exchange is more strict and requires people to authenticate. This is not the case when sending emails to internal email addresses. This is the meaning of 550 5.7.1 Unable to relay Exchange exception.
This is how people will usually describe this issue
The first pass ran through fine and files burst into folder – all 187. I then chose to email and burst - the file got through to number 45 or so and then started to fail.
In the
logs/documentburster.log
file there is an exception similar
with
java.net.SocketTimeoutException: Read timed out
This is usually happening when the email SMTP server (Exchange?) your organization is using needs some tuning/configuration in order to distribute many emails in a short period of time.
Following possible approaches can be taken in order to solve the situation
DocumentBursterâ„¢ can be configured to log more details about the SMTP communication.
Edit the file
config/burst/settings.xml
and do the bold change
<emailserver><debug>false</debug></emailserver>
change to
<emailserver><debug> true </debug></emailserver>.
Run the program again and check DocumentBursterâ„¢ log file to see more details about the email SMTP communication.
If you have problems in getting the upload functionality to work make sure the upload command is configured properly, as described in Section 3.5, “Upload Reports� .
In addition, you might check the
logs/cURL.log
file for further
details about any possible upload error.
In DocumentBurster™ main window select →
Select edit for the configuration template which needs to be
restored and copy the default values
from the
config/burst/default/defaults.xml
existing file.