[Microsoft][SQL Native Client][SQL Server]The specified schema name "TEST2" either does not exist or you do not have permission to use it. Error detected in E:\Program Files\Serena\Dimensions 2009 R1\CM\dbms\mssql\translated\mssql_create_base_tables.sql, line 14 Called from E:\Program Files\Serena\Dimensions 2009 R1\CM\dbms\common\setup_base_database.sql, line 279
The Serena Oracle 11 x64 runtime installation does not created the instance if during the installation a different location is specified for the DB files to the Oracle binaries. The installer asks for the installation location first and later on for the location of the actual database files. If you choose two locations on different drives then the installation will run through but the instance never gets created.
This problem happens when you go through the wizard to setup the import. On the screen where you " Specify Data to Import" you pick your table and if you choose the "Data type of matching column" and choose "Character" your import will work fine as long as you don't put anything in the "where" box. So if you choose "Character" as the matching column and put anything in the "Select records from source table when" box then you will get the following error when you run the import.
When referencing ts_name or ts_internalname in ts_states with an app script, if either is over 30 characters, it fails with "ORA-00972:Identifier is too long" which is due to an Oracle limitation. It appears we accommodate this limitation in other areas in Composer when creating names /internal names , States can still be created with long names /internal names .
Example to reproduce: 1) Create a transition form with two text fields with the same display name (different db name ), make sure both are required 2) Enable form validation feature for this form
ontacts in the xls can be specified with the first name in addition to the last name (2 different formats). First name will be considered during import.
Windows Service with specified name "SRA-Agent" already exists . This happens on fresh Windows installations so the error message is misleading. As a workaround the service can be created using the following batch file
DS "S1" COR4300107E Error: The stream specified - 'S11' - does not exist in the product => if you try to delete the stream in a third stream, it doesn't delete the expected the stream
DS "S1" COR4300107E Error: The stream specified - 'DIME1' - does not exist in the product => if you try to delete the stream in a third stream, it doesn't delete the expected the stream
