Purpose (problem description)

The page helps you resolve the error - "Invalid Connection profile name "<NAME OF THE CONNECTION PROFILE>" when trying to run analysis or delete a version from AIP Console -

Observed in CAST Version


Release

Yes/No

1.1x.y(tick)
Observed in RDBMS

RDBMS

Yes/No

Oracle Server(error)
Microsoft SQL Server(error)
CSS3(tick)
CSS2(tick)
Step by Step scenario
  1. Create packages in AIP Console
  2. Initiate the Analysis or Try to Delete the version. 

Error stack is shown below

NF: 2019-06-20 17:14:32: Using arguments:
                            deleteVersion
                            -temporaryPath: C:\ProgramData\CAST\CAST\CASTMS
                            -version: Version-2019-06-20-2
                            -logRootPath: C:\ProgramData\CAST\CAST\Logs
                            -appli: MS_Drone_AIPConsole
                            -workingPath: C:\ProgramData\CAST\CAST\CASTMS
                            -connectionProfile: test_mngt on CastStorageService _ test:2282
                            -logFilePath: E:\AIP_Console\AipNode\data\logs\external_logs\test_AIPConsole-delete_version-20190620-171431.txt
INF: 2019-06-20 17:14:32: Log file : E:\AIP_Console\AipNode\data\logs\external_logs\test_AIPConsole-delete_version-20190620-171431.txt
INF: 2019-06-20 17:14:32: Loading ini file: E:\Program Files\Cast\8.3\CastGlobalSettings.ini
ERR: 2019-06-20 17:14:33: Invalid Connection profile name "test_mngt on CastStorageService _ test3:2282"
                            com.castsoftware.java.ExternalException:Invalid Connection profile name "test_mngt on CastStorageService _ test:2282"
                              com.castsoftware.pmc.run.CLIPMCConfiguredApplication.buildConnection(CLIPMCConfiguredApplication.java:171)
                              com.castsoftware.pmc.run.PMCConfiguredApplication.onTreatment(PMCConfiguredApplication.java:422)
                              com.castsoftware.pmc.run.CLIPMCConfiguredApplication.onTreatment(CLIPMCConfiguredApplication.java:185)
                              com.castsoftware.mda.run.ConfiguredApplication$2.call(ConfiguredApplication.java:244)
                              com.castsoftware.mda.run.ConfiguredApplication$2.call(ConfiguredApplication.java:234)
                              com.castsoftware.util.logger.Logging.execute(Logging.java:527)
                              com.castsoftware.util.logger.Logging.runInNewContext(Logging.java:415)
                              com.castsoftware.mda.run.ConfiguredApplication.run(ConfiguredApplication.java:233)
                              com.castsoftware.pmc.run.CLIPMCConfiguredApplication.executeInLogContext(CLIPMCConfiguredApplication.java:107)
                              com.castsoftware.pmc.run.CLIPMCConfiguredApplication$1.call(CLIPMCConfiguredApplication.java:73)
                              com.castsoftware.pmc.run.CLIPMCConfiguredApplication$1.call(CLIPMCConfiguredApplication.java:68)
                              com.castsoftware.util.logger.Logging.execute(Logging.java:527)
                              com.castsoftware.util.logger.Logging.runInNewContext(Logging.java:415)
                              com.castsoftware.pmc.run.CLIPMCConfiguredApplication.execute(CLIPMCConfiguredApplication.java:67)
                              com.castsoftware.pmc.CLI.main(CLI.java:34)
INF: 2019-06-20 17:14:33: Return value: 1000
Action Plan

The issue is usually coming when the NODE and the CONSOLE are launched as Windows services. The user that runs the service is not the same than the one that has opened AIP Console.

To solve the issue, perform the below actions 

  1. Modify the CastGlobalSettings.ini file in the Cast Installation Folder as shown below - 

    (XXX being your Trigram/Windows login Name)   

    ; Set current user's path
    CAST_CURRENT_USER_WORK_PATH=C:\Users\XXX\AppData\Roaming\CAST\CAST\$CAST_MAJOR_VERSION$.$CAST_MINOR_VERSION$\
    ; Set current user's temporary path
    CAST_CURRENT_USER_TEMP_PATH=C:\Users\XXX\AppData\Local\Temp\CAST\CAST\$CAST_MAJOR_VERSION$.$CAST_MINOR_VERSION$\
  2. In the Windows services, edit the AIP Console services properties :
    1. Stop the AIP-node and AIP-console services.
    2. Edit the properties : Right click on the services and select properties
    3. In the Log on tab, Log on as "This account" must be selected, and define your user and password (same XXX user) as below screenshot:

  3. Restart both Console and Node Services. 
  4. If the above steps do not solve your issue contact CAST Technical Support. with the following Relevant input for CAST Technical Support to carry out further investigation.        

 

Relevant input

Notes/comments

Ticket #18366

Related Pages