What task are you performing when that error occurred? Did you happen to see this somewhat-similar kb article?
<content>Error: "12 DD_UPDT 2650" during migration of System Information and data from a previous (legacy) version of Sage 100.</content>
<content>
Possible issue with Windows permissions.
</content>
<content>
- If running the migration from a workstation accessing the Sage 100 server, try starting the migration process at the Sage 100 server itself.
- When logging onto the Sage 100 server, do so as a Domain Administrator.
- To migrate, right-click "..\MAS90\Migration\Migrate.exe" program and select "Run as Administrator".
- Note: Run the migration from the new Sage 100 installation, not from the previous Sage 100 installation.
</content>
ID:87371------------------------------
Brett Zimmerman
Net at Work
Greater Boston Area
------------------------------
Original Message:
Sent: 07-23-2020 23:46
From: Alnoor Cassim
Subject: Error 80 DD_updt Line 2650
Hmm I've seen this error only on conversion before. Any chance the 2019 install completed OK but then you get this error trying to convert your client's MAS_xxx folder which came from an earlier version and had mods? If so, I suggest you just install the mod on the 2019 system then try converting again.
(It's in a CopyFile routine used during conversion when Sage adds a new alternate key / index to a table. I remember @Jeff Schwenk had this error and it was b/c the M/D mod from the old system had added its own custom key to an A/R table but had not yet been installed on the new system yet, thus Error 80.)
If that scenario is not applicable to you then at the error you might want to click Info then Debug then type this at the prompt:
CLIP_BOARD WRITE FILEPATH$
Now go into Notepad or similar and do a paste (Ctrl-V).
After doing that, type this below at the prompt and then paste again:
CLIP_BOARD WRITE X$
------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)
Email: alnoor@asifocus.com
Orange County, CA
------------------------------