|
Results |
|
SBM Version Diff
Differences Between Versions ... htm2014- 12 -23 ... -05- 12 16:27 ... ... + padding: 12 px 12 px 1px 12 px; ... -left: 12 px; ... + height: 12 px; ... + width: 12 px; ... left: - 12 px; ... + height: 12 px; ... left: - 12 px; ... -left: 12 px; ... left: - 12 px; ... ;padding: 12 px 12 px 1px 12 px}. ... ... -left: 12 px;display ...
|
|
|
SBM Version Diff
Differences Between Versions ... "2013- 12 -25 ... "2014- 12 - 12 ... // parameter error { - msg ... ... / permission denied error { - msg ... ... // database error passed through { ... ... // general error passed through { ... ... "2014- 12 -24 18 ... ... 01-19 12 :02: ... ... -01- 12 17:57 ... 12 :25: ... ... "2014- 12 -11 03 ... ... "2014- 12 -11 03 ... ... -1, 12 +1, ... ... 01 00: 12 :02. ... ... .length - 12 , className. ...
|
|
|
SQL*Plus Report
... c3e 12 c_accessibility ... ... _SOAP11 Fault EXECUTE /e ... ... 619_AuditedProfile 12 EXECUTE /e ... ... EXECUTE /ea 12 ead2_ ... ... ec0dfc 12 _AnnotationHandlerExt EXECUTE ... ... ecb6ba 12 _JArray EXECUTE ... ... EXECUTE /ee 12 e138_ ... EXECUTE /eebc 12 f4_ ... ... eeee2e 12 _MetalPopupMenuSepara EXECUTE ... ... f136be 12 _DGroupPattern EXECUTE ... ... 3_PKCS 12 PBECipherCore EXECUTE / ... ... bc_ParserTable 12 EXECUTE /f ... ... a_AuditedProfile 12 Audi EXECUTE / ... ... abec_MotifLookAndFeel 12
|
|
|
Dim12: SSO: Error processing LDAP search result(s): Unprocessed Continuation Reference(s)
The following error can occur when attempting to log into Dimensions CM and using an SBM SSO Server: Error processing LDAP search result(s): Unprocessed Continuation Reference(s). The above error generally occurs after enabling LDAP authentication within the SBM SSO Configuration.xml file as per our Knowledgebase Solution S138351 How to setup Dimensions CM, RM and other Serena products to utilize the SBM SSO using LDAP authentication model
|
|
|
Dim12: SSO: When using a Load Balancer with Dimensions CM and SSO, the Dimensions CM Servers provide error messages
When using a Load Balancer with Dimensions CM and SSO where the SSO Server resides on the SBM Server, the Dimensions CM Servers provide error messages similar to the following: ALF SSO Gatekeeper error has occurred: Error processing federation services response. Detail
|
|
|
Dim12: SBM2DM Connector: Error: Could not start transition from state Development to state QA (-1) Transition '' is not valid for transitioning item number 2511 (item 34) in table 1006. [(:TSPrimaryItemStartTransition: Error starting transition Start transition failed.
Dim12: SBM2DM Connector: Error: Could not start transition from state Development to state QA (-1) Transition '' is not valid for transitioning item number 2511 (item 34) in table 1006. [(:TSPrimaryItemStartTransition: Error starting transition Start transition failed.
|
|
|
Dim10: SBM2DM: When validating connection through Connector between Serena Business Mashups 2009 R1 and Dimensions 10 an Authentication Failed error occurs
This can be caused by "Accept Info From Browser/Header" checkbox being unchecked in the Mashup Administrator . You can find this setting in the Mashup Administrator under Options / Settings / Server / Authentication.
|
|
|
Dim2009R2: SSO CAC: Web Client and Admin Console provide a 404 Page not found error when using SBM SSO Server
DIM CM w/SSO: WebClient and AdminConsole provide 404 Page not found error Environment: SBM 2009R3 with SSO already installed and working on this machine with IIS Web Server
|
|
|
Errors appear in Chinese for SBM-DIM web services operation
If you see what appear to be Chinese characters in Common Log entries (and you are not on a Chinese locale), this may be because your default OS locale is set to one that uses high-ASCII characters (such as French, Spanish, German) and the OS is sending an error message as a result of a problem when making a WebService call. This character is not translated to UTF8 when pasted into the CL entry, thus causing the CL display to display incorrect characters.
|
|
|
Dim10: SBM2DM Integration: Request ID is missing
Dim10: SBM2 DM Integration: Request ID is missing error occurs in log files.
|
|
|