Actuate 8 Import Error

浪迹天涯

Overview : When installing the Actuate Integration component in Maximo Enterprise Suite (MXES) or performing the ACIMPORT command, you may encounter the error \"Specified user name or password is incorrect or this user does not have administrator privilege.\" This occurs when using the Maximo Administrative username maxadmin. You will get a similar error if trying to login to the Actuate volume via the Management Console as this user. The error in the rsse log file will show \"InvalidPasswordException: Invalid Password for user: maxadmin; RSSE CODE: 104\".

Solution This error can occur for a number of reasons. These include errors starting MXServer, the location of the Actuate install, the Maximo jar files not synchronized with the Actuate jar files, etc. Given the nature of the issue, there are a number of steps listed below but any one of these steps can resolve the issue. It is important to test after each process to see if the error has been corrected. Points to consider:

The Maximo instance must be started and free of startup errors prior to running the Actuate integration or acimport command. You must be able to login to the Maximo application using your maxadmin username and password. Actuate cannot be installed in a directory that contains spaces. The Actuate server must have a client connection to the database. For Oracle, this would be through tnsnames. For SQL Server, there must be an ODBC present on the Actuate server to connect to the database.
• The cache timeout setting for the Open Security should be set to 1 Minute - down from 60 Minutes. To do this, perform the following:
  - Access the Actuate System Administration via acadmin - http://servername:8900/acadmin
  - Login to System Administration as user Administrator
  - Click the System Volumes link and then click your volume name. Under the Open Security tab, set the Cache Timeout to 1.
  - Click OK and logout of the System Administration.

The remainder of this article includes the various steps to follow in troubleshooting / correcting this issue.

1) The following configuration files contain your Actuate server name and volume information. The references to the name of your server and volume should be consistent from one file to another. If they do not match you may receive the error noted above. Please check the following files and ensure that the values for the iServer and volume are correct and consistent.

- <MAXIMOROOT>\\applications\\maximo\\properties\\maximo.properties (if changed, rebuild maximo.ear) - <MAXIMOROOT>\\applications\\activeportal\\WEB-INF\\web.xml (if changed, rebuild acweb.ear) - Actuate8\\iServer\\etc\\acserverconfig.xml (if changed, restart the Actuate Process Management Daemon service - PMD) - Actuate8\\iServer\\etc\\acpmdconfig.xml (if changed, restart the Actuate Process Management Daemon service - PMD)

2) This issue can occur if Maximo is unable to bind to port 1099 upon startup. This is the default port for binding but if another process is using this port, Maximo will bind to an alternate port. Since the RSSE component (Report Server Security Extensions) also has reference to this port, the port will need to be changed to match that to which Maximo is binding. To correct this issue, we will hardcode another unused port for binding.

- In the <MAXIMOROOT>\\applications\\maximo\\properties\\maximo.properties file, you will see the following:
mxe.rmi.port=0

On the line below this entry, add another line as follows :
mxe.registry.port=9898

This is how it should appear when finished:
mxe.rmi.port=0
mxe.registry.port=9898

*The port can be any available port on the system - 9898 is just for example purposes. To check which ports are available, do a netstat a and see which ports are being used. Use a port that does not appear in this list.

- In the Actuate8\\iServer\\etc\\rsse_maximo.properties, change the maximo.port value to match the registry port specified in the maximo.properties file.
For example,

#Rmi registry port for maximo. Default is 1099 if left blank.
maximo.port=9898

- Once the changes have been made to each file, you will need to rebuild the maximo ear file and restart the webserver.
- Restart the Actuate PMD service.
- Wait for 1 minute after the PMD starts and then access the acadmin via http://servername:8900/acadmin. In the dropdown, select the volume and try logging in as your maxadmin user. If the error persists, continue to the next step.

3) Another reason for this error could be that the businessobjects.jar file for Maximo is out of sync with the actuatebo.jar file for Actuate. This can happen if Maximo was updated to a new patch level but a new jar file wasn\'t updated on the actuate server.

To determine if this is a problem, perform the following:
- Stop the Actuate Process Management Daemon (PMD) service under Control Panel.
- Navigate to the C:\\Actuate8\\iServer\\servletcontainer\\webapps\\acrsse\\WEB-INF\\lib directory. Rename the actuatebo.jar to be actuatebo_orig.jar
- Navigate to the MAXIMO\\deployment\\default folder and open the maximo.ear file with winzip. Locate the businessobjects.jar and extract it to the actuate folder listed above - in place of the actuatebo.jar
- Restart the PMD
- Wait for 1 minute after the PMD starts and then access the acadmin via http://servername:8900/acadmin. In the dropdown, select the volume and try logging in as your maxadmin user. If the error persists, continue to the next step.

*If this suggestion resolves the issue, please contact MRO Support Services to obtain a valid actuatebo.jar for your patch level.

4) Another reason why this error can occur is if the RSSE component is using cached information. To eliminate this issue, it is recommended to \"refresh\" the RSSE Service by following the following steps:

- Stop the Actuate PMD process.
- Navigate to the Actuate8\\iServer\\etc folder and open the acserverconfig.xml file with notepad. Locate the following line:
EnableRSSEService=\"true\"
Change this value to false and save the file
- Go up one directory level to the iServer folder and delete the encyc folder
- Restart the Actuate PMD Service
- Login to the Actuate acadmin via System Administration. Click the System Volumes link and then click the volume name listed. Under the Open Security tab, select the radio button to enable as a webservice. Click OK and logout.
- Stop the PMD again
- In the Actuate 8\\iServer directory, delete the new encyc folder that was created ( this is created with each restart)
- Restart the PMD.
- Wait for 1 minute after the PMD starts and then access the acadmin via http://servername:8900/acadmin. In the dropdown, select the volume and try logging in as your maxadmin user.

If you have any questions or concerns pertaining to this article, or if you require additional assistance, please contact MRO Support Services.

walner

上述办法测试过，相应方案无法解决，实际的原因是因为在以前的版本中没有MAXADMIN这个用户，所以需要在sysadm组中加入MAXADMIN用户再启动就可以了。

iss_hanson

导入空库时候没有sysadmin组，遇到这个问题怎么办呢？自己重新建一个sysadmin，按照你说的处理，导入百科全书还是报错同样的错误！

snow.lovers

非常简单的问题，楼主的错误在于不认真看安装手册

27357487

我有次就因为没有仔细看安装文档，把服务器搞的都不能远程连了 [s:13]