This document explains how to troubleshoot missing icons in NFuse.
When logging into an NFuse web site, you see the names of published applications but instead of an application icon you see a red X. This situation can be caused by one of the following scenarios:
1. Web root is misconfigured in NFuse.conf
When you install NFuse, you are asked for the location of your web server document root. Typically, this is C:Inetpubwwwroot on Windows servers. This means if your IIS server is called myserver, when you browse to http://myserver/default.htm you are loading the file stored beneath the C:Inetpubwwwrootdefault.htm directory.
The NFuse Java Objects need to know where the document root is, and an NFuseIcons folder must exist beneath the document root. The location of the document root is specified in NFuse.conf by the UrlMapping./ entry. If you change your web server document root after installing NFuse, you must update this value in NFuse.conf. You must also create a folder named NFuseIcons beneath the new document root so that the NFuse Java objects can create and publish icons with a virtual path of http://myserver/NFuseIcons.
2. Insufficient permissions on the NFuseIcons folder
The NFuseIcons folder referenced by NFuse.conf and discussed in the previous step must be editable by the web server user account. By default, IIS runs as a local account named IUSR_MachineName. For example, if your IIS server is called myserver then the account would be named IUSR_MYSERVER.
When NFuse receives application icons from the XML service, the web server process will attempt to write these icons to disk. The path to which the icons are written is determined by concatenating two values in NFuse.conf: UrlMapping./ and SessionField.NFuse_IconCache.
On IIS servers, NTFS permissions should be set so that the IUSR_MachineName account (or whatever account IIS runs as) has at least Modify permission on the NFuseIcons folder.