> I can't imagine what could cause that error All I can think of is : check Java's classpath. But that seems unlikely for a single profile, and would indicate something unusual in the deployment. HTH Tom