IIS 6.0 keeps restarting itself

Steve,
You mentioned that it works for a day and then freaked out. Did you try to
go to the Command Prompt and try the IISReset Command. What happens when you
do this. Does the application start working.

I would first check the Application Pool Recycling settings in IIS

See if you can log this http://support.microsoft.com/kb/332088 in the
Eventlog
and see if it coincides with the time when IWP stops serving through IIS.

Regards,

Trevor Benedict
MCSD

"Steve-o" <stevenmartin@hotmailDOTcom> wrote in message
news:342BCE98-2330-40E5-9E6F-7F0B9BCC1B73@microsoft.com...
>I have a strange problem that I just can't figure out. First of all let me
>say that I have a bit of experience with Server 2003 but not a lot with
>IIS. I have a client that uses Filemaker for several databases that they
>use in their office. Filemaker has a feature that makes databases available
>to people via a browser called "Instant Web Publishing" (IWP). Well, this
>IWP makes use of IIS in order to publish these databases. The only
>requirement for IIS to work for filemaker is basically to make sure that
>anonymous access is enabled. So, I installed IIS and made sure that
>anonymous access was enabled. Then I installed Filemaker Server and told it
>to use IIS for the IWP. Everything went smoothly and it was serving up the
>Filemaker databases just beautifully for almost 24 hours. The next day at
>about noon it all blew up and stopped working completely. Anything that was
>made available via IWP wouldn't show up at all although Filemaker Server
>still functioned fine for everything else it does. IIS wouldn't even show
>its default web page. So I uninstalled and re-installed IIS and we could
>then see the default web page so it appeared that IIS was again functioning
>properly. But, whenever I tell Filemaker to use IIS, IIS freaks out and
>restarts itself and Filemaker comes back with an error saying it is unable
>to communicate with IIS.
>
> I can provide logs if someone can tell me which ones you need and where to
> find them. I am open to calling anyone that has good experience with IIS.
> I also would mind paying you for your help if we can solve this problem.
>
> Thanks,
>
> Steve
 >> Stay informed about: IIS 6.0 keeps restarting itself 

Thanks for responding. I have just run the IISReset command but will not be
able to test it until after hours today as Filemaker Server must be stopped
on the temporary machine before I can test it out on this server. Hopefully
that fizes things.

Also, I checked out the Application Pool Recycling settings by right
clicking the Application Pools and choosing properties (is that the right
place). The setting are:

On Tab "Recycling"
Recycle Worker Processes in munites: 1740
No other checkboxes checked

On tab "Performance"
(Idle Timeout) Shutdown worker processes after being idle for (in minutes):
20
(Request queue limit) Limit the kernel request queue (number of requests):
1000
(web garden) Maximum number of worker processes: 1
No other checkboxes checked

On tab "Health"
(Enable Pinging) Ping worker processes every (in seconds): 30
(Enable Rapid Fail Protection) Disable the application pool if there are a
certain number of worker process failures within a specified time period:
Failures: 5, Time Perios (in minutes): 5
(Startup time limit) Worker processes must start within (Time in seconds):
90
(Shutdown Time limit) Worker process must shut down within (time in
seconds): 90

Do you see any of these settings that should be changed and if so do I turn
them off or just change the values? Let me know. I really appreciate your
help.

Steve.

"Trevor Benedict" <trevornews DeleteThis @gmail.com> wrote in message
news:OJz02P0bIHA.4196@TK2MSFTNGP04.phx.gbl...
> Steve,
> You mentioned that it works for a day and then freaked out. Did you try to
> go to the Command Prompt and try the IISReset Command. What happens when
> you do this. Does the application start working.
>
> I would first check the Application Pool Recycling settings in IIS
>
> See if you can log this http://support.microsoft.com/kb/332088 in the
> Eventlog
> and see if it coincides with the time when IWP stops serving through IIS.
>
> Regards,
>
> Trevor Benedict
> MCSD
>
> "Steve-o" <stevenmartin@hotmailDOTcom> wrote in message
> news:342BCE98-2330-40E5-9E6F-7F0B9BCC1B73@microsoft.com...
>>I have a strange problem that I just can't figure out. First of all let me
>>say that I have a bit of experience with Server 2003 but not a lot with
>>IIS. I have a client that uses Filemaker for several databases that they
>>use in their office. Filemaker has a feature that makes databases
>>available to people via a browser called "Instant Web Publishing" (IWP).
>>Well, this IWP makes use of IIS in order to publish these databases. The
>>only requirement for IIS to work for filemaker is basically to make sure
>>that anonymous access is enabled. So, I installed IIS and made sure that
>>anonymous access was enabled. Then I installed Filemaker Server and told
>>it to use IIS for the IWP. Everything went smoothly and it was serving up
>>the Filemaker databases just beautifully for almost 24 hours. The next day
>>at about noon it all blew up and stopped working completely. Anything that
>>was made available via IWP wouldn't show up at all although Filemaker
>>Server still functioned fine for everything else it does. IIS wouldn't
>>even show its default web page. So I uninstalled and re-installed IIS and
>>we could then see the default web page so it appeared that IIS was again
>>functioning properly. But, whenever I tell Filemaker to use IIS, IIS
>>freaks out and restarts itself and Filemaker comes back with an error
>>saying it is unable to communicate with IIS.
>>
>> I can provide logs if someone can tell me which ones you need and where
>> to find them. I am open to calling anyone that has good experience with
>> IIS. I also would mind paying you for your help if we can solve this
>> problem.
>>
>> Thanks,
>>
>> Steve
>
>
 >> Stay informed about: IIS 6.0 keeps restarting itself 

Steve,
We still don't know if the Process Recycle is the issue, but it is worth
checking. Remember to take screen shots of whatever you have before you make
this change so that you can rollback if you like to.

Under the Recycling Tab, uncheck the "Recycle Worker Process in minutes"
option. DO NOT CHANGE any of the values in the Checkbox. Rolling back will
be easier for you.

Under the Performance Tab, uncheck Shutdown worker processes after being
idle for (in minutes).

Click on OK.

You can also test this without making all these changes. Stop and restart
your IWP Server & IIS. Then make sure the IWP is working. Right click on the
Application Pool that is hosting the website and Click on Recycle. If IWP
stops working after a couple of minutes (few minutes for the process to
recycle), then we will know if this is the culprit. Post your findings here.
There are others who monitor this thread too and will probably have some
idea as to how to further isolate this issue.

Some material for you to read if you like
http://msdn2.microsoft.com/en-us/library/aa719533(VS.71).aspx

Regards,

Trevor Benedict
MCSD


"Steve-o" <stevenmartin@hotmailDOTcom> wrote in message
news:E0F3394B-2085-446B-9628-BA9BD6533E6D@microsoft.com...
> Thanks for responding. I have just run the IISReset command but will not
> be able to test it until after hours today as Filemaker Server must be
> stopped on the temporary machine before I can test it out on this server.
> Hopefully that fizes things.
>
> Also, I checked out the Application Pool Recycling settings by right
> clicking the Application Pools and choosing properties (is that the right
> place). The setting are:
>
> On Tab "Recycling"
> Recycle Worker Processes in munites: 1740
> No other checkboxes checked
>
> On tab "Performance"
> (Idle Timeout) Shutdown worker processes after being idle for (in
> minutes): 20
> (Request queue limit) Limit the kernel request queue (number of requests):
> 1000
> (web garden) Maximum number of worker processes: 1
> No other checkboxes checked
>
> On tab "Health"
> (Enable Pinging) Ping worker processes every (in seconds): 30
> (Enable Rapid Fail Protection) Disable the application pool if there are a
> certain number of worker process failures within a specified time period:
> Failures: 5, Time Perios (in minutes): 5
> (Startup time limit) Worker processes must start within (Time in seconds):
> 90
> (Shutdown Time limit) Worker process must shut down within (time in
> seconds): 90
>
> Do you see any of these settings that should be changed and if so do I
> turn them off or just change the values? Let me know. I really appreciate
> your help.
>
> Steve.
>
> "Trevor Benedict" <trevornews.RemoveThis@gmail.com> wrote in message
> news:OJz02P0bIHA.4196@TK2MSFTNGP04.phx.gbl...
>> Steve,
>> You mentioned that it works for a day and then freaked out. Did you try
>> to go to the Command Prompt and try the IISReset Command. What happens
>> when you do this. Does the application start working.
>>
>> I would first check the Application Pool Recycling settings in IIS
>>
>> See if you can log this http://support.microsoft.com/kb/332088 in the
>> Eventlog
>> and see if it coincides with the time when IWP stops serving through IIS.
>>
>> Regards,
>>
>> Trevor Benedict
>> MCSD
>>
>> "Steve-o" <stevenmartin@hotmailDOTcom> wrote in message
>> news:342BCE98-2330-40E5-9E6F-7F0B9BCC1B73@microsoft.com...
>>>I have a strange problem that I just can't figure out. First of all let
>>>me say that I have a bit of experience with Server 2003 but not a lot
>>>with IIS. I have a client that uses Filemaker for several databases that
>>>they use in their office. Filemaker has a feature that makes databases
>>>available to people via a browser called "Instant Web Publishing" (IWP).
>>>Well, this IWP makes use of IIS in order to publish these databases. The
>>>only requirement for IIS to work for filemaker is basically to make sure
>>>that anonymous access is enabled. So, I installed IIS and made sure that
>>>anonymous access was enabled. Then I installed Filemaker Server and told
>>>it to use IIS for the IWP. Everything went smoothly and it was serving up
>>>the Filemaker databases just beautifully for almost 24 hours. The next
>>>day at about noon it all blew up and stopped working completely. Anything
>>>that was made available via IWP wouldn't show up at all although
>>>Filemaker Server still functioned fine for everything else it does. IIS
>>>wouldn't even show its default web page. So I uninstalled and
>>>re-installed IIS and we could then see the default web page so it
>>>appeared that IIS was again functioning properly. But, whenever I tell
>>>Filemaker to use IIS, IIS freaks out and restarts itself and Filemaker
>>>comes back with an error saying it is unable to communicate with IIS.
>>>
>>> I can provide logs if someone can tell me which ones you need and where
>>> to find them. I am open to calling anyone that has good experience with
>>> IIS. I also would mind paying you for your help if we can solve this
>>> problem.
>>>
>>> Thanks,
>>>
>>> Steve
>>
>>
>
 >> Stay informed about: IIS 6.0 keeps restarting itself 

Ok the IISReset didn't really do anything. Whenever I try to tell Filemaker
Server to talk to IIS, several errors are logged in the System event log.
They are:

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7034
Date: 2/14/2008
Time: 11:16:55 PM
User: N/A
Computer: MEDSOURCE2
Description:
The IIS Admin Service service terminated unexpectedly. It has done this 17
time(s).

And:

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7034
Date: 2/14/2008
Time: 11:16:55 PM
User: N/A
Computer: MEDSOURCE2
Description:
The World Wide Web Publishing Service service terminated unexpectedly. It
has done this 17 time(s).

Then:

Event Type: Information
Event Source: IISCTLS
Event Category: None
Event ID: 4
Date: 2/14/2008
Time: 11:16:56 PM
User: N/A
Computer: MEDSOURCE2
Description:
IIS kill command received from user NT AUTHORITY\SYSTEM. The logged data is
the status code.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 ....

And:

Event Type: Information
Event Source: IISCTLS
Event Category: None
Event ID: 2
Date: 2/14/2008
Time: 11:16:56 PM
User: N/A
Computer: MEDSOURCE2
Description:
IIS stop command received from user NT AUTHORITY\SYSTEM. The logged data is
the status code.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 ....

