04-16-2012 12:16 PM - edited 03-17-2019 11:04 PM
I am running TMSXE 2.2 and getting an error on enabling sinks: interface unknown. Has anyone else seen this?
Solved! Go to Solution.
04-16-2012 01:44 PM
Hi ok, this is a known issue with tmxe 2.x on server 2008. It might happen under heavy load and randomly. Only workaround is to reboot the server for a temporary fix or install it on win 2003 server, im not sure if you can restart the information store service to quick fix it, but as I remember it need to reboot. This issue is not present with TMSXE 3.0.
The issue is described as a note in TMSXE 2.3.x documentation. I think its in the installation guide. But the issue is there for 2.2 as well and win2k8.
I hate to give bad news but at least you know that its not your fault.
/magnus
Sent from Cisco Technical Support iPhone App
04-16-2012 12:46 PM
Hi
Are you running it on windows server 2008?
Sent from Cisco Technical Support iPhone App
04-16-2012 12:50 PM
Hi Magnus,
Yes, 2008 SP 2. The main reason I noticed it is because I am having an issue with one video unit. When you schedule it through Outlook, it doesnt get booked on the backend with TMS. Every other room in TMS books fine through Outlook.
04-16-2012 01:44 PM
Hi ok, this is a known issue with tmxe 2.x on server 2008. It might happen under heavy load and randomly. Only workaround is to reboot the server for a temporary fix or install it on win 2003 server, im not sure if you can restart the information store service to quick fix it, but as I remember it need to reboot. This issue is not present with TMSXE 3.0.
The issue is described as a note in TMSXE 2.3.x documentation. I think its in the installation guide. But the issue is there for 2.2 as well and win2k8.
I hate to give bad news but at least you know that its not your fault.
/magnus
Sent from Cisco Technical Support iPhone App
04-16-2012 01:48 PM
Hi Magnus,
Thanks for the info. Glad to see its not something I missed. When you say "rebbot the server" are you referring to rebooting the Exchange server TMSXE 2.2 is on or to rebooting TMS? We have clustered 2008 servers that TMSXE is on right now, so rebooting that may not be a big deal.
Thanks for the help.
04-17-2012 07:42 AM
im not sure if you can restart the information store service to quick fix it, but as I remember it need to reboot.
Restarting the Exchange Information Store will also (temporarily) bring back service; there is no need to reboot the entire server.
But really: all customers affected by the "interface is unknown" problem (defect #CSCtr25483) should migrate to TMSXE 3.0 as soon as possible.
04-17-2012 08:00 AM
Yes, we are going to look at applying the hotfix in the short term. TMSXE is on seperate Exchange cluster that can be rebooted with no impact except to tmsxe. We will be moving to 3.0, but that will still be a bit of time before we have everything ready.
04-16-2012 01:52 PM
I'm referring to rebooting the exchange server where tmsxe resides, yes.
I'm glad this info helped you.
/magnus
Sent from Cisco Technical Support iPhone App
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide