After hostname changed, encountered some error

Lugaan · 2024-04-04T10:34:19+00:00

There was an error rendering this rich post.

Hi all,

I recently performed a hostname change for the windows server as well as documentum servers. However, I am getting this error from the repo logs.

Also, I used OTDS to authenticate the users, but when I go to login to D2 it throws an error saying "[DM_SESSION_E_AUTH_FAIL]error: Authentication failed for user <username> with docbase <docbase_name>"

If anyone knows how to solve this please let me know. Thank you so much in advance.

Find more posts tagged with

Documentum

OTDS

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

All comments

Hicham Bahi

You need to use the utility MigrationUtil.bat if you want to change the host name. Checkout the Documentum Platform and Platform Extensions CE 23.2 - Installation Guide English (EDCSY230200-IGD-EN-01), section 2.7.9 "Using the migration utility". It will take care of updating any referenced to the host name in scripts, config files (e.g. server.ini.user_auth_target) and in the database.

Lugaan

I indeed did use the MigrationUtil.bat to update the hostname change. I changed the the hostname twice as in I used the FQDN and the shorter version of FQDN as well. However, somehow it didn’t work.

Hicham Bahi

OK then something must have gone very wrong. I haven't used that utility myself yet. Did you check the logs of the utility? The error from the repo log indicates an issue with the docbroker request having failed. So check first that the docbroker is running properly.

Lugaan

Yes I did check the logs, no errors was indicated. It runs, even loading da and D2 works.

Michael McCollough

Probably best to open a support ticket to get a bit of guided support here. What does your docbroker log look like, did it successfully start?

If you go to command prompt and do: netstat -a | findstr "1489" do you see the hostname/ip expected and that is is listening on 1489?

Double-check server.init and %DOCUMENTUM_CONFIG%\dfc.properties to ensure the hostname updated.

I am doing this from the top of my head (that is why support would be a better option as they can guide better). Hopefull this or a support case will help resolve your issue.

I remember a little something with windows services were the hostname might be part of the service startup (check the command line for the dmdocbroker services (Start→Run→services.msc) it might have the old hostname, preventing the docbroker from starting up.