Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Uniphi memory errors on idle reason codes via Citrix

Status
Not open for further replies.

bobthemule

Technical User
Sep 17, 2009
3
IE
Uniphi memory error when using Aspect idle reason codes via Citrix

Hi,

Has anyone experienced the following on Citrix?

We are running;

Aspect Call Centre 9.3 and Aspect Uniphi Connect 1.2.1 CM07 via Citrix,


We do not have any issues until we activate ‘idle reason codes’, we then see the Uniphi application hang with the user getting the following error;

UNIPHISERVER.EXE - APPLICATION ERROR
instruction at "0x7c82a0f0" referenced memory at "0x004dd59e". memory could not be "written"

The corresponding emulator log looks like this;

2009-09-12 08:56:56,326 ERROR Emulator ReceiveLenAndProtoCB grp=66,inst=595 - Error reading length and protocol data from the client socket!!!
Exception: System.Net.Sockets.SocketException

Uniphi locks up at this point and the user has to restart the application, giving the following message.

Message: An existing connection was forcibly closed by the remote host
Source: System
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at Aspect.CallCenter.Uniphi.Emulator.ReceiveLenAndProtoCB(IAsyncResult ar)


I did see a thread which suggested an upgrade to Uniphi Connect 1.3.0.8 had resolved similar memory issues, however, Aspect said this version had additional features that we did not require and that 1.2.1 CM07 should suffice.

Any ideas where to go next?

Thanks, bob
 
Does this happen on all instances? I had a couple memory errors like this and we upgraded to 1.3 CM01 and did a complete uninstall (clean up registry), rename the Uniphi Connect folder to "Uniphi Connect.old" and then reinstall. This fixed my issue.
 
This error occurs on subsequent calls after the Aspect 'class of service' has been updated to include 'idle reason codes' and it happens for any user connected to this particular Citrix Server, which has been taken out of the 'Citrix Farm' but is still an identical build.

I'll ask Aspect again to provide 1.3 CM01 for our test Citrix Server, so at least we can discount this as a possible solution.

Thanks bob.
 
Hi arznrchrd,

Were your memory error issues specific to idle reason codes?

Was there a specific reason for the upgrade to 1.3 CM01?

Thanks bob.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top