Error Message Guide

Error Messages Explained
BusinessObjects XI Release 2 Update
Windows and UNIX

Patents Business Objects owns the following U.S. patents, which may cover products that are offered
and sold by Business Objects: 5,555,403, 6,247,008 B1, 6,578,027 B2, 6,490,593 and
6,289,352.
Trademarks Business Objects, the Business Objects logo, Crystal Reports, and Crystal Enterprise are
trademarks or registered trademarks of Business Objects SA or its affiliated companies in the
United States and other countries. All other names mentioned herein may be trademarks of
their respective owners.
Copyright Copyright © 2006 Business Objects. All rights reserved.

Last update: March 2006
Third-party Business Objects products in this release may contain redistributions of software licensed
contributors from third-party contributors. Some of these individual components may also be available
under alternative licenses. A partial listing of third-party contributors that have requested or
permitted acknowledgments, as well as required notices, can be found at:
http://www.businessobjects.com/thirdparty
Contents
List of Error Messages 5
Chapter 1 Setup Error Messages 17
Chapter 2 Administration & Security Error Messages 25
Chapter 3 Universe Error Messages 33
Chapter 4 Document and Universe Exchange Error Messages 39
Chapter 5 Data Access Error Messages 63
Chapter 6 Web Intelligence Error Messages 77
Chapter 7 Miscellaneous Error Messages 107
Chapter 8 Crystal Reports Error Messages 111
Chapter 9 Enterprise Performance Management Error Messages 115
Chapter 10 Process Tracker Error Messages 125
Chapter 11 Report Conversion Tool Error Messages 129
Chapter 12 Question Designer and Intelligent Question Error Messages 135
Appendix A Business Objects Information Resources 141
Error Messages Explained 3

Contents
4 Error Messages Explained

List of Error Messages
A ADW0016 Cannot find Index section in RSS file.
A A runtime error has occurred. (IQ (ADW0016) 30
00024) 139 ADW0017 Cannot find Insert section in RSS file.
ADM 00207 You do not have the rights to use (ADW0017) 31
personal data files. Please contact your Business ADW0019 Cannot create document domain.
Objects supervisor. (ADM 00207) 28, You are not (ADW0019) 31
authorized to delete a user who also belongs to at ADW0021 Cannot find the external script.
least one group that you cannot administrate. Use (ADW0021) 31
the “rg” command instead. Line <number> will not ADW0025 Cannot access network layer.
be processed. (ADM 00207) 28 (ADW0025) 31
ADM 00208 You do not have the rights to use C
personal data files. Please contact your Business CAT0001 The category name contains invalid
Objects supervisor. (ADM 00208) 29 characters. Valid characters are: (CAT0001) 41
ADM0012 Cannot connect to the universe Crystal Reports Crystal Reports error messages
domain. (ADM0012) 26 112
ADM0017 Too many candidates (ADM0017) 26
ADM0026 Unsupported RDBMS (ADM0026) 26
D
ADM0069 Parent class has changed. DA0005 Connection or SQL sentence error.
(ADM0069) 27 (DA0005) 35
ADM0070 Parent class definition is incorrect. DA0009 BLOB column cannot fetch more than
(ADM0070) 28 one row. (DA0009) 35
ADM0195 The current user cannot be found. DA0010 Some of the objects from the universe
Please contact your supervisor. (ADM0195) 28 are missing or ambiguous. You cannot run the
ADM0200 Cannot start agent UX. Contact query on this universe. (DA0010) 35
Business Objects Customer DMA0002 Bad hierarchy name (DMA0002) 65
Support. (ADM0200) 28 DMA0005 Export failed! (DMA0005) 65
ADM0201 Error during copy. Contact Business DMA0006 Editing this data provider requires an
Objects Customer Support. (ADM0201) 28 additional BusinessObjects component which has
ADW0002 Setup failed! (ADW0002) 29 not been installed on your computer. Please
ADW0011 Cannot create universe domain. contact your system administrator. (DMA0006) 66
(ADW0011) 29 DMA0007 The following data providers have not
ADW0012 Cannot find RSS file. (ADW0012) 29 been successfully refreshed (DMA0007) 66
ADW0013 Cannot find Repository section in DMA0008 A variable prevented the data
RSS file. (ADW0013) 30 provider from being refreshed. (DMA0008) 67
ADW0014 Cannot find Create section in RSS DPP0001 Cannot open file. (DPP0001) 67
file. (ADW0014) 30 DPP0002 You are not authorized to use this
ADW0015 Cannot find Table section in RSS file. stored procedure. (DPP0002) 67
(ADW0015) 30 DPQ0001 Connection is not defined.
(DPQ0001) 67

DPQ0003 The server is not responding! DX0022 You requested to export the secured
(DPQ0003) 68 file <document>. This action on the file is
DPQ0005 Connection problem (DPQ0005) 68 forbidden to you. The export was canceled for
DPQ0006 Does not exist. (DPQ0006) 68 <document>. (DX0022) 45
DPS0001 This stored procedure has been DX0024 Unknown error during export of
removed. (DPS0001) 69 <document>. Export stopped. <document> not
DPS0002 You are not allowed to use this stored exported. (DX0024) 45
procedure (DPS0002) 69 DX0025 Database error during export of
DWZ0001 The server is not responding. <document>. Export stopped. <document> not
(DWZ0001) 69 exported. (DX0025) 45
DX 00050 Document deletion failed. (DX 00050) DX0026 Break during export of <document>:
48, Try deleting the document again. If you Export has stopped. <document> is not exported.
receive the message again, try logging out and (DX0026) 46
logging back in and repeating the process. 48 DX0027 Cannot open file associated with
DX0001 Cannot generate temporary file. <document>. <document> not exported.
(DX0001) 41 (DX0027) 46
DX0002 The file will not be secured on your DX0037 Cannot load the dll. Check the
workstation. (DX0002) 41 Microsoft Exchange installation. (DX0037) 46
DX0003 RSS file not accessible. (DX0003) 41 DX0040 Cannot open file associated with
DX0004 Wrong SQL used. (DX0004) 42 <document>. (DX0040) 46
DX0005 Error during import. (DX0005) 42 DX0041 Cannot send the message. (DX0041)
DX0007 Error during import. (DX0007) 42 46
DX0009 Unknown error during import of DX0044 Unable to get the document's
<document>. Import canceled. <document> properties! (DX0044) 47
cannot be imported. (DX0009) 42 DX0045 Database error (DX0045) 47
DX0010 Unable to close <document>. Import DX0046 The document domain is not
canceled. <document> cannot be imported. responding! (DX0046) 47
(DX0010) 43 DX0047 You need a more recent version of
DX0011 Unable to create file associated with BusinessObjects to import this document.
<document>. Import canceled. <document> (DX0047) 47
cannot be imported. (DX0011) 43 E
DX0012 Unable to delete previous file. Import
EPM 00001 Cannot create query. (EPM 00001)
canceled. <document> cannot be imported.
117
(DX0012) 44
EPM 00002 DBDriver not set. (EPM 00002) 117
DX0014 Unable to write to <document>.
EPM 00003 Database type not found: %1. (EPM
Import canceled. <document> cannot be
00003) 117
imported. (DX0014) 44
EPM 00004 Could not communicate with Web
DX0017 The file cannot be deleted. (DX0017)
Intelligence. (EPM 00004) 117
44
EPM 00005 A problem occurred during attempt to
DX0018 The file name is not compliant with the
publish the document '%1' (%2). (EPM 00005)
platform you are working on. Change the name.
117
(DX0018) 45
EPM 00006 The model refreshed data cannot be
retrieved from the database properly. Contact
your Business Objects administrator. (EPM
00006) 118
6 Error Message Guide

EPM 10001 Could not retrieve user profile for filter EPM 30005 Error pushing universe '%1'. (EPM
'%1' equals to '%2'. (EPM 10001) 118 30005) 122
EPM 10002 Information on the selected subject EPM 30006 Universe not found. (EPM 30006) 123
area cannot be retrieved. Check the list definition. EPM 40001 Cannot get new task ID. (EPM 40001)
(EPM 10002) 118 123
EPM 10003 SQL cannot be generated for the EPM 60001 You are not a Set Analysis user.
selected objects. (EPM 10003) 118 (EPM 60001) 123
EPM 10004 No data to fetch. (EPM 10004) 119 G
EPM 10005 No count object exists in the subject
GUI0003 The file name contains forbidden
area %1. (EPM 10005) 119
characters. (GUI0003) 109
EPM 10006 No dimension object has been
GUI0005 File not found. Please verify the
defined in the universe as the subject key for the
correct file name was given. (GUI0005) 109
subject area %1. (EPM 10006) 119
GUI0006 <name> path not found. Please verify
EPM 10007 No IPDATE object exists in the
the correct path name was given. (GUI0006) 109
subject area %1. (EPM 10007) 119
EPM 10008 No IPFILTER object exists in the I
subject area %1. (EPM 10008) 120 IQ 00001 The question domain could not be
EPM 10009 More than one count object exists in loaded. (IQ 00001) 136
the subject area %1. (EPM 10009) 120 IQ 00002 The Question Engine server is
EPM 10010 More than one Subject Key object currently unavailable. (IQ 00002) 136
exists in the subject area %1. (EPM 10010) 120 IQ 00003 The question domain could not be
EPM 20001 Cannot parse analytic XML. (EPM loaded. (IQ 00003) 136
20001) 120 IQ 00004 The Question Engine server is
EPM 20002 Invalid analytic token. (EPM 20002) currently unavailable. (IQ 00004) 136
120 IQ 00005 The Question Engine is not running.
EPM 20003 Cannot find Pareto. (EPM 20003) 121 (IQ 00005) 136
EPM 20004 Cannot find the appropriate metric to IQ 00006 The question domain referenced
drill down. (EPM 20004) 121 <number> universe objects which could not be
EPM 20005 The system is unable to retrieve this found. (IQ 00006) 137
goal. (EPM 20005) 121 IQ 00007 A subject used by this question no
EPM 20006 Goal has expired. (EPM 20006) 121 longer exists. (IQ 00007) 137
EPM 20007 Cannot generate SQL. (EPM 20007) IQ 00008 Attribute <name> no longer exists. (IQ
121 00008) 137
EPM 20008 This link is unavailable. It is IQ 00009 A runtime error has occured. (IQ
impossible to contact the server. (EPM 20008) 00009) 137
121 IQ 00010 You must specify a label for this filter.
EPM 20009 Visual Data Query XML not found for (IQ 00010) 137
dimension. (EPM 20009) 122 IQ 00011 The label All is built-in and cannot be
EPM 30002 Error while attempting to link to redefined. (IQ 00011) 137
AARepoMgt.exe. (EPM 30002) 122 IQ 00012 Attribute does not have any values
EPM 30003 Repository Version Manager failed: selected. (IQ 00012) 137
%1. (EPM 30003) 122 IQ 00013 Favorite question must be given a
EPM 30004 Error while reading the parameter name. (IQ 00013) 137
'LastPushUnv' in the ci_param table. (EPM IQ 00014 IQ license key doesn’t exist. (IQ
30004) 122 00014) 138

IQ 00015 Couldn’t log on to Business Objects Q

Enterprise. (IQ 00015) 138 QP0001 Error during SQL generation.
IQ 00016 Couldn’t log on to Business Objects (QP0001) 70
Enterprise. (IQ 00016) 138 QP0002 Internal memory error during SQL
IQ 00017 Couldn’t log on to Business Objects generation. (QP0002) 70
Enterprise. (IQ 00017) 138 QP0003 Memory error during SQL generation.
IQ 00018 No universes have changed. (IQ (QP0003) 70
00018) 138 QP0004 Incompatible combination of objects.
IQ 00019 The question domain cannot be (QP0004) 70
exported because it is not yet complete. (IQ QP0005 Outer joins are incoherent. (QP0005)
00019) 138 70
IQ 00020 The question domain referenced QP0006 Cartesian product not allowed.
<number> universe objects which could not be (QP0006) 71
found. (IQ 00020) 138 QP0007 The query does not reference a table.
IQ 00022 Filter <name> does not exist (IQ (QP0007) 71
00022) 139 QP0008 There is a reference to a table that
IQ 00023 IFilter <name> does not exist (IQ has been deleted. (QP0008) 71
00023) 139 QP0009 One of the objects in the query is not
IQ 00024 A runtime error has occurred. (IQ valid. (QP0009) 71
00024) 139 QP0010 One of the properties in the query is
IQ 00025 An error has occurred. The subject not valid. (QP0010) 72
with ID <number> does not exist in the CMS or QP0011 The .PRM file cannot be found.
you don’t have the right to access it. (IQ 00025) (QP0011) 72
139 QP0013 The complex condition has created a
IQ00021 Filter <name> does not exist. (IQ Cartesian product. (QP0013) 72
00021) 139 QP0014 Loop in complex condition. (QP0014)
L 72
LOV0001 Too many selected values. QP0015 This query is too complex. One of the
(LOV0001) 109 subqueries contains incompatible objects.
LOV0002 You have not been authorized to use (QP0015) 73
this universe. (LOV0002) 109 QP0016 The server is not responding.
(QP0016) 73
P QP0017 Columns of the SELECT clause are
PT 00001 Unexpected command "{0}" different from the result objects. (QP0017) 73
encountered. (PT 00001) 127 QP0018 Syntax error in variable. (QP0018) 73
PT 00002 Invalid key code. (PT 00002) 127 QP0019 You are not authorized to use the
PT 00003 You do not have the required key object. (QP0019) 74
code to run Process Tracker. (PT 00003) 127 QP0020 Aggregate aware resolution failed.
PT 00004 Process Tracker is not configured for (QP0020) 74
this CMS. (PT 00004) 127 QP0021 Ambiguous condition on a measure.
PT 00005 An error has occurred, please contact Remove it or cancel your scope of analysis.
your system administrator and see the log for (QP0021) 75
more information. (PT 00005) 127 QP0022 You cannot create a new tab before
including at least one result object in this tab.
(QP0022) 75

QP0023 You cannot combine subqueries. STU 00008 You did not provide the CD
(QP0023) 75 <diskNumber>. (STU 00008) 19
QP0025 You cannot delete this query. You STU 00009 The distribution is already installed in
must delete the condition first. (QP0025) 75 this directory. (STU 00009) 19
QP0027 Some obsolete objects have been STU 00010 Your Business Objects server is still
removed from the query. (QP0027) 76 running. Stop it, then retry. (STU 00010) 19
QPF0001 The only authorized SQL command is STU 00015 You have logged in with a different
““Select”” (QPF0001) 69 user account than that used for the installation.
R (STU 00015) 19
STU 00019 Patch directory is not correct. (STU
RCT 00001 Unknown error (RCT 00001) 131
00019) 19
RCT 00002 Incorrect login or password (RCT
STU 00020 Temporary directory is not correct.
00002) 131
(STU 00020) 19
RCT 00003 Cannot open document (RCT 00003)
STU 00021 Installation directory is not correct.
131
(STU 00021) 20
RCT 00006 Error while loading XML description
STU 00023 Source directory is not correct. (STU
(RCT 00006) 131
00023) 20
RCT 00007 Error while saving XML description
STU 00024 Installation directory is needed. (STU
(RCT 00007) 131
00024) 20
RCT 00008 Some audit data cannot be added to
STU 00026 Source directory is needed. (STU
database (RCT 00008) 132
00026) 20
RCT 00009 Incorrect URL to portal (RCT 00009)
STU 00027 Unknown feature <feature>. (STU
132
00027) 20
RCT 00010 Error occurred while trying to access
STU 00028 Unknown language <language>.
portal (RCT 00010) 132
(STU 00028) 20
RCT 00012 Audit connection is not defined (RCT
STU 00029 Current language is not one of the
00012) 132
installed languages. (STU 00029) 20
RCT 00014 Publish failed (RCT 00014) 132
STU 00031 You do not have a license for this
RCT 00015 Error occurred while trying to start the
feature: <feature>. (STU 00031) 21
conversion engine (RCT 00015) 133
STU 00040 Feature <feature> is already installed.
S (STU 00040) 22
STU 00004 This Business Objects distribution is STU 00041 Feature <feature> is not installed.
for <OS name> not for <OS name>. (STU 00004) (STU 00041) 22
18 STU 00050 Impossible to create temporary file
STU 00005 This Business Objects distribution <file>. (STU 00050) 22
only supports Solaris 8. (STU 00005) 18, This STU 00051 Impossible to create <directory>.
Business Objects distribution only supports AIX 5. (STU 00051) 22
(STU 00005) 18, This Business Objects STU 00052 Impossible to copy files to
distribution only supports HP-UX 11. (STU 00005) <directory>. (STU 00052) 22
18 STU 00053 winstall has already been copied to
STU 00006 ProductID.txt file not found. (STU this directory. (STU 00053) 22
00006) 18 STU 00060 Not enough space in the disk. (STU
STU 00007 Impossible to retrieve files from 00060) 23
<directory>. (STU 00007) 18 STU 00070 This directory does not contain
Business Objects products. (STU 00070) 23

STU 00071 Your directory does not contain the UNV0017 The server is not responding.
correct Business Objects distribution. (STU (UNV0017) 38
00071) 23 UNV0035 This object already exists. (UNV0035)
STU 00072 Impossible to upgrade this installation 38
release. (STU 00072) 23 UNV0049 Strategy connection not found.
STU 00080 You can't install this patch on this (UNV0049) 38
version. (STU 00080) 23 USR0006 You are not authorized to use
STU 00081 The features you want to patch are Designer. (USR0006) 32
not installed. (STU 00081) 23 USU0001 Cannot find <name>. Please check
STU 00082 Patch <patchname> is already that all components have been correctly installed.
installed. (STU 00082) 24 (USU0001) 110
STU 00083 Patch <patchname> not found. (STU UX0001 The universe was exported but may
00083) 24 contain errors. Please refer to the designer of this
STU 00090 Patch <patchName> is not the most universe. (UX0001) 48
recent patch. Please remove patches in reverse UX0010 No universe domain is available.
installation order. (STU 00090) 24 Contact your supervisor for help. (UX0010) 48
STU 00091 This patch has not been installed. UX0011 The universe <universe> does not
(STU 00091) 24 exist in this universe domain. (UX0011) 48
STU 00092 Impossible to access UX0012 The file name <name> does not exist
<pathDirectory>. (STU 00092) 24 in your local folder. (UX0012) 48
U UX0013 Could not retrieve columns of
universe tables. The associated universe
UNM0001 May be inconsistent. (UNM0001) 35
connection is not valid. (UX0013) 49
UNM0002 Bad number format (UNM0002) 35
UX0015 The connection associated with the
UNM0003 Missing quote ""..."" (UNM0003) 36
universe has not been defined. You must create a
UNM0004 Missing double quote ""...""
connection. (UX0015) 49
(UNM0004) 36
UX0016 Could not update the connection
UNM0005 Missing closing bracket {...}
locally. (UX0016) 49
(UNM0005) 36
UX0023 Cannot open the universe. (UX0023)
UNM0006 Missing opening parenthesis after
49
function name (UNM0006) 36
UX0028 Cannot load the repository. (UX0028)
UNM0007 Missing closing parenthesis
50
(UNM0007) 36
UX0029 Cannot release the current repository.
UNM0008 Missing parameters (UNM0008) 36
(UX0029) 50
UNM0009 Wrong number of parameters
UX0032 The universe file name does not exist.
(UNM0009) 36
(UX0032) 50
UNM0010 Bad character (UNM0010) 37
UX0033 The universe domain does not exist.
UNM0011 Bad indent (UNM0011) 37
(UX0033) 50
UNM0012 Incompatible operand (UNM0012) 37
UX0034 The universe ID does not exist in the
UNM0013 Looping in variable definition
repository. (UX0034) 50
(UNM0013) 37
UX0036 The universe name does not exist.
UNM0014 Returns type incompatible with the
(UX0036) 51
user object type. (UNM0014) 37
UX0037 The repository is not responding!
UNM0015 Syntax error (UNM0015) 37
(UX0037) 51
UNM0016 Cannot create two user objects with
the same name. (UNM0016) 37

UX0038 The universe domain is not UX0062 Cannot begin transaction and export
responding! (UX0038) 51 <universe>. Problem with the security domain.
UX0039 The context name does not exist! (UX0062) 59
(UX0039) 51 UX0063 Cannot begin transaction and export
UX0040 The document domain does not exist <universe>. Problem with the document domain.
on the same data account. You cannot export (UX0063) 59
your lists of values. (UX0040) 52 UX0064 Cannot obtain information on
UX0041 The document domain account is previous <name>. (UX0064) 59
different. You cannot import your lists of values. UX0065 Cannot delete previous <name>.
(UX0041) 52 (UX0065) 60
UX0042 Cannot export the lists of values. UX0066 Cannot terminate transaction and
(UX0042) 53 export <universe>. Problem with the document
UX0043 Cannot update the lists of values in domain. (UX0066) 60
the universe domain. (UX0043) 53 UX0067 Cannot terminate transaction and
UX0044 Cannot import the lists of values. export <universe>. Problem with the security
(UX0044) 53 domain. (UX0067) 60
UX0045 Incremental export operations are not UX0068 Database error during export of the
available. Do you want to export the whole list of values file. (UX0068) 61
universe? (UX0045) 53 UX0069 Export of the lists of values
UX0046 Cannot lock the universe. (UX0046) interrupted. (UX0069) 61
54 UX0071 Universe already exists in the domain.
UX0047 Cannot save the universe. (UX0047) Do you want to overwrite it? (UX0071) 61
54 V
UX0048 Cannot delete previous <universe>.
VAR0001 Syntax error (VAR0001) 110
(UX0048) 54
VBA 00009 Error when trying to access VBA.
UX0049 <character> is replaced by
(VBA 00009) 76
<character>. (UX0049) 55
VBA 00010 Unable to edit the procedure. (VBA
UX0050 Cannot create destination folder or
00010) 76
universe file. (UX0050) 55
VBA 00011 Unable to create the procedure. (VBA
UX0051 Database error (UX0051) 55
00011) 76
UX0052 Unable to create the list of values file.
VBA 00012 You must select a procedure in the
(UX0052) 56
list. (VBA 00012) 76
UX0053 Cannot open the list of values file.
VBA 00013 Unable to delete the procedure. (VBA
(UX0053) 56
00013) 76
UX0054 Cannot close the list of values file.
(UX0054) 56 W
UX0055 Unable to delete the previous lists of WIH 00001 Invalid block definition. (WIH 00001)
values file. (UX0055) 57 79
UX0057 Unable to write to the list of values file. WIH 00002 This object has already been inserted.
(UX0057) 57 (WIH 00002) 79
UX0058 Unable to get data from the lists of WIH 00003 This filter has already been inserted.
values file. (UX0058) 58 (WIH 00003) 79
UX0059 RSS file not accessible. (UX0059) 58 WIH 00004 This document includes advanced
UX0060 Incorrect SQL used. (UX0060) 58 formatting that requires the Java Report Panel.
UX0061 Not enough memory. (UX0061) 58 (WIH 00004) 79

WIH 00005 Cannot insert measures on the X- WIJ 20001 An unexpected problem occurred
Axis. (WIH 00005) 80 when Web Intelligence tried to refresh the
WIH 00006 Cannot insert dimensions or details document data and open the document. The data
on the Y-Axis. (WIH 00006) 80 source has been modified or deleted, or a prompt
WIH 00007 Cannot insert measures on the Z- on the document has no value selected. (WIJ
Axis. (WIH 00007) 80 20001) 83
WIH 00008 You must insert a result object before WIJ 20002 The Web Intelligence Java Report
choosing another tab. (WIH 00008) 80 Panel cannot connect to the server. Close the
WIH 00009 You cannot create a section using a report panel and try to connect again or see your
measure. (WIH 00009) 80 BusinessObjects administrator. (WIJ 20002) 84
WIH 00010 You cannot insert dimension or detail WIJ 20003 Unable to retrieve the first page of the
objects on the Z-axis of this type of chart. (WIH current report. Check the report for errors or
00010) 80 contact your administrator. The report panel will
WIH 00011 You cannot insert dimension or detail switch to Structure View. (WIJ 20003) 84
objects on the X-axis of this type of chart. (WIH WIJ 30000 The query in this document is empty.
00011) 80 Check that the Result Objects pane on the query
WIH 00012 Report names cannot be blank. Close tab or view includes objects before running the
this dialog box and then enter a name for the query. (WIJ 30000) 84
report. (WIH 00012) 81 WIJ 30001 At least one query in this document is
WIJ 10000 You need to use the Formula Editor to empty. Check that the Result Objects pane
create a correctly formed formula. (WIJ 10000) 82 includes objects before running the queries. (WIJ
WIJ 10001 You cannot create a variable that has 30001) 84
the same name as an existing document object. WIJ 30003 Out of memory. Reduce the browser
Give the new variable a different name. (WIJ window size or re-launch the report panel. (WIJ
10001) 82 30003) 85
WIJ 10500 You cannot position this report WIJ 40001 Your user profile does not allow you to
component in relation to a block, cell, or section save personal or corporate documents. See your
that is positioned relative to this report Business Objects administrator. (WIJ 40001) 85
component. Select a different block, cell, or WIJ 44444 An unexpected error occurred.
section in the "Relative to...of:" dropdown list or Contact your administrator with details of the
unselect the "Relative to:" option. (WIJ 10500) 82 actions you performed before the error occurred.
WIJ 11111 The Web Intelligence Java Report (WIJ 44444) 85
Panel requires Java Runtime Environment (JRE) WIJ 55555 The information sent to the server
1.4.2_01 to run on your computer. The JRE contains invalid character(s). Use the Undo button
currently installed is {0}. Either contact your to cancel the latest changes to the document and
administrator to upgrade to 1.4.2_01 or select the then retry. (WIJ 55555) 85
[default VM] entry in the [Java Plug-in Control WIJ 77777 Web Intelligence cannot retrieve this
Panel], if you already have the required version document due to a server problem or an error in
installed. (WIJ 11111) 83 the document structure. See your
WIJ 20000 An error occurred while the document BusinessObjects administrator. (WIJ 77777) 86
was being decoded. Try to open the document in WIJ 77778 Your Web Intelligence WIQT session
InfoView. If this doesn't work, see your has reached timeout. Log out and log in again to
BusinessObjects administrator. (WIJ 20000) 83 InfoView. (WIJ 77778) 86

WIS 00001 Some objects are no longer available WIS 00015 Multiple query filters contain a prompt
in the universe. See your BusinessObjects with the same text, but the prompts use a different
administrator. (WIS 00001) 87 operand type or operator count of values. (WIS
WIS 00002 Some objects are not available to 00015) 90
your user profile. You cannot refresh this WIS 00016 The query contains an @Script()
document. See your BusinessObjects function, which is not supported. See your
administrator. (WIS 00002) 87 BusinessObjects administrator. (WIS 00016) 92
WIS 00003 Some predefined filters are no longer WIS 00017 The following objects cannot be used
available in the universe. See your as result objects: {obj_list}. See your
BusinessObjects administrator. (WIS 00003) 87 BusinessObjects administrator. (WIS 00017) 92
WIS 00004 Some database tables are no longer WIS 00018 The following objects cannot be used
available in the universe. See your in query filters: {obj_list}. See your
BusinessObjects administrator. (WIS 00004) 87 BusinessObjects administrator. (WIS00018) 92
WIS 00005 Invalid Prompt definition. See your WIS 00501 Universe not found. See your
BusinessObjects administrator. BusinessObjects administrator. (WIS 00501) 92
(WIS 00005) 87 WIS 00502 User rights not found. See your
WIS 00006 Invalid Aggregate Aware definition. BusinessObjects administrator. (WIS 00502) 93
See your BusinessObjects administrator. (WIS WIS 00503 You are not authorized to access the
00006) 88 universe {unv_name}. See your BusinessObjects
WIS 00007 A filter contains a wrong value. You administrator. (WIS 00503) 93
cannot run this query. (WIS 00007) 88 WIS 10001 Syntax error in formula at position {n}.
WIS 00008 The query cannot run because it (WIS 10001) 93
contains incompatible objects. See your WIS 10005 The object name {object} at position
BusinessObjects administrator. (WIS 00008) 88 {n} is not unique in the report. Use the fully-
WIS 00009 The query cannot run because an qualified object name. (WIS 10005) 93
advanced filter contains an incompatible object. WIS 10006 The object {object} at position {n}
See your BusinessObjects administrator. (WIS does not exist in the report. (WIS 10006) 93
00009) 88 WIS 10012 The integer number {number} at
WIS 00010 The universe does not allow using a position {n} has a format that is incompatible with
complex expression in a GROUP BY statement. your regional settings. (WIS 10012) 93
You cannot run this query. See your WIS 10014 The real number {number} at position
BusinessObjects administrator. (WIS 00010) 88 {n} has a format that is incompatible with your
WIS 00011 The object(s): {obj list} contain regional settings. (WIS 10014) 94
multiple attributes. This syntax is no longer WIS 10016 A closing quotation mark does not
supported in this version. See your appear in the formula after the quotation mark
BusinessObjects administrator. before {formula_part} at position {n}. (WIS 10016)
(WIS 00011) 89 94
WIS 00012 You cannot run this query as it will WIS 10019 The object name {object} at position
produce a Cartesian product. See your {n} is ambiguous. Use the fully-qualified object
BusinessObjects administrator. (WIS 00012) 89 name. (WIS 10019) 94
WIS 00013 SQL generation failed. See your WIS 10033 The variable {variable name} cannot
BusinessObjects administrator. (WIS 00013) 90 be deleted because it has dependent formulas or
WIS 00014 Incompatible combination of objects. variables linked to {variable name}. (WIS 10033)
See your BusinessObjects administrator. (WIS 94
00014) 90

WIS 10034 There is already a variable called WIS 30000 The query in this document is empty.
{variable}. Choose another variable name. (WIS Check that the Result Objects pane on the query
10034) 94 tab includes objects before running the query.
WIS 10035 The date/time format {datetime} at (WIS 30000) 97
position {n} is not valid. Specify a valid date/time WIS 30001 At least one query in this document is
format. (WIS 10035) 94 empty. Check that the Result Objects pane on
WIS 10036 The expression/sub-expression at each query tab includes objects before running
position {n} is not valid. Specify a valid expression. the queries.
(WIS 10036) 95 (WIS 30001) 97
WIS 10037 The expression/sub-expression at WIS 30251 Your security profile does not include
position {n} uses an invalid data type. Specify a permission to edit the queries in Web Intelligence
valid data type. (WIS 10037) 95 documents. (WIS 30251) 98
WIS 10038 Invalid character {character} in WIS 30252 Your security profile does not include
variable name at position {n}. Specify a valid permission to edit Web Intelligence documents.
character. (WIS 10038) 95 (WIS 30252) 98
WIS 10039 The context you specified for the WIS 30253 Your security profile does not include
measure {measure} at position {n} is not valid. permission to refresh Web Intelligence
Specify a different context. (WIS 10039) 95 documents. (WIS 30253) 98
WIS 10040 The formula for variable {variable} WIS 30254 Your security profile does not include
contains a reference to a variable with the same permission to refresh lists of
short name. You must use the fully-qualified values. (WIS 30254) 98
variable name in the formula to remove this WIS 30255 Your security profile does not include
ambiguity. (WIS 10040) 95 permission to use lists of
WIS 10041 Incorrect use of multiple comparison values. (WIS 30255) 98
operators at position {n}. (WIS 10041) 95 WIS 30256 Your security profile does not include
WIS 10042 There is a circular reference because permission to view the SQL generated by the
the formula for variable {variable_name} query. (WIS 30256) 99
references a variable whose formula references WIS 30257 Your security profile does not include
{variable_name}. (WIS 10042) 95 permission to use the Web Intelligence formula
WIS 10701 Your Database server does not language. (WIS 30257) 99
support the Both and Except operators. Redefine WIS 30258 Your security profile does not include
your filters using different operators and then run permission to perform drill analysis. (WIS 30258)
the query again. (WIS 10701) 96 99
WIS 10702 A filter is defined on an object that is WIS 30259 Your security profile does not include
incompatible with all the objects selected on the permission to extend the scope of analysis. (WIS
Result Objects pane. Remove the filter from the 30259) 99
Query Filters pane or remove the objects from the WIS 30270 An internal error occurred while
Result Objects pane. calling the {api_name} API. (WIS 30270) 100
(WIS 10702) 96 WIS 30271 Max binary file size limit exceeded.
WIS 10801 Your security level does not allow you The document is too large to be processed by the
to refresh this document. Contact your Business server. Contact your BusinessObjects
Objects administrator. (WIS 10801) 96 administrator.
WIS 10901 Database error: {error_db}. Contact (WIS 30271) 101
your administrator or database supplier for more
information. (WIS 10901) 97

WIS 30272 Max character file size limit exceeded. WIS 30752 The XML file for this document cannot
The document is too large to be processed by the be opened. Contact your BusinessObjects
server. Contact your BusinessObjects administrator. (WIS 30752) 104
administrator. WIS 30753 An error occurred while parsing the
(WIS 30272) 101 Web Intelligence XML document. Contact your
WIS 30351 Web Intelligence cannot complete the BusinessObjects administrator. (WIS 30753) 104
steps necessary to build the query or generate the WIS 30761 The Web Intelligence 2.x document
report, due to missing or invalid information could not be migrated. (WIS 30761) 105
concerning the data source or query definition. WIS 30762 This document cannot be migrated.
Contact your BusinessObjects administrator. The query and report of the original Web
(WIS 30351) 101 Intelligence 2.x document are not synchronized.
WIS 30371 A query with this name already exists. Try to refresh and save the original document;
Rename this query. (WIS 30371) 102 then attempt migration again. (WIS 30762) 105
WIS 30381 You cannot edit this document, WIS 30763 The Web Intelligence 2.x document
because the query property option "Allow other could not be migrated, because the WIQT module
users to edit the query" was not enabled when the returned an error. Contact your administrator.
document was created. (WIS 30381) 102 (WIS 30763) 105
WIS 30551 An internal error has been generated WIS 40000 Your user profile does not provide you
by the WIQT. Contact your BusinessObjects with access to a document domain to save
administrator. (WIS 30551) 102 corporate documents. Save this document as a
WIS 30553 Your Web Intelligence WIQT session personal document or contact your Business
has reached timeout. Log out and log in again to Objects administrator. (WIS 40000) 106
InfoView. (WIS 30553) 102
WIS 30554 No more WIQT servers are available.
The maximum number of concurrent users is
already logged into Web Intelligence. (WIS
30554) 103
WIS 30555 Your security profile does not include
permission to save documents as corporate
documents or to send documents via InfoView.
(WIS 30555) 103
WIS 30556 A Corporate document with this name
already exists. Your security profile does not
include permission to delete corporate documents
created by other users. (WIS 30556) 103
WIS 30557 There is no document with this name
in InfoView. Specify a different document name.
(WIS 30557) 103
WIS 30650 Web Intelligence cannot perform the
intended action on this document.
(WIS 30650) 104
WIS 30751 The Web Intelligence server failed to
load the XML document. Contact your
BusinessObjects administrator. (WIS 30751) 104


Error Message Guide
Setup Error Messages
chapter
1 Setup Error Messages
Setup error messages

Setup error messages include the following ranges and categories:
Range Category
STU 00004 - STU 00092 UNIX Setup
STW 10000 Windows Setup
This Business Objects distribution is for <OS name> not for <OS name>.
(STU 00004)
Cause You have tried to install a distribution on a system other than the one for
which it was intended.
Action Install the correct version for your platform.
This Business Objects distribution only supports Solaris 8. (STU 00005)

Cause The version of the operating system you are running is not the correct one.
This distribution only runs on Solaris 8.
Action Install your distribution on a Solaris 8 platform.
This Business Objects distribution only supports AIX 5. (STU 00005)

This distribution only runs on AIX 5.
Action Install your distribution on a AIX 5 platform.
This Business Objects distribution only supports HP-UX 11. (STU 00005)
This distribution only runs on HP-UX 11.
Action Install your distribution on a HP-UX 11 platform.
ProductID.txt file not found. (STU 00006)

Cause The mounted source does not contain a Business Objects CD.
Action Make sure the CD you have mounted is a Business Objects CD.
Impossible to retrieve files from <directory>. (STU 00007)

Cause The installer cannot find the distribution packages or is unable to decompress
them.
Action Make sure you the CD you have provided is a Business Objects CD.

1
If all the CDs have been copied in a directory on a disk and you are running
the installation from this directory, make sure that all the CDs have been
correctly copied and that you have read permission for this directory.
You did not provide the CD <diskNumber>. (STU 00008)

Cause When you install the distribution from the command line, you need to insert
each CD one after the other. You did not give them in correct order.
Action Insert each CD in the correct order.
The distribution is already installed in this directory. (STU 00009)

Cause The directory you have specified already contains a Business Objects
distribution.
Action Choose another directory or remove the previous distribution.
Your Business Objects server is still running. Stop it, then retry. (STU 00010)
Cause It is not possible to change installation options while the server is running.
Action Stop the system, then try again.
You have logged in with a different user account than that used for the
installation. (STU 00015)
Cause You cannot perform the operation on the installation directory since you
logged in using a different user account than the one used for the installation.
Action Log out, then log in again using the user account used for the installation.
Patch directory is not correct. (STU 00019)

Cause The patch directory syntax is incorrect. It may be a relative path, or it may
contain spaces or unsupported characters.
Action Enter a valid absolute directory for the patch directory that does not contain
any of the following characters: [space], '#" or '$'.
Temporary directory is not correct. (STU 00020)

Cause The temporary directory syntax is incorrect. It may be a relative path, or it may
Action Enter a valid absolute directory for the temporary directory that does not
contain any of the following characters: [space], '#" or '$'.

Installation directory is not correct. (STU 00021)

Cause The installation directory syntax is incorrect. It may be a relative path, or it
may contain spaces or unsupported characters.
Action Enter a valid absolute directory for the installation directory that does not
contain any of the following characters: [space], '#" or '$'.
Source directory is not correct. (STU 00023)

Cause The source directory syntax is incorrect. It may be a relative path, or it may
Action Enter a valid absolute directory for the source directory that does not contain
any of the following characters: [space], '#" or '$'.
Installation directory is needed. (STU 00024)

Cause You have not specified the installation directory.
Action Use the -i parameter to specify the installation directory.
Source directory is needed. (STU 00026)

Cause When you retrieve packages from the Business Objects CD, you need to
specify the source directory.
Action Use the -s parameter to specify the source directory.
Unknown feature <feature>. (STU 00027)

Cause The feature you specified is not available in this distribution.
Action Check that you spelled the name of the feature correctly.
Check that the distribution contains this feature. A list of features that the
distribution contains may be found in the CD/setup/mymenu.xml file.
Unknown language <language>. (STU 00028)

Cause The language you specified is not available in this distribution.
Action Check that you spelled the name of the language correctly.
Check that the distribution contains this language. A list of languages that the
distribution contains can be found in the CD/setup/lang.dat file.
Current language is not one of the installed languages. (STU 00029)

Cause The language you specified as the current language is not available in this
distribution or will not be installed.
Action Check that you spelled the name of the language correctly.

1
Check that the distribution contains this language. Check that the language
will be installed. If not, install it.
You do not have a license for this feature: <feature>. (STU 00031)
Cause Your license is not valid for the feature you tried to install.
Action You can choose not to install the feature, or you can request a license that
covers this feature.
You should also check that you have read permission for these files.
Request valid licenses from Business Objects Support.

Feature <feature> is already installed. (STU 00040)

Cause The feature you want to add to the current installation is already installed.
Action Remove the name of this feature from the command line.
Feature <feature> is not installed. (STU 00041)

Cause The feature you want to remove from the current installation is not installed.
Action Remove the name of this feature from the command line.
Impossible to create temporary file <file>. (STU 00050)

Cause When you run winstall or wmodify, these scripts need to create temporary files
in the /tmp directory. If the disk is full, or if you do not have write access to the
temporary directory, you cannot create the files you need.
Action If the /tmp directory is not empty, delete some files to free up the space you
need.
If you are not allowed to create files in the /tmp directory, change your
permissions for this directory.
Impossible to create <directory>. (STU 00051)

Cause You are not allowed to create the directory.
Action Make sure you have the right permissions to create a directory. If not, change
your permissions for the parent directory or install the distribution in another
directory.
Impossible to copy files to <directory>. (STU 00052)

Cause You are not allowed to write files in the installation directory.
Action Make sure you have the right permissions to write files in this directory. If not,
change your permissions for this directory or install the distribution in another
directory.
winstall has already been copied to this directory. (STU 00053)

Cause You tried to copy winstall to a directory where it has already been copied.
To avoid possible incompatibilities between different versions of installer,
winstall prevents you from using a directory where a bootstrap installer is
already copied.
Action Delete the previous version of winstall, or copy the new version to a
different directory.

1
Not enough space in the disk. (STU 00060)
Cause The total size of files to install exceeds the available space on the disk.
Action Install fewer features or languages, or free up some disk space. You can also
specify another directory to install the files on another disk.
This directory does not contain Business Objects products. (STU 00070)
Cause Your installation directory does not contain Business Objects products.
Action Specify a directory that already contains Business Objects products.
Your directory does not contain the correct Business Objects distribution.
(STU 00071)
Cause Your Service Pack or your patch is not intended for the Business Objects
distribution contained in the specified installation directory.
Action Specify a directory that contains the correct Business Objects distribution.
Impossible to upgrade this installation release. (STU 00072)

Cause You tried to upgrade your installation, but your current version is more recent
than the Service Pack you tried to install.
Action Retrieve the most recent Service Pack distribution to upgrade your current
installation.
If you want to install an older Service Pack, you must perform a new
installation in another location.
You can't install this patch on this version. (STU 00080)

Cause You tried to install a patch that is not intended for this version.
Action If your patch is intended for a lower release, you don't need to install it. Its
content is already included in the release you have installed.
Otherwise, upgrade your installation to the release for which your patch is
intended, then install the patch.
The features you want to patch are not installed. (STU 00081)
Cause The patch cannot be installed because none of the features it covers are
installed.
Action If you still want to install this feature, you must first install the features it
covers by using the wmodify command.

Patch <patchname> is already installed. (STU 00082)

Cause You tried to install a patch that is already installed.
Action Check that the patch is indeed installed.
Patch <patchname> not found. (STU 00083)

Cause You tried to install a patch that cannot be found in the patch directory.
Action Make sure your patch source directory contains this patch. Check that you
typed the patch name correctly.
Patch <patchName> is not the most recent patch. Please remove patches in
reverse installation order. (STU 00090)
Cause The patch you tried to remove is not the most recent one installed.
Action Remove the most recent patches in reverse order.
The error message gives the command you must run from the command line
to remove the other patches.
This patch has not been installed. (STU 00091)

Cause The installation has not been patched with the patch.
Action Type a valid patch name.
Impossible to access <pathDirectory>. (STU 00092)

Cause The save directory <pathDirectory> that must contain the files to restore does
not exist or is not accessible. It is impossible to remove your patch.
Action Reinstall your installation.

Error Message Guide
Administration & Security

Error Messages
chapter
2 Administration & Security Error Messages
Administration & Security error messages

Administration error messages include the following ranges and categories:
Range Category
ADM0012 - ADM 00208 Administration errors
ADW0002 - ADW0025 Administration Wizard errors
USR0006 Security
Cannot connect to the universe domain. (ADM0012)

Cause You cannot make a connection to the universe domain, either because there
is no network connection, or the server on which the universe domain is
located is down.
Action Verify the network connection by “pinging” the server. If the network is running
properly, the database administrator should then use database middleware
(such as Net8 for Oracle) to check if there is any response from the repository
database.
Too many candidates (ADM0017)

Cause You tried to create or import a universe with too many loops, or a universe
which endlessly loops between two or more tables.
Action The universe designer should run an Integrity Check on the universe to locate
and fix the problem. The designer can then save and reexport the universe to
the repository.
Unsupported RDBMS (ADM0026)

Cause The installation of your ODBC databases is not correct, or the .sbo file has
been changed or damaged. Each of the databases you are using has an
associated .sbo file.
The above error message is generated if you try to access your data
warehouse via the repository after the associated database .sbo file has been
moved, renamed, deleted, or damaged. This message can also occur if the
.sbo is locked by another application or user.
Action Run Setup and reinstall your ODBC connections (which you can find in the
Data Access folder). This reinstalls the Odbc.sbo file.
Example The name of the .sbo file for ODBC databases is Odbc.sbo.

Administration & Security Error Messages
2
Parent class has changed. (ADM0069)
Cause One of the database objects you are trying to access belongs to a class
whose name has been changed.
Action Ask the universe designer to fix the parent class definition, and to reexport the
universe to the repository.

Parent class definition is incorrect. (ADM0070)

Cause One of the database objects you are trying to access belongs to a class which
has an invalid name. Class names must be unique within a universe, and
must not exceed 35 alphanumeric characters.
Action Ask the universe designer to fix the parent class definition, and to reexport the
universe to the repository.
The current user cannot be found. Please contact your supervisor.

(ADM0195)
Cause While you were logged into a BusinessObjects session, your user ID was
deleted from the repository by the supervisor.
Action The supervisor must first recreate your user ID before you can continue
working with BusinessObjects.
Cannot start agent UX. Contact Business Objects Customer

Support. (ADM0200)
Cause A required .dll file has been deleted or damaged.
Action Reinstall Designer.
Error during copy. Contact Business Objects Customer Support. (ADM0201)

Cause This error message may occur when you import data to the repository. It
indicates that one or more tables of the repository are corrupted.
Action Contact Business Objects Customer Support.
You do not have the rights to use personal data files. Please contact your
Business Objects supervisor. (ADM 00207)
Cause You do not have the proper rights to use personal data files.
Action Contact your Business Objects supervisor.
You are not authorized to delete a user who also belongs to at least one
group that you cannot administrate. Use the “rg” command instead. Line
<number> will not be processed. (ADM 00207)
Cause The batch import file includes a DU command (Delete User). This would
delete all instances of the user from the repository. However, at least one
instance of the user belongs to a group which you do not have the right to
administrate, so you are not authorized to use the DU command for this user.
Action To remove the user from the group you are authorized to administrate, use
the RG command (Remove from Group) instead.

2
You do not have the rights to use personal data files. Please contact your
Business Objects supervisor. (ADM 00208)
Cause You tried to use personal data files for which you do not have the correct
rights.
Action Contact your Business Objects supevisor to get the correct rights.
Setup failed! (ADW0002)

Cause BusinessObjects must create a temporary folder during installation. This
folder is deleted when the installation is finished. However, the disk is full.
Action Empty your Recycle Bin. If necessary, delete any redundant or unwanted
files, and empty the Recycle Bin again.
Cause You have read-only privileges to the root C:\ drive.
Action The system or network administrator can grant you Change or Full Control
privileges on the C:\ root drive.
Cannot create universe domain. (ADW0011)

Cause You tried to create a universe domain, but the system on which you want the
domain to reside cannot be reached. Either the node is not running, or the
network connection is down.
database.
Cannot find RSS file. (ADW0012)

Cause A .rss file is associated with each of the databases that you are using. These
files are located in the associated database folders.
You may receive the above error message if BusinessObjects tries to access
one of these databases after the associated .rss file has been deleted or
corrupted.
Action You need to replace the deleted or corrupted .rss file with a clean copy of the
file, either from another BusinessObjects installation, or with one provided by
Business Objects Customer Support.

Cannot find Repository section in RSS file. (ADW0013)

You receive the above error message if BusinessObjects tries to access the
Repository section in one of these database .rss files after this section of the
file has been corrupted.
Action You need to replace the corrupted .rss file with a clean copy of the file, either
from another BusinessObjects installation, or with one provided by Business
Objects Customer Support.
Cannot find Create section in RSS file. (ADW0014)

Cause An .rss file is associated with each of the databases that you are using. These
the Create section in one of these database .rss files after this section of the
Cannot find Table section in RSS file. (ADW0015)

Cause An .rss file is associated with each of the databases that you are using. These
the Table section in one of these database .rss files after this section of the file
has been corrupted.
Cannot find Index section in RSS file. (ADW0016)

the Index section in one of these database .rss files after this section of the

2
Cannot find Insert section in RSS file. (ADW0017)
the Insert section in one of these database .rss files after this section of the file
has been corrupted.
Cannot create document domain. (ADW0019)

Cause The disk is full.
Action Empty your Recycle Bin. If necessary, delete any redundant or unwanted files,
and empty the Recycle Bin again.
Cause You have read-only privileges to the root C:\ drive.
Action The system or network administrator can grant you Change or Full Control
privileges on the C:\ root drive.
Cause You are trying to create the document domain on another machine (cluster
node), but either the machine is down, or the connection is not working
correctly.
Action “Ping” the machine to see if the network connection is valid.
Cannot find the external script. (ADW0021)

Cause You are trying to use an external SQL script in order to create a customized
repository. However, BusinessObjects does not have the correct pathname to
the script.
Action Check the pathname to the script file, and correct it.
Cannot access network layer. (ADW0025)

Cause The error occurs when you try to launch a Business Objects product and
connect to the repository, while the middleware that allows all clients to access
the database is not properly installed.
Action Check your middleware installation:
• When you install BusinessObjects, make sure that the
BusinessObjects-RDBMS access is checked.
• At the end of the setup, check the middleware.
• Check in the AUTOEXEC.BAT file that the database environment path is
correct. It should be something like [Local drive]\Orawin\bin.

You are not authorized to use Designer. (USR0006)

Cause You tried to start Designer, but do not have the necessary authorization
(i.e., you do not have a designer user profile).
Action A supervisor can change your user profile to designer (or supervisor-
designer).

Error Message Guide
Universe Error Messages
chapter
3 Universe Error Messages
Universe error messages

Universe error messages include the following ranges and categories:
Range Category
DA0005 - DA0010 Database errors
UNM0001 - UNM0016 Universe management errors
UNV0017 - UNV0049 Universe errors

3
Connection or SQL sentence error. (DA0005)
Cause You may get a connection or SQL sentence error after changing the date
format in the sbo file.
Action Verify that the Oracle NLS_DATE_FORMAT parameter is set to the date
format that you have set in the sbo file. Check your Oracle documentation for
more information.
Cause Your ODBC drivers have been moved, deleted, renamed, or damaged.
Action Install the Microsoft ODBC driver again.
BLOB column cannot fetch more than one row. (DA0009)

Cause Your corporate database does not support the retrieval of Binary Large
Objects (BLOBs) which extend beyond a single row.
Some of the objects from the universe are missing or ambiguous. You
cannot run the query on this universe. (DA0010)
Cause This message is displayed whenever you try to run a query on a universe
which has missing objects.
Action Delete the objects from the report that seem to be missing. You can check
which objects they are in the Details tab of the error message. Then change
the objects in the query from Data > View Data.
May be inconsistent. (UNM0001)

Cause The universe may contain:
• Invalid syntax in the SQL definition of an object, condition, or join
• Loops
• Isolated tables
• Missing or incorrect cardinalities.
Action Run an Integrity Check on the universe. This checks whether the structure of
your universe matches the requirements of the database.
Bad number format (UNM0002)

Cause There is a syntax error in the SQL formula you entered. The number format is
incorrect.
Action Reenter the number, and resubmit the formula.

Missing quote ""..."" (UNM0003)

Cause There is a syntax error in the SQL formula you entered. The formula lacks a
single quotation mark.
Action Enter the missing single quote, and resubmit the formula.
Missing double quote ""..."" (UNM0004)

double quotation mark.
Action Enter the missing double quote, and resubmit the formula.
Missing closing bracket {...} (UNM0005)

closing bracket.
Action Enter the missing closing bracket, and resubmit the formula.
Missing opening parenthesis after function name (UNM0006)

Cause There is a syntax error in the SQL formula you entered. The formula lacks an
opening parenthesis.
Action Enter the missing opening parenthesis, and resubmit the formula.
Missing closing parenthesis (UNM0007)

closing parenthesis.
Action Enter the missing closing parenthesis, and resubmit the formula.
Missing parameters (UNM0008)

Cause There is a syntax error in the SQL formula you entered. The formula lacks
one or more parameters.
Action Enter the missing parameters, and resubmit the formula.
Wrong number of parameters (UNM0009)

Cause There is a syntax error in the SQL formula you entered. The formula may
either lack one or more parameters or have too many parameters.
Action Enter the correct number of parameters, and resubmit the formula.

3
Bad character (UNM0010)
Cause There is a syntax error in the SQL formula you entered. You included an
unauthorized character in one of the field statements.
Action Check and correct the syntax. Then resubmit the formula.
Bad indent (UNM0011)

illegal indent in one of the field statements.
Incompatible operand (UNM0012)

operand that is not compatible with the current SQL function.
Action Check and correct the SQL. Then resubmit the formula.
Looping in variable definition (UNM0013)

Cause There is a syntax error in the SQL formula you entered. You included a loop
which cannot be resolved.
Returns type incompatible with the user object type. (UNM0014)

Cause There is a syntax error in the SQL formula you entered. There are
inconsistencies in the User Object Definition.
Syntax error (UNM0015)

Cause This error message appears when special characters are used in object
names, including:
[]=&@×$%,;!ß£~§µ+'(){}-
Action Do not use special characters in object names.
Cannot create two user objects with the same name. (UNM0016)
Cause You tried to create a user object with a name that is already assigned to
another user object.
Action Choose a unique name for the user object. Then resubmit the formula.

The server is not responding. (UNV0017)

Cause This message may occur when you try to access the database (to “ping” a
connection, refresh the structure of the universe, or refresh a document).
database.
This object already exists. (UNV0035)

Cause The object that you are trying to create already exists in the class. Objects
must have unique names within the same class.
Action Rename the existing object, or give the new object another name. If you
change the name of an existing object, documents using this object may not
refresh correctly.
Strategy connection not found. (UNV0049)

Cause This message may be displayed when an external object strategy is used to
access the repository.
Action The connection referenced in the [CONNECTION] section of the .PRM file
must be defined as a personal connection. If it is defined as a secured
connection, it will not work. This is because this connection enables you to
access every metadata structure, and might not be available for all other
users.
Note: External strategy files are declared in the .PRM files located in the
various subfolders of:
$INSTALLDIR\dataAccess\RDBMS\legacy\<database name>

Error Message Guide
Document and Universe

Exchange Error Messages
chapter
4 Document and Universe Exchange Error Messages
Document and Universe Exchange error

messages
Document and universe exchange error messages include the following
ranges and categories:
Range Category
CAT0001 Category errors
DX0001 - DX 00050 Document Exchange errors
UX0001 - UX0071 Universe Exchange errors

Document and Universe Exchange Error Messages
4
The category name contains invalid characters. Valid characters are:
(CAT0001)
Cause You tried to name a new category, using unauthorized characters.
Action Reenter the category name, using only valid characters. Valid characters
include: a-z A-Z 0-9 \- _ $ , and Space (except at the beginning).
Cannot generate temporary file. (DX0001)

Cause You tried to send a document to the repository. However, BusinessObjects
always temporarily saves files locally to disk before sending them to the
repository. These temporary files are stored in the folder:
My Documents\BusinessObjects Documents\UserDocs
Either you do not have write-access to the disk, or the disk is full.
files, and empty the Recycle Bin again. If you have read-only privileges on the
root C:\ drive, the system or network administrator can grant you full access
privileges on the drive.
The file will not be secured on your workstation. (DX0002)

Cause You tried to publish a document to corporate documents before saving it. In
order to secure the local version of this document, you must first save it.
Otherwise, any security restrictions placed on the document in the repository
would not apply to the document on the file system until it is overwritten by the
version in the repository.
Action Save the local version of this document before publishing it.
RSS file not accessible. (DX0003)

Cause This error can occur when security domain tables are shifted to a different
database. As a result, the Connection parameters of the universe are no
longer valid
Action A designer can restore the connection as follows:
1. Create a new connection (Tools > Connections) for the universe.
2. Assign the connection to the universe (File > Parameters).
3. Save the universe.
4. Reexport the universe to the repository (File > Export).

Wrong SQL used. (DX0004)

Cause BusinessObjects has encountered an exceptional error while attempting to
access your corporate database.
Error during import. (DX0005)

Cause An error occurred while you were retrieving a document from the repository.
The import was aborted for one of the following reasons:
• There was a network error.
• The server which hosts the document domain has failed.
Action Verify the network connection by “pinging” the server hosting the repository. If
the network is running properly, the database administrator should then use
database middleware (such as Net8 for Oracle) to check if there is any
response from the repository database.
Error during import. (DX0007)

Cause An error occurred while you were retrieving a document from the repository.
The import was aborted for one of the following reasons:
• There was a network error.
• The server which hosts the document domain has failed.
Unknown error during import of <document>. Import canceled.

<document> cannot be imported. (DX0009)
Cause Documents are successfully exported to the repository and users can retrieve
them, but as soon as you want to open these files, you see the above error
message. This error occurs when the client computer does not have the same
character settings as the database to read the information. In addition to the
middleware settings, these character settings must be set in an environment
variable.
Action Modify the client computer to use the same character settings as the
database.
On the client computer, set the variable DB2CODEPAGE with the same
setting that exists in your database (ask the database administrator for the
variable and its setting). The most common value is 850, but may vary when
you have specific languages.

4
Make sure you change these settings on the client side, not the server. Where
you add DB2CODEPAGE to the environment variables depends on your
operating system:
• For Windows 2000: You can find the environment variables in
My Computer > Properties > Advanced > Environment Variables.
• For Windows NT (3.51 and 4.0): You can find the environment variables
in My Computer > Properties > Environment tab.
Then reexport the document to the repository and import the document.
Information can then be read in the same way it was exported.
Unable to close <document>. Import canceled. <document> cannot be

imported. (DX0010)
Cause This message may be generated after you have opened a universe with an
associated List of Values (LOV). An LOV is a file which contains the data
values associated with an object.
Although the LOV file is still open, you have lost your connection to the
document domain.
Action If the document domain is hosted on a different server, try “pinging” the server
on which it resides to make sure it is responding. If the network is running
properly, the database administrator then use database middleware (such as
Net8 for Oracle) to check if there is any response from the repository
database.
If the document domain has been damaged, a contact the supervisor.
Unable to create file associated with <document>. Import canceled.

<document> cannot be imported. (DX0011)
Cause You tried to import a document from the repository, but you cannot write the
file locally to disk. This may be due to:
• Windows access rights: the Windows administrator may not have granted
you the necessary read/write authorization in the folder where you are
trying to import the file.
• Insufficient disk space to import the file.
Action Try the following:
• Ask the Windows administrator to grant you full access to the folders on
the system where you are trying to import the file.
• Quit the application, free up some disk space, delete any unnecessary
files and empty your Recycle Bin. Then try to import the file again.
• Change the default location in which you import the documents.

Unable to delete previous file. Import canceled. <document> cannot be

imported. (DX0012)
Cause This message may be generated when you try to reimport a document from
the repository. Because a previous version of the document already exists on
your system, you must delete the previous version before importing the new
version. In this case, however, the previous version of the document cannot
be deleted. This may be because:
• you do not have write-access to the file or folder.
• the file is currently open and being used by another application.
• Shut down any other applications that are running, and try reimporting
the document again.
• Ask the Windows administrator to grant you full access privileges to the
file and/or folder.
Unable to write to <document>. Import canceled. <document> cannot be

imported. (DX0014)
Cause This message may be displayed when you try to import reports after migrating
from one database to another or running a Safe Recovery to create a new key
file.
Action When you recreate the key file, only the connection to the security domain is
rebuilt. The connections to the universe and document domains remain the
same. You must therefore do one of the following:
• Edit the connections so that they point to the new database.
• Change your aliases to point to the new database.
• Create a new document and universe domain, and import the information
into them. Once this is done, check that the new domains work correctly,
then delete the old domains.
The file cannot be deleted. (DX0017)

Cause This message may be displayed when you attempt to delete or import a
document from the repository.
Action The document file (.rep) is probably open. Close the document file and repeat
the procedure.

4
The file name is not compliant with the platform you are working on. Change
the name. (DX0018)
Cause You tried to retrieve a document from the repository, but the file name is not
compatible with the platform you are using.
Action Change the name of the document so that it is compliant with your platform
and then reexport it. Then try retrieving the document once again.
You requested to export the secured file <document>. This action on the file
is forbidden to you. The export was canceled for <document>. (DX0022)
Cause This message may be displayed when you attempt to send a document to the
repository.
Action If no restrictions are placed on your profile by the supervisor, check the
c:\temp folder:
1. Delete the unused documents in the c:\temp folder (if possible, empty the
content in the temp folder).
2. Reboot the machine.
3. Resend the document to the repository.
Unknown error during export of <document>. Export stopped. <document>

not exported. (DX0024)
Cause The table space in the repository is full. There is not enough room to store
your document.
Action Ask the database administrator to increase this table space.
Cause The system hosting the repository has run out of free disk space.
Action The network or system administrator needs to free up some disk space on
this system.
Database error during export of <document>. Export stopped. <document>

Cause The repository is full. There is not enough room to store your document.
Action Ask the database administrator to increase this table space.
Cause The system hosting the repository has run out of free disk space.
Action The system or network administrator needs to free up disk space on this
system.
Cause The table size for obj_x_documents is too small.
Action Ask the database administrator to increase the table size for
obj_x_documents.

