Link to home
Start Free TrialLog in
Avatar of OAC Technology
OAC TechnologyFlag for United States of America

asked on

File not found problems with Sage 100 ERP 2013 / MAS 90

We're having lots of problems with our MAS90. Clients are receiving random file not found errors.  We're trying to rebuild the key files for each module and they all seem to rebuild just fine with exception to the Accounts Receivable module. The Accounts Receivable rebuild gets stuck at AR_Audit and will sit overnight without moving on to the next section. We have run checkdisk several times, restarted the server, rebuilt sort files on all modules, ran sfc scan, and made sure MAS90 is up to date with all patches. Antivirus software is also disabled.

Also some additional information: The MAS90 server is running in a Hyper-V virtual machine running Windows 2012 Standard. There are also points and time where even when I try double-clicking the sage icon from the server it will take 5+ minutes to display the login prompt and another 5+ minutes after clicking login to show the MAS90 page. I don't see any other network problems when this happens (ping times are fine, no network disconnects, etc.)

 What should my next steps be?
Avatar of Bill Bach
Bill Bach
Flag of United States of America image

Are you running the MAS90 release based on Pervasive PSQL, or the one based on SQL Server?
Avatar of OAC Technology

ASKER

I believe it is Pervasive but is there a way I can check to be 100% sure?
Of course, but Sage never makes things easy, because they use a non-standard installer for PSQL and hide most of the real good tools.  

On the server, check for the presence of the Server database engine, called NTDBSMGR.EXE (for 32-bit engines) or NTDBSMGR64.EXE (for 64-bit engines), or for the Workgroup Engine, look for W3DBSMGR.EXE.  Alternatively, check the Services list (Right-Click Computer/Manage) for either the Pervasive PSQL Transactional Engine and Relational Engine services, or for the Pervasive PSQL Workgroup Engine service.  The Workgroup Service will only show up if it was installed as a service -- it may have been installed as an application, in which case it will only be loaded when Sage is running.
Actually I don't see any of these processes running and don't see any Pervasive services in the services panel. I also don't see any SQL services installed. This is what I see in my Programs and Features on the server if it's helpful:

Sage 100 ERP 2013
Sage 100 Standard ERP 2013 Workstation
Sage Advisor Update
Sage Exchange
Sage ODBC 64-bit Installer
If you launch Sage, then go into Task Manager to view ALL processes, do you see W3DBSMGR.EXE?
I still don't see anything like this in task manager when viewing all processes. Also, this took me a while to check as Sage took about 10 minutes to open on the server (another one of our random problems) and another 5 minutes to log in and users are complaining it is too slow to work with right now. Everything else on the server seems to move just fine. Processor utilization is at 10% and memory usage is at 30%. Network seems fine as well.
Interesting.  Well, you may not be using PSQL/Btrieve (which is my forte), but I can offer another suggestion -- get a copy of both Wireshark (www.wireshark.org) and Process Monitor (www.sysinternals.com) and put them on the machine in question.  Then, shut down EVERY other application on the machine that you can, activate one of the tracing tools, and launch the app to duplicate the problem.  Stop it as soon as the load finishes.  Then, do the same with the other one.

That is, of course, the easy part.  Beyond that, you'll need to try to interpret the results.  I'd start with Wireshark and see what is happening on the network side.  Specifically, look for huge delays in the timeline when the system appears to be doing "nothing".  It may be issuing network requests (such as DNS lookups) that take time to fail.  (Some such requests can take 30 seconds to fail, and if the app does it three times, there goes a minute and a half.)
Thanks for the idea, I'll try this later. Any idea on why the AR_Audit module refuses to rebuild and how to fix this module?
Without knowing your database type, no.  Can you see how big the data file is right now?  It is possible that the audit trail is huge, and it just takes a long time to rebuild.
I don't believe Sage is using anything other than the built in database. The only database connection I see on that server is an ODBC connection for MAS90 ProvideX ODBC driver. The AR folder also seems very small at 7.35MB. Although when I enter this folder I do not see any files named AR_Audit. Could the fact that I don't see this file be the problem with the rebuild?

Thanks for your help
Yeah -- it looks like they changed databases once again.  My experience is with the older, PSQL versions of MAS90.  Sorry, but I cannot advise on this second issue.
ASKER CERTIFIED SOLUTION
Avatar of OAC Technology
OAC Technology
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Found solution