-
Posted to
IIS 7 - Troubleshooting
by
zdenek
on
01-07-2009, 2:15 PM
how about adding something like:
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<system.webServer>
<handlers accessPolicy="Read, Script" />
</system.webServer>
</configuration>
Chances are you do not have ...
-
Posted to
IIS7 - Classic ASP
by
zdenek
on
01-07-2009, 12:56 PM
any warnings in event viewer? usually these log information so if you can find some, that would be a good start
-
Posted to
IIS 7 - Troubleshooting
by
zdenek
on
01-07-2009, 12:54 PM
it restarts the underlying IIS admin service which has usually HTTP SSL, Simple Mail Transfer Protocol (if installed) and world wide web publishing service as dependents and they restart as well.
During the restart essentially all dlls loaded as well as all resources (including DB connections and Soap connection pools) are disposed. It's ...
-
Posted to
IIS 7 - ASP.NET Administration
by
zdenek
on
01-07-2009, 10:38 AM
Interestingly enough now the ajax extensions work even in integrated framework when using precompiled application.Try to deploy the website project rather than copy the files and it should include dependencies.
-
Posted to
IIS 7 - Troubleshooting
by
zdenek
on
01-07-2009, 10:32 AM
It has been a week with no error. I checked through the source changes and there were a few so someone tested this on IIS 7 and corrected the iis specific issues. It seems that there may have been a slight change in memory handling in this version and that would explain why dll that worked on 5 & 6 was causing heap issues.
-
Posted to
IIS 7 - Troubleshooting
by
zdenek
on
12-29-2008, 6:22 PM
The pool that I'm using was native pool with isapi dll from tomcat jakarta project. While the dll works great under 5/6, it may have been allocating memory in incompatible format or in a way that IIS7 does not like. I upgraded the DLL today on the machine because I saw that a lot of changes went into main source of the isapi plugin in last few ...
-
Posted to
IIS 7 - Troubleshooting
by
zdenek
on
12-29-2008, 8:41 AM
This is on my personal server and I'm not sure whether that kind of support is part of the 2008 Web Edition OEM or not. I certainly would not want to pay for it, i'd rather wait until it is resolved by someone else if it is not included. The licensing is way too complicated for person like me to parse and figure out what kind of support is ...
-
Posted to
IIS 7 - Troubleshooting
by
zdenek
on
12-25-2008, 12:27 PM
the errors coincide with IIS warnings:
A process serving application pool 'insert_pool_name_here' suffered a fatal communication error with the Windows Process Activation Service. The process id was '4844'. The data field contains the error number.
the detail only contains one 4 byte word: 8007006D - i gather that would ...
-
Posted to
IIS 7 - Troubleshooting
by
zdenek
on
12-25-2008, 11:22 AM
I'm getting in my logs mostly 374:
Faulting application w3wp.exe, version 7.0.6001.18000, time stamp 0x47919413, faulting module ntdll.dll, version 6.0.6001.18000, time stamp 0x4791a7a6, exception code 0xc0000374, fault offset 0x000b015d, process id 0x12ec, application start time 0x01c96694475a2dc0.
I did apply originally KB956120 ...
-
Posted to
IIS 7.0 - PowerShell
by
zdenek
on
12-15-2008, 10:30 AM
[quote user="zdenek"] because the powershell 1 is installed when SQL 2008 [/quote]
Actually I was wrong about this one. Although SQL Server 2008 requires powershell 1, it comes with windows 2008 according to some docs i found on microsoft website.
I will still investigate further to see if I can get it all working under PowerShell 1 ...