If you have developed or deployed Actuate 8 reports for Maximo 6, you have undoubtedly encountered this error many times. The problem is usually due to the fact that there is a connection problem to the database and it is the user account name that is causing this error. So when you try to run a report whether it be from e.Report designer or from Maximo the error you get is as follows:
This error doesn’t explain much as to why it’s happening and can be troublesome to fix. First and foremost, I would try to resolve this issue within e.Report designer before publishing it to your report server.
Before an Actuate report runs, it needs to be able to access the database with a valid username and password. This user account needs to have the right permissions to execute queries and so forth in SQL Server. The default user account for running reports is ‘MAXIMO’ so we will use that. Some of you may or may not use this account but whatever username you create for running your reports needs to be in upper case. This is very important. If you create a username in anything other that upper case, you will recieve this Actuate error. I think this the part that most people miss when running reports. Next, the ‘MAXIMO’ account needs to have permissions to execute queries. You can set this account to dbo owner running this command:
EXEC sp_changedbowner 'MAXIMO'
Once you have created a valid username and given it the right permissions, you should no longer be getting this error message while you are in e.Report designer running your report.
Now when you go to deploy your report on the server and still getting this error, you need to modify the maximo.properties file. I will assume that you have already created a valid ODBC on the report server that connects to your database and set the property to this:
// Actuate database connection string. mxe.report.actuate.db.connectstring=max6
where ‘max6’ is the name of your ODBC. Go to your rsse_maximo.properties file and ensure that the username is in upper case and of course you need to rebuild ears and redeploy once you make changes.
For more information and for Oracle databases, read this IBM KB article here.
UPDATE: If you are using SQL Server, do not use the ‘sa’ user to try and connect to the database. This will also give you the same error.