Backup Related Issues
org.postgresql.util.PSQLException: ERROR: index "xxxx_pk" contains unexpected zero page at block {x}
KB-ID: BK01
Exception trace:
java.util.zip.ZipException:
duplicate entry: ZIA*.pdf
Reason for the issue:
Breakage in ZIA Feature
Steps to resolve the issue:
The suggested fix for the issue is to upgrade the application to any build higher than 11009.
If an upgrade is not possible immediately, then to overcome this issue, you can take a trimmed backup (if it's manual backup) or you can take a backup of the database alone (if it's a scheduled backup).
And during the upgrade, take a manual trimmed backup and skip the backup during the upgrade process to prevent this issue from happening during upgrade.
KB-ID: BK02
Exception trace:
ERROR = *ERROR: Wrong key or corrupt data*org.postgresql.util.PSQLException: ERROR: Wrong key or corrupt data
Reason for the issue:
Wrong password reset query was executed in the DB
Steps to resolve the issue:
-
We need to need to update the wrongly updated password. Please connect to ServiceDesk Plus DB by following the steps available here .
-
Once connected, execute the below query.
select distinct(length(salt)) from aaapassword;
select * from aaapassword where length(salt) != 94 and length(salt) !=78 ;
Once the output is displayed, take a screenshot of the output for reference. -
Now, execute the below query to resolve the issue.
update AaaPassword set password='$2a$12$fZUC9IK8E/AwtCxMKnCfiu830qUyYB/JRhWpi2k1vgWLC6iLFAgxa', SALT=pgp_sym_encrypt('$2a$12$fZUC9IK8E/AwtCxMKnCfiu','SChar@123Mas!er','s2k-mode=1, cipher-algo=aes256'),algorithm='bcrypt' where length(salt)=13 or length(salt)=29 ; -
After successful execution of the query, restart the services of ServiceDesk Plus once and then try to take a backup.
KB-ID: BK03
Exception trace:
java.lang.OutOfMemoryError: Java heap space
Reason for the issue:
A huge amount of data resides in a specific table and the application is running out of memory while trying to fetch data from the specific table.
Steps to resolve the issue:
-
Open CMD and navigate to Drive:\ManageEngine\ServiceDesk\bin and type in the below command.Drive:\ManageEngine\ServiceDesk\bin> write backUpData.bat
-
This will open up the restoreData.bat file in write mode. In this file locate the string -Xmx
-
Next to this Xmx string, you should see a value. Please change the existing value to a higher value i.e if the existing value is 512m, change it to 1024m; if the value is 1024m, change it to 2048m
-
Once you've changed the value, save the file and try to run a backup.
KB-ID: BK04
Exception trace:
java.io.FileNotFoundException
Reason for the issue:
Breakage in the Request (created via Email) attachments with attachment name containing
colon(:)
in it
Steps to resolve the issue:
The suggested fix for the issue is to upgrade the application to any build higher than 11105.
If
an upgrade is not possible immediately, then to overcome this issue,
you can take a trimmed backup (if it's manual backup) or you can take a
backup of the database alone (if it's a scheduled backup).
And
during the upgrade, take a manual trimmed backup and skip the backup
during the upgrade process to prevent this issue from happening during
upgrade.
KB-ID: BK05
Exception trace:
org.postgresql.util.PSQLException: ERROR: index "xxxx_pk"
contains unexpected zero page at block
{x}
Reason for the issue:
DB indexing issue/ Data corruption
Steps to resolve the issue:
-
Stop ServiceDesk Plus Service.
-
Navigate to Drive:\ManageEngine\ServiceDesk\ and copy the pgsql folder to a different location as a backup
-
After the copy is complete, open CMD with admin privileges and navigate to Drive:\ManageEngine\ServiceDesk\bin and invoke the startDB.bat command as shown below.
Drive:\ManageEngine\ServiceDesk\bin > startDB.bat 65432 -
Once you see the message 'Database Started', connect to ServiceDesk Plus DB by following the steps available here .
-
Once connected, execute the below queries one-by-one in the same order.
reindex database servicedesk;
vacuum full;
reindex database servicedesk; -
After the above commands are executed successfully, close the CMD and open a new CMD with admin privileges.
-
In the new CMD, try to run a backup.
-
If the backup still fails, y ou can then raise a support ticket where we can help you with this further.
New to ADSelfService Plus?
Related Articles
Inputs required for analyzing Performance Issues
We need a couple of details to analyze Performance issue. So, please send the below details : Below mentioned details should be gathered before restarting the application. 1. Let us know whether you are taking Scheduled full backup or backup without ...Alternative for Full Backup - Trimmed backup
Applicable till 8.1 version (Till 8121 builds) Nowadays the database size is huge in various users instance. It is because the indexing related files, archived files, file attachments are folder are huge in size. Due to which either our application ...Inputs required for backup issues
Unable to take manual backup or schedule backup Backup is throwing an error Out of memory while taking backup Backup is slow. Inputs required. 1. ...Backup Issue - Stream closed error
Backup Error - Stream closed error : I request you to follow the below steps and take a trimmed back and check the case. 1. Shut down the application. 2. Edit the backUpData.bat (present under SupportCenter\bin folder) and tune the backUpData.bat as ...Error while invoking backup_MSSQLException: TDS Protocol error
java.sql.SQLException: TDS Protocol error: Invalid packet type 0x64 at Based on the Email screenshot it looks like you have the "TDS Protocol Error" message. We have seen this message occur under different situations and mostly it is a SQL or network ...