I am trying to install Microsoft Azure service fabric while installation I am getting below error.
There is some dependency on other product but I am not able to get it.
Any help will be appreciated.
Related
I have installed the following packages into our Dev systems with no failures.
2sic_2SexyContent_08.12.00_Install
2sic_2SexyContent_09.43.02_Install
2sic_2SexyContent_10.25.02_Install
However, when I try to run these in our production DNN Evoq 9.1.1 site that is running in a Azure Web App, I am getting errors with the database entries and a failed installation. In short, the errors are about passing Null values into database objects. Unfortunately, I do not have any logs to share, but was wondering if anyone else has had a similar issue with installing 2sxc in sites running with Azure Web Apps. Azure leverages more control on the SQL Server and databases than a traditional set up. Currently this production site has a 2sxc 7.1.2 and I want to upgrade it to 10.25.02.
I'm trying to back up an azure vm to acronis, but whenever I try to deploy the acronis extension on azure I recieve the following error:
At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.
VM has reported a failure when processing extension 'AcronisBackup'. Error message: "Failed to connect to Acronis Backup Cloud. Check specified credentials and firewall settings. For more information please refer to https://kb.acronis.com/content/47189"
It basically says that the provisioning state failed. How can i fix this?
Issues related to installation of Acronis extension should be investigated with the help of Acronis support team.
Just a suggestion, you can try redeploying the VM to see if that lets you successfully install the extension. If issue persist, reach out to support and share below information with the technical professionals.
Error details with screenshot if possible
Detail steps followed for deployment
I have installed latest service fabric 2.3.311 runtime and when I run actor application. I see the error attached. Please help!. I'm stuck here.But I'm able to run all the stateless and state ful services.
How can I install a MSI into service fabric remotely or after a deployment? I have an install I need on each node in the cluster. Using Remote Desktop and running the MSI is not an option. I need something that scales. Any thoughts?
You could take a look at Desired State Configuration (DSC) there is an extension which you can use within your ARM template, it is a big topic so here is a couple of links that might help get you started.
vmss with dsc
installing msi with dsc
I figured out how to do this using the SetupEntryPoint and ExeHost in the ServiceManifest.xml file. See the documentation here Documentation to SetupEntryPoint
We just upgraded from the Windows Azure 1.7 SDK to 2.0.
This created a lot of problems in the codebase, but we got them ironed out and running locally.
Now when we try to publish to our cloud service machine in Azure, the worker role keeps trying to run but can't start.
My guess is that the cloud service machine is missing the 2.0 SDK.
Is there some way to install this manually on the remote machine? I can RDP and I've been looking around, but I can't seem to a) Verify which version it's trying to use and b) How to install a newer SDK.
I've found some errors about the worker role not running, but they're pretty uninformative.
The solution ended up being pretty simply, but I imagine other people will run into this problem.
We had 5-7 projects all referencing Azure SDK 1.8. Specifically these libraries:
Microsoft.ServiceBus
Microsoft.WindowsAzure.Configuration
Microsoft.WindowsAzure.Diagnostics
Microsoft.WindowsAzure.ServiceRunTime
Microsoft.WindowsAzure.StorageClient
If the project is a cloud service project, you need to right click on the project, go to properties, and upgrade the project. This changes the deployment when publishing. It will create the Azure VM based on the cloud service Azure SDK version. I missed that at first.
All the libraries above need to be upgraded to SDK 2.0 in all projects. Initially I missed some projects that were dependencies - and missing the Microsoft.ServiceBus library.
The last part was moving from Microsoft.WindowsAzure.StorageClient to Microsoft.WindowsAzure.Storage. I guess for SDK 2.0 they changed the library name, which has also introduced some breaking code changes.
After all that the cloud service now publishes correctly. Whew.