HPDM Server Service won’t start - db upgrade error

[danieldunn10]

Hi our HPDM console has suddenly stopped working and we can see the server service will not start 

in the logs we can see it is trying to do a database upgrade and failing at this point

2022-07-04 20:13:28 [main ] ERROR BatchingBatch - HHH000315: Exception executing batch [java.sql.BatchUpdateException: Invalid column name 'error_md5'.], SQL: insert into dm_tasklog (comment, error_code, error_detail, error_md5, update_date, device_id, sequence_num, subtask_id, task_id) values (?, ?, ?, ?, ?, ?, ?, ?, ?)
2022-07-04 20:13:28 [main ] WARN SqlExceptionHelper - SQL Error: 207, SQLState: S0001
2022-07-04 20:13:28 [main ] ERROR SqlExceptionHelper - Invalid column name 'error_md5'.

Can anyone help?

thank you

[MarcusC]

Hey @danieldunn10 🙂

Thank you for visiting the HP Support Community!

Admin and Mods are here to guide the customer to get the best experience from the Community.

To help volunteers that reply to posts in the Community, please provide more details about your issue. Here are some recommendations of information that can help volunteers to better understand and provide support to your question:

- Exact model of your printer / Desktop/ notebook (if you need help, click here for information on how to find your model number model).
- Operating system (including revisions made with service packs, 32-bit or 64-bit, etc.)
- Connection method - USB, physical LAN, or wireless?
- Error messages - on the printer display and/or computer, any patterns for flashing lights.
- Any system changes before the problem starts (Example: Operating System Update, Software installation);

Regards,

MarcusC

[danieldunn10]

Hi the HPDM software version is 5.0.8 running on Server 2016.

The only change was a server reboot.

The problem seems to be that it is trying to upgrade the database as the server service starts.

At the same time of starting the service (10:32am) we can see that in this log C:\Program Files\HP\HP Device Manager\Server\logs\hpdm-dbsetup.log

We can see it is because of this

2022-07-05 10:32:16 [main ] DEBUG Extension - nativeUpdateQuery DROP TABLE dm_tasklog
2022-07-05 10:32:16 [main ] DEBUG Extension - nativeUpdateQuery CREATE TABLE dm_tasklog (device_id nvarchar(50) not null, sequence_num numeric(19,0) not null, subtask_id nvarchar(50) not null, task_id nvarchar(50) not null, comment ntext null, error_code nvarchar(16) null, error_detail nvarchar(255) null, update_date datetime not null, primary key (device_id, sequence_num, subtask_id, task_id))
2022-07-05 10:32:16 [main ] DEBUG DMConnectionProvider - Checked out count:0
2022-07-05 10:32:16 [main ] DEBUG DMConnectionProvider - Checked out count:1
2022-07-05 10:32:16 [main ] INFO HibernateDBObject - Restoring task log table.
2022-07-05 10:32:16 [main ] DEBUG EntitiesHome - [TimeSpan] persist: 0
2022-07-05 10:32:16 [main ] DEBUG HibernateDBObject - v442_AddDynamicGroupingAttr
2022-07-05 10:32:16 [main ] DEBUG EntitiesHome - [TimeSpan] persist: 0
2022-07-05 10:32:16 [main ] DEBUG EntitiesHome - [TimeSpan] persist: 0
2022-07-05 10:32:16 [main ] DEBUG HibernateDBObject - v443_AddDynamicGroupingAttr
2022-07-05 10:32:16 [main ] DEBUG EntitiesHome - [TimeSpan] persist: 0
2022-07-05 10:32:16 [main ] DEBUG HibernateDBObject - v45_ChangeTable_ARM
2022-07-05 10:32:16 [main ] ERROR BatchingBatch - HHH000315: Exception executing batch [java.sql.BatchUpdateException: Invalid column name 'error_md5'.], SQL: insert into dm_tasklog (comment, error_code, error_detail, error_md5, update_date, device_id, sequence_num, subtask_id, task_id) values (?, ?, ?, ?, ?, ?, ?, ?, ?)
2022-07-05 10:32:16 [main ] WARN SqlExceptionHelper - SQL Error: 207, SQLState: S0001
2022-07-05 10:32:16 [main ] ERROR SqlExceptionHelper - Invalid column name 'error_md5'.

It appears to us that the 'error_md5' column isn’t created in the CRETE TABLE command and when values are tried to be inserted into it the column doesn’t exist

I'm not sure how I can be any clearer on the issue! it seems like a bug in the software? although I am not sure how to get around it

Thanks

[Manu_2680]

Hello Danieldunn10, 

Please ask your SQL Admin to allow read/write or complete access to the user that is used in HPDM Database. this mostly happens due to access restrictions on SQL Server.  I would like to know what was the older version of HPDM you had?

This error is normally caused : The ID that is being used to install the client does not have the correct permissions to the database tables.

[danieldunn10]

Thanks for your reply!

This doesn’t seem to be the issue I have checked with the DBA

We can view the table and make changes to it.

As you can see in the log above

- It drops the table

- creates a table without the column

- the sql command doesn’t include the column as you will see from the log above 

- because the column wasnt in the sql command, when the next sql command tries to insert some values it errors

- because it is trying to add to a column that doesn’t exist

We believe it is a bug in the software 

[danieldunn10]

Below is where it is creating the table

CREATE TABLE dm_tasklog (device_id nvarchar(50) not null, sequence_num numeric(19,0) not null, subtask_id nvarchar(50) not null, task_id nvarchar(50) not null, comment ntext null, error_code nvarchar(16) null, error_detail nvarchar(255) null, update_date datetime not null, primary key (device_id, sequence_num, subtask_id, task_id))

it looks like it creates these columns 

device_id

sequence_num

subtask_id

task_id

comment

error_code

error_detail

update_date 

and then it is inserting into the table it is just created

insert into dm_tasklog (comment, error_code, error_detail, error_md5, update_date, device_id, sequence_num, subtask_id, task_id) values (?, ?, ?, ?, ?, ?, ?, ?, ?)

these columns

comment

error_code

error_detail

error_md5

update_date

device_id

sequence_num

subtask_id

task_id

as you can see above the error_md5 column wont exist in the table it creates, but it tries to add a value to it which causes an error and then the server service wont start

[Manu_2680]

please open a case with HP Thin client Support. this might need a better look into the installation and debug logs from HPDM.