The outdial.exe is giving a error "Command result: Communication error"

[lancebailey]

The outdial has been working fine since November 11 2013, but to day i get this error.

The outdial.exe is giving a error "Command result: Communication error"

[Anonymous]

Lance,

Where were you getting that from the cmd prompt? Or in the UC Server logs?

Somehow it seems to lost contact to the Application service. First thing I would say is to reboot your server.

Are you still getting that error?

If it keeps happening, I would say you would need to open up a support ticket.

-Mark

[lancebailey]

Thanks for you quick response as always.

I rebooted the machine and  that didn't resolve the issue.

I had my vendor  submit the support ticket 

[Anonymous]

Lance,

Sorry I can’t be more help.

Can you give more details?

-When exactly does the error occur?

-What is you manually try to launch the outdial.exe from a cmd prompt?

-Is everything else working on the server?

-Are all services running that are supposed to be running?

-Mark

[lancebailey]

I am using outdial to do appointment reminder calls. When I checked the Log entry for the sent Items None of my calls from monday where there. It had been working fine since September and I also so all of Fridays calls So I went to the command prompt to manually use outdial  and Got the error.

First thing I check was to see if all the automatic services were still running in control panel. Then I restarted the Server. Everything else seems to be working fine. I also tried to obtain a list of all queued calls with outdial.exe from the command line and got the same error.

• Side Note when i use the command to get a list of all queued calls, It gives every call  that was ever made using the outdial.exe. Is there any way to purge the old calls?

[Anonymous]

Will do some digging for you.

Just curious, do you have plenty of HD space?

Regarding your side note,

This is one way I have done it in class.

If you go to “C:\Program Files (x86)\ADTRAN\NetVanta UC Server\Data\System\OutboundCallQueue\” folder there should be all your previous and current call queues.

I have had to go in there an delete all of them before in class. Stop the UC Server Application Services service then select all the files and delete them.

Then restart the service.

-Mark

[lancebailey]

yes i have abot 200 gb of free space

[Anonymous]

Lance,

Need the swlog.txt file. Can you go into the ADTRANLogs folder and delete the current swlog.txt file, then try to run outdial.exe from cmd prompt as you did before to get the error. Then copy and attach the file to the post. You should be able to respond to this email with the file.

Let me know if you have any questions.

-Mark

[lancebailey]

I have attached the file

[Anonymous]

Lance,

Can you test one thing. Before launching the cmd.exe program, can you right click on it and select “run as Administrator” and see if you get the same results. Let me know.

-Mark

[lancebailey]

I tried that and got the same error

[Anonymous]

Lance,

Here is response from Engineering:

Outdial.exe leveraged the authentication from the server just like a client.

The problem seems to be that after authentication when using outdial.exe, it is trying load too much event data and maxes out before returning an event to the command in the shell ….ergo “Communication error”

Can you can navigate to the Admin logs folder: C:\Program Files (x86)\ADTRAN\NetVanta UC Server\Data\Users\00000000\LogArchives

and see how many files exists and what size?

or

Can you log in with the client and see them via the user Admin logs tab? I suspect if this has been in use for some time the logs are just piling up specially if the Client UI is seldom used.

Also check these option settings for log archiving :

-Mark

[lancebailey]

The size of the LogArchives is 88mb with 88 files.

The setting for log archiving where set exactly like your screen shot.

The archive logs in the client under admin date back to December 2012

[Anonymous · Accepted solution]

Delete the files if they are not required, just keep the current log.clg – alternatively move them elsewhere for historical purposes. E.g. create a folder in the ADTRAN root folder called “Old Logs”

Do all that then restart the server for a fresh start. Then try again.

Delete the syslog.txt file before you try again so we can have a fresh one if we need one for debugging purposes again.

-Mark

[lancebailey]

Thank you so much for all your help That fixed everything

[Anonymous]

Awesome! Glad that worked.

Well I can’t take all the credit, I was just a relay between Engineering. I will tell Alex that you said thanks and it worked! He was the man on this one!

Have a great week Lance!

-Mark

[Anonymous]

Lance,

Here is some more info from the PM on your sidenote question:

• Side Note when i use the command to get a list of all queued calls, It gives every call  that was ever made using the outdial.exe. Is there any way to purge the old calls?

From PM:

When using outdial.exe from the command line the server will always maintain a list of past jobs.  When running the Outdial.exe command from the command line, always add the –dd 0 switch. This will automatically purge the outdial queue immediately. Otherwise it will keep it indefinitely.

Hope that helps!

-Mark