support
Unable to access newly-unboxed ARES system
Immediately after unboxing ARES, you may encounter messages such as:
You are not authorized to access that menu.

or:
You are not authorized to modify this unit's identity settings.

Additionally, when attempting to run the Setup Wizard, you may see messages like:
(your name) is not authorized to access the database directly.

This indicates that the autoexec.as notecard did not run successfully. This may happen for several reasons:
  • By far the most common reason is that you are a veteran of Companion who is using ARES for the first time, and did not realize that ARES requires a few extra setup procedures before it can be used. Please make sure you follow the instructions in the Booting up for the first time tutorial very carefully. ARES is similar to Companion, but because it is model-agnostic, it must be initialized first.
  • The second most likely problem is that the autoexec.as file was not correctly inserted into the ARES HUD. If you do not hold down the Ctrl key (Mac: Command key), or drag it into the wrong part of the HUD, then it may end up in the wrong prim, or not drop into the HUD at all. Right-click the ARES HUD and choose Edit, then switch to the Contents tab and drag the autoexec.as file from your inventory into the HUD.
  • Somewhat less likely, you may be in a region of Second Life experiencing difficulties connecting to the asset servers, in which case you have probably noticed other issues such as missing textures. Visit Second Life Grid Status to see if any outages have been reported, or consider contacting the owner of your region to request a simulator restart.
  • Finally, if you are using a brand-new version of ARES that has just been released within the last 24 hours, it is possible that something went wrong during the QA process and your installation of ARES cannot parse script notecards correctly. If you have evidence that this is the case, consider rolling back to an earlier version, and filing a bug report.
Alternatively, if you are performing QA, you may also attempt to bypass the problem by manually running the relevant commands from the autoexec.as script yourself:
commandeffect
@security auditgrants access to the unit
@xset version db kernel.version
@set version %word 1 in $version
@fs source setup http://my.nanite-systems.com/$version/setup/
@alias setup do asu_0.as
@set version %undefined		prepares the @setup command
The other parts of the autoexec.as file are responsible for ensuring ARES correctly displays the name of your controller model. You may run these manually by putting @ before each line.