Internal Error when adding collection to queue

[StephenColeman]

Hi all, I'm hoping someone has seen this error previously and can help with resolving.  I'm using a standard process which opens an Excel spreadsheet using the MS Excel VBO, gets worksheet as collection (fast) and then uses the Internal - Work Queues - Add to Queue object.  I am getting an Internal error at the Add to Queue stage: "Internal : The underlying secure session has faulted before the reliable session fully completed. The reliable session was faulted" If I try to step over the action again, I get the error: "Internal : The communication object, System.ServiceModel.Channels.ReliableRequestSessionChannel, cannot be used for communication because it is in the Faulted state." If I step over another action, e.g. Count Collection Rows, and then try to step over the Add to Queue stage again, I get a repeat of the first error: "Internal : The underlying secure session has faulted before the reliable session fully completed. The reliable session was faulted" Can't seem to find reference to this in the forums or KB, so hoping someone here can help. I'm using Blue Prism 6.1.0 Thanks, Steve

[Anonymous]

Having the same problem over here, does anyone have an answer?

[DerekTurner]

We had a similar issue when trying to add a collection with more than 40 columns to the work queue.  How many columns are you trying to load into the work queue?  Not sure if this is your issue or not. Supposed to be fixed in 6.3 I think.  Perhaps someone can confirm this for us.

[RahulYadav]

Hello Guys, Can Anyone have update on the above Issue? Got Any Resolution, facing the same Issue  ""The communication object, System.ServiceModel.Channels.ReliableRequestSessionChannel, cannot be used due to an error that occurred during close"". Thanks Rahul Yadav

[david.l.morris]

Could you guys describe the collections you're using, such as the number of columns and rows and if there is anything unusual about the data? I tested 117 columns and 1,000 rows in 6.3, and it added them all to the queue as expected. I'll try in 6.1 later on and see if I get any issue. Dave

[StephenColeman]

Hi Dave, My data was a simple spreadsheet. 12 columns and 10 rows.  Data like client name, account number and address.  All alphanumeric characters, no 'special' characters.   Thanks, Steve

[TetsujiJunicho]

Hi See the following link: https://help.blueprism.com/1158450492 How to resolve your issue: If moving to a WCF server connection mode was a business requirement, upgrade to Blue Prism Version 6.3 where the issue has been resolved. If upgrading is not an option, either reduce the number of fields in the Collection which the Work Queue is using to fewer than 40, or change the Application Server and Runtime Resource connection mode to use a "".Net Remoting"" method in the Connection configuration Hope this helps.