This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(9.6, 69%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMB%3C/text%3E%3C/svg%3E)
Hello all,
I created a script in powershell to collect mailbox information from our tenants on Exchange Online. It stopped working somewhere aroung the 1st of May. Im going to explain what my process is in some detail and when the error occurs.
There are some prerequisites:
The process I use is as follows:
New-PartnerAccessToken -ServicePrincipal -ApplicationId $AzureAppGUID -Credential $CSPCredential -Scopes $PartnerCenterScope -Tenant $CSPTenantGUID -UseAuthorizationCode
Every other time using previously generated and non-expired refresh token:
New-PartnerAccessToken -ApplicationId $AzureAppGUID -RefreshToken $CSPPartnerRefreshToken -Scopes $PartnerCenterScope -Tenant $CSPTenantGUID -Credential $CSPCredential
New-PartnerAccessToken -Module ExchangeOnline
Every other time using refresh token:
New-PartnerAccessToken -Module ExchangeOnline -ApplicationId $ExchangeOnlineApplicationGUID -RefreshToken $CSPExchangeRefreshToken -Scopes $ExchangeOnlineScope -Tenant $CSPTenantGUID
New-PartnerAccessToken -RefreshToken $CSPExchangeRefreshToken -Scopes $ExchangeOnlineScope -Tenant $TenantMicrosoftGUID -ApplicationId $ExchangeOnlineApplicationGUID
Connect-ExchangeOnline -DelegatedOrganization $CustomerMicrosoftGUID -AccessToken $CustomerExchangeAccessToken -ShowBanner:$False -Verbose -EnableErrorReporting -LogDirectoryPath $LogPath -LogLevel All
Step #4 is where I get an error. When I use the -Verbose and -Debug parameters with the Connect-ExchangeOnline command I get the following error message:
VERBOSE: Returning precomputed version info: 3.4.0
VERBOSE: ModuleVersion: 3.4.0
VERBOSE: [ThreadID: #] Returning the provided AccessToken
VERBOSE: ConnectionContext Removed
Unexpected character encountered while parsing value: F. Path '', line 1, position 1.
At C:\Program Files\WindowsPowerShell\Modules\ExchangeOnlineManagement\3.4.0\netFramework\ExchangeOnlineManagement.psm1:766 char:21
+ throw $_.Exception;
+ ~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OperationStopped: (:) [], JsonReaderException
+ FullyQualifiedErrorId : Unexpected character encountered while parsing value: F. Path '', line 1, position 1.
I have no clue what this error even means. I have used a JWT explorer to validate the token is okay, and all scopes are included, the signature is verified in HS256 alg. I have no clue where to continue my search for a solution.
Pls halp!
Thanks in advace.
Peace!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 74%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERM%3C/text%3E%3C/svg%3E)
It looks like the error is in the ExchangeOnlineManagement module, on line 766. It may be trying to open a JSON file.
Assuming(!) that the 3.4.0 in the verbose output refers to the ExchangeOnlineManagement module, you might try using a more recent version, like 3.5.0.
I uninstalled all ExchangeOnlineManagement modules. For some reason I had 3.0.0, 3.1.0 and 3.4.0 installed
Installed to 3.5.0 clean. Tried again.
Here is the error:
Connect-ExchangeOnline -DelegatedOrganization $CustomerMicrosoftGUID -AccessToken $CustomerExchangeAccessToken -ShowBanner:$False -Verbose -Debug
VERBOSE: Computed version info: 3.5.0
VERBOSE: ModuleVersion: 3.5.0
VERBOSE: [ThreadID: #] Returning the provided AccessToken
VERBOSE: ConnectionContext Removed
Unexpected character encountered while parsing value: F. Path '', line 1, position 1. At C:\Program Files\WindowsPowerShell\Modules\ExchangeOnlineManagement\3.5.0\netFramework\ExchangeOnlineManagement.psm1:766 char:21
+ throw $_.Exception;
+ ~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OperationStopped: (:) [], JsonReaderException
+ FullyQualifiedErrorId : Unexpected character encountered while parsing value: F. Path '', line 1, position 1.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(44.800000000000004, 43%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBJ%3C/text%3E%3C/svg%3E)
Looks like the issue is more related to your JSON file, please kindly understand that the Exchange Online tag here we mainly focus on general issues about Exchange Online.
I put the "Exchange Online" tag because I considered this to be an issue with the authentication process with the Exchange Online through PowerShell.
Can you at least point me to the place where this JSON file exists? I don't manually generate or edit or use any JSON file (at least to the extent of my knowledge). And if this is indeed an issue with some JSON file, I would be grateful if anyone knew what JSON file is being opened or used.
I understand that the content of the error suggests that there is some issue with a JSON file since this is what it reads:
+ CategoryInfo : OperationStopped: (:) [], JsonReaderException
but again, since I personally am not using, editing, opening, closing (or whatever other operation comes to mind) a JSON file, I am unsure how to correct this issue. It seems out of my control.
.
The line that seems to be the issue is line 766 in the "ExchangeOnlineManagement.psm1" file. That line contains the following code:
717 catch
718 {
719 # If telemetry is enabled, log errors generated from this cmdlet also.
720 # If telemetry is not enabled, calls to cmdletLogger will be a no-op.
721 $errorCountAtProcessEnd = $global:Error.Count
722 $numErrorRecordsToConsider = $errorCountAtProcessEnd - $errorCountAtStart
723 for ($i = 0 ; $i -lt $numErrorRecordsToConsider ; $i++)
724 {
725 $cmdletLogger.LogGenericError($connectionContextID, $global:Error[$i]);
726 }
727
728 $cmdletLogger.CommitLog($connectionContextID);
729
730 if ($EnableErrorReporting.Value -eq $true -and $UseRPSSession -eq $true)
731 {
732 if ($global:_EXO_TelemetryFilePath -eq $null)
733 {
734 $global:_EXO_TelemetryFilePath = New-EXOClientTelemetryFilePath -LogDirectoryPath $LogDirectoryPath.Value
735
736 # Import the REST module
737 $RestPowershellModule = "Microsoft.Exchange.Management.RestApiClient.dll";
738 $RestModulePath = [System.IO.Path]::Combine($PSScriptRoot, $RestPowershellModule);
739 Import-Module $RestModulePath -Cmdlet Set-ExoAppSettings;
740
741 # Set the AppSettings
742 Set-ExoAppSettings -ShowProgress $ShowProgress.Value -PageSize $PageSize.Value -UseMultithreading $UseMultithreading.Value -TrackPerformance $TrackPerformance.Value -ConnectionUri $ConnectionUri -EnableErrorReporting $true -LogDirectoryPath $LogDirectoryPath.Value -LogLevel $LogLevel.Value
743 }
744
745 # Log errors which are encountered during Connect-ExchangeOnline execution.
746 Write-Message ("Writing Connect-ExchangeOnline error log to " + $global:_EXO_TelemetryFilePath)
747 Push-EXOTelemetryRecord -TelemetryFilePath $global:_EXO_TelemetryFilePath -CommandName Connect-ExchangeOnline -CommandParams $PSCmdlet.MyInvocation.BoundParameters -OrganizationName $global:_EXO_ExPSTelemetryOrganization -ScriptName $global:_EXO_ExPSTelemetryScriptName -ScriptExecutionGuid $global:_EXO_ExPSTelemetryScriptExecutionGuid -ErrorObject $global:Error -ErrorRecordsToConsider ($errorCountAtProcessEnd - $errorCountAtStart)
748 }
749
750 $global:EXO_LastExecutionStatus = $false;
751
752 if ($_.Exception -ne $null)
753 {
754 # Connect-ExchangeOnline Failed, Remove ConnectionContext from Map.
755 if ([Microsoft.Exchange.Management.ExoPowershellSnapin.ConnectionContextFactory]::RemoveConnectionContextUsingConnectionId($connectionContextID))
756 {
757 Write-Verbose "ConnectionContext Removed"
758 }
759
760 if ($_.Exception.InnerException -ne $null)
761 {
762 throw $_.Exception.InnerException;
763 }
764 else
765 {
766 throw $_.Exception;
767 }
768 }
769 else
770 {
771 throw $_;
772 }
773 }
I have tried to enable error logging, and this is what I got:
(I formated the output a bit to make it easier to interpret, and to redact any sensitive information)
This is the order of execution of the commands, their start and end times. You can clearly see that the "Get-ConnectionContext" command is the only one with a finish time. The previous commands did not finish at all.