Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Community Member

TMS No HTTP response

Hey All,

I'm investigating an issue currently where TMS (14.3.2) is reporting No HTTP response (Or No HTTPS response, depnding on what setting is configured in TMS) for:

  • MSE Supervisor 8050 2.3(1.31)
  • MCU 4.4(4.32)
  • MSE 8510 4.4(4.32)

There are over 50 endpoints along with a VCS Control (sitting on the same network segment as the three above devices) and VCS Expressway and no other devices have this issue.

The log-liveservice.txt contains:

2014-01-10 12:26:22,967 [RTLib.FsmProcessor : SYS:63] WARN  Tandberg.TMS.Live.Fsm.SystemFeedbackHandlerFSM - Failed getting events from system, 63

2014-01-10 12:26:22,967 [RTLib.FsmProcessor : SYS:63] ERROR Tandberg.TMS.Live.Fsm.SystemFeedbackHandlerFSM -

Tandberg.TMS.Common.SystemExceptions.CommunicationFailureHTTPException: hostAddress: x.x.x.x, description: Posting https request to 'https://x.x.x.x/RPC2' failed after 100023 ms (5000).. URL: http://x.x.x.x/RPC2, base exception: The operation has timed out

   at Tandberg.TMS.SystemAPI.Util.Codian.Communication.PostUrl(String networkAddress, Int32 port, String url, String data, Int32 httpTimeout)

   at Tandberg.TMS.SystemAPI.CodianMCU.XMLRequestor.GetRPC2Document(XmlNode commandDocument)

   at Tandberg.TMS.SystemAPI.CodianMCU.Status.GetParticipantChanges(Int32 lastRevisionNumber)

   at Tandberg.TMS.Live.Fsm.SystemFeedbackHandlerFSM.Ready_OnGetStatusChangesSignal(GetStatusChangesSignal signal)

Similarly the log-TMSDatabaseScanner.txt contains:

2014-01-10 12:11:35,321 [TMSDBScanner-TMSDatabaseScannerService.Scanners.SystemCdrCollector] WARN  Tandberg.TMS.Service.CallLog.CallLogService - Could not store call log entries for system 63, with message hostAddress: x.x.x.x, description: GetDocument Failed. URL: , base exception: hostAddress: x.x.x.x, description: Posting https request to 'https://x.x.x.x/RPC2' failed after 100035 ms (30000).. URL: http://x.x.x.x/RPC2, base exception: The operation has timed out

2014-01-10 12:13:46,497 [TMSDBScanner-TMSDatabaseScannerService.Scanners.SystemCdrCollector] WARN  Tandberg.TMS.Service.CallLog.CallLogService - Could not store call log entries for system 60, with message hostAddress: x.x.x.x, description: GetDocument Failed. URL: , base exception: hostAddress: x.x.x.x, description: Posting https request to 'https://x.x.x.x/RPC2' failed after 100250 ms (30000).. URL: http://x.x.x.x/RPC2, base exception: The operation has timed out

2014-01-10 12:20:56,617 [TMSDBScanner-TMSDatabaseScannerService.Scanners.SystemCdrCollector] WARN  Tandberg.TMS.Service.CallLog.CallLogService - Could not store call log entries for system 63, with message hostAddress: x.x.x.x, description: GetDocument Failed. URL: , base exception: hostAddress: x.x.x.x, description: Posting https request to 'https://x.x.x.x/RPC2' failed after 100013 ms (30000).. URL: http://x.x.x.x/RPC2, base exception: The operation has timed out

2014-01-10 12:23:06,675 [TMSDBScanner-TMSDatabaseScannerService.Scanners.SystemCdrCollector] WARN  Tandberg.TMS.Service.CallLog.CallLogService - Could not store call log entries for system 60, with message hostAddress: x.x.x.x, description: GetDocument Failed. URL: , base exception: hostAddress: x.x.x.x, description: Posting https request to 'https://x.x.x.x/RPC2' failed after 100012 ms (30000).. URL: http://x.x.x.x/RPC2, base exception: The operation has timed out

Everyone's tags (2)
1 ACCEPTED SOLUTION

Accepted Solutions
Community Member

TMS No HTTP response

Turns out this issue was caused by BITS proxy settings on the network service account:

C:\Windows\system32>bitsadmin /util /getieproxy networkservice

BITSADMIN version 3.0 [ 7.5.7600 ]

BITS administration utility.

(C) Copyright 2000-2006 Microsoft Corp.

BITSAdmin is deprecated and is not guaranteed to be available in future versions

of Windows.

Administrative tools for the BITS service are now provided by BITS PowerShell cm

dlets.

Current Internet proxy settings for account networkservice:

(connection = default)

Proxy usage:  AUTODETECT

C:\Windows\system32>bitsadmin /util /setieproxy networkservice no_proxy

BITSADMIN version 3.0 [ 7.5.7600 ]

BITS administration utility.

(C) Copyright 2000-2006 Microsoft Corp.

BITSAdmin is deprecated and is not guaranteed to be available in future versions

of Windows.

Administrative tools for the BITS service are now provided by BITS PowerShell cm

dlets.

Internet proxy settings for account networkservice set to NO_PROXY.

(connection = default)

C:\Windows\system32>

C:\Windows\system32>

C:\Windows\system32>

C:\Windows\system32>

C:\Windows\system32>

C:\Windows\system32>

C:\Windows\system32>bitsadmin /util /getieproxy networkservice

BITSADMIN version 3.0 [ 7.5.7600 ]

BITS administration utility.

(C) Copyright 2000-2006 Microsoft Corp.

BITSAdmin is deprecated and is not guaranteed to be available in future versions

of Windows.

Administrative tools for the BITS service are now provided by BITS PowerShell cm

dlets.

Current Internet proxy settings for account networkservice:

(connection = default)

Proxy usage:  NO_PROXY

9 REPLIES
VIP Purple

TMS No HTTP response

Do you perhaps have the SNMP community strings configured on all of the devices that are working, and not on the ones that are reporting errors.  I've seen similar behaviour before when that is the case.  Adding the ability for TMS to access the device via SNMP fixed the issue.

Wayne

--

Please remember to rate responses and to mark your question as answered if appropriate

Wayne
--
Please remember to rate responses and to mark your question as answered if appropriate.
Community Member

TMS No HTTP response

Hi Wayne,

SNMP is configured correctly on the devices. Thanks for the response.

VIP Purple

TMS No HTTP response

Hi Jason,

Did these devices just stop working at a certain date or time, or are they new ones that you're adding?  If they did work, then don't any more - what changed in your environment around that time?  Proxy server/firewall/other infrastructure change?

If you delete one of the devices from TMS and re-add it, does it continue to give the error?

There's alos some newer software versions for your MCUs... have you checked the release notes of any of them to see if there's any reported bug/fix?

Wayne

--

Please remember to rate responses and to mark your question as answered if appropriate?

Wayne
--
Please remember to rate responses and to mark your question as answered if appropriate.
Community Member

TMS No HTTP response

I had this with one of my C20s...... I checked everything that's been mentioned in the posts above... as it seems you have.

Then I did a Factory Reset, reconfigured the unit, and it was fine.

Just a thought.

Community Member

Re: TMS No HTTP response

Thanks for your response Derek. I'll leave this as a last resort, while i'm still working with TAC. Also in reference to my earlier post, upgrading had no impact on the problem.

Sent from Cisco Technical Support iPad App

Community Member

Re: TMS No HTTP response

Hi Wayne,

TMS was upgraded from 13.0.2 > 13.2.2 > 14.3.2, no other infrastructure changes have occurred. I did have a look at the release notes but nothing appears to be related. I will try upgrading to the latest versions as a next step now however.

Sent from Cisco Technical Support iPad App

Community Member

TMS No HTTP response

Turns out this issue was caused by BITS proxy settings on the network service account:

C:\Windows\system32>bitsadmin /util /getieproxy networkservice

BITSADMIN version 3.0 [ 7.5.7600 ]

BITS administration utility.

(C) Copyright 2000-2006 Microsoft Corp.

BITSAdmin is deprecated and is not guaranteed to be available in future versions

of Windows.

Administrative tools for the BITS service are now provided by BITS PowerShell cm

dlets.

Current Internet proxy settings for account networkservice:

(connection = default)

Proxy usage:  AUTODETECT

C:\Windows\system32>bitsadmin /util /setieproxy networkservice no_proxy

BITSADMIN version 3.0 [ 7.5.7600 ]

BITS administration utility.

(C) Copyright 2000-2006 Microsoft Corp.

BITSAdmin is deprecated and is not guaranteed to be available in future versions

of Windows.

Administrative tools for the BITS service are now provided by BITS PowerShell cm

dlets.

Internet proxy settings for account networkservice set to NO_PROXY.

(connection = default)

C:\Windows\system32>

C:\Windows\system32>

C:\Windows\system32>

C:\Windows\system32>

C:\Windows\system32>

C:\Windows\system32>

C:\Windows\system32>bitsadmin /util /getieproxy networkservice

BITSADMIN version 3.0 [ 7.5.7600 ]

BITS administration utility.

(C) Copyright 2000-2006 Microsoft Corp.

BITSAdmin is deprecated and is not guaranteed to be available in future versions

of Windows.

Administrative tools for the BITS service are now provided by BITS PowerShell cm

dlets.

Current Internet proxy settings for account networkservice:

(connection = default)

Proxy usage:  NO_PROXY

Community Member

Thank you for posting this

Thank you for posting this Jason, I had the exact same issue on a 14.3.2 that was recently upgraded and placed on server 2008

 

C:\Windows\system32>bitsadmin /util /setieproxy networkservice no_proxy

 

fixed the no https response on all codecs that were on remote subnets.

Cisco Employee

Using netsh and winhttp is

Using netsh and winhttp is the direct way of controlling the proxy settings for the service accounts

See - http://technet.microsoft.com/en-us/library/cc731131(v=ws.10).aspx

 

The cheater list

to reset to no proxy.. open a command prompt and enter

netsh winhttp reset proxy

easiest way to setup the proxy... Open Internet Options Control panel, click Connectiosn tab, click LAN Settings button, and configure proxy section as desired at the bottom of the window, save changes.  Then in a command prompt

netsh winhttp import proxy source=ie

 

Why is this a problem?

Depending on the setup in your environment, the default 'detect proxy' setting may be picking up a proxy config in your environment unintentionally or may be causing extended timeouts before determining no proxy is in use.. leading to timeouts from TMS using the windows HTTP libraries.

Internet Options settings are per user profile, and since the TMS services are running under service accounts, just setting the proxy as the administrator will not apply to the accounts used by TMS.  Setting the winhttp properties allows you to configure the settings for services using winhttp directly.

3171
Views
5
Helpful
9
Replies
CreatePlease to create content