PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 03/07/2019 8:23 AM by  pjnowak
ACA BN299 Manifest File
 11 Replies
Sort:
You are not authorized to post a reply.
Author Messages
Kristie Starzyk
HRIS Coordinator
Rush-Copley Medical Center
Veteran Member
(158 points)
Veteran Member
Posts:64


Send Message:

--
02/08/2019 12:16 PM

    I'm in version 10.0.8, and the BN299 manifest file is still not generating the Augmentation Number... anyone else having these issues?  We are in the process of upgrading to Version 10.0.10 and when I'm testing, it works in that version.  Just curious if we missed a patch for our current version that is obviously programming fix in 10.0.10.

     

    Thanks!

    Tila11523
    Comp & Benefits Assistant
    Private
    New Member
    (3 points)
    New Member
    Posts:1


    Send Message:

    --
    02/08/2019 1:59 PM
    There was a patch CTP119646 for BN299 manifest files missing company address digits. Reference number JT-1252813. I am waiting for ours to be installed!
    Margie Gyurisin
    Private
    Private
    Veteran Member
    (1434 points)
    Veteran Member
    Posts:538


    Send Message:

    --
    02/08/2019 4:45 PM
    We have all updates in our system and it is not populating for me once again.  Brings back nightmares.  I found previous forum posts about this  at "1094 checksumaugmentationnum error".  In it I reference this document form 2017.  I guess we will need to do it again unless someone knows how to make it work in Lawson.
    Margie Gyurisin
    Private
    Private
    Veteran Member
    (1434 points)
    Veteran Member
    Posts:538


    Send Message:

    --
    02/08/2019 4:45 PM
    We have all updates in our system and it is not populating for me once again.  Brings back nightmares.  I found previous forum posts about this  at "1094 checksumaugmentationnum error".  In it I reference this document form 2017.  I guess we will need to do it again unless someone knows how to make it work in Lawson.
    Margie Gyurisin
    Private
    Private
    Veteran Member
    (1434 points)
    Veteran Member
    Posts:538


    Send Message:

    --
    02/08/2019 4:47 PM
    Sorry.  I meant to upload this pdf file
    Attachments
    Margie Gyurisin
    Private
    Private
    Veteran Member
    (1434 points)
    Veteran Member
    Posts:538


    Send Message:

    --
    02/11/2019 7:28 AM
    Kristie,

    I am curious - Do you have any messages in the log for your completed BN299 job? I get this message and wonder if it is related to it - /usr/bin/rm: cannot remove 'd:/lsf10test/law/print/NT00000004/bn299ssc/1/1094C_Request_*': No such file or directory
    TIME 17320600
    Running BN299
    PAYROLL SYSTEM
    'openssl' is not recognized as an internal or external command,
    operable program or batch file.
    Kristie Starzyk
    HRIS Coordinator
    Rush-Copley Medical Center
    Veteran Member
    (158 points)
    Veteran Member
    Posts:64


    Send Message:

    --
    02/11/2019 1:29 PM
    I know! I had horrible flash backs on this checksumaugmentation thing too. I looked at my log for BN299, and I do not have that error message. I do have the "'openssl' is not recognized" message. My files did create on my server.
    Margie Gyurisin
    Private
    Private
    Veteran Member
    (1434 points)
    Veteran Member
    Posts:538


    Send Message:

    --
    02/11/2019 1:41 PM
    My files created as well on the server. I did open an incident and mentioned I wasn't the only one with the issue. Did you open an incident? When you say you are going to 10.0.10, is that environment or apps? I didn't know Lawson was up that high on apps versions.
    Kristie Starzyk
    HRIS Coordinator
    Rush-Copley Medical Center
    Veteran Member
    (158 points)
    Veteran Member
    Posts:64


    Send Message:

    --
    02/11/2019 1:54 PM
    Sorry. We are going to environment 10.0.10, apps 10.0.8. We are currently environment 10.0.5 and apps 10.0.3.
    Margie Gyurisin
    Private
    Private
    Veteran Member
    (1434 points)
    Veteran Member
    Posts:538


    Send Message:

    --
    02/26/2019 8:28 AM
    It looks like we have the checksum value issue fixed. Lawson had us do this.

    Lawson Technology would like you to install OpenSSL and add it to the system path statement so it can be found and executed.

    If you have an incident open, have your person reference incident 13180695 for the fix. Chris did a great job in helping us.
    Kristie Starzyk
    HRIS Coordinator
    Rush-Copley Medical Center
    Veteran Member
    (158 points)
    Veteran Member
    Posts:64


    Send Message:

    --
    02/27/2019 8:31 AM
    We actually just did the work around from last year because I wanted to get them submitted to the IRS. I'll have to keep your incident number on hand for next year if it's still not fixed. Who knows what version we'll be in by then!
    Thanks as always, Margie!
    pjnowak
    Application Analyst
    Private
    New Member
    (3 points)
    New Member
    Posts:1


    Send Message:

    --
    03/07/2019 8:23 AM

    If the checksum is not being populated, you may need to have the OpenSSL program installed on your server. BN299 calls OpenSSL to get the checksum. We had this problem when the IRS switched from the previous encryption method to SHA256. We're running on Windows Server.

     

    You are not authorized to post a reply.