SOAP error in ITPAM when starting Automated Migration Job

Document ID : KB000050103
Last Modified Date : 14/02/2018
Show Technical Document Details



  • Migration Process completes the preparation phase but the ITPAM process errors on the first SOAP call.

  • The error in the process which we see in the PAM client is:

    • SOAP invocation failed: Message send failed


  • CABI/ITPAM server:

  • Windows 2008 R2 x64

  • Local SQL 2008

  • CABI 3.2

  • ITPAM 3.0 SP1

  • EEM

  • MDB Server:

  • Local SQL 2005

  • ITCM Server:

  • Windows 2008 R2 x64

  • ITCM r12.5

  • Automated Migration patch


  • Automated Migration Manager (AMM) creates the process definition in ITPAM when the AMM patch is installed.

  • To allow this it does not code the Web Service URL directly in to the process, rather it uses a variable which is configured with the correct value by AMM when a migration is activated

    Figure 1

  • In the environment above ITPAM and ITCM are on different servers so ITPAM needs to call the Web Service on the ITCM server

  • AMM only passed the shortname of the ITCM server when it provided the URL and ITPAM could not access the webservices with this url

  • This was not a name resolution issue and the ITPAM server could resolve the shortname of the ITCM server from the command line.


Modify the process definitions to have the actual FQDN of the Web Service URL in all the SOAP calls in the process

  1. Logon to ITPAM as ITPAM Admin and open the ITPAM Client

  2. Click "File - Open Library Browser - Default Environment - Orchestrator"

  3. Select "DsmAutomatedMigration"

  4. Dbl click the "Wipe and Reload Process"

    • This will display the Process editor

      Figure 2

  5. Dbl Click the first SOAP Call to display its proerties

    Figure 3

  6. Open the Connection properties section on the right hand pane that opens and overtype the value for the Web Service URL with the FQDN address of the web services on the ITCM server.

  7. Click the "check out" button in the tool bar

    Figure 4

  8. Change Web service URL to the actual FQDN value

    Figure 5


    • The port number may be different in your implementation and you should amend accordingly

    • The value must be surrounded by Quotes""

  9. Click apply

  10. Repeat for the other SOAP calls in the process

  11. Click the save button on toolbar

  12. Click the "check in" button on toolbar

  13. Repeat this for the "Machine Replacement" Process

The design has been modified in Service Pack 1 which is due to release early 2012. This design change causes AMM to always use the FQDN avoiding the need to make this modification if the products are distributed as above.