Sometimes, we screw up too.
Nov. 17th, 2005 05:07 pm![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
daerlyn.livejournal.com posting in ![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png){kind=small}
techrecoveryTales from my workplace:
In the last week, we have had three major issues in the IT department.
1 - Last Friday (when I was off, thank god), our warehouse's network went down. No H: drives, no inventory database, no email. The problem? Someone had unplugged the hub that connected us to the head office servers.
2 - Today, while printing the 75 million (I exaggerate slightly) carton labels that are required for our stuff to ship to stores, in between one print job and the next, the printer just stopped spooling. No error messages. So after 1600 print jobs sit in the queue for about five hours, one of our sys admins comes over to check it out. Somehow, the network cable had wiggled itself loose. Not entirely, it was connected enough that the network thought the printer was there, but not enough that any information was actually transmitting. *sigh*
3 - The network comm unit for our RF scanners was for some reason not downloading the hex image we use for the scanners to said scanners. After an hour in the server room with the tech from the manufacturer . . . we discovered that the serial cable hadbeen crushed by the moron techs from the other building who keep adding more crap to my server room died.
If I see another cable related problem, power or otherwise, anytime in the next month, everyone had better stay out of line of sight of the belltower.
In the last week, we have had three major issues in the IT department.
1 - Last Friday (when I was off, thank god), our warehouse's network went down. No H: drives, no inventory database, no email. The problem? Someone had unplugged the hub that connected us to the head office servers.
2 - Today, while printing the 75 million (I exaggerate slightly) carton labels that are required for our stuff to ship to stores, in between one print job and the next, the printer just stopped spooling. No error messages. So after 1600 print jobs sit in the queue for about five hours, one of our sys admins comes over to check it out. Somehow, the network cable had wiggled itself loose. Not entirely, it was connected enough that the network thought the printer was there, but not enough that any information was actually transmitting. *sigh*
3 - The network comm unit for our RF scanners was for some reason not downloading the hex image we use for the scanners to said scanners. After an hour in the server room with the tech from the manufacturer . . . we discovered that the serial cable had
If I see another cable related problem, power or otherwise, anytime in the next month, everyone had better stay out of line of sight of the belltower.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}