Highlighted
Valued Contributor.. Valued Contributor..
Valued Contributor..
162 views

Error reading data by Connect-IT connector.

Hello,

I would to use ServiceCenter/Service Manager connector in Connect-It to read data (produce documents) from SM. I'm facing the problem when the connector produce certain count of documents, it finished with following error:

null[<SOAP-ENV:Fault> <faultcode>SOAP-ENV:Server</faultcode> <faultstring>A CXmlApiException was raised in native code : error 15 : scxmlapi(15) - Invalid file handle provided on recordset SOAP request - dbdict5eef28b7001a904c80241848</faultstring> <faultactor>Server</faultactor> </SOAP-ENV:Fault>

 

Here are all lines from CIT log regarding this error:

2020/06/21 10:43:45.875 0 16 [(entitiesDst) entities] Consumed document ID 'entitiesDst', document name 'entities'.
2020/06/21 10:43:45.882 0 16 Request=<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<SOAP-ENV:Envelope xmlns:SOAP-ENV=\"http://schemas.xmlsoap.org/soap/envelope/\"><SOAP-ENV:Header/><SOAP-ENV:Body><recordset count=\"100\" filehandle=\"device5eef19c50009a2e5811ed740\" operation=\"list\" start=\"500\" total=\"1\"/></SOAP-ENV:Body></SOAP-ENV:Envelope>
2020/06/21 10:43:45.980 0 16 The response code value is 500: <recordset count=\"100\" filehandle=\"device5eef19c50009a2e5811ed740\"\n    operation=\"list\" start=\"500\" total=\"1\"/>\n
2020/06/21 10:43:46.120 0 16 Response=<loginResponse attachmentCompressed=\"false\" loginRC=\"0\" xmlns=\"http://servicecenter.peregrine.com/PWS\"/>\n
2020/06/21 10:43:46.204 0 1 (0) null[<SOAP-ENV:Fault>\n    <faultcode>SOAP-ENV:Server</faultcode>\n    <faultstring>A CXmlApiException was raised in native code : error 15 : scxmlapi(15) - Invalid file handle provided on recordset SOAP request - device5eef19c50009a2e5811ed740</faultstring>\n    <faultactor>Server</faultactor>\n</SOAP-ENV:Fault>\n]
2020/06/21 10:43:46.286 0 16 Request=<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<SOAP-ENV:Envelope xmlns:SOAP-ENV=\"http://schemas.xmlsoap.org/soap/envelope/\"><SOAP-ENV:Header/><SOAP-ENV:Body><recordset filehandle=\"device5eef19c50009a2e5811ed740\" operation=\"close\"/></SOAP-ENV:Body></SOAP-ENV:Envelope>
2020/06/21 10:43:46.378 0 16 The response code value is 500: <recordset filehandle=\"device5eef19c50009a2e5811ed740\" operation=\"close\"/>\n
2020/06/21 10:43:46.544 0 16 Response=<loginResponse attachmentCompressed=\"false\" loginRC=\"0\" xmlns=\"http://servicecenter.peregrine.com/PWS\"/>\n
2020/06/21 10:43:46.625 0 2 null[<SOAP-ENV:Fault>\n    <faultcode>SOAP-ENV:Server</faultcode>\n    <faultstring>A CXmlApiException was raised in native code : error 15 : scxmlapi(15) - Invalid file handle provided on recordset SOAP request - device5eef19c50009a2e5811ed740</faultstring>\n    <faultactor>Server</faultactor>\n</SOAP-ENV:Fault>\n]
2020/06/21 10:43:46.705 0 4 Retry the action ...
2020/06/21 10:43:46.775 0 16 The response code value is 500: <recordset filehandle=\"device5eef19c50009a2e5811ed740\" operation=\"close\"/>\n
2020/06/21 10:43:46.917 0 16 Response=<loginResponse attachmentCompressed=\"false\" loginRC=\"0\" xmlns=\"http://servicecenter.peregrine.com/PWS\"/>\n
2020/06/21 10:43:46.970 0 1 (0) null[<SOAP-ENV:Fault>\n    <faultcode>SOAP-ENV:Server</faultcode>\n    <faultstring>A CXmlApiException was raised in native code : error 15 : scxmlapi(15) - Invalid file handle provided on recordset SOAP request - device5eef19c50009a2e5811ed740</faultstring>\n    <faultactor>Server</faultactor>\n</SOAP-ENV:Fault>\n]
2020/06/21 10:43:47.041 0 1 (0) java.lang.Exception: null[<SOAP-ENV:Fault>\n    <faultcode>SOAP-ENV:Server</faultcode>\n    <faultstring>A CXmlApiException was raised in native code : error 15 : scxmlapi(15) - Invalid file handle provided on recordset SOAP request - device5eef19c50009a2e5811ed740</faultstring>\n    <faultactor>Server</faultactor>\n</SOAP-ENV:Fault>\n]
2020/06/21 10:43:47.105 1 16 at com.hp.ov.cit.connector.smc.SMClient.closeQuery (SMClient.java:638)
2020/06/21 10:43:47.147 1 16 at com.hp.ov.cit.connector.smc.SMRecordSet.close (SMRecordSet.java:146)
2020/06/21 10:43:47.198 1 16 at com.hp.ov.cit.connector.smc.recordset.SmcRecordsetProxy.close (SmcRecordsetProxy.java:48)
 
There is also difference in count of documents, that depends on what connector is consuming it. For example if I use Delimited text connector to write data to text file, error occures after 3100 produced documents. When I use Management as a Service connector to write data directly to SMAX, error occures every time after 500 produced documents.
 
Is there any limit parameteres that must be changed in ConnectIt or why could exactly this counts raise the error?
 
Thanks for any help 
0 Likes
12 Replies
Highlighted
Micro Focus Contributor
Micro Focus Contributor

Re: Error reading data by Connect-IT connector.

Hello Cavoki1,

   On the SM / SC connector, the scxmlapi error are usually coming from the SM server, instead of the CIT engine. I would trace the SM side and see if there is any limitation on the time (timeout for the socket or session) that is preventing the records to be returned completdly. Also, if you are retrieving devices, I would reccomend to use the WS API, using the join* extacces records instead of the DB direct connection since devices are joined tables between 2 or more, and using the legacy method will only bring data incomplete. 

   As for the SMAX side, the 500 limit sounds to be a limit on the API settings. 

   In CIT, the only way to limit records is by the test production setting, but it will not error out, it will simply stop at the configured limit which I don't see its the case. 

Regards,  

Highlighted
Valued Contributor.. Valued Contributor..
Valued Contributor..

Re: Error reading data by Connect-IT connector.

Hello,

we tried trace it on SM side, but there is same error message without any other entry that could identify root cause of problem. I opened service request with MF, so will post solution here if they will resolve it.

Regards

Ivan

Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: Error reading data by Connect-IT connector.

It may also be related to  user permissions on SMAX side.

Would it be possible to post the CIT  scn file? (remove sensitive data).

 

0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: Error reading data by Connect-IT connector.

Never experienced it. Are you connecting to a dedicate port?
Share the SM logs as well.
Regards,
Breno Abreu

If you feel this was helpful please click the KUDOS! thumb below!
0 Likes
Highlighted
Valued Contributor.. Valued Contributor..
Valued Contributor..

Re: Error reading data by Connect-IT connector.

Hello,

this is the part of SM logs from the time when error occurred:

 

3628( 8068) 06/24/2020 11:04:10 RTE I Using "utalloc" memory manager, mode [0]
3628( 8068) 06/24/2020 11:04:10 RTE I Process sm 9.63.0006 () System: 13091 (0x784DFB00) on PC (x64 64-bit) running Windows (6.2 Build 9200) Timezone GMT+01:00 daylight Locale cs_CZ from SAPLAB330
3628( 8068) 06/24/2020 11:04:10 RTE I Host network address: 10.6.230.162
3628( 8068) 06/24/2020 11:04:10 RTE I Thread attaching to resources with key 0x784DFB00
3628( 1512) 06/24/2020 11:04:10 RTE I Undisplayed message:Your last successful login was on 24/06/20 10:59:44
3628( 1512) 06/24/2020 11:04:10 RTE I Thread termination cleanup complete. Thread was active for 0 days,00:00:23. Threads remaining: 1 of 50
3628( 8068) 06/24/2020 11:04:11 RTE I Info: SQL State: 01000-5701 Message: [Microsoft][ODBC SQL Server Driver][SQL Server]Changed database context to 'smtest'.
3628( 8068) 06/24/2020 11:04:11 RTE I Info: SQL State: 01000-5703 Message: [Microsoft][ODBC SQL Server Driver][SQL Server]Changed language setting to us_english.
3628( 8068) 06/24/2020 11:04:11 RTE I API=SQLConnect
3628( 8068) 06/24/2020 11:04:11 RTE I Connection established to dbtype 'sqlserver' database 'SM32_SAPLAB389' user 'smtest_user'
3628( 8068) 06/24/2020 11:04:11 RTE I Connected to Data source 'SM32_SAPLAB389' SQL server 'SAPLAB389\SMTEST16' version: 13.0.5698 through SQL driver version: 6.3.9600 using database 'smtest' as user 'smtest_user'
3628( 8068) 06/24/2020 11:04:11 RTE I MS SQL Server collation 'Czech_CI_AS', varchar codepage 1250, comparison 196609: case insensitive, accent sensitive
3628( 8068) 06/24/2020 11:04:11 RTE I Thread 089EC58E98BE2D5571A471C57717E9EF initialization done. Thread 2 of 50.
3628( 8068) 06/24/2020 11:04:11 RTE I Total sessions since process began: 68
3628( 8068) 06/24/2020 11:04:11 JRTE I GUID=ecc30788-d7ff-4d6b-a12a-9a0faa340a0f
3628( 8068) 06/24/2020 11:04:11 RTE I User SM_CIT logged in. Already licensed
3628( 8068) 06/24/2020 11:04:11 RTE I User SM_CIT has logged in and is using a Named license ( 2 out of a maximum 20 )
3628( 8068) 06/24/2020 11:04:11 RAD I Your last successful login was on 24/06/20 11:03:47
3628( 8068) 06/24/2020 11:04:11 RTE I -Memory : S(4522240) O(745724) MAX(5267964) - MALLOC's Total(176597)
3628( 8068) 06/24/2020 11:04:11 RTE A Performance-7-$G.assignment, Globallist $G.assignment contains too many items! num=739 ; application(apm.global.initer), panel(start.loop)
3628( 8068) 06/24/2020 11:04:11 RTE I Base login Response: 0.281 -- RAD: 0.001 JS: 0.172 Log:0.000 Database: 0.108(00817) LDAP: 0.000 (CPU 0.202) application:login,cleanup
3628( 8068) 06/24/2020 11:04:11 RTE W Exception occurred for method recordset and XML request <?xml version="1.0" encoding="utf-8"?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header/><SOAP-ENV:Body><recordset count="100" filehandle="dbdict5ef316f40005c22c80f52f78" operation="list" start="200" total="1"/></SOAP-ENV:Body></SOAP-ENV:Envelope>
3628( 8068) 06/24/2020 11:04:11 RTE E Caught XML API exception scxmlapi(15) - Invalid file handle provided on recordset SOAP request - dbdict5ef316f40005c22c80f52f78
3628( 7132) 06/24/2020 11:04:11 JRTE W Send error response: A CXmlApiException was raised in native code : error 15 : scxmlapi(15) - Invalid file handle provided on recordset SOAP request - dbdict5ef316f40005c22c80f52f78
3628( 7116) 06/24/2020 11:04:11 JRTE I Creating new worker thread 37CCDA97BA3404DF401F9ED994488565 t@55
3628( 7796) 06/24/2020 11:04:11 RTE I Using "utalloc" memory manager, mode [0]
3628( 7796) 06/24/2020 11:04:11 RTE I Process sm 9.63.0006 () System: 13091 (0x784DFB00) on PC (x64 64-bit) running Windows (6.2 Build 9200) Timezone GMT+01:00 daylight Locale cs_CZ from SAPLAB330
3628( 7796) 06/24/2020 11:04:11 RTE I Host network address: 10.6.230.162
3628( 7796) 06/24/2020 11:04:11 RTE I Thread attaching to resources with key 0x784DFB00
3628( 7796) 06/24/2020 11:04:11 RTE I Info: SQL State: 01000-5701 Message: [Microsoft][ODBC SQL Server Driver][SQL Server]Changed database context to 'smtest'.
3628( 7796) 06/24/2020 11:04:11 RTE I Info: SQL State: 01000-5703 Message: [Microsoft][ODBC SQL Server Driver][SQL Server]Changed language setting to us_english.
3628( 7796) 06/24/2020 11:04:11 RTE I API=SQLConnect
3628( 7796) 06/24/2020 11:04:11 RTE I Connection established to dbtype 'sqlserver' database 'SM32_SAPLAB389' user 'smtest_user'
3628( 7796) 06/24/2020 11:04:11 RTE I Connected to Data source 'SM32_SAPLAB389' SQL server 'SAPLAB389\SMTEST16' version: 13.0.5698 through SQL driver version: 6.3.9600 using database 'smtest' as user 'smtest_user'
3628( 7796) 06/24/2020 11:04:11 RTE I MS SQL Server collation 'Czech_CI_AS', varchar codepage 1250, comparison 196609: case insensitive, accent sensitive
3628( 7796) 06/24/2020 11:04:11 RTE I Thread 37CCDA97BA3404DF401F9ED994488565 initialization done. Thread 3 of 50.
3628( 7796) 06/24/2020 11:04:11 RTE I Total sessions since process began: 69
3628( 7796) 06/24/2020 11:04:11 JRTE I GUID=bf406bac-2eeb-4a57-b6e4-0fb140e4812f
3628( 7796) 06/24/2020 11:04:11 RTE I User SM_CIT logged in. Already licensed
3628( 7796) 06/24/2020 11:04:11 RTE I User SM_CIT has logged in and is using a Named license ( 2 out of a maximum 20 )
3628( 7796) 06/24/2020 11:04:11 RAD I Your last successful login was on 24/06/20 11:04:11
3628( 8068) 06/24/2020 11:04:11 JRTE I Termination signal: 0
3628( 8068) 06/24/2020 11:04:11 RTE I -Memory : S(6043824) O(1473388) MAX(9143996) - MALLOC's Total(401385)
3628( 8068) 06/24/2020 11:04:11 RTE I Thread termination in progress
3628( 8068) 06/24/2020 11:04:11 RTE A SUMMARY-1 The following event has been reported 1 times in the last 0 minute(s)
3628( 8068) 06/24/2020 11:04:11 RTE A Performance-7-$G.assignment, Globallist $G.assignment contains too many items! num=739
3628( 8068) 06/24/2020 11:04:11 RTE I User SM_CIT has logged out. Still licensed ( 2 sessions remaining )
3628( 8068) 06/24/2020 11:04:11 RTE I Thread termination cleanup complete. Thread was active for 0 days,00:00:00. Threads remaining: 2 of 50
3628( 7796) 06/24/2020 11:04:11 RTE I -Memory : S(4522824) O(741044) MAX(5263868) - MALLOC's Total(176671)
3628( 7796) 06/24/2020 11:04:11 RTE A Performance-7-$G.assignment, Globallist $G.assignment contains too many items! num=739 ; application(apm.global.initer), panel(start.loop)
3628( 7796) 06/24/2020 11:04:11 RTE I Base login Response: 0.265 -- RAD: 0.000 JS: 0.155 Log:0.000 Database: 0.110(00822) LDAP: 0.000 (CPU 0.171) application:login,cleanup
3628( 7796) 06/24/2020 11:04:11 RTE I Stop request received from client
3628( 7796) 06/24/2020 11:04:11 JRTE I Termination signal: 0
3628( 7796) 06/24/2020 11:04:11 RTE I -Memory : S(2106928) O(2131820) MAX(9143996) - MALLOC's Total(400763)
3628( 7796) 06/24/2020 11:04:11 RTE I Thread termination in progress
3628( 7796) 06/24/2020 11:04:11 RTE A SUMMARY-1 The following event has been reported 1 times in the last 0 minute(s)
3628( 7796) 06/24/2020 11:04:11 RTE A Performance-7-$G.assignment, Globallist $G.assignment contains too many items! num=739
3628( 7796) 06/24/2020 11:04:11 RTE I User SM_CIT has logged out. Still licensed ( 1 session remaining )
3628( 7796) 06/24/2020 11:04:11 RTE I Undisplayed message:Your last successful login was on 24/06/20 11:04:11
3628( 7796) 06/24/2020 11:04:11 RTE I Thread termination cleanup complete. Thread was active for 0 days,00:00:00. Threads remaining: 1 of 50

 

Because I'm not SM expert, it provides me my colleague that administer Service manager. If you have some idea to what else logs we should check on SM side,  please let me know. Thanks.

Regards

Highlighted
Valued Contributor.. Valued Contributor..
Valued Contributor..

Re: Error reading data by Connect-IT connector.

Hello,

the issue occurs accidentally and not only during import data to SMAX. Attached is scenario where import to text file is configured and error also occurred with it.

Regards

0 Likes
Highlighted
Micro Focus Contributor
Micro Focus Contributor

Re: Error reading data by Connect-IT connector.

Hello,

On the same test, add the RTM:3 and debugdbquery:999 to the tracing, it might throw some more detail on the reasons for the error.

Reagrds, 

Highlighted
Knowledge Partner
Knowledge Partner

Re: Error reading data by Connect-IT connector.

This is the correct log; are you connecting to a specific server on port 13091 from connect or are you using a Load Balancer?

If you are using a Load Balancer, try to use direct to one  server port.

My question is because you are using paging, getting 100 records per request; the way SM does this, on next request you see that he changes the file handler to an ID plus some attributes to see in which page you are, how many records to return etc.. but I'm not sure this is available cross sessions,  servlets nor servers.

So the hitting from the file handler leads me to believe that connect is open a new connection to the same or other server or servlet and then SM second session cannot honor the paging made at the initial connection.. not sure it is this but I'd take a look into this.

You could also take a look at the connector and scenario general options for Keep-Alive connection, set it to true and also to simultaneous threads on the source, leave it at 1. Unfortunately I don't have connect in any of my environments now; So I can't give you precise information about how to do this on connect but as I remember such options exists.

3628( 8068) 06/24/2020 11:04:11 RTE W Exception occurred for method recordset and XML request <?xml version="1.0" encoding="utf-8"?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header/><SOAP-ENV:Body><recordset count="100" filehandle="dbdict5ef316f40005c22c80f52f78" operation="list" start="200" total="1"/></SOAP-ENV:Body></SOAP-ENV:Envelope>

3628( 7132) 06/24/2020 11:04:11 JRTE W Send error response: A CXmlApiException was raised in native code : error 15 : scxmlapi(15) - Invalid file handle provided on recordset SOAP request - dbdict5ef316f40005c22c80f52f78

Let us know!

Regards,
Breno Abreu

If you feel this was helpful please click the KUDOS! thumb below!
Highlighted
Valued Contributor.. Valued Contributor..
Valued Contributor..

Re: Error reading data by Connect-IT connector.

Log with activated tracing options is attached. This is line with error:

 

Line 10730:   2792(  8148) 07/03/2020 10:57:53  RTE E Caught XML API exception scxmlapi(15) - Invalid file handle provided on recordset SOAP request - dbdict5efef2c9003c72ec805e9340

0 Likes
Highlighted
Valued Contributor.. Valued Contributor..
Valued Contributor..

Re: Error reading data by Connect-IT connector.

Hello,

I'm connecting to specific server with dedicated port only for CIT connection, so in one time no other connection is open through this port.
I didn't find Keep-Alive connection for Service Manager Rest connector, as I remember this option is used for database connectors. There is also no simultaneous threads on the source, I'm using just 1.

Regards

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: Error reading data by Connect-IT connector.

seems like lot of custom stuff. Also missing a file  Privileges.dsc , and may be a mapping table/script to run the attached scenario.

 

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.