The Memory could not be written error, Windows 2000

[KeyserSoze1877]

Yes I too am plauged by the memory cannot be written error. However, I have a very good idea on the direction to look at.

Here's what happened, I have a program, it doesn't matter what program it is. That program is installed as a service and is using a domain account to run.

I made some GPO changes, tightened up the security. However, I was making GPO changes for 2003 and was not away a OU with 2000 servers linked to that GPO. After the changes were made and the servers rebooted, the service popped the memory error when it tries to start. I put the account is uses to run in the local Admin group, works fine. Take it out. Memory error.

I reverted teh GPO back to the original setup and no luck, same thing. I have a hunch that there was a registry setting that the 2003 GPO set that 2000 doesnt have a local policy for, yet keeps the key. Administrators bypasses it.

So... I know its some kind of permission or network NTLM restriction or something somewhere.

6 people have spent two days looking hard and wide for the answer other than local Admin group, but we have not found the inital break setting.

Help!

---------------
Keyser Soze
"Vote Pedro."

---------------
Keyser Soze
"Vote Pedro.

 

[KeyserSoze1877]

Got it!

CurrentControlSet, Microsoft Current Version, and a few other critial registry keys were getting access denied when the account running the service tried to access them.

After running RegMon it became so clear, reverted the security permissions to what they were supposed to be, everything cleared up and worked.

The Memory "written" error was not what was going on at all, misleading, and STUPID!!!

It was, in my case, access denied when trying to read Reg Keys!

http://www.sysinternals.com/

RegMon and FileMon, life-savers once again!



---------------
Keyser Soze
"Vote Pedro.