Re: "The agent id is invalid" - Page 2

mlarrimore · ‎08-05-2005

I'm have a problem logging agents into their desktop agents getting the error the agent id is invalid i'm not sure how to resolve this i tried deleting the profile and user configuraation sometimes this work but not all the time. Everything is done the profile is associated with the user and the RMuser and a skill is added to the agent but the error continues to come up. PLEASE HELP! Thanks inadvance for any assistance.

tnooning · ‎08-13-2005

Glad to hear it's working. And I'm not sure why it didn't work correctly in the first place, but I've found that when in doubt restarting the CTIManager on CallManager and/or the CRA engine usually clears up flaky issues like this.

mlarrimore · ‎08-15-2005

Hi, well "it's back", created a profile for a agent today and i'm getting the error again i think it's something more that is wrong because i really can't be restarting the cra engine every time i need to create a agent profile. Well looks like i will have to open a case with TAC.

tnooning · ‎08-15-2005

Please post the resolution, I'm curious to see what is going on.

mmach · ‎08-17-2005

I have recently run in to this same issue. Last Friday I had a use that could not login. I compared this user to other users and there was no difference. I deleted the user completely and entered user new, did all the associations and the user still could not login. I had stopped and started engine, and even re-booted all the call servers on Friday night. Finally on Monday I was able to get the user to work, how I have no clue.

Today I had another user just stop working. She was working on Friday when she left and today I could not get her to work. I went through the process of deleting, recreating, stopping and restarting etc.

If you come up with a solution, please let me know.

mmach · ‎08-17-2005

We just pushed WinXP service pak2 I was wondering if you recently did the same. I was trying to come up with something that was done recently to cause the issue.

ciscogini · ‎08-19-2005

Make sure to restart all of these,

Restart CRA Services ( All of them)

Restart CTI Manger on the Call manager.

mlarrimore · ‎08-19-2005

hi TAC said "I believe the issue may have been related to several configuration issues; specifically the CTI Manager Server from hostname to ip address through dsbrowser." and after this change the CRA server was restarted and the CTI manager on both Callmanagers.

george · ‎08-29-2005

Hi,

I have been working on the same issue for the past few days. I have tried all of the suggestions above without any success. The strange thing is that out of 8 agents (WinXP SP2) only 2 have problem login in. Do you have any more suggestions?

./G

mlarrimore · ‎08-29-2005

Well for me there was no more issues after the CRA server hostname was changed to the ip address in the dsbrowers. Now other changes were made that i think made no difference to how the agents logged in, the media channel and changing the line config for agent for "Maximum Number of Calls" and "Busy Trigger" from 4/2 to 2/1. It maybe another issue for you but if you tried every thing else i suggest you create a case with TAC.

george · ‎08-30-2005

The CRA server is already changed to IP in the dsbrowser. Below is the agent log

13:27:38 08/30/2005 INFO FChooker VERSION:[Release 4.5.6.2] [SMR(2)] PLATFORM:[XP Service Pack 2] DBGLEVEL:[1-204]

13:27:38 08/30/2005 INFO PhoneDev VERSION:[Release 4.5.6.2] [SMR(2)] PLATFORM:[XP Service Pack 2] DBGLEVEL:[1-204]

13:27:38 08/30/2005 INFO FastCall VERSION:[Release 4.5.6.2] [SMR(2)] PLATFORM:[XP Service Pack 2] DBGLEVEL:[1-204]

13:27:38 08/30/2005 INFO FastCall FC0181 FastCall Starting Up

13:27:47 08/30/2005 INFO DAClient Could not get value for app CTI Manager List key CTI Manager Host B

13:27:52 08/30/2005 INFO FastCall FC0365 License verified

13:27:53 08/30/2005 INFO FastCall EI0095 Enterprise connected

13:27:55 08/30/2005 INFO FCCTI_1000 CRS patch for 3.5.2.x JTAPI VERSION: Cisco JTAPI Cisco JTAPI version 2.0(1.12) Release

13:27:56 08/30/2005 INFO PhoneDev PD2528 CTI Server Login: Open new session to CTI server confirmed

