Many of the errors associated with NWEA are related to the control of the database on the server. Unexpectedly dropped connecions and "hanging users" can tie up the database or individual students files and cause "quirky" errors. Here are the general things to try:
1) Start by ensuring that no TestTaker sessions are running, all client workstations are disconnected from the network, and that taa.hts is not running on any admin PC.
2) Try propagating the permissions (see article)
3) Try using ServerAdmin->AFP->Connections to see who is currently connected to the server and the state of the connection. If using <guest> for NWEA sessions, forcing all hanging <guest> connections off with the "Disconnect" button can release portions of the database that NWEA thinks are busy.
4) Try using WorkgroupManager->Sharing (10.4) or ServerAdmin (10.5) to un-share, then re-share the [school]_NTE folder.
5) Using an admin PC, try using taa.hta to re-download the appropriate data (Agency, Test, or Student) from NWEA.
1) Start by ensuring that no TestTaker sessions are running, all client workstations are disconnected from the network, and that taa.hts is not running on any admin PC.
2) Try propagating the permissions (see article)
3) Try using ServerAdmin->AFP->Connections to see who is currently connected to the server and the state of the connection. If using <guest> for NWEA sessions, forcing all hanging <guest> connections off with the "Disconnect" button can release portions of the database that NWEA thinks are busy.
4) Try using WorkgroupManager->Sharing (10.4) or ServerAdmin (10.5) to un-share, then re-share the [school]_NTE folder.
5) Using an admin PC, try using taa.hta to re-download the appropriate data (Agency, Test, or Student) from NWEA.