Adaxes Bacup/Restore error

Question

Hi there

When I want to do a Backup from C:\Program Files\Softerra\Adaxes 3\Service\Softerra.Adaxes.BackupRestore.exe tool, I get this error:

"Can't back up or restore the Adaxes configuration, because it is stored on a remote computer."

Can you please help.

I want to do the upgrade to 2013.1 from 2012.1 (3.3.8308.0) 64bit

Comments

Hello,

Can you send us your Adaxes service configuration file so that we could troubleshoot the issue? To do this:

1. Navigate to the folder where your Adaxes service is installed (by default, C:\Program Files\Softerra\Adaxes 3\Service).
2. Find the file called Softerra.Adaxes.Service.exe.Config. The file contains settings of your Adaxes service.
3. Send the file to our support email (support[at]adaxes.com).

---

Email send :)

Answer 1

Hi there

It was an DNS error.

But now, when I run the Backup: It doesn't create the file and Powershell keeps running?

Run the script using the following command:
.\BackupApprovalRequests.ps1 -backupFilePath "<backup_file_path>" -defaultServiceAdminName "<admin_username>"
where
<backup_file_path> - the path to the backup file created on the 1st step.
<admin_username> - the username of the default service administrator. If you are logged on as the default service administrator, you can omit this parameter.

Comments

Hello,

It seems like the script is encountering the same issue as Adaxes backup/restore tool: it cannot successfully resolve the name of the computer where Adaxes service is installed.

How did you resolve the issue with the backup/restore tool: did you set up a DNS alias or performed an upgrade in a multiserver environment? We recommend setting up a DNS alias for the computer where Adaxes service is installed. In this case, the issue will be resolved not only for the backup/restore tool, but also for the script that backups pending Approval Requests.

If you opt for upgrading in a multi-server environment, Pending Approval Requests are not replicated among services sharing the same configuration. In this case we would recommend upgrading when there are no Pending Approval Requests. This is the only way how you can correctly upgrade without resolving the DNS issue with the computer where Adaxes is installed.

---

Hi

I made some changes in the Host file

ok, There are no "Pending Approval Requests"! So the Upgrade and restore of the other backups will be fine then?

Regards
Wally

---

Hi there

Upgrade was successful, but when I want to login vie the Anonymous user i get the following error:

Server Error in '/anonymous' Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>

What do I do?
Regards
Wally

---

Hello,

Yes, in case you don't have any Pending Approval Requests, you can upgrade without the script, however keep in mind that if you want to preserve Processed Approval Requests, you need to upgrade in a multi-server environment. If you don't need Processed Approval Requests, you can upgrade using the backup/restore tool.

As to the Web Interface issue, to help us troubleshoot it, can you do the following:

1. On the computer where your Web Interface is installed, take a look at Adaxes Service Event Log. It may contain a more specific and detailed description of the error. For instructions on how to view the log, see the following help article: Service Event Log.
2. Try logging in to the Web Interface site from the computer where the Web Interface site is installed, by replacing the computer name in the URL with localhost. For example, if you access the Web Interface by using http://host.example.com/AdaxesCustomWebSite, try accessing it by using the following URL: http://localhost/AdaxesCustomWebSite. When accessing a Web Interface site locally, IIS can return a more specific error and details.

---

The only error in Eventviewer is:

+ System

- Provider

[ Name] Adaxes Service

- EventID 0

[ Qualifiers] 0

Level 2

Task 0

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2013-05-21T10:02:40.000000000Z

EventRecordID 6077

Channel Adaxes

Computer vmw5487.cf-network.local

Security

- EventData

Softerra.Adaxes.ShutdownException: Failed to unregister 'cf-network.local'. ---> Softerra.Adaxes.Adsi.DirectoryComException (0x8000500C): Value 'ADM_MANAGEDDOMAINSTATUS_OPERATING' cannot be converted to the 'ADSTYPE_UNKNOWN' type. at Softerra.Adaxes.Adsi.AdsPropertyValue.SetValue(Object value, ADSTYPEENUM type, Boolean useCloning) at Softerra.Adaxes.Adsi.AdsPropertyEntry..ctor(String name, ADSTYPEENUM adsType, ADS_PROPERTY_OPERATION_ENUM controlCode, Object[] rawValues) at Softerra.Adaxes.Adsi.SingleCustomPropertyHandler.ReadProperties(ReadPropertiesContext context) at Softerra.Adaxes.Adsi.AdmObject.ReadProperties(ReadPropertiesContext context) at Softerra.Adaxes.Adsi.AdmObject.GetInfoEx(Object props, Int32 reserved) at #P.#gg.GetEx(IAdmObject obj, String name) at Softerra.Adaxes.Adsi.AdmObject.GetEx(String name) at #P.#gg.Get(IAdmObject obj, String name) at Softerra.Adaxes.Adsi.AdmManagedDomain.get_Status() at Softerra.Adaxes.Initializer.#Xib() --- End of inner exception stack trace ---

