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 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 Import: mapping single select values gives error "Number of bound columns exceeds the number of result columns"
6. Run the import wizard. Make sure to choose the "Import from another SBM database" option, but connect to source using the new Oracle 11.1.0.6 ODBC driver DSN . You should now be able to map the select values without errors.
CMS-XML SBM Installation against SQL Server 2012 SP1 does not work
When trying to install SBM 10.1.3.1 on a Windows 2008 R2 x64 Server against a local SQL Server 2012 SP1 it is not possible to get this setup working. 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.
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 . ... Step 2: Verify the IUSR permissions
CMS-XML Composer - Adding images via dropdown in Image control does not check-out the Application as needed
Composer - Adding images via dropdown in Image control does not check-out the Application as needed
CMS-XML SBM Composer Script context menu doesn't have a validate script option
The Script context menu does not contain a validate script option. A validate script option would make it easier to view the script.
CMS-XML Unable to validate escaped app script with multiple quotes.
The following code is valid vbscript and is used to escape a double quote but when you try to validate it in composer you get the error below. It's hard to read but there are six double quotes total, three on each side of the text variable used.
CMS-XML Composer error - connection attempt failed. Could not connect to the Repository. Please check that the connection settings are correct. Underlying error: (No compatible tokens found on the request).
Could not connect to the Repository. Please check that the connection settings are correct. Underlying error: (No compatible tokens found on the request).
CMS-XML Upon validation of process app, verify that workflow annotations do not have invalid XML characters.
Upon validation of process app, verify that workflow annotations do not have invalid XML characters.
CMS-XML Should not auto-validate a script when using the Composer "find" feature
When you use the Composer find feature for a string in any AppScript (with many results of same string) the results are posted in the "Find Results". When to select these and "go to location" then appscript is validated each and every time.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs