Failed to allocate bytes: The paging file is too small for operation to complete.

[Avail]

Hello!

My original inputs at the very beginning of the workflow are .yxdb files.

I am running a large amount of data through a Unique tool and linking it it back up through a Find And Replace tool. For the Find and Replace tool, the "Find Within Field" and "Find Value" fields are both Record IDs that have been converted to strings (since the find and replace tool does not allow for numeric types to be used). 

Here are the work arounds I have tried and have not worked...

1. Turning off AMP engine and re-running

2. Changing Record ID type to string in the Record ID tool at the beginning of the workflow and adding an Auto-Field tool right after to optimize the length of the field.

4. Doing the same thing as #2 and deleting leading zeros before running through the rest of the workflow. 

3. Changing Record ID type to string in a select tool (and changing field length to 999999999) before the unique and find/replace tools. 

Now I'm stuck. My workflow contains sensitive data so unfortunately I cannot share my data or workflow. Only an image of the error. 

Any advice or information is gratefully appreciated! Thank you :)

[binuacs]

@Avail 

This error suggests that Alteryx is trying to allocate memory (about 4MB) for an operation but the system paging file (virtual memory) is too small to handle this request. Increase the memory. Go to Control Panel > System and Security > System > Advanced system settings > Performance Settings > Advanced > Virtual memory > Change. Here, you can increase the initial and maximum size of the paging file. 

[psja]

Hi, sorry to revive a 7-month-old thread, but is there a way to avoid this from happening? I'm doing some troubleshooting on my workflow in the Gallery and it was never an issue before for this workflow. Aside from adjusting the size of the paging file, is there anything else I can do? Thanks!

[SwapnilG]

Any recommendation on making the changes to max size to allow the workflows to run smoothly.

[apathetichell]

You should not be doing what you are doing. Simple answer. The Unique tool is not designed for this. Use the summarize tool. The limit you are hitting is a max string size limit. Don't use the unique tool for this. Please.

[SwapnilG]

Attached are the error messages which we are receiving when trying to run the workflows, what can be the best solution for this one? 

[apathetichell]

My message includes the solution --- do not use the Unique tool.