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 VM and SBM installed on the same server can yield Failed to add MIME Type "text/plain" for file extension ".properties" when VM uses IIS
Anonymous Logon User Anonymous
CMS-XML Login to SBM fails: SBM gsoap application pool inadvertently changes from 64-bit to 32-bit
On 64-bit servers, if the Application Pool Defaults value in IIS is changed to 32-bit (either by an administrator or by another installed application), then the next time you apply changes in SBM Configurator, the dedicated gsoap application pool will also change to 32-bit mode (Configurator sets gsoap to match the default when you click Apply
CMS-XML How to setup Dimensions CM, RM and other Serena products to utilize the SBM SSO using LDAP authentication model
Once the user is authenticated via LDAP, a SAML token will be issued to the client for the user. If the user exists in the client requesting authentication, the user will be logged in , otherwise a login failure will occur. For example, if I go to the Dimensions CM website, I will be redirected to the SBM SSO Engine where my login can be authenticated via LDAP.
CMS-XML Error "InitExtension Failed" when logging into the SBM User Workspace
Open the Widnows ODBC Data Source Administrator > System DSN, and configure the SBM DSN. As you click through the wizard, you will be asked for the login /password. ... The user needs these permissions: Full permissions to the SBM installation directory
CMS-XML ALFEventManager.log error if Event Manager email settings are partly configured
If only the SMTP server is ticked and configured the following error messages are logged in the ALFEventManager.log file 2015-02-25 08:46:58,948 ERROR [mailto-Worker-15] [org.apache.axis2.transport.mail.MailTransportListenerEx] [::] -- Error connecting to mail server for address : SBMEventUser@localhost :: Connect failed ... Connect failed ;
CMS-XML If you install SBM then Soo and promote the solutions without going to workcenter then get SRC errors - Error Getting Catalog: No service Catalogs found.
If you install SBM and then SOO and then promote the snapshots per the documentation then all the promotes are marked as status complete but all have the following info message in the activity log: ... Failed to complete the deployment to server "Work Center Server" at 13/01/14 10:20. ... This results in the following error when trying to logon to SRC:
CMS-XML Email Submit: IMAP connection uses Mailbox Name instead of Mailbox Email Address to login
After setting up the system to allow for email submit (See S138405 for details.), the emailclient.log ... 01/04/2012 12:57:32: IMAP Response failure , Command: LOGIN , Response: A1 BAD Too many arguments provided n3if51719575qcb.44
CMS-XML For SBM versions 11.0 to 11.6.1, the default sample SBM Certificates for STS, Federation Server and SSO Gatekeeper expire on 15th June 2020.
**** Warning: Expired SSO certificates will prevent login even if you are running SBM Sessions. ... Users will not be able to connect to SBM and will see the error message: Failed to verify signature If you regenerated your SSO certificates at install /upgrade time, you will not be affected at this time.
CMS-XML Mapping auth section to working data complex type doesn't use userid password
5. Assuming you have SSO turned on login with an admin account. 6. Do whatever transition you set up to make the orchestration run and look at the debug log. ... 10. Notice the orchestration should fail because this time it's using the userid and password specified.
PDF Full-Text Indexing for Social Experts in Serena Business Manager
... of the service logon account. ... , it is configured using the Local ... ... account (or logon account of FDLauncher ... When an Oracle Text index is not functioning, the following error appears in the Event Viewer and the Application Event Log: "ORA-29861: domain index is marked LOADING/ FAILED /UNUSABLE". To fix this issue, you must perform the following steps to remove all of the broken indexes: 1. To get list of all broken indexes, run the following command:
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs