I’ve just been getting my feet wet with Publishing Service and specifically how to set it up with docker. With that said, I ran into an error which I hadn’t been able to google up a solution for:

2020-01-15 15:30:23.678 -06:00 [Information] New Job queued : e04be103-8b42-4c3e-802d-51ccb96d2d88 - Targets: "Internet"

2020-01-15 15:30:23.678 -06:00 [Error] Error during publish of e04be103-8b42-4c3e-802d-51ccb96d2d88 - Error: "Could not resolve stores core of type source"
System.Exception: Could not resolve stores core of type source
at Sitecore.Framework.Publishing.Data.DefaultStoreFactory.CreateSources(DataAccessContextType dataAccessContext, String[] names)
at Sitecore.Framework.Publishing.PublishContext..ctor(IStoreFactory storeFactory, PublishOptions publishOptions, Guid jobId, DateTime started)
at Sitecore.Framework.Publishing.PublishContextFactory.Create(IStoreFactory storeFactory, PublishOptions publishOptions, Guid jobId, DateTime started)
at Sitecore.Framework.Publishing.Tasks.PublishTask.d__12.MoveNext()

Mind you, I’d seen a lot about missing “targets” which essentially had to do with custom pub targets not being defined in publishing service. That made a ton of sense when I read through them.

This…was another beast. I validated that the sc.publishing.xml was valid. See this snip:

 <StoreFactory>
          <Options>
            <Stores>
              <Service>
                <Type>Sitecore.Framework.Publishing.Data.ServiceStore, Sitecore.Framework.Publishing.Data</Type>
                <ConnectionName>Service</ConnectionName>
                <FeaturesListName>ServiceStoreFeatures</FeaturesListName>
              </Service>
              <Sources>
                <Master>
                  <Type>Sitecore.Framework.Publishing.Data.SourceStore, Sitecore.Framework.Publishing.Data</Type>
                  <ConnectionNames>
                    <master>Master</master>
                  </ConnectionNames>
                  <FeaturesListName>SourceStoreFeatures</FeaturesListName>
                  <!-- The name of the Database entity in Sitecore. -->
                  <ScDatabase>master</ScDatabase>
                </Master>
              </Sources>
              <Targets>
                <!--Additional targets can be configured here-->
                <Internet>
                  <Type>Sitecore.Framework.Publishing.Data.TargetStore, Sitecore.Framework.Publishing.Data</Type>
                  <ConnectionName>Internet</ConnectionName>
                  <FeaturesListName>TargetStoreFeatures</FeaturesListName>
                  <!-- The id of the target item definition in Sitecore. -->
                  <Id>8E080626-DDC3-4EF4-A1D1-F0BE4A200254</Id>
                  <!-- The name of the Database entity in Sitecore. -->
                  <ScDatabase>web</ScDatabase>
                </Internet>
              </Targets>
              <ItemsRelationship>
                <Type>Sitecore.Framework.Publishing.Data.ItemsRelationshipStore, Sitecore.Framework.Publishing.Data</Type>
                <ConnectionName>Links</ConnectionName>
                <FeaturesListName>ItemsRelationshipStoreFeatures</FeaturesListName>
              </ItemsRelationship>
              <!--<Custom>
                <MyCustomStore>
                  <Type>Sitecore.Framework.Publishing.Data.CustomStore, Sitecore.Framework.Publishing.Data</Type>
                  <ConnectionName>MyCustomConnectionName</ConnectionName>
                  <FeaturesListName>MyCustomStoreFeatures</FeaturesListName>
                </MyCustomStore>
              </Custom>-->
            </Stores>
          </Options>
        </StoreFactory>

No mention of the “core” in there…which is funny. Then I managed to look down to the admin screen

So yeah, if you’re using Publishing Service and have switched your DB Context to Core, you’re going to see some errors like that and it will fail. Maybe this is a bug, but I sure feel stupid for it.