Syncing mobile devices with Exchange errors with: The certificate chain did not end in a trusted root
When trying to sync a mobile device or testing your Exchange configuration using testexchangeconnectivity.com you receive the following error:
“The certificate chain did not end in a trusted root. Root = OU=VeriSign Trust Network, OU=”(c) 1998 VeriSign, Inc. – For authorized use only”, OU=Class 3 Public Primary Certification Authority – G2, O=”VeriSign, Inc.”, C=US”
The problem is that a certificate in your certificate chain is untrusted. If you look at the OU it tells you what certificate is untrusted. Go to the certificate authority’s website to download and install the appropriate certificate.
NOTE: for the issue that I had with my Verisign certificate, I ran around in circles looking for the right cert to download. It is quite apparent that Verisign’s knowledge base search sucks. Only after calling their support department was I able to get the right information. That said article SO13347 in Verisign’s knowledgebase had the correct certificate to resolve this problem.
I’ve seen this all over the web and I’m a victim of it as well. What happened was I rooted my new LG Optimus S that I got when I switched over to MetroPCS. While uninstalling some of the bloatware that came with it, I removed the MetroWeb browser. I figured that since I installed Opera Mobile I didn’t need it. BIG mistake! Apparently the MetroWeb browser is so tied to the system that I couldn’t get the Android Market to install anything. Any attempt at downloading and installing an app would cause the dreaded andriod.process.media error.
Anyway, this is how I finally got around it. NOTE: this fix requires that you have root explorer 2.16 installed on your phone. If you don’t have it installed, you can download it from here.
First thing to do is you need a copy of the Browser.apk and Browser.odex from a working phone or download them from my box.net widget on this blog.
Next, hook up your android to your computer via a USB cable so you can access your sdcard and copy the two files to your sdcard.
Next, open root explorer and copy the Browser.apk and Browser.odex files from your sdcard to your /system/app directory on your phone. (be sure to toggle the Mount R/W button so your can copy the files).
NOW THE IMPORTANT PART! What you will need to do is to change the permissions and the owner for these two files.
Long hold on the Browser.apk file and select Permissions. Give Read, Write and Execute permissions to Owner, Group and Others. Basically you’re checking all 9 boxes. You don’t need to check any of the Special Permissions. Click “OK” when done.
Long hold again on the Browser.apk file and select “Change Owner”. Change the owner to “0 – root” for both Owner and Group. Click “OK” when done.
Toggle the “Mount R/O” button.
Power down your phone and then power it back up. If all goes well, you should see the MetroWeb app in your app listing.
most likely this is and issue with the look up for your alias. a quick workaround for is to set the Data Source and Provider Strings to the following:
<FQ hosting name>:<port>/<alias>
thanks to bkgroups<AT>yahoo<DOT>com for the post all the way back in 2007 on sqlmonster.com for the answer.
Steps to update the firmware for a Toshiba 40G300U1 since the instructions that Toshiba supplies in their manual are wrong.
1) Format the USB stick as FAT32. Make sure that you DO NOT perform a quick format.
2) copy the firmware update to the USB drive. NOTE that it must be the only file on the drive.
3) Turn the TV OFF (Toshiba saids you can let it on)
4) Insert the USB stick into the USB slot.
5) Turn the TV ON.
At this point the TV will detect the firmware update and start going. DO NOT power off the TV unless you want a really expensive and crappy mirror hanging on your wall.
After the update is complete (it will say so). Turn the TV OFF and THEN remove the USB drive.
Congrats you’re at the least version.