Blog Post

Exchange Team Blog
3 MIN READ

Easier Room Booking in Outlook on the Web!

The_Exchange_Team's avatar
The_Exchange_Team
Platinum Contributor
Jul 31, 2019
How often have you or your users tried to find rooms that are free for your meeting time, your recurring series, that have the capacity and resources you need, and are close to you? Probably enough t...
Updated Feb 27, 2024
Version 2.0
announcements
Calendaring
exchange online
office 365
OWA
markoim's avatar
markoim
Copper Contributor
Dec 25, 2019

Just like user  Andreas Lannerberg, 

 
I had same problem with running commands on a PC that has Serbian Latin regional settings. Running (and not copy/paste but typing) from cmd shell or powershell or new windows terminal app nothing worked I always got  error: "Cannot process argument transformation on parameter 'GeoCoordinates'. Cannot convert valu
e "44.494222;20.272701" to type "Microsoft.Exchange.Data.GeoCoordinates". Error: "The lat
itude specified in '44.494222;20.272701' is invalid. Latitude must be a number between -9
0.0 and 90.0.""       The thing that worked was NOT to use En-US keyboard but to actually use Serbian-latin keyboard and change command line into this>    Set-Place -Identity place1 -GeoCoordinates "44,494222;20,272701"                               
 
  If you look carefully you will notice there is no . but ,  in coordinates.                           
                 This has everything to do with regional settings and character encoding BUT this is actually checking the regional settings on local pc and doesn't care what shell client you are running which is a new kind of HELL for administrators. 
 ... So MS dev team can you PLEASE  decide what encoding you are using unicode-wise   are you going to accept UTF-8 like rest of normal world or are you going to torture users with UTF-16LE/UTF16BE BS  ?