Ares Known Issues
7 results found
-
The Ares updater may create unnecessary WebValidation entries.
The AresUpdate.sql script is using checks to determine if a web validation entry exists. The entries were necessary in the 4.6.0 major update but were not removed in the subsequent point releases.
As an example, if a site chose to not use the PasswordHint field they may have removed the validation. The update script will add the validation back in each 4.6.x update if the site had already removed the web validation entry.
1 votereleased ·
AdminDustin Stokes
(Chief Technology Officer @ Atlas Systems, Inc., Atlas Systems, Inc.)
responded
Released in Ares 4.6.6
-
Ares Server Installer does not have a default selected for SQL Server location
Found while testing the Ares 4.6.5 server update. The installer should have a default option visible.
1 votereleased ·AdminDustin Stokes
(Chief Technology Officer @ Atlas Systems, Inc., Atlas Systems, Inc.)
responded
Released in Ares 4.6.6
-
Not entering a backup file will cause the update wizard to fail.
When updating Ares, if you choose to back up the database and don't enter anything when prompted for the path for the backup file,clicking next will cause the update wizard to fail and force you to exit.
1 vote -
Exporting course details may not work in the web after updating from Ares 4.5.1 or 4.5.2 to Ares 4.6.0.
The workaround for this is installing or repairing the installation of the AresServerUpdate.msi on the affected sites.
1 vote -
The Ares server installer does not allow repairs.
When trying to run the Ares server installer in repair mode, and error occurs indicating that SQL server login failed for user 'sa' (error 18456). It looks like the SQL connection verification step is running in repair mode when it shouldn't be. This error causes the repair to fail and rollback.
1 vote -
The Ares installer may incorrectly try to add existing document types on update.
Repro Steps
When adding the document types for mp4, docx, pptx, and xlsx in the update script, it is incorrectly checking for existing records with the same DocumentTypeName and Extension. Since only the DocumentTypeName is a primary key field, an existing record with the same DocumentTypeName but different extension will result in a primary key violation. This has come up with the New School, which had already added an mp4 document type.1 votereleased ·AdminDustin Stokes
(Chief Technology Officer @ Atlas Systems, Inc., Atlas Systems, Inc.)
responded
Released in Ares 4.6.6
-
0 votes
Released in the 5.0.1 Server Release
