Azure CosmosDb Emulator Error: Failed loading emulator secrets certificate - azure

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

Related

Azure CLI - AKS Communication Issue

i have problem in executing Kubectl commands, its errors out with 502 certificate error
Unable to connect to the server: x509: certificate signed by unknown authority
I can able to login to az login after that I'm connecting with my AKS cluster by using below command
az aks get-credentials --resource-group sitecore10.x-dev-k8s --name sitecore102-Dev-AKS-v1 --overwrite-existingenter code here
After that executing Kubectl get pods or Kubectl get services but it doesn't work
already tried adding environment variables
Opened .kube file and opened the same Url in browser , displayed the below error
Resolved
I got a chance to resolve this issue.
The actual issue is AKS URL (https://AKSInstance.hcp.westus.azmk8s.io:443) is blocked by Company Internet Monitoring Software (Netskope).
i raised a support ticket to whitelist the URL https://*.azmk8s.io
How to check the issue :
C:\Users[YourUserName].kube open config file to identify the AKS URL, try opening the URL directly in the browser, if your getting 401 authentication issue then your good, otherwise if your getting error message related to certificate then it should be your Internet Monitoring software is blocking the AKS URL calls.
I tried to reproduce the same in my environment to connect the AKS cluster from a windows machine:
I have created AKS cluster, like below.
Go to Azure Portal > Kubernetes Services > Create.
Download Kubectl tool here and install the same on a windows machine, like below.
open powershell in CMD and navigate to download folder and run kubectl.exe , like below.
connect your cluster using cloud shell to download .kube.config file. like below.
once connected to the cluster, download the config file to the Local windows machine.
Create a folder with .kube name in your username folder and place the downloaded config file in the same folder.
Path C:\Users\yourusername
Now run kubectl cmd to get the AKS cluster details from the windows machine, like below.
Reference: kubectl unable to connect to server: x509: certificate signed by unknown authority by bherto39.

Cloud Explorer Equivalent Debug VS2022 for zipped published code uploaded to storage?

Cloud explorer in VS2022 has been removed. I publish & zip the code and upload it to Azure in a private azure storage account that then runs Function Apps (running from a package file). How can I debug remotely like I used to do with clould explorer?
Publish does not offer the Hosting option. so the Stackoverflow answers don't work for me. Also I have connected the Function App to Connected Services and I click on Attach debuger but it does not stop the code when executed, i.e. step-in code to debug doesn't work like Cloud Explorer did.
After deployment checks some settings.
Check Remote debugging is ON on azure portal and Select the Remote Visual Studio version, if not selected.
Go to visual studio and go-to tool and select get tool and features. You just need to take Azure development. after this Storage Emulator is automatically installed if not installed go to the Microsoft site and install this.
If installed you can run it by using this command. AzureStorageEmulator.exe start. More information about Azure Storage Emulator for Development and testing by Microsoft Document on
Change Configuration from Release to Debug.
Start Azure Storage Emulator below cmds. if not installed in your system click here to Download from the Microsoft site.
C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator>AzureStorageEmulator.exe
Windows Azure Storage Emulator 5.10.0.0 command line tool
Error: Expected command as first argument.
Usage:
AzureStorageEmulator.exe init : Initialize the emulator database and configuration.
AzureStorageEmulator.exe start : Start the emulator.
AzureStorageEmulator.exe stop : Stop the emulator.
AzureStorageEmulator.exe status : Get current emulator status.
AzureStorageEmulator.exe clear : Delete all data in the emulator.
AzureStorageEmulator.exe help [command] : Show general or command-specific help.
See the following URL for more command line help: http://go.microsoft.com/fwlink/?LinkId=392235
C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator>AzureStorageEmulator.exe start
Windows Azure Storage Emulator 5.10.0.0 command line tool
Autodetect requested. Autodetecting SQL Instance to use.
Looking for a LocalDB Installation.
Probing SQL Instance: '(localdb)\MSSQLLocalDB'.
Found a LocalDB Installation.
Probing SQL Instance: '(localdb)\MSSQLLocalDB'.
Found SQL Instance (localdb)\MSSQLLocalDB.
Creating database AzureStorageEmulatorDb510 on SQL instance '(localdb)\MSSQLLocalDB'.
Granting database access to user FAREAST\v-pusharma.
Database access for user FAREAST\v-pusharma was granted.
Initialization successful. The storage emulator is now ready for use.
Error: Unable to start the storage emulator.
C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator>netstat -p tcp -ano | findstr :10000
TCP 127.0.0.1:10000 0.0.0.0:0 LISTENING 9764
C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator>taskkill /F /PID 9764
SUCCESS: The process with PID 9764 has been terminated.
C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator>AzureStorageEmulator.exe start
Windows Azure Storage Emulator 5.10.0.0 command line tool
The storage emulator was successfully started.
C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator>
Check whether Storage Emulator show is connected or not.
Then add break point on visiual studio and run function . it's working,
Using this option to attach debug remotely. because in visual studio 2022 not show Cloud Explorer.

jenkins job unable to read Service fabric registry Keys

I am trying to setup jenkins job to create service fabric cluster locally using powershell script DevClusterSetup.ps1[By default available in setup directory] file. The script is working perfectly when runnin through local powershell. Biut when i am runnins same script it is unable to read registry keys of service fabric. When i am trying with other registry keys its working. only with service fabric reg keys its not working.
Get-ItemProperty : Cannot find path 'HKLM:\Software\Microsoft\Service Fabric SDK' because it does not exist.
At C:\Program Files\Microsoft SDKs\Service Fabric\ClusterSetup\DevClusterSetup.ps1:61 char:20
Where as service fabric sdk is already installed in my system.

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

OBEngine Service missing from a fresh install of Azure Backup

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?

Resources