I am starting to see this error pop up. I have followed several posts and they fixe the issue for the phone. The config is good and the actual fix is to either unsubscribe and resubscribe to the service or reset device firmware.
DNS is good and phones were working for 18 months. This seems to have started in last 60 days.
I am trying to fix the problem that causes this. It seems to work fine until the user changes their greeting and then next time it errors out. I have never seen this problem on my phone but I changed my greeting to test the hypothesis. My phone started doing same error.
It's doubtful that the greeting has anything to do with it. This issue could be complex (especially if it's a Connection cluster and/or there are firewalls between the phone and Connection) so you might be better off getting TAC to help troubleshoot.
But to narrow down the issue, you should try to figure out if it's the phone midlet/firmware or something on Connection (or possibly something in the middle). To do that, you need to take a look at the phone logs (see
Basically, when you press a button on the phone, the midlet acts like a web browser and should contact Connection to perform the login. There are obviously a lot of different things that can happen due to caching and whether or not there was response received (especially if there is failover involved), but essentially it's important to make sure this phone->Connection communication is still happening. Of course, the Midlet is at the mercy of the phone firmware for accomplishing this, so the firmware version (and phone type) is very important and can impact things.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.