caseware error

  • Thread starter Thread starter pdch@shaw.ca
  • Start date Start date
P

pdch@shaw.ca

Guest
I have an application "caseware" that gives an error saying registry
editing has been disabled by the admin. I have granted permissions
under HKLU and HKLM to the specific application in question, but still
doesn't work. Tech support for caseware recommends "enabling"
disableregistryediting on the terminal server ( I don't feel
comfortable doing that...) I ran regmon, but it didn't come up with
anything regarding access denied to any registry key.
Does anyone have any suggestions?
Thanks!
 
Re: caseware error

Hi,

Are they referring to the group policy setting "Prevent access to
registry editing tools"? If you have this set to enabled have you
tried Disabling it or setting it to Not Configured to see if the error
still occurs (just for testing).

I have never come accross an application that requires this
setting and if the application did I would want them to give me
a good explanation as to why. If their app needs to edit the
registry they can do it through standard api calls and do not need
the registry editor or reg.exe.

Process monitor is the latest version of regmon. Run it as an
administrator and then logon as a normal user and run the
problem software. Look for access denied or other problems
both for files and registry keys. You can use filtering to limit
the display to items matching the .exe name for caseware.

Process Monitor

http://www.microsoft.com/technet/sysinternals/utilities/processmonitor.mspx

-TP

pdch@shaw.ca wrote:
> I have an application "caseware" that gives an error saying registry
> editing has been disabled by the admin. I have granted permissions
> under HKLU and HKLM to the specific application in question, but still
> doesn't work. Tech support for caseware recommends "enabling"
> disableregistryediting on the terminal server ( I don't feel
> comfortable doing that...) I ran regmon, but it didn't come up with
> anything regarding access denied to any registry key.
> Does anyone have any suggestions?
> Thanks!
 
Re: caseware error

Hi--

Your best bet at this point is likely talking to Caseware to see what key
the application needs to edit and ensuring that it has access to that
particular key.
--
Regards,
Christa Anderson [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
http://blogs.msdn.com/ts

<pdch@shaw.ca> wrote in message
news:1193690733.886424.201850@k35g2000prh.googlegroups.com...
>I have an application "caseware" that gives an error saying registry
> editing has been disabled by the admin. I have granted permissions
> under HKLU and HKLM to the specific application in question, but still
> doesn't work. Tech support for caseware recommends "enabling"
> disableregistryediting on the terminal server ( I don't feel
> comfortable doing that...) I ran regmon, but it didn't come up with
> anything regarding access denied to any registry key.
> Does anyone have any suggestions?
> Thanks!
>
 
Re: caseware error

On Oct 31, 2:14 pm, "Christa Anderson [MSFT]"
<c...@online.microsoft.com> wrote:
> Hi--
>
> Your best bet at this point is likely talking to Caseware to see what key
> the application needs to edit and ensuring that it has access to that
> particular key.
> --
> Regards,
> Christa Anderson [MSFT]
> This posting is provided "AS IS" with no warranties, and confers no rights.http://blogs.msdn.com/ts
>
> <p...@shaw.ca> wrote in message
>
> news:1193690733.886424.201850@k35g2000prh.googlegroups.com...
>
>
>
> >I have an application "caseware" that gives an error saying registry
> > editing has been disabled by the admin. I have granted permissions
> > under HKLU and HKLM to the specific application in question, but still
> > doesn't work. Tech support for caseware recommends "enabling"
> > disableregistryediting on the terminal server ( I don't feel
> > comfortable doing that...) I ran regmon, but it didn't come up with
> > anything regarding access denied to any registry key.
> > Does anyone have any suggestions?
> > Thanks!- Hide quoted text -
>
> - Show quoted text -

Thanks for all the replies. I downloaded the processmonitor and found
the "access denied" registry keys it was having problems with. I gave
the appropriate user group god-like access to the keys, but still the
error persists. I did contact the caseware people and they said there
were too many keys to list to give access to. I'm sure the GPO is
denying access, but explicit access has been granted on the
appropriate keys. I'm guessing that the "deny" permission is
overwriting the allow permission. What is odd is that the users can
still do their business in the application (create docs - which is
what the registry keys 'allow' was supposed to fix) ... it creates the
docs they need, all the while giving the "registry access has been
denied" error.
I"m ready to quit IT !!!!
 
Back
Top