x Want to participate? Join the group to interact
Options
  • Replies 5 replies
  • Subscribers 106 subscribers
  • Views 948 views
  • Users 0 members are here
Browse Forums
Announcements
293
topics
370
replies
Business Object Interface
1k
topics
7k
replies
Core Financial Modules
2k
topics
8k
replies
Customization and Productivity
3k
topics
12k
replies
Distribution, Manufacturing, and Applications
2k
topics
7k
replies
General Discussion
1k
topics
3k
replies
Partner Cloud
45
topics
92
replies
Payroll, Time Tracking, and Job Cost
777
topics
1k
replies
Reporting and Analytics
962
topics
3k
replies
Sage CRM for Sage 100
164
topics
357
replies
Technical and Installation
2k
topics
9k
replies
Year-end Forum
89
topics
237
replies
j-fly

UI Does Not Exist

Posted By

Hey all. We are moving from Mas90 4.3 to Sage100 Cloud. Finally! Over the weekend, we made a backup of our entire Mas90 directory and uninstalled some shipping link software before moving data from all companies. Long story made short, we did not get to move the data, and now we cannot launch AR/Inventory History Inquiry. The exact error is:

The object AR_INVENTORYHISTORYINQUIR_UI does not exist

It does in fact exist.

So I replaced that particular file with one from the backup and the error persists. I read on another thread that if you have multiple installs of Mas90 on a single share, there might be issues like this. 

I have also tried renaming all of the other files related to Invoice History Inquiry, and then replacing them with the backups, but to no avail. I even reinstalled the workstation client on my machine thinking maybe it was something local, but the error persists.

I thought I'd reach out to see if anyone has any experience/thoughts about how to troubleshoot without replacing the entire AR directory. I am concerned that if I replace the entire folder, it still won't work and I will be out if ideas. I am a novice at supporting Mas90. 

Thanks!

  • Contact your Sage partner, or Sage support for assistance.  A failed migration / upgrade cannot be properly diagnosed in a forum, without  a full detailed list of all actions taken.

    Really, the v4.3 system should have been left 100% untouched, with new installed to a different directory, with a parallel migration.  What you describe doesn't sound like this was done.

    If the uninstall you mention was for an old enhancement you don't want to bring into new, it's often necessary to re-run the server install program to repair what was broken by the uninstall... but you need to follow the Master Developer's guidance on what to do for their specific enhancement.  If you need to uninstall something for the migration, that's best done from a folder copy, to avoid damaging the original install.

    We have Live systems with 2-3 old versions still on the server / share (disabled by renaming a key system file to prevent unintended use), without issue.

  • in reply to Kevin M

    Thanks Kevin! I think I'm leaving this one alone. Out of my depth Slight smile

  • When you have a third party add-on you have to know exactly when in the process you should install the software. 

  • FormerMember
    FormerMember

    First step is update to 4.5 then to 2017. Going to 2020 should be less painful from there.

  • in reply to FormerMember

    Very good point... for pre-v4.5.8 source, at least one middle step is mandatory.

*Community Hub is the new name for Sage City