gunner - Monday, October 17, 2011 11:12 PM:
I was trying to setup a Custom report I had built and place this in the ARAS reports screen for the users to access. I went to the TOC, Reports, typed in the details on the Report tab page and when I went to select the menu option "Report Manager" I got this error:
Server Error
404 - File or directory not found.
The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.
It sounds like it does not appear to be ARAS related, more of a IIS side issue? But also sounds like perhaps ARAS settings? Seems when I select the Report Manager option - either way - in ARAS I get this message.
Are there any settings file I should be looking at or required to change something to fix this?
Appreciated for any tips or hints?
Thanks...
eric_h - Tuesday, October 18, 2011 6:56 PM:
Gunner,
I had never used the 'Report Manager' before (didn't know at first where to even find it), but since I have been messing with reports I thought I'd take a look at this:
Turns out 'Report Manager' is a report tied to the Report item type. When I opened up the report itself, the first thing I noticed is there is not a defined report query. Maybe this does not matter, but I have never seen this before (in my somewhat limited) report experience. So then I took a look at the associated XSLT stylesheet. One thing I noticed is that most of the stylesheet is CSS style information, but this part stood out:
<body onload="location='/Reports'">
</body>
It appears that the body wants to load '/Reports' via the onload (JavaScript) event. In fact, if you look at the source of the error page you get, you'll see that Innovator is trying to open up a '/Reports' directory at the root of the IIS server (not even root of the Aras instance running in IIS). But this just does not exist. So you get a 404 'resource not found' error.
Actually, it turns out when you open an existing report or create a new one, it opens up the report manager. So I guess I have been using the report manager all along. My guess is that this is historical baggage having the report manager accessed via the 'Report Manager' report tied to the Report item type. If this is not needed, Aras should remove the association from the Report item type and just delete the report. Of course, maybe this needs to stay because of legacy systems, but I am guessing this might just be cruft lost in the shuffle. I could be wrong.
Eric
