5 Replies Latest reply: Sep 3, 2013 4:57 PM by jonhwilliams RSS

    HFM 11.1.2.1 creating new app classic version

    872235
      We just installed the new HFM 11.1.2.1 as a classic version. We created a new application and registered it, but when I try to open it up, it gives me error ->

      Code: -2147217900Description: An error has occurred. Please contact your administrator.
      Actor: Hyperion.HFMErrorHandler.1Trace: Error Reference Number: {32C30A5C-0022-48FF-B560-631B4BCDB3E1};User Name: lx2@Native Directory<BR>Num: 0x80040e14;Type: 0;DTime: 6/29/2011 10:19:22 AM;Svr: SDCFGCT05;File: CHsxServerImpl.cpp;Line: 2025;Ver: 11.1.2.1.000.3082;<BR>Num: 0x80040e14;Type: 0;DTime: 6/29/2011 10:19:28 AM;Svr: SDCFGCT05;File: CHsxServerImpl.cpp;Line: 2361;Ver: 11.1.2.1.000.3082;<BR>Num: 0x80040e14;Type: 0;DTime: 6/29/2011 10:19:28 AM;Svr: SDCFGCT05;File: CHsxServerImpl.cpp;Line: 4092;Ver: 11.1.2.1.000.3082;<BR>Num: 0x80040e14;Type: 1;DTime: 6/29/2011 10:19:28 AM;Svr: SDCFGCT05;File: CHsxServer.cpp;Line: 1460;Ver: 11.1.2.1.000.3082;DStr: OpenApplication: FGCNEW;<BR>Num: 0x80040e14;Type: 0;DTime: 6/29/2011 10:19:27 AM;Svr: SDCFGCT04;File: CHsxClient.cpp;Line: 2417;Ver: 11.1.2.1.000.3082;<BR>Num: 0x80040e14;Type: 0;DTime: 6/29/2011 10:19:27 AM;Svr: SDCFGCT04;File: CHFMwManageApplications.cpp;Line: 213;Ver: 11.1.2.1.000.3082;

      This error message is certainly not helpful.

      I didn't get any error when creating it through either the web or the client. Server and app are registered and DCOM is enabled. The security on shared service looks fine. But there must be something I'm missing and I totally run out of clues. Could someone please help me out? Is it something related to server configuration? Any idea would be greatly appreciated! (btw, it's on IE8 and Windows 7)

      Thanks!
        • 1. Re: HFM 11.1.2.1 creating new app classic version
          CBarbieri
          The snippet you included here is insufficient to determine the problem. Please review all of the logs contained within the \Logs folder on each HFM application server. The most important is the HsvEventLog.Log file. Use the Win32 event log viewer utility on the server to read this, and perhaps it will reveal the root cause.

          --Chris                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               
          • 2. Re: HFM 11.1.2.1 creating new app classic version
            beyerch2
            Also note, that you may find more than one error some of which are more helpful than others...... If you want to post additional errors, be sure to include all relevant items.

            FWIW
            • 3. Re: HFM 11.1.2.1 creating new app classic version
              beyerch2
              I forgot to add....

              From what you posted, I'm guessing the issue is database related. SQL Server as the backend, perhaps?
              • 4. Re: HFM 11.1.2.1 creating new app classic version
                John A Booth
                Was this using the Hyperion sample application files or did you use files from another release? We have seen that an invalid .per file (from another release) will cause similar behavior -- if you used an older .per file I suggest you create a new one in 11.1.2.1 and re-create.

                Regards,

                John A. Booth
                http://www.metavero.com
                • 5. Re: HFM 11.1.2.1 creating new app classic version
                  jonhwilliams

                  On 11.1.2.2.xxx today, I confirm John's post is still accurate; Using the Sample applications appropriate to the patch level and release will resolve this issue.