rrice - Thursday, June 3, 2010 8:56 AM:
Intermittant error. Not sure where it is comming from. Does not seem to stop the operation of the application, but I am new and may not realize that a function is not working :)
<html>
<head>
<title>The remote server returned an error: (401) Unauthorized.</title>
<style>
body {font-family:"Verdana";font-weight:normal;font-size: .7em;color:black;}
p {font-family:"Verdana";font-weight:normal;color:black;margin-top: -5px}
b {font-family:"Verdana";font-weight:bold;color:black;margin-top: -5px}
H1 { font-family:"Verdana";font-weight:normal;font-size:18pt;color:red }
H2 { font-family:"Verdana";font-weight:normal;font-size:14pt;color:maroon }
pre {font-family:"Lucida Console";font-size: .9em}
.marker {font-weight: bold; color: black;text-decoration: none;}
.version {color: gray;}
.error {margin-bottom: 10px;}
.expandable { text-decoration:underline; font-weight:bold; color:navy; cursor:hand; }
</style>
</head>
<body bgcolor="white">
<span><H1>Server Error in '/InnovatorServer/NotificationServer' Application.<hr width=100% size=1 color=silver></H1>
<h2> <i>The remote server returned an error: (401) Unauthorized.</i> </h2></span>
<font face="Arial, Helvetica, Geneva, SunSans-Regular, sans-serif ">
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Net.WebException: The remote server returned an error: (401) Unauthorized.
Source Error:
<table width=100% bgcolor="#ffffcc">
<tr>
<td>
<code>
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.</code>
</td>
</tr>
</table>
Stack Trace:
<table width=100% bgcolor="#ffffcc">
<tr>
<td>
<code><pre>
[WebException: The remote server returned an error: (401) Unauthorized.]
System.Net.HttpWebRequest.GetResponse() +5314029
Aras.Tools.ProxyHttpWebRequest.GetResponse() +15
Aras.Tools.ProxyPageHandler.InitializeProxySession(BaseRetargetProvider initialize_session_provider) +74
Aras.Tools.ProxyPageHandler.UserNotificationsHandler_Load(Object sender, EventArgs e) +226
System.Web.UI.Control.OnLoad(EventArgs e) +99
System.Web.UI.Control.LoadRecursive() +50
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +627
</pre></code>
</td>
</tr>
</table>
<hr width=100% size=1 color=silver>
Version Information: Microsoft .NET Framework Version:2.0.50727.4016; ASP.NET Version:2.0.50727.4016
</font>
</body>
</html>
<!--
[WebException]: The remote server returned an error: (401) Unauthorized.
at System.Net.HttpWebRequest.GetResponse()
at Aras.Tools.ProxyHttpWebRequest.GetResponse()
at Aras.Tools.ProxyPageHandler.InitializeProxySession(BaseRetargetProvider initialize_session_provider)
at Aras.Tools.ProxyPageHandler.UserNotificationsHandler_Load(Object sender, EventArgs e)
at System.Web.UI.Control.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
[HttpUnhandledException]: Exception of type 'System.Web.HttpUnhandledException' was thrown.
at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context)
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at ASP.usernotifications_proxypage_aspx.ProcessRequest(HttpContext context) in c:WindowsMicrosoft.NETFrameworkv2.0.50727Temporary ASP.NET Filesinnovatorserver_notificationserver1c3838b46265b3d4App_Web_ldqzr35s.0.cs:line 0
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
--><!--
This error page might contain sensitive information because ASP.NET is configured to show verbose error messages using <customErrors mode="Off"/>. Consider using <customErrors mode="On"/> or <customErrors mode="RemoteOnly"/> in production environments.-->
RobMcAveney - Thursday, June 3, 2010 11:38 AM:
This message is related to the notification server, which is a new feature that allows administrators to send out notifications to users (e.g. "System Maintenance at 6:00pm"). There have been some scattered reports of problems with it and the support team is looking into them.
rrice - Tuesday, September 14, 2010 2:15 PM:
Any updates?
RobMcAveney - Tuesday, September 14, 2010 2:57 PM:
Try this: http://www.aras.com/university/TechNotes/NotificationServer%20Additional%20Setup.pdf
rrice - Tuesday, September 14, 2010 4:09 PM:
Thanks Rob. I saw this in the other threads about SOAP errors, but I have server 2003R2 and am not sure if this applies. BTW the error is comming up about every 10 min but it does not take the application down. Just really annoying for everyone.
Harley - Wednesday, September 29, 2010 5:54 PM:
Thanks Rob. I saw this in the other threads about SOAP errors, but I have server 2003R2 and am not sure if this applies. BTW the error is comming up about every 10 min but it does not take the application down. Just really annoying for everyone.
I was also hoping to find a solution to this problem. Like rrice, I am also running the English language version of Windows Server 2003 and using the default port (80), so I am unable to make use of the solutions in the document Rob linked to.
Please help.
rrice - Thursday, September 30, 2010 12:01 PM:
Harley,
I was able to fix the problem by changing the windows authentication service as decribed in the other procedure. I was in a harder to find place in 2003. Under properties of the website in ISS console.
Harley - Tuesday, November 30, 2010 4:58 PM:
Harley,
I was able to fix the problem by changing the windows authentication service as decribed in the other procedure. I was in a harder to find place in 2003. Under properties of the website in ISS console.
Thanks very much!
