In our final blog post in our technical tour of Sage 300 ERP diagnostic tools, we take a look at RVSpy, another tool that I am sure is familiar to most of you.
What it is
RVSpy records everything that happens at the business logic layer:
Why do you need it?
RVSpy records operations on all application views and includes any third party applications that you have.
Sometimes a DBSpy is run in combination with the RVSpy to show what database calls are made for a particular view.
Here is a video that outlines how you can run a combined RVSpy/DBSpy:
What’s in an RVSpy log?
Views are identified by View IDs where the first two characters are always the application prefix so you can see if a view is coming from Sage 300 ERP or a third party application:
Here are some of the common return codes for functions you will see in the RVSpy log:
– 0 = success
– 1 = Warning
– 1020 = RECORD_NOT_FOUND
– 1024 = RECORD_INVALID
– 1026 = RECORD_CONFLICT (Record modified by another user)
– 1041 = TABLE_NOT_FOUND
– 1120 = KEY_INVALID
When to run an RVSpy
We have a video that details how to run an RVSpy log:
Now there are certain issues that you may encounter where running any of the spy logs (RVSpy, DBSpy or COM Spy) won’t be useful. Those situations include:
If your logs don’t capture anything then the issue may be happening before it hits the three layers as noted in the above diagram. This could indicate that it is an environment issue.
So that concludes our technical tour of the Sage 300 ERP diagnostic tools. Hope you enjoyed the journey. If you have any questions about any of our diagnostic tools, ask away in the comments.
For the latest support news and updates...Follow us on...
Hello everyone if you are create a uniq password for window10 and you are not conform how to create the new password if you are like the more conformation are there Microsoft password manager some people are like this website you are enjoy the more movements of the life.