Clarity Service Management

Expand all | Collapse all

Migration Fail error231

Jump to Best Answer
  • 1.  Migration Fail error231

    Posted 10-27-2017 03:38 PM

    Hello Team

     

    On migrating step it keeps failing giving error 231. How ever this error belongs to 8dot3 which is already enabled on server in both HD partition  . What could be issue then??

     

    Attachment(s)

    zip
    stdout.txt.zip   42K 1 version
    zip
    stdlog.txt.zip   141K 1 version
    zip
    error log.txt.zip   2K 1 version
    zip
    pdm_migrate.txt.zip   5K 1 version


  • 2.  Re: Migration Fail error231

    Posted 10-27-2017 04:14 PM

    Hey Aamir,

     

    Can you hit us up with the c:\stdout.txt  file  before you close out the above?  Another one could be the NX_ROOT/log/migrat**  logs.

     

    _R



  • 3.  Re: Migration Fail error231

    Posted 10-27-2017 04:31 PM

    Hello Raghu

     

    Thanks for your quick response

    How can i attach logs here ?.. idont find any option to attach the file... :s



  • 4.  Re: Migration Fail error231

    Posted 10-27-2017 04:33 PM

    Raghu i just attached those 2 files to my post. Please check



  • 5.  Re: Migration Fail error231

    Posted 10-27-2017 04:43 PM

    It seems like SDM did not start in DBADMIN mode for whatever reason, and that's why it failed.

     

    One last item maybe... before we go the route of getting a support case for this.

     

    Upload the latest std logs / checkdb.log  from NX_ROOT/log    Maybe that'll give some clues

     

    Thx

    _R



  • 6.  Re: Migration Fail error231

    Posted 10-27-2017 04:58 PM

    Raghu i have attached stdlog and errorlog file(from db server) & there is checkdb.log file

     

    PLease check



  • 7.  Re: Migration Fail error231

    Posted 10-27-2017 05:14 PM

    Check  c:\windows\paradigm.in file.

     

    it should be some thing like this  (in your case e:/... )

     

    [PARADIGM]
    NX_ROOT=C:/PROGRA~2/CA/SERVIC~1
    NX_LOCAL=C:/PROGRA~2/CA/SERVIC~1

    NX_OS_TYPE=WINNT
    [Product]
    type=CA Service Desk Manager
    version=14.1.0.111

     

    I think you have it set as:   E:\Program Files (x86)\CA\SERVIC~1   in the above file.  Can you confirm?

     

    The reason why i say it is this in the stdlogs : 

     

    10/27 14:21:03.86 gbb-casdmdev-0 pdm_d_mgr 1340 EXIT mgr_os_if.c 2458 : Could not execute command: E:\Program Files (x86)\CA\SERVIC~1\bin\pdm_d_mgr.exe -w -m E:\Program Files (x86)\CA\SERVIC~1\site\r17_0_pdm_startup.dat error: 193
    10/27 14:21:20.65 gbb-casdmdev-0 pdm_d_mgr 1552 EXIT mgr_os_if.c 2458 : Could not execute command: E:\Program Files (x86)\CA\SERVIC~1\bin\pdm_d_mgr.exe -w -c -s DBADMIN error: 193
    10/27 14:21:23.99 gbb-casdmdev-0 pdm_perl 1668 SIGNIFICANT migrate_common.pm 205 ERROR: Problem starting services.
    10/27 14:21:23.99 gbb-casdmdev-0 pdm_perl 1668 SIGNIFICANT migrate_common.pm 205 Check the migration log file in $NX_ROOT\log, and the mdb install log in $NX_ROOT\temp for errors. Correct the errors and restart this process.

     

     

    Thx

    _R



  • 8.  Re: Migration Fail error231

    Posted 10-27-2017 05:22 PM

    Hi Raghu

     

    i checked this.

     

    its already E drive set 

     



  • 9.  Re: Migration Fail error231

    Posted 10-30-2017 08:40 AM

    Hello Raghu.Rudraraju

     

    we already opened a case on this issue. No one responded yet

     

    Please note case # 00878329 .

     

    Thanks



  • 10.  Re: Migration Fail error231

    Posted 10-31-2017 12:51 PM

    I took the case and did respond. I was waiting on a response from you. I made suggestions and asked you to carry out tasks: 

     

     

    Created By: Kaveek Jimmy (2017/10/29 4:48 PM)
    Hi Ayodeji 

     

    Thank you for contacting CA Support. I have taken ownership of this issue and will be assisting you find a solution for this issue. 

     

    Regards, 
    Kaveek



  • 11.  Re: Migration Fail error231

    Posted 10-30-2017 09:14 AM

    Hi Aamir,

     

    You need to set your paradigm.ini file to have the complete short name for the service desk directory:

     

    For Example:

     

    [PARADIGM]
    NX_ROOT=E:/PROGRA~2/CA/SERVIC~1
    NX_LOCAL=E:/PROGRA~2/CA/SERVIC~1
    NX_OS_TYPE=WINNT
    [Product]
    type=CA Service Desk Manager
    version=14.1.0.111


    NOTE: if you have ONLY the "Program Files (x86)" and not "Program Files" in the E drive, then the short name for "Program Files (x86)" might be "PROGRA~1"

     

    Navigate to E:\   then run "dir /x" and it will show you the short name for all directories... see if its PROGRA~1 or PROGRA~2.

     

    Then re-run pdm_configure.

     

    I also updated jimka01 who owns your case so he has the same info.

     

    Hope this helps, let us know.

    Jon I.



  • 12.  Re: Migration Fail error231

    Posted 10-30-2017 04:58 PM

    As a note, the 17.0 documentation specifies that 8.3 notation (8dot3) is required for SDM installations:

     

    CA SDM Deployment Planning Considerations - CA Service Management - 17.0 - CA Technologies Documentation 



  • 13.  Re: Migration Fail error231

    Posted 10-31-2017 08:38 AM

    Thanks David-Ng!

    @La-Qa - Were you able to make that change and try to run configure again?



  • 14.  Re: Migration Fail error231

    Posted 10-31-2017 11:33 AM

    hi jon

     

    thanks for ur usual support

     

    I tried this but not helped.

     

    On 31-Oct-2017 5:38 pm, "Jon Israel" <communityadmin@communities-mail.ca.com>



  • 15.  Re: Migration Fail error231

    Posted 10-31-2017 11:42 AM


  • 16.  Re: Migration Fail error231

    Posted 10-31-2017 12:30 PM

    Thanks Paul - I believe that Aamir had tried that already as David had posted that earlier. 

    @Aamir - are you sure that 8dot3 was turned on BEFORE SDM was installed and not after?   If it was turned on after, then a complete uninstall and reinstall of the product would be required. 

    8dot3 not being on to start with prior to the original installation would definitely cause this problem to occur and is really the only likely cause here.

    I would recommend at this point that you open a CA Support Case for this so that an engineer can dig into it further with you.

    Thanks!

    Jon I.



  • 17.  Re: Migration Fail error231
    Best Answer

    Posted 10-31-2017 12:33 PM

    Jon_Israel - there is already a CA Support ticket open (#00878329)



  • 18.  Re: Migration Fail error231

    Posted 10-31-2017 12:35 PM

    Thanks Paul_Coccimiglio!  

    @Aamir - please continue to work on the Support Case for this one, and we will make sure the solution is posted here as well.



  • 19.  Re: Migration Fail error231

    Posted 10-31-2017 12:35 PM

    hello Jon

     

    yes offcourse i enabled 8dot3 before sdm installatiom for sure. and i

    already opened a case for this issue but no help so far

     

    i already shared case number in my previous message

     

    Thanks

     

    On 31-Oct-2017 9:30 pm, "Jon_Israel" <communityadmin@communities-mail.ca.com>



  • 20.  Re: Migration Fail error231

    Posted 10-31-2017 12:38 PM

    Thanks Aamir - I am reaching out to the engineer who owns the case.



  • 21.  Re: Migration Fail error231

    Posted 10-31-2017 12:39 PM

    thanks Jon

     

    On 31-Oct-2017 9:38 pm, "Jon_Israel" <communityadmin@communities-mail.ca.com>



  • 22.  Re: Migration Fail error231

    Posted 10-31-2017 12:39 PM

    Aamir - please update the case if you have done what Kaveek provided, and advise that it didnt work if thats what you found.

    Thanks,

    Jon



  • 23.  Re: Migration Fail error231

    Posted 10-31-2017 12:54 PM

    I do not understand why you keep insisting no help is been offered when you are not responding on the ticket:

     

    Created By: Kaveek Jimmy (2017/10/31 10:52 AM)
    Hi Ayodeji 

     

    Kindly confirm if you have followed the instructions as show below: 

     

    You need to set your paradigm.ini file to have the complete short name for the service desk directory: 

     

    For Example: 

     

    [PARADIGM] 
    NX_ROOT=E:/PROGRA~2/CA/SERVIC~1 
    NX_LOCAL=E:/PROGRA~2/CA/SERVIC~1 
    NX_OS_TYPE=WINNT 
    [Product] 
    type=CA Service Desk Manager 
    version=14.1.0.111 

     

    NOTE: if you have ONLY the "Program Files (x86)" and not "Program Files" in the E drive, then the short name for "Program Files (x86)" might be "PROGRA~1" 

     

    Navigate to E:\ then run "dir /x" and it will show you the short name for all directories... see if its PROGRA~1 or PROGRA~2. 

     

    Then re-run pdm_configure. 

     

    In addition to the notes about 8.3 notation (8dot3) is required for SDM installations: 

     

    https://docops.ca.com/ca-service-management/17-0/en/implementing/implement-ca-service-management-17-0/planning-for-ca-service-management-17-0-installation/planning-for-ca-service-desk-manager-implementation/ca-sdm-deployment-planning-considerations 

     

    Regards, 
    Kaveek



  • 24.  Re: Migration Fail error231

    Posted 10-31-2017 01:11 PM

    Hello Jimka

    Sorry for the words but I just changed nx root and nx local to PROGR~2 as

    it was previously Program Files (x86) and save the file and re run

    setup..migration is now successful..

     

    many thanks.

     

    On 31-Oct-2017 9:54 pm, "jimka01" <communityadmin@communities-mail.ca.com>



  • 25.  Re: Migration Fail error231

    Posted 10-31-2017 01:18 PM

    That is fantastic new Aamir!

     

    Please ensure that the CA Support ticket is updated accordingly.