0 votes

Hi all,

I want to create an external Username (username-ext).
Loginname is the same as the initials.
Changing the intiakls -> intials-ext
samaccountname -> samaccountname-ext
userPrincipalName = samaccountname

After performing the script, I'm always getting this errormessage.
I have changed the Logininformation to an other Domain-Admin, same result:

Softerra.Adaxes.CommandPipeline.CommandProcessingException: Der folgende Befehl verursachte eine Ausnahme während der Ausführung: 'Löschen, Bitte (xxx.net\Users)' ändern: von Kürzel auf 'test5-ext' festlegen, von Benutzer-Anmeldename (prä-Windows 2000) auf 'test5-ext' festlegen, von Benutzer-Anmeldename auf 'test5-ext@xxxx.net' festlegen. ---> Softerra.Adaxes.Adsi.DirectoryComException (0x80072014): Der angeforderte Vorgang erfüllt mindestens eine Einschränkung nicht, die für diese Objektklasse Bedingung ist. (Server: xxxx) ---> System.DirectoryServices.Protocols.DirectoryOperationException: Eine Verletzung der Objektklasse ist aufgetreten.
   bei #F.#Rq.SendDirectoryRequest(ILdapConnection connection, DirectoryRequest request, ReferralChasingOptions referralChasing, TimeSpan clientTimeout, IDirectoryRequestErrorHandler errorHandler)
   bei #F.#Rq.SendDirectoryRequest(NtdsDirectoryIdentifier directoryId, ADS_AUTHENTICATION_ENUM authOptions, DirectoryRequest request, ReferralChasingOptions referralChasing, TimeSpan clientTimeout, IDirectoryRequestErrorHandler errorHandler)
   bei #F.#Rq.SendDirectoryRequest(NtdsDirectoryIdentifier directoryId, ADS_AUTHENTICATION_ENUM authOptions, DirectoryRequest request, ReferralChasingOptions referralChasing, TimeSpan clientTimeout, IDirectoryRequestErrorHandler errorHandler)
   bei Softerra.Adaxes.Adsi.AdmObject.SendDirectoryRequest(DirectoryRequest request, ReferralChasingOptions referralChasing)
   bei Softerra.Adaxes.Adsi.AdmObject.ModifyObjectInDirectory(ICollection`1 propertiesToWrite)
   bei Softerra.Adaxes.Adsi.AdmObject.ModifyObject(WritePropertiesContext writePropertiesContext)
   bei Softerra.Adaxes.Adsi.AdmObject.SetInfoEx(Object props)
   bei Softerra.Adaxes.CommandPipeline.Actions.SetPropertiesAction.ExecuteAction(IAdmTop targetObject, AdmPropertyList propertyListCopy)
   bei Softerra.Adaxes.CommandPipeline.Actions.ActionBase.Execute(IAdmTop targetObjectArg)
   bei Softerra.Adaxes.CommandPipeline.Actions.ActionBase.Execute(ICommand command)
   --- Ende der internen Ausnahmestapelüberwachung ---
by (450 points)
0

Hello Massimo,

How do you assign the external username? As far as we understand, you use some sort of a script for this purpose? Can you post it here or send it to our support e-mail (support[at]adaxes.com)?

0

Good morning support,

I'm not using a script to create this username.
Changing the user is my way in this case.
The Login are the initials which we type in manually.
After creating the user, Adaxes should change the Loginname (initials)
from %initials% to %initials%-ext. This is the "new" Loginname for external user.

Thank you

1 Answer

0 votes
by (450 points)
selected by
Best answer

Think having found the Solution for this.
The AD-Scheme for %initials% is only from 1 to 6 signs.
Solution is to change the Schemelengh

Related questions

0 votes
0 answers

I have been getting the following error when running the built in user creation script. This has worked fine up until about 2 months ago. As you can see Adaxes sees my ... error. The account that I am using has the correct permissions to Exchange as well.

asked Dec 9, 2020 by joshua.velez (20 points)
0 votes
1 answer

I created a new interface...on the Home Page Action, it only has new user. after the fields are filled out, I get "name is not specified for the new object". Please advise.

asked Oct 18, 2013 by MeliOnTheJob (1.7k points)
0 votes
0 answers

Hi All, I have setup an action to cancel all meetings in outlook when a user is leaving. We use Exchange online but I'm getting an error 'The operation is supported by Exchange online and Exchange versions starting from 2019' I cant see where you specify.

asked Sep 6 by DarrenFisk (60 points)
0 votes
1 answer

Hi When one of our admins create a user through the webinterface, the following error appears, and the user is not created: Access to the attribute is not permitted because ... is owned by the Security Accounts Manager (SAM). (Server: domain.local) Any ideas?

asked Jun 4, 2013 by kjesoo (960 points)
0 votes
1 answer

We use TOPdesk as our ITSM solution. Several departments are able to create new users. When a create user task fails we would like to receive the alert as the Adaxes ... Adaxes to sent out the incident to our TOPdesk. Is there a solution for this?

asked Oct 5, 2023 by mrkvd16 (50 points)
3,549 questions
3,240 answers
8,232 comments
547,814 users