I would definitely try to save to RAMP first in a location that can be accessed by the file viewer/downloader app. Filesystem access from RAMP is generally quite painfully slow. Size is one issue, but any operation that involves large numbers of files, even small files, can be even slower.
Thanks for the perspective.
Has anyone asked the RAMP team about the
USE ASYNCHRONOUS WRITE Citrix policy
https://support.citrix.com/article/CTX201515
I'm not clear what other solutions may also exist for Citrix.
Or some of the other patches or configuration tweeks
support.citrix.com/.../CTX138656
https://support.citrix.com/article/CTX208936
Hi Tom,
We're on RAMP using Citrix and I regularly run large output sets and save them to my local drives without issue. I'd suggest contacting RAMP support as this seems unusual. Best of luck!
Sara
We encountered this issue trying to save into an Excel file from an extraction. Exactly due to the same reasons, we started to use the EXTRXXXX file automatically saved by the extraction, instead of saving into Excel. You need to choose "File" as "Destination" instead of "List", and the extraction saves the file as EXTRXXXX in RAMP in the Impftp.lnk//Extract folder, where XXXX is the extraction number. I believe the file is in CVV format, which can easily be saved to the local machine afterwards.
I did not inquire with RAMP at that time, but this problem predates Citrix in our case. It can still be due to a 2X/Citrix protocol issue, but I suspect that the length of the file and virus protection on our end may be causing a timeout issue.
We never tried to save files into Excel directly after moving to Citrix. I would be curious to know, what RAMP has to say, if you decide to contact them.
We have already contacted the RAMP migration team. We are waiting for responses.