Skip to main content

Insufficient system resources exist to complete the requested service (0xFFF0) code = 800705AA),

Thread needs solution

Hello, 

Looking to see if other have run into occational "Insufficient system resources exist to complete the requested service (0xFFF0) code = 800705AA)," errors with ATI 2018? 

Error message is below. 

Win10 desktop w/ i5, 12GB RAM, 1TB HDD with over 700GB free

4 ATI scheduled back up jobs (each running twice per week on different day) that run fine for about a week or to an then one by one start to get this error. Three of the jobs backup from NAS to local D drive and one backup C drive to NAS. 

If I reboot the PC or NAS they start to work again for another week or two and then fail. I have been troubleshooting this for a few months and initially thought it was a NAS issue but the last two time the errors started, I rebooted the PC instead of the NAS and the error cleared ... for another week or two. This seems that say a memory leak of some type but no other apps/programs on the PC complain (not that I do a ton of things on the PC). 

Thoughts? 

Access to the file is denied. (0x40014)
function = "WNetAddConnection3W",
path = "\\192.#.#.#",
$module = "ti_demon_vs_15470"
winnt_dir::SetPassword:
Insufficient system resources exist to complete the requested service (0xFFF0)
code = 800705AA),
$module = "ti_demon_vs_15470"
Common::Error::AddWindowsError:

0 Users found this helpful

I have not seen any other users in the forums reporting this error, but if it is resolved (albeit temporarily for a period of time), then perhaps it indicates some other issues at work here, i.e. some form of memory leakage that is eventually starving the ATI processes.

maybe... but.... 

The PC had existing drive mappings to the NAS under the normal logged in user. When ATI runs, I have it using different creds to connect to the NAS and run the back up jobs. I am using different creds because when initially setting up the backup jobs, ATI got errors saying "too many logins"... almost saying it did not like using the existing mappings and wanted a different connection. 

I don't have issues with "default" drive mappings nor errors with accessing files...