Can't Run Outlook 2003 with Limited User Account

[rVidia]

I have Microsoft Office Basic Edition 2003 installed on my machine (XP SP2), and I am able to run both programs (Outlook and Word) on my admin account. However, when using a limited user account, I am unable to open Outlook.

When I attempt to open Outlook OR Word on my limited account, I get the following error message:

http://tinyurl.com/evse6

I am able to open Word by clicking OK and then cancel:

http://tinyurl.com/kuqsl

After I do this, Word opens, but when I attempt to do the same with Outlook, I get this:

http://tinyurl.com/hgond

I don't think it is necessary to reinstall and am set on figuring out what is causing this problem.

When I attempt to open Outlook using Run As (to open it with admin privileges), I get this error message:

http://tinyurl.com/fsvd6

Office is installed on a separate partition (than the OS) where I install all of my programs.
EDIT: Run As is not working with any application, all resulting in the above error.

Any ideas? All suggestions are appreciated!

[dbarrow]

Was the program originally installed under an admin user?
Was it granted "all user" rights"
Sounds like a permissions problem.
Try going to the .exe and right click, properties,security,
bring up the list of users.
If the limited user is not on the list there, use add to add that user.

[rVidia]

Was the program originally installed under an admin user?
Yes.
Try going to the .exe and right click, properties,security,
bring up the list of users.
It was set to "Everyone"

[dbarrow]

I still think you are dealing with a user SID permissions problem.
Are there any Group Security policies?
Can this user access all files and folders?
If you can't browse to the .exe from the user and access (launch) it without getting that permissions screen, it is a permissions problem.
Add the specific user to the security permissions list.
Create a new limited user and see if that one works.
There may have been some problem when creating the user.

I see where limited users can have some problems.
I created a limited user for my wife that has some strange quirks I can't iron out. Sound settings refuse to stick and cause the sound config panel to launch every logon. Think I may delete/redo as a full user, get it working right, then change the user to limited.

Settings get carried from Docs&Settings\Default User when you create a user and that base profile can get messed up.
There is MSKB article on configuring Default User. Browsed but didn't pay close attention to it.

[rVidia]

I see where limited users can have some problems.
I created a limited user for my wife that has some strange quirks I can't iron out. Sound settings refuse to stick and cause the sound config panel to launch every logon. Think I may delete/redo as a full user, get it working right, then change the user to limited.
I removed my limited account (which I use only for web browsing/email) and created a new admin account, then changed account to limited, and I am now able to open Outlook. However, I am still unable to use Run As on anything at all, resulting in the same error here (http://img238.imageshack.us/img238/161/t011515806xy2.jpg).

[dbarrow]

I believe RUN or run as commands are defaulted off in limited user accounts unless set otherwise. The purpose of the limited user is to prevent execution of code using a run command.
I forget where this is located... group or security policy, but I do remember seeing an item in there that would prevent a limited user from executing such commands.

[rVidia]

I believe RUN or run as commands are defaulted off in limited user accounts unless set otherwise. The purpose of the limited user is to prevent execution of code using a run command.
I forget where this is located... group or security policy, but I do remember seeing an item in there that would prevent a limited user from executing such commands.
That was it. I had Secondary Logon in the Services Editor set to Disabled, so I had to set it to Automatic/start it on my admin account. Logged on to my limited user and I was able to use Run As ;)