tag:blogger.com,1999:blog-143925273655347334.post2710416005850485082..comments2024-03-27T07:30:02.390+00:00Comments on drsolly: A consulting jobdrsollyhttp://www.blogger.com/profile/15954188290191548178noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-143925273655347334.post-13216811591855754072018-01-25T11:03:25.681+00:002018-01-25T11:03:25.681+00:00Nice :)
That reminds me of a customer who had a ...Nice :) <br />That reminds me of a customer who had a 10m/bit coax network to run their accounts system, for several days at the end of every month they got 'Disc Error 57' errors throughout the day which shut clerks out of the system. These happened on one PC at a time, didn't follow a recognisable pattern, but the coaxial network was suspected. <br />After replacing many connectors, ethernet cards and cable sections they wanted to return the whole system to the supplier, and they called me in to look. I took a look at when it was happening and decided the accounts office was very busy at end of month and there must be something more logical causing the 'Disc Error 57' <br /><br />I got on the phone to the Accounts Software supplier (Pegasus Systems in Kettering) and got their view that the error meant either the hard disc on the PC had bad sectors or, the network was at fault. <br />So I got to the server - running NetWare 2.11 - and loaded the monitor to see what might be happening. I called out to ask a colleague and one of the clerks to post invoices from seperate PCs at roughly the same time while I watched how many file handles the server opened. <br />It was sitting at 6 or 7 then went up to 12. Sure enough 'Disc Error 57' on one of the PCs in the office came up. <br /><br />Back then maximum file handles was fixed at compile time on Netware, and the server OS was built from floppy disc, so that was a long job to fix, but such a simple thing!Tony Blandnoreply@blogger.com