Am using odler version of WWWC with FoxInCloud. Beenn running automation mode. Suddenly FiC was gettuibg not enough memory to complete this operation messages. WWWC was loading 3-6 copies of .exe even though .ini specifies 1 or 2 servers. ( I have changed real names to "xxx" for reasons of confidentiality.)

Example:

Server1=xxxxxxfund.xxxTestServer 
Server2=xxxxxxfund.xxxTestServer 
;Server3=xxxTest.xxxTestServer 

Is this something I don't know about, or ?????

Not enough information. How are you running the application?

FWIW - there's no such thing as 'all of a sudden'... something changed. 😄

+++ Rick ---

"All of a sudden" you ruined my chance to sound like an annoying user for once instead of being on the receiving end!

So: I cannot see any changes. Rather than putting a screen shot of everything in the world, what information would be helpful??

Thanks

File Mode? COM Mode? (assuming COM)

Are servers crashing? Take a look at the wcErrors.txt log.

+++

COM and no errors.

It happens when the servers have high loads, so waiting for next occurence to send more info.

C'mon Tuvia, you know better how to make a useful error report...

• What version
• .NET Connector or ISAPI

+++ Rick ---

I do, but as said, I am waiting for next occurence so I can include additional info memory etc.

Swapped out a potentially bad memory chip and I do not see the problem anymore. Hopefully that was the issue!

Hi Tuvia,

This thread deals with the 'not enough memory to complete this operation' error.

In short, on Windows Server > 2012, using DCOMCNFG, you need to explicitly set the executing user instead of relying on the launching user, even if it's the same.

Good luck!

Thierry,

I think that's circumstantial at best.

Windows doesn't care how the security context gets provided as long as you get the right context. I haven't set DCOMCNFG settings in 20 years for any of my servers running COM.

The only exception to that would be if your application for some reason is misconfigured and there are multiple IIS application pool sites point at the same folder or host name that is individually and differently configured (ie. a different application context with a different user) gets fired.

The machine wide DCOM settings (on the Computer node) can have an effect for access, but that's a all or nothing situation.

+++ Rick ---

Inter. esting. Will tr.y.