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 Error "BAD User is authenticated" after trying to setup email authentication
ERROR 24-05-2022 10:08:05 [MailClient] -- Exception while processing mailbox recordersbm@o365.MyCompany.com : IX4 BAD User is authenticated but not connected .
CMS-XML SBM: OAuth2 tokens must be refreshed every hour
nested exception is: com.sun.mail.iap.BadCommandException: R4 BAD User is authenticated but not connected . at com.sun.mail.imap.IMAPFolder.logoutAndThrow(IMAPFolder.java:1180)
CMS-XML Dim10: SBM2DM: When validating connection through Connector between Serena Business Mashups 2009 R1 and Dimensions 10 an Authentication Failed error occurs
Error : Could not connect to Serena Business Mashups! Authentication Failed.No user information.; TSSERVER::Send: Initial retCode from Server was 0;
CMS-XML SBM: SQL Server using Windows authentication fails with "OpenEx failed with connect string"
Login failed for user 'USERNAME$'. Login failed for user 'USERNAME$'.
CMS-XML How to use Anonymous Authentication for External users while using NT Challenge/Response ( NTCR ).
This authentication choice is good for users who are internal to an organization and are logged into a domain. However, this is not suitable choice if you plan to need to allow other users access (e.g. outside of the domain). To get around this, you will need to make your server accessible to those users outside of your organization, (you can alternatively set up a second server outside a firewall that connects to the same production database.)
CMS-XML Get the following error when using test connect in Composer "Underlying error: (The HTTP request was forbidden with client authentication scheme 'Anonymous'.)"
You will see these errors if you have enabled "Client Certificate Authentication" from within Configurator but have not followed the steps yet to configure Composer to use those settings. If you look in Configurator and go to the Security > Client Certificate Authentication tab and the "Enable SSL Client Certificate Authentication" checkbox is checked then make sure you also do the following for your Composer users . Open the SBM Installation Guide for your version of SBM
CMS-XML Logging into Repository or Composer gives "Authentication Failed: Unable to contact Authentication Service"
Users are able to log into the SBM Application Engine ( http://servername/tmtrack/tmtrack.dll ?), however, no one can log into the Repository ( http://servernmae/mashupmgr ) or connect using Composer. Composer gives error: Connection attempt failed.
CMS-XML General error message when user with insufficient privileges tries to Manage Data on an auxiliary table
The following error message appears when a user without privileges for Auxiliary tables clicks the Manage Data link :
CMS-XML Authentication failure. User '' is deleted or non-existent. Failed to contact Authentication Service at with reason: Invalid User ID or Password.
Authentication failure. User '' is deleted or non-existent. Failed to contact Authentication Service at with reason: Invalid User ID or Password.
CMS-XML Logging into Repository gives error "Authentication error: A Soap fault occurred while contacting the authentication service"
When trying to log into the SBM Application Repository, the user gets the following error:
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs