I am having a similar problem. We have a site that uses child portals for each school. We want teachers to be able to run various reports. In a previous DNN site - no child portals everyone was on same portal - I designed ActiveReports (from Data Dynamics) and used the PDFExport() method to dump the report contents into an .aspx page. The .aspx page resided on the root of the DNN site and all user's could open the reports and had no problem.

Our new DNN site is on version 3.2.2. I tried the same technique. What is really weird is that for 1 1/2 days, the reports worked fine!! During testing I had several teachers sign on at the same time and run reports simultaneously making sure each saw their own data, etc, etc. Things were great. So, I began developing more reports. 1/2 way through the 2nd day, all the sudden anyone running any report has the following behavior - the report actually opens just fine, but after viewing the report, when they go to click on any element of the DNN window, they get the log in screen!! Same behavior happens even on the first reports, which I did not change in any way, shape or form!!!! The same reports that did not cause this behavior when we ran them the first day or two are now causing the same behavior!

My research has caused me to think that it has something to do with security issues  - the teacher accounts are all contained in child portals, they don't exist in the parent portal. I am trying to find out if our vendor made any changes that would explain why things worked fine for 1 1/2 days, but not now, but she has a hard time remember what she did on what day. I do know that she was in our system applying various updates (but supposedly just to vendor-supplied controls, not DNN itself). I followed some instructions I found for going into the file Manager and giving the teacher role permission to the .aspx file in the root directory. To no avail. I tried moving the reports into website/MainFolder/portalHTTPAlias/nameofreport.aspx. To no avail - actually this worked when I "hardcoded" the name of the portal into the javascript function, but when I had the program pass it in as a variable, somehow the portalHTTPAlias got changed to some seemingly arbitrary number making the resulting URL invalid, so of course, the page wouldn't display!! (Our system was designed by a vendor and they designed it so the portalHTTPAlias is the same as the school number instead of alpha characters, which makes sense for alot of reasons. Anyway, this didn't work.

Any suggestions, or help would be appreciated. On Friday afternoon I actually found a posting that talked about making changes to DNN HTTPHandler code. I am actually sick with sinus/ear infections and bronchitis, so I stopped work when I couldn't hold up any longer, thinking I saved the URL, but alas, in my drug-induced and sick-in-the-head state of mind I apparently didn't. Anyway, not feeling any better and still can't find this posting regarding making changes to some handler in DNN. If this rings a bell with anyone, I would be grateful for someone pointing me in the right direction. Also, I will re-read the postings here when I'm a little better and see if anything here can help me overcome my problem. Does it sound like this is similar to several of the other postings here?

Thanks, Patricia