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 Exception caught in common logger while ...
There could be several reasons behind these error messages and some of those are described below : 1) If SBM is connected to an SQL Server 2005 these errors will be thrown if the ODBC connection is created via an ' SQL Server ' ODBC driver as opposed to an 'SQL Native Client' ODBC driver .
CMS-XML If SQLServer2008 or higher is used and instance name is set, common logger exception occur
SBM 2009 R3
CMS-XML LoggerConf.xml uses incorrect driver when admin installs latest SQL Server driver
Exception caught in common logger while getting context types. Common logger will not be used. Check that the configuration file '.../Serena/SBM/Application Engine/LoggerConf.xml' exists and has correct settings.
CMS-XML SBM: Event viewer gives error "Exception caught in common logger while getting context types. Common logger will not be used."
Details: Failed to connect to database. - [Microsoft][ SQL Server Native Client 10.0] SQL Server Network Interfaces: Error Locating Server/
CMS-XML SBM 10.x and above: How to migrate your SQL Server or Oracle database to another supported DBMS
Repository database Common Log database Configuration Settings database
CMS-XML Database Clients and Drivers for SBM
\Serena\SBM\Application Engine This file contains the datasource connection information for the Common Log database. If you are upgrading from an earlier version, make sure you install the appropriate SQL Server driver for your database (as described above) before the upgrade.
CMS-XML How to enable SBM to communicate via SSL with a SQL Server database
Application Repository Common Log Note:
CMS-XML How to enable SBM to communicate via SSL with a SQL Server database in SBM 11.x
Application Repository Common Log Note:
CMS-XML SBM: About the "Clear History" feature used to schedule Common Log cleanup (Delete Common Logger)
from QRTZ_ACTIVITY where NAME = 'ClearCommonLogJob' SQL Server : SELECT NAME, CHRON_SCHEDULE, dateadd(ss, TIME_STOPPED/1000, '1/1/1970') as LAST_COMPLETED,
CMS-XML The Common Log does not report Application Engine messages when using Oracle as your database
To correct this problem, edit the LoggerConf.xml file and set the proper driver information. The original file will appear with the SQL Server driver information by default: <?xml
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs