BREAKING: ATF eForms Broken. Again. Still. More.

1. Restarting a server 5 times a day and it takes an hour to come back? Someone tell the ATF that Windows ME is a HORRIBLE server architecture.

   • Which is why they chose it. Interminable delays are a form of back-door gun control.

     Screw ’em and leave ’em begging for more.

2. If your “system” has to be restarted 5 times a day, you don’t have a system. A mental illness, perhaps, but not a system.

   • So true.

3. How about you guys stop pandering to the masses and include the attachment that was in that email explaining how batch processing is the problem with the system.

   • I have seen the attachment forwarded from someone else, but I too am a registered e-Forms user and my email only included the above information. We are verifying the attachment and will post an update shortly.

     • To an FFL/SOT or as Form 1 user?

       • I’m registered as a Form 1 user, the person that forwarded me the attachment is an SOT. But he’s a d-bag and not above dicking with me by including a fake letter from the ATF on April Fools’, so I need someone else to verify the attachment.

         [email protected] if you have the email as well.

   • I’m sitting here, just waiting to start feeling pandered to.

4. When you see how badly the government screwed the pooch on the healthcare exchange – something that many people desperately needed to work flawlessly in order to maintain their integrity and career – you begin to understand how something as unimportant and insignificant as ATF e-forms will have less than a snowballs chance in hell of ever reaching even 50% of it’s stated uptime.

5. How is this breaking?

   Now if you had said ‘ATF E-Forms fixed and Backlog eliminated’ I’d have expected an April Fools at the end.

6. The attachment is the important part. In short: stop batch uploading!

7. I think Nick’s leg has been pulled…

   • Return-Path:
     Received: from mx-jdcw.usdoj.gov (mailsc31.usdoj.gov. [2607:f330:8400:403::13])
     by mx.google.com with ESMTPS id d93si8147739qgd.161.2014.04.01.13.19.50
     for
     (version=TLSv1 cipher=RC4-SHA bits=128/128);
     Tue, 01 Apr 2014 13:19:51 -0700 (PDT)
     Received-SPF: pass (google.com: domain of [email protected] designates 2607:f330:8400:403::13 as permitted sender) client-ip=2607:f330:8400:403::13;
     Authentication-Results: mx.google.com;
     spf=pass (google.com: domain of [email protected] designates 2607:f330:8400:403::13 as permitted sender) [email protected]
     Received: from emsagent1.doj.gov (emsagent3.doj.gov [10.222.4.38])
     by mailsc31.usdoj.gov (8.14.5/8.14.5) with ESMTP id s31KJoel001086;
     Tue, 1 Apr 2014 16:19:50 -0400
     Received: from ad.msnet.atf.gov ([10.248.193.19])
     by emsagent1.doj.gov (8.14.1/8.14.1) with ESMTP id s31KJd3S016855;
     Tue, 1 Apr 2014 16:19:39 -0400
     Received: from ([10.248.192.247])
     by hqpironml2.ad.msnet.atf.gov with ESMTP id 7H00QM1.22510925;
     Tue, 01 Apr 2014 16:18:29 -0400
     Received: from webmail.doj.gov ([131.253.64.15]) by HQPEXCHBH02.ad.msnet.atf.gov with Microsoft SMTPSVC(6.0.3790.4675);
     Tue, 1 Apr 2014 16:40:06 -0400
     Received: from 004FCH1MPN2-001.004f.mgd2.msft.net ([fe80::90db:864c:6fe:2e6d])
     by 004FCH1MMR2-001.004f.mgd2.msft.net ([fe80::597d:2a98:c076:4be%11]) with
     mapi id 14.03.0174.002; Tue, 1 Apr 2014 15:18:29 -0500
     From:
     To:
     Subject: Urgent ATF eForms Notice

     • This is why we can’t have nice things….

     • For those that don’t know what they’re looking at, that is a *completely legit* full message header.

8. The only things that the Feds do well are waste trillions of dollars and kill large numbers of people. And then, they fvck up the paperwork

9. The only ones that appear to be whining, are probably low volume, straight MSRP dealers……….

   • Man Randy that was exactly what I was thinking.

   • You forget, sir, that there are a LOT of Form 1 users out there, too. I’ve been trying to submit two Form 1s for the last 2 weeks. Not only has the reboots been a major factor, but the reboot time has exceeded 1 hour on every instance. Last night the 11pm EST rebooted and did not come back online until 3am EST, only to have it reboot again at 4am EST. That reboot did not come back online until 7am EST. The next reboot was scheduled for 9am EST.

     During these small windows of opportunity, the system is running super slow and takes around 10-20mins to navigate through each page. There are 7 pages to get through before hitting Pay.Gov and submitting your forms. There just isn’t enough time to get a single form done!

     This is the frustration most of us have been dealing with. My SOT has two of my Form 4’s and 12 other from various customers. For the last 3 weeks he was only able to get 5 processed! It’s crazy!

     Hopefully they get their act together. William Burke (2nd responder) had it right. This may be their way to control the number of submissions in hopes of making some drastic changes to NFA ownership rules. Then again, I’m a conspiracy aficionado. 🙂

10. If your server is down for 5 out of every 24 hours your server is BROKEN. Is it really so difficult in this day and age to find competent coders and sysadmins?

11. Only in .gov would this be acceptable. What’s sad is that there are probably better admins, DBAs and programmers that can’t find work.

Comments are closed.