11-01-2004 05:25 AM - edited 03-18-2019 03:45 PM
Im seeing a message in the event viewer about one of my unity ports... See below:
Port 17 has been busy since Sep 14, 2004 @ 11:10:51. The System Threshold is 240 minutes, so this port might be misbehaving.
after going to the port status monitor, nothing was on that particular port, so I highlighted it and reset it... Then the following showed up in the event log:
Component Miu: Thread 0x00000920 had a Failure on Port 17 in Method CAvMiuLine::Drop()
DESCRIPTION: Drop() called lineDrop() 0 times with result UNDEFINED HRESULT..
DETAILS:
HCALL: 0x0001047D
CallState: LINECALLSTATE_UNKNOWN.
CALL SEQUENCE:
[12:22:48:964 - 0x00000CD0] MakeCall(96905994) - E_MIU_RESOURCE_UNAVAILABLE
[12:22:48:995 - 0x00000CD0] MakeCall(96905994) entered
[12:22:48:995 - 0x00000CD0] MakeCall(96905994) - E_MIU_RESOURCE_UNAVAILABLE
[12:22:49:011 - 0x00000CD0] MakeCall(96905994) entered
[12:22:49:011 - 0x00000CD0] MakeCall(96905994) - E_MIU_RESOURCE_UNAVAILABLE
[12:22:49:027 - 0x00000CD0] MakeCall(96905994) entered
[12:22:49:027 - 0x00000CD0] MakeCall(96905994) - E_MIU_RESOURCE_UNAVAILABLE
[12:22:49:042 - 0x00000CD0] MakeCall(96905994) entered
[12:22:49:042 - 0x00000CD0] MakeCall(96905994) - E_MIU_RESOURCE_UNAVAILABLE
[12:22:49:074 - 0x00000CD0] MakeCall(96905994) entered
[12:22:49:074 - 0x00000CD0] MakeCall(96905994) - E_MIU_RESOURCE_UNAVAILABLE
[12:22:49:089 - 0x00000CD0] MakeCall(96905994) entered
[12:22:49:089 - 0x00000CD0] MakeCall(96905994) - E_MIU_RESOURCE_UNAVAILABLE
[12:22:49:105 - 0x00000CD0] MakeCall(96905994) entered
[12:22:49:105 - 0x00000CD0] MakeCall(96905994) - E_MIU_RESOURCE_UNAVAILABLE
[12:22:49:120 - 0x00000CD0] MakeCall(96905994) entered
[12:22:49:120 - 0x00000CD0] MakeCall(96905994) - E_MIU_RESOURCE_UNAVAILABLE
[12:22:49:152 - 0x00000CD0] MakeCall(96905994) entered
[12:22:49:152 - 0x00000CD0] MakeCall(96905994) - E_MIU_RESOURCE_UNAVAILABLE
[12:22:49:167 - 0x00000CD0] MakeCall(96905994) entered
[12:22:49:167 - 0x00000CD0] MakeCall(96905994) - E_MIU_RESOURCE_UNAVAILABLE
[12:22:49:183 - 0x00000CD0] MakeCall(96905994) entered
[12:22:49:183 - 0x00000CD0] MakeCall(96905994) - E_MIU_RESOURCE_UNAVAILABLE
[12:22:49:199 - 0x00000CD0] MakeCall(96905994) entered
[12:22:49:199 - 0x00000CD0] MakeCall(96905994) - E_MIU_RESOURCE_UNAVAILABLE
[12:22:49:230 - 0x00000CD0] MakeCall(96905994) entered
[12:22:49:230 - 0x00000CD0] MakeCall(96905994) - E_MIU_RESOURCE_UNAVAILABLE
[12:22:49:245 - 0x00000CD0] MakeCall(96905994) entered
[12:22:49:245 - 0x00000CD0] MakeCall(96905994) - E_MIU_RESOURCE_UNAVAILABLE
[12:22:49:261 - 0x00000CD0] MakeCall(96905994) entered
[12:22:49:386 - 0x00000CD0] MakeCall(96905994) entered
[12:22:49:386 - 0x00000CD0] MakeCall(96905994) - Eentered
[12:22:50:824 - 0x00000CD0] MakeCall(96905994) - E_MIU_RESOURCE_UNAVAILABLE
[12:22:50:855 - 0x00000CD0] MakeCall(96905994) entered
[12:22:50:855 - 0x00000CD0] MakeCall(96905994) - E_MIU_RESOURCE_UNAVAILABLE
[12:22:51:042 - 0x00000CD0] MakeCall(96905994) entered
[12:22:51:042 - 0x00000CD0] MakeCall(96905994) - E_MIU_RESOURCE_UNAVAILABLE
[12:22:51:058 - 0x00000CD0] MakeCall(96905994) entered
[12:22:51:058 - 0x00000CD0] MakeCall(96905994) - E_MIU_RESOURCE_UNAVAILABLE
[12:22:51:105 - 0x00000CD0] MakeCall(96905994) entered
[12:22:51:105 - 0x00000CD0] MakeCall(96905994) - E_MIU_RESOURCE_UNAVAILABLE
[08:08:38:784 - 0x00000920] StopIO(TERM_DROPPED) entered
[08:08:38:784 - 0x00000920] StopIO(TERM_DROPPED) - S_OK
I went into the call manager for that port and did a reset on it... but it still shows UNREGISTERED...
Help??
11-01-2004 08:21 AM
Hi -
You didn't mention your Unity version. I am running 4.0(4) and have not had this type of problem since upgrading. I did experience a similar problem with 3.1(5) where a port would occasionally hang in TRaP. Make sure your Unity TSP version is current. If the port is unregistered to CallManager, I believe only a Unity server reboot will correct this. Somewhere in your application event log prior to 11:10:51 you will see the MIU error that resulted in the hung port. If this continues, TAC can help you set up the necessary micro traces to further diagnose the cause.
Sincerely,
Ginger
11-01-2004 08:59 AM
yes, sorry unity 3.1.5. The error I had included was an MIU error... I can reboot, just wasn't the preferred method.. its probably an anomoloy as no changes have been made to either call manager or unity and its been functioning fine... I was really trying to see if there was any way to fix without a reboot is what I was looking for...
Thank you Ginger
Chris
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: