Multiple Errors from non-main accounts on Server 2008

Notched
Notched used Ask the Experts™
on
I've searched the forums and have tried the solutions posted there to no avail. Here's my situation.

Windows Server 2008 (32 bit). The Administration account runs EVERYTHING fine. We have to keep this on 32 bit due to a program limitation that has to run. Anyway, when creating another user on the server (for Remote Access purposes), logging in brings some interesting issues.

1. MMC gives the "Failed to create empty document" error. I've tried the environment variable for the Temp and TMP folders. Didn't fix the issue. Tried stopping the indexing service. Didn't fix the issue.

2. The menu buttons on the non-admin user accounts are missing their text (see the attached screenshot).

3. Finally, the windows, minimize, maximize and close buttons do not work. The buttons are clickable, but they simply won't work. Trying to click and drag the window around, does nothing.

Luckily this hasn't been brought into full production yet, but do you think I should just do a full reinstall and start fresh or am I missing something? I will say that trying to run the software (it's a towing company software) from the non-administration accounts gives an "Out of Memory" error, if that means anything...Screenshot of just about all issues on one screen
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Architect/Designer
Commented:
Hmmm. sounds like a dodgy one....

The issues are likely to be space or permissions.

Assuming you have checked disk space, free memory & permissions to the temp folders mentioned in the many links around the internet for the MMC issue?

I'd lean towards permissions when taking the other symptoms into account, but this can be hard to resolve as you can fix permissions for weeks only to find more that are wrong.

I'd recommend wiping and starting again as it is not a production machine. You may need to reset permissions in Regedit and for folders on the disk. its a messy job but let us know if you decide to have a go.

Author

Commented:
Totallytonto,

You know what? I ended up just saying screw it and reinstalled the OS. Being that it wasn't production yet, I had nothing to lose. Everything worked fine after the reinstall (though the proprietary software had to be reinstalled 5 to 6 times before it actually "held").

Thanks so much for the help though. Glad that it is now resolved!

Author

Commented:
Wiping and starting fresh was pretty much the only option!

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial