OBEngine Service missing from a fresh install of Azure Backup - azure

I downloaded the MS Azure Recovery Agent from the portal and registered and set up the server fineI set up a quick backup job to test and when I came to run it I get the following error:
I have rebooted the server and still the same error
The service is missing so i guess that's why it won't run but I cant see or find how to get that service installed.
I would not have expected this issue from a clean install?Anyone help please?

Related

Azure DevOps Artifact Agent log "Error: UPGRADE FAILED: timed out waiting for the condition"

So the CD part was working perfectly fine for a whole year, now without any changes it started giving this error. Any help would be appreciated.
This is the command that gets executed:
The issue here has nothing to do with Kubernetes or the AKS cluster( that was my first thought) I tried deploying manually using the same commands I set up in the CD pipeline, I figured that my docker image was broken and wasn't matching the latest helm release.
I solved it by replicating the issue manually (both CI and CD) and inspecting the pipeline in debug mode.

Azure CosmosDb Emulator Error: Failed loading emulator secrets certificate

I installed Azure CosmosDb Emulator but it does not start and gives error:
"Failed loading emulator secrets certificate. Error: 0x80092022"
When I check my certificates, it also does not create any certificates related to cosmos db emulator. Then, I tried to create the certificates manually by "Microsoft.Azure.Cosmos.Emulator.exe /GenCert" command on cmd but this time show the error "Error generating Emulator SSL certificates"
How can I solve this problem?
This is an issue I am actively troubleshooting as well. The way to generate the missing certificates is to do the following:
Open cmd.exe with Administrator
Navigate to CosmosDB Install folder with this command
C:\Program Files\Azure Cosmos DB Emulator
Run this command to ensure the CosmosDB Emulator is shutdown
Microsoft.Azure.Cosmos.Emulator.exe /Shutdown
Run this command to generate the missing certificates:
Microsoft.Azure.Cosmos.Emulator.exe /GenCert
Ensure the following certificate correctly generated in Computer Certificates under Local Computer\Personal\Certificates
DocumentDbEmulatorCertificate | LocalHost
Start CosmosDB from either the start menu or command line and wait for it to fully initialize

Unable to install the VSTS Agent Azure VM extension

I am unable to install the VSTS Agent Azure VM extension on an Azure VM. I tried both the Install extension blade in the Azure portal and the Powershell option. When I try from the portal it just gets stuck at transitioning. If I run the Powershell script it gets stuck trying to connect to server.
I was able to install it on another server without any issues. The 2 servers are part of a web farm so they are exact images.
I am following the steps detailed at this url https://learn.microsoft.com/en-us/vsts/build-release/concepts/definitions/release/deployment-groups/howto-provision-deployment-group-agents?view=vsts .
I am trying to deploy from VSTS to an Azure VM.
This is the screen when I try to run the powershell script.
Run the config file directly (from C:/vstsagent folder) in cmdline and try again with dev.azure.com/{organisation name} url.

Deluge Windows Service

I am trying to run the DelugeD.exe as a windows service. After installing Deluge and creating the services using NSSM, I try to start the service and get the following error:
Windows could not start the Deluged service on Local Computer. The service did not return an error. This could be and internal Windows error or and internal service error. If the problem persists, contact your system administrator.
I have created the Deluge-web-debug.exe as a Windows Service and it successfully starts. When I browse to http://localhost:8112 the web client appears, however the Connection Manager shows the Deluged daemon has not started.
No error, no logs, what could be the cause?
Thanks!
I thought I would start from scratch, reinstall deluge for windows, and try again. After this it still failed.
Using nssm, the error was:
deluged: Unexpected status SERVICE_PAUSED in response to START control.
This placed the service in a perpetual Paused state.
Finally, I decided to tear down the services using nssm remove, kill any running deluge processes, then delete the Config folder where deluged was pointing.
I am certain deleting the Config folder and all files was what solved the problem, and now it starts successfully.
I think I just solved this one by checking the "Allow service to interact with desktop" box under the LogOn tab for both the Deluge daemon and the WebUI services I created with nssm:
"Allow service to interact with desktop" in services.msc

Deploying Sails App on Openshift

Can any one help me with deploying a SailsJS app on Openshift?
I followed How you get Sail.js running on Openshift
After making my changes and pushing it to the repo I get the status as successful but when I go to my link it says
Service Temporarily Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
Apache/2.2.15 (Red Hat) Server at kittylogintest-kittygame.rhcloud.com Port 80
I finally managed to deploy my sails application on openshift
Most of the steps mentioned in the link mentioned in my question will help
After following the steps i was getting an error stating permission denied for grunt-cli
I solved it by SSHing in to my app and then doing the npm install in app-root/runtime/repo
Hope this helps if some one stumbles on the same stair.

Resources