App needs .NET Framework permissions?

[boomerang]

I just installed the 2007 version of some payroll software my wife uses at work for her.

The 2006 version ran fine under a limited user account just by assigning permissions at the folder level.

When closing the 2007 version, an error message is generated from the software referring to the .NET Framework and registry access.

I contacted the software company and their idea of help is that this is a Microsoft issue and for me to contact them. Grrrrr! They did tell me that Limited Users will need the same permission in .NET as administrators.

I really don't know where to begin, although I'm thinking this is a Group Policy thing. This would be unchartered waters for me and I will need some hand-holding.

Could someone help or point me in the right direction?

Edit: I should add that this is a small office with three computers and there is no domain. All systems are fully patched and at .NET 2.0.

 

[WannaFly]

Couple Suggestions:
1. If the 2007 version doesnt NEED the 2.0 framework, try it against the 1.0/1.1 framework.
2. Use something similar to regmon to see what key is being accessed, then use regedt32 to give the limited account write permissions

 

[boomerang]

Originally posted by: WannaFly
Couple Suggestions:
1. If the 2007 version doesnt NEED the 2.0 framework, try it against the 1.0/1.1 framework.
2. Use something similar to regmon to see what key is being accessed, then use regedt32 to give the limited account write permissions

1) Would this mean uninstalling 2.0? I said I'd need some hand-holding.

2) I actually understand this, but have never done any permissions doodling at the registry level. I can cross that bridge when I come to it though.

 

[beggerking]

is there some kind of configuration file that you can update?

 

[MrChad]

Originally posted by: boomerang

Originally posted by: WannaFly
Couple Suggestions:
1. If the 2007 version doesnt NEED the 2.0 framework, try it against the 1.0/1.1 framework.
2. Use something similar to regmon to see what key is being accessed, then use regedt32 to give the limited account write permissions

1) Would this mean uninstalling 2.0? I said I'd need some hand-holding.

2) I actually understand this, but have never done any permissions doodling at the registry level. I can cross that bridge when I come to it though.

1.1 and 2.0 can run side-by-side. No need to uninstall 2.0.

 

[boomerang]

Originally posted by: beggerking
is there some kind of configuration file that you can update?

If there is. I know nothing of it. The 2006 version did not need .NET. This is a whole new ballgame.

 

[boomerang]

Originally posted by: MrChad

Originally posted by: boomerang

Originally posted by: WannaFly
Couple Suggestions:
1. If the 2007 version doesnt NEED the 2.0 framework, try it against the 1.0/1.1 framework.
2. Use something similar to regmon to see what key is being accessed, then use regedt32 to give the limited account write permissions

1) Would this mean uninstalling 2.0? I said I'd need some hand-holding.

2) I actually understand this, but have never done any permissions doodling at the registry level. I can cross that bridge when I come to it though.

1.1 and 2.0 can run side-by-side. No need to uninstall 2.0.

I'm clueless as to how to point the app to use 1.1 versus 2.0.

 

[stash]

It should figure that out on its own.

That said, I not really sure how to resolve this problem. There is a .NET security configuration snap-in, but I haven't used it much. Can you post the exact error you're getting?

 

[boomerang]

Originally posted by: stash
It should figure that out on its own.

That said, I not really sure how to resolve this problem. There is a .NET security configuration snap-in, but I haven't used it much. Can you post the exact error you're getting?

Well, the error is generated from the program itself, but here it is;

"Application attempted to perform an operation not allowed by the security policy. To grant this application the required permission, contact your system administrator, or use the Microsoft .NET Framework Configuration tool.

If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.

Requested registry access is not allowed."

Crude though it may be, I may just go through the .NET config utility and mirror the settings from admin to limited. There's lots of "stuff" in there though. None of which I'm familiar with.

I'm rather upset with Peninsula Software. From the error message itself, you can tell they forsaw this coming. Their refusal to help is not the right thing to do IMO. But on the other hand, I do see their point. They feel if I'm going to run my users on a limited account that I should know how to deal with these situations. Catch 22 for me.

