Core elements missing when running multiple local instances

[ben637]

Hi,

I suspect I am doing something stupid here, so apologies in advance. We have a developer who has set up Umbraco commerce and has it working on their machine. This has been committed and I am trying to load the branch.

It is:

• Umbraco commerce 13.1.6
• Commerce Deploy has been added and the setting serialised
• We are using SQLLite
• due to an error I was receiving initially when running Deploy (database lock - same as SQLite Error 6: 'database table is locked #394), I set up the UC database as a separate instance

When I run the site locally, the database is created and the tables created from the Migrations.
I notice that the "Commerce" User Group is not created (there may be other things missing too). If I try to create a Store, I get an error in the UI (nothing in the error logs).

"Server error: Contact administrator, see log for full details.
Failed to save store
Failed to save store teststore: Failed to save store"

The fact the user group is missing suggests some initialisation has not happened. Is there something I need to do if I have UC already in a project but load it on a new database?

I suspect if I can get UC into the state where everything that should exist exists, my Deploy of UC settings may work.

We are yet to deploy this into our Umbraco Cloud Development environment but am concerned I will get the same issue.

What am I missing? Is it something stupid?

Thanks

Ben

[ben637uk]

I had been under the impression that the user group was created as part of the install but I have just seen this https://docs.umbraco.com/umbraco-commerce/13.commerce.latest-lts/getting-started/umbraco-configuration

So it may be that there is not missing set up after all. However I am still unable to create a shop due to errors which don’t present in the log. I will take another deeper look tomorrow but if there is anything that comes to mind. Please let me know.

[ben637uk]

Just discovered the root cause of this. It appears to have been down to this issue #565
after much debugging the only difference between the working and non working instance was environmental and specifically .net version. Further debugging identified an issue with Cache and googling the specific issue once discovered, found the above ticket.

[mattbrailsford]

Ahh, that’s good to know. I wasn’t aware that issue also affected cloud deploys. I take it upgrading to the latest version resolves this?

[ben637uk]

I don’t know for sure that it would have when deploying to the hosted environment in cloud, I had the issues locally prior to looking to do our first deploy up to development. They may not be running the updated .net version yet. I have now upgraded to the latest v13 and it all works now.

[mattbrailsford]

Ok so at least upgrading resolves the issue which is good news. I'd probably suggest you upgrade the live environment as soon as you can and as soon as you are happy things are working locally. The .NET update seems to go out in windows updates so can occur automatically.

[ben637uk]

Its a new build so we don’t have it in live yet. But yes if I did it would be going out ASAP!