IIS 7 in VISTA Home Premium

IIS 7 in VISTA Home Premium

Posted by admin on Dec 28th, 2006

Responses

1. anonymous Says:
   Jan 3rd, 2007 at 09:40 am

   Hi,Like IIS in previous Win versions, you need to have an index or default page created before the system will recognize it as a valid host. If I recall correctly, there was also an issue with php, but I don't know if that was resolved with v7. First set up the page, see what happens. Best of Luck,Rick Rogers, aka "Nutcase" Microsoft MVP mvp.support.microsoft.com/ Windows help www.rickrogers.org"Nadanakeerthi"

2. anonymous Says:
   Jan 5th, 2007 at 10:55 am

   Thanks for the response. i already put test.php page inside my inetpub/wwwroot/ folder after that i try on my internet explore type in ULR localhost/test.php i get an error Server ErrorHTTP Error 500.0 Internal Server Error Description: Module "FailedRequestsTracingModule" could not be found Error Code: 0x80070002 Notification: BeginRequest Module: IIS Web Core Requested URL: localhost:80/phpmyadmin/index.php Physical Path: C:\inetpub\wwwroot\phpmyadmin\index.php Logon User: Not yet determined Logon Method: Not yet determined Handler: Not yet determined Most likely causes: The module could not be found. IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred. IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly. IIS was not able to process configuration for the Web site or application. The authenticated user does not have permission to use this DLL. What you can try: Verify that the module name is not misspelled in the configuration/system.webServer/globalModules config section. The error description may contain additional information to help you determine which module is causing the error. Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account. Check the event logs to see if any additional information was logged. Verify the permissions for the DLL. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here. that link is this iis.net/default.aspx?tabid=2&subtabid=25&i=969&p=1 i read that artical and i try to follow that but i create FailedRequestsTracingModule but it is not appear in Default Web Site configure pane i don't know why please help "Rick Rogers" wrote:

3. anonymous Says:
   Jan 9th, 2007 at 06:14 am

   Hi,It has to be named default or index. Best of Luck,Rick Rogers, aka "Nutcase" Microsoft MVP mvp.support.microsoft.com/ Windows help www.rickrogers.org"Nadanakeerthi"

4. anonymous Says:
   Jan 13th, 2007 at 04:38 am

   I rather think he has a problem with the web.config file. Set the impersonate value to false "Rick Rogers" schrieb im Newsbeitrag

5. anonymous Says:
   Jan 17th, 2007 at 02:01 pm

   thanks for the reply, but i dont know hoe to do the web.config and set the impersonate value to false. please explean more."Richard Stallmann" wrote:

Leave a Reply