When I attempt to create a cluster using the CreateServiceFabricCluster.ps1 script I get the following error: "JSON config is invalid. Check syntax/model.: System.IO.FileNotFoundException: Could not load file or assembly 'Newtonsoft.Json, Version=6.0.0.0...". I have tried this three different systems (2012 R2, and two 2016 servers) with the same results. I'm using runtime version 5.3.3.11 and SDK version 2.3.311.
I found the problem. You can't have the Service Fabric Runtime or SDK installed on the same machine you are building the cluster on. Once I removed both of those I was able to create the cluster.
Related
I have implemented Xero oAuth20 in Asp.Net Web forms using Xero.NetStandard.OAuth2 -Version 0.4.0 version from Nuget package manager.
This is working fine in my local, how ever if I try to deploy solution in Azure server, the publish is getting failed.
Please help to fix this issue.
This is the error
"Your role instances have recycled a number of times during an update or upgrade operation. This indicates that the new version of your service or the configuration settings you provided when configuring the service prevent the role instances from running. Verify your code does not throw unhandled exceptions and that your configuration settings are correct and then start another update or upgrade operation."
When trying to create linked service in azure data factory which uses the Microsoft integration run time (self-hosted), the connection test throws error "Could not load file or assembly 'System.EnterpriseServices.Wrapper.dll' or one of its dependencies. The specified module could not be found."
screenshot with error
This is for copy activity in azure data factory which will have source db as an on-premise SQL db, self-hosted integration runtime is set up and running successfully.
Could not load file or assembly 'System.EnterpriseServices.Wrapper.dll or one of its dependencies
Since self-hosted integration runtime is set up and running successfully, this error may be caused by the environment of on-premise. You could try to re-install .net framework or follow below similar solutions:
1.System.EnterpriseServices.Wrapper.dll error
2.Could not load file or assembly 'System.EnterpriseServices.Wrapper.dll'
I have an infrastructure pipeline in Azure DevOps that setup a service fabric cluster. The fabric cluster's key vault and certificate are generated by a custom PowerShell script I wrote, while the cluster and its resources are generated by an ARM template. They are executed as tasks in the pipeline.
However, I am having problems accessing the generated fabric cluster via Service Fabric Explorer using web address: https://myclustername.mylocation.cloudapp.azure.com:19080/Explorer
I also have problem accessing the nodes using RDP:
I tried the following:
Restarted virtual machine scale set.
Checked the ports are open on load balancer: 3389-3391
I don't get this problem if I setup the fabric resource group with visual studio.
I checked the certificate generated and made sure it has a subject that is the same as the fabric cluster url. Does anyone know what might be causing this?
I think I used the ARM template that came with visual studio 2017. The template is old (2016). I updated the template to the recent one and the issue is resolved:
https://github.com/Azure/azure-quickstart-templates/tree/master/service-fabric-secure-cluster-5-node-1-nodetype
I still have some problem for adding a custom internal load balancer, but all the other resources out of the ARM template are working.
The Service Fabric runtime cab used to be part of the standalone package, but appears to have been removed in the latest release. As far as I can tell, the new DownloadServiceFabricRuntimePackage.ps1 script should do the job of retrieving it when creating a cluster. However, running the new script fails with the below error. Where can I manually download the latest CAB please?
"Runtime package cannot be downloaded. Check you internet connectivity. If the cluster is not connected to the internet use DownloadServiceFabricRuntimePackage.ps1 script to download the latest package. Then run CreateServiceFabricCluster.ps1 -ClusterConfigur
ationFilePath -FabricRuntimePackagePath to create the cluster. Exception thrown : System.IO.FileNotFoundException: Cannot find Fabric resource file ClusterSettings.json in C:\Program Files\Microsoft Service Fabric
\bin\fabric\fabric.code C:\Windows\Microsoft.Net\assembly\GAC_64\Microsoft.ServiceFabric.DeploymentManager\v4.0_5.0.0.0__31bf3856ad364e35.
at Microsoft.ServiceFabric.DeploymentManager.Common.StandaloneUtility.FindFabricResourceFile(String filename)
at Microsoft.ServiceFabric.DeploymentManager.Common.StandaloneUtility.GetGoalStateUri()
at Microsoft.ServiceFabric.DeploymentManager.DeploymentManagerInternal.d__10.MoveNext()"
Thanks,
Hans
Ok, I found the needed link on https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-cluster-creation-for-windows-server here.
Hans
I Try to deploy a application using Microsoft Release Management for Visual Studio or better known as "InRelease". But i face unexpected Problems using the MSI-Deployer.
The deployment fails with the flowing error:
Setup.msi XXX139W8 10/1/2014 11:19:18 AM 00:00:00 Package location '\\Server\drop\Application\Build_20140930.5\Setup.msi' does not exist or Deployer user does not have access. Failed
First suggestion(incorrect Path) is not the case, i double checked that.
So why does my Deployer user not have access to my server? And how to fix that?
I tried out running the DeploymentAgent as Administrator, as Local Service adding XXX139W8$ permissions to the drop folder, running as domain user with admin rights on the drop folder.
Sadly the deployment agent is totally unreachable or the error mentioned above shows up.
Here are some system specs:
TFS and RM Server run on a Windows Server 2012 R2 with SQL Server Express 2012 Installed.
The client i am Working on uses the Release Management Client for Microsoft Visual Studio 2013
The Target Machine is a Windows 8.1.
The deployer user is defined in the MS Deployment Service, ensure that this account has access to your Drop folder. I give the domain\EVERYONE account read access to the drop folder so that anyone can read the data
I resolved this Problem.
The cause was that i specified a File as Package (quite confusing if you try to deploy a single msi file) but the Component should only specify a Folder "Package".
The deployment agent fails to access the Folder (Setup.msi) and fails with the error i showed above.
Then i wasted hours in trying to fix my access problem, because if i enter the "Package location" everything worked fine._.