Invalid serial number for shell descriptor Error

[JoshLefebvre]

I am constantly getting the following error when trying to setup a new tenant:

I am not familiar with the terminology used here and therefore don't know where to look in order to further debug. Where exactly is this serial number getting generated ?

When I look at priorSerialNumber it is set to 0, while serialNumber is set to 3 ?

[jtkech]

Which version? Can you share the recipe you used?

Looks like something went wrong in a recipe step

Would need more infos, a more complete satck trace

Do you have some errors logged under App_Data/logs?

[JoshLefebvre]

Hey jtkech,

I was running a custom recipe. I haven't confirmed but I am pretty sure I was forgetting to set my database prefix string which resulted in a conflict. Thanks for pointing me in the right direction

[jtkech]

@JoshLefebvre Cool then ;)

[nikeshmhrzn]

InvalidOperationException: Invalid serial number for shell descriptor

I am facing the same issue how do we resolve it ?

[jptissot]

@nikeshmhrzn I think you need to restart the site.

[jtkech]

@nikeshmhrzn

I saw your comment on gitter

I got this error while implementing new theme in orchard core.

Which version are you using? Did you just enable a new theme? OR run its recipe through the admin UI? OR by selecting its recipe on a new fresh setup?

E.g. if you delete a tenant folder, then re-do a setup but pointing to a database where a shell descriptor already exists and with a different serial number

[Piedone]

I've seen this happening but have no idea how to reproduce it; the exception itself tells that the shell' state (like which features are on/off) is out of sync between the DB and what's loaded into memory in the app. In any case, an app restart should solve it.

[PixPunch]

I did setup and remove tenant with same name multiple times to test the Custom Recipe and dump into 'Invalid serial number for shell descriptor' error. The issue was that I was trying to use the same name of tenant, but when you name it differently - everything is fine.
Following steps helped me to resolve an issue while developing at localhost:

1. Stop your app
2. Delete all database tables with prefixes of your faulty tenant (if they were created).
3. Open OrchardCore.Cms.Web\App_Data\Sites, and Remove a folder with your faulty tenant.
4. Open OrchardCore.Cms.Web\App_Data\tenants.json and Remove settings of your faulty tenant.
5. OrchardCore.Cms.Web\wwwroot\is-cache and Remove everything here

Now create your tenant gain.