We reverted all of our servers back to the version 1, build 17 version. I will have to setup another server to test with, and reinstall the new COM check utility. I will let you know as soon as I get it setup & have a chance to test again.
Thank You,
Ronnie Jenkins
Financial Services Group
P&C Sourcing Support Services
Computer Sciences Corporation
(o) 803-333-4110
(c) 803-318-0010
email: [EMAIL PROTECTED]
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| "Dirk Bulinckx"
<[EMAIL PROTECTED]>
03/29/2006 01:20 AM
|
|
From what we know you're the only one then to get the performance drop.
In the 1st cycle the check will take "longer" then in the next cycles, however it should never take that long. The authentication as such can indeed take upto 15 seconds (just as with the v1 check). Does it do the same when checking the local system?
Dirk Bulinckx.
From: Ronnie E Jenkins [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 29, 2006 7:50 AM
To: Servers Alive Discussion List
Subject: [SA-list] [SA-list] Problems with COM Check ver 2 build 55
We had been using the version 1.0 build 17 of the COM Check utility. During the roll-out to the new version of SA, we upgraded to the latest COM Check (v 2, build 55). The performance on the new com check was terrible. We saw an increase in the time required to perform a check go from 20 - 30 seconds to 5 minutes or more. In many cases, the com checks would still fail to complete with a 300 second time-out, and the second knock checked. We have a server that's primary function is external COM checks. It typically takes this server 50 - 70 minutes to complete a check cycle. With the new version, it failed to even complete two cycles in an 8 hour period. We were forced to remove the new version, and re-install the version 1, build 17 version. Everything returned to normal using the old version. There was a mix of Win2000 & Win2003 servers being checked, and they all seemed to be affected by this.
We were hoping to see a speed increase in the new version, but saw a drastic drop in performance. Any ideas?
Thank You,
Ronnie Jenkins
Financial Services Group
P&C Sourcing Support Services
Computer Sciences Corporation
(o) 803-333-4110
(c) 803-318-0010
email: [EMAIL PROTECTED]
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected]
To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected]
To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected]
