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 KM-Dim7: ORA-00209: control file blocksize mismatch, check alert log for more info
ORA-00209: control file blocksize mismatch, check alert log for more info occurs usually when the db block size has been modified in the init<SID>.ora file.
CMS-XML MCLG: Netscape error ''Access to the port number given has been disabled for security reasons'' when logging into Collage
The Netscape browser, by default, disables several ports. The port where Collage was installed was one of these blocked ports and Netscape cannot access it.
CMS-XML SDA: How to configure tomcat to start a new logfile when the current log file becomes a certain size
It is possible to configure tomcat to "swallow" the output and direct it through the log4j software. To do this, locate the <context> block . Within the Serena Common Tomcat, you may wish to use the <context> block that is located in <tomcat-root>/conf/context.xml.
CMS-XML Errors in logs containing the word ModSecurity
You will need to review your configuration files to determine if your particular pertains to a valid block or needs reconfiguring. Further information to Configure this is in the Configurator help.
CMS-XML MCLG: Getting message "Windows has blocked this software because it can't verify the publisher." PopupMenu.dll
After logging into collage get this error against PopupMenu.dll: "Windows has blocked this software because it can't verify the publisher."
CMS-XML KM-Dim9:2006-FATAL_MOVE_CUROSR_1 Fatal Internal Error: Cannot move the cursor to the application block field %s.
A detailed control plan report Event logs (Windows OS only) /var/adm/messages file (Unix Only)
CMS-XML KM-Dim9:2003-FATAL_DESIGN_CANNOT_INVOKE_APP Fatal Design Error: Either application block %s does not exist or it cannot be entered.
A detailed control plan report Event logs (Windows OS only) /var/adm/messages file (Unix Only)
CMS-XML KM-Dim9:2009-FATAL_DESIGN_DB_3 Fatal Design Error: The database does not contain the necessary information for menus, application blocks, or user-definable attributes.
A detailed control plan report Event logs (Windows OS only) /var/adm/messages file (Unix Only)
CMS-XML KM-Dim10: Installation: During installation on Unix user might receive error concerning disk blocks
Installing Dimensions 10 on Unix, a "Disk space check error" can abort the installation. Following is an excerpt from an installation log on Solaris:
CMS-XML "Error contacting MongoDb!" or "MongoDb client not configured correctly!" errors in Server.log
If the service is actually running, other possibilities that may generate these errors or similar errors include the following: Local communication on the designated Active Diagnostics TCP port (default is 27017) is blocked by your security software or local machine firewall restrictions.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs