Error using WebService Call LinkComputersToUpByName on EnterprisenitGrou

Document ID : KB000101439
Last Modified Date : 13/06/2018
Show Technical Document Details
Issue:
When using LinkComputersToUnitGroupByName Web Services Call on Enterprise, we receive the error: "1,The requested object was not found" The computer and group are both visible on the Enterprise server and physical computer names and login values are correct. This type of problem can also happen with Web Services calls on the Domain Manager.
Environment:
Any supported Enterprise or Domain Manager system.
Cause:
Here is a sample XML run and the error returned. All items seem valid when checked:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:r11="urn://www.ca.com/Unicenter/DSM/r11">
<soapenv:Header/>
<soapenv:Body>
  <r11:LinkComputersToUnitGroupByName>
      <r11:sessionId>C7713CFB9BA3B1479A4B6C403A76E968</r11:sessionId>
      <r11:unitGroupPropertiesByName>
      <r11:unitGroupName>GROUP NAME</r11:unitGroupName>
      <r11:objectPreference></r11:objectPreference>
  </r11:unitGroupPropertiesByName>
      <r11:arrayOfComputerPropertiesByName>
      <r11:computerPropertiesByName>
      <r11:computerName>MACHINE NAME</r11:computerName>
      <r11:objectPreference></r11:objectPreference>
      <r11:domainName>DM MACHINE NAME</r11:domainName>
  </r11:computerPropertiesByName>
  </r11:arrayOfComputerPropertiesByName>
  </r11:LinkComputersToUnitGroupByName>
</soapenv:Body>
</soapenv:Envelope>

And response is:

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xop="http://www.w3.org/2004/08/xop/include" xmlns:xmime5="http://tempuri.org/xmime5.xsd" xmlns:dsm2="urn://www.ca.com/Unicenter/DSM/r12" xmlns:dsm1="urn://www.ca.com/Unicenter/DSM/r11" xmlns:ASWS2="automationServiceSoapBinding" xmlns:ASWS1="urn:com.ca.dsm.automationwebservice">
<SOAP-ENV:Header/>
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
    <faultcode>1,CMM000015</faultcode>
    <faultstring>1,The requested object was not found</faultstring>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

However in this case...the client had a custom Domain Display Name that was not the actual Enterprise/Domain Machine Name...This causes the call to fail as we look for the DISPLAY NAME rather than the actual DM/ES machine name...
Resolution:
The fix is simple...just update the XML to use the DISPLAY NAME for the Enterprise or Domain name shown in DSM Explorer, rather than the real name of the Server.