09-29-2005 05:59 AM - edited 03-13-2019 10:41 AM
When trying to associate or disassociate a device, I receive the following error:
The following error occurred while trying to load the requested page.
Could not update user. 1
Error No: -1009
Error Description
Any ideas?
Brandon
Solved! Go to Solution.
09-29-2005 08:28 AM
Are you using AD2000 or AD2003?
There were a couple of bugs, like CSCeg34036, that would cause this error during device association. But these should be fixed in 4.1(3). Please capture a sniffer trace to see what is happening. You will probably see something like this in the trace:
Lightweight Directory Access Protocol, Modify Result
Message Id: 16
Message Type: Modify Result (0x07)
Message Length: 153
Response To: 2983
Time: 0.000000000 seconds
Result Code: Constraint violation (0x13)
Matched DN: (null)
Error Message: 000020B5: AtrErr: DSID-03152286, #1:\n\t0: 000020B5:
DSID-03152286, problem 1005 (CONSTRAINT_ATT_TYPE), data 0, Att 7cb40001
(ciscoatAppProfile)\n
We will need to look at the Modify Request before this to determine what is happening.
You can forward it to me if you would like (will look when I have a chance) or open a TAC case (better option) to have it looked at.
Kevin
09-29-2005 08:28 AM
Are you using AD2000 or AD2003?
There were a couple of bugs, like CSCeg34036, that would cause this error during device association. But these should be fixed in 4.1(3). Please capture a sniffer trace to see what is happening. You will probably see something like this in the trace:
Lightweight Directory Access Protocol, Modify Result
Message Id: 16
Message Type: Modify Result (0x07)
Message Length: 153
Response To: 2983
Time: 0.000000000 seconds
Result Code: Constraint violation (0x13)
Matched DN: (null)
Error Message: 000020B5: AtrErr: DSID-03152286, #1:\n\t0: 000020B5:
DSID-03152286, problem 1005 (CONSTRAINT_ATT_TYPE), data 0, Att 7cb40001
(ciscoatAppProfile)\n
We will need to look at the Modify Request before this to determine what is happening.
You can forward it to me if you would like (will look when I have a chance) or open a TAC case (better option) to have it looked at.
Kevin
09-29-2005 11:12 AM
I had a TAC case open and this bug did turn out to be the issue. I'm not sure how it is showing up in 4.1(3).
Thanks,
Brandon
09-29-2005 12:55 PM
Please email me the case number so I can follow up with TAC and development regarding finding this in 4.1(3).
Kevin
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: