Lync Server 2010 - Device Update error codes

After each reboot and occasionally afterward, a UC phone will attempt to contact the Device Update website to download any available firmware updates which may be available. 

• Phone POSTS manufacturer, model, current firmware version.
• Server checks set of Device Update Rules for two things:

a) That a rule exists for the specific manufacturer, model, and revision of phone

b) Whether a more recent update file has been approved for the given device

• Server will respond as appropriate:

a) (0x0 / 200) - No update exists

b) Internal / External URL for the firmware update (http for internal, https for external -- hardcoded!)

c) (0x# / 0x#####) - Error

• Device will stop any existing download of the Address Book and delete all of the ABS files (to clear disk space)
• Device will GET firmware using either the internal or external URL provided by Device Update server
• Device will apply the image, then reboot after 5 minutes of inactivity (idle)

Check the System Information screen for key pieces of troubleshooting information:

Version - Current firmware version (e.g. 4.0.7576.0 = Lync RTM) and Bootloader version (1.23 or later required)

Last Update - Last time a firmware was downloaded/installed successfully

Last Update Request - Should be today, or moments ago if phone was rebooted

Last Update Status - Status code indicating success/failure (details below)

Format:  (0x#/0x#####)

Possible error codes highlighted in red are as follows:

0x0 = Ok eg, 0x0/200 means update request was sent successfully

 

0x2 = certificate validation failed (e.g. on a SHIP device when we download a test signed or unsigned image or an image signed with the wrong certificate, image update fails because the image is not signed with correct cert.  Images prior to RTM were signed with a MD5 certificate.  RTM images and post-RTM images are signed with SHA1 certificate.)

 

0xd = Failure to write the image in Nand flash after download. This happens due to multibit error in Nand flash. – RTM software will not be able to update if this error occurs. However, this will be fixed in CU1 i.e. if a multi-bit error is found in the OS region during the image update, the image update software will properly deal with this error and will complete the update process successfully

 

0x7 = Failure to download image update files because FileSystem is corrupted(eg multibit error in FS) or the filesystem is Full. – In this case, the user should perform a hard reset which reformats the file system and fixes this problem. After the hard reset, image update will succeed

 

0x5/401 - this is auth failure during image update request

Error codes highlighted in yellow are HTTP related and can be found here:

http://msdn.microsoft.com/en-us/library/ms681382(VS.85).aspx