Installation and Technical Issues

[TRoop]

Hello folks,

I recently ran into a problem tring a test upgrade to Mas 500 7.2 this weekend. I got a DMOAsync Error -131063twice. One for the tciBatchLog table and one for the timItem table. Here are the steps that I had taken to attempt this Friday evening...

1. Restore a production bakcup from the the previous eveing (Thurs)
2. Run the Databse Synchronization Utility
3. We are using a Citrix-based client, so we made sure it was loaded with the 7.05 client and MU
4. log in using the Citrix client 
5. Post all batches in all modules
6. Run script to find any other unposted batches
7. Once all batches are posted, log out of Mas 500
8. Run the Database Upgrade Utility on the server

Here are the options selected within the Upgrade Utility...

1.  Run a comparison using the selected options
   1. Select the appropriate databases from the dropdowns
   2. Check the option "Compare with Pre-Processed Database information"
   3. Select version "7.2"
   4. Check the option "Generate database upgrade script"
2. Run the Upgrade using the following settings...
   1. Select appropriate databases
   2. Select the Update to version "7.20"
   3. Check the option "Use Pre-generated database upgrade script"

Has anyone ever run into anything like during an upgrade??

[TRoop · Accepted solution]

Ok... here is what we found to be the issue...

I started looking at what we had "customized" within these two tables that might be causing the issue. There were 2 things consistent between the 2 table that could have potentially caused a problem here. First, I noticed that both of these tables had custom triggers attached to them that when a record was either inserted or updated (designed in house), would update "extended" tables. I also noticed that one of these tables had 3rd party triggers enabled. I disabled our "in house" triggers and tried another update. No Luck!!  So then I turned my attention to the 3rd party (Single Source SM+) triggers. Since only one of the tables had the 3rd party triggers enabled, I doubted that tthe triggers were the cause. I then started looking at the other things on the tables that might be causing it. I found that both of them had foreign key constraints on them that were tied to the SM+ tables. As our business took a turn away from being service-oriented, we had opted to upgrade out of the SM+ software. We didn't have support with the SM+ software to be able to get assisitance with the removal of the Single Source modules so I opted to just remove the foreign key constraints and try upgrading again. This did the trick and allowed the upgrade to finally complete successfully!!

[RDCushing]

Can anyone tell me what is being upgraded in the v.7.05 to v.7.20 script when the upgrade log indicates "Upgrading Sale Multiple"? I'm getting the same DMOAsync error at that point, and I don't know what table(s) might be involved in order to look for non-standard indexes, constraints or triggers.

Any help would be appreciated. Thanks.