IT Management Suite

 View Only
  • 1.  How to fix remote reports in a hierarchy are giving 404 errors in SMP 7.x

    Posted Oct 17, 2014 12:14 PM

    Dear All,

    I have a hierarchy with three servers and when I execute reports from the parent to either of the children (or back), I get 404 errors.

    I think that I know the reason for this, as the URL for the remote server is http://server.fqdn.com/ReportEtc and I am accessing the originating server using http://servername/. If it restructure the report on the originating server to use the http://servername/ structure in IE, then the report works. the sorts of reports are hierarchy ones and global reports that then go to the Child Servers or vice versa.

    This was happening on the system when it was SMP 7.1 SP2 MP1 and it is now happening in SMP 7.5.

    How can I fix this? What configuration do I need to do to make it work, please?

    Kindest regards,

     

    QuietLeni



  • 2.  RE: How to fix remote reports in a hierarchy are giving 404 errors in SMP 7.x

    Broadcom Employee
    Posted Oct 17, 2014 02:00 PM

    Hi!

    If I'm not wrong, it takes same address for hierarchy reports like it is specified in Hierarchy page. Otherwise, if on Parent NS Server you've added 1st Child, using http://servername and 2nd Child with http://FQDN, then on attempt to open child NS report from Parent NS, it will use:

    I wonder, you're opening these reports from Console directly connected to Parent Server via RDC, or you're using I.E on workstation and trying to open Child NS reports from there? Then seems like you need to make sure that this workstation has correct network settings that allows to resolve these Child servers by hostname and by FQDN.



  • 3.  RE: How to fix remote reports in a hierarchy are giving 404 errors in SMP 7.x

    Posted Oct 20, 2014 09:13 AM

    Igor,

    Thanks for the response. Actually, I am using the Console on the Parent or Child Servers and not from a PC (I do not have such access).

    Each child was using the Server Name, not FQDN. If I look at the ForwardServers table, I think that I see the FQDN, though.

    Hmmm.