Now that the Aeries web application includes various data import features, older installations of Aeries may not have sufficient permissions to accomplish these imports.


This information applies to any import in Aeries Web.  At this time the following imports are available:

  • CASEMIS Import
  • NSLP Import
  • Import Test Results – CAASPP, ACT, AP, SAT, etc.
  • CALPADS Extracts – New SSID Import, SSID Replacement Import, SELA Import, Direct Certification Import, LTEL Import


If the Aeries application pool is running as NETWORK SERVICE, as is common, NETWORK SERVICE would need the ability to write to the FileStore path, whereas it previously did not.


To determine what App Pool a Web App is running as, follow the steps displayed below in IIS Manager.




Now navigate to Application Pools to see what identity it is running as.




NOTE: All further examples demonstrate adding permissions for NETWORK SERVICE since that is the identity our sample Application Pool is running as. Yours may be something other than NETWORK SERVICE.


Follow one set of instructions below, based on whether the Aeries Web application and the Aeries Reporting Service are on the same server or different servers.


Scenario 1: Web and Reporting on Same Server


If the Aeries Reporting Service is running on the same server as the Aeries Web Application, you need to elevate permissions on the Aeries Reporting FileStore.




Scenario 2: Web and Reporting on Separate Servers


If the Aeries Reporting Service is running on a separate server and accessed via a UNC path from the Aeries Web application, you need to make sure the share permissions are correct.





It is also a good practice to run the Aeries Reporting Service as the same identity as the app pool so it is likewise elevated. Microsoft has also tightened permissions on how NETWORK SERVICE may interact with UNC paths.

The FileStore$ share and file level security may also need full permissions for the machine account of the web server(s) for it to work. In other words, it may be necessary to add WebServer$ to the share permissions and file permissions with read/write (where "WebServer" is the machine name of the web server)


Add machine account permissions as illustrated below for each web server that connects to the Aeries Reporting Service to both the FileStore directory and the FileStore$ share.