While starting AEM 6.3 upgrade insance we are getting following
error:Exception in thread "SpringOsgiExtenderThread-12"
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'facilitatedExternalService' defined in URL
resolve reference to bean 'userProfileService' while setting bean
property 'userProfileService'; nested exception is
org.springframework.beans.factory.BeanCreationException: Error cr --> -->...
Thanks For the update.please find the attached logs for the
same.28.08.2017 16:43:57.302 *INFO* [10.150.184.95  GET
12557739398483571255773939850169 XssFilter, Filter Path:
/bin/lordabbett/, /content/lordabbett/28.08.2017 16:43:57.311 *WARN*
Hi All,we tried to migrate from AEM 6.0 to AEM 6,3. Successfully in
place upgrade done. But After upgrade, we are having issue like, not
able to import class from one module to another module class. That
imported class is bean class. The class is that we are importing is
service class. Build is successfully and corresponding bundles are in
active mode. Please let me know, if you need any other
details.Thanks,Lakshmi Raghava Reddy M,
No Opkar ,we followed above steps,it's not working,. We are not able to
delete /var/discovery folder. we performed other steps, but it is not
working. One more thing is, we are using stand alone instance, it's not
clustered instance.If you have the steps to restore for stand alone
instance, please provide the steps ASAP.
Yes Opkar, we recently copied the instance. I opened the topology. I am
not able under stand anything. No it's not a production environment, it
is our lower environments.I attaching the those text file and please go
through those and please let me know, if you know any solution.
If those instances are not unique, is there any way to make those those
unique, suppose if I am copying the work flows from stand alone to Mongo
cluster vice versa, how to resolve the issue. Same case from stand alone
to stand alone, how to resolve the issue.
Hi Opkar,yes, DAM update asset workflow is failing, we didn't modify
that. we have taken the package from other environment, where workflow
is working fine. I guess there is no difference of the environment. if
you know the steps to get it back the default out of box work flow,
please give else if you have clean package, Please send it as a