Geek Answers Handbook

Fabric service deployment error: ServiceManifest.xml is not available for maintenance

I added the Stateless Service Fabric project to my solution and configured it as my own Web Api host. I did not touch anything in any of the files added by Visual Studio. The only thing that went wrong was the Git merge error in the solution file, which is why I need to add projects manually again.

Projects are named as follows:

  • Project Name / sfproj: ClientCore.CommandStackApi.Deploy
  • Service Name / csproj: ClientCore.CommandStackApi

When I try to deploy, I get the following error:

Application BuildLayout in C: \ SfDevCluster \ Data \ ImageBuilderProxy \ AppType \ ClientCore.CommandStackApi.DeployType is invalid. ServiceManifest.xml is not available for the ClientCore.CommandStackApiPkg service.

When I compare the files and all the project parameters that I can think of with my other Fabric Projects, everything looks fine, but he continues to complain about the lack of a service manifest. The only thing I noticed was the SF project, which was missing from the CommandStackApi project, but that didn't change anything.

I tried on two different computers, the last of which had a new SDK Service Fabric installation, etc.

I assume that this will work if I delete all projects and configure everything again, but this happened earlier when I tried to create the deployment package and powershell script from the MSDN manual, so I really like some understanding of what I can do wrong . If this happens with a more mature project, I will not have the opportunity to recreate the solution from scratch and touch the Blackbox magic settings in Visual Studio, what it should do behind the scenes. Any ideas that may be wrong will be appreciated.

+5
source share
2 answers

So, I finally realized what was wrong.

I looked at files and project-dependent dependencies, but missed the missing service dependency. When two projects were removed from the solution by merging, the SF project was supposed to lose the service link. By adding this to the fixed issue.

+7
source

When I added the existing Fabric project (.csproj) to the service project (.sfproj), I had to create two sections manually in the \ ApplicationPackageRoot \ ApplicationManifest.xml file.

Example:

<ServiceManifestImport> <ServiceManifestRef ServiceManifestName="Sample.Service.Commander" ServiceManifestVersion="1.0.0" /> <ConfigOverrides> <ConfigOverride Name="Config"> <Settings> <Section Name="EndpointConfigSection"> <Parameter Name="UseDifferentPorts" Value="[StatelessServices_UseDifferentPorts]" /> </Section> </Settings> </ConfigOverride> </ConfigOverrides> <Policies> <EndpointBindingPolicy EndpointRef="OwinEndpoint" CertificateRef="ClusterCert" /> <EndpointBindingPolicy EndpointRef="OwinEndpoint0" CertificateRef="ClusterCert" /> <EndpointBindingPolicy EndpointRef="OwinEndpoint1" CertificateRef="ClusterCert" /> <EndpointBindingPolicy EndpointRef="OwinEndpoint2" CertificateRef="ClusterCert" /> <EndpointBindingPolicy EndpointRef="OwinEndpoint3" CertificateRef="ClusterCert" /> <EndpointBindingPolicy EndpointRef="OwinEndpoint4" CertificateRef="ClusterCert" /> </Policies> </ServiceManifestImport>

and

 <Service Name="Commander"> <StatelessService ServiceTypeName="CommanderType" InstanceCount="[MyService_InstanceCount]"> <SingletonPartition /> </StatelessService> </Service>
0
source

More articles:


All Articles