*apfMsConnTask_0: Apr 21 11:12:12.918: 40:fc:89:30:3a:dd Sending Assoc Response to station on BSSID c0:62:6b:29:9d:40 (status 17)
Status Code 17 is usually used for Load Balancing... If you run your debug longer, is your client ALWAYS associating to that same AP and ALWAYS getting rejected with Status 17?
Does it work or fail if you move to another area with another AP?
Load-balancing should only reject a client X number of times and then let it on.... Your client clearly isn going somewhere else, so it should be allowed on.
Other than that, 17 is used for saying we can support another association.... I guess it could be possible the AP just won take new associations.... Can you get some other new device associated to the same AP?
Everytime Ive seen Status 17, it was load-balancing rejecting it... but this could be something new, and should impact all client on this AP (maybe other clients are properly going to another AP)
What is your load-balancing paramters?
what about the statistics (number of rejections)?