Windows Power User, .Net Initialization Error, Application Crashes

ottobock used Ask the Experts™
Hello Experts,

I am testing user access to a server where not everyone should have full administrator access.  At the moment, adding the users to the Power Users built-in group works well, but a required application fails to launch. I cannot seem to find why.

The program runs in the tray fine for a local admin, but after logging in as a Power User, the following errors occur:

- Error 1: Initialization Error. This software requires the .Net Framework 2.0 or higher. Please install the .Net Framework and run this software again.

- Error 2: Application_Name has encountered a problem and needs to close. Sorry for the inconvenience.

- Error 3: Application Error. Exception EAccessViolation in module application_name.exe at 00021361. Access violation at address 00421361 in module 'app_name.exe'. Read of address 00000000.

--> .Net Framework is installed. <--
Obviously this is an access issue because the user is in the Power Users group, but does anyone have an idea what is blocked? User has full access to the app folders, Windows\Microsoft.NET folders, etc...

Any ideas?
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Top Expert 2015
Hard to tell, but a common error I see is application that tries to write in the installation directory. Applications are usually installed in Program Files, and from .NET application, Program Files is read-only for non-administrators.

A lot of programmers have kept their old habit of using the application directory for some data or configuration files that need to be written to. They develop and test as administrators, so they do not catch that new security feature built into the framework.

Except for read-only files, application files should be stored in the application directory (C:\Users\<username>\AppData\ in Windows Vista, 7 & 8). The convention is to create there a subdirectory for the company, and another one for each application, and store the application files in that directory.


Still can't find the problem ~ but thanks anyway for the info.

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