Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 276
  • Last Modified:

APCOMMON.DLL

We are running Sage 300 12.1.36
When posting checks in AP we receive a windows crash caused by apcommon.dll.

please see attached file.

I have uninstalled Sage 300 and reinstalled. same error.
Could this be related to pervasive?
TLE-error-when-trying-to-run-che.docx
0
mikeg95
Asked:
mikeg95
  • 2
  • 2
1 Solution
 
mirtheilCommented:
Could this be related to pervasive?

Not based on the error you are getting.  According to one of the screenshots, it's an unhandled exception.  Pervasive itself, usually, doesn't have any unhandled exceptions.  

Did this work correctly at some point and stop working or has it always failed?  If it stopped working, what changed?  Did you apply a Sage update or a Pervasive update?
0
 
Bill BachPresidentCommented:
Doubtful. The PSQL engine always returns some status code, which should be then interpretted by the application.

You can check the PVSW.LOG on the server just to be sure there are no file corruptions being reported that Sage might not handle. Also, you could try enabling the MKDE Tracing to see what the last operation and return code might be, but again, I'm not expecting it'll show you much.
0
 
mikeg95Author Commented:
Not getting anything in the logs and this started friday no update was applied. I can replicate the error every time I go to print checks when creating the text file.
0
 
Bill BachPresidentCommented:
In that case, it could be a bad record in the database, perhaps with a bad date or something else that is causing a routine to fail.  Enabling the MKDE Tracing will give you more information, but won't necessarily provide many insights -- it can be VERY useful if you open a trouble ticket with Sage, though.  

If you have the PCC on your system, then you can enable the MKDE Tracing from the server.  If not, you can turn it on and off with the free SetTrace utility (which should come up if you Google "settrace btrieve").  Be sure to run the program to immediately before the crash before turning it on to limit the amount of trace data, then shut it off before you clear the error message.  If you need to locate the trace file, check HKLM/Software/Pervasive Software/Microkernel Workstation Engine/Version xx/Settings and look for the "Trace" registry entries.
0
 
mikeg95Author Commented:
I was actually able to find this before I was able to read your note. but it was a bad Vendor that was selected and caused the crash.
0

Featured Post

The Firewall Audit Checklist

Preparing for a firewall audit today is almost impossible.
AlgoSec, together with some of the largest global organizations and auditors, has created a checklist to follow when preparing for your firewall audit. Simplify risk mitigation while staying compliant all of the time!

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now