0 votes

Failed to import schema to the service backend using 'ldifde.exe'.

It then rolls back everything. Is my AD too big?

by (80 points)
0

What error is reported?
What operating system do you use?
What msi package do you use (x86 or x64)?

The problem is not related to the size of your AD, since Adaxes doesn't extend the Active Directory schema.
During the installation, Adaxes extends the schema of the ADAM instance installed by the product.

0

The error reported is "Failed to import schema to the service backend using 'ldifde.exe'."
OS is Windows Server 2003 sp2
MSI is x86.

0

OS is Windows Server 2003 sp2

Is the OS 32 or 64-bit?
And what is the edition of your OS, Enterprise or Datacenter?

0

32 bit standard edition

0

Unfortunately we can't reproduce your problem in out environment.
The error occurs because the installation fails to launch ldifde.exe to extend the schema of the backend. It looks like the file is either missing or inaccessible.
Please check whether ldifde.exe is present in the C:\WINDOWS\ADAM\ folder and whether this file is accessible.

0

The file is there, and if I open a command prompt it executes.

0

Just tried on a completely different server in the same domain. Still failed. Perhaps something in our build process? We use some of the NIST standard templates.

0

1. Does the Extending ADAM instance schema operation fail immediately or after a delay? (see image attached)

2. Please check whether ldif.log or ldif.err files exist in the temp directory of the user who launches the installation. If not, please try to search for these files on your system.

0

I tried again on a 3rd server in a different domain that uses a different build process, Windows Server 2008 x64 standard.
Same result, using the 64 bit english download.

It stops immediately, a search of the c drive for ldif* finds nothing.

1 Answer

0 votes
by (18k points)

Jim, we've found an issue that might be the cause of your problems.
Please download and try to install a new build that fixes that issue:
x86: http://softerra-downloads.com/adaxes/Jo ... x86_en.msi
x64: http://softerra-downloads.com/adaxes/Jo ... x64_en.msi

Please inform us whether the problem is solved.

0

This new build fixed the problem, thanks for the response!

0

BTW, we've uploaded Adaxes 2010.1 SP1 that contains this fix and a couple of others.
http://www.adaxes.com/download_direct.htm

Related questions

0 votes
1 answer

During the upgrade of the second server with version 2021.1, shared installation selected, the process stops in "pending authorization" not allowing the process to complete ... to find Adaxes services that are waiting for authorization." Any suggest? Thanks

asked Mar 18 by Simone.Vailati (70 points)
0 votes
0 answers

When attempting to assign licenses during the "after creating a user" rule we're reciving the following error. Failed to create a remote mailbox for the user. The address ' ... mail attribute to the proper format that isn't the onmicrosoft.com domain as well.

asked Sep 2 by zorps (20 points)
0 votes
1 answer

Our adaxes service account is able to create the mailbox when running our create user business rule, but cannot change any settings like disable OWA. What level of security will it need?

asked Apr 6 by bstone (50 points)
0 votes
1 answer

Hi, We encounter an error on one of our Adaxes service (Adaxes 2016 3.7.13430) when activating Licence for new user : Softerra.Adaxes.CommandPipeline.CommandProcessingException: The ... stack trace --- Any idea ? Thank you in advance for your help regards

asked Sep 20, 2017 by smasset (730 points)
0 votes
0 answers

I'm suddenly receiving the following error when trying to perform certain web functions in the web portal. Fatal error Error Failed to decrypt using provider 'CurrentUserDataProtectionProvider ... : 3.7.11926.0 Any assistance would be appreciated. Thx! --Joel

asked Nov 2, 2015 by ashmite (470 points)
2,554 questions
2,297 answers
6,126 comments
662,047 users