x Want to participate? Join the group to interact
Options
  • State Not Answered
  • Replies 4 replies
  • Subscribers 42 subscribers
  • Views 2260 views
  • Users 0 members are here
Browse Forums
Announcements
68
topics
93
replies
Customization and Integration
262
topics
822
replies
Financials, Projects, and Administration
382
topics
843
replies
General Discussion
327
topics
836
replies
Installation and Technical Issues
335
topics
1k
replies
Manufacturing, Distribution, and Applications
341
topics
696
replies
Reporting and Analytics
124
topics
482
replies
tcallin

Errors in tracker when closing a VB task

Posted By

I will start this off that I am using the tracker to review issues with a third party integration.

With that disclaimer, we are moving from 7.3 to 7.6 (cannot do 7.7 yet due to add-on). I am seeing that when we close most VB tasks (this one I used Maintain Items), the following string of errors display in the tracker feed.

10:25:42(5911 - 261012477)-UnloadSelf(Item Maintenance: ltContext 64)
10:25:42(1 - 261012478)-CheckUIActiveStateIncludingChild::"Item Maintenance" - GetlUIActive()
10:25:42(1 - 261012479)-"Item Maintenance" - GetlUIActive Failed, return value: 0
10:25:42(1 - 261012480)-UnloadObject::"Item Maintenance" - QueryShutdown(ltContext: 64)
10:25:42(2 - 261012482)-"UnloadObject" - UnloadUI(ltContext: 91161784)
10:25:42(2 - 261012484)-UnloadObject::"Item Maintenance" - TerminateObject(ltContext: 64)
10:25:42(2 - 261012486)-ReleaseSystemObject: Object not found.
10:25:42(2 - 261012488)-Caught Exception: "ReleaseSystemObject" - OLE Dispatch Error: m_scError:-2147175422(0x8004b402), Desc:ReleaseSystemObject: Object not found., Help:0, Help File-:: System Definition:

I just confirmed with another customer who has 7.6 running that they are seeing the same behavior. No known application issues.

I am a strong supporter of not ignoring errors even if they don't seem to be causing corruption or stop the user from performing a specific task.

 

Any feedback the community has would be appreciated.
Thank you all.

  • 0
    Just a shot in the dark ... if you are cleaning up objects when shutting down, are you checking to make sure the objects exist before setting them to nothing (especially if they are optionally created)?
  • 0 in reply to Ramon M.
    Hi Ramon. The error is from standard Sage code/objects. No custom code here. The errors I mentioned are shown with out of the box Sage 500 7.6. I tested 7.6 to 7.6.8. Same error shown in tracker for the VB objects for each version of 7.6. Test it with Maintain Items to see the behavior.
    If you are still at Sage, can you look at source and see why this is happening?
  • 0 in reply to tcallin
    I looked into it briefly. Applications are having some sort of trouble shutting down a common object. Don't know why. I saw that this has come across Support's view, and I can only proceed further if they set a high enough priority. It has been happening since at least 7.4, and probably earlier, and has no know side effects other than Tracker messages.

    Sorry I don't have any good news for you at this point.
  • 0 in reply to Ramon M.
    I figured as much. I don't have source code anymore or I would have tried to narrow down what was not shutting down.
    In general, I hate to ignore an error message due to it not causing data corruption or an application error. I am one of the few who uses the tracker to look into issues. In the case, the tracker found an error that the application didn't know it had. Thanks Ramon.

*Community Hub is the new name for Sage City