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!

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.

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.

Sorry.  I meant to upload this pdf file

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.

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.

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.

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.

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.

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!

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.