This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

C2DM configuration incomplete, accountName is not set

Hello everyone:

Every time I send any command to Android devices from SMC console -install/unistall apps for instance-, I fails and I recieve an error like this:

Error report created at: Wed May 07 15:01:14 CEST 2014

Sync URL:                smc.iss.es:80/servlets/OmaDsServlet

Sync URL SSL:            smc.iss.es:443/servlets/OmaDsServlet

Message:

C2DM configuration incomplete, accountName is not set

 I have searched in the forum and documentation without success. I have realized that some users had the same problem, but thed had no answer or it was fixed without any action.

The firewall rules are properly configured and I don't know where is the problem. Any idea?

Thanks in advance!

:49668


This thread was automatically locked due to age.
Parents
  • Hi Carlos,

    that is strange. Normally Google Cloud Messaging (GCM) is used to send out messages / tasks to Android devices.

    Can you please make sure, that your SMC server and the Android devices can reach the Google Servers as described in our KBA 113217.

    Maybe this solves the problem? Otherwise, try these steps:

    • Create a new Android command bundle with the following settings:   
    1. SetConfiguration (as name use c2dmAccountName and as value 510474213058. Do not change anything on these values).
    2.     gcmUnregister
    • Deploy this command to the Android devices of the customer. This will fail in a first step, as the devices cannot be contacted via C2DM anymore.
    • On each device the command has been applied to open the SMC client and press the "synchronize" button. This way the task bundle will be transferred to the device.
    • Now, the devices should communicate via GCM.

    Note: If the devices are within a wireless network, make sure that the ports used by the devices for GCM (5228, 5229 and 5230) are opened.

    Using the above procedure the devices will be forced to use GCM again. Using the manual synchronization on the device, the device will contact the server and get all currently waiting tasks.
    Normally, all devices should use GCM, therefore this error is a bit strange and could only occur if there is something wrong with the communication to the servers required.

    Best regards

    Stefan

    :49818
Reply
  • Hi Carlos,

    that is strange. Normally Google Cloud Messaging (GCM) is used to send out messages / tasks to Android devices.

    Can you please make sure, that your SMC server and the Android devices can reach the Google Servers as described in our KBA 113217.

    Maybe this solves the problem? Otherwise, try these steps:

    • Create a new Android command bundle with the following settings:   
    1. SetConfiguration (as name use c2dmAccountName and as value 510474213058. Do not change anything on these values).
    2.     gcmUnregister
    • Deploy this command to the Android devices of the customer. This will fail in a first step, as the devices cannot be contacted via C2DM anymore.
    • On each device the command has been applied to open the SMC client and press the "synchronize" button. This way the task bundle will be transferred to the device.
    • Now, the devices should communicate via GCM.

    Note: If the devices are within a wireless network, make sure that the ports used by the devices for GCM (5228, 5229 and 5230) are opened.

    Using the above procedure the devices will be forced to use GCM again. Using the manual synchronization on the device, the device will contact the server and get all currently waiting tasks.
    Normally, all devices should use GCM, therefore this error is a bit strange and could only occur if there is something wrong with the communication to the servers required.

    Best regards

    Stefan

    :49818
Children
No Data