<div dir="ltr">In addition to the ES that Scott suggested, a simple work around is also available. I would recommend an ES but see below to address your specific issue.<br><br><table class="table-formatted-alt-vborders" style="padding-bottom: 10px;" border="0" cellpadding="0" cellspacing="0" width="100%">
<tbody><tr valign="bottom"><th align="left">CSCsc86904 Bug Details
</th>
<th class="th-content-left" style="border-right: 1px solid rgb(204, 204, 204); font-weight: normal; padding-left: 10px; color: rgb(102, 102, 102);" align="right">
<br></th>
</tr>
</tbody></table>
<input name="appContext" value="/Support/BugToolKit" type="hidden">
<table border="0" cellpadding="5" cellspacing="2" width="100%"><tbody><tr>
<td colspan="2" style="padding: 8px; font-size: 88%;">
<span>
<strong> WS03: Cannot log back in to SA after timeout </strong>
</span>
</td>
</tr>
<tr>
<td style="padding: 0px 8px 8px; font-size: 88%;" valign="top">
<span>
<b>Symptom:</b><br><br>Cisco Unity administrators are unable to access the Cisco Unity System Administrator via Internet Explorer.<br><br><b>Conditions:</b><br><br>Seen
occasionally with Unity servers that run on Microsoft Windows Server
2003, typically after an SA session has timed out. Seen with Cisco
Unity 4.2(1) and Unity 5.0(1).<br><br><b>Workaround:</b><br>1) Restart the WWWP service.<br><br>or <br><br>2)
Increase the SA Session Timeout value in Internet Information Services
(IIS) Manger from the default of 20 minutes to 180 minutes, or more.
Additionally, there is evidence that the issue can be worked around by
setting the Idle Timeout to a value lower than the SA Session Timeout. <br>This doesn't prevent the problem, but it does decrease the chances of running into the problem.<br><br>Following
are detailed steps to increase both the session and the idle timeout
values, and to set the idle timeout to a value less than the session
timeout.<br><br>To Increase the Session Timeout <br>1. Go to Start->Programs->Administrative Tools->Internet Information Services (IIS) Manger.<br>2. In the left-hand pane, expand the tree for the local computer.<br>
3. Right-click the Default Web Site and select Properties.<br>4. Click the Home Directory tab. <br>5. Click the Configuration button.<br>6. On the Application properties sheet, click the Option tab.<br>8. Increase the session timeout from the default 20 minutes to the desired number (180 minutes or more, is fine).<br>
<br>To Change the Idle Timeout<br>9. In IIS Manager, expand the "Application Pools" folder.<br>10. Right-click on "DefaultAppPool" and select Properties.<br>11. Select the "Performance" tab.<br>
12. Change the value in "Idle timeout" to a couple of minutes less than the session timeout for the SA.<br>13. Press "Apply".<br>14. Restart the "DefaultAppPool"<br> <br>The
result will be that after the timeout fires, the browser window will
either close on its own or a dialog box will appear asking if you wish
to close the window. A new SA session can be opened by the Unity icon
in the System Tray.<br> <br>If you don't see the Application Pools
container in IIS Manager, do the following steps to display Application
Pools and then adjust the Idle Timeout. (See CSCsi42693 for additional
problems that happen when the Application Pools is not displayed in IIS
Manager.)<br><br>To Display Application Pools<br>1. Open IIS Manager (Click Start > All Programs > Administrative Tools > Internet Information Services (IIS) Manager.)<br>2. Expand the tree in the left pane.<br>
3. Right-click Web Sites and select Properties.<br>4. Click the Service tab.<br>5. In the Isolation Mode section at the top of the page, uncheck the check box "Run WWW service in IIS 5.0 isolation mode".<br>6. Click OK on the message box to restart IIS. The Application Pools container should now be displayed<br>
7. Close IIS Manager.
</span></td></tr></tbody></table><br><br><div class="gmail_quote">On Tue, Sep 9, 2008 at 3:40 PM, omar parihuana <span dir="ltr"><<a href="mailto:omar.parihuana@gmail.com">omar.parihuana@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div dir="ltr">Hi List,<div><br></div><div>I've just completed the Unity 5.x installation and so far all are working well, however some days ago, I cannot log into Administration web portal, it take a long time for connect (and finally it never connect). Today the same error appeared, after of put usr/pass the administration webpage never appeared. I've checked IIS service and is running, the first time, I restart the Unity and all start to work well. Today I've stopped the IIS service, and after that the Administration webpage start to work. I've checked Event viewer, and all seems ok! so what's happened? pls suggestion will be very appreciated.</div>
<div><br></div><div>Rgds.<br clear="all"><br>-- <br>Omar E.P.T<br>-----------------<br>Certified Networking Professionals make better Connections!<br>
</div></div>
<br>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br></div>