Peoplesoft Excel To Ci Error
Contents |
April 07, 2011 ExcelToCI Error occurred in routine sendSOAPRequest_SubmitToDB: The operation timed out. When trying to upload about 7000 rows using ExcelToCI for a custom component, users are getting the following error. Error occurred in routine sendSOAPRequest_SubmitToDB: Error: Number: -2147012894 error occurred in routine sendsoaprequest_submittodb Description: The operation timed out After doing my investigation, checking the web server and error occurred in routine sendsoaprequest_getcishape appserver access log I found the following issues, and here is what i did to resolve the issue. This is not error occurred in routine sendsoaprequest_getcishape: error: number: documented anywhere. Please create a resolution if possible to help others. 1. Found that ExcelToCI uses SERVERXMLHTTP MSXML 6.0 object to send the SOAP request to the webserver, Set xHTTP = CreateObject("MSXML2.SERVERXMLHTTP.6.0") This the response text is not valid xml. login data cleared request has a default 30 second timeout for receiving a packet of response data from the target server, See link : http://msdn.microsoft.com/en-us/library/ms760403 for more details on timeouts. 2. After checking the webserver access log (PIA_Access.log), determined that some of the POST request are taking about 59 seconds to complete and therefore we were receiving the error. To resolve this issue, change the VB Macro code in ExcelToCI spreadsheet as
Excel To Ci Chunking Factor
follows ======================================================= Add this line before xHTTP.send xDoc.xml in StagingAndSubmission Module under function sendSOAPRequest_SubmitToDB Dim lResolve, lConnect, lSend, lReceive As Long lResolve = 60 * CLng(1000) lConnect = 90 * CLng(1000) lSend = 90 * CLng(1000) lReceive = 120 * CLng(1000) xHTTP.setTimeouts lResolve, lConnect, lSend, lReceive ======================================================= After changing this value, the ExcelToCI was still failing. Once again I checked the web Server and App server log and found that after loading about 50 to 60 rows, request is taking more than 5 minutes to respond and appserver is killing the appserv thread and therefore error was received saying that The Operation time out. I had two options 1. Increase the XMLHTTP timeout and also increase the appserver timeout or find out why a request is taking more than 5 minutes to complete. Used Precise i3 performance monitoring tool and also the live Oracle session and determined the following issue. 1. CI was firing sql to fetch location code description using a view that was not correctly joined with other large table using location code. 2. A Save Edit Peoplecode was written at Level 2 to fetch some data from the Oracle table using SQL Exec. This was causing this sql to fire 160,000 times as it was
Interview October 23, 2016 You are here:Home PeopleTools Excel to CI Error - Invalid XML Returned Excel to CI Error - Invalid XML Returned Tweet Tweet Posted by Rakesh Subhagan in PeopleTools | 3 Comments Today
Error Occurred In Routine Sendsoaprequest_submittodb:error:number: -2147012744
one of our users called in stating that they were getting an error peoplesoft excel to ci operation timed out while trying to upload the data using the Excel to CI utility. The text of the error was: Error: Invalid error occurred in routine send soap request get in shape XML Returned. The response text is not valid XML. Login Data cleared. Excel to CI Error - Invalid XML Returned Upon investigation, it was found that a wrong entry in the Connect Information http://peoplesoftexperts.blogspot.com/2011/04/exceltoci-error-occurred-in-routine.html sheet was the root cause of this error. The PeopleSoft Site Name entered was incorrect. After entering the correct site name, the tool started working perfectly. Well, another reason for this error to occur would be that none of the Permission Lists that are associated with the user has access to WEBLIB_SOAPTOCI iScript. But in our case, this was ruled out as this user was able to http://www.psoftsearch.com/excel-to-ci-error-invalid-xml-returned/ use Excel to CI till the week before. If you have ruled out the above possibilities, then there could be yet another reason that this may happen. It can be due to the presence of invalid characters in the actual data being uploaded, the most common such character being "&". Tags:Errors, Excel to CI PeopleSoft Excel to CI Comma as Thousand Separator in File Layout? PS Query is a reporting utility provide by PeopleS... PeopleSoft Query « Comma as Decimal Separator in File Layout? » Using Multiple SQL Statements in an SQL Action Subscribe to Comments RSS Feed in this post 3 Responses Nevena # I got the same error and discovered that it could be caused by the wrong Web Server Machine Name as well. Reply Rakesh Subhagan # @Nevena - Thanks for posting it here. It could be useful for someone looking for a solution. Reply Mohsin # We got the same error and found that it was due to employee password was about to expire (10 days were remaining). Changing the password fixed the issue. Reply Leave a Reply Cancel reply Your email address will not be published. Required fields are marked * Name
Enter data on the data input sheet. View staged data. Create SOAP/XML requests. Send requests. Receive responses. Diagnose and resolve errors. Add new languages. Understanding the Excel-to-Component Interface Utility Use the https://docs.oracle.com/cd/E28394_01/pt852pbh1/eng/psbooks/tcpi/htm/tcpi10.htm Excel to Component Interface utility and component interfaces to upload data from Microsoft Excel into PeopleSoft databases. Each source workbook contains both worksheets and Excel Visual Basic code modules that execute http://javier-ps.blogspot.com/2010/02/exceltoci-under-https-with-ssl.html business logic for each transaction. Use the Microsoft Excel workbooks as a template to create worksheets that are specific to the business logic that you need to use when you error occurred are uploading data to the PeopleSoft system. You can copy the data input sheet to other workbooks for distribution without copying the code modules. The code formats spreadsheet data into a PeopleSoft readable Document Object Model (DOM) structure, and submits it to the PeopleSoft database. Next a PeopleCode program parses the DOM structure and uses the component interface to create entries in error occurred in the PeopleSoft database, validating the data submitted against the business logic that is built into the PeopleSoft component. Because the component interface is a wrapper around the component, all logic applied during data entry is applied when you are loading data through this tool. The component interface executes all the necessary PeopleCode events and the field-level edits. Based upon results from saving the component interface, another DOM is created in the PeopleCode that returns success, warnings, errors, or a combination of the three to the Microsoft Excel document. Records in error can be corrected and resubmitted. Prerequisites for Using the Excel to CI Utility To use the Excel to CI utility you must have the following software installed. Check the My Oracle Support web site for the currently certified versions of software supported. Microsoft Excel. Microsoft Visual Basic 6.0 SP5: Run-Time Redistribution Pack. You can download this software from the Microsoft website. See http://www.microsoft.com/downloads/Search.aspx?displaylang=en Microsoft Core XML Services (MSXML) 6.0 or higher. You can download this software from the Microsoft website. See http://www.microsoft.com/downloads/Search.aspx?displaylang=en Understanding Building Component Interfaces for the Excel to Component Interface Ut
in PeopleSoft environment which could only be accessed through HTTPS. However, as the certificate in the web server was expired, ExcelToCI would error out whenever the user wanted to create a new template or submit the data to the database.Obviously, this issue would have been solved by simply renewing the web server certificate, but the customer was not in a position to do this now and we had to seek an alternative solution.Our solution was to modify the ExcelToCI macros to tell them to ignore SSL certificate errors. To do so, we had to do the following changes on the CreateCITemplate.sendSOAPRequest_GetCIShape() and StagingAndSubmission.sendSOAPRequest_SubmitToDB() functions:Replace the following variable declaration: Dim xHTTP As XMLHTTP by Dim xHTTP As New MSXML2.ServerXMLHTTP40Replace the following variable initialization: Set xHTTP = New XMLHTTP by Set xHTTP = New MSXML2.ServerXMLHTTP40Add the following line before calling the Send method: xHTTP.setOption 2, 13056 'Ignore all SSL errorsThe SetOption call is actually telling the Send method to ignore any SSL certificate error. Publicadas por Javier Delgado a la/s 9:12 PM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Etiquetas: ExcelToCI, HTTPS, SSL 19 comments: mack said... I had a similar problem but just renewed the SSL certificate (it was much easier) but i've bookmarked this incase I have different circumstances of clients in the future February 22, 2010 at 1:24 PM Javier Delgado said... That's true, although this particular customer said it would take some weeks to get the certificate renewed because of internal approval procedures.It's clear this is just a workaround. February 22, 2010 at 4:44 PM DuncanDavies said... This saved me a lot of searching today. Thank you. April 1, 2010 at 1:23 AM Michael said... Javier,We receive this error but the description is different (its just the number again). Also our certificates are definitely not expired. This works in IE6 but breaks in IE8. Any idea on what this could be? May 6, 2010 at 11:55 PM Javier Delgado said... Michael,I'm not sure what you mean, as IE is not involved in the process.However, depending on the Excel version, the MsXML objects may have different properties. Still I don't see any relation with IE.Thanks! May 25, 2010 at 10:08 AM Neeraj Kholiya said... I prefer winhttp in this case .. I tried using in a javascript through peoplesoft and achieved same results July 19, 2010 at 12:16