Sage MAS 90 and 200 Sage MAS 500 blogs Product Feedback Support Training
Reply
Sage MAS 90 Customer
blorf
Posts: 32
Registered: 11-03-2009
0

Converting from 4.20.0.24 to 4.3 fails with an error box with no message

Hi.

 

Trying to upgrade to 4.3, we have about 5 companies, and all of them fail to convert the A/R module, all with the same error box that has no message.  Our Reseller is stumped.

 

We know it's AR that fails, because if we rename the AR directory to something it gets passed by and the rest of the data converts.

 

I have rebuilt sorts, and keys, and removed all the debris from older updates, like the .soa files and the .old files.  Also removed the log files from past updates, and still, it fails.  Because the error message is blank, I have no idea what might cause the problem.  In a few of the companies, VI jobs run in A/R but not all, so VI is not the cause.

 

Any ideas would be appreciated.

 

Thank you,

ChaZ

Super Contributor
rmikolainis
Posts: 1,252
Registered: 10-29-2008
0

Re: Converting from 4.20.0.24 to 4.3 fails with an error box with no message

Go to Library Master | Reports | Activity Log

 

Does it give any errors there?

 

Off the top of my head it sounds like you might have a corrupted AR_Options table.

Sage MAS 90 Customer
blorf
Posts: 32
Registered: 11-03-2009
0

Re: Converting from 4.20.0.24 to 4.3 fails with an error box with no message

Neat.  It is the options table.  Verified by activating a new company, and copying the new options table into a company that fails.  Thank you.

 

New problem though, found by accident but it worries me.  In the converted companies, if I attempt to rebuild key files, I get an error that says the disk is full, or can not create back up files.  I am having my network guy double check security settings, but he doesn't think that has anything to do with it.

 

Again, thank you.

 

ChaZ

Super Contributor
rmikolainis
Posts: 1,252
Registered: 10-29-2008
0

Re: Converting from 4.20.0.24 to 4.3 fails with an error box with no message

The def sounds like a permissions/rights issue on the server. I would just make sure the MAS users have full read/write/modify access to the ENTIRE MAS90 folder.