A few months ago, I tripped over a very mysterious problem while attempting to connect to a 7.3 CS docbase from within dqMan.
\nWe had 3 docbases and we could connect using this client to all of them but one ! Moreover, we could connect to all three using a remote Documentum Administrator or the local idql\/iapi command-line tools. Since we could connect to at least one of them with dqMan, this utility was not guilty. Also, since all three docbases accepted connections, they were all OK in this respect. Ditto for the account used, dmadmin or nominative ones; local connections were possible hence the accounts were all active and, as they could be used from within the remote DA, their identification method and password were correct too.
\nWe tried connecting from different workstations in order to check the dqMan side, we cleared its caches, we reinstalled it, but to no avail. We checked the content server’s log, as usual nothing relevant. It was just the combination of this particular docbase AND dqMan. How strange !
\nSo what the heck was wrong here ?
\nAs we weren’t the only administrators of those repositories, we more or less suspecting someone else change some setting but which one ? Ok, I sort of gave it away in the title but please bear with me and read on.
\nI don’t remember exactly how, we were probably working in panic mode, but we eventually decided to compare the docbases’ dm_docbase_config object side by side as shown below (with some obfuscation):<\/p>\n
\npaste <(iapi bad_boy -Udmadmin -Pxxx <<eoq | awk '{print substr($0, 1, 80)}'\nretrieve,c,dm_docbase_config\ndump,c,l\nquit\neoq\n) <(iapi good_boy -Udmadmin -Pxxx <<eoq | awk '{print substr($0, 1, 80)}'\nretrieve,c,dm_docbase_config\ndump,c,l\nquit\neoq\n) | column -c 30 -s $'t' -t | tail +11 | head -n 48\nUSER ATTRIBUTES USER ATTRIBUTES\n object_name : bad_boy object_name : good_boy\n title : bad_boy Repository title : good_boy Global Repository\n subject : subject :\n authors []: authors []: \n keywords []: keywords []: \n resolution_label : resolution_label :\n owner_name : bad_boy owner_name : good_boy\n owner_permit : 7 owner_permit : 7\n group_name : docu group_name : docu\n group_permit : 5 group_permit : 5\n world_permit : 3 world_permit : 3\n log_entry : log_entry :\n acl_domain : bad_boy acl_domain : good_boy\n acl_name : dm_450xxxxx80000100 acl_name : dm_450xxxxx580000100\n language_code : language_code :\n mac_access_protocol : nt mac_access_protocol : nt\n security_mode : acl security_mode : acl\n auth_protocol : auth_protocol :\n index_store : DM_bad_boy_INDEX index_store : DM_good_boy_INDEX\n folder_security : T folder_security : T\n effective_date : nulldate effective_date : nulldate\n richmedia_enabled : T richmedia_enabled : T\n dd_locales [0]: en dd_locales [0]: en\n default_app_permit : 3 default_app_permit : 3\n oldest_client_version : oldest_client_version :\n max_auth_attempt : 0 max_auth_attempt : 0\n client_pcaching_disabled : F client_pcaching_disabled : F\n client_pcaching_change : 1 client_pcaching_change : 1\n fulltext_install_locs [0]: dsearch fulltext_install_locs [0]: dsearch\n offline_sync_level : 0 offline_sync_level : 0\n offline_checkin_flag : 0 offline_checkin_flag : 0\n wf_package_control_enabled : F wf_package_control_enabled : F\n macl_security_disabled : F macl_security_disabled : F\n trust_by_default : T trust_by_default : T\n trusted_docbases []: trusted_docbases []: \n login_ticket_cutoff : nulldate login_ticket_cutoff : nulldate\n auth_failure_interval : 0 auth_failure_interval : 0\n auth_deactivation_interval : 0 auth_deactivation_interval : 0\n dir_user_sync_on_demand : F dir_user_sync_on_demand : F\n check_client_version : T check_client_version : F\n audit_old_values : T audit_old_values : T\n docbase_roles []: docbase_roles [0]: Global Registry\n approved_clients_only : F approved_clients_only : F\n minimum_owner_permit : 2 minimum_owner_permit : 0\n minimum_owner_xpermit : minimum_owner_xpermit :\n dormancy_status : dormancy_status :\n<\/pre>\nThe only significant differences were the highlighted ones and the most obvious one was the attribute check_client_version, it was turned on in the bad_boy repository. Now that we finally had something to blame, the universe started making sense again ! We quickly turned this setting to false and could eventually connect to that recalcitrant docbase. But the question is still open: check against what ? What criteria was applied to refuse dqman access to bad_boy but to allow it to good_boy ? That was still not clear, even though we could work around it.
\nNow, who and why turned it on, that had to remain a mystery.
\nWhile we were at it, we also noticed another attribute which seemed to be related to the previous one: oldest_client_version.
\nWas there any other client_% attribute in dm_docbase_config ?<\/p>\n
\npaste <(iapi good_boy -Udmadmin -Pdmadmin <<eoq | grep client\nretrieve,c,dm_docbase_config\ndump,c,l\nquit\neoq) <(iapi bad_boy -Udmadmin -Pdmadmin <<eoq | grep client\nretrieve,c,dm_docbase_config\ndump,c,l\nquit\neoq) | column -s $'t' -t\n oldest_client_version : oldest_client_version : \n client_pcaching_disabled : F client_pcaching_disabled : F\n client_pcaching_change : 1 client_pcaching_change : 1\n check_client_version : F check_client_version : T\n approved_clients_only : F approved_clients_only : F\n\n<\/pre>\nYes, but they looked quite harmless in the current context.
\nThus, the relevant attributes here are check_client_version and oldest_client_version. Let’s discover a bit more about them.<\/p>\n
Digging<\/h2>\n
As usual, the documentation is a bit scketchy about these attributes:<\/p>\n
\ncheck_client_version Boolean S T means that the repository\n servers will not accept connections\n from clients older than the\n version level specified in the\n oldest_client_version property.\n F means that the servers accept\n connections from any client version.\n The default is F.\n\noldest_client _version string(32) S Version number of the oldest\n Documentum client that will access\n this repository.\n This must be set manually. It is used\n by the DFC to determine how to\n store chunked XML documents. If\n check_client_version is set to T,then\n this value is also used to identify the\n oldest client version level that may\n connect to the repository.\n<\/pre>\nBut what is the client version ? Logically, it is the version of its DfCs or, for older clients, the version of the dmcl shared library.
\nSo, if check_client_version is true, the client version is checked and if it is older than the one defined in oldest_client_version, the client is forbidden to connect. That makes sense except that in our case, oldest_client_version was empty. Maybe in such a case, the client has to match exactly the content server’s DfC version ? As dqMan was either using the dmcl40.dll library or an old Dfc version, it was rejected. Let’s verify these hypothesis with a 16.4 target repository.
\nConnecting from an ancient 5.3 client<\/strong>
\nWe exhumed an old 5.3 CS installation to use its client part with the default configuration in the target docbase:
\n
\ndmadmin@osboxes:~\/documentum53$ idql dmtest -Udmadmin -Pdmadmin
\n
\n
\n\tDocumentum idql - Interactive document query interface
\n\t(c) Copyright Documentum, Inc., 1992 - 2004
\n\tAll rights reserved.
\n\tClient Library Release 5.3.0.115 Linux
\n
\n
\nConnecting to Server using docbase dmtest
\n[DM_SESSION_I_SESSION_START]info: \"Session 0100c35080003913 started for user dmadmin.\"
\n
\n
\nConnected to Documentum Server running Release 16.4.0080.0129 Linux64.Oracle
\n<\/code>
\nFine so far.
\nLet’s activate the dm_docbase_config.check_client_version in the target:
\n
\nretrieve,c,dm_docbase_config
\n...
\nset,c,l,check_client_version
\nSET> T
\n...
\nOK
\nAPI> save,c,l
\n...
\n[DM_DCNFG_E_CANT_SAVE]error: \"Cannot save dmtest docbase_config.\"
\n
\n[DM_DCNFG_E_SET_OLDEST_CLIENT_VERSION_FIRST]error: \"The docbase_config object attribute oldest_client_version has to be set before setting attribute check_client_version to T.\"
\n<\/code>
\nInteresting. At that time, this attribute was empty and yet the check_client_version was active. Is this constraint new in 16.4 or did the unknow administrator hack around this ? As I don’t have a 7.x repository available right now, I cannot test this point.
\nLet’s play by the rules and set oldest_client_version:
\n
\nreset,c,l
\nset,c,l,oldest_client_version
\n16.4
\nsave,c,l
\nOK
\nset,c,l,check_client_version
\nSET> T
\n...
\nOK
\nAPI> save,c,l
\n...
\nOK
\n<\/code>
\nTry connecting from the 5.3 client: still OK.
\nMaybe a reinit is necessary to actuate the changes:
\n
\nreinit,c
\n<\/code>
\nTry again:
\n
\ndmadmin@osboxes:~\/documentum53$ idql dmtest -Udmadmin -Pdmadmin
\n&nbps;
\n&nbps;
\n\tDocumentum idql - Interactive document query interface
\n\t(c) Copyright Documentum, Inc., 1992 - 2004
\n\tAll rights reserved.
\n\tClient Library Release 5.3.0.115 Linux
\n
\n
\nConnecting to Server using docbase dmtest
\nCould not connect
\n[DM_SESSION_E_START_FAIL]error: \"Server did not start session. Please see your system administrator or check the server log.
\nError message from server was:
\n[DM_SESSION_E_AUTH_FAIL]error: \"Authentication failed for user dmadmin with docbase dmtest.\"
\n
\n\"
\n<\/code>
\nSo a reinit it required indeed.
\nNote the misleading error, it is not the authentication that is wrong but the client version validation. It is such wrong messages that make diagnosis of Documentum problems so hard and time-consuming. Anyway, let’s revert the check_client_version to F:
\n
\nset,c,l,check_client_version
\nF
\nsave,c,l
\nreinit,c
\n<\/code>
\nTry connecting: OK. So, the client version filtering is effective. Let’s try it with a 5.3 client version:
\n
\nAPI> set,c,l,oldest_client_version
\nSET> 5.3
\n...
\nOK
\nAPI> save,c,l
\n...
\nOK
\nAPI> set,c,l,check_client_version
\nSET> T
\n...
\nOK
\nAPI> save,c,l
\n...
\nOK
\nAPI> reinit,c
\n...
\nOK
\n<\/code>
\nTry connecting: OK, that’s expected.
\nLet’s try it for a minimum 5.2 client version: it still works, which is expected too since the test client’s version is 5.3 and in my books 5.3 > 5.2.
\nLet’s try it for a miminum a 5.4 client version: the connection fails, so client version checking works as expected here.
\nLet’s try it for a miminum a 20.0 client version: the connection fails as expected. No check on the version’s value is done, which is quite understandable programmatically speaking, although a bit optimistic in the context of the turmoil Documentum went through lately.
\nLet’s go back to a more realistic value:
\n
\nAPI> set,c,l,oldest_client_version
\nSET> 7.2
\n...
\n[DM_SESSION_E_AUTH_FAIL]error: \"Authentication failed for user dmadmin with docbase dmtest.\"
\n
\n
\nAPI> save,c,l
\n<\/code>
\nOops, interestingly, the last change did not make it because with the current setting so down the way into the future, the present client’s session was disconnected and there is no way to reconnect in order to revert it !
\nLet’s do the rollback from the database level directly:
\n
\nsqlplus dmtest@orcl
\n
\nSQL*Plus: Release 12.2.0.1.0 Production on Mon Jun 10 16:25:56 2019
\n
\nCopyright (c) 1982, 2016, Oracle. All rights reserved.
\n
\nEnter password:
\nLast Successful login time: Mon Jun 10 2019 16:25:40 +02:00
\n
\nConnected to:
\nOracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production
\nWith the Partitioning, OLAP, Advanced Analytics and Real Application Testing options
\n
\nSQL> update dm_docbase_config_s set check_client_version = 0;
\n
\n1 row updated.
\nSQL> commit;
\n
\nCommit complete.
\n
\nquit;
\n<\/code>
\nTry to connect:
\n
\niapi dmtest@docker:1489
\nPlease enter a user (dmadmin):
\nPlease enter password for dmadmin:
\n
\n
\n\tOpenText Documentum iapi - Interactive API interface
\n\tCopyright (c) 2018. OpenText Corporation
\n\tAll rights reserved.
\n\tClient Library Release 16.4.0070.0035
\n
\n
\nConnecting to Server using docbase dmtest
\n[DM_SESSION_E_AUTH_FAIL]error: \"Authentication failed for user dmadmin with docbase dmtest.\"
\n<\/code>
\nStill not ok because the reinit is missing but for this we need to connect which we still cannot because of the missing reinit. To break this catch-22 situation, let’s cut the gordian knot and kill the dmtest docbase’s processes:
\n
\ndmadmin@docker:~$ ps ajxf | grep dmtest
\n 1 27843 27843 27843 ? -1 Ss 1001 0:00 .\/documentum -docbase_name dmtest -security acl -init_file \/app\/dctm\/dba\/config\/dmtest\/server.ini
\n27843 27849 27843 27843 ? -1 S 1001 0:00 _ \/app\/dctm\/product\/16.4\/bin\/mthdsvr master 0xe901fd2f, 0x7f8a50658000, 0x223000 50000 5 27843 dmtest \/app\/dctm\/dba\/log
\n27849 27850 27843 27843 ? -1 Sl 1001 0:03 | _ \/app\/dctm\/product\/16.4\/bin\/mthdsvr worker 0xe901fd2f, 0x7f8a50658000, 0x223000 50000 5 0 dmtest \/app\/dctm\/dba\/log
\n27849 27861 27843 27843 ? -1 Sl 1001 0:03 | _ \/app\/dctm\/product\/16.4\/bin\/mthdsvr worker 0xe901fd2f, 0x7f8a50658000, 0x223000 50000 5 1 dmtest \/app\/dctm\/dba\/log
\n27849 27874 27843 27843 ? -1 Sl 1001 0:03 | _ \/app\/dctm\/product\/16.4\/bin\/mthdsvr worker 0xe901fd2f, 0x7f8a50658000, 0x223000 50000 5 2 dmtest \/app\/dctm\/dba\/log
\n27849 27886 27843 27843 ? -1 Sl 1001 0:03 | _ \/app\/dctm\/product\/16.4\/bin\/mthdsvr worker 0xe901fd2f, 0x7f8a50658000, 0x223000 50000 5 3 dmtest \/app\/dctm\/dba\/log
\n27849 27899 27843 27843 ? -1 Sl 1001 0:03 | _ \/app\/dctm\/product\/16.4\/bin\/mthdsvr worker 0xe901fd2f, 0x7f8a50658000, 0x223000 50000 5 4 dmtest \/app\/dctm\/dba\/log
\n27843 27862 27843 27843 ? -1 S 1001 0:00 _ .\/documentum -docbase_name dmtest -security acl -init_file \/app\/dctm\/dba\/config\/dmtest\/server.ini
\n27843 27863 27843 27843 ? -1 S 1001 0:00 _ .\/documentum -docbase_name dmtest -security acl -init_file \/app\/dctm\/dba\/config\/dmtest\/server.ini
\n27843 27875 27843 27843 ? -1 S 1001 0:00 _ .\/documentum -docbase_name dmtest -security acl -init_file \/app\/dctm\/dba\/config\/dmtest\/server.ini
\n27843 27887 27843 27843 ? -1 S 1001 0:00 _ .\/documentum -docbase_name dmtest -security acl -init_file \/app\/dctm\/dba\/config\/dmtest\/server.ini
\n27843 27901 27843 27843 ? -1 S 1001 0:00 _ .\/documentum -docbase_name dmtest -security acl -init_file \/app\/dctm\/dba\/config\/dmtest\/server.ini
\n27843 27944 27843 27843 ? -1 Sl 1001 0:06 _ .\/dm_agent_exec -docbase_name dmtest.dmtest -docbase_owner dmadmin -sleep_duration 0
\n27843 27962 27843 27843 ? -1 S 1001 0:00 _ .\/documentum -docbase_name dmtest -security acl -init_file \/app\/dctm\/dba\/config\/dmtest\/server.ini
\n<\/code>
\nand:
\n
\nkill -9 -27843
\n<\/code>
\nAfter restarting the docbase, the connectivity was restored.
\nSo, be cautious while experimenting ! Needless to say, avoid doing it in a production docbase or in any heavily used development docbase for that matter, or the wrath of the multiverses and beyond will fall upon you and you will be miserable for ever.
\nConnecting from a 7.3 client<\/strong>
\nThe same behavior and error messages as with the precedent 5.3 client were observed with a more recent 7.3 client and, inferring from the incident above, later clients behave the same way.<\/p>\nConclusion<\/h2>\n
We never stop learning stuff with Documentum ! While this client version limiting feature looks quite exotic, it may make sense in order to avoid surprises or even corruptions when using newly implemented extensions or existing but changed areas of the content server. It is possible that new versions of the DfCs behave differently from older ones in dealing with the same functionalities and Documentum had no better choice but to cut the older versions off to prevent any conflict. As usual, the implementation looks a bit hasty with inapt error messages costing hours of investigation and the risk to cut oneself off a repository.<\/p>\n","protected":false},"excerpt":{"rendered":"
A few months ago, I tripped over a very mysterious problem while attempting to connect to a 7.3 CS docbase from within dqMan. We had 3 docbases and we could connect using this client to all of them but one ! Moreover, we could connect to all three using a remote Documentum Administrator or the […]<\/p>\n","protected":false},"author":40,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[525],"tags":[],"type_dbi":[],"class_list":["post-12501","post","type-post","status-publish","format-standard","hentry","category-enterprise-content-management"],"acf":[],"yoast_head":"\n
An exotic feature in the content server: check_client_version - dbi Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/an-exotic-feature-in-the-content-server-check_client_version\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"An exotic feature in the content server: check_client_version\" \/>\n<meta property=\"og:description\" content=\"A few months ago, I tripped over a very mysterious problem while attempting to connect to a 7.3 CS docbase from within dqMan. We had 3 docbases and we could connect using this client to all of them but one ! Moreover, we could connect to all three using a remote Documentum Administrator or the […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/an-exotic-feature-in-the-content-server-check_client_version\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2019-06-16T15:26:24+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-10-24T07:32:15+00:00\" \/>\n<meta name=\"author\" content=\"Middleware Team\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Middleware Team\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"12 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/an-exotic-feature-in-the-content-server-check_client_version\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/an-exotic-feature-in-the-content-server-check_client_version\\\/\"},\"author\":{\"name\":\"Middleware Team\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/8d8563acfc6e604cce6507f45bac0ea1\"},\"headline\":\"An exotic feature in the content server: check_client_version\",\"datePublished\":\"2019-06-16T15:26:24+00:00\",\"dateModified\":\"2025-10-24T07:32:15+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/an-exotic-feature-in-the-content-server-check_client_version\\\/\"},\"wordCount\":1137,\"commentCount\":0,\"articleSection\":[\"Enterprise content management\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/an-exotic-feature-in-the-content-server-check_client_version\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/an-exotic-feature-in-the-content-server-check_client_version\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/an-exotic-feature-in-the-content-server-check_client_version\\\/\",\"name\":\"An exotic feature in the content server: check_client_version - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"datePublished\":\"2019-06-16T15:26:24+00:00\",\"dateModified\":\"2025-10-24T07:32:15+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/8d8563acfc6e604cce6507f45bac0ea1\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/an-exotic-feature-in-the-content-server-check_client_version\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/an-exotic-feature-in-the-content-server-check_client_version\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/an-exotic-feature-in-the-content-server-check_client_version\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"An exotic feature in the content server: check_client_version\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/8d8563acfc6e604cce6507f45bac0ea1\",\"name\":\"Middleware Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/ddcae7ba0f9d1a0e7ae707f0e689e4a9c95bb48ec49c8e6d9cc86d43f4121cb6?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/ddcae7ba0f9d1a0e7ae707f0e689e4a9c95bb48ec49c8e6d9cc86d43f4121cb6?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/ddcae7ba0f9d1a0e7ae707f0e689e4a9c95bb48ec49c8e6d9cc86d43f4121cb6?s=96&d=mm&r=g\",\"caption\":\"Middleware Team\"},\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/author\\\/middleware-team\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"An exotic feature in the content server: check_client_version - dbi Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/an-exotic-feature-in-the-content-server-check_client_version\/","og_locale":"en_US","og_type":"article","og_title":"An exotic feature in the content server: check_client_version","og_description":"A few months ago, I tripped over a very mysterious problem while attempting to connect to a 7.3 CS docbase from within dqMan. We had 3 docbases and we could connect using this client to all of them but one ! Moreover, we could connect to all three using a remote Documentum Administrator or the […]","og_url":"https:\/\/www.dbi-services.com\/blog\/an-exotic-feature-in-the-content-server-check_client_version\/","og_site_name":"dbi Blog","article_published_time":"2019-06-16T15:26:24+00:00","article_modified_time":"2025-10-24T07:32:15+00:00","author":"Middleware Team","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Middleware Team","Est. reading time":"12 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/an-exotic-feature-in-the-content-server-check_client_version\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/an-exotic-feature-in-the-content-server-check_client_version\/"},"author":{"name":"Middleware Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d8563acfc6e604cce6507f45bac0ea1"},"headline":"An exotic feature in the content server: check_client_version","datePublished":"2019-06-16T15:26:24+00:00","dateModified":"2025-10-24T07:32:15+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/an-exotic-feature-in-the-content-server-check_client_version\/"},"wordCount":1137,"commentCount":0,"articleSection":["Enterprise content management"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/an-exotic-feature-in-the-content-server-check_client_version\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/an-exotic-feature-in-the-content-server-check_client_version\/","url":"https:\/\/www.dbi-services.com\/blog\/an-exotic-feature-in-the-content-server-check_client_version\/","name":"An exotic feature in the content server: check_client_version - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2019-06-16T15:26:24+00:00","dateModified":"2025-10-24T07:32:15+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d8563acfc6e604cce6507f45bac0ea1"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/an-exotic-feature-in-the-content-server-check_client_version\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/an-exotic-feature-in-the-content-server-check_client_version\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/an-exotic-feature-in-the-content-server-check_client_version\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"An exotic feature in the content server: check_client_version"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d8563acfc6e604cce6507f45bac0ea1","name":"Middleware Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/ddcae7ba0f9d1a0e7ae707f0e689e4a9c95bb48ec49c8e6d9cc86d43f4121cb6?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/ddcae7ba0f9d1a0e7ae707f0e689e4a9c95bb48ec49c8e6d9cc86d43f4121cb6?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/ddcae7ba0f9d1a0e7ae707f0e689e4a9c95bb48ec49c8e6d9cc86d43f4121cb6?s=96&d=mm&r=g","caption":"Middleware Team"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/middleware-team\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/12501","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/40"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=12501"}],"version-history":[{"count":1,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/12501\/revisions"}],"predecessor-version":[{"id":41186,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/12501\/revisions\/41186"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=12501"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=12501"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=12501"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=12501"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}