RE: OWA 5.5 has just stopped and i can't start it again!
James, Update to SP6 (NT) on all the servers. Then update to SP4 on your Exchange 5.5 AND on the OWA/IIS box. This should fix it. This is a known issue with Exchange / NT and lower SPs. Bob Fronk, MCSE BTR Technologies, Inc. -Original Message- From: James Palmer [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 17, 2002 6:04 AM To: MS-Exchange Admin Issues Subject: OWA 5.5 has just stopped and i can't start it again! I am Using exchange 5.5 sp3 on one server and IIS4 with OWA 5.5 sp3 on another server. OS is NT4. OWA has just stopped, I rebooted both machines - still no joy. I then restored a backup - still no joy. The only error message that comes up if you leave it long enough is; error 'ASP 0113' Script timed out /exchange/USA/LogonFrm.asp The maximum amount of time for a script to execute was exceeded. You can change this limit by specifying a new value for the property Server.ScriptTimeOut or by changing the value in the IIS administration tools. I have checked the timeouts and they are fine. ANY IDEAS??? Regards, James Palmer E-mail mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] This e-mail has been scanned for all viruses by Star Internet. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: OWA 5.5 has just stopped and i can't start it again!
You may have a corrupt metabase.bin file. -Original Message- From: James Palmer [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 17, 2002 6:04 AM To: MS-Exchange Admin Issues Subject: OWA 5.5 has just stopped and i can't start it again! I am Using exchange 5.5 sp3 on one server and IIS4 with OWA 5.5 sp3 on another server. OS is NT4. OWA has just stopped, I rebooted both machines - still no joy. I then restored a backup - still no joy. The only error message that comes up if you leave it long enough is; error 'ASP 0113' Script timed out /exchange/USA/LogonFrm.asp The maximum amount of time for a script to execute was exceeded. You can change this limit by specifying a new value for the property Server.ScriptTimeOut or by changing the value in the IIS administration tools. I have checked the timeouts and they are fine. ANY IDEAS??? Regards, James Palmer E-mail mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] This e-mail has been scanned for all viruses by Star Internet. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: OWA 5.5 has just stopped and i can't start it again!
Title: RE: OWA 5.5 has just stopped and i can't start it again! Yep.. Bob hit it on the mark(or Bob).. that's your issue. -Original Message- From: Bob Fronk (BTR Technologies, Inc) [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 17, 2002 6:22 AM To: MS-Exchange Admin Issues Subject: RE: OWA 5.5 has just stopped and i can't start it again! James, Update to SP6 (NT) on all the servers. Then update to SP4 on your Exchange 5.5 AND on the OWA/IIS box. This should fix it. This is a known issue with Exchange / NT and lower SPs. Bob Fronk, MCSE BTR Technologies, Inc. -Original Message- From: James Palmer [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 17, 2002 6:04 AM To: MS-Exchange Admin Issues Subject: OWA 5.5 has just stopped and i can't start it again! I am Using exchange 5.5 sp3 on one server and IIS4 with OWA 5.5 sp3 on another server. OS is NT4. OWA has just stopped, I rebooted both machines - still no joy. I then restored a backup - still no joy. The only error message that comes up if you leave it long enough is; error 'ASP 0113' Script timed out /exchange/USA/LogonFrm.asp The maximum amount of time for a script to execute was exceeded. You can change this limit by specifying a new value for the property Server.ScriptTimeOut or by changing the value in the IIS administration tools. I have checked the timeouts and they are fine. ANY IDEAS??? Regards, James Palmer E-mail mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] This e-mail has been scanned for all viruses by Star Internet. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
