Hi Rick,
We are having some problems with our app in web connect and are trying to track it down. We've been running web connect for probably 6 years now and in the last month or so have started having quite a few issues with Comm servers not restarting correctly after we update the .exe (but once you restart the entire server the comm servers start fine which makes me think our .exe is not the problem [but I could be wrong]) and other weird errors.
Looking in the IIS error logs, I'm seeing a lot of errors of:
- Connection_Dropped_List_Full WebConnection (WebConnection is the name of our app pool)
- Client_Reset
- Timer_ConnectionIdle
I can't quite tell from a google search what would cause these (as in is it from the .net code you're running or would our comm servers cause this).
We are running several servers with web connect to help load balance our app and I am seeing the errors on multiple servers. We process on average 500K-750K req / day and most requests seem to be making it just fine but we still show 1-3 IIS errors per minute according to the logs.
Any thoughts? If you need to connect in and look at our configuration with us let us know and we can schedule something and pay you for your time. We are running web connect 6.21.
Those errors sound like IIS errors that are related connection management and http protocol handling. Possibly related to your use of the load balancing proxy or router management... That would be the first place to look.
What's in the Web Connection logs?
+++ Rick ---
Hi Rick,
The web connect logs only show errors (i.e. wwRequestLog.Error = .T.) and don't have anything since February. wcTraceLog.txt matches what's in wwRequestLog. I vaguely remember turning off most web connect built in logging years ago to help increase the speed of our requests. What would I need to change to turn that back on while we troubleshoot this so wwRequestLog contains more than just the errors?
I'll see if I can track down anything else related to this in IIS.
The log you want to look at is the one in the temp folder wcErrors.txt which is the low level handler log.
If this doesn't have anything in it it means the errors you're seeing are occurring before the servers ever get hit - ie. at the protocol level in IIS (or in the load balancing router).
+++ Rick ---
Hi Rick,
Looking at the wcerrors.txt, I don't have as many errors as I see in the IIS logs but there are a bunch of these: Any idea what would cause this?d
2024-04-11 14:20:06.742 - 15_c99be463 - Unable to retrieve COM Instance: - /cpwc.wc?(params)
2024-04-11 14:20:07.270 - 9_5e9d5027 - Unable to retrieve COM Instance: - /cpwc.wc?(params)
2024-04-11 14:20:09.742 - 22_95a22691 - Unable to retrieve COM Instance: - /cpwc.wc?(params)
2024-04-11 16:20:18.242 - 23_3c1ae927 - Unable to retrieve COM Instance: - /cpwc.wc?(params)
2024-04-12 00:33:19.325 - 15_9e46f118 - Unable to retrieve COM Instance: - /cpwc.wc?(params)
2024-04-12 00:33:20.314 - 17_23eb4f25 - Unable to retrieve COM Instance: - /cpwc.wc?(params)
2024-04-12 06:20:06.813 - 15_e9335ab - Unable to retrieve COM Instance: - /cpwc.wc?(params)
2024-04-12 06:20:07.346 - 9_5f31e73d - Unable to retrieve COM Instance: - /cpwc.wc?(params)
2024-04-12 06:20:08.739 - 19_50fb89d1 - Unable to retrieve COM Instance: - /cpwc.wc?(params)
2024-04-12 06:20:09.770 - 22_5322c6e3 - Unable to retrieve COM Instance: - /cpwc.wc?(params)
as well as these
2024-04-05 09:37:34.237 - 34_52a68d2 - Unable to retrieve COM Instance: Server cpmobile.cpmobileServer[12] failed to start in time. - /cpwc.wc?(params)
2024-04-05 09:37:35.691 - 56_16cf0765 - Unable to retrieve COM Instance: Server cpmobile.cpmobileServer[12] failed to start in time. - /cpwc.wc?(params)
2024-04-05 09:37:37.037 - 7_f271e536 - Unable to retrieve COM Instance: Server cpmobile.cpmobileServer[12] failed to start in time. - /cpwc.wc?(params)
2024-04-05 09:37:39.409 - 85_34893315 - Unable to retrieve COM Instance: Server cpmobile.cpmobileServer[12] failed to start in time. - /cpwc.wc?(params)
2024-04-05 09:37:39.927 - 54_b95effec - Unable to retrieve COM Instance: Server cpmobile.cpmobileServer[12] failed to start in time. - /cpwc.wc?(params)
2024-04-05 09:37:40.053 - 41_6ccd8254 - Unable to retrieve COM Instance: Server cpmobile.cpmobileServer[12] failed to start in time. - /cpwc.wc?(params)
2024-04-05 09:37:42.183 - 84_f5935d34 - Unable to retrieve COM Instance: Server cpmobile.cpmobileServer[12] failed to start in time. - /cpwc.wc?(params)
2024-04-05 09:37:44.146 - 5_add94151 - Unable to retrieve COM Instance: Server cpmobile.cpmobileServer[12] failed to start in time. - /cpwc.wc?(params)
2024-04-05 09:37:46.691 - 51_d9ce0493 - Unable to retrieve COM Instance: Server cpmobile.cpmobileServer[12] failed to start in time. - /cpwc.wc?(params)
2024-04-05 09:37:47.869 - 68_6b197e7d - Unable to retrieve COM Instance: Server cpmobile.cpmobileServer[12] failed to start in time. - /cpwc.wc?(params)
2024-04-05 09:37:49.192 - 55_850637b8 - Unable to retrieve COM Instance: Server cpmobile.cpmobileServer[12] failed to start in time. - /cpwc.wc?(params)
2024-04-05 09:37:51.546 - 44_69842476 - Unable to retrieve COM Instance: Server cpmobile.cpmobileServer[12] failed to start in time. - /cpwc.wc?(params)
2024-04-05 09:37:51.577 - 7_84749132 - Unable to retrieve COM Instance: Server cpmobile.cpmobileServer[12] failed to start in time. - /cpwc.wc?(params)
2024-04-05 09:37:51.656 - 41_ebcd1db6 - Unable to retrieve COM Instance: Server cpmobile.cpmobileServer[12] failed to start in time. - /cpwc.wc?(params)
2024-04-05 09:37:51.687 - 84_331a8151 - Unable to retrieve COM Instance: Server cpmobile.cpmobileServer[12] failed to start in time. - /cpwc.wc?(params)
2024-04-05 09:37:52.929 - 83_879c1301 - Unable to retrieve COM Instance: Server cpmobile.cpmobileServer[12] failed to start in time. - /cpwc.wc?(params)
2024-04-05 09:37:54.216 - 53_dc651ac3 - Unable to retrieve COM Instance: Server cpmobile.cpmobileServer[12] failed to start in time. - /cpwc.wc?(params)
2024-04-05 09:37:55.928 - 40_77a275d5 - Unable to retrieve COM Instance: Server cpmobile.cpmobileServer[12] failed to start in time. - /cpwc.wc?(params)
2024-04-05 09:38:00.635 - 52_59358cf5 - Unable to retrieve COM Instance: Server cpmobile.cpmobileServer[12] failed to start in time. - /cpwc.wc?(params)
2024-04-05 09:38:00.916 - 22_e1b4c68a - Unable to retrieve COM Instance: Server cpmobile.cpmobileServer[12] failed to start in time. - /cpwc.wc?(params)
2024-04-05 09:38:00.916 - 87_ea53ed68 - Unable to retrieve COM Instance: Server cpmobile.cpmobileServer[12] failed to start in time. - /cpwc.wc?(params)
2024-04-05 09:38:01.565 - 27_cecd2915 - Unable to retrieve COM Instance: Server cpmobile.cpmobileServer[12] failed to start in time. - /cpwc.wc?(params)
2024-04-05 09:38:01.675 - 45_1375a23 - Unable to retrieve COM Instance: Server cpmobile.cpmobileServer[12] failed to start in time. - /cpwc.wc?(params)
I don't think the errors in wcerrors.txt are related to the errors you're seeing in IIS. Those two errors look like they're related to a crashed/hung server instance which can happen and is not abnormal unless you see it a lot.
This seems to suggest the issue is happening at the IIS or protocol layer or not related Web Connection.
+++ Rick ---
Thanks for the reply. I'll keeping looking at the IIS side for now.