compukidmike - Wednesday, February 5, 2014 1:23 PM:
Hi, I'm having a problem with the new 10.0 release. I'm admittedly not an expert when it comes to configuring windows server, so please let me know if I screwed something up.
The install is fine, no errors, and I can log in (looking through other posts on this topic, I gather that this means SQL is working properly). The problem arises when I try to add new items or edit existing ones, I get a 404 error, stating that the page doesn't exist. The page it's looking for is indeed not there. Here's what it's looking for...
C:Program Files (x86)ArasInnovatorInnovatorClientscripts abItemView
I've tried everything I can think of, and searched for days for answers. I have created multiple new VMs, both server 2008 R2 and Win 7 x64. No matter what I do, it's the same thing.
I have searched the entire Innovator folder for that "tabItemView" file, and it's not there. I even extracted all the files from the installer, and it's not there.
Would any of you that got it working, be willing to check if that file is there in your installation?
Thanks,
Michael
bpb - Tuesday, March 4, 2014 3:56 PM:
I would just like to say I am having the same issue. If it's something wrong with IIS settings I wish somebody could point me in the right direction. Something with redirects? I'm just not sure what to check.
ergr - Friday, April 10, 2015 12:09 PM:
Hi,
Any one of you were able to get out of that problem? I am also facing the same error: 404 , Innovator/Innovator/client/scripts/tabItemView is not found.
Thank you
vasant - Monday, April 20, 2015 12:29 AM:
Hi,
Add below lines of script into Aras Installation @C:Program Files(x86)ArasInnovatorInnovatorweb.config
<modules runAllManagedModulesForAllRequests="true" >
<remove name="UrlRoutingModule"/>
</modules>
Thanks - Vasant
Jeroen Bosch - Monday, April 20, 2015 9:43 AM:
...
Add below lines of script into Aras Installation @C:Program Files(x86)ArasInnovatorInnovatorweb.config
<modules runAllManagedModulesForAllRequests="true" >
<remove name="UrlRoutingModule"/>
</modules>
...
Hi Vasant,
could you please explain what this script is doing?
Thank you,
Jeroen
vasant - Tuesday, April 21, 2015 12:20 AM:
Hi,
The IIS core engine uses preconditions to determine when to enable a particular module. Performance reasons, for example, might determine that you only want to execute managed modules for requests that also go to a managed handler.
You can also use a shortcut to enable all managed (ASP.NET) modules to run for all requests in your application, regardless of the "managedHandler" precondition.
To enable all managed modules to run for all requests without configuring each module entry to remove the "managedHandler" precondition, use the runAllManagedModulesForAllRequests property in the <modules> section:
<modules runAllManagedModulesForAllRequests="true" />
When you use this property, the "managedHandler" precondition has no effect and all managed modules run for all requests.
Thanks - Vasant
