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: 
mikefromoke
Creator II
Creator II

nsq caused trouble with scheduler

Hi,

we use nPrinting ver16.4, installed on QV-Server.

There are 5 Reports scheduled for nPinting to mail pdf-documents.

In the last week we had some trouble, because the scheduler stopped working, the nPrinting-service still was started.

After testing and support we found out, that one of the 5 nsq-files was the reason for the trouble.

Only way to solve that problem and get the scheduler started again, was to uninstall and re-install the nPrinting-server.

Now, after one week without starting the one nsq, we have now problems.

If i start that nsq manual, there is no problem....

​We will build this nsq new, without copying anything from the old one, to test again.

But, has anyone an idea, why this happened?

Or anyone with the same issue?

regards

4 Replies
ramchalla
Creator
Creator

Hi Micheal,

Please restart the NPrinting services. go to command prompt -> services.msc ->select NPrinting server in the list of services and restart.

maleksafa
Specialist
Specialist

when you say on of the nsq files was the reason, where you able to execute this nsq manually outside of the schedule? is it working fine. what about the scheduler, if you schedule it will it execute and stop or it won't execute at all. is it showing under the monitoring tool of the management application

mikefromoke
Creator II
Creator II
Author

Hi,

yes, we were able to execute it manually.

the scheduler starts to execute, there is an entry in the log-gile, but then it comes to no end, like an "application hang", without any further entry in the log.

the reports, that should start after that task, were not able to start.

mikefromoke
Creator II
Creator II
Author

Hi ram,

we did that, but the scheduler still didn't work. We had to un-install and install the nPrinting Server to solve the problem...

this worked untill the next day, where the report again stopped the scheduler.