Cannot create test scripts on RQM 6.0.2

Hi, Prussian

1. Do you see all those messages when saving test scripts?
2. whether any test script save will end up with same errors?
3. whether test script summary is over 250 characters?
4. is it happening in any browser?
5. what is the output
https://server:port/qm_context_root/resource/itemOid/com.ibm.rqm.planning.ExecutionElement2/_0SN-MH5LEeaigvKWNLaMyQ
from a web browser?
(server:port and qm_context_root should be matching to your environment)

1. Yes, I see those message mostly in every single test script that I have saved. FYI, The messages is same, but they have different unique itemID for each of the test script
   
   
   1. Some of them is successfully saved, but when I edited it, it returns with error.
   
   
2. Test summary is blank
   
   
3. Yes, I have tried in Firefox 48.0.2 and Chrome 11.0
   
   
   5. 
    ---- start of line-----
   {"errorClass":"com.ibm.team.repository.service.internal.vvc.UnsetConfigurationException","errorCode":500,"errorTraceMarshall"
   .....
   
   "errorMessage":"CRJAZ0931I Error redirecting to web from location \"https:\/\/qacictd.btn.co.id:9443\/qm\/service\/com.ibm.team.repository.service.internal.ItemRenderService\/itemOid\/com.ibm.rqm.planning.ExecutionElement2\/_0SN-MH5LEeaigvKWNLaMyQ\". Exception message: Attempt to fetch config aware type with no configuration set"}
   ----- end of line ------

I can't tell from the error "Attempt to fetch config aware type with no configuration set"
 if there is anything to do configuration management. If this is a configuration enabled project, you may check with other project and see if you see similar problem.

I don't find any reported problem in v602 which has the same errors in this post. In a general approach, you may try to apply ifix on v602 first and see how it works.

Obviously if ifix does not help, further trace is required to find out more, if you know how to use firebug, you can reproduce the issue and see if the firebug can reveal anything more. if you can contact support, there is some further trace they can enable for qm.log for investigation.

Donal, the condition is like below:

I don't see the link between the error and RS staying at 6.0.1. You can upgrade RS now as I understand because JTS is now at 6.0.2.