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 Get the following error in the browser when opening or submitting an item. "The item could not be found."
Open the ODBC datasource screen in Windows which is usually in the Administrative Tools area Go to the System DSN tab and just verify that your new ODBC connection is using the driver called "ODBC Driver 11 for SQL Server" If it's not using that driver you can manually create one on that screen and select the driver then open configurator and point to the new ODBC Connection.
CMS-XML LogLevel information is missing from the Deployment Tool documentation
... /live " DSN =TeamTrack Sample; UID =PWD= ... /test " DSN =TT test; UID =;PWD ... ... the Deployment Tool verifies it can process ... ... ERROR: databases are not the same ... the Deployment Tool verifies the specified databases ... ... :30: verifying the controlled deployment ... ... :30: verifying the controlled deployment ... ... :30: verifying the controlled deployment ... ... deployment lock timestamp doesn't match, live ... ... : deployment locks are not valid ... the Deployment Tool verifies the system data ... 12/11/2006 10:48:55: verifying the system data lastids match
CMS-XML SBM: Settings on ODBC Data Source change every time we click Apply in Configurator
Next to the SBM_AE data source, click the link for "Change". ... Select the same SBM_AE option, and click the box for "Configurator will not overwrite any settings in your data source". ... Verify that your custom changes are still in place.
CMS-XML New Features in StarTool FDM 7.8
0001) DSN =SYS1 ... 0002) DSN =SYS1 ... 0003) DSN =SYS1 ... 0004) DSN =SYS1 ... 0005) DSN =SYS1 ... 0006) DSN =ADCD. ... 0007) DSN =CEE. ... 0008) DSN =CSQ520 ... 0009) DSN =IOE. ... 0010) DSN =EOY. ... 0011) DSN =HLA. ... 0012) DSN =CBC. ... 0013) DSN =IGY310 ... 0014) DSN =IEL111 ... 0015) DSN =FAN130 ... 0016) DSN =SYS1 ...
CMS-XML Readme for SBM 10.1 as of 9th February 2012
No longer supported: ... been deprecated and will not contain any of ... ... Oracle for SBM DSN Changes and Support ... ... the Flash Player is not installed or enabled ... ... SBM Application Administrator does not use an ODBC ... ... " and " Is Not (None) ... ... for creating escalations has not changed, however ... ... to those that do not have subscribers. ... of all files does not exceed the size ... ... the last cycle is not yet finished. ... means that users do not have to log ... ... the auth, make sure that the user ... ... automatically assigned and cannot be modified.
CMS-XML Configuration Files, Web Interface Templates, JavaScript Files, and String Changes That Have Changed in 2009 R4
... TABLE"> Could not read NSInstance table ... ... }'' does not exist.< ... ... .EN} does not have the privilege ... ... .EN} does not have the privilege ... ... .EN} does not have the privilege ... ... .EN} does not have the privilege ... ... .EN} does not have the privilege ... ... .EN} does not have the privilege ... ... .EN} does not have the privilege ... ... .EN} does not have the privilege ... ... .EN} does not have the privilege ... ... .EN} does not have the privilege ...
CMS-XML Restrictions and recommendations on use of NULLFILE promotion shadow libraries
... the Shadow Library dataset name if you wish ... ... , overlay messages will not show a ' ... but there is no promotion history) ... The general design around use of NULLFILE promotion shadow datasets has not changed for many years and dates back to pre-ChangeMan ... Wherever possible we recommend that customers define shadow libraries for their promotion environments to ensure that optimum behaviour is obtained
CMS-XML FAQ - DB2 Option Changes in ZMF 8.1.1
... for CMNPLAN on DSN looks like this ... ... CMNDB2SQ does not set DB2 ... ... in the PKLIST does not work for pre ... Wouldn't the wildcard entry in the PKLIST support the pre-8.1.1 version of CMNDB2SQ (i.e. *.CMNDB2SQ)? ... Meaning the DB2 special register (CURRENT PACKAGESET) is not set. ... Meaning, the DB2 special register (CURRENT PACKAGESET) is not set. ... EXPLAIN( NO ) VALIDATE (RUN) ACQUIRE(USE) RELEASE(COMMIT)
MS-WORD ChangeMan ZMF Hilo Documentation Content and Notes
... Generally, this will not be the case ... ... SET CPYLIBA = NO ... $$XSC ensures that the extracted ... ... interface, then no additional customization related ... ... DELETE), DSN =&& ... ... PASS), DSN =&& ... ... DELETE), DSN =&& ... ... PASS), DSN =&& ... ... DELETE), DSN =&& ... ... PASS), DSN =&& ... ... DELETE), DSN =&& ... ... PASS), DSN =&& ... ... DELETE), DSN =&& ... //SYSUT2 DD DISP=(NEW,PASS), DSN =&&&&SOURCE(&CMPNAME),
PDF ChangeMan ZMF 6.1 CMNCICS1 NEWCOPY.fm
... =SHR, DSN =CMNTP. ... ... =SHR, DSN =CMNTP. ... =SHR, DSN =CMNTP. ... =SHR, DSN =CMNTP. ...
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs