-Vulture-
Mon May 14 07:34:03 CDT 2007
On 11 Mai, 12:27, -Vulture- <philipp.rit...@innochange.com> wrote:
> On 11 Mai, 11:51, David Wang <w3.4...@gmail.com> wrote:
>
>
>
> > On May 11, 1:16 am, -Vulture- <philipp.rit...@innochange.com> wrote:
>
> > > On 10 Mai, 10:57, David Wang <w3.4...@gmail.com> wrote:
>
> > > > There are lots of things between your ePages-shop system and the end
> > > > user's browser that can sporadically break to cause connection
> > > > disconnect.
>
> > > > Since you think the issue has something to do with the IIS, please
> > > > provide the actionable information that makes you arrive at this
> > > > conclusion, and we can go from there.
>
> > > > Otherwise:
> > > > - I do not believe you have provided sufficient proof that ePages-shop
> > > > system is bug-free software. FYI: A random crash in that software
> > > > system can cause sporadic disconnect that resumes on F5-refresh. Can
> > > > you provide concrete evidence that the ePages-shop system has no bugs
> > > > and does not crash?
> > > > - I do not believe you have provided sufficient proof that IIS itself
> > > > sporadically disconnects.
> > > > - I do not believe you have provided sufficient proof that the
> > > > intervening network and network appliances are not at fault.
> > > > - Showing that the issue occurs on IE7, Firefox, and different PCs
> > > > only says the problem is probably not specific to a client, but once
> > > > again, there are lots of things between the client and server that you
> > > > have not diagnosed
>
> > > > Troubleshooting is like crime-investigation -- you have to put away
> > > > one's personal/irrational bias towards any suspect, be creative at
> > > > looking for evidence, and deduce what the evidence suggests.
>
> > > >
http://blogs.msdn.com/david.wang/archive/2005/12/31/HOWTO_Basics_of_I...
>
> > > > //David
http://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> > > > //
>
> > > Hi David, thanks for your response.
>
> > > I know that everything is a bit more complex than i have described in
> > > my first post. I say its no ePages-error because the error message
> > > shown comes directly from the browser, not the shop itself. And ePages
> > > has a lot of error messages to show, but this one isnt one ;)
> > > Thats why i thought more into the direction of the web service, the
> > > IIS.
>
> > > I now have reconfigured the epagesApplicationPool which created a
> > > suspicious info message in the system protocol, maybe that helped.- Hide quoted text -
>
> > > - Show quoted text -
>
> > You are assuming that ePages errors result in error responses viewable
> > from the browser. That is a false assumption.
>
> > If ePages randomly crashes on the server, you will not see an error
> > response (because ePages doesn't get a chance to execute code to
> > generate that error response). In that case, IIS6 will appear to hang
> > or drop the connection, and F5 on clients will refresh and as if
> > nothing happened.
>
> > Hmm... that sounds suspiciously like the issue that is bothering you,
> > but ok, you seem to insist the issue is with IIS6 and not something
> > like eShop...
>
> > Anyways, I highly suggest that you disclose more information (such as
> > what you reconfigured and what resulting event log entry) as well as
> > listen and read helpful URLs that has been offered to you. Otherwise,
> > you may be impeding your own progress as well as dissuade others from
> > offering you assistance.
>
> > //David
http://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> > //
>
> Hi David,
>
> again, thanks for your answer and sorry for the triple post.
> Your document was indeed very informative.
>
> This server wasnt the first one we set up with Win2k3 and ePages5, but
> it was the first one with this error. And cause the shop should go
> live in the next days i'm a bit under pressure. I looked at the
> settings of the other servers, thats why i reconfigured the
> ePagesApplicationPool. Now ill wait for a response of our developers.
It seems like this option solved my problem, i just wanna let you
know. Thanks!