virgilm - Friday, April 9, 2010 12:10 PM:
Just upgraded my server from 9.1 to 9.2 and now after loging in I receive two errors, the first a 401 error where the details looks like:
=================================================================================
<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.
=================================================================================
And the second one looks like :
=================================================================================
*** Wrong SOAP message! *** Error: <SPAN>*** Wrong SOAP message! *** Error: <SPAN>*** Wrong SOAP message! *** Error: <SPAN>
=================================================================================
After which the client comes up and works normally. However , when trying to set up a new client I found that the local client would hang when trying the download the ActiveX controls.
My workaround was to avoid doing a DNS search for the name of the server by directly specifying the server IP adress - ie instead of myservername.mydomain.com/InnovatorServer i switched to 192.168.255.255/InnovatorServer.
Once that was done all errors went away .
This is obviously a temporary fix that would stop working when the server IP address changes, but it will do until Aras finds and fixes the DNS lookup problem.
FoxyXI - Saturday, April 17, 2010 4:57 PM:
I get exactly the same messages, but also get them when specifying the IP address of the server directly. Aras does seem to be working correctly, but I am just starting to build up users and such so I don't know for sure.
zhigang.wang - Monday, May 17, 2010 12:15 PM:
i have the same question too,how to solve it?
virgilm - Monday, May 17, 2010 1:32 PM:
I think what we are running into here is a problem with the DNS server. What I found that the server I am running Innovator on has a different DNS name the the full computer name. I am now using the full computer name and everything seems to be working fine.
Iversen - Tuesday, June 1, 2010 4:39 AM:
I don't have any problems with the DNS and I also have the problem.
But I think this line cun be the problem:
at ASP.usernotifications_proxypage_aspx.ProcessRequest(HttpContext context) in c:WindowsMicrosoft.NETFramework64v2.0.50727Temporary ASP.NET Filesinnovator_92_test_notificationserver8f0fa9d0aa2f9bdaApp_Web_mttic0jk.0.cs:line 0
I think:
innovator_92_test_notificationserver should be: innovator_92_test/notificationserver
Iversen - Thursday, June 3, 2010 12:38 AM:
ARAS Support has given this answer.
- Open up Control Panel -> Programs and Features
- Select "Turn Windows features on or off" under the Tasks menu
- Install "Windows Authentication" under Internet Information Services -> World Wide Web Services -> Security
- Open up Control Panel -> Administrative Tools -> Server Manager
- Right click on Web Server (IIS) under the Roles on the TOC and select "Add Role services"
- Install the "Windows Authentication" role service located under Security
And this work be me....
himanshukz - Sunday, July 25, 2010 11:25 PM:
Thanks a lot Henrik.
This solution really works.
-Himanshu
L.Kumar - Monday, August 2, 2010 1:26 AM:
Hi,
Can you please suggest how to resolve this issue in Windows XP.
Thanks,
L.Kumar
Harley - Wednesday, September 29, 2010 6:03 PM:
Is there a resolution for this problem that can be applied to Windows Server 2003?
PedroRosa - Wednesday, April 13, 2011 6:59 AM:
Hello all.
After days of configurations and several erros passed, I finally stumbled on this one.
Got the following configuration:
- Windows Server 2008 R2 Standard, Portuguese language
- SQL Express 2008
I simply can't figure why it keeps poping the same error.
I've configured Windows Authentication and edited web.config to add the specific user for my server language.
Any more clues how to suprass this?
Trying to put Aras into a project for this year, but simply can't evaluate it :(
Joerg_Hermes - Tuesday, August 3, 2010 3:00 AM:
Hi,
i install ARAS 9.2 on a Windows Server 2003 R2 .
After installation i got the same Error Message as the posts before. *** Wrong Soap message
/innovatorServer/NotificationServer
I try to adapt the 2008 problem solution to IIS 6.0 But have not positive effects.
Can somebody help ?
Thanks,
Joerg
drnorthcott - Tuesday, April 26, 2011 8:33 PM:
We are having the same issues. When we are internal we can address the server directly using an IP address, the problem goes away. However from outside the network the error happens. I've tried:
-notificationserver.dll patch
-Checked the language issue
-Enabled Windows Authentication (on 2003 SBS server)
But it still happens. To reduce the annoyance, since we are not using the notification messages, I edited the "MessageCheckInterval" variable to add a bunch of zeros to the end (900000000 instead of 900000). I get the message(s) once when I log in and then I have not experienced it again. I think this should last about 7 days before it happens, most people will not be logged in that long...
Danny
carterdawson - Tuesday, May 24, 2011 11:30 PM:
I'm in the same situation as you are, Danny, where all of the suggested fixes have failed, and I've decided on the same course of action, which is to disable the Notification capability altogether.
Rather than change the MessageCheckInterval variable, though (which is a great idea), I went into the file
C:Program FilesArasInnovatorInnovatorClientjavascriptuser_notifications.js
and commented out the following lines, near the top of the file:
//this.UpdateMessageCollection();
//setTimeout('top.aras.UserNotification.StartIterativeUpdateMessageCollection()', this.CheckInterval);
After telling IE to clear the browser cache, the user is never presented with that error, not even once.
Good luck!
Shaun
