Set-place command and room finder

Hi Dev Sp,

Thank you for posting on Microsoft Forum.  

Based on you description, I understand that you are getting an error when trying to run Set-place command.

Before you can run this cmdlet, you must be assigned permissions. Some parameters may be inaccessible if they are not included in the permissions assigned to you, I suggest checking if you have the required the permissions Find the permissions required to run any Exchange cmdlet | Microsoft Docs.

This cmdlet does not work on the following synchronized room mailbox attributes in hybrid environments: City, CountryOrRegion, GeoCoordinates, Phone, PostalCode, State, and Street. To change these attributes on synchronized room mailboxes, except GeoCoordinates, use the Set-User or Set-Mailbox cmdlets (Works in on-premises Exchange) Set-Place (ExchangePowerShell) | Microsoft Docs.

Looking forward to hearing from you.

Best Regards,

De Paul

Thanks for the response De Paul, have checked the permissions along with the Room mailbox been in the cloud this is fine. Like i mentioned this was working fine a couple of weeks ago but now appears to be having issues.

Same problem as you, same scenario. It all worked a ~week or two ago and now fails with the same error you describe. All resources are in-cloud and NOT synced from AD, I am running commands as global admin, same account that worked before and no privileges have changed.

Same problem here.

In my company's environment, AD is on-premises and synchronised with M365 but Exchange is cloud-only. On-premises Exchange has been decommissioned a few months after migrating to Microsoft 365. So, from the Exchange point of view, this is not a hybrid configuration. Am I right?
So, I'm considering deleting all resource mailbox accounts that were created before the migration to M365 from the local AD and re-create them as cloud-only accounts because Exchange Powershell online does not have the permissions to alter these accounts although there is no on-premises Exchange anymore.
So, for my new meeting rooms, I created on-cloud only accounts but still I can't use the City, CountryOrRegion, GeoCoordinates, Phone, PostalCode, State and Street parameters with the Set-Place command.
Am I missing something?

Kind regards,

Marc Devriendt

I am having similar trouble, although I'm trying to set -City and -State.

I saw an article that said to capture more information, use:

$error[0] | fl * -force

That gave me "ScriptStackTrace : at

If it helps, it seems this problem goes away 24 hours after the New-Mailbox command is run to create the room. Of course, I don't want to run the New-Mailbox script today, and a different Set-Place script tomorrow.

I have been able to power through the problem by logging out, rebooting the entire PC, logging in, and then running the Set-Place script - although it only updates a single room before changing into the error state. I can log out, reboot, log in again and get Set-Place to update one more object, ad infinitum. (Mostly - I keep trying, and the most recent attempt did not successfully get another object updated).

I've run the command successfully on 6 resource mailboxes and got the same error as Dev Sp on other two. I have permissions of global administrator.

The error is quite inconsistent.

writeErrorStream : True

PSMessageDetails :

OriginInfo : outlook.office365.com

Exception : System.Management.Automation.RemoteException: Encountered an internal server error.

TargetObject :

CategoryInfo : NotSpecified: (:) [Set-Place], TaskException

FullyQualifiedErrorId : [Server=PR3PR01MB6666,RequestId=89cdc396-ad15-4b6b-b0c6-0b6ddd66d66f,TimeStamp=31.08.2022 10:19:07] [FailureCategory=Cmdlet-TaskException] 35B25AD4,Microsoft.Exchange.Management.Recip

ientTasks.SetPlace

ErrorDetails :

InvocationInfo :

ScriptStackTrace : at

PipelineIterationInfo : {}

Same problem here, and same error :

writeErrorStream : True

PSMessageDetails :

OriginInfo : outlook.office365.com

Exception : System.Management.Automation.RemoteException: Nous avons rencontré une erreur de serveur interne.

TargetObject :

CategoryInfo : NotSpecified: (:) [Set-Place], TaskException

FullyQualifiedErrorId : [Server=MR1P264MB1844,RequestId=7b3e6544-c63a-4c4e-bd57-f15140796939,TimeStamp=02/09/2022 08:22:15] [FailureCategory=Cmdlet-TaskException]

37D74782,Microsoft.Exchange.Management.RecipientTasks.SetPlace

ErrorDetails :

InvocationInfo :

ScriptStackTrace : at

PipelineIterationInfo : {}

Even though it might work just fine tomorrow, I'd like to create my rooms in one go and forget about it, this is very frustrating.

Hello there,

I am getting the very same error when runing set-place (workspace was created just few minutes back).

So the workaround is to wait till the next day?

Any fix to be presented soon for this?

Or maybe at least more information about what was wrong (the error "Set-Place: Encountered an internal server error." is not very helpfull here)?

I've personally found (and, yes, it's a terrible workaround) - limiting parameter settings sent to set-place when doing it in bulk helps avoid the internal server error.

Thanks Joshua Laine, you are correct.

The command:

Set-Place -Identity "Conference_Room" -CountryOrRegion "US" -City "Washington" -Floor 1 -Capacity 54 -Street "2533 W 5th Street" -GeoCoordinates "35.546552; -77.052174" -Building "Main Office" -State NC -PostalCode 27889 -Phone "+1 252 946 5175" -Label "Conference_Room" -VideoDeviceName "Microsoft Teams" -Tags Training, Development, Videoconference

always ended in Encountered an internal server error.

+ CategoryInfo : NotSpecified: (:) [Set-Place], TaskException

Removing all the parameters except for

Set-Place -Identity "Conference_Room" -Label "Conference_Room"

seems to have worked