Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML CM: Upgrade to 14.3.1 - Pulse no longer starts up correctly - org.springframework.beans.factory.BeanCreationException
Application is org.springframework.beans.factory.BeanCreationException: Error creating bean with name ' databaseSchemaUpgrade ' defined in URL [jar:file:/C:/Program%20Files/Serena/common/tomcat/8.0/webapps/pulse/WEB-INF/lib/platform-dbschema-14.3.1-SNAPSHOT.jar!/META-INF/starlight/app-components.xml]:
CMS-XML DimCM: Pulse: Database upgrade fails 'Missing IN or OUT parameter at index:: 2' if any product has a default review check list
Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name ' databaseSchemaUpgrade ' defined in URL [jar:file:/C:/Program%20Files/Micro%20Focus/common/tomcat/8.5/webapps/pulse/WEB-INF/lib/platform-dbschema-14.5.0-SNAPSHOT.jar!/META-INF/starlight/app-components.xml]:
CMS-XML Logging in gives error "The proxy server isn’t responding" and server.log gives "Error creating bean with name 'liquibase' defined in class path resource"
Logging in gives error "The proxy server isn’t responding" and server.log gives "Error creating bean with name 'liquibase' defined in class path resource"
CMS-XML ERROR 12-02-2016 09:56:58 [localhost-startStop-5] [LocalizationBean:132] - Can't initialize localization bean and No Catalog Found error logging into Request Center
com.serena.solfwk.srp.service.LocalizationServiceImpl.localizationBean; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'localizationBean' defined in class path resource [srp-context.xml]: Invocation of init method failed; nested exception is java.lang.NullPointerException
CMS-XML Build Job Timeouts with Error when SSO is Enabled
When enabling the SSO (supplied with SBM) for Dimensions CM 12.1, there may be issues with the Build completing if “localhost” is used to define the default Dimensions CM URLs when the SSO URL is set the machine name .
CMS-XML RLC.log gives error: liquibase.exception.LockException: Could not acquire change log lock. (Liquibase FAQ)
nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'configuration' defined in class path resource
CMS-XML External mashup events give error in alfeventmanager.log.
The problem is if you use the Mashup Event tab on a Nofication Definition. You can create a Notification definition for things like Item Add, Item Update etc and when you fill in the Mashup Event tab you can tell it the endpoint url and event name .
CMS-XML 404 error when trying to load SSO login page - server.log has error regarding "sbmSAML2SPConfigFilter"
Cannot find class [com.microfocus.sbm.sso.idp.saml2sp.SBMSAML2SPConfigFilter] for bean with name 'sbmSAML2SPConfigFilter' defined in ServletContext resource [/WEB-INF/conf/saml2sp/securityContext.xml]; nested exception is java.lang.ClassNotFoundException: com.microfocus.sbm.sso.idp.saml2sp. SBMSAML2SPConfigFilter
CMS-XML Getting random Invalid User ID or Password errors in rlm.log or alm.log
If you edit any of the url's make sure to deploy all the applications that use that endpoint. If any of the RLM endpoints are pointing to the wrong server ( Most commonly a problem after promoting all your applications ) then you could run into a problem where the SSO token used in the various orchestrations is not valid if the endpoint is pointing to the wrong server. This seems like a random problem when this situation occurs because sometimes their are two endpoints defined with slightly different names but two different url's are used in the environment.
CMS-XML MCLG: How to setup dynamic preview for JSP pages.
... the site contains Java Beans , then copy the Java Bean files to the ... ... It must be defined for each project ... ... and click its name to display the "Edit Metadata Definitions " dialog box ... ... add a metadata definition . ... from the Metadata name ... add another metadata definition . ... Choose "Preview URL " from the Metadata name ... , enter the URL for the ROOT ... ... part of the URL (such as ... Long Path Names ... (404) error may result when ... ... limit, the error will occur. ... , a "Directory browsing not allowed" error will occur ...
Pages [Next]

Welcome kb sso

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs