hiker-az - Wednesday, November 7, 2007 3:18 PM:
Followed the install instructions when I attempt to login I get a "Page not found" message in the IE browser. The IIS virtual directory is named InnovatorServer.
I have tried from the localhost: localhost/InnovatorServer http://<servername>/InnovatorServer and same results. If I just do http://localhost I do see the Under Construction page.
I have also tried access from a client machine with the above same results - page not found. Obiously I didn't use localhost but the IP address and the servername.
2003 R2 64-bit
Sql Server 2005
.Net 2.0
Bill - Friday, February 29, 2008 9:35 PM:
I believe that IIS is set to prohibit .NET 2.0 Web Extension. Please look in the IIS manager and make sure ASP.NET v2.0.50727 is set to Allow in the Web Extentions.
-Bill
sas0 - Wednesday, March 5, 2008 7:35 AM:
Bill:
I believe that IIS is set to prohibit .NET 2.0 Web Extension. Please look in the IIS manager and make sure ASP.NET v2.0.50727 is set to Allow in the Web Extentions.
-Bill
Hi,
I think I'm having the same problem, but dont' see where in IIS you can set it to Allow the .NET 2.0 web extensions? Can you be a little more descriptive where this is added?
Thanks!
sas0 - Wednesday, March 5, 2008 7:42 AM:
I see how to change it now... in IIS I was looking under:
local computerWeb SitesDefault Web Sites
it's under
local computerWeb Service Extensions
sas0 - Wednesday, March 5, 2008 8:07 AM:
After changing IIS to allow .NET 2.0 extensions, it now seems to try to open the page.
However, when I try to browse to the page the address bar look like it's redirecting and loading but then you hear the IE 7.0 "popping" sound like it's trying to kill a popup.
I've gone through both "Aras Innovator 8.1 - .NET Client Configuration.pdf" & "Aras Innovator 8.1 - Internet Explorer Client Machine Configuration.pdf" to confim the browser setting are as listed in those .pdf's.
Any thoughts or way to diagnose?
Edit... I had to explicitly disable the IE 7 pop-up blocker: Tools>Popup Blocker>Turn off Popup blocker
Now I get the pop-up with "Aras Innovator client has failed to initialize" though...I doubled checked the .NET 2.0 settings manually and they all look right...
sas0 - Wednesday, March 5, 2008 1:12 PM:
Finally got past the above mentioned "Aras Innovator client has failed to initialize" by changing the IIS virtual directory properties to Execute Permission = Scripts only.
There was a note in the forums which said,
The permissions must be Scripts only and not Scripts and Executables
Kamal Hammoutene - Thursday, June 30, 2011 9:21 AM:
After changing IIS to allow .NET 2.0 extensions, it now seems to try to open the page.
.......
I can confirm that authorizing IIS to run .NET extensions solves the problem on a fresh installation.
