| |
Results |
|
KM-Dim9: When trying to run the CRDB command with a Process Model export from Dimensions 7, error of Error: unknown command , Error detected in basedb_cpl.exp, line 1 occurs.
|
This is because the export file format in Dimensions 8.x and 9.1.x is very different and the scripts that create the new Base Database cannot interpret the file generated from Dimensions 7 installations. The errors you receive will look like this:
|
|
|
|
DateAdd 1st of month: Numeric overflow -- ERR #2 Line X
|
Work Around As a work around, we can modify the script the so that instead of expiring the item in 6 months, we will expire the item in 180 (30 *6) days. dtExpires = DateAdd( "m", 6, dtWedding ) becomes
|
|
|
|
How To: #1028 Create a local input script (User receives an Error 1; run fine from command-line but not from CB script call)
|
--------------------------------------------------------------- The key is that $(_Source)($(_Target)) is on a secondary line in the first column & followed on the next line by a < in the first column.
|
|
|
|
Communication Error -1 when transferring a large number of files on an AIX server
|
This situation occurs because the server ran out of address space for the Data segment, causing an abort signal to be issued when attempting to malloc() for a "new" declaration. The solution is to add a line in the execution script of the server (if one exists), or just to bump up the ulimit as follows: ulimit -d value
|
|
|
|
Incorrect underscore in SBM2008 R2 script documentation
|
The underscore at the end of the line denotes that the next line is an extension of the previous one . In this case, the underscore is not necessary. This has been corrected in the 2009 R1 Mashup Script Reference guide.
|
|
|
|
Communication Error -1 when transferring a large number of files on UNIX server
|
This situation occurs because the server ran out of address space for the Data segment, causing an abort signal to be issued when attempting to malloc() for a "new" declaration. The solution is to add a line in the execution script of the server (if one exists), or just to bump up the ulimit as follows: ulimit -d value
|
|
|
|
Dim CM 2009 R2: Deploy script error inconsistent
|
TPL1602017E Error obtaining entry point: Abandoning callout request TPL1602002I at line 2 in file test 1 .tpl TPT1600145I template processing terminating: errors were encountered
|
|
|
|
KM RTM 5.6 icConcept Error : Error parsing script. This script can't be edited using the Script generator. The script must be edited manually
|
The output should tell you what attribute is the root cause of the Error message if the error raised is from one of line 5 to 13 of the script you will need to delete the "corrupted" attribute the re-create it (*)Content of the Script.sql see below
|
|
|
|
Script content with {} bound variables throws unterminated string error
|
</script> This defect can be worked around by putting the entire javascript function on one line with no line breaks like below. <script>var x= GetFieldValue("");alert(x);</script>
|
|
|
|
Rich text field in discussion log causing slow script error
|
3. Now open the second item and type " Line One " and hit enter and then type " Line Two" and hit enter. Now save
|
|
|
