Hiep Le
Jul 24, 2023
visibility 3249
star star star star star
(0 votes)

No valid combination of account information found

You might have stumbled upon the error below while upgrading the minor commerce version:

I encountered this while upgrading from EPiServer Commerce version 13.32.3 to 13.33.0.

Google gave me this: https://stackoverflow.com/questions/13913589/azure-blob-storage-no-valid-combination-of-account-information-found

So I wondered what does my upgrade have anything to do with Azure Blob Storage? 

Turned out, it has something to do with Azure Blob Storage indeed.

In version 13.33.0, you can use Azure Blob Storage to keep the site's blobs, using this article if you want to do that: https://world.optimizely.com/blogs/ram-kumar-k/dates/2018/3/using-azure-cloud-for-storing-episerver-cms-blobs/

It gave me the hint to find that the upgrade has inserted a new provider section below in my Web.config

<blob defaultProvider="azureblobs">
      <providers>
        <add name="azureblobs" type="EPiServer.Azure.Blobs.AzureBlobProvider,EPiServer.Azure" connectionStringName="EPiServerAzureBlobs" container="mysitemedia"/>
      </providers>
</blob>
<event defaultProvider="azureevents">
      <providers>
        <add name="azureevents" type="EPiServer.Azure.Events.AzureEventProvider,EPiServer.Azure" connectionStringName="EPiServerAzureEvents" topic="MySiteEvents"/>
      </providers>
</event>

Additionally, new connections were added:

<add name="EPiServerAzureBlobs" connectionString="DefaultEndpointsProtocol=https;AccountName=mystorageccount;AccountKey=abcdefghijklmnoabcdefghijklmnoabcdefghijklmno"/>
    <add name="EPiServerAzureEvents" connectionString="Endpoint=sb://myservicebus.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=abcdefghijklmnoabcdefghijklmnoabcdefghijklmno="/>    

Commented out both sections since I am not going to use them yet and my site is back to life.

Jul 24, 2023

Comments

error Please login to comment.
Latest blogs
Surviving a Dirty Feed. Part 3: Error Handling and Event Batching

Committing a 250,000-row Optimizely catalog import row by row, returning a per-row failure report, and coalescing catalog events into one per batch.

Stanisław Szołkowski | Oct 16, 2026 |

Building UI Extensions for Optimizely SaaS CMS

Introduction Developers have been extending the functionality of Optimizely PaaS CMS for years using addons built in C# and deployed as NuGet...

Mark Stott | Oct 15, 2026

Cheapskate AI Translator: Because Translation Should Not Require a Second Mortgage

There is a particular kind of software project that begins with a detailed architecture document, a product roadmap, and a carefully assembled...

Linh Doan Cuu | Oct 15, 2026

Computed Fields in CMS 13 Content Contracts with Optimizely Graph

Content Contracts in Optimizely CMS 13 allow different content types to share a common structure when querying Optimizely Graph. But what if the...

Mardy | Oct 14, 2026