He privately emailed me me the same @Alnoor work-around that @Brett did. When I showed the CRC error (above) that I get when I did that. he said he was trying to recreate it at my PU2 level.
Original Message:
Sent: 03-20-2023 09:26
From: Jeff Schwenk
Subject: VI Import Fails Because It Is the SAME Level???
Hopefully, you can get a hotfix out of them
------------------------------
Jeff Schwenk
Bottomline Software, Inc.
(540) 221-4444
------------------------------
Original Message:
Sent: 03-19-2023 13:47
From: Dan Burleson
Subject: VI Import Fails Because It Is the SAME Level???
This has been confirmed as a bug by Bret Richion at Sage and is scheduled for correction in the July 2023 PU.
------------------------------
Dan Burleson
Software Consultant
Connex Software
Original Message:
Sent: 03-13-2023 19:33
From: Dan Burleson
Subject: VI Import Fails Because It Is the SAME Level???
@Kevin Moyes Thanks for the suggestion. I'm hoping I don't have to get involved in every installation's import
@Doug Higgs Thanks for the suggestion. These records look identical except for the SecurityChecksum$ in SY_Module which isn't unexpected. The first of each pair below is from a system that was not imported. The second of each pair below is from a system that I did import to and get the CRC error message. REVISION: I just noticed that the failing system has an ExpirationDate$ that has passed, but updating it, which is likely invalid to do, didn't change anything. Note that I get the same crazy message in both installations (both the one imported into using the SOTA.INI hack and the one not imported into) about the "import file" and "imported into file" are the same version of P/R.
------------------------------
Dan Burleson
Software Consultant
Connex Software
Original Message:
Sent: 03-13-2023 18:51
From: Doug Higgs
Subject: VI Import Fails Because It Is the SAME Level???
Compare the records for a valid module to the sy0ctl.soa lP/R record and the sy_module P/R records. See if there is a field difference.
------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles
Original Message:
Sent: 03-13-2023 18:35
From: Dan Burleson
Subject: VI Import Fails Because It Is the SAME Level???
Thanks for the "DevelopmentSystem" suggestion. This does change the install to provide the option to continue. However, after the install and on launching Sage 100 and then the P/R module, I get the message "The Payroll module record contains an invalid value or crc error." shown here:
Although the import appears to have worked, clearly I can't use the DevelopmentSystem option on a customer install give this message, but does any know anything about this error. I'm not finding anything.
------------------------------
Dan Burleson
Software Consultant
Connex Software
Original Message:
Sent: 03-13-2023 09:01
From: Brett Zimmerman
Subject: VI Import Fails Because It Is the SAME Level???
I wonder if this sota.ini workaround will help:
------------------------------
Brett Zimmerman
Net at Work
Greater Boston Area
Original Message:
Sent: 03-13-2023 08:23
From: Carmen Cruz
Subject: VI Import Fails Because It Is the SAME Level???
That has to be a defect. Because no way....