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 If you import an SLS export file that does not include the default US English values then on import all defaults are deleted and you get errors : "Missing default Locales(en_US) value for key"
If you import an SLS export file that does not include the default US English values then on import all defaults are deleted and you get errors : "Missing default Locales(en_US) value for key"
CMS-XML SLS, Application Engine, Unknown Error, During SLS Import Of New Property Files
Task Category: None Level: Error Keywords: Classic
CMS-XML Cannot import localization (SLS) file to On-Demand SBM - get following error - An error occurred while importing locales: On-Demand user not allowed to import new Key:
Cannot import localization file to SAAS SBM via the Application Administrator: Error: An error occurred while importing locales: On-Demand user not allowed to import new Key:
CMS-XML Some strings are not being shown in Locale - default string is being shown instead - Regression in 11.4.1 - localization - Error: Unknown Error, During SLS Import Of New Property Files
This can happen if you have a particularly large string then a database exception occurs and the end user sees the default strings instead Error in Windows Event Viewer: Unknown Error, During SLS Import Of New Property Files: 'C:\Program Files\MicroFocus\SBM\Application Engine\bin/javascript/appacmin/locale'
CMS-XML SQL Server: Incorrect SQL unique constraint violation occurs during SLS import when data contains characters that are not in the default SQLServer collator
This problems affects 32 and 64-bit SBM installations. Administrators can use the following SQL to fix SLS import problems on SQL Server when the data contains characters that are not in the default SQLServer collator. This causes incorrect SQL unique constraint violations to appear.
CMS-XML Error after upgrade :org.hibernate.exception.GenericJDBCException: could not insert: [com.serena.sls.entity.Value]. Not possible to see SLS values for ProcessApps
00000 ERROR 24-04-2015 15:25:34 [ImportExportServiceImpl] -- error Value : Import Error (Category: c77d0182-8c6e-43ee-bc9a-722ccc486e56, Section: APPDESC, Key: c1f2f84e-f822-40da-8d44-cf57775d89c6): javax.persistence.PersistenceException:
CMS-XML Users unable to get into Work Center due errors "Unable to validate user" and "Error: Not Found" and "Error static Top : Not Found"
Below, we describe different causes for this error: Use Case 1: SLS Import fails with "User does not have privilege to perform this operation"
CMS-XML After upgrade, Work Center does not load, gives error "Error static Top : Not Found"
02/25/2014 18:15:32: Begin SLS Import of 'C:\Program Files\Serena\SBM\Application Engine\payload\ sls _swc.xml'
HTML Template Content Differences
successfully 3148 SLS . import .activity. error =An error
HTML SBM Version Diff
Differences Between Versions ... (data. error ){ ... >File upload error error .msg+ ... ;s< sl ;s+ ... ... $scope. err (resp) ... ... } catch ( err ) { ... showErrorMessage(' Error initializing pin app ... ... ">$ SLS (swc. ... ... ">$ SLS (swc. ... ... ">$ SLS (swc. ... ... ="$ SLS (swc. ... ... p>$ SLS (swc. ... ... p>$ SLS (swc. ... ... p>$ SLS (swc. ...
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions RM: Importing Requirements
This demonstration show you how to import requirements from CSV, Microsoft Word, and Microsoft Excel files to Dimensions RM.

Additional Assistance

  • Submit a Case Online
  • FAQs