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: 
iLoveDataVis
Contributor II
Contributor II

NPrinting Scheduler service stopping automatically on the server - what is the cause? Server inactivity perhaps?

Hello,

We have NPrinting installed in a single node server.

It is a relatively new environment and things function mostly fine.

However, we have noticed services such as the Scheduler stop automatically after a while. I have not much concrete data but was thinking, could it be due to a day or X hours of inactivity? I.e. nobody using NPrinting for a good few hours can cause the service to automatically stop?

The problem is we then have to log into the server and start it.

If it is due to inactivity, is there a way to extend the inactivity timeout value for the NPrinting services?

Labels (2)
1 Solution

Accepted Solutions
JustinDallas
Specialist III
Specialist III

I had the same issue years ago.  Are NPrinting and Qlik hosted on the same server? 

 

I learned the hard way that if you do that, NPrinting will just go to sleep without any fanfare.

View solution in original post

5 Replies
Frank_S
Support
Support

Good morning!

When you start the scheduler service are you able to gracefully shut it down? (send a stop command and the service stops without doing 'end task' in the task manager)

If not then it is likely your scheduler service has become corrupted.

 

It's also possible that there is a problem with either the RabbitMQ users and permissions or the internal NPrinting certificates.

Use the following article to check both these points.

You may attempt to repair on your own but I would suggest starting a support request so we can assist you with this one on one.

 

But before you do any of the above, please ensure to make a backup of your NPrinting Database in the event that you need to perform a complete uninstall and re-installation.

 

Kind regards...

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

Hi @Frank_S 

 

Yes we can stop and start the service fine. All the services run as normal.

But sometimes we notice services such as Scheduler are in a stopped state and we don't know why. Our theory is the server/NPrinting is not being used so it automatically stops some services?

Frank_S
Support
Support

The next step is to follow the troubleshooting points in the previous comment even if the scheduler service shuts down gracefully.

NPrinting services are windows services and should not stop on their own due to inactivity. If they are stopping without any user intervention, this is generally indicative of a problem/corruption within the underlying windows NPrinting service.

 

You may use the suggested troubleshooting/diagnoses steps in the previous comments. If they reveal no issue, I would suggest to start a support case if the issue is persistent.

 

One thing to check in the meantime as well is to ensure that any antivirus running on the NP server is excluding all NPrinting files and folders.

Also ensure that the messaging and repo services are using 'Local System' and 'Network Service' accounts respectively as seen here below. These are configured by NPrinting upon installation and should not be changed.

 

 

Kind regards...

 

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

I had the same issue years ago.  Are NPrinting and Qlik hosted on the same server? 

 

I learned the hard way that if you do that, NPrinting will just go to sleep without any fanfare.

Frank_S
Support
Support

Interesting point!

 

It was recognized that in this particular scenario that the NP and QS server were installed on the 'same' computer for demo purposes - which is NOT supported in a PROD environment  - but that perhaps and for that very reason (same server install)  could very well be the cause of the issue reported. 

 

 

Thank you @JustinDallas

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