Created by: Karthik Bahiradhan on 21-05-2013 10:18:16 AM I am testing Agent attribute value update using UCCE Web API, I am sending this input https://192.168.10.71/unifiedconfig/config/agent/5015 with put method, data is
and it is throwing response as "500 internal server error"
Response:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <apiErrors> <apiError> <errorMessage>No row with the given identifier exists: [com.cisco.ccbu.cce.unifiedconfig.api.ref.DialedNumberRef#5002]</errorMessage> <errorType>internalServerError</errorType> </apiError> </apiErrors>
could you please guide me what would be error?
Subject: RE: Agent Attribute Value Update using UCCE Developer API Replied by: Thomas Weissinger on 21-05-2013 07:28:37 PM Can you post the results of a GET request on the same agent? https://192.168.10.71/unifiedconfig/config/agent/5015 Also can you provide the result of a GET request on https://192.168.10.71/unifiedconfig/config/dialednumber/5002 (It may return a 404 not fond) Also can you send what gets output from the Error<date>.startup.log in the c:\icm\tomcat\logs directory when the error occurs? There may be multiple errors in that log, but I'd like to see only the error stack trace when that request fails. Thanks, Tom
Subject: RE: Agent Attribute Value Update using UCCE Developer API Replied by: Matthew Reiter on 22-05-2013 02:23:55 PM Given the limited number of object types that reference dialed numbers, my guess is that the agent being updated belongs to a team with a supervisor script dialed number that no longer exists. If so, clearing the supervisor script dialed number should fix the problem.
Subject: RE: Agent Attribute Value Update using UCCE Developer API Replied by: Karthik Bahiradhan on 22-05-2013 11:06:46 PM
Matthew Reiter:
Given the limited number of object types that reference dialed numbers, my guess is that the agent being updated belongs to a team with a supervisor script dialed number that no longer exists. If so, clearing the supervisor script dialed number should fix the problem.
Thanks Matthew Reiter & Thomas Weissinger. This issue is solved. I gave wrong datatype value to this agent attribute value. I have to pass true / false instead of number. After i did the changes, it is working.
Subject: RE: Agent Attribute Value Update using UCCE Developer API Replied by: Thomas Weissinger on 23-05-2013 09:45:40 AM That's good news. Let us know if you encounter the issue again as we have some other ideas, too.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: