It's all about the answers!

Ask a question

RQM Excel importer error: of type testsuite The remote server returned an error: (500) Internal Server Error.


Neeta Valera (45128) | asked Jul 28 '16, 2:33 p.m.
edited Jul 28 '16, 2:51 p.m.
Hi,
When I export a bunch of excel test procedures to RQM, some of them import just fine but a few give this error:
of type testsuite
The remote server returned an error: (500) Internal Server Error.

I tried copying the data from that excel to a brand new blank excel file but still get the same error. I tried deleting the value in the cell and typing a new value but still gives the same error. Not sure what the issue is, why some import others don't.

I found that the procedures that fail to export are very big with over 1200 rows in the excel sheet. they have test suite and rest are all test cases.

Also, when the export is in progress it gives this message:
Message box:
"Unhandled exception has occurred in a component of your application.

Attempted to read or write protected memory."

Details:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
   at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   at System.Windows.Forms.NativeWindow.DefWndProc(Message& m)
   at System.Windows.Forms.Control.DefWndProc(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.TextBoxBase.WndProc(Message& m)
   at System.Windows.Forms.RichTextBox.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
RQMExcelImporter
    Assembly Version: 6.0.2.19868
    Win32 Version: 6.0.2.19868
    CodeBase: file:///C:/Program%20Files%20(x86)/IBM/RQMExcelImporter/RQMExcelImporter.dll
----------------------------------------
Extensibility
    Assembly Version: 7.0.3300.0
    Win32 Version: 7.00.9466
    CodeBase: file:///C:/WINDOWS/assembly/GAC/Extensibility/7.0.3300.0__b03f5f7f11d50a3a/Extensibility.dll
----------------------------------------
Mso2Rqm_Common
    Assembly Version: 6.0.2.19867
    Win32 Version: 6.0.2.*
    CodeBase: file:///C:/Program%20Files%20(x86)/IBM/RQMExcelImporter/Mso2Rqm_Common.DLL
----------------------------------------
Microsoft.Office.Interop.Excel
    Assembly Version: 15.0.0.0
    Win32 Version: 15.0.4569.1506
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.Office.Interop.Excel/15.0.0.0__71e9bce111e9429c/Microsoft.Office.Interop.Excel.dll
----------------------------------------
office
    Assembly Version: 15.0.0.0
    Win32 Version: 15.0.4823.1000
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/office/15.0.0.0__71e9bce111e9429c/office.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8686 (QFE.050727-8600)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5491 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5495 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5494 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Web
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5491 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Web/2.0.0.0__b03f5f7f11d50a3a/System.Web.dll
----------------------------------------
CustomMarshalers
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_32/CustomMarshalers/2.0.0.0__b03f5f7f11d50a3a/CustomMarshalers.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.




Thanks
Neeta

One answer



permanent link
James Chapman (256) | answered Jul 28 '16, 6:59 p.m.
Hi Neeta,
I have often found this error to be down to one of the following causes:
1. If you are trying to perform an update, the artefact you are attempting to update might be  in an 'Approved' state, typically this prevents any changes being made to the artefact.
2. There are missing mandatory values 
3. If you have selected the option in the 'Manage this project area' screen to ensure unique artefact names, there could be another artefact  already in existence that has the same value in its summary field as the one you are trying to import.

Hope this helps.

Comments
Neeta Valera commented Aug 02 '16, 11:20 a.m.

Thank you for the reply. I checked all three causes you have listed. Not an update, all mandatory values are there and not enforcing name uniqueness.

I did try something is to reduce the size of the file and it worked just fine. So not sure its a bug or a memory issue. If the test suite has about 1000 test cases, it says it created all of the 1000 test casesĀ and fails on the very very last step when it tries to create the test suite.

Your answer


Register or to post your answer.