"File or directory not found" errors when viewing the Home, Monitors or Reports pages in the Symantec Endpoint Protection Manager Console.
|Article:TECH96037|||||Created: 2009-01-08|||||Updated: 2010-08-18|||||Article URL http://www.symantec.com/docs/TECH96037|
While logged in to the Symantec Endpoint Protection Manager console, when you try to view some pages on the Home, Monitors, or Reports pages, you get a page with a message "File or Directory Was Not Found" and an additional line that says "The requested file or directory could not be located."
When logged in to the Symantec Endpoint Protection Manager console, while viewing the Home, Monitors, and Reports pages, some of the various views work normally, and some present a page with no data stating "File or Directory Was Not Found" and the line "The requested file or directory could not be located."
The user account that IIS is running under does not have permissions to create files in the <Program Files>\Symantec\Symantec Endpoint Protection\Inetpub\Reporting\temp directory.
If you are using the default account, that user is 'IUSR_<machine name>', and it should have full control of the entire Reporting directory and all child objects.
Assign full control permissions for the user account that our sites are running under to the directory <Program Files>\Symantec\Symantec Endpoint Protection\Inetpub\Reporting and all child objects
When the PHP scripts are launched by the web server, they try to use a temporary directory under the Reporting folder to create images and populate data to be dispayed in the interface. If the user account that our web pages is running under does not have full control of that temporary directory, the scripts will fail with a 'File or Directory Was Not Found' error. Filemon can be used to track this down further, as it will show an ACCESS DENIED to the temp folder for that user account.
Article URL http://www.symantec.com/docs/TECH96037