But I'm not going to have 3 employees that can barely turn the computer on running as administrators.

 

[boomerang]

At another forum,I've been told of some .NET related registry keys to change permissions on that I need to try today. I also heard about this free program that has some potential as an easy fix.

I'm going to try to get over to the office today to try these out. It's difficult during a normal workday.

This looks promising.

 

[KB]

If this is a .Net App running locally it should have full .Net trust to do everything the user can do.

As recommended byWannaFLy: use the REGMON tool from sysinternals to monitor which regsitry key is being accessed when the error occurs and grant limited users access to it.

 

[WannaFly]

Originally posted by: MrChad

Originally posted by: boomerang

Originally posted by: WannaFly
Couple Suggestions:
1. If the 2007 version doesnt NEED the 2.0 framework, try it against the 1.0/1.1 framework.
2. Use something similar to regmon to see what key is being accessed, then use regedt32 to give the limited account write permissions

1) Would this mean uninstalling 2.0? I said I'd need some hand-holding.

2) I actually understand this, but have never done any permissions doodling at the registry level. I can cross that bridge when I come to it though.

1.1 and 2.0 can run side-by-side. No need to uninstall 2.0.

Yes they can, but that doesnt mean the app will run in each version - it depends on many things, when the app was installed, what it was originally written in, and when the frameworks were installed...IIRC. I dont think this will fix your poblem, but just wanted to mention it.

As for the registry, chances are the program is trying to write to HKLM(HKey_Local_Machine) instead of HKCU(HKey_Current_User), which users to not have permission to write there.

Using regmon, find out what key its trying to edit, then run regedt32, browse to it, right click it and select "Permissions" then grant "everybody" write permission to that key.

 

[KentState]

I bet the computer needs to have the framework configured. From the administrative tools under control panel, select .Net Framework 2.0 Configuration. Inside that, expand My Computer --> Runtime Security Policy --> Machine --> Code Groups --> All_Code. Rigth click on All_Code and select New... From there give a name like 'Anything', click next and select All Code, next Full Trust, and then Finish. You will have to do this same process for the .Net Framework 1.0 Configuration as well. See if this works and we can go from there.

 

[waitman]

http://www.mechbgon.com/build/LimitedSW.html

Might try this advice from mechBgon.

 

[boomerang]

To all who suggested it, I did the regmon thing. There are a lot of keys being opened and closed, but only two being edited. And it appears successfully so. Nontheless, I gave the appropriate permissions with no success.

Originally posted by: KentState
I bet the computer needs to have the framework configured. From the administrative tools under control panel, select .Net Framework 2.0 Configuration. Inside that, expand My Computer --> Runtime Security Policy --> Machine --> Code Groups --> All_Code. Rigth click on All_Code and select New... From there give a name like 'Anything', click next and select All Code, next Full Trust, and then Finish. You will have to do this same process for the .Net Framework 1.0 Configuration as well. See if this works and we can go from there.

This was the advice I thought I needed as I was totally unfamiliar with configuring .NET.

I did this to 1.1 with no success. After some uninstalling and reinstalling (letting the app install the version of .NET it wanted) I determined that 2.0 was what it wanted to work with. The system now has only 2.0 installed.

Now the problem. I can find no configuration utility for 2.0. I find some references online to mscorcfg.msc, but this won't run on my system. I had no configuration references for 2.0 both when downloaded as an update from Microsoft and when installed automatically with the application.

At this point, I believe this is the answer, but without a configuration utility, I'm stuck.

 

[beggerking]

Originally posted by: boomerang

Originally posted by: beggerking
is there some kind of configuration file that you can update?

If there is. I know nothing of it. The 2006 version did not need .NET. This is a whole new ballgame.

some .net apps uses .config file in xml format...if there is one, you should check it out..