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 The data source 'DSN=xy Oracle;UID=xz' could not be verified
the server name, login ID, and password to make sure
CMS-XML Report gives error "Cannot create a connection to data source 'DataSource1'. Server location is invalid"
However, it defaults to the current server name. So, if the report server and the application server are on different machines, the default value will be incorrect. To prevent this problem, you should make sure the correct server (the application server) is entered.
CMS-XML DimCM: MF Connect: Error "Could not communicate with connect server" generated when setting up Dimensions CM as a Data Source for MF Connect
DMPOOL 2020/05/12 10:03:25 T P988 T1220-CT7 rpc_StartServer_srv2(00000000000002B0): Start dmappsrv for MICROFOCUS-CONNECTOR DMPOOL 2020/05/12 10:03:25 T P988 T1220-CT7 findLicense(nodenotused, dmsys): Checking out new license of type DIMENSIONS
CMS-XML Cannot connect to Mashup Manager / Application Repository
see WebWare gsoap ISAPI module documentation." Check that your datasource is correctly defined in your Mashupmgr-ds.xml in the deploy directory. Example of SQLServer snippet - replace the italics as appropriate
CMS-XML SBM Installation against SQL Server 2012 SP1 does not work
The documentation states the SQL Server Native Client 11.0 must be used for the ODBC system DSN but if this is used then Configurator states "A data source configuration conflict has been detected. Please make sure the Application Engine ODBC data source settings are synchronized with settings in the Database Servers tab. Database Servers".
CMS-XML ODBC password displaying in mail log
The data source 'DSN=TeamTrack_Prod;UID=teamtrak;PWD=*********' could not be verified . Error Opening Database The actual password for the database is displayed in the log file when this error appears.
CMS-XML Get "InitExtension Failed Some TS_LASTIDS table entries conflict with TS_ID values in other tables" when logging into SBM
InitExtension Failed: The data source 'DSN=SBM;UID=sa' could not be verified . Error Opening Database
CMS-XML InitExtension - Error Opening Database while logging on the SBM User WorkSpace.
InitExtension Failed: The data source 'DSN=Mashup2009;UID=sa' could not be verified . Error Opening Database.
CMS-XML InitExtension error when AE db needs to be upgraded still says to use SBM System Administrator
InitExtension Failed: The data source 'DSN=SBM;UID=sa' could not be verified . Error Opening Database
CMS-XML Tracker 7.5.00 with Sybase 12.5 - Tracker Admin will shut down unexpectedly if invalid information is entered in the DBMS User or Administrator field, and the Verify User or Verify Admin button is clicked.
The Test Connect feature in the ODBC driver may be used to verify valid user information. To access the Test Connect feature, open the ODBC or Data Sources control panel, double-click on the Sybase driver in the User or System DSN tab, and click Test Connect.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs