Essbase Agent Error

Question

Whenever we try to connect to the Essbase Server from the eas console, we get this error:
Network Error 10061: Unable to connect to <servername>
The client timed out waiting to connect to Essbase agent using TCP/IP.
Check your network connections.
Also make sure that server and port values are correct.
When we login to the server, we see this error:
Essbase Agent encountered a problem and needed to close.
In the OPMN logs, we see this:
[2011-01-22T17:41:44][opmn][ERROR:1][661][OPMN]Process Crashed: Essbase1~EssbaseAgent~AGENT~1 (1461847556:3136) - Not restarting
What does this mean?
The connections were working fine until last week. If I restart OPMN, then everything is fine-again the same problem starts the next day.
Please help with suggestions to troubleshoot.
Thanks,
Sujani                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

Answer 1

784749 wrote:
I checked the Essbase.cfg file-it has the correct port number:1423 listed.
I also tried starting Essbase in the foreground: startEssbase.bat
It says:
fatal error:ESSBASE is already loadedfatal error:ESSBASE is already loaded ....This means your Essbase.exe is working fine...but we need to know that on which port its processing...
Find out on which port it is processing...
i will tell you the steps to check the prot number....please find below...
How do I find the Ports?
*1.     Export the list of currently running tasks to a text file.*
a.     From the Start menu, click Run.
b.     In the Run dialog box, type: CMD. Click OK.
c.     At the command prompt, type: tasklist /svc > c:\tasklist.txt. Press the ENTER key on your keyboard.
Note: If using Windows XP Home Edition, tasklist may not be a recognized command. If this is the case, the Process Identifier (PID) must be found using Windows Task Manager. Open Windows Task Manager, click the Processes tab, click View, and then click Select Columns. In the Select Columns dialog box, check PID (Process Identifier), and then click OK. Locate the program you are troubleshooting and find the corresponding PID number.
*2.     Export the list of currently open ports to a text file.*
a.     At the command prompt, type: netstat -aon >c:\netstat.txt. Press ENTER.
View Picture
*3.     Open tasklist.txt.*
a.     From the Start menu, click Run.
b.     In the Run dialog box, type: c:\tasklist.txt. Click OK.
*4.     In the tasklist file, locate the program you are troubleshooting. Note the Process Identifier (PID) for the process. In this example we are troubleshooting Windows Media Player (wmplayer), which is PID 1988.*
View Picture
*5.     Open netstat.txt.*
a.     From the Start menu, click Run.
b.     In the Run dialog box, type: c:\netstat.txt. Click OK.
*6.     In the netstat file, find an entry with the same PID as you found in the earlier step. In this example, we are finding PID 1988.*
View Picture
*7.     In the netstat file, note the protocol used (TCP or UDP) for the PID you found. In this example, the protocol is UDP.*
*8.     In the netstat file, note the port number for the PID you found. The port number is the number following the IP address in the Local Address column. In this example, the IP address is 127.0.0.1 and the port number is 1081. Windows Firewall requires the port number and the protocol to create an exception. In this example, the port number is 1081 and the protocol is UDP.*
Note: If the port number(s) for the process are less than 1024, it is likely that the port numbers will not change. If the numbers used are greater than 1024, the application may be using a range of ports, so opening individual ports may not reliably resolve the issue.
Check it and let me know on which port number the Aggent is running...if it is not running on port number 1423 you will get this error....
Regards,
Prabhas...
Edited by: P on Feb 9, 2011 9:55 PM
Edited by: P on Feb 9, 2011 9:56 PM
Edited by: P on Feb 9, 2011 9:57 PM