Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Richarddb

Pages: 1 [2] 3 4
16
Strange but now it's working again (didn't change anything). Hope it will keep working now :)

17
Running QueueMetrics / Re: Queue details export in Excel
« on: January 26, 2011, 12:02:07 »
Code: [Select]
I think it's

Code:
dateformat_completeshort=MM/dd - HH:mm:ss

Becaise that's the one that does not include the year.
In order to activate it, change the language (e.g. to German) and then change back to English.

Do i need to change it into:
dateformat_completeshort=MM/dd/YYYY - HH:mm:ss ?

And do i need to restart a process or is the change directly active after saving?

18
Where can i check if this is changed? We run daily reports so it's an important issue for us.

19
Before the update there was no problem with it. Do we need to copy a licensefile? Or something else?

20
Running QueueMetrics / Custom Report error after Update to 1.6.3.1
« on: January 25, 2011, 11:41:13 »
I get the following error when i try to run a custom report after the update:




How can this be solved?

21
Running QueueMetrics / Re: Communication error on wallboard
« on: January 20, 2011, 14:00:03 »
I could send/show you a daily log? Because it happens every day between 17.00 PM and 17.10 PM.
It's a catalina.out log of 3.4 MB

22
QueueMetrics installation / Database changes in version 1.6.3
« on: January 19, 2011, 12:06:47 »
Hi,

Soon we will upgrade from version 1.6.0.1 to 1.6.3.
Are there any changes in the database structure? If yes, which ones? (Maybe there is a document for it)

23
Running QueueMetrics / Re: Communication error on wallboard
« on: January 19, 2011, 12:03:09 »
But is there something we can do to not get the Communication error anymore?

24
Running QueueMetrics / Re: Communication error on wallboard
« on: January 14, 2011, 12:04:08 »
Probably this is the code of the time when the error came... do you know if there is anything wrong here?