There are more as well basically this received a stop control and then it
goes through and starts them all back up. Any other ideas? I have tried
uninstalling IIS and re-installing with no success. I'm sure it is the
littlest dumbest thing but I can't figure it out. Let me know if you have
any fresh ideas.

Thanks,
Steve



"Steve-o" <stevenmartin@hotmailDOTcom> wrote in message
news:E0F3394B-2085-446B-9628-BA9BD6533E6D@microsoft.com...
> Thanks for responding. I have just run the IISReset command but will not
> be able to test it until after hours today as Filemaker Server must be
> stopped on the temporary machine before I can test it out on this server.
> Hopefully that fizes things.
>
> Also, I checked out the Application Pool Recycling settings by right
> clicking the Application Pools and choosing properties (is that the right
> place). The setting are:
>
> On Tab "Recycling"
> Recycle Worker Processes in munites: 1740
> No other checkboxes checked
>
> On tab "Performance"
> (Idle Timeout) Shutdown worker processes after being idle for (in
> minutes): 20
> (Request queue limit) Limit the kernel request queue (number of requests):
> 1000
> (web garden) Maximum number of worker processes: 1
> No other checkboxes checked
>
> On tab "Health"
> (Enable Pinging) Ping worker processes every (in seconds): 30
> (Enable Rapid Fail Protection) Disable the application pool if there are a
> certain number of worker process failures within a specified time period:
> Failures: 5, Time Perios (in minutes): 5
> (Startup time limit) Worker processes must start within (Time in seconds):
> 90
> (Shutdown Time limit) Worker process must shut down within (time in
> seconds): 90
>
> Do you see any of these settings that should be changed and if so do I
> turn them off or just change the values? Let me know. I really appreciate
> your help.
>
> Steve.
>
> "Trevor Benedict" <trevornews.RemoveThis@gmail.com> wrote in message
> news:OJz02P0bIHA.4196@TK2MSFTNGP04.phx.gbl...
>> Steve,
>> You mentioned that it works for a day and then freaked out. Did you try
>> to go to the Command Prompt and try the IISReset Command. What happens
>> when you do this. Does the application start working.
>>
>> I would first check the Application Pool Recycling settings in IIS
>>
>> See if you can log this http://support.microsoft.com/kb/332088 in the
>> Eventlog
>> and see if it coincides with the time when IWP stops serving through IIS.
>>
>> Regards,
>>
>> Trevor Benedict
>> MCSD
>>
>> "Steve-o" <stevenmartin@hotmailDOTcom> wrote in message
>> news:342BCE98-2330-40E5-9E6F-7F0B9BCC1B73@microsoft.com...
>>>I have a strange problem that I just can't figure out. First of all let
>>>me say that I have a bit of experience with Server 2003 but not a lot
>>>with IIS. I have a client that uses Filemaker for several databases that
>>>they use in their office. Filemaker has a feature that makes databases
>>>available to people via a browser called "Instant Web Publishing" (IWP).
>>>Well, this IWP makes use of IIS in order to publish these databases. The
>>>only requirement for IIS to work for filemaker is basically to make sure
>>>that anonymous access is enabled. So, I installed IIS and made sure that
>>>anonymous access was enabled. Then I installed Filemaker Server and told
>>>it to use IIS for the IWP. Everything went smoothly and it was serving up
>>>the Filemaker databases just beautifully for almost 24 hours. The next
>>>day at about noon it all blew up and stopped working completely. Anything
>>>that was made available via IWP wouldn't show up at all although
>>>Filemaker Server still functioned fine for everything else it does. IIS
>>>wouldn't even show its default web page. So I uninstalled and
>>>re-installed IIS and we could then see the default web page so it
>>>appeared that IIS was again functioning properly. But, whenever I tell
>>>Filemaker to use IIS, IIS freaks out and restarts itself and Filemaker
>>>comes back with an error saying it is unable to communicate with IIS.
>>>
>>> I can provide logs if someone can tell me which ones you need and where
>>> to find them. I am open to calling anyone that has good experience with
>>> IIS. I also would mind paying you for your help if we can solve this
>>> problem.
>>>
>>> Thanks,
>>>
>>> Steve
>>
>>
>
 >> Stay informed about: IIS 6.0 keeps restarting itself 

I currently have Filemaker Server running on an old XP Pro box as a
temporary solution while I figure out this servers problem. IWP is running
fine on it. It has IIS version 5.1 while the server has IIS version 6. Just
comparing a few things, there is not an asp.net tab on the XP Pro box within
the properties of the default Web Site. There is also no Application Pools
on the XP Pro box, and under "home directory" in the web site properties,
the XP Pro box has "Application Protection" set to "Medium (Pooled)". The
server 03 box has "Application Pool" set to "DefaultAppPool". Anyway,
hopefully that gives someone enough information to at least help me look at
something else.

"Steve-o" <stevenmartin@hotmailDOTcom> wrote in message
news:752C4859-E061-409D-9812-188EB4CE1757@microsoft.com...
> Ok the IISReset didn't really do anything. Whenever I try to tell
> Filemaker Server to talk to IIS, several errors are logged in the System
> event log. They are:
>
> Event Type: Error
> Event Source: Service Control Manager
> Event Category: None
> Event ID: 7034
> Date: 2/14/2008
> Time: 11:16:55 PM
> User: N/A
> Computer: MEDSOURCE2
> Description:
> The IIS Admin Service service terminated unexpectedly. It has done this
> 17 time(s).
>
> And:
>
> Event Type: Error
> Event Source: Service Control Manager
> Event Category: None
> Event ID: 7034
> Date: 2/14/2008
> Time: 11:16:55 PM
> User: N/A
> Computer: MEDSOURCE2
> Description:
> The World Wide Web Publishing Service service terminated unexpectedly. It
> has done this 17 time(s).
>
> Then:
>
> Event Type: Information
> Event Source: IISCTLS
> Event Category: None
> Event ID: 4
> Date: 2/14/2008
> Time: 11:16:56 PM
> User: N/A
> Computer: MEDSOURCE2
> Description:
> IIS kill command received from user NT AUTHORITY\SYSTEM. The logged data
> is the status code.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 00 00 00 00 ....
>
> And:
>
> Event Type: Information
> Event Source: IISCTLS
> Event Category: None
> Event ID: 2
> Date: 2/14/2008
> Time: 11:16:56 PM
> User: N/A
> Computer: MEDSOURCE2
> Description:
> IIS stop command received from user NT AUTHORITY\SYSTEM. The logged data
> is the status code.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 00 00 00 00 ....
>
> There are more as well basically this received a stop control and then it
> goes through and starts them all back up. Any other ideas? I have tried
> uninstalling IIS and re-installing with no success. I'm sure it is the
> littlest dumbest thing but I can't figure it out. Let me know if you have
> any fresh ideas.
>
> Thanks,
> Steve
>
>
>
> "Steve-o" <stevenmartin@hotmailDOTcom> wrote in message
> news:E0F3394B-2085-446B-9628-BA9BD6533E6D@microsoft.com...
>> Thanks for responding. I have just run the IISReset command but will not
>> be able to test it until after hours today as Filemaker Server must be
>> stopped on the temporary machine before I can test it out on this server.
>> Hopefully that fizes things.
>>
>> Also, I checked out the Application Pool Recycling settings by right
>> clicking the Application Pools and choosing properties (is that the right
>> place). The setting are:
>>
>> On Tab "Recycling"
>> Recycle Worker Processes in munites: 1740
>> No other checkboxes checked
>>
>> On tab "Performance"
>> (Idle Timeout) Shutdown worker processes after being idle for (in
>> minutes): 20
>> (Request queue limit) Limit the kernel request queue (number of
>> requests): 1000
>> (web garden) Maximum number of worker processes: 1
>> No other checkboxes checked
>>
>> On tab "Health"
>> (Enable Pinging) Ping worker processes every (in seconds): 30
>> (Enable Rapid Fail Protection) Disable the application pool if there are
>> a certain number of worker process failures within a specified time
>> period: Failures: 5, Time Perios (in minutes): 5
>> (Startup time limit) Worker processes must start within (Time in
>> seconds): 90
>> (Shutdown Time limit) Worker process must shut down within (time in
>> seconds): 90
>>
>> Do you see any of these settings that should be changed and if so do I
>> turn them off or just change the values? Let me know. I really appreciate
>> your help.
>>
>> Steve.
>>
>> "Trevor Benedict" <trevornews RemoveThis @gmail.com> wrote in message
>> news:OJz02P0bIHA.4196@TK2MSFTNGP04.phx.gbl...
>>> Steve,
>>> You mentioned that it works for a day and then freaked out. Did you try
>>> to go to the Command Prompt and try the IISReset Command. What happens
>>> when you do this. Does the application start working.
>>>
>>> I would first check the Application Pool Recycling settings in IIS
>>>
>>> See if you can log this http://support.microsoft.com/kb/332088 in the
>>> Eventlog
>>> and see if it coincides with the time when IWP stops serving through
>>> IIS.
>>>
>>> Regards,
>>>
>>> Trevor Benedict
>>> MCSD
>>>
>>> "Steve-o" <stevenmartin@hotmailDOTcom> wrote in message
>>> news:342BCE98-2330-40E5-9E6F-7F0B9BCC1B73@microsoft.com...
>>>>I have a strange problem that I just can't figure out. First of all let
>>>>me say that I have a bit of experience with Server 2003 but not a lot
>>>>with IIS. I have a client that uses Filemaker for several databases that
>>>>they use in their office. Filemaker has a feature that makes databases
>>>>available to people via a browser called "Instant Web Publishing" (IWP).
>>>>Well, this IWP makes use of IIS in order to publish these databases. The
>>>>only requirement for IIS to work for filemaker is basically to make sure
>>>>that anonymous access is enabled. So, I installed IIS and made sure that
>>>>anonymous access was enabled. Then I installed Filemaker Server and told
>>>>it to use IIS for the IWP. Everything went smoothly and it was serving
>>>>up the Filemaker databases just beautifully for almost 24 hours. The
>>>>next day at about noon it all blew up and stopped working completely.
>>>>Anything that was made available via IWP wouldn't show up at all
>>>>although Filemaker Server still functioned fine for everything else it
>>>>does. IIS wouldn't even show its default web page. So I uninstalled and
>>>>re-installed IIS and we could then see the default web page so it
>>>>appeared that IIS was again functioning properly. But, whenever I tell
>>>>Filemaker to use IIS, IIS freaks out and restarts itself and Filemaker
>>>>comes back with an error saying it is unable to communicate with IIS.
>>>>
>>>> I can provide logs if someone can tell me which ones you need and where
>>>> to find them. I am open to calling anyone that has good experience with
>>>> IIS. I also would mind paying you for your help if we can solve this
>>>> problem.
>>>>
>>>> Thanks,
>>>>
>>>> Steve
>>>
>>>
>>
>
 >> Stay informed about: IIS 6.0 keeps restarting itself 

Tried all of the below suggestions to no avail. Still can't get Filemaker
Server IWP to communicate with IIS. Just knocks it out whenever it tries. I
also added some more details in another post.

"Trevor Benedict" <trevornews.TakeThisOut@gmail.com> wrote in message
news:uuBIgx2bIHA.5888@TK2MSFTNGP02.phx.gbl...
> Steve,
> We still don't know if the Process Recycle is the issue, but it is worth
> checking. Remember to take screen shots of whatever you have before you
> make this change so that you can rollback if you like to.
>
> Under the Recycling Tab, uncheck the "Recycle Worker Process in minutes"
> option. DO NOT CHANGE any of the values in the Checkbox. Rolling back will
> be easier for you.
>
> Under the Performance Tab, uncheck Shutdown worker processes after being
> idle for (in minutes).
>
> Click on OK.
>
> You can also test this without making all these changes. Stop and restart
> your IWP Server & IIS. Then make sure the IWP is working. Right click on
> the Application Pool that is hosting the website and Click on Recycle. If
> IWP stops working after a couple of minutes (few minutes for the process
> to recycle), then we will know if this is the culprit. Post your findings
> here. There are others who monitor this thread too and will probably have
> some idea as to how to further isolate this issue.
>
> Some material for you to read if you like
> http://msdn2.microsoft.com/en-us/library/aa719533(VS.71).aspx
>
> Regards,
>
> Trevor Benedict
> MCSD
>
>
> "Steve-o" <stevenmartin@hotmailDOTcom> wrote in message
> news:E0F3394B-2085-446B-9628-BA9BD6533E6D@microsoft.com...
>> Thanks for responding. I have just run the IISReset command but will not
>> be able to test it until after hours today as Filemaker Server must be
>> stopped on the temporary machine before I can test it out on this server.
>> Hopefully that fizes things.
>>
>> Also, I checked out the Application Pool Recycling settings by right
>> clicking the Application Pools and choosing properties (is that the right
>> place). The setting are:
>>
>> On Tab "Recycling"
>> Recycle Worker Processes in munites: 1740
>> No other checkboxes checked
>>
>> On tab "Performance"
>> (Idle Timeout) Shutdown worker processes after being idle for (in
>> minutes): 20
>> (Request queue limit) Limit the kernel request queue (number of
>> requests): 1000
>> (web garden) Maximum number of worker processes: 1
>> No other checkboxes checked
>>
>> On tab "Health"
>> (Enable Pinging) Ping worker processes every (in seconds): 30
>> (Enable Rapid Fail Protection) Disable the application pool if there are
>> a certain number of worker process failures within a specified time
>> period: Failures: 5, Time Perios (in minutes): 5
>> (Startup time limit) Worker processes must start within (Time in
>> seconds): 90
>> (Shutdown Time limit) Worker process must shut down within (time in
>> seconds): 90
>>
>> Do you see any of these settings that should be changed and if so do I
>> turn them off or just change the values? Let me know. I really appreciate
>> your help.
>>
>> Steve.
>>
>> "Trevor Benedict" <trevornews.TakeThisOut@gmail.com> wrote in message
>> news:OJz02P0bIHA.4196@TK2MSFTNGP04.phx.gbl...
>>> Steve,
>>> You mentioned that it works for a day and then freaked out. Did you try
>>> to go to the Command Prompt and try the IISReset Command. What happens
>>> when you do this. Does the application start working.
>>>
>>> I would first check the Application Pool Recycling settings in IIS
>>>
>>> See if you can log this http://support.microsoft.com/kb/332088 in the
>>> Eventlog
>>> and see if it coincides with the time when IWP stops serving through
>>> IIS.
>>>
>>> Regards,
>>>
>>> Trevor Benedict
>>> MCSD
>>>
>>> "Steve-o" <stevenmartin@hotmailDOTcom> wrote in message
>>> news:342BCE98-2330-40E5-9E6F-7F0B9BCC1B73@microsoft.com...
>>>>I have a strange problem that I just can't figure out. First of all let
>>>>me say that I have a bit of experience with Server 2003 but not a lot
>>>>with IIS. I have a client that uses Filemaker for several databases that
>>>>they use in their office. Filemaker has a feature that makes databases
>>>>available to people via a browser called "Instant Web Publishing" (IWP).
>>>>Well, this IWP makes use of IIS in order to publish these databases. The
>>>>only requirement for IIS to work for filemaker is basically to make sure
>>>>that anonymous access is enabled. So, I installed IIS and made sure that
>>>>anonymous access was enabled. Then I installed Filemaker Server and told
>>>>it to use IIS for the IWP. Everything went smoothly and it was serving
>>>>up the Filemaker databases just beautifully for almost 24 hours. The
>>>>next day at about noon it all blew up and stopped working completely.
>>>>Anything that was made available via IWP wouldn't show up at all
>>>>although Filemaker Server still functioned fine for everything else it
>>>>does. IIS wouldn't even show its default web page. So I uninstalled and
>>>>re-installed IIS and we could then see the default web page so it
>>>>appeared that IIS was again functioning properly. But, whenever I tell
>>>>Filemaker to use IIS, IIS freaks out and restarts itself and Filemaker
>>>>comes back with an error saying it is unable to communicate with IIS.
>>>>
>>>> I can provide logs if someone can tell me which ones you need and where
>>>> to find them. I am open to calling anyone that has good experience with
>>>> IIS. I also would mind paying you for your help if we can solve this
>>>> problem.
>>>>
>>>> Thanks,
>>>>
>>>> Steve
>>>
>>>
>>
>
>
 >> Stay informed about: IIS 6.0 keeps restarting itself 

Well, if anyone is interested, I think I have finally found the solution
although I did several things and am not 100% certain which one was the
answer although I have an idea. I told IIS to run as if it was the 5.0
version, kind of like compatibility mode in XP. But what I think was the
real cuplrit is the default Internet user account or anonymous Internet user
account. Not sure what happened but when IIS freaked out, Filemaker could
never communicate with it again. I changed the rights on the directory that
Filemaker uses and bingo Filemaker could talk to IIS again. After that I
started having access rights issues when we would try to actually open a
database through IE. Anyway, to make a long story short, I created a new
anonymous Internet user account and told IIS to use it instead and then told
windows to allow this new user to have rights on the various folders and
sites that it needed, and bingo, everything was back to normal. I still wish
I knew what it was that made IIS blow up in the first place. One monute it
was working fine, and then without anyone being logged into the server or
anything, it just stops working. Very strange. Anyway, I appreciate your
help, it didn't provide me an answer but it gave me places to look and that
is very much appreciated.

