Moderators: enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, s0lid
VicidialNOW is a server ... (if you just put this in to mean "I'm testing it" ignore this question, it just threw me off a bit).test vicidialnow on agent system
there is a problem of time synchronization in your system. please contact administrator
mflorell wrote:For some background on this error, it is new for 2.0.5.
The code in the agent application that synchronizes the time with the server runs a check on the server_updater table and the web server to see if either the dialer, web server or database are more than a few seconds out of time sync from each other. If they are then the message appears.
It can also be an indicator that one script or several scripts are not running at all on the dialer.
We have had this in production for several months at many client sites and it usually preemptively causes us to fix time sync problems before they become critical, or in the case of server process not running, the message is received faster by IT now that this message shows up on the agent screen than before this message was displayed.
gardo wrote:Are you running a default install of VicidialNOW on a single server?
mflorell wrote:This warning cannot really be safely ignored. If it comes up there is at the very least a time sync problem that will cause logging issues, or at worst will mean that you will miss calls or your system won't run at all.
After you changed the IP address, did you run the server ip address change script?
/etc/init.d/apache2 restart
Please tell us where you read this error (web browser? CLI? Moon Spots?)Purkuutoop wrote:how to fix run-time error 339???
Its says Run-time error 339:
Component MSINET.OCX or one of its dependencies not correctly registered: a file is missing or invaild
at the first time that i run conquer after setup agine
and when i try to login to my account the client crash
abacus1 wrote:I have tried all option but no luck.
Can someone pls help me on this.
This error is unacceptable.
Is it bug in vicidialnow ?
iptables -F
iptables -P INPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables -P OUTPUT ACCEPT
99.951172% 99.963379% 99.963379% 99.951172% 99.963379% 99.951172%
--- Results after 6 passes ---
Best: 99.963379 -- Worst: 99.951172 -- Average: 99.957275
Return to ViciDialNow - GoAutoDial
Users browsing this forum: Google [Bot] and 12 guests