NPrinting server is not writing schedule Logs, has anyone had this issue? How to solve it?

[Anonymous]

Greetings,

NPrinting Server is running a scheduled job that takes approximately 3 hours to finish, however the Schedule Log is not being created or updated, even though it is parameterised in NPrinting Designer and NPrintingServer.

Has anyone ever had this issue? How to solve it?

Thank you in advance.

Regards,

Susana Silva

[#2]

1. Does the NPrinting Admin user have rights to create files to that directory?
2. Does that path exist (in lots of servers, either there is no c drive, or it's locked down
3. Is there sufficient disk space to create the log file
4. If you run a task manually from the NPrinting Designer (client), do you see the log file being generated in the "Details" window in the middle of the NPrinting window?

[Anonymous]

Greetings Aran,

1. Yes, the NPrintingAdmin user has Adminitrator acess to that directory.
2. The path does exist, i can access it and see other files in it.
3. There are 18Gb left of disk space.
4. When i run the task manually in the NPrinting Designer i can see the log being generated in:

[Frank_S · Accepted solution]

It's possible that you are using the same path to the log file and using the same name for the log file. If the NPrinting designer log file is open when the Server log file attempts to generate, then nothing can be written to the log file.

To ensure you are able to write to the log file.

1. Change the Name of the server log file to something like NPrintingSVC

2. Change the path of the log files away in the NPrinting server management console options from the public folder to a location on the drive the also contains your templates. see below for examples:

c:\NPrinting

c:\NPrinting\templates

c:\NPrinting\logs

c:\NPrinting\Nprinting files

etc

3. After updating the log file name and path, stop the NPrinting service using the NPrinting server management console

4. Start the service from the NPrinting management console.

5. View the log files in the newly created log folder.

If the issue persists, please contact the support desk at the link below.

Technical Product Support | Qlik

[Anonymous]

Thank you Frank, the same file name was the problem,

Changing the log file name solved it.