Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Buen día. Tenemos un problema con la ejecución de las tareas de publicación de NPrinting.
Resulta que en México, cancelaron el horario de Verano, debido a ésto, el pasado fin de semana NO cambiamos de horario, y mantenemos el llamado "Horario de Invierno".
El problema es que, a pesar de que ajustamos el servidor de NPrinting para que no cambie de horario (Y de hecho no cambió) las tareas de publicación de NPrinting se ejecutan 1 hora antes de lo previsto.
Si reviso los correos que NPrinting envía con los informes, puedo ver que esos correos llegaron a las 6 AM, pero las tareas están configuradas a las 7 AM. Más aún, si reviso el panel de "Ejecución de Tareas" me dice que la tarea se ejecutó a las 7 AM, pero llegó a las 6.
¿Alguien sabe por qué pasa ésto?
Muchas gracias de antemano.
Daylight Savings Time Problem
Good day.
We have a problem with the execution of the NPrinting publish tasks. It turns out that in Mexico, they canceled the Summer time, due to this, last weekend we did NOT change the schedule, and we keep the so-called "Winter Time".
The problem is that, despite the fact that we adjusted the NPrinting server so that it does not change the schedule (And in fact it did not change) the NPrinting publish tasks are executed 1 hour before the expected time. If I check the emails that NPrinting sends with the reports, I can see that those emails arrived at 6 AM, but the tasks are set to 7 AM. Furthermore, if I check the "Task Execution" panel it tells me that the task was executed at 7 AM, but it arrived at 6.
Does anyone know why this happens?
Hi,
We just released May 2023 which has the time zones updated.
From the Release Notes at https://community.qlik.com/t5/Release-Notes/Qlik-NPrinting-Release-notes-May-2023-Initial-Release/ta...
Jira issue ID: OP-95830
The list of time zones has been updated to IANA 2023c.
Best Regards,
Ruggero
Hello @Gabo77
Your original post has been manually translated to English with Google Translate.
To solve this,
That should do it.
Kind regards.
@Gabo77 NPrinting uses the IANA time zone database I believe, so until the database is updated in NPrinting, it still believes the time change did occur. Changing the Windows time will not have any effect, the time zone is internal to Nprinting. We've had this issue with our Brazil customers, since Brazil seems to change DST often.
@Ruggero_Piccoli is this correct?
Hi,
The latest update to the IANA time zona database was made in Qlik NPrinting May 2022 SR3 which has the IANA 2022e. You can see it in the official Release Notes.
If you are using May 2021 please upgrade to latest available version.
When posting new questions in the community please add only one label, the one of the version you are using, because in some cases, like this, the answer could depend on it.
Best Regards,
Ruggero
Hi guys... thanks... i will check it out and come back to you. Regards!
I have the same issue. We'll update the NPrinting version, but I'm afraid this will not work, because you mentiona a May 2022 version, and the official notification of changes in Daylight Saving Time (horario de verano) in México was at october 2022. There is a more recent version of the IANA time zone database?
Hi @EduardoUlloa ,
The most recent version of IANA database available in Qlik NPrinting is 2022e that was added in Qlik NPrinting May 2022 SR3 https://community.qlik.com/t5/Release-Notes/Qlik-NPrinting-Release-Notes-May-2022-Service-Release-3/...
Qlik NPrinting May 2022 SR4 is, at the moment, latest version but it doesn't have IANA database upgrades https://community.qlik.com/t5/Release-Notes/Qlik-NPrinting-Release-notes-May-2022-Service-Release-4/...
Best Regards,
Ruggero
Thanks Ruggero. Do you know if exists any way to update manually the IANA database?
Hi @Gabo77 , it could be very helpful to know the results after your NPrinting update, please comment.
Hi @EduardoUlloa ,
There is not documented way to manually update the IANA database included in Qlik NPrinting. You have to wait next release. Developers are aware of the issue.
Best Regards,
Ruggero