Facing error message in deployment of rtc plugin at rtc server instance 5.
Hi,
I am trying to deploy one RTC plugin at RTC instance version 5. This plugin is working fine at my local. But in deployment of this plugin at RTC server I am getting following error -
I am trying to deploy one RTC plugin at RTC instance version 5. This plugin is working fine at my local. But in deployment of this plugin at RTC server I am getting following error -
ERROR eam.repository.provision.internal.ProvisionService - CRJAZ0288E The profile device "net.atos.ssc.copy.linked.attibutes.server.feature" could not be installed from the update site "file: Ccm / sites / copy_linked_attribute-update-site "because it is referenced in the" d: \ PROGRA ~ 1 \ IBM \ JAZZTE ~ 1 \ server \ conf \ rtc5b \ provision_profiles \ copy_linked_attribute-update-site.ini "profile file.
I have created the deployable as mentioned in IBM Rational Team Concert4.X Extensibilty pdf.
2 answers
The error message looked same as the post https://jazz.net/forum/questions/221643/rtc-601-ccm-goes-offline-after-plugin-deployment.
You may debug the issue following the comments posted by Donald Nong.
This is a typical deployment error. Without more information about the features content and the provision profile ini file there is nothing we can do.
One thing I notice is " d: \ PROGRA ~ 1 \ IBM \ JAZZTE ~ 1 \ server \ conf \ rtc5b \ provision_profiles \ copy_linked_attribute-update-site.ini "profile file
1. You should never ever ever install jazz servers inside the Program Files folder - there are issues as that folder is managed and you will always "run as administrator".
2. I have never seen an absolute path in an error message like this as would not expect to see one. Check the provision profile.
One thing I notice is " d: \ PROGRA ~ 1 \ IBM \ JAZZTE ~ 1 \ server \ conf \ rtc5b \ provision_profiles \ copy_linked_attribute-update-site.ini "profile file
1. You should never ever ever install jazz servers inside the Program Files folder - there are issues as that folder is managed and you will always "run as administrator".
2. I have never seen an absolute path in an error message like this as would not expect to see one. Check the provision profile.