Share via

New-mailbox -shared

Anonymous
2023-12-10T21:52:35+00:00

A while ago this command:

New-Mailbox -Shared -Name ******@tenant.onmicrosoft.com -DisplayName "Info" -Alias  info -PrimarySmtpAddress ******@tenant.onmicrosoft.com

worked, but lately whenever I configure new tenant I get this error:

Write-ErrorMessage : Ex6AE46B|Microsoft.Exchange.Data.Directory.ADOperationException|Active Directory operation failed on PAXPR04A14DC002.EURPR04A014.PROD.OUTLOOK.COM. This error is not retr

iable. Additional information: The parameter is incorrect..

Active directory response: 00000057: LdapErr: DSID-0C091372, comment: Error in attribute conversion operation, data 0, v4563

At C:\Users\miha\AppData\Local\Temp\tmpEXO_px5sf1ke.toj\tmpEXO_px5sf1ke.toj.psm1:1190 char:13

+             Write-ErrorMessage $ErrorObject

+             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : NotSpecified: (:) [New-Mailbox], ADOperationException

    + FullyQualifiedErrorId : [Server=AS1PR04MB9655,RequestId=fc1fefb0-bcf8-7937-d907-868b3627008f,TimeStamp=Sun, 10 Dec 2023 21:48:26 GMT],Write-ErrorMessage

I work around by creating a shared mailbox in web interfac, but I'd like to know why this happens.

Can anybody help?

Microsoft 365 and Office | Subscription, account, billing | For business | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

13 answers

Sort by: Most helpful
  1. Anonymous
    2024-06-04T09:28:06+00:00

    Hello,

    I think I solved the problem. I had another problem lately - I couldn't do new-dkimsigningconfig command. The error was the same. I turned to Microsoft support with little hope of success. And shure the first suggestion was - use english Windows. What a stupid suggestion from support.

    But, I did install a virtual machine with English windows with english keyboard... and ****!!! Both commands (new-mailbox -shared and new-dkimsigningconfig) work!!!

    So, there are two possible solutions - I always use domain joined computers and this one wasn't, but I think I already checked that once. More likely the solution was Windows in english and maybe with english keyboard.

    Check if it works for you too.

    Regards

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2023-12-11T18:38:38+00:00

    My problem has nothing to do with on premises. For a few times now, I got a new tenant to prepare O365 solution for smaller firm. I imported a few users and my next step is shared mailbox. The same command worked about three months ago, but it's not working for at least two months now. I did it step by step with only required swithes always with above error.

    I belive the problem is with exchange-online powershell command.

    So, even if this is completely O365 problem I turn to https://learn.microsoft.com/en-us/answers/questions/??

    Regards

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2023-12-11T13:45:24+00:00

    Do you have any on-prem exchange servers? Because we experience the exact same problem, and we are only cloud based. So something is wrong at Microsofts side as far as I can see.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-12-11T13:41:56+00:00

    We have the exact same problem, and we do not have any on-prem exchange servers.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2023-12-10T23:53:02+00:00

    Dear MihaŻitko,

    Good day! Thank you for posting to Microsoft Community. We are happy to assist you.

    Based on your description, your issue is with Exchange server and Active Directory which are not within our support scope, we are for Office365 cloud products.

    I tried to reach the consult team and got some advices, please refer to the information below:

    Based on the error message you provided, it seems that there is an issue with the attribute conversion operation in Active Directory. This could be caused by incorrect parameter values or a problem with the Active Directory schema.

    To troubleshoot this issue, you can try the following steps:

    1. Check if the parameter values you are using are correct and valid. Make sure that the name, display name, alias, and primary SMTP address are all unique and do not conflict with any existing objects in your Active Directory.
    2. Check if there are any issues with the Active Directory schema. You can use the ADSI Edit tool to check the schema and make sure that all required attributes are present and correctly configured.
    3. Check if there are any replication issues in your Active Directory environment. Make sure that all domain controllers are replicating properly and that there are no errors in the event logs.

    If the issue persists, we suggest you post your query on Questions - Microsoft Q&A. There are many experts on all kinds of Microsoft products and they are high technical skilled. I think you can find more useful information on that community.

    I hope the information helps! If there is any update or I misunderstand you, please feel free to let me know. I will continue to assist you. Your understanding and co-operation are highly appreciated.

    Thanks for your precious time. Have a nice day.

    Sincerely,

    Sherry | Microsoft Community Moderator

    Was this answer helpful?

    0 comments No comments