Wednesday, December 30, 2009

javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed

javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

I had upgraded Xythos software for content management and their wiki feature failed to launch everytime because of the error above. The cert was from godaddy and the web server was jakarta tomcat. The cert worked fine for everything except the wiki feature. Took me sometime before figuring out what the issue was.
My version of jdk was 1.5.0_06 then. Upon installing JDK1.6.0_17 it worked like a charm. So whenever you get a ssl handshake exception, try upgrading your JDK to latest version from http://java.sun.com/javase/downloads/index.jsp before venturing out other options.

In cases where your system talks with a different system using ssl then you will need to import the ssl cert of the other system to your keystore. Sometimes, that might not work because the cert from the other system might not be from a notable CA. Java hiccups when using free certs from providers like IPSca. In such cases you will need to import the cert from the other system to the "cacerts" keystore located in C:\Program Files\Java\jdk1.6.0_17\jre\lib\security\.

Friday, December 18, 2009

Robocopy Error 123 Scanning Destination Directory The filename, directory name, or volume label syntax is incorrect.

Ok. Everytime my script ran fine. One time I opened it and thought of adding some parameters and closed the script. I got an error 123 saying the destination G:\BackupFolder\ could not be found.

This was what I was using to copy some of the backup data over to a different location from a share in NAS.

robocopy \\naslocation\SharedFolder G:\BackupFolder /E /Z /COPYALL /R:3 /W:10 LOG+:G:\LogNASbkprbcpy.txt /NP

Looking at the script above can you figure out the flaw? Its darn simple actually though I had to rewrite it again because I overlooked something. Here's a correct script:

robocopy \\naslocation\SharedFolder G:\BackupFolder /E /Z /COPYALL /R:3 /W:10 /LOG+:G:\LogNASbkprbcpy.txt /NP

Hope you can figure the difference now. Its the "/" before the LOG parameter. It was missing in the previous script which got robocopy to think it was a part of destination parameter as well.

Lessons learnt: Be humble enough to consult help "robocopy /?" and match the syntax. Get proper sleep.

Monday, December 14, 2009

Outloook Client - The name could not be resolved. The name could not be matched to a name in the address list.

A user account was disabled and moved to a different OU in active directory. The account was later enabled so that the mails could be archived. But trying to create an account in outlook failed. It said "the name could not be resolved. The name could not be matched to a name in the address list".

The account was good to log in to the domain and also to access exchange OWA. So I did a little research. These were the links that I got referenced to from "google".
http://technet.microsoft.com/en-us/library/dd439366(EXCHG.80).aspx
http://support.microsoft.com/?kbid=297801

The solution was a bit lengthy to read. So, I thought of exploring the user account properties in Active Directory Users and Computers. Presto! It was right there.

In user account properties (right click the user in context and then choose properties or double-click the user) I went to Exchange Advanced tab. There was a checkbox which read "Hide from Exchange address lists". That thing was checked. Unchecking that let me configure the mail account on outlook client.

So next time, check your mail settings for that user thoroughly before you google.