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 Disable Audit Monitoring in Application Repository
Disable Audit Monitoring in Application Repository
CMS-XML Audit Log Purge History does not Clear
Audit Log Purge History does not Clear
CMS-XML Vul ID: V-69375 / STIG ID: APSC-DV-000680 - The application must provide audit record generation capability for HTTP headers
Vul ID: V-69375 / STIG ID: APSC-DV-000680 - The application must provide audit record generation capability for HTTP headers
CMS-XML High CPU on database for Application Repository at midnight and also when selecting to purge the "Audit History log"
High CPU on database for Application Repository at midnight and also when selecting to purge the " Audit History log"
CMS-XML SBM 11.4.2 Hotfix 3: Ability to turn on/off the automatic Audit Monitoring purge (workaround for DEF320998)
SBM 11.4.2 Hotfix 3: Ability to turn on/off the automatic Audit Monitoring purge (workaround for DEF320998)
CMS-XML Is there a way to remove adding and deleting notes/attachments regardless of ownership or submitter and only base it on State or the Active/Inactive? Possible audit requirement
Is there a way to remove adding and deleting notes/attachments regardless of ownership or submitter and only base it on State or the Active/Inactive? Possible audit requirement
CMS-XML Purging the audit log history impossible to cancel permanently on SQL Server and can cause deadlocks with Oracle - java.exe CPU 100% even after restarting
Purging the audit log history impossible to cancel permanently on SQL Server and can cause deadlocks with Oracle - java.exe CPU 100% even after restarting
CMS-XML Application Repository receives Method Not Allowed (405) error when proxied through IIS
Application Repository action performed Clear audit log Edit or remove servers from environment
CMS-XML SBM: Repository Purge History always adds 2000 to the year
When trying to purge data (Repository > Advanced > Audit History > Purge History), you can give a date. However, no matter what the user enters as the year, the system always adds 2000 to the year.
CMS-XML Fails to get the snapshot list if last promote activity was deleted and purged
2. In the activity view, delete the promote activity. 3. In the Audit Log view, purge all history items 4. Refresh the snapshot view
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs