For one of our BB device (8700) the info "Configuration state" is failing in the BES-Manager.
"Configuration Status: Device state invalid".

Also I see this messages in our Policy-Log (BES f. Domino Server 4.1) for this device:

[20000] (11/14 00:40:02):{0x6D00} The current state for PIN xxxxxxxx is not available.
[20000] (11/14 00:40:02):{0x6D00} {myemail@mydomain.com, PIN=xxxxxxxx, UserId=1}RequestHandler::PollForMissingApps: GetHHCodePackages failed with the error: HHCM_NO_STATE_INFO_FOR_PIN.

I guess the application config should be ok.

Whats happen with this BB device ? Whats going wrong ?

-Dominik

I am having a similar issue and am finding the same error in the POLC log... Did you ever get a fix for this? Thanks -- Don

Just received the error today after patching an 8703 with the new DST 2007 patches. I pushed the program to the handheld and the next day it says "Device state invalid".

Did you all receive this error after pushing an app or program or really anything to the device?

What release of the handheld software are you guys running. The version you have may not need the DST patch.

The 8703 should not need DST patch. Our next test is see what happens when we push it to a device that doesn't need it.

the 8703e has 4.1.0.344 which according to RIM does require the DST patch and according to other people is the only version that anyone can get to successfully show up under the DSTquery2007 tool as being applied

Fixed the error by removing some duplicate SQL entries. Awesome.

So what entries were causing the issue?

Doing an Enterprise Activation will clear this error.

The Device State Invalid refers to the information on the BlackBerry handheld being out of sync with the information on the BlackBerry Enterprise Server. To force this information to be updated, please perform the following steps:

Procedure #1:

1. Delete the Desktop[SYNC] service book on the handheld.
2. Un-delete the service book by once again clicking the track wheel and choosing Undelete.
3. Hard reset the handheld by removing and replacing the battery.
4. Once the handheld has completed its reboot.
5. The handheld will need a few minutes to resynchronize.
6. Open the BlackBerry Manager refresh screen and verify if the status has changed.

If the issue still occurs we can force the information to synchronize by using the following procedure:

Procedure #2:

1. Set the user's activation password in BlackBerry Manager.
2. Have the user run Enterprise Activation on the handheld - no security wipe necessary.
3. Verify functionality.

Jekter's solution fixes most problems, but we did see a situation which required the handheld to be wiped before the state would get updated properly.

The SQL entries that were causing my issue had todo with Berry411 being installed on the BB more than once. Even though the BB only shows 1 install of berry411 the files were still in the users State DB causing SQL errors. You have to find duplicate entries in the SQL database and delete all of them or just leave the most recent one.