"Steve-o" <stevenmartin@hotmailDOTcom> wrote in message
news:55BBB673-4F20-4830-9A5E-EDD131772FF2@microsoft.com...
>I currently have Filemaker Server running on an old XP Pro box as a
>temporary solution while I figure out this servers problem. IWP is running
>fine on it. It has IIS version 5.1 while the server has IIS version 6. Just
>comparing a few things, there is not an asp.net tab on the XP Pro box
>within the properties of the default Web Site. There is also no Application
>Pools on the XP Pro box, and under "home directory" in the web site
>properties, the XP Pro box has "Application Protection" set to "Medium
>(Pooled)". The server 03 box has "Application Pool" set to
>"DefaultAppPool". Anyway, hopefully that gives someone enough information
>to at least help me look at something else.
>
> "Steve-o" <stevenmartin@hotmailDOTcom> wrote in message
> news:752C4859-E061-409D-9812-188EB4CE1757@microsoft.com...
>> Ok the IISReset didn't really do anything. Whenever I try to tell
>> Filemaker Server to talk to IIS, several errors are logged in the System
>> event log. They are:
>>
>> Event Type: Error
>> Event Source: Service Control Manager
>> Event Category: None
>> Event ID: 7034
>> Date: 2/14/2008
>> Time: 11:16:55 PM
>> User: N/A
>> Computer: MEDSOURCE2
>> Description:
>> The IIS Admin Service service terminated unexpectedly. It has done this
>> 17 time(s).
>>
>> And:
>>
>> Event Type: Error
>> Event Source: Service Control Manager
>> Event Category: None
>> Event ID: 7034
>> Date: 2/14/2008
>> Time: 11:16:55 PM
>> User: N/A
>> Computer: MEDSOURCE2
>> Description:
>> The World Wide Web Publishing Service service terminated unexpectedly.
>> It has done this 17 time(s).
>>
>> Then:
>>
>> Event Type: Information
>> Event Source: IISCTLS
>> Event Category: None
>> Event ID: 4
>> Date: 2/14/2008
>> Time: 11:16:56 PM
>> User: N/A
>> Computer: MEDSOURCE2
>> Description:
>> IIS kill command received from user NT AUTHORITY\SYSTEM. The logged data
>> is the status code.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>> Data:
>> 0000: 00 00 00 00 ....
>>
>> And:
>>
>> Event Type: Information
>> Event Source: IISCTLS
>> Event Category: None
>> Event ID: 2
>> Date: 2/14/2008
>> Time: 11:16:56 PM
>> User: N/A
>> Computer: MEDSOURCE2
>> Description:
>> IIS stop command received from user NT AUTHORITY\SYSTEM. The logged data
>> is the status code.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>> Data:
>> 0000: 00 00 00 00 ....
>>
>> There are more as well basically this received a stop control and then it
>> goes through and starts them all back up. Any other ideas? I have tried
>> uninstalling IIS and re-installing with no success. I'm sure it is the
>> littlest dumbest thing but I can't figure it out. Let me know if you have
>> any fresh ideas.
>>
>> Thanks,
>> Steve
>>
>>
>>
>> "Steve-o" <stevenmartin@hotmailDOTcom> wrote in message
>> news:E0F3394B-2085-446B-9628-BA9BD6533E6D@microsoft.com...
>>> Thanks for responding. I have just run the IISReset command but will not
>>> be able to test it until after hours today as Filemaker Server must be
>>> stopped on the temporary machine before I can test it out on this
>>> server. Hopefully that fizes things.
>>>
>>> Also, I checked out the Application Pool Recycling settings by right
>>> clicking the Application Pools and choosing properties (is that the
>>> right place). The setting are:
>>>
>>> On Tab "Recycling"
>>> Recycle Worker Processes in munites: 1740
>>> No other checkboxes checked
>>>
>>> On tab "Performance"
>>> (Idle Timeout) Shutdown worker processes after being idle for (in
>>> minutes): 20
>>> (Request queue limit) Limit the kernel request queue (number of
>>> requests): 1000
>>> (web garden) Maximum number of worker processes: 1
>>> No other checkboxes checked
>>>
>>> On tab "Health"
>>> (Enable Pinging) Ping worker processes every (in seconds): 30
>>> (Enable Rapid Fail Protection) Disable the application pool if there are
>>> a certain number of worker process failures within a specified time
>>> period: Failures: 5, Time Perios (in minutes): 5
>>> (Startup time limit) Worker processes must start within (Time in
>>> seconds): 90
>>> (Shutdown Time limit) Worker process must shut down within (time in
>>> seconds): 90
>>>
>>> Do you see any of these settings that should be changed and if so do I
>>> turn them off or just change the values? Let me know. I really
>>> appreciate your help.
>>>
>>> Steve.
>>>
>>> "Trevor Benedict" <trevornews.RemoveThis@gmail.com> wrote in message
>>> news:OJz02P0bIHA.4196@TK2MSFTNGP04.phx.gbl...
>>>> Steve,
>>>> You mentioned that it works for a day and then freaked out. Did you try
>>>> to go to the Command Prompt and try the IISReset Command. What happens
>>>> when you do this. Does the application start working.
>>>>
>>>> I would first check the Application Pool Recycling settings in IIS
>>>>
>>>> See if you can log this http://support.microsoft.com/kb/332088 in the
>>>> Eventlog
>>>> and see if it coincides with the time when IWP stops serving through
>>>> IIS.
>>>>
>>>> Regards,
>>>>
>>>> Trevor Benedict
>>>> MCSD
>>>>
>>>> "Steve-o" <stevenmartin@hotmailDOTcom> wrote in message
>>>> news:342BCE98-2330-40E5-9E6F-7F0B9BCC1B73@microsoft.com...
>>>>>I have a strange problem that I just can't figure out. First of all let
>>>>>me say that I have a bit of experience with Server 2003 but not a lot
>>>>>with IIS. I have a client that uses Filemaker for several databases
>>>>>that they use in their office. Filemaker has a feature that makes
>>>>>databases available to people via a browser called "Instant Web
>>>>>Publishing" (IWP). Well, this IWP makes use of IIS in order to publish
>>>>>these databases. The only requirement for IIS to work for filemaker is
>>>>>basically to make sure that anonymous access is enabled. So, I
>>>>>installed IIS and made sure that anonymous access was enabled. Then I
>>>>>installed Filemaker Server and told it to use IIS for the IWP.
>>>>>Everything went smoothly and it was serving up the Filemaker databases
>>>>>just beautifully for almost 24 hours. The next day at about noon it all
>>>>>blew up and stopped working completely. Anything that was made
>>>>>available via IWP wouldn't show up at all although Filemaker Server
>>>>>still functioned fine for everything else it does. IIS wouldn't even
>>>>>show its default web page. So I uninstalled and re-installed IIS and we
>>>>>could then see the default web page so it appeared that IIS was again
>>>>>functioning properly. But, whenever I tell Filemaker to use IIS, IIS
>>>>>freaks out and restarts itself and Filemaker comes back with an error
>>>>>saying it is unable to communicate with IIS.
>>>>>
>>>>> I can provide logs if someone can tell me which ones you need and
>>>>> where to find them. I am open to calling anyone that has good
>>>>> experience with IIS. I also would mind paying you for your help if we
>>>>> can solve this problem.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Steve
>>>>
>>>>
>>>
>>
>
 >> Stay informed about: IIS 6.0 keeps restarting itself 

