No history log been stored
-
- Posts: 49
- Joined: Tue May 22, 2012 4:40 pm
No history log been stored
Bill, we are experiencing problem with the program not saving or logging the incoming calls. The system recognizes the callers information, display on the monitor and also advanced scripts work and sends out texts to out to our staff members but doesn't log the caller info in the main windows under the tab Calls field and also doesn't show up on the online web version either. Our last log file was 2/10/2016 and we are useing version 3.0.0.0 any thoughts
Re: No history log been stored
Hi samsungpower,
First, make sure the data drive has free disk space. The data drive is normally the boot drive, and can be verified in the About box (Help menu -> About Ascendis Caller ID) by right-clicking on the "Ascendis Software" text at the bottom of the window and choosing "Open Data Folder").
If there's plenty of free disk space (> 1GB should be safe), please send a Technical Support Report (on the Help menu) so I can see any error messages. If you don't want to send it unless we have no other options, at least save one now before we lose the information it contains.
Then, try exiting Ascendis Caller ID (File -> Exit) and restarting it. If the calls are still missing, my best guess is that the database is corrupt, in which case I recommend the following:
If that doesn't solve the problem but the Repair Database command found problems, your best bet is probably to restore a backup. By default, Ascendis Caller ID makes backups each day. The location of the backups is specified in the "Auto Backup" window accessed by File -> Auto Backup Database.
If there's plenty of disk space and no problems were found in the database, then I'll need more information to diagnose the problem. Hopefully the Technical Support Report will help.
Finest regards,
Bill Root
Ascendis Software LLC
First, make sure the data drive has free disk space. The data drive is normally the boot drive, and can be verified in the About box (Help menu -> About Ascendis Caller ID) by right-clicking on the "Ascendis Software" text at the bottom of the window and choosing "Open Data Folder").
If there's plenty of free disk space (> 1GB should be safe), please send a Technical Support Report (on the Help menu) so I can see any error messages. If you don't want to send it unless we have no other options, at least save one now before we lose the information it contains.
Then, try exiting Ascendis Caller ID (File -> Exit) and restarting it. If the calls are still missing, my best guess is that the database is corrupt, in which case I recommend the following:
- Backup the database (File -> Backup Database)
Repair the database (File -> Repair Database)
If that doesn't solve the problem but the Repair Database command found problems, your best bet is probably to restore a backup. By default, Ascendis Caller ID makes backups each day. The location of the backups is specified in the "Auto Backup" window accessed by File -> Auto Backup Database.
If there's plenty of disk space and no problems were found in the database, then I'll need more information to diagnose the problem. Hopefully the Technical Support Report will help.
Finest regards,
Bill Root
Ascendis Software LLC
-
- Posts: 49
- Joined: Tue May 22, 2012 4:40 pm
Bill,
Drive disk free space 124 GB, exit and restart, send you the Technical Support Report, backup database no errors, repair database no errors but still same results incoming call not being saved or log. We were in the starting process of replace this old computer but was hoping it would last 2 -3 more months.
Drive disk free space 124 GB, exit and restart, send you the Technical Support Report, backup database no errors, repair database no errors but still same results incoming call not being saved or log. We were in the starting process of replace this old computer but was hoping it would last 2 -3 more months.
Thank you for the report. Unfortunately it didn't include any relevant error messages. When the problem happens again can you send another report? If the problem happens when you call the monitored phone line(s) with another phone, you should be able to trigger it right away.
I suppose I should ask whether you made any changes to the Ascendis Caller ID configuration recently. It's possible to delete a call from an action, which would cause the behavior you reported.
Finest regards,
Bill Root
I suppose I should ask whether you made any changes to the Ascendis Caller ID configuration recently. It's possible to delete a call from an action, which would cause the behavior you reported.
Finest regards,
Bill Root
-
- Posts: 49
- Joined: Tue May 22, 2012 4:40 pm
I reponded to your email you sent me. We have number of calls from the date when it stop working. The only thing I can thing of we added a web page link in our pushover script. It fires on ring action and we thought of that so we delete our changes to bring it back to original and that did fix the problem and so we put the ring action to do nothing restarted the pc and still having the same problem.
-
- Posts: 49
- Joined: Tue May 22, 2012 4:40 pm
So the problem went away when you changed the ring action? But it came back when you changed the ring action to "Do Nothing"?The only thing I can thing of we added a web page link in our pushover script. It fires on ring action and we thought of that so we delete our changes to bring it back to original and that did fix the problem and so we put the ring action to do nothing restarted the pc and still having the same problem.
-
- Posts: 49
- Joined: Tue May 22, 2012 4:40 pm
Just to clarify for other users it was a typo error "the problem DIDN'T go away"So the problem went away when you changed the ring action? But it came back when you changed the ring action to "Do Nothing"?
The problem is fix now, this is embarrassing
![Embarassed :oops:](./images/smilies/icon_redface.gif)
Thank you for sharing your solution!
I'm happy you fixed the problem, and sorry I didn't think of this. You said when a call came in an older call was highlighted in the Calls list -- this was presumably the actual call, but since the date was wrong, it appeared lower in the list than expected, and with the wrong date, of course.
Windows should be updating the time from the internet periodically, but sometimes the configured time server stops working. Also, I think Microsoft has been extending the window between time updates.
Finest regards,
Bill Root
Ascendis Software LLC
I'm happy you fixed the problem, and sorry I didn't think of this. You said when a call came in an older call was highlighted in the Calls list -- this was presumably the actual call, but since the date was wrong, it appeared lower in the list than expected, and with the wrong date, of course.
Windows should be updating the time from the internet periodically, but sometimes the configured time server stops working. Also, I think Microsoft has been extending the window between time updates.
Finest regards,
Bill Root
Ascendis Software LLC