Delphi comes with a web application example iServer.dll's correct settings
Once an accidental opportunity, I am playing the iServer.dll web application server that comes with Delphi on Windows XP Pro, and finding that the initial text is even displayed, and when I click on the link to the database in the page, Always prompt the server in the server (HTTP 500). In the case of affirmation of your IIS directory and permission setting, Best can't understand. Today, I'm watching the "IIS in question" in May 2002, "IIS has a reply", "Try to use ASP to access the database" Access Rejected "" problem, after his tips, I use Filemon The tool is monitored for ISERVER.DLL files, and finally found that ISERVER.DLL running errors is insufficient for PDOXUser.net files.
This is a paragraph in this article in Brett Hill, "There is a great free utility called Filemon, you can
It is found on http://www.sysinternals.com. When I taught IIS, I let the students save this tool on the floppy disk, regardless of wherever they are. I am not full of jokes. You can quickly diagnose most permissions issues in FileMon because it can display all files accessed on the server, call the name of the process, and access results. In this way, for any "access denied" message, no matter how deep in nesting include, no matter how blurred in the temporary index - can be easily identified. ", I believe there are some help to some programmers.
Let's take a look at my discovery process:
1. Run Filemon software, exclude its process, reduce monitoring targets, and suspend file monitoring
2, open IE and open
Http://loclahost/webapp/isere.dll (WebApp is an executable false file in my IIS server), and the initial file page of ISERVER.DLL will be normal.
3. Open Filemon's file monitoring. Click on the secondary link in the initial page in IE
(
Http://loclahost/webapp/iserr.dll/custumoerlist), "Server Internal Error" will appear.
4. Switch to Filemon, you will find "Access Rejected" when DllHost.exe accesses C: /PDoxUser.net.
5, find PDOXUser.net, add the Internet guest account to the access list and allow its read and write permissions.
6. Open DCMCNFG.EXE, close the "running program" IIS related content. Then, re-click the initial two-level link in IE, everything is OK!
Reason for problems:
iServer.dll is generated using the Parodox database for its page. Since the application reads and writes the PDOXUser.net file when accessing the Parodox database, the PDOXUSER.NET file can be read properly to become a premise for the application. In Windows XP, IIS servers typically use the host / IUSR_HOST account to access resources (Host is the name of the computer), and the local permissions of the account are very limited, which can only read the resources in the IIS corresponding virtual directory. PDOXUser.net is typically placed in a C: plate root directory (you can also move), and the Host / IUSR_HOST account is not accessible by default, so ISERVER.DLL is rejected through the BDE engine during the run. In IE, please make a prompt "server internal error HTTP 500). Kunlun in April 2005 in Urumqi
