locked
PerformancePoint Dashboard - "An unexpected error occurred." RRS feed

  • Question

  • I have installed MOSS 2007, PPS on Windows 2003 server.

    I can able to access the PerformancePoint Dashboard webparts in the same machine. (using url http://localhost:1234/Site1/..)
    But if i try to acces the same url in the internet using http://xx.xxx.x.xx:1234/site1, then i can able to browse the website. But all the dashboard web parts are throwing the error "An unexpected error occurred.". Few other dashboard webparts are giving message like "Updating ..."

    Please help.

    - Saravana Gandhi. K

    Thursday, October 29, 2009 2:39 PM

Answers

  • So, our configuration was missing the JSON Handler (We're running under IIS 7, so it's in the system.webServer/handlers instead of system.web/httpHandlers

    Here's the configuration line:

     

    <add name="JSONHandlerFactory" path="*.json" verb="*" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" resourceType="Unspecified" preCondition="integratedMode" />

     

    Friday, February 4, 2011 3:33 PM

All replies

  • Hi Saravana Gandhi,

    Please clarify whether the user is connecting Intranet / Internet.  If it is extranet scenario then you need implement what is mentioned in TechNet WhitePaper http://technet.microsoft.com/en-us/library/dd861515.aspx  Note: Dashboard Designer is not supported in Extranet Scenario

    I hope you tried ping the server from the client workstation, can you install Dashboard Designer just for testing to make sure the connectivity.

    Thank you,
    Sundar - MSFT
    This posting is provided "AS IS" with no warranties, and confers no rights.
    Thursday, October 29, 2009 3:11 PM
  • Hi Saravana,

     

    Were you able to figure out what was causing the problem?  I've run into this a couple of times too, and can't remember how I fixed it in the past, etc.

     

    -Matt

    Friday, February 4, 2011 2:49 PM
  • So, our configuration was missing the JSON Handler (We're running under IIS 7, so it's in the system.webServer/handlers instead of system.web/httpHandlers

    Here's the configuration line:

     

    <add name="JSONHandlerFactory" path="*.json" verb="*" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" resourceType="Unspecified" preCondition="integratedMode" />

     

    Friday, February 4, 2011 3:33 PM