When opening Web from localhost:

Server Error in '/anonymous' Application.
--------------------------------------------------------------------------------

Could not load file or assembly 'Softerra.Adaxes.Adsi, Version=3.3.8308.0, Culture=neutral, PublicKeyToken=43a637781bd9a3c2' or one of its dependencies. The system cannot find the file specified.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.IO.FileNotFoundException: Could not load file or assembly 'Softerra.Adaxes.Adsi, Version=3.3.8308.0, Culture=neutral, PublicKeyToken=43a637781bd9a3c2' or one of its dependencies. The system cannot find the file specified.

Source Error:

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

<%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your application:

<configuration>
<system.web>
<compilation debug="true"/>
</system.web>
</configuration>

Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

Assembly Load Trace: The following information can be helpful to determine why the assembly 'Softerra.Adaxes.Adsi, Version=3.3.8308.0, Culture=neutral, PublicKeyToken=43a637781bd9a3c2' could not be loaded.

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

Stack Trace:

[FileNotFoundException: Could not load file or assembly 'Softerra.Adaxes.Adsi, Version=3.3.8308.0, Culture=neutral, PublicKeyToken=43a637781bd9a3c2' or one of its dependencies. The system cannot find the file specified.]
Softerra.Adaxes.Web.Initializer.Init() +0
ASP.global_asax.Application_BeginRequest(Object sender, EventArgs args) +40
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +80
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +171

--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.5466; ASP.NET Version:2.0.50727.5456

---

The reason for the error is that the Web Interface site is looking for the old version of Softerra.Adaxes.Adsi.dll. This can happen for two reasons:

1. Since it is a custom Web Interface site, after the upgrade you need to replace old files of the Web Interface site with new ones by copying them from the folder of an existing Web Interface as recommended in our Installation Notes. If you failed to do this, Adaxes Web Interface site is still using the old files for the site that were in the folder before the upgrade, including the Web Interface configuration file that specifies the version of Softerra.Adaxes.Adsi.dll that should be used for the Web Interface.
2. The old dll version may be cached by IIS. Try restarting IIS on the computer where your Web Interface is installed.

---

Hi there

Still not working and can't find the Softerra.Adaxes.Adsi.dll file anywhere on the server?

---

Still the same

the "Softerra.Adaxes.Adsi.dll" file is not on the server

---

Hello,

The Softerra.Adaxes.Adsi.dll file is usually located in a hidden folder inside your Windows installation directory, and since, as far as we can see, all the rest of Web Interface tyhpes installed on that computer work properly, the file is there and provides the necessary functionality to Adaxes Web Interface.

The issue is obviously in your custom Web Interface type. To help us troubleshoot it, can you do the following:

1. On the computer where your Web Interface is installed, open the folder that hosts files for all Web Interface types. By default, all Web Interface types are located in the following folder: C:\Program Files\Softerra\Adaxes 3\Web Interface\.
2. Locate the folder for the Web Interface type that you are experiencing issues with and zip it.
3. Send the zipped folder to our support email (support[at]adaxes.com).

---

The issue is that you didn't replace all the old files of the Web Interface site with new ones as recommended in our Installation Notes.

Some files are replaced with the new versions, however certain files in subfolders are still of old Adaxes 2012.1 versions. Please copy all the content (all files, subfolders and files in subfolders) from one of the existing Web Interface types (Administrator, Help Desk or Self-Service) to the folder that hosts your custom Web Interface type, and then reconfigure the Web Interface type.

---

:oops:
It looks like I might have missed that one.

Thanks for the help, now its working :geek:

Wally

---

Hi there

2013.2

When I do a Web interface restore with Softerra.Adaxes.Web.UI.Configuration.exe tool. I get this error:

Error 0x8013150b
Error 0x80131509
Web Interface coonfig files not found. Make sure you are running the application from the Web Interf installation dir.

Help please
Thanks
Wally

---

Hello Wally,

How do you launch Web interface backup/restore: from command line or by clicking the Restore Configuration button in the Web interface Configuration tool?

To help us troubleshoot the issue, can you send the following to our support e-mail (support@adaxes.com):

1. Screenshots of all the error messages.

2. The Web interface backup file that you are trying to restore.

3. Configuration files of your Web Interface types. All the files have the same name: Web.config. They are located in the folders for your Web Interface types. By default, Adaxes Web Interface sites are installed to the following folders:

   • Administrators:
     C:\Program Files\Softerra\Adaxes 3\Web Interface\Admin\
   • Help Desk:
     C:\Program Files\Softerra\Adaxes 3\Web Interface\HelpDesk\
   • Self-Service:
     C:\Program Files\Softerra\Adaxes 3\Web Interface\SelfService\

Also, make sure that the Web interface Configuration tool that you are launching is located in the folder for Adaxes Web interface (which is C:\Program Files\Softerra\Adaxes 3\Web Interface\ by default) and that the folder contains subfolders for your Web interface types.