*** NOTE: ALL INFORMATION IS ACCURATE AT DATE OF PUBLISHING ***
This could be a very unique error, but sharing just in case it comes up for anyone else. While setting up some new Power Pages sites, I started getting an error even though the site had previously loaded fine. It was a fun message of Exception Message The chunked cookie is incomplete. Only 0 of the expected 2 chunks were found, totalling 0 characters. A client size limit may have been exceeded. This post is quick and simple and gives you a fix to get the site loaded again. Hope it helps someone!
I started getting an error shortly after creating a portal. The portal was a trial, with the only way to view it by authenticating using my Microsoft account login credentials. So, usually when you get the message starting with ‘we’re sorry, but something went wrong’ a restart of the site can often fix it. I tried that, nothing. I did a scan for any errors, nothing. However, it was something to do with cookies… so I had a think about it.
If you go in to the developer console of your browser (F12 or right click, inspect), you can see the cookies that are set in your browser for that site.
If you then right click on the name of the site, you can then clear those cookies.
Make sure the cookie list is empty then refresh the page.
After clearing out the cookies, the site showed without any error at all.
It seems that when you sign in to a Power Pages site using an external identity provider such as Azure AD, the portal creates an authentication ticket that contains your user identity and related claims. If that ticket becomes too large, it is automatically split into multiple cookie “chunks”, typically named .AspNet.ExternalCookieC1 and .AspNet.ExternalCookieC2, so it can still be stored within browser limits. Problems occur when something interrupts this process during login or page redirects, such as a redirect loop, a page refresh mid-authentication, or leftover stale cookies from a previous session. In those situations, the browser may end up storing only part of the expected cookie set, or none of the chunks at all. When the portal later tries to reassemble the authentication ticket, it cannot find the full set of cookie pieces it expects, which leads to the error: “Only 0 of the expected 2 chunks were found.”
In my case, I was setting up 3 different portals for a demo, which likely caused issues and resulted in the cookie chunks issue. Might never happen again, but putting this blog together just in case!
Check out the latest post:
Create a Customer Insights Journeys Overview Page for Contacts
This is just 1 of 598 articles. You can browse through all of them by going to the main blog page, or navigate through different categories to find more content you are interested in. You can also subscribe and get new blog posts emailed to you directly.