iMc 7.3 E0705P04 dbman not working

[RuudTeeling]

imc 7.3 E0705P04 on Windows 2012 R2, remote SQL Server, SQL2008R2

dbman not working, manual backup failed. 

dbman.db.log:

2020-05-06 10:58:58 [ERROR] [getPwdFromhwConf] not find imchw.conf .
2020-05-06 10:58:58 [ERROR] [decryptMsg] not find ks.dat .
2020-05-06 10:58:58 [DEBUG] [CConfigT::decodePasswordInConf] After debase64 length: 16
2020-05-06 10:58:58 [ERROR] [getPwdFromhwConf] not find imchw.conf .
2020-05-06 10:58:58 [ERROR] [decryptMsg] not find ks.dat .
2020-05-06 10:58:58 [DEBUG] [CConfigT::decodePasswordInConf] After debase64 length: 16
2020-05-06 10:58:58 [ERROR] [getPwdFromhwConf] not find imchw.conf .
2020-05-06 10:58:58 [ERROR] [decryptMsg] not find ks.dat .
2020-05-06 10:58:58 [DEBUG] [CConfigT::decodePasswordInConf] After debase64 length: 16
2020-05-06 10:58:58 [ERROR] [getPwdFromhwConf] not find imchw.conf .
2020-05-06 10:58:58 [ERROR] [decryptMsg] not find ks.dat .
2020-05-06 10:58:58 [INFO] [Main] Version: 7.3
2020-05-06 10:58:58 [INFO] [Main] Global directory: C:/Program Files/iMC/dbman
2020-05-06 10:58:58 [INFO] [Main] Listenning on port: 2810
2020-05-06 10:58:58 [DEBUG] [Main] arv count 3
2020-05-06 10:58:58 [DEBUG] [Main] arv 1: dbman
2020-05-06 10:58:58 [DEBUG] [Main] arv 2: -backup
2020-05-06 10:58:58 [DEBUG] [Main] arv 3: C:\dbmanbak
2020-05-06 10:58:58 [INFO] [Client::connect_to_server] Starting connect to 127.0.0.1: 2810
2020-05-06 10:58:58 [INFO] [Client::connect_to_server] Established connection to 127.0.0.1: 2810
2020-05-06 10:58:58 [ERROR] [getPwdFromhwConf] not find imchw.conf .
2020-05-06 10:58:58 [ERROR] [encryptMsgAes] not find ks.dat .
2020-05-06 10:58:58 [ERROR] [make_msg_encode] code dbman_encode_len() failed!

2020-05-06 10:58:58 [ERROR] [Client::send_manual_backup] Fail to send data
2020-05-06 10:58:58 [DEBUG] [My_Accept_Handler::handle_input] Connection established 127.0.0.1
2020-05-06 10:58:58 [DEBUG] [CDataConnStreamQueueT::deal_msg] Client close conn

This error appears in def_log in folder .\dbman\bin

2020-05-06 10:58:58.233 [ERROR (101)] [THREAD(12616)] [qvdm::QvGetConfItem] Fail to get config path, please check if QVROOT is configured.

How to fix this?

[jguse]

Hello,

The errors are caused by two security files in iMC (imchw.conf and ks.dat) that are apparently missing. Are you performing a migration here? If so, please copy the following files manually from the old system from which you took the backup to the same path on the new one.

iMC\server\conf\imchw.conf 

iMC\common\conf\ks.dat

This will need to be done on all systems where DMA is installed, including the DB server. Then try restarting iMC and attempt the restore again.

[IvoVelikov]

Hello,

I see that you are running MSSQL 2008, which is not supported with the newest patch.

Please check the readme-file below, section Installation Prerequisites to see what are the minimum requrements for running the system:

https://support.hpe.com/hpesc/public/docDisplay?docId=a00098608en_us

Thanks,

Regards,

Ivaylo

[RuudTeeling]

Hello Justin,

No, I am not performing a migration. I would like to, but I don't get dbman working. Both files are present in the paths. There is only one server with DMA installed, the SQL server only has dbman.

Can I do backup and restore at SQL backup level? Or with backup solution like Veeam?

Best Regards,
Ruud

[jguse]

Hello,

Are you trying to run dbman manually on the DB Server? That is no longer supported for some time now, and there may be issues, also because of the addition of the security files I mentioned. If they don't exist on the DB server you could run into errors like you are seeing here.

To run dbman properly on the DB server, please install DMA by running installslave.bat (in E0705 installation files) and following the wizard, connecting it to the IP of the iMC system. Doing so will ensure dbman has the proper configuration files to work. Remember to restart iMC afterwards - you should see the dbman.exe and tftpserver.exe processes running on the IP of the DB server on DMA 'process' tab.

Then try the backup again. Note that if there's still an issue, in Domain environments you may also need to grant 'Full Control' permission to local 'Users' group for the iMC\dbman\bak folder on the servers - it's where the DB backups are temporarily stored before being transferred and moved to the destination folder.

Dbman backs up not only the databases, but also important configuration and security files on the filesystem of the iMC server(s). Hence backup via other solutions like SQL Server backup will not work properly, you will definitely run into issues during the migration if you tried that.

[RuudTeeling]

Hello,

Thanks for your reply.

SQL Server has OS Windows Server 2008 R2. iMc Server has Windows 2012 R2, I upgraded iMC server succesfully to E0705P04. When I run installslave on SQL Server it says: Current OS not supported...

Start checking installation environments...

Checking OS version...
Checking failed. Current OS is not supported.
Checking ports occupied...
Passed
Checking physical memory size...
Passed
Checking database installation...
Passed
Checking database connectivity...
Passed

I want to upgrade the OS of the iMc server to Windows 2019 (new Server) and I want to Upgrade the SQL server to SQL 2017 Enterprise (new Server). What steps do I take so I can migrate?