Class: it.loway.app.queuemetrics.autenticazione.preparaParametriReport
Class: it.loway.app.queuemetrics.validazione.logon
Class: it.loway.app.queuemetrics.autenticazione.effettuaLogOn
[3CAF9104F22CDBAE3B36BC7570E4D854] 201101111706 Tempo totale esecuzione verbo 'qm_realtime2_ds': 684 ms
4.JSON In esecuzione:Tue Jan 11 17:06:48 CET 2011
[E277F52D2481F4F014A8A9D318840B33] 201101111706 Tempo totale esecuzione verbo 'qm_realtime2_ds': 48 ms
4.JSON In esecuzione:Tue Jan 11 17:06:49 CET 2011
[75BF2C3D004397A5AC4410F8BEBC37BA] 201101111706 Tempo totale esecuzione verbo 'qm_realtime2_ds': 51 ms
4.JSON In esecuzione:Tue Jan 11 17:06:50 CET 2011
[3CAF9104F22CDBAE3B36BC7570E4D854] 201101111706 Tempo totale esecuzione verbo 'qm_realtime2_ds': 78 ms
4.JSON In esecuzione:Tue Jan 11 17:06:52 CET 2011
LoadAttivitaAgente - modo file - Agente 'Agent/2387' - lookback:65000 bytes
Unknown verb: ''
[E277F52D2481F4F014A8A9D318840B33] 201101111706 Tempo totale esecuzione verbo 'qm_realtime2_ds': 47 ms
4.JSON In esecuzione:Tue Jan 11 17:06:54 CET 2011
[3CAF9104F22CDBAE3B36BC7570E4D854] 201101111706 Tempo totale esecuzione verbo 'qm_realtime2_ds': 43 ms
4.JSON In esecuzione:Tue Jan 11 17:06:57 CET 2011
LoadAttivitaAgente - modo file - Agente 'Agent/2438' - lookback:65000 bytes
Unknown verb: ''
[E277F52D2481F4F014A8A9D318840B33] 201101111706 Tempo totale esecuzione verbo 'qm_realtime2_ds': 39 ms
4.JSON In esecuzione:Tue Jan 11 17:06:59 CET 2011
LoadAttivitaAgente - modo file - Agente 'Agent/2689' - lookback:65000 bytes
Unknown verb: ''
[75BF2C3D004397A5AC4410F8BEBC37BA] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 49 ms
4.JSON In esecuzione:Tue Jan 11 17:07:00 CET 2011
[3CAF9104F22CDBAE3B36BC7570E4D854] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 46 ms
4.JSON In esecuzione:Tue Jan 11 17:07:02 CET 2011
[E277F52D2481F4F014A8A9D318840B33] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 48 ms
4.JSON In esecuzione:Tue Jan 11 17:07:04 CET 2011
[3CAF9104F22CDBAE3B36BC7570E4D854] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 47 ms
4.JSON In esecuzione:Tue Jan 11 17:07:07 CET 2011
[E277F52D2481F4F014A8A9D318840B33] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 147 ms
4.JSON In esecuzione:Tue Jan 11 17:07:10 CET 2011
[75BF2C3D004397A5AC4410F8BEBC37BA] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 47 ms
4.JSON In esecuzione:Tue Jan 11 17:07:10 CET 2011
[3CAF9104F22CDBAE3B36BC7570E4D854] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 45 ms
4.JSON In esecuzione:Tue Jan 11 17:07:12 CET 2011
[E277F52D2481F4F014A8A9D318840B33] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 45 ms
4.JSON In esecuzione:Tue Jan 11 17:07:14 CET 2011
[3CAF9104F22CDBAE3B36BC7570E4D854] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 52 ms
4.JSON In esecuzione:Tue Jan 11 17:07:17 CET 2011
[E277F52D2481F4F014A8A9D318840B33] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 45 ms
4.JSON In esecuzione:Tue Jan 11 17:07:19 CET 2011
[75BF2C3D004397A5AC4410F8BEBC37BA] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 49 ms
4.JSON In esecuzione:Tue Jan 11 17:07:20 CET 2011
[3CAF9104F22CDBAE3B36BC7570E4D854] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 51 ms
4.JSON In esecuzione:Tue Jan 11 17:07:22 CET 2011
[E277F52D2481F4F014A8A9D318840B33] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 49 ms
4.JSON In esecuzione:Tue Jan 11 17:07:24 CET 2011
LoadAttivitaAgente - modo file - Agente 'Agent/2394' - lookback:65000 bytes
Unknown verb: ''
[3CAF9104F22CDBAE3B36BC7570E4D854] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 55 ms
4.JSON In esecuzione:Tue Jan 11 17:07:27 CET 2011
[E277F52D2481F4F014A8A9D318840B33] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 59 ms
4.JSON In esecuzione:Tue Jan 11 17:07:29 CET 2011
[75BF2C3D004397A5AC4410F8BEBC37BA] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 44 ms
4.JSON In esecuzione:Tue Jan 11 17:07:30 CET 2011
[3CAF9104F22CDBAE3B36BC7570E4D854] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 49 ms
4.JSON In esecuzione:Tue Jan 11 17:07:32 CET 2011
[E277F52D2481F4F014A8A9D318840B33] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 48 ms
4.JSON In esecuzione:Tue Jan 11 17:07:34 CET 2011
[3CAF9104F22CDBAE3B36BC7570E4D854] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 44 ms
4.JSON In esecuzione:Tue Jan 11 17:07:37 CET 2011
[E277F52D2481F4F014A8A9D318840B33] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 45 ms
4.JSON In esecuzione:Tue Jan 11 17:07:39 CET 2011
[75BF2C3D004397A5AC4410F8BEBC37BA] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 45 ms
4.JSON In esecuzione:Tue Jan 11 17:07:40 CET 2011
[3CAF9104F22CDBAE3B36BC7570E4D854] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 52 ms
4.JSON In esecuzione:Tue Jan 11 17:07:42 CET 2011
[E277F52D2481F4F014A8A9D318840B33] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 40 ms
4.JSON In esecuzione:Tue Jan 11 17:07:44 CET 2011
[3CAF9104F22CDBAE3B36BC7570E4D854] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 55 ms
4.JSON In esecuzione:Tue Jan 11 17:07:47 CET 2011
*** DBVER:19
*** Esce 3
REQUEST:

25
Running QueueMetrics / Re: Communication error on wallboard
« on: January 13, 2011, 11:29:50 »
There are some localhost_log files which are around 2GB each

26
Running QueueMetrics / Re: Queue details export in Excel
« on: January 13, 2011, 11:12:39 »
The settings are now like this:

dateformat_complete=MMMM dd yyyy, HH:mm
dateformat_date=yyyy-MM-dd
dateformat_completeshort=MM/dd - HH:mm:ss
dateformat_time=HH:mm:ss
dateformat_timeshort=HH:mm
dateformat_flow=1

Which one should i change?

27
Running QueueMetrics / Queue details export in Excel
« on: January 13, 2011, 10:36:17 »
Hi,

When i do an export of queue details of december 2010, the first column is filled with the date. But Excel automatically adds a year to it, in this case the current year 2011 so the information is not correct.

Is there an option where you can do an export including the year so Excel doesn't make it 2011?

It's a custom export in the tab All from Queue details.

28
Running QueueMetrics / Re: Communication error on wallboard
« on: January 13, 2011, 09:42:09 »
Since 2 months it happens and always on the same time around 5, we didn't change anything. Around 5 pm there are almost no callers.
In which log could there be information?

When the screen refreshes, it's working again so it's a quit strange error.

29
Running QueueMetrics / Communication error on wallboard
« on: January 11, 2011, 07:25:31 »
Hi,

Since a few days our wallboard gives an error around 5 PM with the following error code:

Communication error: RPC server did not send response before timeout

What does it mean and how can we solve this?

30
The problem was already before the change, and the change had no effect...

Pages: 1 [2] 3 4