Skip to main content
  • EN

I have reviewed the recommended Virtual Memory settings in this post. But, my server is hosted in Azure. It has 32GB of physical memory, 4 cores, and has a dedicated 149GB drive for the pagefile that is managed by Azure. Still getting this error when reading in 5M well records from Enverus data to our SQL Server Enterprise Geodatabase (SDE). The FME version is the lates - 2022.1.3. Just upgraded from 2020.2.2. 2020.2.2 did not have this issue.

 

 

To clarify - I have NOT made the suggested settings as Azure manages the pagefile and it is substantial.

You should check where fme is writing temp files. Could it be that the temp location is on a small disk which is getting full?

 

Thank you virtualcitymatt. That was it. I did have an FME_TEMP system variable set up and pointing to a drive. That drive was NOT big enough for the new activity. I increased the drive space and the workbench ran successfully.

Reply


Community Stats

30,162
Posts
114,509
Replies
37,819
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.