Shared Services and Financial Management

Subtopics

Application Creation Failure

Issue: You receive an Application Creation Fails error message.

Solution: Perform these tasks:

  • Review SharedServices_SecurityClient.log.

    If group cache errors are displayed, ensure that the group URL and filter are set correctly to accommodate group counts. If data broker property errors are displayed, enable interopjava logging. Use JRE 1.5 to support 1,000 or more groups.

    On the server, review SharedServices_Security.log.

    If errors relate to group caching, ensure that the group URL and filter are set to accommodate group counts.

  • Review the Financial Management logs. See “Financial Performance Management Applications Logs” in Using EPM System Logs..

  • Ensure that the Financial Management application server can communicate with Shared Services using HTTP and WEBDAV protocol. Webdav may be blocked if you proxy requests from IIS to interoperate with the Web application. If so, ensure that the UrlScan IIS extension does not block propfind methods.

    If you are using IIS on Windows 2003 SP1, add the IIS the UseBasicAuth registry key to dword 1 in the registry HKLM\SYSTEM\CurrentControlSet\Services\WebClient\Parameters.

  • If the interop Web site redirects to the Web application server, ensure that the authentication method is anonymous and that Windows integration authentication is not used.

Smart View Timeouts

Issue: Smart View with Financial Management times out after about 30 minutes.

Solution: Try one or more of these procedures:

  • Run the Server and Web configuration utility on the Financial Management Web server, and change the Web session timeout setting. (The default setting is 20 minutes.)

  • If the client is using the URL provider for Smart View (not the Shared Services provider), right-click for the properties of the HFMOfficeProvider virtual directory in IIS and click Configuration on the Virtual Directory tab. In the new window, click Options and change the session state timeout setting.

  • Change the setting of the default Web site.

Also check the timeout settings of the Default Web site and the Smart View Provider settings in the FM Server and Web Configuration.