Search results for query: *

Thanks! I just found that also. I tried using the ALL option in the command but it didn't like that. Using the inactive option worked.

I'm trying to remove just one file from our backup system so that it can not be restored any longer. The file was only on our system for one week and was backed up twice. I thought the Delete Backup command was what I needed but running that comes back with a "no files matching search criteria"...

Thanks! It was after we reloaded languages and went to reseat the callpilot card that I finally noticed the controller card was disabled.....duh...all working now....

We have a 61C with CallPilot. After a system shutdown/restart (just flipped the breakers-didn't take CallPilot down gently) the system came back up, call pilot channels show idle but when dialing into voicemail just get one ring then dead air. Went thru Conf.Wizard again which does a shutdown...

Oops...read that too quickly....that's not quite what you're looking for after all......

POSITION IN QUEUE <skillset> is probably what you're looking for.

We were having similar troubles on occasion in a couple different skillsets. On the real-time display a call would show as waiting with an Idle agent, but if the agent hit their display calls in queue button it would show zero waiting. Our maint. tech added an IF CALL NOT QUEUED command in the...

A reboot did fix the problem....Thanks!

I see this is an old message, if you're still out there wondered if you corrected your problem. I'm receiving the same error message. Was thinking of doing a power-down and reseating the card. Wondering if that is a "you need to replace this card" message. Thanks!

Just installed visio 2000 on a users new xp pro pc. When opening a chart a box will display saying "opening page x of x" and then hang. This happens on all the charts they have copied from a win98 pc. From what I can find visio 2000 should be compatible with xp---perhaps not? Any suggestions on...

I don't read this site daily so didn't see your question till today. If you still need answers (and if my memory is correct), we were getting inflated postcall times because the agents were only going not ready for lunch/breaks/etc. We had them log out on those occasions and just use not ready...

At a &quot;>&quot; prompt you can enter ERR ####, where #### is whatever error code you were receiving.