John500
asked on
C# application doesn't launch on Server 2008 but runs on XP & Vista
Greetings,
I have a program the company has been using quite a while on Server 2003 and XP. We recently started a migration to Server 2008 and Vista. The program has no problems yet on Vista and works on some Server 2008 machines. For the Servers it doesn't work on it gives a Problem Signature error:
System.UnauthorizedAccess
This program is located in the following directory:
C$\ProgramData\Microsoft\W indows\Sta rt Menu\Programs\Startup
Is there some configuration item that is lacking which causes this problem?
This is additional information generated by the C# application:
Attempted to perform an unauthorized operation.
mscorlib -- System.UnauthorizedAccessE xception, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=
Thanks!
Status-program-stops-working.JPG
I have a program the company has been using quite a while on Server 2003 and XP. We recently started a migration to Server 2008 and Vista. The program has no problems yet on Vista and works on some Server 2008 machines. For the Servers it doesn't work on it gives a Problem Signature error:
System.UnauthorizedAccess
This program is located in the following directory:
C$\ProgramData\Microsoft\W
Is there some configuration item that is lacking which causes this problem?
This is additional information generated by the C# application:
Attempted to perform an unauthorized operation.
mscorlib -- System.UnauthorizedAccessE
Thanks!
Status-program-stops-working.JPG
ASKER
Ok, I'll keep these in mind as alternate solutions. However, it appears UAC is the problem because this executable is located in the Startup directory:
C$\ProgramData\Microsoft\W indows\Sta rt Menu\Programs\Startup
Apparently this directory defaults to the 'User' account especially for primary domain controlers which have no local user/group policies (for security reasons).
The end result is that unless the 'User' account is given write permission on the directory it needs, the application won't be able to write even if the user running the application is considered an administrator of the domain.
I'd try your suggestion right now but it would require a reboot on the PDC... but that's not happening during normal working hours.
Any additional thoughts?
C$\ProgramData\Microsoft\W
Apparently this directory defaults to the 'User' account especially for primary domain controlers which have no local user/group policies (for security reasons).
The end result is that unless the 'User' account is given write permission on the directory it needs, the application won't be able to write even if the user running the application is considered an administrator of the domain.
I'd try your suggestion right now but it would require a reboot on the PDC... but that's not happening during normal working hours.
Any additional thoughts?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks!
Also you might want to add it to the Windows Firewall as an exception.