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 MCLG: Error ''Storage: MetaData.setValue - Failed. metaName= userMetaData=true value='' in deploy log
MCLG: Error ''Storage: MetaData.setValue - Failed. metaName= userMetaData=true value='' in deploy log
CMS-XML MCLG: When creating a new project, the screen is blank, and error "Unable to read project options from server" is in the Tomcat log
When you click the New Project button to create a new project, you can enter the name of the new project, but the next screen is blank. Also, the following error is in the Tomcat log.
CMS-XML MCLG: Error ''*** IncludeAsset Error locating asset ***'' using the IncludeAsset component.
The IncludeAsset component can use a property called FindFile which will search for files with the name specified in the current folder and folders above the file where the code is currently being called from.
CMS-XML MCLG: Project rebuild gives error "***** SQL error: Specified database is invalid"
If the Sybase project you are rebuilding contains an ampersand (&), you get an error when running a rebuild on this project. As an example, if the project is named "this_&_that.db", the complete Sybase error will be:
CMS-XML Getting "Storage.GetFileAssetData: Invalid asset XXX" error when opening a project.
SET Value = 'xxx' WHERE ( Name = 'DefaultFilterHtmlSettingsAssetId') After this query is run try to open the project again.
CMS-XML MCLG: Deploy gives error "error: The file My Bookmarks.properties was already added by asset My Bookmarks"
When all the conditions above are true, Collage incorrectly flags "Work Cabinet" assets for generation. When this happens, if there are multiple assets with the same name , such as "My Bookmarks", errors will be produced and the deploy will fail. Workaround : If all three criteria are required (not common), then the Deploy will complete if it is submitted with "Only Fatal Errors" set for the failure criteria.
CMS-XML MCLG 4.0: ''System username is not allowed to log on to the database server'' error when setting up MSSQL server to connect with Collage.
If the MSSQL server name is something like computername\serverinstancename. In this case serverinstancename is the second instance of SQL installed on this box. (Note the slash in the name)
CMS-XML MCLG: Content Upload fails with javascript error when using French language interface
Workaround: Change the two named strings to not contain apostrophes. Restart Collage.
CMS-XML MCLG: Backup of an Oracle project gives error "can't exec: exp doesn't exist"
The project being backed up has a space in the name . In this case, the backup scripts in Collage will not run correctly. Either copy the project to a new name that does not have spaces, or run the backup directly from Oracle instead of using the Collage driven backup.
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".
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs