• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1078
  • Last Modified:

Permissions required to READ Windows registry by an isapi dll ?

Given an isapi dll created with Delphi / IntraWeb 10.0.23 running on IIS6 (Win2003), I'm having a problem getting to read values from the server's registry.
I have no obvious problem with the code, which runs just fine inside the same application compiled as a standalone server, running on my development machine (WinXP).
This appears to be a permissions issue and I have progressively/selectively allowed upto 'Full Control' on the group/user accounts for the isapi.dll in NTFS with particular attention to the IUSR_xxxxxx account (which for typical usage would need to be Read & Execute). The registry values just don't get read whatever permissions I set. The read requests are explicitly coded as so ... and I think that I should be able to do this. There are no errors generated.

Can you help with advice regarding permissions ?
Is there possibly a setting within IIS6 which applies to an/the isapi dll ? ...
I've looked at the dll's properties within IIS6 but as yet found nothing to help.

thanks and best regards

  • 2
1 Solution
TheRealLokiSenior DeveloperCommented:
I'm not a web server admin so take my lack of knowledge ansers in the helpful manner they are intended.

just a hunch, but it probably inherits the permission of the web server (IIS service?)
if it's worth a check, use the services.msc and change the service to log in as a specific account that has the rights you need (e.g. try "administrator" for a quick test)
make a note of what user the service is currently using though, so you can change it back.

If this works then at least we know we're on teh right track, and can use an appropriate user and settings for the web server
RetroRockerAuthor Commented:
Thanks for the help anyhow. I was already working as a 'Administrator' on this server in any case. I have now found the solution and it turned out to be nothing so complex as permissions ... and we know how complex they can be :)
I had missed the fact that the registry keys I needed to read should reside below the 'Wow6432Node' registry node because this was a 32 bit process running on a 64 bit server ... oh well ;)

RetroRockerAuthor Commented:
Own solution found as posted above.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Train for your Pen Testing Engineer Certification

Enroll today in this bundle of courses to gain experience in the logistics of pen testing, Linux fundamentals, vulnerability assessments, detecting live systems, and more! This series, valued at $3,000, is free for Premium members, Team Accounts, and Qualified Experts.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now