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

Access Permissions to the registers files in a OLE Object.

I have an application, that is a DCOM Server (OLE),I use in this application the TRegIniFile class to access an register file for load parameters.

If I create an instance of this ole object in another Delphi application there is no problems. The problem is the following:

I need to create the OLE object in an Active Server Page,
when I do it there is an error, this last is that the OLE object can't access the register file because it don't has permission.

What I can do ?
0
lantero
Asked:
lantero
  • 2
1 Solution
 
Russell LibbySoftware Engineer, Advisory Commented:

The DCOM server is probably set up to run as the launching user. (To confirm this, run dcomcnfg.exe and check the Identity tab of the Properties dialog for your DCOM server.)

When launching via active server page, it is most likely running as IUSR_<servername>. This is the default guest account set up by IIS, as is limited to what resources it can access. (unless you have changed the security for the asp page)

To make this work, you can use dcomcnfg.exe to change the identity to a specific user. (this would be the simplest)There are other methods available, for more info check MSDN web site on article Q201843.

Russell
0
 
Russell LibbySoftware Engineer, Advisory Commented:
No comment has been added lately, so it's time to clean up this TA.
I will leave a recommendation in the Cleanup topic area that this question is:

To be PAQ/Refund

Notes:
I DID answer the question, but feel that it is a conflict of interest to recommend the points to myself.

Please leave any comments here within the next seven days.
 
PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!
 
Thank you,
Russell

EE Cleanup Volunteer
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

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