"Error sending to server ID_01 of type requirement" during test case upload in RQM.

Hi,

We are trying to upload test cases in RQM using the RQM Excel Importer and we always encounter the error mentioned above. Kindly help us in understanding what is causing the error.

Below are the log entries containing the error.

3/16/2015 4:43:26 PM:
--------------------------------------------------------------------------------
3/16/2015 4:43:26 PM:
SESSION: 3/16/2015 4:43:26 PM

3/16/2015 4:43:26 PM: Getting artifacts from current document outgoing FT.xlsx
3/16/2015 4:43:27 PM: Created 21 artifacts, sending to server
3/16/2015 4:43:27 PM: sending requirement0 named INF0079,_______INF081,__INF084,__DFDCBC121,_______INF147,______INF0148
3/16/2015 4:43:27 PM: Error sending to server INF0079,_______INF081,__INF084,__DFDCBC121,_______INF147,______INF0148 of type requirement
3/16/2015 4:43:27 PM: sending requirement1 named INF0079,_______INF081,__INF084,__DFDCBC121,_______INF147,______INF0148
3/16/2015 4:43:27 PM: Error sending to server INF0079,_______INF081,__INF084,__DFDCBC121,_______INF147,______INF0148 of type requirement
3/16/2015 4:43:27 PM: sending requirement2 named INF0079,_______INF081,__INF084,__DFDCBC121,_______INF147,______INF0148
3/16/2015 4:43:27 PM: Error sending to server INF0079,_______INF081,__INF084,__DFDCBC121,_______INF147,______INF0148 of type requirement
3/16/2015 4:43:27 PM: sending requirement3 named INF0079,____INF080_______INF081,__INF084_,__DFDCBC121,_______INF147,______INF0148
3/16/2015 4:43:27 PM: Error sending to server INF0079,____INF080_______INF081,__INF084_,__DFDCBC121,_______INF147,______INF0148 of type requirement
3/16/2015 4:43:27 PM: sending requirement4 named INF0079,____INF0080,_____INF081,__INF084______DFDCBC121,_______INF147,______INF0148
3/16/2015 4:43:27 PM: Error sending to server INF0079,____INF0080,_____INF081,__INF084______DFDCBC121,_______INF147,______INF0148 of type requirement
3/16/2015 4:43:27 PM: sending requirement5 named INF0079,__________INF204,
3/16/2015 4:43:27 PM: Error sending to server INF0079,__________INF204, of type requirement
3/16/2015 4:43:27 PM: sending requirement6 named INF0079,_______INF081,__INF084______,__DFDCBC121,_______INF147,______INF0148
3/16/2015 4:43:27 PM: Error sending to server INF0079,_______INF081,__INF084______,__DFDCBC121,_______INF147,______INF0148 of type requirement
3/16/2015 4:43:27 PM: sending testscript7 named TRD_FT_INC_TC002
3/16/2015 4:43:28 PM: Server returned code OK
3/16/2015 4:43:28 PM: sending testscript8 named TRD_FT_INC_TC002
3/16/2015 4:43:28 PM: Server returned code OK
3/16/2015 4:43:28 PM: sending testscript9 named TRD_FT_INC_TC002
3/16/2015 4:43:28 PM: Server returned code OK
3/16/2015 4:43:28 PM: sending testscript10 named TRD_FT_INC_TC002
3/16/2015 4:43:28 PM: Server returned code OK
3/16/2015 4:43:28 PM: sending testscript11 named TRD_FT_INC_TC002
3/16/2015 4:43:28 PM: Server returned code OK
3/16/2015 4:43:28 PM: sending testscript12 named TRD_FT_INC_TC002
3/16/2015 4:43:28 PM: Server returned code OK
3/16/2015 4:43:28 PM: sending testscript13 named TRD_FT_INC_TC002
3/16/2015 4:43:29 PM: Server returned code OK
3/16/2015 4:43:29 PM: sending testcase14 named TRD_FT_INC_TC002
3/16/2015 4:43:29 PM: Server returned code Created
3/16/2015 4:43:29 PM: sending testcase15 named TRD_FT_INC_TC002
3/16/2015 4:43:29 PM: Server returned code OK
3/16/2015 4:43:29 PM: sending testcase16 named TRD_FT_INC_TC002
3/16/2015 4:43:30 PM: Server returned code OK
3/16/2015 4:43:30 PM: sending testcase17 named TRD_FT_INC_TC002
3/16/2015 4:43:30 PM: Server returned code OK
3/16/2015 4:43:30 PM: sending testcase18 named TRD_FT_INC_TC002
3/16/2015 4:43:30 PM: Server returned code OK
3/16/2015 4:43:30 PM: sending testcase19 named TRD_FT_INC_TC002
3/16/2015 4:43:30 PM: Server returned code OK
3/16/2015 4:43:30 PM: sending testcase20 named TRD_FT_INC_TC002
3/16/2015 4:43:30 PM: Server returned code OK
3/16/2015 4:43:30 PM: finished writing artifacts

And here is the configuration that we are using.

// This configuration file creates a test case linking with test script attached to it. It has provision to link to existing requirements as well.All the test cases will be linking to the Test Suite mentioned in the test case document


requirement.XLSStartRow=5
requirement.XLSArtifactID=B
requirement.dc:title=B


testsuite.dc:title=B1
testsuite.dc:description=B2
//testsuite.testcases=testcase
testsuite.XLSLink=testcase
testsuite.XLSWorksheetID="Test Case"



// Start looking for scripts after row 5
testscript.XLSStartRow=5

// use the data in the first row of a found script's column B
testscript.XLSArtifactID=C
testscript.dc:title=E
testscript.dc:description=F


// the literal "execution" will be put into the step type tag, so all steps will be of type execution
testscript.steps.type="execution"
testscript.steps.description=I
testscript.steps.title=E
testscript.steps.name=F
testscript.steps.expectedResult=J



// a new script starts when we encounter an empty row
testscript.XLSDelimeter=\n
testcase.ID=testscript.XLSArtifactID


// by refering to the testscript's field instead of the column that data comes from
// the tool will also create links to each of the test scripts.
testcase.XLSStartRow=5
testcase.dc:title=C
testcase.dc:description=D
testcase.dc.priority=T
testcase.Section("myns:com.ibm.rqm.planning.editor.section.testCasePreCondition","RQM-KEY-TC-PRE-COND-TITLE")=G