Mitel Forums - The Unofficial Source
Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: Tnobrien on August 06, 2009, 10:26:07 AM
-
This was already posted once, but the answer didn't work for me and the topic was 120+ days old, so I'm reposting.
The issue is, every time I log into the ESM using the system password and choose "System Administration Tool" I receive
"Your session has time out. Please exit the application and log in again."
I logged out of the ESM and closed my browser, but still have this issue.
I tried several other workstations
I attempt to restart the WebServer, and here is the output from that:
Shell restarted
-> ts WebServer
ts WebServer
value = 0 = 0x0
-> tr WebServer
tr WebServer
value = 0 = 0x0
-> i WebServer
i WebServer
NAME ENTRY TID PRI STATUS PC SP ERRNO DELAY
---------- ------------ -------- --- ---------- -------- -------- ------- -----
WebServer websvxmain__ 3672800 160 PEND+T 132dc50 3f5ef90 3d0002 14
value = 0 = 0x0
-
You may just have to reboot.
Telnet to the system and do a scheduled reboot after business hours.
Command is
Prog reboot sched <mon, tue, etc> 2:15
then
Prog reboot sched on
Let it reboot overnight and try again.
Ralph
-
I did reset the first night this started occurring (I forgot to mention that). I will schedule a reboot and check it again.
Should this be done through the SSH connection Telnet?
Is that the exact format for the command?
Thanks.
-
You can do this through standard Telnet.
The above was the command syntax.
Ralph
-
And the telnet logon of admin/sx2000?
-
I never post passwords. Even default. No need to make it easier for hackers.
I'll PM you them.
Ralph
-
Your i WebServer information looks fine, this might be an IE problem, what version are you running and does your company change any settings on IE at all.
-
Ie 7. I also tried it on IE6 and on multiple computers. No, we don't do any restrictions on IE through policy if that's what you're referring to.
-
You may just have to reboot.
Telnet to the system and do a scheduled reboot after business hours.
Command is
Prog reboot sched <mon, tue, etc> 2:15
then
Prog reboot sched on
Ralph, in your PM you modified this to:
prog reboot sched thru 21:00
That worked, thank you. Now I'll see if a reboot gets it.
-
Hi I came accross the same fault on a couple of systems over here they where both on R6 I think. Have never had this problem with any systems R7 and up. What version is your system on?
-
R7.
-
Ok so you can log into the system via telnet but not the front end. In this case I don't think a reboot will work, but you never know. If this does not work, try a full shutdown and power up.
When I tried this problem in release 8ur5, the reboot of the controller did not work.
-
I scheduled a reboot based on the recommendations of Ralph and it worked. I had reset before and that didn't take. Thanks to all here who contributed. I will definitely stick around and help out the community where I can.