

You might experience the following error from the RQM Excel Importer utility while involving Requirement artifacts:
Use the following samples shipped along with the Excel Import Utility:
"C:\Program Files (x86)\IBM\RQMExcelImporter\Samples-Excel\Requirements 001.cfg"
"C:\Program Files (x86)\IBM\RQMExcelImporter\Samples-Excel\Requirements 001.xls"
"C:\Program Files (x86)\IBM\RQMExcelImporter\Samples-Excel\TestPlan with TestCases 001 linked to requirement 001.cfg"
"C:\Program Files (x86)\IBM\RQMExcelImporter\Samples-Excel\TestPlan with TestCases 001 linked to requirement 001.xls"
You will end up with the error as follows reflected from the Utility:
3/9/2016 3:28:44 PM: Getting artifacts from current document Requirements 001.xls
3/9/2016 3:28:44 PM: Created 5 artifacts, sending to server
3/9/2016 3:28:44 PM: sending requirement0 named ID.04
3/9/2016 3:28:44 PM: Error sending to server ID.04 of type requirement
3/9/2016 3:28:44 PM: sending requirement1 named ID.05
3/9/2016 3:28:45 PM: Error sending to server ID.05 of type requirement
3/9/2016 3:28:45 PM: sending requirement2 named ID.03
3/9/2016 3:28:45 PM: Error sending to server ID.03 of type requirement
3/9/2016 3:28:45 PM: sending requirement3 named ID.01
3/9/2016 3:28:45 PM: Error sending to server ID.01 of type requirement
3/9/2016 3:28:45 PM: sending requirement4 named ID.02
3/9/2016 3:28:45 PM: Error sending to server ID.02 of type requirement
3/9/2016 3:28:45 PM: finished writing artifacts


Further, when you drill the debug log for more troubleshooting, you should see the following :
“C:\Users\<user> \AppData\Roaming\Mso2Rqm\Mso2Rqm_Debug.log”
************************************* START Mso2Rqm\Mso2Rqm_Debug ****************
3/10/2016 10:24:53 AM: Getting artifacts from current document Requirements 001.xls
3/10/2016 10:24:53 AM: Created 5 artifacts, sending to server
3/10/2016 10:24:53 AM: INFO: <Unknown Caller Context>: ExportRepositoryDialog.reqUrl : System.Collections.Hashtable
3/10/2016 10:24:53 AM: sending requirement0 named ID.04
3/10/2016 10:24:53 AM: ERROR: <Unknown Caller Context>: RMConnector: PutReqToServer - Error putting resource: https://clmweb.ibm.com:9443/rm/requirementFactory?projectURL=https%3A%2F%2Fclmweb.ibm.com%3A9443%2Frm%2Fprocess%2Fproject-areas%2F_I47u0PMGEeOzOMU71X7Rag
3/10/2016 10:24:53 AM: ERROR: <Unknown Caller Context>: The remote server returned an error: (403) Forbidden.
3/10/2016 10:24:53 AM: EXCEPTION: : The remote server returned an error: (403) Forbidden.
3/10/2016 10:24:53 AM: at System.Net.HttpWebRequest.GetResponse() at Mso2Rqm_Common.RMConnector.PutReqToServer(String url, String postData)
3/10/2016 10:24:53 AM: ERROR: <Unknown Caller Context>: <rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:err="http://jazz.net/xmlns/prod/jazz/foundation/1.0/">
<rdf:Description>
<err:detailedMessage rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>CRRRS6404E The OSLC request could not be completed because the request is missing this required property: instanceShape.</err:detailedMessage>
<err:errorMessage rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
>Forbidden</err:errorMessage>
<err:errorStatus rdf:datatype="http://www.w3.org/2001/XMLSchema#long"
>403</err:errorStatus>
</rdf:Description>
</rdf:RDF>
3/10/2016 10:24:53 AM: Error sending to server ID.04 of type requirement
3/10/2016 10:24:53 AM: ERROR: <Unknown Caller Context>: ExcelExportRepositoryDialog: Error saving to url https://clmweb.ibm.com:9443/qm of type requirement
3/10/2016 10:24:53 AM: EXCEPTION: : Object reference not set to an instance of an object.
3/10/2016 10:24:53 AM: at RQMExcelExporter.ExcelExportRepositoryDialog.doExport(IList`1 artifacts)
************************************* START Mso2Rqm\Mso2Rqm_Debug ****************
Lets analyze this problem further:
The issue primarily is due to the following tag used in the CFG file:

requirement.resourceShape="Requirement"
If you look at the Requirements artifact type from RRC/RNDG, you will see that there are no artifact type called “requirements” , and this is the sole reason for the above error.

Here you can notice that the CFG file mentions the artifact type as “Requirement” where as the existing artifact is “Use case requirement”.
Here's how you can solve this!
To resolve this you need to mention the CFG file tag as follows as existing from the RM Project Area.
requirement.resourceShape="Use Case Requirement"
OR
requirement.resourceShape="Feature"
OR
requirement.resourceShape="Actor"
and So on…