2010-03-16 16:24:40,996 [HttpProcessor[8900][1]] ERROR com.mro.actuate8.rsse.MerlinJDBCUserManagerModel - Failed to open database connection for url: jdbc:oracle:thin:@DXB-MAXDEV-XP:1521:maxtest2
java.sql.SQLException: ORA-01017: invalid username/password; logon denied
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:289)
at oracle.jdbc.ttc7.O3log.receive2nd(O3log.java:497)
at oracle.jdbc.ttc7.TTC7Protocol.logon(TTC7Protocol.java:279)
at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:365)
at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:547)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:347)
at java.sql.DriverManager.getConnection(DriverManager.java:512)
at java.sql.DriverManager.getConnection(DriverManager.java:171)
at com.mro.actuate8.rsse.MerlinJDBCUserManagerModel.getConnection(Unknown Source)
at com.mro.actuate8.rsse.MerlinJDBCUserManagerModel.getStatement(Unknown Source)
at com.mro.actuate8.rsse.MerlinJDBCUserManagerModel.getStatement(Unknown Source)
at com.mro.actuate8.rsse.MerlinJDBCUserManagerModel$ResultSetIterator.<init>(Unknown Source)
at com.mro.actuate8.rsse.MerlinJDBCUserManagerModel.getUsers(Unknown Source)
at com.mro.actuate8.rsse.MerlinJDBCUserManagerModel.userExists(Unknown Source)
at com.mro.actuate8.rsse.MaximoJDBCRSSE.doesUserExist(Unknown Source)
at com.actuate8.rsse.wsdl.ActuateSoapBindingImpl.doesUserExist(Unknown Source)
at sun.reflect.GeneratedMethodAccessor424.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.java:402)
at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:309)
at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:333)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:71)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:150)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:120)
at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:481)
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:323)
at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:854)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:339)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1027)
at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1125)
at java.lang.Thread.run(Thread.java:536)
2010-03-16 16:24:40,996 [HttpProcessor[8900][1]] DEBUG com.mro.actuate8.rsse.MerlinJDBCUserManagerModel - Statement is being released.
2010-03-16 16:24:40,996 [HttpProcessor[8900][1]] DEBUG com.mro.actuate8.rsse.MaximoJDBCRSSE - Does user maxadmin exist: false
|------+------|
|Document |M04750 |
|Number: | |
|------+------|
| | |
|------+------|
|Product: ||------| |
| || [X] MAXIMO | |
| || [ ] MAXIMO MainControl | |
| || [ ] MAXIMO Advantage | |
| || [ ] MAXIMO Asset Tracker | |
| || [ ] OCS | |
| ||------| |
|------+------|
| | |
|------+------|
|Release/Versio|6.0 |
|n: | |
|------+------|
|Revision: | |
|------+------|
|------+------+------|
|Title: |Actuate 8 Import Error: "Specified| |
| |user name or password is incorrect| |
| |or this user does not have | |
| |administrator privilege." | |
|------+------+------|
| | | |
|------+------+------|
|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". | |
|------+------+------|
|------|
|Contents: |
| |
| 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 the error persists, continue to the |
|next step. |
| |
|If you have any questions or concerns pertaining to this article, or if |
|you require additional assistance, please contact MRO Support Services. |
|------|