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 DA does not clean-up Dimensions log when it performs integration attempt.
DA does not clean -up Dimensions log when it performs integration attempt.
CMS-XML Need to cleanup 404 errors from IIS logs (httperr1.log)
Just to be clean , we should cleanup these errors. There shouldn't be 404 errors in the IIS logs.
CMS-XML DEMOTE log entires do not identify DEMOTE and CLEANUP.
DEMOTE log entires do not identify DEMOTE and CLEANUP .
CMS-XML IIS hangs with message in the application logs "Unknown Exception occurred during cleanup"
, Unknown Exception occurred during cleanup . User: username
CMS-XML mongoDB_winservice.log files for Active Diagnostics are not cleaned up
The "mongoDB_winservice. log " files being created in the "SBM\Common\Diagnostics\MongoDb\ log " directory for Active Diagnostics are not cleaned up automatically. You will need to manually clean them up occasionally.
CMS-XML SBM: About the "Clear History" feature used to schedule Common Log cleanup (Delete Common Logger)
The common log (sometimes called Common Logger) allows you to view information related to deployed applications and orchestrations. The common log data is stored in a database, as defined in the SBM Configurator. The data is only visible from the SBM Application Repository and from SBM Composer. It is best practices to prevent this log from growing too big.
CMS-XML When using the "Clear History" feature for common log cleanup, the job does not start at the time chosen by the user
When using the "Clear History" feature for common log cleanup , the job does not start at the time chosen by the user
CMS-XML Whole import log was sent in each notification email
Notification email for user/data import log contains all old import logs concatenated and not the current import log alone. Import log is not automatically cleaned up and whole import log was sent in each such notification email. Eventually the import log size grows and exceeds the email server size limit for email message, and customer stopped to receive emails with import results.
CMS-XML "reportimages" directory not getting cleared out and "Error trying to delete" messages in Application Event Viewer log
The files generated in the "Application Engine\reportimages" directory for scheduled reports are not getting cleaned out and there are the below messages in the Application Event Viewer log : Log message occurred in file: 'd:\bld\bm_mainline\bm_mainline-aex64\application_engine\software\teamtrack\source\utility\fileutil.cpp', line 58.
CMS-XML IIRF: New log file generated on every IIS restart
IIRF generates log files with filenames decorated with process id. This results in a new log file getting created every time IIS is reset and a user logs into WorkCenter. Currently we do not have mechanism to clean up old log files which will result in filling up the Application Engine/ log directory with iirf.out.#. log files (where # is a process ids) and so log files need to changed to have a single file or remove the procid.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs