Documentum Bug 147071

Bug 147071 was introduced in D6 and was patched with hotfix  You’ve probably run into bug 147071 if you have recieved a Documentum VMware image from a colleague, moved an image from one server to another, or are running the Content Server on a host that does not have a static IP address.  Your encounter with the bug probably looked something like this:

[DM_SESSION_E_CLIENT_AUTHENTIFICATION_FAILURE] error: “Could not authenticate the client installation for reason: Client hostname in authentication string doesn’t match value in registry

The hotfix clears the problem up easily.  The problem I have is, I can never remember where to find the hotfix?  So, as a service to all of you frusterated developers, here is the hotfix and the support note (#esg90932):  There is additional information in support notes #esg92607 and #esg103473.

Anther possible remedy to this bug is to delete the dfc.keystore file and reboot server.  I have never tried this.  If you have, let me know how it works.


About Scott
I have been implementing Documentum solutions since 1997. In 2005, I published a book about developing Documentum solutions for the Documentum Desktop Client (ISBN 0595339689). In 2010, I began this blog as a record of interesting and (hopefully) helpful bits of information related to Documentum, and as a creative outlet.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: