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 Changing Threshold for Long Running Reports Recorded by Active Diagnostics
Changing Threshold for Long Running Reports Recorded by Active Diagnostics
CMS-XML CMNDB2TM incorrectly reporting IA table out of date
Despite improving the diagnostics associated with and also fixing one potential cause of the problem documented under solution number 14401 in CMN ZMF 5.5.3, it appears that the same symptoms persist from another underlying problem. The symptoms seen show the CMNDB2TM installation jobstep to fail with a return code 4 claiming that the IA table is out of date. This is despite the fact that the improved diagnostics prove that the problem library does indeed exist in the BUN table.
CMS-XML CMNEX034 causing CMNDB2TM to incorrectly report IA table out of date
This solution is related to solutions 14401 and 5005449 which both resulted in additional diagnostics being added to CMNDB2TM. Anyway, it appears that the underlying problem is being caused because CMNEX034 is coded to treat a library type as like-JCL and the application being processed does NOT contain a library type named JCL. The specific error messages vary from version to version but now look like this: CHANGEMAN(R) 5.6.1C DB2TM - 2007/11/06 01:54:02
CMS-XML MongoDB is reported by some security tools as a problem on its port 27017
Mongo DB (also known as Active Diagnostics or SBM Logging Services) is reported by some security tools as a problem on its port 27017 SBM only uses Mongo DB to log information and diagnostics for Support and R&D use.
PDF Serena® Mariner® 6.2 Data Access and Reporting Guide
SPGetDriverInfo SPGetDriverInfo returns information about the connection that is useful for diagnostics : the database title, the database server, and <web server/application server>. 44
PDF SBM Reporting Guide
Important: On-premise customers must ensure that the SBM Active Diagnostics service is running in SBM Configurator in order to capture and display application usage information. To run the report:
CMS-XML An unexpected error was encountered when uploading a custom report into Mariner.
The item '/PESReports/PESCustomReports/MARINER-VMWARE_trialjumpstartaccelerator/PESAdminReports/ACME-Report' cannot be found. ---> Microsoft.ReportingServices. Diagnostics .Utilities.ItemNotFoundException: The item '/PESReports/PESCustomReports/MARINER-VMWARE_trialjumpstartaccelerator/PESAdminReports/ACME-Report' cannot be found.
CMS-XML Looking at the Report Server Manager page there isn't a Contents or Properties tab.
The permissions granted to user 'MARINER2009VM\IUSR_MARINER2009VM' are insufficient for performing this operation. ---> Microsoft.ReportingServices. Diagnostics .Utilities.AccessDeniedException: The permissions granted to user 'MARINER2009VM\IUSR_MARINER2009VM' are insufficient for performing this operation.
CMS-XML Diagnostics: Not able to set maximum log size.
Diagnostics : Not able to set maximum log size.
CMS-XML KM-Dim7: How to run PC Client Diagnostics
KM-Dim7: How to run PC Client Diagnostics
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs