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 When clocks go back from daylight saving elapsed times calculations on transitions cause incorrect elasped time or transition failure with error : Calculation underflow error with operands ....
(2) Elapsed2 = Last modifed date minus submit date This occurs for 1 hour in a year for transitions occuring between midnight and 2am for when return from daylight saving . Example to reproduce:
CMS-XML DIM CM: JavaScript now fails when setting attribute value
When setting an attribute value using the Java API, for example Length (attr.setDisplayLength(40)), a subsequent save or set of valid set fails with a null pointer exception: JavaException: com.serena.dmclient.api.DimensionsRuntimeException: java.lang.NullPointerException
CMS-XML Orchestration fails with stack overflow when too much data included in event
Orchestrations fail before they are even started (nothing gets written to the Common Log) with what appears to be a stack overflow in the server.log file when the event includes too much data (over 2,000 multi-relational field values in this particular example).
CMS-XML Changes in aewebservices71 web services after 10.1.3 cause applications to fail
When an item has extended fields, the API used to return a blank object with blank name/value pairs. However, after upgrading to 10.1.3, the calls return a null object. Now all API apps need to be re- written to look for null instead of blank.
CMS-XML Composer reports 'Load attempt failed' for report without any columns
3) Delete all columns from the report (there will be Item Id and Title columns by default) 4) Save and Close process app 5) Open the newly created process app, try editing the listing report
CMS-XML Patch Context Process app with INCLUDE statement to global fail validation. 09R4.01
A process app in a patch context. This process app references the global app. Scripts in the process app that include scripts from the global can't validate because the scripts from the global are not written to the validation directory.
CMS-XML Orchestration failing when working data variable mapped to
To work around this issue, make sure that all working data variables have the same namespace or use a calculate step to write a value to the working data variable rather than mapping it directly on the orchestration workflow data mappings.
CMS-XML CM/SDA/SRA/SDA/RLM: Error "SSO Gatekeeper error has occurred: Error obtaining security token. Validation of WS-Federation token failed with code 40:Token issuer not allowed"
to export the certificate. Save this as a .pem
CMS-XML 12.2 : when deploying a preserved load on z/os, got this error : MDHMDA4501692E Error: Failed to create metadata directory "//.dm/": mkdir() failed with 133 (EDC5133I No space left on device.)
MDHMDA4501692E Error: Failed to create metadata directory "//.dm/": mkdir() failed with 133 (EDC5133I No space left on device.). COR4501240E Error: failure writing metadata for file MVS::MDHUSER.DIMSVI.LOADLIB(AER121) COR4200138E Error: Failed to update Item for 'MDHUSER.DIMSVI.LOADLIB(AER121)'
CMS-XML How to get a copy of the certificate chain and copy it to the certificate trust store ("PKIX path building failed" or similar SSL connection errors.)
On the Details tab, click the "Copy to File" button, and save the certificate as a DER encoded .cer file.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs