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 Release Automation: Startup Fails with error: No version information in version file in nolio_dm_all.log file
org.springframework.beans.factory.BeanCreationException: Error creating bean with name << details snipped for size>> : No version information in version file [conf/version]
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 After Upgrade, user is unable to login because resource ... sp-metadata.xml does not exist.
'org.opensaml.saml2.metadata.provider.ResourceBackedMetadataProvider#33ab6c41' of type [org.opensaml.saml2.metadata.provider.ResourceBackedMetadataProvider] while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.opensaml.saml2.metadata.provider.ResourceBackedMetadataProvider#33ab6c41' defined in ServletContext resource [/WEB-INF/conf/saml2sp/securityContext.xml]:
CMS-XML MCLG: 5.1.0.6 Hot fix: Several LDAP and deploy bugs have been addressed
LDAP: Depending on the configuraiton on the LDAP server, users may have been forced to log into Collage twice every time. When this happens, the Tomcat log would show error " Bean : OpenProject: <project name > com.merant.ldap.LdapException".
CMS-XML MCLG: How to setup dynamic preview for JSP pages.
... the site contains Java Beans , then copy the Java Bean files to the ... ... and click its name to display the ... ... from the Metadata name ... from the Metadata name Long Path Names ... (404) error may result when ... If the total length of the path to the temporary files exceeds the 255 Windows character limit, the error will occur. ... If the site has never been deployed, a "Directory browsing not allowed" error will occur because the included file cannot be found on the web server.
CMS-XML SDA: silent SDA Agent install on AIX leaves the "/opt/serena/DeployAutomationAgent/core" folder empty
... installing Files ( bean 7) ... /agent. name =f20 ... ... .service. name =SDA- ... locked/agent. name =f20c ... locked/agent.service. name =SDA-Agent ... (Mar 12, 2015 2:36:00 AM), Install, com.ibm.wizard.platform.aix.AixProductServiceImpl, msg1, installing Ascii File Update Product Action ( bean 2) ... Error : Port Library failed to initialize: -125 Error : Could not create the Java Virtual Machine. ... Error : A fatal exception has occurred.
CMS-XML Special characters are not allowed in Project Names error
Special characters are not allowed in Project Names error
CMS-XML FDM: VERIFY gives non-standard member name error
FDM: VERIFY gives non-standard member name error
CMS-XML KM-Dim9: Error: Baseline is not a Release Baseline
KM-Dim9: Error : Baseline is not a Release Baseline
CMS-XML KM-Dim9: Replicator: Error: The path name is too long.
KM-Dim9: Replicator: Error : The path name is too long.
Pages [Next]

Welcome kb sso

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs