Sage 100

Client on 4.5 had an error 84 in SY_Launcher.pvc last night while doing SO Register. This morning anyone can restart and then gets MAS HAS STOPPED RESPONDING with no errors. I could see in the Activity Log from last night I/O errors with error 261 in SY_Service.pvc line 678, SY_LineEntryDetail_bus line 533 and IM_ItemWarehouse_bus.pvc line 786. With no numbered errors happening now, I don't even know where to start. I've rebuilt some AR and SO files, but feel like I'm just throwing darts at a dart board. Help!

do you have the line number in SY_launcher.pvc that had the error 84 ? what service update for 4.50 ?

Standard or Advanced? If Advanced, does MAS90 Mode work?

Nevermind, I thought you meant they couldn't open MAS at all.

Do not have the line number for the original error, sadly enough. And my bad - 4.4 su 8

4.4 or 4.5 ?

Beth. There's an old resolution for version 4.4, that occurred because the printer the report was being printed to ""by default"" was either invalid or off line. Can you check the printer the report is going to and change to another if it appears to be unavailable? Otherwise, there is more in depth approach on Sage City under 110-531341 ""MAS has stopped working"".

@ChrisStAmand - I saw that and I don't think it's it - I was able to change the printer before getting the MAS has stopped working error (and usually you can't). I also can't find it in the SY_ReportSetting file to delete. I'll check that 110-531341

One of the inventory files that is part of the update from SO most likely has damaged data. The damage makes the system hang, rather than report the error, which I have seen before. I would bet it is IM_ItemTransactionHistory, but it could be IM_ItemWarehouse or IM_ItemCost, (or any of the IM tables being updated, including IM_ItemWhseHistorybyPeriod, etc.....

Hi - just following up to see if you got this fixed ....

Got to a point in the rebuilding that we were getting errors again instead of just that damn ""stopped working"", so rebuilt those files (AR_TransactionPosting and AR_TransactionPostingHistory), then went back to ""stopped working"" again. One of the rebuilds mentioned a particular customer, so with the end user's permission, I manually deleted the 2 last invoices in the file (which were for this customer) and it finally updated. I'm having them check this morning to see how much disaster is out there.