Glad you got it to work. What I don't understand is that if it were a
permssion issue, it should not have worked for the first 24 hours too.

Regards,

Trevor Benedict
MCSD

"Steve-o" <stevenmartin@hotmailDOTcom> wrote in message
news:5D9594CA-7190-4E30-9CE9-A826C23D214E@microsoft.com...
> Well, if anyone is interested, I think I have finally found the solution
> although I did several things and am not 100% certain which one was the
> answer although I have an idea. I told IIS to run as if it was the 5.0
> version, kind of like compatibility mode in XP. But what I think was the
> real cuplrit is the default Internet user account or anonymous Internet
> user account. Not sure what happened but when IIS freaked out, Filemaker
> could never communicate with it again. I changed the rights on the
> directory that Filemaker uses and bingo Filemaker could talk to IIS again.
> After that I started having access rights issues when we would try to
> actually open a database through IE. Anyway, to make a long story short, I
> created a new anonymous Internet user account and told IIS to use it
> instead and then told windows to allow this new user to have rights on the
> various folders and sites that it needed, and bingo, everything was back
> to normal. I still wish I knew what it was that made IIS blow up in the
> first place. One monute it was working fine, and then without anyone being
> logged into the server or anything, it just stops working. Very strange.
> Anyway, I appreciate your help, it didn't provide me an answer but it gave
> me places to look and that is very much appreciated.
>
> "Steve-o" <stevenmartin@hotmailDOTcom> wrote in message
> news:55BBB673-4F20-4830-9A5E-EDD131772FF2@microsoft.com...
>>I currently have Filemaker Server running on an old XP Pro box as a
>>temporary solution while I figure out this servers problem. IWP is running
>>fine on it. It has IIS version 5.1 while the server has IIS version 6.
>>Just comparing a few things, there is not an asp.net tab on the XP Pro box
>>within the properties of the default Web Site. There is also no
>>Application Pools on the XP Pro box, and under "home directory" in the web
>>site properties, the XP Pro box has "Application Protection" set to
>>"Medium (Pooled)". The server 03 box has "Application Pool" set to
>>"DefaultAppPool". Anyway, hopefully that gives someone enough information
>>to at least help me look at something else.
>>
>> "Steve-o" <stevenmartin@hotmailDOTcom> wrote in message
>> news:752C4859-E061-409D-9812-188EB4CE1757@microsoft.com...
>>> Ok the IISReset didn't really do anything. Whenever I try to tell
>>> Filemaker Server to talk to IIS, several errors are logged in the System
>>> event log. They are:
>>>
>>> Event Type: Error
>>> Event Source: Service Control Manager
>>> Event Category: None
>>> Event ID: 7034
>>> Date: 2/14/2008
>>> Time: 11:16:55 PM
>>> User: N/A
>>> Computer: MEDSOURCE2
>>> Description:
>>> The IIS Admin Service service terminated unexpectedly. It has done this
>>> 17 time(s).
>>>
>>> And:
>>>
>>> Event Type: Error
>>> Event Source: Service Control Manager
>>> Event Category: None
>>> Event ID: 7034
>>> Date: 2/14/2008
>>> Time: 11:16:55 PM
>>> User: N/A
>>> Computer: MEDSOURCE2
>>> Description:
>>> The World Wide Web Publishing Service service terminated unexpectedly.
>>> It has done this 17 time(s).
>>>
>>> Then:
>>>
>>> Event Type: Information
>>> Event Source: IISCTLS
>>> Event Category: None
>>> Event ID: 4
>>> Date: 2/14/2008
>>> Time: 11:16:56 PM
>>> User: N/A
>>> Computer: MEDSOURCE2
>>> Description:
>>> IIS kill command received from user NT AUTHORITY\SYSTEM. The logged data
>>> is the status code.
>>>
>>> For more information, see Help and Support Center at
>>> http://go.microsoft.com/fwlink/events.asp.
>>> Data:
>>> 0000: 00 00 00 00 ....
>>>
>>> And:
>>>
>>> Event Type: Information
>>> Event Source: IISCTLS
>>> Event Category: None
>>> Event ID: 2
>>> Date: 2/14/2008
>>> Time: 11:16:56 PM
>>> User: N/A
>>> Computer: MEDSOURCE2
>>> Description:
>>> IIS stop command received from user NT AUTHORITY\SYSTEM. The logged data
>>> is the status code.
>>>
>>> For more information, see Help and Support Center at
>>> http://go.microsoft.com/fwlink/events.asp.
>>> Data:
>>> 0000: 00 00 00 00 ....
>>>
>>> There are more as well basically this received a stop control and then
>>> it goes through and starts them all back up. Any other ideas? I have
>>> tried uninstalling IIS and re-installing with no success. I'm sure it is
>>> the littlest dumbest thing but I can't figure it out. Let me know if you
>>> have any fresh ideas.
>>>
>>> Thanks,
>>> Steve
>>>
>>>
>>>
>>> "Steve-o" <stevenmartin@hotmailDOTcom> wrote in message
>>> news:E0F3394B-2085-446B-9628-BA9BD6533E6D@microsoft.com...
>>>> Thanks for responding. I have just run the IISReset command but will
>>>> not be able to test it until after hours today as Filemaker Server must
>>>> be stopped on the temporary machine before I can test it out on this
>>>> server. Hopefully that fizes things.
>>>>
>>>> Also, I checked out the Application Pool Recycling settings by right
>>>> clicking the Application Pools and choosing properties (is that the
>>>> right place). The setting are:
>>>>
>>>> On Tab "Recycling"
>>>> Recycle Worker Processes in munites: 1740
>>>> No other checkboxes checked
>>>>
>>>> On tab "Performance"
>>>> (Idle Timeout) Shutdown worker processes after being idle for (in
>>>> minutes): 20
>>>> (Request queue limit) Limit the kernel request queue (number of
>>>> requests): 1000
>>>> (web garden) Maximum number of worker processes: 1
>>>> No other checkboxes checked
>>>>
>>>> On tab "Health"
>>>> (Enable Pinging) Ping worker processes every (in seconds): 30
>>>> (Enable Rapid Fail Protection) Disable the application pool if there
>>>> are a certain number of worker process failures within a specified time
>>>> period: Failures: 5, Time Perios (in minutes): 5
>>>> (Startup time limit) Worker processes must start within (Time in
>>>> seconds): 90
>>>> (Shutdown Time limit) Worker process must shut down within (time in
>>>> seconds): 90
>>>>
>>>> Do you see any of these settings that should be changed and if so do I
>>>> turn them off or just change the values? Let me know. I really
>>>> appreciate your help.
>>>>
>>>> Steve.
>>>>
>>>> "Trevor Benedict" <trevornews DeleteThis @gmail.com> wrote in message
>>>> news:OJz02P0bIHA.4196@TK2MSFTNGP04.phx.gbl...
>>>>> Steve,
>>>>> You mentioned that it works for a day and then freaked out. Did you
>>>>> try to go to the Command Prompt and try the IISReset Command. What
>>>>> happens when you do this. Does the application start working.
>>>>>
>>>>> I would first check the Application Pool Recycling settings in IIS
>>>>>
>>>>> See if you can log this http://support.microsoft.com/kb/332088 in the
>>>>> Eventlog
>>>>> and see if it coincides with the time when IWP stops serving through
>>>>> IIS.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Trevor Benedict
>>>>> MCSD
>>>>>
>>>>> "Steve-o" <stevenmartin@hotmailDOTcom> wrote in message
>>>>> news:342BCE98-2330-40E5-9E6F-7F0B9BCC1B73@microsoft.com...
>>>>>>I have a strange problem that I just can't figure out. First of all
>>>>>>let me say that I have a bit of experience with Server 2003 but not a
>>>>>>lot with IIS. I have a client that uses Filemaker for several
>>>>>>databases that they use in their office. Filemaker has a feature that
>>>>>>makes databases available to people via a browser called "Instant Web
>>>>>>Publishing" (IWP). Well, this IWP makes use of IIS in order to publish
>>>>>>these databases. The only requirement for IIS to work for filemaker is
>>>>>>basically to make sure that anonymous access is enabled. So, I
>>>>>>installed IIS and made sure that anonymous access was enabled. Then I
>>>>>>installed Filemaker Server and told it to use IIS for the IWP.
>>>>>>Everything went smoothly and it was serving up the Filemaker databases
>>>>>>just beautifully for almost 24 hours. The next day at about noon it
>>>>>>all blew up and stopped working completely. Anything that was made
>>>>>>available via IWP wouldn't show up at all although Filemaker Server
>>>>>>still functioned fine for everything else it does. IIS wouldn't even
>>>>>>show its default web page. So I uninstalled and re-installed IIS and
>>>>>>we could then see the default web page so it appeared that IIS was
>>>>>>again functioning properly. But, whenever I tell Filemaker to use IIS,
>>>>>>IIS freaks out and restarts itself and Filemaker comes back with an
>>>>>>error saying it is unable to communicate with IIS.
>>>>>>
>>>>>> I can provide logs if someone can tell me which ones you need and
>>>>>> where to find them. I am open to calling anyone that has good
>>>>>> experience with IIS. I also would mind paying you for your help if we
>>>>>> can solve this problem.
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Steve
>>>>>
>>>>>
>>>>
>>>
>>
>
 >> Stay informed about: IIS 6.0 keeps restarting itself 

On Feb 14, 7:47 pm, "Trevor Benedict" <trevorn....RemoveThis@gmail.com> wrote:
> Steve,
> We still don't know if the Process Recycle is the issue, but it is worth
> checking. Remember to take screen shots of whatever you have before you make
> this change so that you can rollback if you like to.
>
> Under the Recycling Tab, uncheck the "Recycle Worker Process in minutes"
<