2x 1252s unable to fully join 2504

Question

Hi everyone :)
And thank you for an awesome resource!
I was lucky enough to get my hands on this 2504 at work for labbing and had set the goal for last night to convert the two 1252s to lwap and join them with the controller. Just a simple ssid and thats it.
However imagin my frustration when i saw the access points register however with their radios turned off and no way of turning them back on. These are APs i've had running in autonomous mode for some time now so they work just fine.
Fortunately, and since the setup is just a lab for now, i had my console cable hooked to one of the aps so i could see the boot process running. What i have snipped in here below is a part of the console log from after AP01 booted. I googled for some time to figure this out and during my trouble shooting i toggled the dhcp client to reproduce the error message. Same thing, highlightet below, on both aps!
Just a note, during initial setup on the controller i checked both the US and DK for language / region selection. I found a case with the wrong regulartory domain between controller and ap with similar symptoms as highlightet below. I changed the setting to just DK and kept working, since the APs are ETSI regulatory. 
What is the problem? And what can i do about it :)
Thanks in advance!
/Kim
<snip>
AP01#release dhcp bvi 1
AP01#renew dhcp bvi 1
Not in Bound state.
AP01#renew dhcp bvi 1
Not in Bound state.
AP01#
*Jan 13 23:43:41.451: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.30.18:5246
*Jan 13 23:43:41.555: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 192.168.30.119, mask 255.255.255.0, hostname AP01
renew dhcp bvi 1
AP01#
*Jan 13 23:43:44.295: %WIDS-6-DISABLED: IDS Signature is removed and disabled.
*Jan 13 23:43:44.295: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Jan 13 23:43:44.295: bsnInitRcbSlot: slot 0 has NO radio
*Jan 13 23:43:44.307: %CAPWAP-3-ERRORLOG: Binding Config Initialization failed for binding 1
*Jan 13 23:43:44.331: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Jan 13 23:43:45.339: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down
*Jan 13 23:43:45.347: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Jan 13 23:43:46.367: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Jan 13 23:43:47.367: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
Translating "CISCO-LWAPP-CONTROLLER.mgmt.dk"...domain server (192.168.10.10)
*Jan 13 23:43:54.331: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
*Jan 13 23:43:54.331: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-LWAPP-CONTROLLER.mgmt.dk
*Jan 13 23:44:04.335: %CAPWAP-3-ERRORLOG: Go join a capwap controller 
*Jan 13 23:43:54.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.30.18 peer_port: 5246
*Jan 13 23:43:54.423: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.30.18 peer_port: 5246
*Jan 13 23:43:54.423: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.30.18
*Jan 13 23:43:54.427: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.
*Jan 13 23:43:54.427: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.
*Jan 13 23:43:54.427: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
*Jan 13 23:43:54.427: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 192.168.30.18
*Jan 13 23:43:54.739: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
*Jan 13 23:43:55.015: %WIDS-6-ENABLED: IDS Signature is loaded and enabled
*Jan 13 23:43:55.739: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
AP01#
<snip>

Answer 1

Hi again :)
Thanks for your reply Leo, I was about to 'sh' everything to you guys when the radio led on one of the APs suddently turned on! ;)
Actually, I upgraded the controller to v7.6.130.0. And then, reset the controller to factory defaults... Without checking if the upgrade had worked. After that woila.
So since this is a lab I will downgrade tonight to v7.6.120.0 to try and reproduce the error.
However there was one small detail that baffled me, when i set up the lab I added both US and DK to the language list. I unchecked US when troubleshooting the problem. Then before the upgrade I noticed a log message mentioning a problem with the regulatory domain on the joining AP. The message said something about changing the domain from () to (DK). From nothing to DK. Every time it rebooted...
Anyway, now it works. Thanks Scott and everyone else.
/Kim