
|
 |

Y2K hits ATF and other agencies
|
January 4, 2000
Web posted at: 1:18 p.m. EST (1818 GMT)
by Judi Hasson and FCW staff
|
From...
|
(IDG) -- The Bureau of Alcohol, Tobacco and Firearms temporarily halted licensing businesses that sell firearms Monday after identifying a Year 2000 glitch that made it impossible for its computer system to read the correct date on their applications. The ATF licensing problem was by far one of the most serious computer snafus to emerge from the New Year's rollover to 2000. Although federal officials say its Firearms Licensing System will be suspended for only five days to fix the problem, it could affect functions in other law enforcement agencies, particularly the FBI, which uses the system to verify licensed gun dealers.
 | ALSO |
|
|
Pat Schambach, ATF's chief information officer, said law enforcement officials decided to shut down the system after a test was conducted over the weekend at the ATF's computer facility in Atlanta. "They didn't like what they saw," Schambach said, when the computer was unable to read the correct date on a gun seller's application. The computer center processes about 5,000 firearms applications a month, a process that takes 6 to 8 weeks. Although no other major Year 2000-related snags were reported nationwide, there were spot problems around the country, according to the President's Council on Year 2000 Conversion Web site.
The Energy Department experienced one minor Year 2000-related failure in its more than 545 mission-critical systems, according to agency officials. The failure affected the Dynamic Special Nuclear Materials Control and Accountability System at the Oak Ridge National Laboratory's Y-12 nuclear weapons plant in Tennessee, according to Energy CIO John Gilligan. The problem in the software that automatically transfers data from the Oak Ridge system to DOE headquarters did not affect the actual system, so there was no risk to the nuclear weapons plant. Other problems include the following: - Federal buildings in three cities reported Year 2000-related problems with various systems that were corrected. In Chicago, the National Archives building displayed the date as Jan. 4, 1980, and had to be reset manually. In a federal building in East St. Louis, Ill., an access system had to be used manually, and the security system at the federal building in Benton, Ill., printed 1982 instead of the correct date. The system was manually reset.
- There were a dozen equipment problems in the nation's transportation system. The Federal Aviation Administration is investigating whether they were Year 2000-related.
- A minor Year 2000 problem was discovered at Amtrak's Control Center. The train's system would not retain train symbols as the train progressed and had to be inserted manually and the date reset.
- The San Francisco regional office reported that the Bay Area Rapid Transit experienced a failure on two maintenance-related computers used for time clocks, but there was no impact on operations.
RELATED STORIES:
Reaping the benefits of the Y2K scare January 3, 2000
Charities tap leftover Y2K disaster supplies January 3, 2000
Y2K worriers: Too soon to say all OK January 3, 2000
Two glitches hit Microsoft Internet services as New Year rolls over January 3, 2000
Y2K bug hits heating system in Korean apartments January 3, 2000
Computer problems hit three nuclear plants in Japan January 3, 2000
Feds sound Y2K all-clear January 3, 2000
Arlington County, Va. faces strict Y2K deadline December 31, 1999
Alaska always alert; Y2K just another day December 31, 1999
Confident yet cautious, industries await Y2K December 31, 1999
Japan makes final preparations for Y2K December 31, 1999
LA might be most Y2K-ready city in the World December 31, 1999
New Year's Eve on the Net December 31, 1999
Overlooked patches cause last-minute Y2K glitches December 31, 1999
Raleigh, N.C. to watch and wait December 31, 1999
Y2K planning helps French power utility cope with storms December 31, 1999
Tulsa takes laid-back approach to Y2K December 31, 1999
Vietnam sets up Y2K contingency task force December 31, 1999
Internet surviving Y2K, so far December 31, 1999
RELATED IDG.net STORIES:
NASA discovered last-minute Y2K glitch (Federal Computer Week)
World spent $200 billion on Y2K fixes, U.S. says (Federal Computer Week)
Hackers quiet for New Year, but may hit fed sites later (Federal Computer Week)
All quiet on the Y2K front (InfoWorld.com)
Feds complete weekend Y2K checks (InfoWorld.com)
Y2K bug squashed, Feds say (InfoWorld.com)
FAA says Y2K not to blame for mainframe failure in Northeast (InfoWorld.com)
Bureau of Alcohol, Tobacco and Firearms gets a new lease on life (CIO)
Note: Pages will open in a new browser window
External sites are not endorsed by CNN Interactive.
RELATED SITES:
President's Council on Year 2000 Conversion Web site
U.S. Bureau of Alcohol, Tobacco and Firearms
Note: Pages will open in a new browser window
External sites are not endorsed by CNN Interactive.
|