MAXIMO Knowledge Base - "Assert Statement Failed" error when submi... http://support.mro.com/websup/mrokb.nsf/16b52279f7510b6d85256f13...

Print | Email this doc

"Assert Statement Failed" error when submitting reports in Maximo

Enterprise Suite.
Document Info
Overview : When launching a report in Maximo Enterprise Suite, you may receive the Doc ID: M04656
"Assert Statement Failed" error. This can occur if the actuate connectstring property set in Product:MAXIMO
the maximo.properties file does not match the tns alias in the tnsnames.ora file or the SQL 6.2,
Version:
Server DSN on the actuate server. This error will appear for ALL reports if this property is 6.1, 6.0
incorrect.

The error in the browser will appear as follows:

Related Info
Find all the
important
information
Solution: including
downloads and
1. This problem can occur is the connectstring in the maximo.properties file does not documentation
match a tns alias or a System DSN on the Actuate server Maximo 6.2
Release Page
On the Maximo Server, navigate to \Maximo\applications\maximo\properties folder and
open the maximo.properties file with a text editor. Locate the following entry: Maximo 6.1
Release Page
// Actuate database connection string.
mxe.report.actuate.db.connectstring=max6
Maximo 6.0
This property is used by the Actuate encyclopedia to access the database, and needs to Release Page
reference the same database to which the Maximo application is connected.

For Oracle, the connectstring is the tnsnames.ora alias of the sid. You will need to open the
tnsnames.ora file located on the Actuate server under the oracle client directory and verify
that the alias is identical to the connectstring property specified in the maximo.properties file.
For example, in the above property, max6 is specified as the connectstring. In the
tnsnames.ora file, max6 must also exist as the alias for the database SID. Below is a sample
from the tnsnames.ora file showing the database alias as max6 for the service name of
maximo6.
max6 =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = MXDbase)(PORT = 1521))
)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = maximo6)
)
)

For SQL Server, you would need to configure an ODBC entry on the Actuate srever
specifying a name that matches the connectstring in the maximo.properties file mentioned
above. So if your connectstring is set to max6, you will need an ODBC entry called max6
pointing to your Maximo database.

If you have any questions about creating an ODBC connection for Maximo, you will find
detailed instructions on support.mro.com.

If you are using a case sensitive SQL Server database, and the maximo (dbo) user is created
in lower case, this would cause reports to fail.

1 of 3 5/23/2007 11:17 AM
MAXIMO Knowledge Base - "Assert Statement Failed" error when submi... http://support.mro.com/websup/mrokb.nsf/16b52279f7510b6d85256f13...

If the maximo.properties and (Actuate) maximo_rsse.properties and ODBC all in lower case
the import would work. However, when you try to execute a report you would get an assert
statement failed error message.

The work around would be to re-alias the dbo to an UpperCase MAXIMO. The
maximo.properties and (Actuate) maximo_rsse.properties and ODBC connection would all
have to be changed to Upper case and ears rebuilt and re-deployed.

Please note that if you make a change to the maximo.properties file, you must
rebuild/redeploy your maximo.ear file. For information on rebuilding and redeploying ear
files, please refer to the Maximo Installation Guide included on the On-line Documentation
CD.

2. If using Oracle as the database platform, you need to ensure that the reference to the
mroConnect.xml is listed in the Actuate XML file.
A) On the Actuate Server. navigate to the \Actuate8\iServer\etc (Windows) or \AcServer\etc
(UNIX) folder and open the acserverconfig.xml with a text editor. Search for the string
ConnConfigFile
On Windows OS, it would appear as follows:
ConnConfigFile="C:\Actuate8\iServer\bin\mroConnect.xml"

If this entry does not exist, add it to the Server section on the line following the ActuateBuild
entry. Below is a sample of how it should appear in the server section of the xml file.

<Servers>
<Server
Name="ActServer"
PMDPort="8100"
OSVersion="Windows 2000"
ActuateBuild="80B050401"
LogDirectory="C:\Actuate8\iServer/log"
PMDIPAddress="ActServer"
ActuateVersion="8 Fix 5"
ConnConfigFile="C:\Actuate8\iServer\etc\mroConnect.xml"
ServerIPAddress="ActServer"

Save the file.

B) In the same Actuate8\iServer\etc folder, open the mroConnect.xml. This file contains
references to the oracle dll that was specified during the actuate install. If you installed using
Oracle 9i, you will see references to acorcl90 throughout this file. Verify that this file contains
the correct version of the oracle dll that is installed on the Actuate server.

Please note that if you make any changes to the acserverconfig.xml or mroConnect.xml, you
will need to restart the Actuate Process Management Daemon service or PMD.

3. This error can also be encountered if running an Oracle 10G client on the Actuate server to
connect to the database. Currently, an enhancement is pending for support of Oracle 10G
client on the Actuate server. However, the current workaround for this issue is to install an
Oracle 9.2 oracle client on the Actuate server. This can be used to connect to an Oracle 10G
database.

Any questions or concerns regarding this article can be directed to MRO Support Services.

Did you find this document helpful: Yes No

2 of 3 5/23/2007 11:17 AM
MAXIMO Knowledge Base - "Assert Statement Failed" error when submi... http://support.mro.com/websup/mrokb.nsf/16b52279f7510b6d85256f13...

Legend
- Download File(s) - Tech Alert Notice - Knowledge Base Article

© 2007 MRO Software - Privacy Policy | Site Map | Contact Support Webmaster

3 of 3 5/23/2007 11:17 AM