IT pilot fish at a large organization is supporting a server-based application -- one that keeps falling over.
"We started experiencing issues with communication between devices and server," says fish. "The application would just stop. The fix was to restart a stopped service on the server.
"The issue was soon occurring daily, and the vendor was contacted. Vendor support could find no issues and had no other customers experiencing the issue, but they kept looking.
"Finally our management strongly suggested that the vendor's senior management fly onsite to discuss the issue, the intent being to let them know we were not happy and expected them to do everything in their power to expedite and resolve it -- or else.
"Turns out our network staff had developed a way to tell if the server was running by sending a request to the server. The request was sent to the same port that the application used to communicate to the devices. So when the request went to the server to see if the server was running, the application lost communication with the devices and shut down.
"I never found out how this was explained to the vendor."
Sharky believes no story is better left untold. So send me your true tale of IT life at email@example.com. You'll score a sharp Shark shirt if I use it. Comment on today's tale at Sharky's Google+ community, and read thousands of great old tales in the Sharkives.
Get Sharky's outtakes from the IT Theater of the Absurd delivered directly to your Inbox. Subscribe now to the Daily Shark Newsletter.