13:27:56 08/30/2005 INFO PhoneDev PD1233540 CTIServerLogin: Requesting Device Monitor

13:27:59 08/30/2005 INFO PhoneDev PD2576 CTIServerLogin: Device monitor confirmed

13:27:59 08/30/2005 INFO PhoneDev PD2626 ICDServerLogin: Trying to Create Session for ICDServerA[x.x.x.x]ICDPortA[42027]: Number of Tries [1]

13:27:59 08/30/2005 INFO PhoneDev PD2716 ICDServerLogin: Open new session to ICD Server confirmed

13:27:59 08/30/2005 MAJOR PhoneDev PD2952 OnControlFailureConf: InvokeID is 1

13:27:59 08/30/2005 MAJOR PhoneDev PD2953 OnControlFailureConf: FailureCode = <256> CF_INVALID_AGENT_ID_SPECIFIED.

13:27:59 08/30/2005 MAJOR PhoneDev PD2956 OnControlFailureConf: PeripheralErrorCode = <0>.

13:27:59 08/30/2005 INFO ASL10013 Set agent state call failed (256).

13:27:59 08/30/2005 MAJOR PhoneDev PD2066 AgentLogin: Agent state login request failed: The agent ID is invalid.

13:27:59 08/30/2005 INFO FCCTI_1000 splkJtapiobj:StopProvider: Remove provider observer.

13:28:00 08/30/2005 INFO FCCTI_1000 splkJtapiobj:StopProvider: Provider Shutdown.

13:28:05 08/30/2005 INFO PhoneDev PD1907 PhoneDevShutDown: CTI Shutdown

13:28:09 08/30/2005 INFO PhoneDev PD1907 PhoneDevShutDown: CTI Shutdown

13:28:09 08/30/2005 INFO FastCall FC0393 Releasing license...

13:28:09 08/30/2005 INFO FastCall FC0422 FastCall Shutting Down

13:28:10 08/30/2005 INFO PhoneDev PD1907 PhoneDevShutDown: CTI Shutdown

Note that i have succesfully logged in using a different agent id from the same PC. Also login fails from IP phone itself. It seems that CRA keeps some old config cached and is not cleared even after a reboot.

./G

mmach · ‎08-30-2005

I had the same issue...what I did was deleted the user and totally re-created the user with a different login. Example Jane Smith was JSmith...now I use JS1 and it works. I used the same AD user names etc, the only change was the login ID.

george · ‎08-30-2005

Hehe, that's what I have also tryied today and worked! Strange, I wonder if deleting and re-creating the user in the AD (with old username) if it will fix the problem. Though it seems that CRA or CCM has something cached or again Microsoft is doing some weird tricks. Another thought was to restart the AD server but I haven't tried that. Changing the username is a workaround but not a solution.

I will try to re-create the users and reboot the AD. I have also read about general issues with WinXP SP2 and Active Directory.Anyways, it is a bug somewhere :).

mmach · ‎08-30-2005

Glad to hear your up and running again. I still think it has something to do with the MS patches that were pushed prior to the Service Pak2 upgrade. The reason being that it did not effect every user only a small percentage. (thank goodness) However it did make you want to do the Cisco Disco!! For those that do not know what the Cisco Disco is...it is jumping around and pulling your hair out!!!!

Rob Huffman · ‎09-02-2005

Hi Mike ... I like your sense of humour, and I never knew that when I was jumping around and pulling my hair out at 3:00AM over some bizarre trouble that I was in fact doing the "Cisco Disco". Its nice to now have a name for that crazy dance and will refer to it as this from now on.

Take care! RH

mmach · ‎08-29-2005

The samething happened to me. I up dated 10 PC with service pak 2 and had problems with only 2. I wonder if it has to do with what patches these PC received prior to the service pak 2 upgrade. Reason being the way the patches are rolled out in the up grade to service pak 2.

To get the user to work again I deleted the user, I had to recreate with a different user Login ID and password and associate with Rmjtap. After this the agent worked again.