Posts tagged "quick start"

Error while starting AEM Quickstart after installing AEM Forms

If you happen to see the following error while starting AEM 6.0 quickstart after installing AEM Forms add-on package (adobe-aemfd–pkg-1.0.78.zip)

 

*ERROR* [FelixDispatchQueue] adobe-aemfd-signatures FrameworkEvent ERROR (org.osgi.framework.BundleException: Activator start error in bundle adobe-aemfd-signatures [402].)
org.osgi.framework.BundleException: Activator start error in bundle adobe-aemfd-signatures [402].
at org.apache.felix.framework.Felix.activateBundle(Felix.java:2202)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2070)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1297)
at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NoClassDefFoundError: com/rsa/asn1/ASN_Exception
at com.adobe.fd.signatures.activator.Activator.start(Activator.java:36)
at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:645)
at org.apache.felix.framework.Felix.activateBundle(Felix.java:2152)
… 4 common frames omitted
Caused by: java.lang.ClassNotFoundException: com.rsa.asn1.ASN_Exception not found by adobe-aemfd-signatures [402]
at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1550)
at org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:77)
at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1973)
at java.lang.ClassLoader.loadClass(Unknown Source)
… 7 common frames omitted

 

It is because couple of boot delegation properties not being included in sling.properties file.

 

To resolve these errors , follow the steps mentioned :

  1. Stop AEM server
  2. Add these two properties in sling.properties file under /conf folder

sling.bootdelegation.class.com.rsa.jsafe.provider.JsafeJCE=com.rsa.*
sling.bootdelegation.class.org.bouncycastle.jce.provider.BouncyCastleProvider= org.bouncycastle.*

After restart ensure that there are no errors in error.log file and also status of  AEMFD Signatures Bundle (adobe-aemfd-signatures ) bundle should be in Active state.

 

For more information visit online help docs

 

–Santosh

http://about.me/nskumar

 

If double-click doesn’t work

 

With ADEP release running an Experience Server is as simple as double-clicking Solutions Quickstart

One needs to obtain a license file, copy license file and Solutions Quickstart to some folder and double-click Solutions Quickstart to get everything up and running *but* at times you may notice that Experience Server does not start [though it's not a problem with Solutions Quickstart] on double-click.

Solutions Quickstart is a jar file and it doesn’t start on double-click if some other program has hijacked the jar file extension i.e when we install JRE on Windows system the file “jar” is correctly associated with javaw.exe and if any other program like a zip utility is installed that utility modifies the association of jar file and when you double click Solution Quickstart instead of starting Experience Server it just opens up the file or does nothing.

In order to fix this problem, I suggest four ways :

  1. Right click on Solutions Quickstart jar file , In context sensitive menu Go to open with , Select Java(TM) Platform SE binary. If this option is not visible in context sensitive menu click Choose Program and Browse to <Java_Home>\jre\bin\javaw.exe , Select Java(TM) Platform SE binary in Open with dialog , Check “Always use selected program to open this kind of file”, Click OK
  2. Tweak the registry key “HKEY_CLASSES_ROOT\jarfile\shell\open\command” to “<prefix_correct_path_till_Java_Folder>\\jre6\bin\javaw.exe” -jar “%1″ %*
  3. There are scores of jarfix utilities that are available on internet , You can use any such utility , One such utility is available here [Read terms & conditions , license agreement before using this utility or any such utility]
  4. Re-install JRE
Any of the ways suggested above should fix the problem and you should be able to start Experience Server with just a click of a button.
Alternatively Solutions Quickstart can also be started from command prompt for more information on this refer to my earlier post [Installation section] on my blog