Break during export of <document>: Export has stopped. <document> is

Cause During the export of a document to the repository, the process was
interrupted due to a network failure, or a problem on the repository server.
Try exporting the document once again.
Cannot open file associated with <document>. <document> not exported.

(DX0027)
Cause You tried to export a document to the repository, but the file cannot be
opened. The file may be damaged.
Action Try exporting other files. If this does not work, see the supervisor for more
information on the repository you are using.
Cannot load the dll. Check the Microsoft Exchange installation. (DX0037)
Cause A required .dll file has been deleted or damaged.
Action Check your Microsoft Exchange installation. If the error persists, you may
have to reinstall Microsoft Exchange.
Cannot open file associated with <document>. (DX0040)

Cause You are trying to send a document by mail, but the file that you are trying to
send cannot be opened. This may be because:
• The file has been corrupted.
• The file may be located on a machine that is down or has lost its
connection to the network.
• If the file is located on a shared disk, it may already be in use by another
application or user.
Action Check that the file you want to send is accessible, and check that you can
open it yourself before trying to send it.
Cannot send the message. (DX0041)

Cause You are trying to send a document by mail (MAPI), but BusinessObjects
cannot launch your mailing application.
Action Your mailing application cannot be started, probably due to a missing .dll file
or an incomplete configuration. Try reinstalling the application.

4
Unable to get the document's properties! (DX0044)
Cause Although documents are stored in the document domain, their properties are
stored in the security domain. When you import or export documents, both the
document and the document properties must be transferred. This message
may be generated when the connection to the machine hosting the security
domain is no longer working, or the machine itself is down.
Action If the security domain is hosted on a different server, try “pinging” the server
to make sure it is responding. If the network is running properly, the database
administrator should then use database middleware (such as Net8 for Oracle)
to check if there is any response from the repository database.
Database error (DX0045)

Cause This error may be generated when you try to import, export, or refresh a
document. The problem is not with BusinessObjects, but with your data
warehouse.
Action Note down the error information which is returned with this message, and
check it against your database vendor’s troubleshooting documentation.
The document domain is not responding! (DX0046)

Cause Windows does not have sufficient memory to run the various server systems
that were configured.
Action Review the system requirements to make certain that you have sufficient
memory for BusinessObjects. You can also close other applications to free up
memory. Empty your Recycle Bin and delete any unnecessary files.
Cause The repository may contain errors, or may be damaged.
Action A contact your Business Objects administrator.
You need a more recent version of BusinessObjects to import this

document. (DX0047)
Cause You are using a version of BusinessObjects which is older than
BusinessObjects Enterprise 6. You therefore cannot import documents
created with version 6.
Action To use BusinessObjects Enterprise 6 documents, you must upgrade your
BusinessObjects installation to version 6.

Document deletion failed. (DX 00050)

Cause You attempted to delete a document via the Document Exchange or in the
corporate repository. The process was interrupted or the server may no
longer be responding.
Action Try deleting the document again. If you receive the message again, try
logging out and logging back in and repeating the process.
The universe was exported but may contain errors. Please refer to the
designer of this universe. (UX0001)
Cause You successfully exported a universe, but BusinessObjects detected
inconsistencies in the structure or content of the universe.
Action Run an Integrity Check on the universe to fix the problem, and then to export
it again.
No universe domain is available. Contact your supervisor for help. (UX0010)

Cause You cannot export documents or universes to the repository because it lacks
the necessary rows representing connections in the OBJ_M_RESLINK table.
Action Try exporting a universe again. If the problem persists, contact Business
The universe <universe> does not exist in this universe domain. (UX0011)
Cause You are trying to import a derived universe, which means that it is linked to
another universe.
Linked universes are universes that share common components such as
parameters, classes, objects, or joins. Among linked universes, one universe
is said to be the kernel universe while the others are the derived universes.
In this case, the kernel universe was removed from the universe domain but
not the security domain.
Action Check for the location of the kernel universe, and reexport it to the universe
domain. For more information on linked universes, refer to the Designer’s
Guide.
The file name <name> does not exist in your local folder. (UX0012)
Cause You are trying to reimport a derived universe from the repository. A previous
version of the universe already exists on your system, but a previous version
of the master universe cannot be found. This may be because the master
universe has been deleted from your system.
Action Delete the previous version of the universe from your system, and reimport
the universe.

4
Could not retrieve columns of universe tables. The associated universe
connection is not valid. (UX0013)
Cause You are trying to import a universe, but Designer cannot retrieve the
necessary columns because the connection is no longer valid.
Action The server is not responding. Check your connection and modify it if
necessary, then refresh the structure of your universe.
Cause You are trying to import a universe, but since you started your current
Designer session, the supervisor has deleted this universe.
Action Before you can import this universe, the universe designer must export it to
the repository once again.
The connection associated with the universe has not been defined. You
must create a connection. (UX0015)
Cause You are trying to access data in the repository, but the link between the
universe domain and the security domain has been corrupted. You no longer
have secure access to the universe domain.
Action Contact your system administrator.
Could not update the connection locally. (UX0016)

Cause You are trying to update your connection to the repository, but there are
network problems or the machine which hosts the repository database is
down. This message may also be generated in the course of an operation
which initiates connections to the repository (to send or retrieve documents,
etc).
Cannot open the universe. (UX0023)

Cause You are trying to import a universe, but the universe is damaged.
Action Delete your local version of the universe, import the universe from the
repository again, and then try opening it.
Cause One of more of the components of the universe may be corrupted.
Action To fix the problem, the designer of the universe needs to export a working
version of the universe to the repository.

Cannot load the repository. (UX0028)

Cause You are trying to access data in the repository, but BusinessObjects cannot
load the file kgtrep50.dll. There is a problem with the connection to the
security domain.
Cannot release the current repository. (UX0029)

Cause Designer is unable to free up some of the resources which it initialized in
order to set up a connection to the repository.
Action Try launching Designer once again.
The universe file name does not exist. (UX0032)

Cause You are trying to import a universe, but the universe file has been renamed,
moved, or deleted from the universes folder. This folder is located in:
$INSTALLDIR\Business Objects 6.0\Universes
Action Check that the universe file is physically available and fully accessible in the
Universes folder. If you cannot find the universe, check with the other
designers at your site to determine its possible location.
The universe domain does not exist. (UX0033)

Cause You are trying to import a universe, but the universe domain has been deleted
by the supervisor.
Action Check with the supervisor for information about the repository. The universe
domain may have to be recreated.
The universe ID does not exist in the repository. (UX0034)

Cause You are trying to import a derived universe, which means that it is linked to
another universe.
Linked universes are universes that share common components such as
parameters, classes, objects, or joins. Among linked universes, one universe
is said to be the kernel universe while the others are the derived universes.
In this case, the kernel universe was removed from the repository.
Action Check for the location of the kernel universe, and reexport it to the repository.
For more information on linked universes, refer to the Designer’s Guide.

4
The universe name does not exist. (UX0036)
Cause You are trying to import a universe, but this universe has been renamed,
moved or deleted by the supervisor or by another authorized designer.
Action Check with the supervisor, and any other authorized designers. The universe
may have to be reexported to the repository.
The repository is not responding! (UX0037)

Cause This message is displayed when there is a problem connecting to the
repository. This can be due to network problems or because the machine
which hosts the repository database is down. This message may also be
generated in the course of an operation which initiates connections to the
repository (to send or retrieve documents, send to Broadcast Agent, etc.).
The universe domain is not responding! (UX0038)

Cause The server hosting the repository universe domain is down or the network
connection is not working.
Cause This message is displayed when there is a problem exchanging information
with the universe domain of the repository. This can be due to corrupted
tables in the repository database.
Action A supervisor may need to recreate the repository.
The context name does not exist! (UX0039)

Cause While running Designer, you tried to import or export a universe. However,
one or more contexts in the universe cannot be accessed.
Action To fix the problem:
1. Open the source version of the universe.
2. Select Tools > Detect Contexts to list the candidate contexts of the
universe.
3. Run an Integrity Check on the universe.
4. Export a working version to the repository.

The document domain does not exist on the same data account. You cannot
export your lists of values. (UX0040)
Cause Although your document domain and universe domain are defined in the
same data account, there is a problem with the List of Values (LOV) table.
An LOV is a file which contains the data values associated with an object.
LOVs are stored in the document domain as a table called
OBJ_X_DOCUMENTS. However, in order for a document export to succeed,
this same table must also exist in the universe domain. This is not the case in
your data account.
Action You can create the LOV table manually, or (if you are a supervisor) create it in
the same database as the universe domain.
Example: You have a development, testing and production repository
as well as development, testing and production domains. You have
created a universe with a few objects having files that are LOVs. All of
the objects refresh before use and export with the universe. The LOVs
display with no problem in Designer, but the above error message is
displayed when you try to export the universe.
The document domain account is different. You cannot import your lists of
values. (UX0041)
Cause From Designer, you may see the message when importing a universe. From
BusinessObjects, you may see it when importing a universe (through Tools >
Universes) or when trying to view Lists of Values (LOVs) (through Tools >
Universes > Lists of Values).
The message appears when the LOV which is supposed to be with the
universe in the repository cannot be found.
Action To avoid this error message, export only one LOV of the universe (i.e. refresh
the LOV before the export to create the .lov file). The universe's ID is then
present in the document domain (with the LOV), and the domain is
recognized as the right one.
Of course, you must export all other LOVs assigned to objects with the option
checked Export with universe if you want them to be imported with the
universe.

4
Cannot export the lists of values. (UX0042)
Cause Due to limitations on the data types of some databases, there is no support
for the document domain (or document exchange) or the import or export of
document (.rep) files. Therefore, it is not possible to export universes with
Lists of Values (LOVs) to the repository, because LOVs are stored in the
document domain of the repository.
Action Use an alternative for the distribution of LOV files (such as email or floppy
disk), and copy the LOV files associated with a universe to the following
folder:
$INSTALLDIR\Business Objects 6.0\Universes\<universe domain name>\
<universe name>
Alternatively, a supervisor can create specific universe and document
domains on another database (such as Oracle, SQL Server, MS Access)
while keeping your security domain on the same database.
Cannot update the lists of values in the universe domain. (UX0043)

Cause A List of Values (LOV) is a file which contains the data values associated with
an object. It is stored as a table in the document domain. This message is
generated when you try to reexport a universe with an associated LOV (you
have checked the Export with universe checkbox in Designer), but your
universe and document domains exist in different data accounts.
Action To export an LOV with a universe, both the universe and document domains
must exist in the same data account. You must therefore create a document
domain in the same data account as your universe domain.
Cannot import the lists of values. (UX0044)

an object, and is stored in the document domain. This message is generated
when you try to import a universe with an associated LOV, but the universe
and document domains exist in different data accounts.
Action To import an LOV with a universe, both the universe and document domains
must exist in the same data account. A supervisor must therefore create a
document domain in the same data account as your universe domain.
Incremental export operations are not available. Do you want to export the
whole universe? (UX0045)
Cause You have made extensive modifications to your universe, and are trying to
export them to the repository. However, not all of these modifications have
been saved or exported correctly.
Action Click Yes to perform a normal full export of the universe to the repository.

Cannot lock the universe. (UX0046)

Cause Normally, you can lock a universe in Designer from the Import/Export dialog
box. This ensures that only one designer can update or modify the universe at
any given time. In this case, however, the universe cannot be locked. This
may be because:
• The universe is already locked by another designer.
• The universe domain cannot be accessed.
Action Find out which other designers have access to the universe, and request that
they unlock the universe.
If the universe domain is hosted on a different server, try “pinging” the server
Cannot save the universe. (UX0047)

Cause You need to save a universe to disk before Designer can export it. However,
you have read-only privileges to the disk where you are trying to save the
universe, or the disk is full.
Action Try any of the following:
• Empty your Recycle Bin. If necessary, delete any redundant or unwanted
files, and empty the Recycle Bin again.
• If you have read-only privileges on the disk, the Windows administrator
can grant you full access privileges.
• Save your universe to another folder or computer in which you have write
privileges. In Designer, select File > Save As and indicate another
location for saving your universe.
Cannot delete previous <universe>. (UX0048)

Cause This message may be generated when you try to reexport a universe to the
repository, or reimport a universe from the repository. In both cases, because
a previous version of the universe already exists, you must first delete the
previous version before exporting/importing the new version. This message is
generated if the previous version of the universe cannot be accessed:
• in the repository (during an export)
• on your system (during an import)

4
Action For an export, try the following:
• If you suspect that the universe domain is currently locked by another
user, try exporting again. If this problem occurs frequently, check if your
repository database supports row-level locking. If so, the database
administrator may need to manually activate this feature.
• Check if the machine hosting the universe domain is responding by
“pinging” the server. If the network is running properly, the database
administrator should then use database middleware (such as Net8) to
check if there is any response from the repository database.
For an import, check to see whether you have read-only privileges on your
disk. If so, ask the Windows administrator to grant you full access privileges.
<character> is replaced by <character>. (UX0049)

Cause You have imported a universe, but the universe contained invalid characters
in the class, context, or object definitions. By default, BusinessObjects
automatically replaced these invalid characters with blank characters.
Action You can continue to work normally. However, you should remember that the
universe you have imported is no longer identical to the universe in the
repository.
Cannot create destination folder or universe file. (UX0050)

Cause You are trying to import a universe from the repository. However, you do not
have write-access to your local disk, or the disk is full.
files, and empty the Recycle Bin again. If you have read-only privileges on the
root C:\ drive, the Windows administrator can grant you full access privileges
on the C:\ root drive.
Database error (UX0051)

Cause This error may be generated when trying to import or export a universe. The
problem is not with BusinessObjects, but with your data warehouse.
Action Note down the error information which is returned with this message, and
check it against your database vendor’s troubleshooting documentation.

Unable to create the list of values file. (UX0052)

Cause A list of values (LOV) is a file which contains the data values associated with
an object, and is stored in the document domain. This message is generated
when you try to export a universe with an associated LOV (you have selected
the Export with universe checkbox), but your universe and document domains
exist in different data accounts.
Action To export an LOV with a universe, both the universe and document domains
must exist in the same data account. You must therefore create a document
domain in the same data account as your universe domain.
Cause BusinessObjects cannot create the LOV in the document domain. This may
be because the document domain is located on a server machine which is
down or has lost its connection to the network. Alternatively, the document
domain tables may be corrupted, or there may be insufficient disk space.
Action Check that there is sufficient disk space on the machine on which the
document domain resides. Delete any unnecessary files and empty the
Recycle Bin.
Otherwise the supervisor needs to test the connection to the document
domain. If the problem persists, the supervisor may need to recreate the
repository.
Cannot open the list of values file. (UX0053)

an object, and is stored in the document domain. This message may be
generated when you try to open a universe with an associated LOV. The
document domain tables may be corrupted.
Action Contact the system administrator.
Cannot close the list of values file. (UX0054)

generated after you have opened a universe with an associated LOV.
Although the LOV file is still open, you have lost your connection to the
document domain.
Contact the system administrator because the document domain may be
damaged.

4
Unable to delete the previous lists of values file. (UX0055)
generated when you try to reexport a universe to the repository. Because a
previous version of the universe already exists in the repository, you must first
delete the previous version of the LOV file before exporting the new version.
In this case, however, you cannot delete the previous version of the LOV file
because the document domain cannot be accessed.
• If you suspect that the document domain is currently locked by another
user, run the scheduled task once more. If this problem occurs frequently,
check if your repository database supports row-level locking. If so, you
may need to manually activate this feature.
• Check if the machine which hosts the document domain is responding by
“pinging” the server. If the network is running properly, the database
administrator should then use database middleware (such as Net8 for
Oracle) to check if there is any response from the repository database.
Unable to write to the list of values file. (UX0057)

generated when you try to export a universe to the repository. In this case,
you cannot write to the LOV file. This may be because you do not have the
necessary authorization, the document domain tables are full, or the system
which hosts the document domain has run out of free disk space.
• You may have read-only privileges on the disk which hosts the document
domain. Ask the Windows administrator to grant you full access
privileges.
• Ask the database administrator to increase the space of the document
domain table.
• Free up some disk space on the document domain machine: Delete any
unnecessary files and empty the Recycle Bin. Then try to export the
universe again.

Unable to get data from the lists of values file. (UX0058)

generated when you try to open a universe with an associated LOV. The
document domain tables may be corrupted.
Action Contact your system supervisor.
RSS file not accessible. (UX0059)

Cause One .rss file is created for each database you are using. This file contains the
necessary connection information, and is stored in the database folder:
$INSTALLDIR\Business Objects 6.0\dataAccess\RDBMS\legacy\
<database name>
This error is generated if BusinessObjects cannot find the .rss file under the
database folder, and therefore cannot establish a connection to the database.
Action Copy a backup of the .rss file to the database folder. If you do not have a
backup, a supervisor must recreate the connection in Supervisor.
Incorrect SQL used. (UX0060)

generated when you try to access a universe with an associated LOV using
freehand SQL statements that you enter in the SQL Editor. The SQL you
used may not be compatible with your corporate database.
Action Check which versions of SQL are supported by your corporate database.
Cause BusinessObjects has encountered an exceptional error while attempting to
access your corporate database.
Not enough memory. (UX0061)

Cause Windows does not have sufficient memory to run the various server systems
that were configured.
Action Review the system requirements to ensure that you have sufficient memory
for BusinessObjects. You can also close other applications to free up
memory. Empty your Recycle Bin and delete any unnecessary files.

4
Cannot begin transaction and export <universe>. Problem with the security
domain. (UX0062)
Cause You are trying to export a universe to the repository, but the security domain is
either inaccessible or has been damaged.
If you cannot resolve the problem, contact your system supervisor.
Cannot begin transaction and export <universe>. Problem with the

document domain. (UX0063)
Cause You are trying to export a universe to the repository, but the document domain
is either inaccessible or has been damaged.
administrator should use database middleware (such as Net8 for Oracle) to
check if there is a response from the repository database.
Cannot obtain information on previous <name>. (UX0064)

repository. Because a previous version of the universe already exists in the
repository, a previous version of the List of Values (LOV) should also be
available in the document domain. An LOV is a file which contains the data
In this case, however, the previous version of the LOV cannot be found in the
document domain. This may be because the LOV file has been moved,
renamed, or deleted by the supervisor.
Action Check that the previous version of the file is still available in the document
domain.

Cannot delete previous <name>. (UX0065)

repository. Because a previous version of the universe already exists in the
repository, a previous version of the List of Values (LOV) should also be
available in the document domain. An LOV is a file which contains the data
This file must be deleted before the new LOV can be exported. In this case,
however, the previous version of the LOV cannot be deleted from the
document domain. This may be because you do not have write-access to the
document domain disk.
Action You may have read-only privileges on the disk which hosts the document
domain. Ask the Windows administrator to grant you full access privileges.
Cannot terminate transaction and export <universe>. Problem with the

document domain. (UX0066)
Cause You started to export a universe to the repository, but cannot complete the
operation because the document domain is either no longer accessible or has
been damaged.
Cannot terminate transaction and export <universe>. Problem with the

security domain. (UX0067)
Cause You started to export a universe to the repository, but cannot complete the
operation because the security domain is either no longer accessible or has
been damaged.
administrator should then use database middleware (such as Net8) to check
if there is any response from the repository database.

4
Database error during export of the list of values file. (UX0068)
Cause This message may be generated after a BusObj.exe task has finished
processing (i.e., accessing the repository to send a document, perform an
update, etc). The problem is due to the way in which your repository database
has been set up to handle user access.
Action Check with the database administrator to make sure the database is neither
full nor corrupted.
Export of the lists of values interrupted. (UX0069)

an object, and is stored as a table in the document domain. This message is
generated when you lose your connection to the document domain while you
are trying to export a universe.
Action Verify if the repository is responding by “pinging” the server. If the network is
running properly, the database administrator should then use database
middleware (such as Net8 for Oracle) to check if there is any response from
the repository document domain.
Universe already exists in the domain. Do you want to overwrite it? (UX0071)
Cause The universe that you are trying to export has the same name as another
universe that has already been exported to the universe domain.
Action If you are updating an existing universe, then you can overwrite the universe
that is already in the universe domain. If you are exporting a new universe,
then rename the universe using a unique name, and try exporting it again.


Error Message Guide
Data Access Error Messages
chapter
5 Data Access Error Messages
Data Access error messages

Data access error messages include the following ranges and categories:
Range Category
DMA0002 - DMA 0008 data provider
DPP0001 - DPP0002 file error
DPQ0001 - DPQ0006 connection
DPS0001 - DPS0002 stored procedures
DWZ0001 server
QP0001 - QP0027 SQL/query
QPF0001 SQL
VBA 0009 - VBA 00013 data provider

5
Bad hierarchy name (DMA0002)
Cause This message appears when you try to name a hierarchy with the same name
as an existing hierarchy.
Action Use a unique name for the new hierarchy.
Export failed! (DMA0005)

Cause This error message appears as the result of a failure after you have selected
one of the following file export options:
• Export to local file format -- In the case of an attempted export to a dBase
or Excel file, there has been a general export failure that was possibly
caused by unavailable target files, a Microsoft DAO internal error (such
as an absent ISAM driver), or not enough disk space.
In the case of an attempted export to a text file, there has been a general
export failure that was possibly caused by unavailable target files or not
enough free disk space.
• Copy to DDE -- In the case of an attempted export to DDE (the Windows
Clipboard), there has been a general export failure that was most likely
caused by insufficient memory.
• Export to RDBMS -- In the case of an attempted export through a
BusinessObjects connection, there has been a general export failure
possibly caused by an improper middleware configuration or connection,
the database server being down, or the user not being authorized to
modify an existing table in the database indicated by the connection. In
the case of Export to RDBMS, this error message follows a message
generated from the middleware that contains more specific information.
Action You need to check the option you selected for export and then take the
appropriate following steps:
If you checked, Then

Export to local file make certain that the target files are available and that
format there is enough free disk space. If both of these
conditions are met, look for Microsoft DAO internal
errors such as no ISAM driver.
Copy to DDE make certain there is enough free memory.
Export to RDBMS the preceding (middleware) error message should give
you more specific information.
Cause In BusinessObjects, you attempted to export data to Microsoft Excel.
However, the data contains objects with names made up of special characters
that have specific meanings in Microsoft Excel.

Action When exporting the data do this:

1. Instead of clicking the option Export to Local File Format, click Copy to
DDE.
This allows you to copy the data to the Microsoft Windows clipboard.
2. Launch Excel and paste (special) the data in the cells you wish.
The object names are displayed correctly.
An alternate solution is to use BusinessQuery if it is available at your site. It
also accepts BusinessObjects data which it displays correctly.
Editing this data provider requires an additional BusinessObjects

component which has not been installed on your computer. Please contact
your system administrator. (DMA0006)
Cause This error message appears when you attempt to edit a data provider for a
BusinessObjects report and that data provider requires a component that has
not been installed on your computer.
Action You should contact the system administrator to help you identify the missing
component and to install it.
Example: You want to edit a data provider that uses an OLAP server
and you do not have the specific OLAP Access Pack installed on your
computer.
The following data providers have not been successfully refreshed

(DMA0007)
Cause Essbase products: If you use an table alias name that contains a parenthesis.
Action A table alias name should not contain parenthesis. Contact your system
administrator.
Cause All other Business Objects products: You begin to refresh a document that
prompts you to select values. The Enter or Select Values dialog box appears.
Rather than select values, you select Cancel in the Enter or Select Values
dialog box and stop the data provider from being refreshed.
Action This is not an error. It is a message to tell you that the report cannot display
new data because you stopped the data provider from being refreshed.

5
A variable prevented the data provider from being refreshed. (DMA0008)
Cause This message appears in the following situation. You begin to refresh a
document, but one of the variables contained in the data provider (@Variable,
@Prompt, @Script) cannot be resolved. This prevents the data provider from
being refreshed.
Action You or the universe designer should examine and, if necessary, modify the
variables in the query. You can do this in the Free-Hand SQL Editor or the
universe designer can do it in Designer. For further information about the
correct syntax for variables, refer to the Designer’s Guide.
Cannot open file. (DPP0001)

Cause This error message appears after the failure to open any of the following files
that you are using as a personal data file:
• dBase
• Excel
• text
The file is unavailable because it was possibly deleted, renamed, moved, or
damaged. It is also possible that you are not authorized to use the file; for
example, the file is in a folder with restricted access.
Action You need to check the status of the file.
You are not authorized to use this stored procedure. (DPP0002)

Cause You tried to open a document that was created using a stored procedure,
after the stored procedure was deleted.
Action Contact your database administrator.
Connection is not defined. (DPQ0001)

Cause This error message appears when you try to run a query you have created in
the Free-Hand SQL Editor. There is no connection defined between
BusinessObjects and the database you want to access with your query. It is
therefore impossible to access data for your report.
Action You need to create a database connection from the Free-Hand SQL Editor or
the database administrator needs to define a new connection to the database
with Designer or Supervisor.
You can create a new connection in the Add a connection dialog box, which
you display by clicking the Create a new connection button in the Free-Hand
SQL Editor.

The server is not responding! (DPQ0003)

Cause This error message appears when you refresh a document in
BusinessObjects. There are three possible causes:
• The middleware is not configured correctly.
• The BusinessObjects connection parameters are invalid.
• The database server is down.
Action Click the Details button in the Task Connection dialog box. Make a note of the
database or middleware error and contact the database administrator.
Connection problem (DPQ0005)

Cause This error appears when you attempt to run a query that you have created in
the Free-Hand SQL Editor. A connection is a set of parameters that provides
access to a database. This message appears when the connection has not
been correctly defined.
Action If you have defined the connection to the database from the Free-Hand SQL
Editor, you need to edit it. To edit the connection, select the connection in the
Connection list in the Free-Hand SQL Editor, and click the Edit connection
button.
If you are using a connection that you did not define in the Free-Hand SQL
Editor, the database administrator needs to edit the connection in Designer or
Supervisor.
Does not exist. (DPQ0006)

Cause This error occurs when you try to run a SQL script that you have created in
the Free-hand SQL Editor. The SQL data provider cannot find information
about the connection to a database that it is supposed to use and displays
this error message.
Action You need to look at the database connection to be used by the SQL script to
make sure that it exists and that it is still valid.
If the database connection does not exist, you can define it in the Free-Hand
SQL Editor.
If the database connection exists, is one that you defined in the Free-Hand
SQL Editor, and needs to be modified, then you can edit it by selecting the
connection from the Connection list in the Free-Hand SQL Editor and clicking
the Edit Connection button.
If the database connection exists and you did not define it, then the database
administrator needs to edit it in Designer.

5
This stored procedure has been removed. (DPS0001)
Cause A stored procedure is a type of BusinessObjects data provider. A stored
procedure is an SQL script that is stored on the RDBMS. The supervisor
defines a connection to the database containing the stored procedure and
then assigns it to the user. In this case, you are trying to use a stored
procedure that has been deleted. BusinessObjects cannot generate the
report.
Action Either the supervisor needs to redefine the connection to the database
containing the stored procedure and assign it to you or you need to use
another data provider.
You are not allowed to use this stored procedure (DPS0002)

Cause This error message appears when you attempt to use a stored procedure as
a data provider and the supervisor has not given you permission to use it.
Action Contact the supervisor for permission to use the stored procedure.
The server is not responding. (DWZ0001)

Cause This error message appears in Designer when you run a process that
requires the database server and the database server does not respond.
There are three possible causes:
Action Click the Details button in the Test Connection dialog box. Make a note of the
The only authorized SQL command is ““Select”” (QPF0001)

Cause This error occurs when the SQL has been modified (most likely, manually)
and the Select command was replaced. The SQL Select command is
required for report generation.
Action You need to add the Select command to the SQL and regenerate it. You can
perform these operations in the Query Panel or in the Free-Hand SQL Editor.
BusinessObjects does not accept a comment as the first SQL command.

Error during SQL generation. (QP0001)

Cause This error occurs during the execution of a query. The two possible causes
are an error in the SQL or a problem in the connection between
BusinessObjects and the database.
Action You should verify the SQL. If the SQL appears to be correct, test the
connection.
Internal memory error during SQL generation. (QP0002)

Cause This error occurs when there is no longer enough memory to generate the
SQL.
Action You should close other applications and then rerun the query.
Memory error during SQL generation. (QP0003)

Cause This error occurs when there is no longer enough memory to generate the
SQL.
Action You should close other applications and then rerun the query.
Incompatible combination of objects. (QP0004)

Cause This error is caused by any of the following problems in the definition of the
universe:
• There are incompatible objects in the universe and the universe designer
did not set the option that allows multiple SQL statements for each
context.
• There are no contexts in the universe and the query has created a loop.
• The query objects exclude all possible SQL choices for an aggregate
aware function.
• The universe contains an object which references more than one table on
separate contexts.
Action The universe designer needs to make appropriate modifications to the
universe with Designer.
Outer joins are incoherent. (QP0005)

Cause This error is caused by a universe definition problem. There is a bad
combination of outer joins among tables in the database.

5
Cartesian product not allowed. (QP0006)
Cause A Cartesian product is the result of a query in which two or more tables are
not linked by a join. If executed, the report shows results for each possible
combination of each table row. The BusinessObjects universe designer
specified that Cartesian products would not be allowed when this universe
was created.
universe with Designer. The designer can allow Cartesian products or create
the necessary links among tables in the database.
The query does not reference a table. (QP0007)

Cause This error is caused by a universe definition problem. There is an object in the
universe that cannot be used all alone. In addition, no SQL statement
recognizes this object.
universe with Designer. For further information, refer to the Designer’s Guide.
There is a reference to a table that has been deleted. (QP0008)

Cause This error occurs when you regenerate a SQL statement after having
refreshed a database and the universe has been modified. The SQL
statement cannot execute because it references a table that no longer exists
in the universe.
Action The universe designer needs to modify the universe with Designer so that all
its objects are linked to tables in the universe.
One of the objects in the query is not valid. (QP0009)

Cause This error occurs when one of the objects in a query no longer exists in the
universe.
Action The universe designer can return the object to the universe with Designer or
you can remove the object from your query.

One of the properties in the query is not valid. (QP0010)

Cause This error message appears when you run a query that includes predefined
condition objects from the Query Panel. One of the condition objects in the
query no longer exists in the universe. The query cannot execute and the
error message appears.
Action See the universe designer about the universe and the condition object. Using
Designer, the universe designer can define objects that act as predefined
conditions on a class. Either the universe designer needs to define the
condition object or you need to create the query without the condition. For
further information about defining condition objects refer to the Designer’s
Guide.
The .PRM file cannot be found. (QP0011)

Cause BusinessObjects cannot find a .prm file. A .prm file contains all the
parameters necessary for creating and managing BusinessObjects universes
as well as generating queries. This error indicates that BusinessObjects has
been incorrectly installed.
Action Reinstall BusinessObjects.
The complex condition has created a Cartesian product. (QP0013)

Cause This error occurs when you insert a calculation as part of a complex condition.
The calculation is using objects that reference unlinked tables. A Cartesian
product is the result of a query in which two or more tables are not linked by a
join. If executed, the report shows results for each possible combination of
each table row.
Action The universe designer can use Designer to link the tables referenced by the
objects in your calculation. Or you can remove the condition from the query.
Loop in complex condition. (QP0014)

Cause This error occurs when you insert a calculation as part of a complex condition.
The calculation uses objects whose tables form a loop.
Action The universe designer needs to use Designer to link the tables referenced by
the objects in your query so that they do not form a loop. Or you can remove
the condition from the query.

5
This query is too complex. One of the subqueries contains incompatible
objects. (QP0015)
Cause This error occurs when you have a complex query containing multiple
subqueries and the objects in one subquery are incompatible with the objects
in another subquery.
Action You need to examine the subqueries of the complex query to assure that all
objects in all subqueries are compatible.
The server is not responding. (QP0016)

Cause This error message appears when you run a query from the Query Panel and
no data is being returned from the server. There are three possible causes:
Action Click the Details button in the Task Connection dialog box. Make a note of the
Columns of the SELECT clause are different from the result objects.
(QP0017)
Cause This error typically occurs after you modify the SQL by hand in the Free-Hand
SQL Editor. There are either too many or not enough fields in the Select
clause in comparison with the number of objects in the Query Panel.
Action You need to edit the SQL so that there are the same number of fields in the
Select clause as there are objects in the Query Panel.
Syntax error in variable. (QP0018)

Cause This error occurs when one of the objects in the query contains an @Prompt
or an @Variable that is incorrectly defined in the universe.
Action The universe designer needs to redefine the @Prompt or @Variable in the
Syntax of @Prompt
The syntax of the function is as follows:
@Prompt(‘message’,[‘type’],[lov],[MONO|MULTI],[FREE|CONSTRAI
N])
where
• message is the text of a message within single quotes.
• type is one of the following: ‘A’ for alphanumeric, ‘N’ for number, or ‘D’ for
date.

• lov can be either:

• a list of values enclosed in brackets (each value must be within
single quotes and separated by commas); or
• the name of a class and object separated by a backslash and within
single quotes.
• MONO means that the prompt accepts only one value.
MULTI means that the prompt can accept several values.
• FREE refers to free input as opposed to CONSTRAIN, which means that
the end user must choose a value suggested by the prompt.
Note: The last four arguments are optional. However, if you omit an
argument, you must still enter the commas as separators.
Syntax of @Variable
The syntax of the function is as follows:
@Variable(‘myname’)
where myname can be one of the following:
• The text of an interactive object previously created with the @Prompt
function; i.e. the first argument entered in the @Prompt function.
• A BusinessObjects system variable such as BOUSER. These variables
represent respectively the user name and password forming the user
identification. System variables also exist for the connection to the
RDBMS.
For more information on the correct syntax for defining @Prompt or
@Variable, refer to the Designer’s Guide.
You are not authorized to use the object. (QP0019)

Cause This error occurs when one user tries to open a document created by another
user and that document contains an object for which the user does not have
access rights.
Action The BusinessObjects supervisor can give the user access rights to the object.
Aggregate aware resolution failed. (QP0020)

Cause This error occurs during SQL generation because a measure object that was
defined using the @Aggregate_Aware function was incorrectly defined. It is
necessary to define these measure objects to set up aggregate awareness.
Aggregate awareness enhances the performance of SQL transactions.
Because of the incorrect definition, the SQL cannot be generated.
Action The universe designer needs to examine the measure objects defined with
the @Aggregate_Aware function to make certain that their syntax is correct.

5
Syntax of @Aggregate_Aware
The syntax of the @Aggregate_Aware function is as follows:
@Aggregate_Aware (sum(agg_table_1, ... sum(agg_table_n))
where agg_table_1 is the table with the highest level of aggregation, and
agg_table_n the table with the lowest level. You must enter the names of all
aggregate tables as arguments. Also, be aware of the order in which you
place the names of tables; the precedence is from left to right.
The designer should also make certain that there is a list of incompatible
objects and/or incompatible predefined conditions for each aggregate table in
the universe.
For further information on aggregate awareness and the @Aggregate_Aware
function, refer to the Designer’s Guide.
Ambiguous condition on a measure. Remove it or cancel your scope of

analysis. (QP0021)
Cause When you choose a deeper scope of analysis, you add objects from lower
levels in the hierarchy to the query. SQL uses the Group By order to generate
a synchronized subquery. The operators Equal to, Except, Greater than, Less
than, Greater than or equal to, and Less than or equal to can generate a
synchronized subquery. The operators Between, Matches pattern, and In list
cannot generate a synchronized subquery. The SQL cannot be generated.
Action You can modify the query or you can remove the scope of analysis.
You cannot create a new tab before including at least one result object in
this tab. (QP0022)
Cause This error message appears if you try to create a second query that you want
to combine with a first query and you have removed all the result objects from
the first query.
Action You need to place at least one result object in the first query tab.
You cannot combine subqueries. (QP0023)

Cause This error message appears if you try to combine a subquery of one query
with a second query. This is not allowed.
You cannot delete this query. You must delete the condition first. (QP0025)
Cause This message appears if you try to delete a query that has an attached
subquery without first deleting the attached subquery.
Action In order to delete the query, you must first delete the subquery.

Some obsolete objects have been removed from the query. (QP0027)
Cause This error occurs during SQL generation because your query contains objects
that the universe designer has removed from the query.
Action You need to reconstruct the query without the deleted objects.
Error when trying to access VBA. (VBA 00009)

Cause You have tried to select VBA as a BusinessObjects data provider.
Action Check that VBA is installed correctly.
Unable to edit the procedure. (VBA 00010)

Cause You have tried to edit a VBA procedure used as a BusinessObjects data
provider.
Action The procedure is already open in the Visual Basic editor. Close it and try
again.
Unable to create the procedure. (VBA 00011)

Cause You have tried to create a VBA procedure for use as a BusinessObjects data
provider.
Action Check that VBA is installed correctly.
You must select a procedure in the list. (VBA 00012)

Cause You have tried to run a VBA procedure as a BusinessObjects data provider
without selecting a procedure from the list.
Action Select a procedure from the list.
Unable to delete the procedure. (VBA 00013)

Cause You have tried to delete a VBA procedure used as a BusinessObjects data
provider
Action The procedure is already open in the Visual Basic editor. Close it and try
again.

Error Message Guide
Web Intelligence Error

Messages
chapter
6 Web Intelligence Error Messages
Web Intelligence error messages

Web Intelligence error messages include the following ranges and categories:
Range Category
WIH 00001 - WIH 00012 Web Intelligence HTML report panel
WIJ 10000 - WIJ 77778 Web Intelligence Java report panel
WIS 00001 - WIS 40000 Web Intelligence server

Web Intelligence Error Messages
6
Invalid block definition. (WIH 00001)
Cause You have tried to run the query, or access the Report Filters, Properties, or
Format tab without completing the following criteria:
• For tables, crosstabs, and forms, you must allocate objects to each field.
• For all chart types, you must allocate measure objects only to the Y-Axis.
• For all chart types except pie charts, you must allocate at least one
dimension or detail object to the X-Axis.
• For all chart types, except pie charts, if you have allocated more than one
object to the Y-Axis, you cannot allocate any objects to the Z-Axis.
• For pie charts, you can allocate only one measure object to the Y-Axis.
• For pie charts, you must allocate at least one object to the X-Axis.
Action Properly allocate the objects to each necessary field, then access the tab you
want or run the query.
This object has already been inserted. (WIH 00002)

Cause You cannot insert the same object more than once in a query.
Action Choose another object, or run the query with the object you have selected.
This filter has already been inserted. (WIH 00003)

Cause You cannot insert the same predefined filter more than once in a query.
Action Choose another predefined filter, or run the query with the predefined filter
you have already selected.
This document includes advanced formatting that requires the Java Report
Panel. (WIH 00004)
Cause You have tried to open a document created in the Java Report Panel
containing one of the following elements:
• more than one report
• more than one report block
• filters defined for either a section or report block
• a non-embedded section
• more than three freestanding cells in the page header or footer
• more than one freestanding cell in the top of the report
• more than one freestanding cell in each section of the report
Action Open the document with the Java Report Panel.

Cannot insert measures on the X-Axis. (WIH 00005)

Cause You cannot insert a measure on the X-Axis of a chart. You can only insert a
measure on the Y-Axis.
Action Insert the measure on the Y-Axis.
Cannot insert dimensions or details on the Y-Axis. (WIH 00006)

Cause You cannot insert a dimension or detail on the Y-Axis of a chart. You can only
insert a measure on the Y-Axis.
Action Insert the dimension or detail on either the X- or Z-Axis.
Cannot insert measures on the Z-Axis. (WIH 00007)

Cause You cannot insert a measure on the Z-Axis of a chart. You can only insert a
measure on the Y-Axis.
Action Insert the measure on the Y-Axis.
You must insert a result object before choosing another tab. (WIH 00008)
Cause You tried to access another tab without inserting objects to the report.
Action Insert one or more objects to the report in the Universe Objects pane in the
Query tab.
You cannot create a section using a measure. (WIH 00009)

Cause You can only create sections on dimensions. For example, you can create
sections for time periods, geographies, product categories, customers and so
on. You cannot create sections on measures, for example, sales revenue,
margin, or unit sold.
Action Select a dimension to create a section.
You cannot insert dimension or detail objects on the Z-axis of this type of
chart. (WIH 00010)
Cause You can only insert measure objects on the Z-axis of this chart type.
Action Select a measure for the Z-axis.
You cannot insert dimension or detail objects on the X-axis of this type of
chart. (WIH 00011)
Cause You can only insert measure objects on the X-axis of this chart type.
Action Select a measure for the X-axis.

6
Report names cannot be blank. Close this dialog box and then enter a name
for the report. (WIH 00012)
Cause All reports in a document need to be named.
Action Type a name for this report in the Name text box displayed in either the
Rename or Insert Report dialog box.
Tip: To launch these dialog boxes:
• Go to the HTML Report Panel Report tab, and then click the link in
the Current Report section of the options, which says: To manage
reports in this document, click here.
• Select a report, and then click rename to display the Rename dialog
box.
The document could not be saved. (WIH 00014)

Cause Web Intelligence was unable to save the document to the repository. This
error can occur for a number of reasons. For example: you do not have the
security rights to the folder where you tried to save the document.
Action See your BusinessObjects Administrator to determine why you could not save
the document.

You need to use the Formula Editor to create a correctly formed formula.
(WIJ 10000)
Cause You typed a formula into a cell using the Cell Properties panel instead of the
Formula Editor.
Action Launch the Formula Editor and define the formula in the Formula Definition
pane.
You cannot create a variable that has the same name as an existing
document object. Give the new variable a different name. (WIJ 10001)
Cause A single Web Intelligence document cannot contain multiple objects or
variables with the same name.
Action To save a new variable, give the variable a name that is different from the
objects and variables already included in the document.
You cannot position this report component in relation to a block, cell, or

section that is positioned relative to this report component. Select a
different block, cell, or section in the "Relative to...of:" dropdown list or
unselect the "Relative to:" option. (WIJ 10500)
Cause When you position a report component in relation to another report
component that references the selected one, you create a circular
attachment.
Action Select a different block, cell, or section in the Relative to...of: dropdown list.
Alternatively, unselect the Relative to: option for the selected report
component.

6
The Web Intelligence Java Report Panel requires Java Runtime Environment
(JRE) 1.4.2_01 to run on your computer. The JRE currently installed is {0}.
Either contact your administrator to upgrade to 1.4.2_01 or select the
[default VM] entry in the [Java Plug-in Control Panel], if you already have the
required version installed. (WIJ 11111)
Cause When you use the Web Intelligence Java Report Panel, a Java applet is
installed on your local PC. The Java Runtime Environment 1.4.2_01 (or later
version) needs to be installed and selected in order for the report panel to
function.
Action If Java Runtime Environment 1.4.2_01 (or later version) is already installed
on your PC, then launch the Java Plugin Control panel. To do this:
• Select the Windows menu: Start>Settings>Control Panel.
• Double-click Java Plug-in.
• On the Advanced tab, select Use Java Plug-in Default, then click Apply.
Or
Contact your Business Objects administrator, and request help with installing
Java Runtime Environment 1.4.2_01 (or later version).
An error occurred while the document was being decoded. Try to open the
document in InfoView. If this doesn't work, see your BusinessObjects
administrator. (WIJ 20000)
Cause Web Intelligence cannot decode and open the document in the Java Report
Panel.
Action Open the document in InfoView by clicking the document title where the
document is listed on the InfoView Corporate Documents or Personal
Documents page.
If this does not work, see your BusinessObjects administrator.
An unexpected problem occurred when Web Intelligence tried to refresh the

document data and open the document. The data source has been modified
or deleted, or a prompt on the document has no value selected. (WIJ 20001)
Cause The document has the Refresh on open option selected. One or more of the
following explanations can account for this error:
• The data source has been modified since the document was created.
• The data source has been deleted since the document was created.
• One or more prompts have no values selected.
Action See your BusinessObjects administrator.

The Web Intelligence Java Report Panel cannot connect to the server. Close
the report panel and try to connect again or see your BusinessObjects
Cause The server may be down or your user session may be closed.
Unable to retrieve the first page of the current report. Check the report for
errors or contact your administrator. The report panel will switch to
Structure View. (WIJ 20003)
Cause The report contains structural errors. This means that Web Intelligence
cannot decode the report and display the results.
Action Do one of the following:
• View the report in Structure View and verify the report structure. For
example, errors can be caused if report blocks overlap or if the structure
of a table contains cells that create an asymmetrical table format. Modify
the report structure appropriately.
• Contact your administrator and request them to search for structural
anomalies in the report.
The query in this document is empty. Check that the Result Objects pane on
the query tab or view includes objects before running the query. (WIJ 30000)
CauseCause If the query does not contain any objects, Web Intelligence cannot run the
query and retrieve data from the database.
ActionAction Edit the query and add the appropriate objects to the Query pane.
At least one query in this document is empty. Check that the Result Objects
pane includes objects before running the queries. (WIJ 30001)
CauseCause If a query does not contain any objects, Web Intelligence cannot run the query
and retrieve data from the database. This is the case even if the document
contains multiple queries.
ActionAction Go to the Query pane and verify each Query tab. Add the appropriate objects
to the Query tab that is empty.

6
Out of memory. Reduce the browser window size or re-launch the report
panel. (WIJ 30003)
Cause Your computer has run out of the memory necessary to operate the Web
Intelligence Java Report Panel. This may be because your browser window
size is too large.
• Use your cursor to reduce the size of the browser window displaying the
Java Report Panel.
• Go back to the InfoView browser window and re-launch the Java Report
Panel, by opening an existing document or by creating a new document.
Your user profile does not allow you to save personal or corporate
documents. See your Business Objects administrator. (WIJ 40001)
Cause Your user profile, defined by your administrator, does not allow you to save
personal or corporate documents.
Action If you think you need to be allowed to save personal documents and/or
corporate documents to InfoView, contact your Business Objects
administrator to request they modify your security profile.
An unexpected error occurred. Contact your administrator with details of

the actions you performed before the error occurred. (WIJ 44444)
Cause This message appears when an unexpected error occurs that Web
Intelligence cannot analyze.
Action Provide your BusinessObjects administrator with details of how the error
occurred. Your administrator will need to activate the tracing in order to find
an explanation and solution for this error. Full information about system
tracing is available in the System Administrator's Guide for Windows and the
System Administrator's Guide for UNIX.
The information sent to the server contains invalid character(s). Use the
Undo button to cancel the latest changes to the document and then retry.
(WIJ 55555)
Cause Web Intelligence sends information on the document format and data
definition to the server in XML code in order to render the document and the
results. This error means that there is an error in the XML.
Action Use the Undo button on the report panel toolbar to remove the erroneous
modification made to the document, and then run the query or refresh the
document again.

Web Intelligence cannot retrieve this document due to a server problem or

an error in the document structure. See your BusinessObjects
Cause The Web Intelligence Java Report Panel cannot retrieve the document due to
one or more of the following reasons:
• The server is down.
• The results returned from the server present badly formed XML code that
the report panel cannot decode.
Your Web Intelligence WIQT session has reached timeout. Log out and log
in again to InfoView. (WIJ 77778)
Cause You have remained logged in to InfoView without using Web Intelligence for
longer than the maximum time allowed by the Business Objects system.
Action Log out and then log back into InfoView to continue using Web Intelligence
(you will lose any unsaved modifications you made previous to timeout).
To increase the length of time you are allowed to remain logged in to InfoView
without using Web Intelligence, ask your BusinessObjects administrator to
increase your session timeout parameter.

6
Some objects are no longer available in the universe. See your
BusinessObjects administrator. (WIS 00001)
Cause One or more objects in a universe are no longer available to a document.
Action Delete the objects from the query that seem to be missing. The available
objects are listed on the Data tab. Rebuild the query without the obsolete
objects.
Some objects are not available to your user profile. You cannot refresh this
document. See your BusinessObjects administrator. (WIS 00002)
Cause You do not have the correct user rights to access the data for one or more
objects included in a query. As you are not permitted to access the data for
these objects, you cannot refresh the report.
Action Ask your BusinessObjects administrator to change your user profile to make
these objects accessible.
Some predefined filters are no longer available in the universe. See your
Cause One or more predefined filters are no longer available in the universe.
Predefined filters are condition objects that are predefined WHERE clauses.
You use these to restrict the data returned in a query.
Action Remove the predefined filters from the query, and manually create the same
condition in the query by using the appropriate operators and operands.
Some database tables are no longer available in the universe. See your
Cause One or more database tables referenced by objects in the universe are no
longer available. The tables may have been renamed, or removed from the
database.
Action The universe designer can update the universe structure by selecting
View > Refresh Structure in Designer.
Invalid Prompt definition. See your BusinessObjects administrator.

(WIS 00005)
Cause The syntax in the prompt is not valid, or the prompt makes reference to an
object that no longer exists in the universe.
Action The universe designer can verify that the prompt syntax is correct, and check
that all objects referenced in the prompt exist.

Invalid Aggregate Aware definition. See your BusinessObjects

administrator. (WIS 00006)
Cause One or more objects in the query use the aggregate aware function in their
definition. The syntax for the aggregate aware function is not valid.
Action The universe designer must verify that the aggregate aware syntax is correct.
A filter contains a wrong value. You cannot run this query. (WIS 00007)
Cause The filter has a wrong operand. For example, a filter with an empty constant,
or a filter that deals with numeric values is defined with an alphanumeric
value.
Action Verify the filter syntax.
The query cannot run because it contains incompatible objects. See your
Cause The query contains objects that return data sets that can not be combined or
synchronized. This can be due to parameters that have not been set in the
universe to allow multiple SQL statements for each context, or multiple SQL
statements for each measure.
Action The universe designer can do the following:
• Select the options Multiple SQL statements for each context and Multiple
SQL statements for each measure. These are on the SQL page of the
Universe Parameters dialog box.
• Create a new context that includes the incompatible objects.
The query cannot run because an advanced filter contains an incompatible

object. See your BusinessObjects administrator. (WIS 00009)
Cause The advanced filter is a subquery. You can not combine incompatible objects
in a sub query.
Action Change the advanced filter definition to use only compatible objects.
The universe does not allow using a complex expression in a GROUP BY

statement. You cannot run this query. See your BusinessObjects
Cause A query contains a GROUP BY clause that uses formulas or aliases. The
universe does not allow these expressions in GROUP BY clauses. The
behavior is determined by the parameter
<Parameter Name="GROUPBY_EXCLUDE_COMPLEX">Y</Parameter>
in the PRM file for the target RDBMS.
Action You have two solutions:

6
• Modify the query so that objects using formulas or aliases are not
included in the query.
• A universe designer can open the PRM file for the target RDBMS and
change the value for the parameter GROUPBY_EXCLUDE_COMPLEX
to N. This change should be made only if you are sure that your RDBMS
supports complex GROUP BY expressions.
The object(s): {obj list} contain multiple attributes. This syntax is no longer
supported in this version. See your BusinessObjects administrator.
(WIS 00011)
Cause One or more objects in the query use a comma (",") instead of a
concatenation operator in their definition. This syntax is no longer supported
for current versions.
Action The universe designer has two options:
• Redefine the objects that use the comma to concatenate the data for two
objects. You can use the standard concatenation operator for your
RDBMS.
• If you do not want to redefine the objects, you can add the following line
to the PRM file for the target RDBMS:
<Parameter Name = "REPLACE_COMMA_BY_SEPARATOR"=Y>
This will enable the comma to be accepted syntax for concatenation in
object definitions.
You cannot run this query as it will produce a Cartesian product. See your
Cause The query will produce a Cartesian product. This is a result set that contains
all possible combinations of rows from the tables inferred by objects in the
query. This is rarely a correct result. Parameters have been set in the
universe to prevent Cartesian products.
Action The universe designer has two options:
• Modify the universe table schema to include the appropriate joins and
restrictions to prevent the possible occurrence of a Cartesian product.
• If Cartesian products are acceptable in your business context, then from
Designer, set the Cartesian Products option to Warn. This option is on
the SQLl page of Universe Parameters dialog box. The user will be
warned, but the production of a Cartesian product will not be prevented.

SQL generation failed. See your BusinessObjects administrator. (WIS 00013)

Cause Error occurs during SQL generation of the query. This can be due to a
number of reasons; for example the query doesn't involve any table in the
database.
Action Ask your BusinessObjects administrator to check the SQL associated with the
objects involved in the query.
Incompatible combination of objects. See your BusinessObjects

Cause The query objects exclude all possible SQL choices for an aggregate aware
function.
Action The universe designer can remove the incompatibility between the objects in
Designer. Select Tools > Aggregate Navigation and remove the
incompatibility for the concerned objects.
Multiple query filters contain a prompt with the same text, but the prompts
use a different operand type or operator count of values. (WIS 00015)
Cause The query has multiple prompts that display the same message. Web
Intelligence combines prompts with the same message and displays the
prompt once. If the operator defined for some of these prompts requires you
to enter one value while the operator in other prompts with the same
message requires you to enter multiple values, Web Intelligence cannot
combine the prompt.
Action You need to modify the definition of the prompts. How you do this depends on
how you are viewing the document:
• Via InfoView -- click the Edit link, and then use the Web Intelligence
report panel options to modify the prompts. For more information on how
to do this, refer to the Building Reports Using the Java Report Panel or
Building Reports Using the HTML Report Panel guide.
• In the Web Intelligence Java Report Panel -- go to Query View by clicking
Edit Query in the report panel toolbar, and then double-click the prompts
you want to edit and select operators for each prompt. For more
information on how to do this, refer to the Building Reports Using the
Java Report Panel or Building Reports Using the HTML Report Panel
guide.
Example: The operators you define for the prompts with the same
message text must all require one of the following:
• one value (for example: Equal to, Different from, Greater than, Greater
than or equal to, Less than, Less than or equal to, Except.)

6
• multiple values when the prompt is answered (for example: Between, Not
between, In list, Not in list, Matches pattern, Different from pattern, Both.)

The query contains an @Script() function, which is not supported. See your
Cause The SQL generated by the query for this document includes an @Script()
function, which is not supported.
Action Your administrator will need to remove the @Script in the universe selected
for this document.
The following objects cannot be used as result objects: {obj_list}. See your
Cause The query definition for this document includes objects in the Result Objects
pane that cannot be used in queries.
• Go to Query View by clicking the Edit Query button on the report panel
toolbar, and then remove the listed objects from the Result Objects pane.
• Contact your BusinessObjects administrator and request the ability to
include the listed objects in the Result Objects defined for the query.
The following objects cannot be used in query filters: {obj_list}. See your
BusinessObjects administrator. (WIS00018)
Cause The query definition for this document includes objects in the Query Filters
pane that cannot be used in query filters.
• Go to Query View by clicking the Edit Query button on the report panel
toolbar, and then remove the listed objects from the Query Filters pane.
• Contact your BusinessObjects administrator and request the ability to
include the listed objects in filters defined on the query
Universe not found. See your BusinessObjects administrator. (WIS 00501)

Cause The universe used to refresh the document is not available; for example the
universe does not exist, or has been moved.
Action The universe designer can check that the universe is present in the
repository, and is accessible to the connection. If you are dealing with a linked
universe, check that the links are still valid.
Contact your BusinessObjects administrator with this information.

6
User rights not found. See your BusinessObjects administrator. (WIS 00502)
Cause You cannot retrieve the list of user rights from the repository. This may be
because the server which hosts the repository is down or the network
connection is not working.
Action Verify the network connection by "pinging" the server. If the network is running
database.
You are not authorized to access the universe {unv_name}. See your
Cause Your user profile has the current universe as "Disabled." This user profile
parameter is set by your administrator.
Action Contact your administrator to request a modification to your user profile, so
that you can access this universe.
Syntax error in formula at position {n}. (WIS 10001)

Cause There is a syntax error in your formula at the position indicated.
Action Correct the formula syntax.
The object name {object} at position {n} is not unique in the report. Use the
fully-qualified object name. (WIS 10005)
Cause The object {object} has a name that conflicts with the name of another object
in the report.
Action Use the fully-qualified name for {object}.
The object {object} at position {n} does not exist in the report. (WIS 10006)
Cause The formula refers to an object that no longer exists in the report.
Action Remove the reference to the object from the formula.
The integer number {number} at position {n} has a format that is

incompatible with your regional settings. (WIS 10012)
Cause The format of the integer number {number} is not compatible with your
regional settings.
Action Change the number format to conform with the format permitted by your
regional settings.

The real number {number} at position {n} has a format that is incompatible
with your regional settings. (WIS 10014)
Cause The format of the real number {number} is not compatible with your regional
settings.
Action Change the number format to conform with the format permitted by your
regional settings.
A closing quotation mark does not appear in the formula after the quotation
mark before {formula_part} at position {n}. (WIS 10016)
Cause There is a missing closing quotation mark in the formula.
Action Add the closing quotation mark.
The object name {object} at position {n} is ambiguous. Use the fully-
qualified object name. (WIS 10019)
Cause A formula contains an object name that is ambiguous.
Action Use the fully-qualified object name (qualify the object name with its class) to
remove the ambiguity.
The variable {variable name} cannot be deleted because it has dependent

formulas or variables linked to {variable name}. (WIS 10033)
Cause The variable cannot be deleted because it is referenced by other variables or
formulas.
Action Delete the dependent formulas/variables before deleting the variable.
There is already a variable called {variable}. Choose another variable name.

(WIS 10034)
Cause You attempted to create a variable or update a variable name using a variable
name that already exists.
Action Choose a variable name that does not already exist.
The date/time format {datetime} at position {n} is not valid. Specify a valid
date/time format. (WIS 10035)
Cause The formula contains an invalid date/time format (for example, "bb/MM/yyyy").
Action Specify a valid date/time format in the formula.

6
The expression/sub-expression at position {n} is not valid. Specify a valid
expression. (WIS 10036)
Cause The formula contains an invalid expression/sub-expression.
Action Specify a valid expression/sub-expression.
The expression/sub-expression at position {n} uses an invalid data type.

Specify a valid data type. (WIS 10037)
Cause An expression contains an invalid data type. (For example, you have
attempted to pass a string to a function that requires a date.)
Action Use a valid data type in the expression.
Invalid character {character} in variable name at position {n}. Specify a valid

character. (WIS 10038)
Cause The character {character} is not valid in the variable name.
Action Remove {character} from the variable name.
The context you specified for the measure {measure} at position {n} is not
valid. Specify a different context. (WIS 10039)
Cause The calculation context of {measure} is not valid.
Action Specify a valid context.
The formula for variable {variable} contains a reference to a variable with the
same short name. You must use the fully-qualified variable name in the
formula to remove this ambiguity. (WIS 10040)
Cause The formula of a variable references another variable with the same short
name.
Action Use the fully-qualified variable name.
Incorrect use of multiple comparison operators at position {n}. (WIS 10041)

Cause The formula uses multiple comparison operators incorrectly (for example:
if(1<2=3;0;-1)).
Action Re-structure the formula to avoid using comparison operators incorrectly.
There is a circular reference because the formula for variable

{variable_name} references a variable whose formula references
{variable_name}. (WIS 10042)
Cause A formula contains a circular reference.
Action Remove the circular reference.

Your Database server does not support the Both and Except operators.
Redefine your filters using different operators and then run the query again.
(WIS 10701)
Cause The database on which this document is based does not support the Both
and Except operators. This means that you cannot use the Both operator or
the Except operator when you define filters on the query of this document.
Action Return to Query View by clicking the Edit Query button on the report panel
toolbar, then do one of the following:
• Remove the filter from the Query Filters pane.
• Double-click the filter on the Query Filters pane, and then select a
different operator for the filter.
Tip: If the Query Filters pane is not visible in Query View, click the Show/Hide
Filter Pane button on the Query View toolbar.
A filter is defined on an object that is incompatible with all the objects

selected on the Result Objects pane. Remove the filter from the Query
Filters pane or remove the objects from the Result Objects pane.
(WIS 10702)
Cause One of the query filters is defined on an object which is incompatible with all
the objects selected on the Results Objects pane.
Action Return to Query View by clicking the Edit Query button on the report panel
toolbar, then do one of the following:
• Remove the filter from the Query Filters pane.
• Remove the objects from the Result Objects pane.
Tip: If the Query Filters pane is not visible in Query View, click the Show/Hide
Filter Pane button on the Query View toolbar.
Your security level does not allow you to refresh this document. Contact
your Business Objects administrator. (WIS 10801)
Cause Your user profile does not permit you to view data for one of the objects
included in the query for this document.
The security level for objects is set by the Business Objects administrator at
your organization, using the universe design tool Designer. When the object-
level security for objects in a query is different from the security level specified
in your user profile you cannot refresh the document data.

6
• Cancel the refresh.
• Request your administrator to modify your user profile, so that you can
access data for objects with higher levels of security.
Database error: {error_db}. Contact your administrator or database supplier

for more information. (WIS 10901)
Cause The database that provides the data to this document has generated an error.
Details about the error are provided in the section of the message indicated
by the field code: {error_db}.
Action Contact your BusinessObjects administrator with the error message
information or consult the documentation provided by the supplier of the
database.
The query in this document is empty. Check that the Result Objects pane on
the query tab includes objects before running the query. (WIS 30000)
Cause No data is defined for this document.
Action 1. Depending on the Web Intelligence report panel you are using, either
click Edit Query or click the Query Tab.
2. Add objects to the Result Objects pane to define the data for the query.
3. Run the query again.
At least one query in this document is empty. Check that the Result Objects
pane on each query tab includes objects before running the queries.
(WIS 30001)
Cause No data is defined for at least one of the queries in this document.
Action 1. Click Edit Query on the report panel toolbar.
2. Click the tab for each of the queries in the document to identify the query
or queries that have no objects selected.
3. For each empty query, add objects to the Result Objects pane to define
the data you want Web Intelligence to retrieve.
4. Run the query again.

Your security profile does not include permission to edit the queries in Web
Intelligence documents. (WIS 30251)
Cause Your BusinessObjects administrator has disabled the Edit Query command in
your user profile.
Action Contact your BusinessObjects administrator to request the ability to edit the
queries in Web Intelligence documents.
Your security profile does not include permission to edit Web Intelligence
documents. (WIS 30252)
Cause Your BusinessObjects administrator has disabled the Edit Documents
command in your user profile.
Action Contact your BusinessObjects administrator and request the ability to edit
Web Intelligence documents.
Your security profile does not include permission to refresh Web

Intelligence documents. (WIS 30253)
Cause Your BusinessObjects administrator has disabled the Refresh Documents
Action Contact your BusinessObjects administrator to request the ability to refresh
Web Intelligence documents.
Your security profile does not include permission to refresh lists of

values. (WIS 30254)
Cause Your BusinessObjects administrator has disabled the Refresh List of Values
Action Contact your BusinessObjects administrator to request the ability to refresh
lists of values in Web Intelligence documents.
Your security profile does not include permission to use lists of

values. (WIS 30255)
Cause Your BusinessObjects administrator has disabled the Use List of Values
Action Contact your BusinessObjects administrator to request the ability to use lists
of values in Web Intelligence documents.

6
Your security profile does not include permission to view the SQL generated
by the query. (WIS 30256)
Cause Your BusinessObjects administrator has disabled the View SQL command in
your user profile.
Action Contact your BusinessObjects administrator to request the ability to view the
SQL in Web Intelligence queries.
Your security profile does not include permission to use the Web
Intelligence formula language. (WIS 30257)
Cause Your BusinessObjects administrator has disabled the Use Formula Language/
Create Variables command in your user profile.
Action Contact your BusinessObjects administrator to request the ability to use the
formula language and create variables in Web Intelligence documents.
Your security profile does not include permission to perform drill analysis.
(WIS 30258)
Cause Your BusinessObjects administrator has disabled the Work in Drill Mode
Action Contact your BusinessObjects administrator to request the ability to drill on
Web Intelligence reports.
Your security profile does not include permission to extend the scope of
analysis. (WIS 30259)
Cause You attempted to perform a drill operation outside the defined scope of
analysis. Your administrator must grant you permission to perform such an
operation.
Action Contact your administrator.

An internal error occurred while calling the {api_name} API. (WIS 30270)
Cause Information about the document or the data source is invalid or not available.
The following table provides information about each of the APIs that you may
see named in the {api_name} error message field:
Name Cause
getDocumentInfos The document ID is invalid or the
document is not available.
getCategoriesAndDocuments The document category is invalid or Web
Intelligence is unable to retrieve the
document from the Business Objects
repository.
getGroupAndDomains The user group or document domain
associated with this document is invalid
or cannot be found.
getDataSourceList The list of universes is not available.
getDataProviderResults The data provider is invalid or some of
the objects specified in the query are not
available.
sendDocument This document cannot be sent via
InfoView, because the recipient or the
document ID is invalid.
publishDocument This document cannot be saved as a
corporate document, because the
recipient or the document ID is invalid.
Action Your BusinessObjects administrator can trace the problem that caused the
error by activating the tracking and verifying the trace associated with the API.
Note: For information on how to trace system activity, see the Business
Objects Administrator’s Guide.

6
Max binary file size limit exceeded. The document is too large to be
processed by the server. Contact your BusinessObjects administrator.
(WIS 30271)
Cause When you view a Web Intelligence in Portable Document Format (PDF) or
Microsoft Excel format, the Web Intelligence server generates binary based
output, which is then interpreted by your web browser. This errors occurs, if
the size of the binary output is greater than the maximum size specified by
your administrator for the Web Intelligence server.
Action An administrator can change the parameters set for Maximum binary output
on the Administration Console. However, increasing the maximum binary
output can affect performance.
Contact your administrator with this information.
Max character file size limit exceeded. The document is too large to be
processed by the server. Contact your BusinessObjects administrator.
(WIS 30272)
Cause When you view a Web Intelligence document in HTML format, the Web
Intelligence server generates character based output, which is then
interpreted by your web browser. This errors occurs, if the size of the
character output is greater than the maximum size specified by your
administrator for the Web Intelligence server.
Action An administrator can change the parameters set for Maximum character
output on the Administration Console. However, increasing the maximum
binary output can affect performance.
Contact your administrator with this information.
Web Intelligence cannot complete the steps necessary to build the query or
generate the report, due to missing or invalid information concerning the
data source or query definition. Contact your BusinessObjects
Cause Web Intelligence could not complete one or more of the steps required to
define a query and generate a report. This is due to one of the following
reasons:
• the document was not initialized
• the data source is not valid
• the query was not defined
• the query context was not defined at the universe level
• no values were specified for prompts at the universe level

Action Your BusinessObjects administrator needs to check the following:

• the connection to the data source
• check the universe for unspecified contexts and prompt values
A query with this name already exists. Rename this query. (WIS 30371)
Cause Another query used in this document already has this name.
Action Enter a different name for this query.
You cannot edit this document, because the query property option "Allow
other users to edit the query" was not enabled when the document was
created. (WIS 30381)
Cause The creator of the document did not select the query property option: "Allow
other users to edit the query".
Action Contact the document creator to ask them to enable the option and resave
the document.
Save a copy of the document as a personal document and then edit the query
in the copy.
An internal error has been generated by the WIQT. Contact your

Cause An unexpected error occurred on the WIQT.
Action Contact your BusinessObjects administrator, who may need to seek
assistance from BusinessObjects Worldwide Customer Support.
Your Web Intelligence WIQT session has reached timeout. Log out and log
in again to InfoView. (WIS 30553)
Cause You have remained logged in to InfoView without using Web Intelligence for
longer than the maximum time allowed by the Business Objects system.
Action Log out and then log back into InfoView to continue using Web Intelligence
(you will lose any unsaved modifications you made previous to timeout).
To increase the length of time you are allowed to remain logged in to InfoView
without using Web Intelligence, ask your BusinessObjects administrator to
increase your session timeout parameter.

6
No more WIQT servers are available. The maximum number of concurrent
users is already logged into Web Intelligence. (WIS 30554)
Cause This error message means that the number of users currently using Web
Intelligence has reached the maximum number of concurrent users allowed
by your administrator. Administrators specify the number of preregistered
WIQTs generated at system startup, ready to be used as users log in. The
system assigns a WIQT to each user session at login.
Action Try again later, when less users are using Web Intelligence.
Ask your BusinessObjects administrator to increase the number of concurrent
users allowed by Web Intelligence.
Your security profile does not include permission to save documents as

corporate documents or to send documents via InfoView. (WIS 30555)
Cause Your security profile does not allow you to save Web Intelligence documents
as personal or corporate documents, or to schedule documents.
Action Contact your BusinessObjects administrator to request the ability to:
• save corporate documents
• send documents to users in own groups
• send documents to users in other groups
A Corporate document with this name already exists. Your security profile
does not include permission to delete corporate documents created by
other users. (WIS 30556)
Cause Your security profile does not allow you to overwrite existing corporate
documents.
Action Contact your BusinessObjects administrator, to request the ability to delete
corporate documents saved by other users to InfoView.
There is no document with this name in InfoView. Specify a different

document name. (WIS 30557)
Cause There is no Web Intelligence document with this name in InfoView for one of
the following reasons:
• You have typed the document name incorrectly
• The document with this name has been deleted from InfoView
Action Check that you have entered the document correctly.
Note: Deleted documents cannot be retrieved.

Web Intelligence cannot perform the intended action on this document.

(WIS 30650)
Cause The Web Intelligence server is unable to complete the current task, because
of lack of resources or access problems.
• Close Web Intelligence and log out of InfoView, then log back into
InfoView again.
• Ask your BusinessObjects administrator to verify that your security profile
allows you access to the corporate repository.
The Web Intelligence server failed to load the XML document. Contact your
Cause When you migrate a BusinessObjects document to Web Intelligence 6.x, an
XML file is created that can be opened by the Web Intelligence Report Server.
(The related module on the Administration Console is called the
WIReportServer). In this case an unexpected error occurred on the Web
Intelligence Report Server, while migrating a BusinessObjects document to
Web Intelligence 6.x.
Action Your BusinessObjects administrator can trace the problem that caused this
error by activating the tracking and verifying the trace associated with the
WIReportServer. Contact your administrator with this information.
The XML file for this document cannot be opened. Contact your
XML file is created that can be opened by the Web Intelligence server. This
error occurs when the XML file cannot be opened by the Web Intelligence
server, and so migration cannot be completed. There are two common
causes:
• The XML is Read Only.
• The file path to the XML file is incorrect.
Action Contact your BusinessObjects administrator with this information.
An error occurred while parsing the Web Intelligence XML document.

Contact your BusinessObjects administrator. (WIS 30753)
XML file is created that can be opened by the Web Intelligence server. This
error occurs when the XML file contains structural anomalies that the Web
Intelligence server cannot interpret, and so migration cannot be completed.

6
Action There are two possible actions that an administrator can take to solve this
problem:
• Open the XML file with an XML editing tool and verify the structure of the
document.
• Activate the tracking and verify the trace associated with the
WIReportServer.
The Web Intelligence 2.x document could not be migrated. (WIS 30761)
Cause An unexpected error occurred when trying to migrate a Web Intelligence 2.x
document to the current Web Intelligence version document format.
Action An administrator may be able to identify the cause of this error by activating
the tracking and verifying the trace associated with the Web Intelligence
server. Contact your BusinessObjects administrator with this information.
This document cannot be migrated. The query and report of the original
Web Intelligence 2.x document are not synchronized. Try to refresh and
save the original document; then attempt migration again. (WIS 30762)
Cause In the original Web Intelligence 2.x document, there is a discrepancy between
the objects included in the query and the objects included in the report. This
means that the Web Intelligence server is unable to interpret the document
correctly to migrate it to the current Web Intelligence version document
format.
Action To synchronize the data definition in the query and report of the original
WbIntelligence 2.x document:
1. Use Web Intelligence 2.x to open the original document again.
2. Either run the query or refresh the document data.
3. Save the refreshed document.
4. Try to migrate the document again using the Migration Tool.
If you do not have access to Web Intelligence 2.x or the Migration Tool,
contact your BusinessObjects administrator with this information.
The Web Intelligence 2.x document could not be migrated, because the
WIQT module returned an error. Contact your administrator. (WIS 30763)
Cause The original Web Intelligence 2.x document could not be migrated to the
current Web Intelligence version document format, due to an error generated
by the WIQT (Web Intelligence Query Technique) process.
Action Your BusinessObjects administrator can trace the problem that caused this
error by activating the tracking and verifying the trace associated with the
WIQT. Contact your administrator with this information.

Your user profile does not provide you with access to a document domain to
save corporate documents. Save this document as a personal document or
contact your Business Objects administrator. (WIS 40000)
Cause Your user profile does not include permission to save documents to a
corporate document domain on InfoView.
• Save this document to your Personal Documents area on InfoView by
saving it as a Personal Document
• Contact your Business Objects administrator and request access to a
corporate document domain.

Error Message Guide
Miscellaneous Error
Messages
chapter
7 Miscellaneous Error Messages
Miscellaneous error messages

Miscellaneous error messages include the following ranges and categories:
Range Category
GUI0003 - GUI0006 GUI
USU0001
LOV0001 - LOV0002 List of Values (LOV)
VAR0001

Miscellaneous Error Messages
7
The file name contains forbidden characters. (GUI0003)
Cause You tried to save a universe with a name that contains unauthorized
characters. This restriction may originate from:
• the character set allowed by the database on which the BusinessObjects
repository resides
• the options, set by the supervisor from the Supervisor module, which limit
the characters allowed in the repository
Action Use a different name to save your universe. If the problem persists, ask the
BusinessObjects supervisor about the authorized character set for your
universes.
File not found. Please verify the correct file name was given. (GUI0005)
Cause You tried to open a BusinessObjects report by entering a file name that does
not exist.
Action Enter the correct name of the file, or use the Up One Level button in the Open
dialog box to locate the desired report.
<name> path not found. Please verify the correct path name was given.
(GUI0006)
Cause You tried to open a BusinessObjects report using an incorrect path name. The
report may exist, but it is not at the location you specified.
Action From the Open dialog box, use the Up One Level button to locate the report.
Too many selected values. (LOV0001)

Cause From a list of values in the Query Panel, you attempted to select more than
the authorized number of values. By default, you can select up to 99 values at
the same time.
Action Limit the number of values you select to less than 99.
Cause You selected less than 99 values but the above error appears. This means
that a restriction has been set in the prm file corresponding to your database.
This restriction appears as the parameter MAX_INLIST_VALUES.
Action Remove this parameter, or set its limit to a higher number.
You have not been authorized to use this universe. (LOV0002)

Cause You do not have rights to this universe (to which lists of values have been
assigned).
Action See the BusinessObjects supervisor to find out about the universes you are
authorized to work with.

7 Miscellaneous Error Messages
Cannot find <name>. Please check that all components have been correctly
installed. (USU0001)
Cause You selected the User’s Guide command from the Help menu of the
BusinessObjects application but no guide appeared. The online guides, which
are in Acrobat PDF format, may not have been installed on your hard disk.
Action Check the contents of the online guides language folder of your
BusinessObjects files. If there are no PDF files, then you need to install them
using the BusinessObjects installer program. This program also installs the
Acrobat Reader which lets you read these files.
Syntax error (VAR0001)

Cause The query contains a condition with a prompt for which you must enter one or
more values using a separator between each value. The separator is usually
a semicolon (;) or a comma (,). It is defined in the Windows Control Panel
(Regional Settings).
The error results from the use of the separator. Perhaps you entered it at the
beginning of the prompt, or inadvertently entered it twice between two values.
Action In the Enter or Select Values dialog box, reenter the values using one
separator between each value.

Error Message Guide
Crystal Reports Error

Messages
chapter
8 Crystal Reports Error Messages
Crystal Reports error messages

This document could not be opened. It does not appear to be a Crystal
Report document.
Cause This message occurs when you attempt to open a corrupt Crystal report file
that does not have an RPT extension.
Action A backup copy of the report must be used in place of the corrupted copy.
This document could not be opened. It does not appear to be a Crystal

Report document. The document has the expected extension (.RPT), but it
seems to be corrupted. If this report used to work, try opening it with a
different version of Crystal Reports and if that doesn't work, contact your
administrator.
Cause This message occurs when you attempt to open a corrupt Crystal report file
that has an RPT extension.
Action A backup copy of the report must be used in place of the corrupted copy.
Failed to load database connector.

Cause This message occurs if the database connector is not available on the
machine that is processing the report. The database client software required
by the database connector is not available on the machine that is processing
the report.
Action Ensure that:
• the database connector used by the report is installed on all machines
where the report can be run.
• the necessary database client software required by the database
connector is installed and in the PATH environment system variable on all
machines where the report can be run.

Crystal Reports Error Messages
8
Failed to open the connection. Details: [Database Vendor Code: <vendor
code number>].
Cause This message occurs for one of the following reasons:
• The data source required by the report is unavailable on improperly
configured on the machine that is processing the report.
• The database server required by the report is unavailable.
• The database client is installed but improperly configured on the machine
that is processing the report. For example a DB2 database alias, Oracle
tnsnames entry or Sybase DSEDIT entry is missing or improperly
configured.
Action Ensure that
• the data source required by the report is available and properly
configured on all machines where the report can be run. For example,
the ODBC data source or JNDI data source exists and connectivity can
be proven from a client test tool.
• the database server required by the report is running and that
connectivity can be proven from a client test tool on all machines where
the report can be run.
Failed to retrieve data from the database. Details: [Database Vendor Code:
<vendor code number>].
Cause The report SQL queries that have been sent to the server cannot be
executed, because an error was returned by the database server after it
processed the queries. For example, a field/table/procedure required by the
report is missing, or the queries contain syntax errors.
Action Ensure the report is using the correct connection information. For example,
the data source name, server name, database name and user name are
correct.
In a database client test tool, ensure that the fields, tables and procedures
used by the report exist and that SQL queries can be executed against them.
In the Crystal Reports designer, verify that the SQL query, as shown under
the Database menu Show SQL Query option does not contain syntax errors.
If the SQL query shown in Crystal Reports is valid, execute the same SQL
query through a database client test tool.

8 Crystal Reports Error Messages

Error Message Guide
Enterprise Performance
Management Error
Messages
chapter
9 Enterprise Performance Management Error Messages
Enterprise performance management error messages
Enterprise performance management error

messages
The performance management error messages include the following ranges
and categories:
Range Category
EPM 00001 - EPM 09999 Default zone
EPM 10000 - EPM 19999 Metrics engine
EPM 20000 - EPM 29999 Analytic server
EPM 30000 - EPM 39999 Repository manager
EPM 40000 - EPM 49999 Rules engine
EPM 50000 - EPM 59999 Process Analysis engine
EPM 60000 - EPM 69999 Set engine

Enterprise Performance Management Error Messages
Enterprise performance management error messages 9
Cannot create query. (EPM 00001)
Cause This error message appears for one or more of the following reasons:
• There is a problem in the performance management repository.
• There is an error in the universe fact tables.
• The SQL did not generate correctly.
Action Check the following:
• Verify the connections to the performance management repository in
performance management Setup.
• Verify the connection to the universe fact tables.
• See the trace log for specific information on the errors.
Note: If you have not set up the trace log feature yet, go to performance
management Setup > Parameters > Trace. For more information on how to
set up the trace logs, see the online help in performance management Setup.
DBDriver not set. (EPM 00002)

Cause The database driver was not set correctly.
Action Check your database driver setup.
Database type not found: %1. (EPM 00003)

Cause The database driver was not set correctly.
Action Check your database driver setup.
Could not communicate with Web Intelligence. (EPM 00004)

Cause A Corba exception occurred when the repository tried to communicate with
other servers.
Action The IT administrator needs to restart all the servers in the Central
Management Console.
A problem occurred during attempt to publish the document '%1' (%2). (EPM
00005)
Cause A problem occurred while saving the analytic in the BusinessObjects
Enterprise repository.
Action Check your trace log files to find out where the error occurred.

The model refreshed data cannot be retrieved from the database properly.
Contact your Business Objects administrator. (EPM 00006)
Cause The default value for the packed_result size in the ci_param table is not
compliant with your database configuration.
Action 1. Verify that the ci_param table contains the following values:
(param_id, param_type, item_name, item_value)
where item_name is ' packed_result size', and item_value is an
integer that corresponds to the maximum size of the
ci_context_output.packed_result.
Example:
insert into ci_param (param_id, param_type, item_name,
item_value) values (0, 1, 'packed_result size', 20000)
2. Restart the performance management servers.
3. Refresh the models.
Could not retrieve user profile for filter '%1' equals to '%2'. (EPM 10001)
Cause The user rights for that dimension cannot be loaded.
Action Check the definition for the dimension in performance management Setup >
Dimensions and the rights associated to that user.
Information on the selected subject area cannot be retrieved. Check the list
definition. (EPM 10002)
Cause In the Export List analytic, the associated subject area cannot be found in the
performance management repository. A “subject” is a class on a universe.
Action To resolve this problem:
1. Log into InfoView.
2. In performance management, check your configuration in Setup >
Repository.
3. Update the universe which contains that subject in Setup > Universes.
SQL cannot be generated for the selected objects. (EPM 10003)

Cause Web Intelligence cannot generate the SQL corresponding to the universe
objects selected to create the list.
Action Use Web Intelligence to build a query using the same objects in order to
identify the objects causing the problem, then contact your BusinessObjects
Enterprise Administrator with this information.

No data to fetch. (EPM 10004)
Cause There are no values to display.
Action Select different universe objects that might have some values.
No count object exists in the subject area %1. (EPM 10005)

Cause No Count measure has been identified in that subject area. A “subject” is a
class on a universe.
1. Open the universe in Designer.
2. Create or find the count measure and add "COUNT=Y" to its description.
3. Republish the universe, and update it in performance management in
Setup > Universes.
No dimension object has been defined in the universe as the subject key for
the subject area %1. (EPM 10006)
Cause There is no dimension object identified in the universe for the specified
subject area.
2. Define a dimension object with the "SubjectKey=Y" parameter in its
description.
Setup > Universes.
No IPDATE object exists in the subject area %1. (EPM 10007)

Cause No dimension has been identified in the specified subject area as the date to
be used for the Individual Profiler analytic.
2. Create a date dimension called IPDATE.
Setup > Universes.

No IPFILTER object exists in the subject area %1. (EPM 10008)

Cause No condition has been identified in the specified subject area as the filter to
be used for the Individual Profiler analytic.
2. Create a condition called IPFILTER.
Setup > Universes.
More than one count object exists in the subject area %1. (EPM 10009)
Cause There is more than one measure in that subject area with "COUNT=Y" in its
description
2. Delete all but one of the count measures.
Setup > Universes.
More than one Subject Key object exists in the subject area %1. (EPM 10010)
Cause There is more than one dimension in that subject area with "SubjectKey=Y" in
its description.
2. Delete all but one subject key dimensions.
Setup > Universes.
Cannot parse analytic XML. (EPM 20001)

Cause The analytic is not parsing correctly.
Action Recreate the analytic.
Invalid analytic token. (EPM 20002)

Cause The analytic cannot be retrieved.
Action Logout and then log in again. Try to retrieve the analytic.
If the error message appears again, contact your IT administrator.

Cannot find Pareto. (EPM 20003)
Cause The metric or measure on which the Pareto chart is based could not be found.
Action Check the analytic definition and select a valid metric or measure.
Cannot find the appropriate metric to drill down. (EPM 20004)

Cause The metric could not be found.
Action Check the analytic’s parameters to verify that the metric exists.
The system is unable to retrieve this goal. (EPM 20005)

Cause The query cannot run on the performance management repository.
Action Check the performance management configuration in Setup > Repository,
and the corresponding database.
Goal has expired. (EPM 20006)

Cause The last period you selected for the goal is incompatible with the last
refreshed value of the goal's metric.
The goal's last period must precede the last refreshed value of the goal's
metric.
Action Extend the goal's range.
Cannot generate SQL. (EPM 20007)

Cause The universe objects you have selected to create the Pareto Chart are not
compatible given the structure of your data.
Action Create a Web Intelligence query on the same universe using using
compatible objects.
This link is unavailable. It is impossible to contact the server. (EPM 20008)

Cause You clicked on a link in an SVG analytic that is saved to your computer or in
an email.
Action Open the SVG analytic from its original location inside performance
management.

Visual Data Query XML not found for dimension. (EPM 20009)
Cause In Set Analysis, you selected dimensions to include in the set, but did not
expand them in the Content step of the set building steps.
1. In Set Analysis > Sets, select the set.
2. In Set Building Steps, click Edit.
3. In the Content tab, under Step Detail, click the + sign next to each
measure.
4. Select Estimates Only or Exact Counts to create the query for each
measure.
5. Click Build or Finish.
Error while attempting to link to AARepoMgt.exe. (EPM 30002)

Cause There is a problem with the AARepoMgt.exe file.
Action Contact your IT administrator to see if the AARepoMgt.exe file is up and
running.
The IT administrator should try restarting the performance management
server.
Repository Version Manager failed: %1. (EPM 30003)

Cause A problem occurred in the repository.
Action Check the log file to find the errors.
Error while reading the parameter 'LastPushUnv' in the ci_param table.

(EPM 30004)
Cause An invalid parameter was found in the performance management repository.
Action In the ci_param table, delete all parameters whose name starts with
"LastPushUnv".
Error pushing universe '%1'. (EPM 30005)

Cause The universe could not be updated.
Action Check your trace log files to find out where the error occurred.

Universe not found. (EPM 30006)
Cause The universe ID no longer exists because it was either changed or deleted.
Action In performance management Setup > Universes, check that your universes
are pushed and up-to-date.
Cannot get new task ID. (EPM 40001)

Cause You are not able connect to the Scheduler.
Action Restart the Central Management Server and the AA servers.
You are not a Set Analysis user. (EPM 60001)

Cause Your do not have administrator rights and do not have valid set analysis user
rights.
Action Log in as using a valid user account, or, if you are an administrator, edit the
Set Analysis guest user name in performance management Setup > System
Setup > System User.


Error Message Guide
Process Tracker Error

Messages
chapter
10 Process Tracker Error Messages
Process Tracker includes the

following error meessage categories.
Range Category
PT 00001 - 00005 Process Tracker
126 ErrorMessagesExplained
Process Tracker Error Messages
10
Unexpected command "{0}" encountered. (PT 00001)
Cause This error occurs when the Process list view is unable to differentiate between
a Process and a Process Instance.
Action Contact your IT Administrator.
Invalid key code. (PT 00002)

Cause Your license key is not valid.
Action Have your IT Administrator check that the key codes are up-to-date.
You do not have the required key code to run Process Tracker. (PT 00003)
Cause Process Tracker cannot find your license key.
Action Have your IT Administrator check that the key codes exist and are up-to-date.
Process Tracker is not configured for this CMS. (PT 00004)

Cause There is a problem in the Process Tracker configuration.
Action The IT Administrator needs to check the configuration of Process Tracker
and, if necessary, re-install the software.
An error has occurred, please contact your system administrator and see
the log for more information. (PT 00005)
Cause When you tried to create a new process, Process Tracker checked for your
user credentials to create a session and found that you do not have the
permissions to create a Process Tracker session.
Action Have your IT Administrator check your permissions, and if necessary, activate
your user credentials.

10 Process Tracker Error Messages
128 ErrorMessagesExplained
Error Message Guide
Report Conversion Tool Error

Messages
chapter
11 Report Conversion Tool Error Messages
Report Conversion Tool error messages

Report Conversion Tool error messages include the following ranges and
categories:
Range Category
RCT 00001 - 00015 Report Conversion Tool

Report Conversion Tool Error Messages
Report Conversion Tool error messages 11
Unknown error (RCT 00001)
Cause Report Conversion Tool encountered an error that it cannot resolve.
Action Contact your Business Objects Administrator.
Incorrect login or password (RCT 00002)

Cause Your login is not recognized by the server.
Action Contact your Business Objects Administrator. You must be either an
Administrator or a member of the Report Conversion Tool Users Group,
defined in the Central Management Console.
Cannot open document (RCT 00003)

Cause When the Report Conversion Tool runs, it opens the Desktop Intelligence
report before it converts the report to Web Intelligence. This message
appears when the Report Conversion Tool cannot open the Desktop
Intelligence, REP file before it converts to Web Intelligence, WID file.
Action 1. Ensure that you have a minimum set of security settings.
2. Increase the Access Level for the report to Full Control.
3. Login as an Administrator.
Note: The converted Web Intelligence report inherits the user security
settings from the original Desktop Intelligence report.
The audit connection is not defined. (RCT 00004)

Cause You cannot write data to the audit table unless an audit connection is defined
Action Use Designer and the Central Management Console to create a connection
and assign it to the Report Conversion Tool
Error while loading XML description (RCT 00006)

Cause The conversion batch file has not been saved correctly and the XML is not
well formed.
Action You must begin the conversion process again.
Error while saving XML description (RCT 00007)

Cause You cannot save the state of the conversion batch. One potential reason is
that document name contains unsupported characters.
Action Check the names of the documents you want to convert and rename them if
they contain unsupported characters.

Some audit data cannot be added to database (RCT 00008)

Cause The XML log file format is not well formed.
Connection to the database is not correctly defined.
Action 1. Check that your connection middleware is defined.
2. Set up a separate connection using the Oracle middleware that is
installed on your local hard drive if you want to save the audit data locally.
Incorrect URL to portal (RCT 00009)

Cause The InfoView connection settings are incorrect to view the audit report.
Action Verify the Portal access properties by clicking on the shortcut to InfoView.
Copy the information from the URL that appears in the browser to the Portal
access properties dialog box.
Error occurred while trying to access portal (RCT 00010)

Cause The InfoView portal could not be accessed
Action Try entering your login InfoView parameters again. Tip access InfoView via
shortcut and copy and paste the parameters in the relevant location in the
login box.
Audit connection is not defined (RCT 00012)

Cause The connection to the audit server has not been established by logging into
InfoView.
Action 1. Check that the database connection is present in the CMC under
BusinessObjects Enterprise Applications and select the Report
Conversion Application properties Tab.
2. Try repairing the connection in Designer.
Publish failed (RCT 00014)

Cause The Report Conversion Tool could not publish the converted report.
Action Try to run the conversion process again.

Report Conversion Tool Error Messages
Report Conversion Tool error messages 11
Error occurred while trying to start the conversion engine (RCT 00015)
Cause 1. The Report Conversion Tool was not correctly installed on your client
machine. If you have installed BusinessObjects Enterprise 6.5, on a
server that has BusinessObjects Enterprise 6.5 server, Business Objects
recommends that you uninstall the 6.5 version before running XIR2. The
installer modifies the system pass, and when you run Report Conversion
Tool, it may take the inappropriate system pass that is required by 6.5.
2. The server is not responding.
3. The server is out of storage space.
Action Repair the installation of the Report Conversion Tool.
If you are an expert user, you can also remove the folder from system Path
variable value text box the install directory \bin for BusinessObjects
Enterprise 6 bin file.


Error Message Guide
Question Designer and

Intelligent Question Error
Messages
chapter
12 Question Designer and Intelligent Question Error Messages
Question Designer / Intelligent Question error messages
Question Designer / Intelligent Question

error messages
Question Designer / Intelligent Question error messages include the following
ranges and categories:
Range Category
IQ 00001 - IQ 00025 Question Designer
Intelligent Question
The question domain could not be loaded. (IQ 00001)

Cause Insufficient user permissions, or a universe used by this question domain may
have been modified or deleted.
Action Contact your IT administrator.
The Question Engine server is currently unavailable. (IQ 00002)

Cause You tried to access Intelligent Question when the Question Engine server is
stopped.
Action Contact your IT administrator and ask that the server be started.
The question domain could not be loaded. (IQ 00003)

Cause You tried to access the question domain when you do not have rights to
universes and universe connections used by this Question Domain.
Action Contact your IT administrator, and ask to be given rights to the universes and
universe connections.
The Question Engine server is currently unavailable. (IQ 00004)

Cause You tried to access Intelligent Question in Infoview when you do not have the
rights to access the Question Engine server or server group.
Action Contact your IT administrator, and ask to be given rights.
The Question Engine is not running. (IQ 00005)

Cause You tried to log on to Question Designer when you do not have the rights to
access the Question Engine server.
Action Contact your IT administrator, and ask to be given rights.

Question Designer and Intelligent Question Error Messages
Question Designer / Intelligent Question error messages 12
The question domain referenced <number> universe objects which could
not be found. (IQ 00006)
Cause You tried to import the question domain in Question Designer, when you do
not have any rights to universes and universe connections used by this
question domain. Could also be due to changes in a universe since the last
time this question domain was edited.
A subject used by this question no longer exists. (IQ 00007)

Cause The subject has been removed from the question domain.
Attribute <name> no longer exists. (IQ 00008)

Cause The attribute has been deleted from the question domain.
A runtime error has occured. (IQ 00009)

Cause You used the Top comparator for any subject, selected the number inside the
box, and then deleted it.
Action Reset the comparator.
You must specify a label for this filter. (IQ 00010)

Cause You defined a new filter for the subject without giving it a name.
Action Name the filter.
The label All is built-in and cannot be redefined. (IQ 00011)

Cause You tried to define a filter with the name “All.”
Action Choose a different name.
Attribute does not have any values selected. (IQ 00012)

Cause You tried to select an attribute without selecting any values.
Action Select a value.
Favorite question must be given a name. (IQ 00013)

Cause You tried to save a question to Favorites without giving it a name.
Action Name the Favorite question when you save it.

IQ license key doesn’t exist. (IQ 00014)

Cause The license key was not properly installed or configured.
Action See your IT administrator. The correct license key must be set in the CMS.
Couldn’t log on to Business Objects Enterprise. (IQ 00015)

Cause You entered an invalid system name, or none at all.
Action Enter a valid system name.

Cause You entered an invalid user name, or none at all.
Action Enter a valid user name.

Cause You entered an invalid authentication, or none at all.
Action Select a type of authentication.
No universes have changed. (IQ 00018)

Cause You selected Refresh Universes from the Edit menu, but the universes have
not changed.
Action No action; there is no need for refresh.
The question domain cannot be exported because it is not yet complete. (IQ
00019)
Cause There are still some action you need to take before the domain can be
exported.
Action See the To Do list to find out what needs to be done.
The question domain referenced <number> universe objects which could

not be found. (IQ 00020)
Cause This could be due to changes in a universe since the last time this question
domain was edited, or you may not have permission to view some universe
objects.

Question Designer and Intelligent Question Error Messages
Question Designer / Intelligent Question error messages 12
Filter <name> does not exist. (IQ 00021)
Cause You defined a new filter for any subject, created a question based on the filter,
added it to you Favourite questions, deleted the custom filter, and then tried to
access the question from the Favorites list.
Action Re-create the question.
Filter <name> does not exist (IQ 00022)

got your answer, deleted the custom filter, and then tried to access the
question.
Action Redefine the filter.
IFilter <name> does not exist (IQ 00023)

added it to you Favourite questions, deleted the custom filter, and then tried to
access the question.
Action Re-create the question.
A runtime error has occurred. (IQ 00024)

Cause You created a question, exported it to Web Intelligence, clicked to
Documents, and select Close from the drop-down list.
Action Re-export the question.
An error has occurred. The subject with ID <number> does not exist in the
CMS or you don’t have the right to access it. (IQ 00025)
Cause A subject with this ID number does not exist in the CMS or you don't have the
right to access it.


Error Message Guide
Business Objects
Information Resources
appendix
13 Business Objects Information Resources
Documentation and information services
Documentation and information services

Business Objects offers a full documentation set covering its products and
their deployment. Additional support and services are also available to help
maximize the return on your business intelligence investment. The following
sections detail where to get Business Objects documentation and how to use
the resources at Business Objects to meet your needs for technical support,
education, and consulting.
Documentation
You can find answers to your questions on how to install, configure, deploy,
and use Business Objects products from the documentation.
What’s in the documentation set?

View or download the Business Objects Documentation Roadmap, available
with the product documentation at http://www.businessobjects.com/support/.
The Documentation Roadmap references all Business Objects guides and
lets you see at a glance what information is available, from where, and in
what format.
Where is the documentation?

You can access electronic documentation at any time from the product
interface, the web, or from your product CD.
Documentation from the products

Online help and guides in Adobe PDF format are available from the product
Help menus. Where only online help is provided, the online help file contains
the entire contents of the PDF version of the guide.
Documentation on the web

The full electronic documentation set is available to customers on the web
from support website at: http://www.businessobjects.com/support/.
Documentation on the product CD

Look in the docs directory of your product CD for versions of guides in Adobe
PDF format.
142Error Messages Explained

Business Objects Information Resources
Customer support, consulting and training 13
Send us your feedback
Do you have a suggestion on how we can improve our documentation? Is
there something you particularly like or have found useful? Drop us a line,
and we will do our best to ensure that your suggestion is included in the next
release of our documentation: documentation@businessobjects.com.
Note: If your issue concerns a Business Objects product and not the
documentation, please contact our Customer Support experts. For
information about Customer Support visit: http://www.businessobjects.com/
support.
Customer support, consulting and training

A global network of Business Objects technology experts provides customer
support, education, and consulting to ensure maximum business intelligence
benefit to your business.
How can we support you?

Business Objects offers customer support plans to best suit the size and
requirements of your deployment. We operate customer support centers in
the following countries:
• USA
• Australia
• Canada
• United Kingdom
• Japan
Online Customer Support

The Business Objects Customer Support website contains information about
Customer Support programs and services. It also has links to a wide range of
technical information including knowledgebase articles, downloads, and
support forums.
http://www.businessobjects.com/support/
Error Messages Explained143

Customer support, consulting and training
Looking for the best deployment solution for your

company?
Business Objects consultants can accompany you from the initial analysis
stage to the delivery of your deployment project. Expertise is available in
relational and multidimensional databases, in connectivities, database design
tools, customized embedding technology, and more.
For more information, contact your local sales office, or contact us at:
http://www.businessobjects.com/services/consulting/
Looking for training options?

From traditional classroom learning to targeted e-learning seminars, we can
offer a training package to suit your learning needs and preferred learning
style. Find more information on the Business Objects Education website:
http://www.businessobjects.com/services/training

Business Objects Information Resources
Useful addresses at a glance 13
Useful addresses at a glance
Address Content
Business Objects product Information about the full range of
information Business Objects products.
http://www.businessobjects.com
Product documentation Business Objects product
http://www.businessobjects.com/ documentation, including the
support Business Objects Documentation
Roadmap.
Business Objects Documentation Send us feedback or questions
mailbox about documentation.
documentation@businessobjects.com
Online Customer Support Information on Customer Support
http://www.businessobjects.com/ programs, as well as links to
support/ technical articles, downloads, and
online forums.
Business Objects Consulting Information on how Business
Services Objects can help maximize your
http://www.businessobjects.com/ business intelligence investment.
services/consulting/
Business Objects Education Information on Business Objects
Services training options and modules.
http://www.businessobjects.com/
services/training
Error Messages Explained145

Useful addresses at a glance

Error Message Guide

Uploaded by

Error Message Guide

Uploaded by

Error Messages Explained

BusinessObjects XI Release 2 Update

Windows and UNIX

Copyright Copyright © 2006 Business Objects. All rights reserved.

Chapter 1 Setup Error Messages 17

Chapter 2 Administration & Security Error Messages 25

Chapter 3 Universe Error Messages 33

Chapter 4 Document and Universe Exchange Error Messages 39

Chapter 5 Data Access Error Messages 63

Chapter 6 Web Intelligence Error Messages 77

Chapter 7 Miscellaneous Error Messages 107

Chapter 8 Crystal Reports Error Messages 111

Chapter 9 Enterprise Performance Management Error Messages 115

Chapter 10 Process Tracker Error Messages 125

Chapter 11 Report Conversion Tool Error Messages 129

Chapter 12 Question Designer and Intelligent Question Error Messages 135

Appendix A Business Objects Information Resources 141

Error Messages Explained 3

4 Error Messages Explained

Error Messages Explained 5

6 Error Message Guide

Error Messages Explained 7

IQ 00015 Couldn’t log on to Business Objects Q

8 Error Message Guide

Error Messages Explained 9

10 Error Message Guide

Error Messages Explained 11

12 Error Message Guide

Error Messages Explained 13

14 Error Message Guide

Error Messages Explained 15

16 Error Message Guide

Setup Error Messages

Setup error messages

This Business Objects distribution only supports Solaris 8. (STU 00005)

This Business Objects distribution only supports AIX 5. (STU 00005)

ProductID.txt file not found. (STU 00006)

Impossible to retrieve files from <directory>. (STU 00007)

18 Error Messages Explained

You did not provide the CD <diskNumber>. (STU 00008)

The distribution is already installed in this directory. (STU 00009)

Patch directory is not correct. (STU 00019)

Temporary directory is not correct. (STU 00020)

Error Messages Explained 19

Installation directory is not correct. (STU 00021)

Source directory is not correct. (STU 00023)

Installation directory is needed. (STU 00024)

Source directory is needed. (STU 00026)

Unknown feature <feature>. (STU 00027)

Unknown language <language>. (STU 00028)

Current language is not one of the installed languages. (STU 00029)

20 Error Messages Explained

Error Messages Explained 21

Feature <feature> is already installed. (STU 00040)

Feature <feature> is not installed. (STU 00041)

Impossible to create temporary file <file>. (STU 00050)

Impossible to create <directory>. (STU 00051)

Impossible to copy files to <directory>. (STU 00052)

winstall has already been copied to this directory. (STU 00053)

22 Error Messages Explained

Impossible to upgrade this installation release. (STU 00072)

You can't install this patch on this version. (STU 00080)

Error Messages Explained 23

Patch <patchname> is already installed. (STU 00082)

Patch <patchname> not found. (STU 00083)

This patch has not been installed. (STU 00091)

Impossible to access <pathDirectory>. (STU 00092)

24 Error Messages Explained

Administration & Security

Administration & Security error messages

Cannot connect to the universe domain. (ADM0012)

Too many candidates (ADM0017)

Unsupported RDBMS (ADM0026)

26 Error Messages Explained

Error Messages Explained 27

Parent class definition is incorrect. (ADM0070)