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

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Provisioning failed: HTTP code=500 - Meaning?

On webGUI of SX10 recently upgraded to 7.2.0.

  • TMS visibility is fine
  • Endpoint operates fine
  • TMS is able to send and clear phonebooks fine.
  • No Endpoint Troubleshooting Guide avail. for this soft. version (as of this writing)

 

What is cause of this?  Network issue with certain traffic?

Everyone's tags (1)
1 ACCEPTED SOLUTION

Accepted Solutions
VIP Purple

Make sure your TMS supports

TMS 14.5 doesn't support CE software, you can add it to TMS 14.5 if the endpoint is running TC software, but you must upgrade to TMS 15.0 to use CE software as this is the first TMS release to support it.

Also in the most recent releases of endpoint software, both TC and CE, TLS 1.0 support was removed, so TMS must be able to support TLS 1.1 and 1.2 in order to communicate with the endpoints.  Refer to the TC7 Release Notes on pg 7 and CE8 Release Notes on pg 8 for more information on TLS support.

8 REPLIES
VIP Purple

What all is displayed under

What all is displayed under "Configuration > System Status > Provisioning" in the SX10 web interface?

I'm using 7.1.0 and I don't have any issues that I know of.  What TMSPE template version are you using?

Are you seeing this with any other provisioned endpoints or is it just this one?

New Member

Hi Patrick, Thanks for your

Hi Patrick, Thanks for your input.  It turns out all the endpoints in this particular geographic location are experiencing the same error message.  I appears there is a network visibility issue to the TMS server there.

VIP Green

HTTP Error 500 is a response

HTTP Error 500 is a response back from the server, and a generic one when it can't be more specific about what failed.

What are your provisioning settings set to on your SX10 (Configuration > System Configuration > Provisioning)?  Are they pointing to the correct Provisioning Mode, ExternalManager Address, Path and Protocol?

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.
New Member

Hi Wayne, Thanks for your

Hi Wayne, Thanks for your input.  It turns out all the endpoints in this particular geographic location are experiencing the same error message.  I appears there is a network visibility issue to the TMS server there.

New Member

I'm having the same issue on

I'm having the same issue on a new SX10 version 8.1.1 and the fix noted has no affect. Also having trouble adding it to TMS (14.5) but the two could be related. Any help would be greatly appreciated. 

VIP Purple

Make sure your TMS supports

TMS 14.5 doesn't support CE software, you can add it to TMS 14.5 if the endpoint is running TC software, but you must upgrade to TMS 15.0 to use CE software as this is the first TMS release to support it.

Also in the most recent releases of endpoint software, both TC and CE, TLS 1.0 support was removed, so TMS must be able to support TLS 1.1 and 1.2 in order to communicate with the endpoints.  Refer to the TC7 Release Notes on pg 7 and CE8 Release Notes on pg 8 for more information on TLS support.

New Member

To add some value to this

To add some value to this thread, I am providing a fix down below.

 

Log into the endpoint Web GUI

Configuration > System Configuration > Provisioning

Under the menu for ExternalManager, set the Path to the following:

tms/public/external/management/systemmanagementservice.asmx

 

For some reason, the ExternalManager Path does not recognize the sequence for "Phonebook" and fails the provisioning status.  Simply changing "phonebook" to "management" resolves the issue.

-JL

New Member

Thanks for this.  This is the

Thanks for this.  This is the fix.  We just got this issue AGAIN on our desk from another customer and that was the issue.

1555
Views
5
Helpful
8
Replies
CreatePlease login to create content