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 derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Error:Feature Failed

Status
Not open for further replies.

floppy1

Technical User
Aug 7, 2009
228
GB
Cluster of two 3300’s recently upgraded to 4.1 SP2

Before upgrade from 4.0 read and executed instructions on Migrating to RDN Synchronization via SDS doc to the letter and all went well, or so it seemed.

Get Error:Feature Failed when attempting to log on to Hotdesk ext 1113. All other hotdesk ext’s are ok. The ext numbers involved are not new and were working before upgrade. Ext 1113 is registered to the main controller. OPS and Enterprise have been decommissioned.

Have tried this from other ext’s at both controllers same error. Any help or ideas would be appreciated.


ok - logs show...

Log Type Maintenance
Log Number 2938
Severity Info
Date 2010/Jul/28
Time 14:31:54
Source MOBILITY
Description Hot Desk : Login of 1113 at 2201 initiated
Module Main
File Name and Line Number Maintenance;0

Log Type Maintenance
Log Number 2939
Severity Info
Date 2010/Jul/28
Time 14:31:54
Source MOBILITY
Description Hot Desk : redirect or update failed for 2201
Module Main
File Name and Line Number Maintenance;0

Log Type Maintenance
Log Number 2940
Severity Info
Date 2010/Jul/28
Time 14:31:54
Source MOBILITY
Description Hot Desk : Login failed at 2201 - Redirect or update issue
Module Main
File Name and Line Number Maintenance;0

Log Type Software
Log Number 2941
Severity Warning
Date 2010/Jul/28
Time 14:31:54
Source ViPER
Description LoginManager::sHandleCookieUpdateResult() -> Cookie update/delete fails for DN=2201 when op = REGISTER_COMPLETED
Module Main
File Name and Line Number LoginManager.cpp;2118


 
Which controller is 1113 registered to?
Which controller did you paste these logs from?

Normally this type of error occurs when the ICP/Xnet IP address is incorrect on one or both of the controllers
Check that they are both correct on both controllers

Share what you know - Learn what you don't
 
ext 1113 is registered on the main controller and logs came from the main controller. checked ICP/xnet is correct. all other hotdesk users work.

have got enougth licences. have deleted ext 1113 and reprogrammed still get failure when logging on as 1113 from any set with correct COS. Customer insists this is an ext that has been working previous to upgrade.

I am going to try to go to site today and investigate further

Thanks
 
The extension you are trying to log on to is 2201?

The single biggest problem with communications is the illusion that it has taken place.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top