Skip to main content
Announcements
Defect acknowledgement with Nprinting Engine May 2022 SR2, please READ HERE
cancel
Showing results for 
Search instead for 
Did you mean: 
surender2709
Contributor
Contributor

Error: The object has been run down by the stub manager while there are external clients

We are getting the Error The object has been run down by the stub manager while there are external clients at least once in a week and right after rebooting the Nprinting server, we don't see any issues.

But again after few days ( nearly 1 week ), we are encountering the issue again and we are end up in restarting the server.

Requesting you to share the idea's or solution on this.

 

 

Labels (2)
3 Replies
Andrea_Bertazzo
Support
Support

Hi Surender2709,

Do you have any tasks sending an e-mail message without reports attached?

If not, please, collect the information asked in this post and open a case for Qlik Support:

https://community.qlik.com/t5/Qlik-NPrinting-Discussions/NPrinting-The-object-has-been-rundown-by-th...

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up ! 🙂
Ruggero_Piccoli
Support
Support

Hi,

QlikView NPrinting 16.* is no more supported. I suggest you to try to upgrade to latest version of the 16 series, the 16.10 and test with it. 

I strongly suggest you to plan your migration to Qlik NPrinting 17+, latest version is May 2021.

Best Regards,

Ruggero



Best Regards,
Ruggero
---------------------------------------------
When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads with a LIKE if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads with LIKEs if you feel additional info is useful to others.
Frank_S
Support
Support

Hi @surender2709 

I agree with @Ruggero_Piccoli that Migrating to a supported NPrinting platform is your best best. This way if you still see the issue, then we can thoroughly troubleshoot the issue.

There is only one other instance of this error and it was reported in NP 18 (not NP 16) and it appears related to how the individual was trying to implement task notifications. So if that is the case with you, please know that Task Notification are indeed available in current supported versions of NPrinting.

For more information about the issue and solution see the following community discussion.

How to configure Task Notifications in NPrinting May 2021.

Kind regards...

Please remember hit the 'Like' button and for helpful answers and resolutions, click on the 'Accept As Solution' button. Cheers!