0 votes

Hello,

I'm doing an upgrade to 2013.2. Is there a way to preserve the AdaxesLog.db3 content from the old version to the current version?

I tried to replace the file (previous method), but it now produces an error "failed to load log records". Unable to find assembly 'System.Data.SQLite....'

Thanks,

by (950 points)
0

Hello,

Can you describe the procedure that you followed for the update (step-by-step)?

Can you post the error message?

0

Purpose:
This document describes the steps required to perform an in place upgrade of ADAxes Active Directory Management system.
Procedure:
To upgrade to a new version of Adaxes you need to perform the following steps:
Backup ADAxes configuration.
Run:
C:\Program Files\Softerra\Adaxes 3\Service\Softerra.Adaxes.BackupRestore.exe
Click Next:
Check the “Back up credentials” option, and change the path to:
“C:\AdAxes Installation Files\Configuration Backup\Pre-Upgrade Backup”
Use the Proxy account and its password:
Production = CO-ADProxy
Lab = ADProxy

Verify that you have a complete backup file:

Backup Web Interface Configuration.
Run:
C:\Program Files\Softerra\Adaxes 3\Web Interface\Softerra.Adaxes.Web.UI.Configuration.exe
Change path to:
C:\AdAxes Installation Files\Configuration Backup\Pre-Upgrade Backup\Backup.Adaxes.WebUI.webuicfg
Leave the default (Administrator, Help Desk, and Self Service) checked:
Verify that you have a valid backup file:

Retain Existing Log Database
Copy:
C:\Program Files\Softerra\Adaxes 3\Service\LogDB\AdaxesLog.db3
to:
C:\AdAxes Installation Files\Configuration Backup\Pre-Upgrade Backup

Uninstall the existing version of Adaxes.

Install the new version.
Run:
C:\AdAxes Installation Files\adaxes_x64_en.msi (downloaded from vendor to this folder)

Enable all features:
Use the Proxy account and its password:
Production = CO-ADProxy
Lab = ADProxy
Take defaults:

Click “Restore Service Configuration”:
Browse to and select the backup that was created earlier.
Check “Restore Approval Requests”:
Use the Proxy account and its password:
Production = CO-ADProxy
Lab = ADProxy

Click “Restore Web UI Configuration”:
Click Browse and select the web interface backup file that was created previously:
Click Next (take defaults):

Click Finish:

Stop the ADAxes service and copy the original log database file to the original location:
Copy:
C:\AdAxes Installation Files\Configuration Backup\Pre-Upgrade Backup\AdaxesLog.db3
To:
C:\Program Files\Softerra\Adaxes 3\Service\LogDB\AdaxesLog.db3

Start the ADAXes service and verify that the console and web interface are operational.

Error Message for log:

0

First of all, the following steps:

Retain Existing Log Database
Copy:
C:\Program Files\Softerra\Adaxes 3\Service\LogDB\AdaxesLog.db3
to:
C:\AdAxes Installation Files\Configuration Backup\Pre-Upgrade Backup

and

Stop the ADAxes service and copy the original log database file to the original location:
Copy:
C:\AdAxes Installation Files\Configuration Backup\Pre-Upgrade Backup\AdaxesLog.db3
To:
C:\Program Files\Softerra\Adaxes 3\Service\LogDB\AdaxesLog.db3

are unnecessary because the logging database is already included in the Adaxes service backup file and restored together with Adaxes service configuration.

However, the cause for the issue is different. For some reason, Adaxes service cannot find assembly System.Data.SQLite. It is implemented by file System.Data.SQLite.dll. The file is located in the folder for Adaxes service, which is C:\Program Files\Softerra\Adaxes 3\Service by default. Make sure that the file is present in the folder and that the file version is correct (1.0.51.0). You can lookup the version on the Details page of the dialog with file properties.

0

I'm good without copying the log file - I just wanted to make sure the data was preserved. It did not appear to be - it looked like an empty file was recreated and the history was lost.

0

Probably, you checked it in one of the previous versions. Now, logging information is preserved.

What about the DLL file? Is it present in the directory for Adaxes service? What version is it?

0

0

Hello,

What version of Windows are you running? Is it 32 bit o0r 64 bit?

Did you install the 32 bit or 64 bit version of Adaxes?

0

64 bit.

We are upgrading from 2012.1 to 2013.2.

I don't think the backup from 2012.1 gets the log file:

1 Answer

0 votes
by (950 points)

I got it to work per my original instructions.

I think our lab had a bad log file.

Production is a 120MB file. I took it to the lab and stopped the services, replaced the file with the production log file and restarted. The data is now visible.

Thanks

0

64 bit.

The Operating System, the installation package or both? What is the Windows version?

I don't think the backup from 2012.1 gets the log file:

The support for backing up the logging database was added in one of minor updates for Adaxes 2012.1. Probably, you didn't install that update or any of the subsequent updates. In any case, Adaxes 2013.2 already supports backing up / restoring the logging database. After you manage to complete the upgrade process, you can remove the items for preserving the logging database from you checklist.

Related questions

0 votes
1 answer

We have a need to restore and read audit logs from a backup. We have restored the backup but are looking for guidance on the easiest method to access logs within this file. Thanks in advance!

asked Nov 22, 2016 by VTPatsFan (610 points)
0 votes
1 answer

Hello, We recently applied the 2023 upgrade following the backup / uninstall / install / restore procedure and we faced an issue: UUIDs for Business Units changed, which ... upgrade Adaxes in the future that does not delete and recreate Business Units? Cheers

asked May 4, 2023 by ygini (240 points)
0 votes
1 answer

Hello Everyone I wanted to ask if there is a way to increase the limit for the log file database as it is now 30 days by default or do I need to create a new SQL database? Thank you for the Support

asked Jun 28, 2021 by Sandberg94 (340 points)
0 votes
1 answer

Is it possible to "glue" several log files together? I made the mistake of not resetting the retention interval for our activity log during upgrades to more than 30 days. ... them into a single log file that can utilize the built in query tool. Thanks

asked Jun 27, 2012 by BradG (950 points)
0 votes
1 answer

We are in the process of upgrading from Adaxes 2014.1 to Adaxes 2018.2. As part of the upgrade we plan on moving from a Windows Server 2012 R2 VM to Windows Server 2016 ... I need to get new key files for the Adaxes 2018.2 deployments? Thank you in advance.

asked Mar 15, 2019 by lgibbens (320 points)
3,326 questions
3,026 answers
7,727 comments
544,678 users