I uninstalled and re-installed the Azure CosmosDB emulator on my PC, but cannot start it up now. I keep getting the following error:
Failed creating emulator certificate. Error: 0x8009000f
I have run through all of the steps in the trouble shooting guide but I am still experiencing the problem. Has anyone experienced this too and if so, how did you manage to resolve it?
Many thanks.
From Docs
In order to obtain a certificate to use with languages and runtimes
that do not integrate with the Windows Certificate Store you will need
to export it using the Windows Certificate Manager.
Also when you are running try to use https
Related
im struggling install a website on a given server from my client, which already has IIS but seem like it wasn't working well.
After a few attempts, I tried to reinstall the IIS, and from some article i heard that I must remove the Windows Activation Process Service.
Then, in a moment of stupidity I ran the command sc delete service was in Powershell. After that I realized I should user the Server manager to Uninstall/Install. So I tried to uninstall then install it again, and reset the server. But now Windows Activation Process Service doesnt appear in the Services list anymore (run --> services.msc).
Could you tell me how to install it properly now? Thank you so much.
Silly me, I remove the IIS and reinstall again, now it works. Thanks everyone.
I've been getting above error since yesterday when I'm debugging my MVC webapp locally via VS 2019. The error comes from the negotiate request which is something like below:
http://localhost:53652/signalr/negotiate?clientProtocol=2.1&connectionData=x
I've deployed it to one of our Dev servers in Azure cloud, and now that too getting the same error and SignalR is not workable. However, SignalR is still working fine in our Production servers.
I've followed this: https://github.com/Azure/azure-signalr/issues/909
And this: https://forums.asp.net/t/2154631.aspx?Error+500+using+Azure+SignalR+service
But still no use.
After enabling diagnostics as per the first link, I was getting an error saying that I cannot connect to our Azure SignalR instance. But I don't get it since, the production servers can connect and working fine.
I was in Azure SignalR v1.2.3, and later updated to v1.4.3 thinking that would resolve. But still no luck.
Any help will be highly appreciated.
Thank you.
I created a new app repository in Github, built on the Meteor platform. I am having significant difficulty deploying the app to my DigitalOcean droplet, however. I am trying to connect my Github repository to the droplet and to deploy that to my domain. I am trying to do this in SSH using puTTy; however, after setting up a root account and password, I am unable to log in through SSH. I receive the following error: disconnected: no supported authentication methods available (server sent:publickey)
Does anyone know why this error is coming up? I have looked through more tutorials for deploying a meteor app on digitalocean than I care to admit, but they all seem to take different approaches and many are outdated. Any advice would be greatly appreciated!
Thank you
I reckon the easiest way is to use meteor up. It's a very simple process, and you don't need to be continually sshing into your target server, with all the hassles involving ssh keys.
In my experience, once you have it set up, it's a very painless process, and you can deploy with a simple command each time.
http://meteor-up.com/
It looks after the following:
Setting up your server with docker instances
Creating SSL certs using Let's encrypt
Building your app, bundling it, transferring it
Starting the app
Rolling back if it doesn't work
There is some trust involved, but it's worth it for a seamless deployment scenario
After following the Meteorjs instructions and successfully creating an app, the deployment step failed. I am familiar with the developer account and the normal procedure. The Error being provided is stating that I have unauthorized access to Galaxy and that I am attempting to deploy on it (this is the paid cloud service of Meteor released recently and not the testing cloud service of Meteor.com for developers). I am not understanding why this redirection is occurring. It would be helpful to point out the issue. The name of the app being deployed follows the format appname.meteor.com. Please also note that
The developer-account dependency was installed
The app was created through the Meteorjs dashboard
I was also logged in from the console prior to deploying
Thanks in advance
I would like some clarity on the process you're attempting, however meteor killed free hosting in March of 2016 (three months ago at the time of this post).
This post explains the details of MDG cancelling that service.
This means there is no longer a testing cloud service, which seems like what you're attempting to deploy to (can't tell as you've given no specifics on your process), there is only Galaxy.
I am trying to publish a website from my computer to an IIS web server via web deploy.
I have 3 servers. All servers have installed the same things (Webdeploy etc.) and the services are started (Web Deployment Agent Service and Web Management Service).
On the first server I have no problems on connecting. But the other two servers give me some error when I "Validate Connection" in Visual Studio to the IIS. When I look at the logs on the IIS server, there are my accesses listet with html code 200 (ok).
An error ocurred when the request was processed on the remote computer. Filename: MACHINE/WEBROOT
Error: The configuration section 'system.webServer/management/delegation' cannot be read because it is missing schema
I really have no idea what could solve this problem and hope you are able to help me.
I had the exact same problem, it turned out I had installed Web Deploy 3.6 on top of 3.5. Remove Web Deploy 3.6 and reinstall 3.5 and see if it solves your issue.
You can also try #james-wilkins comment below: "In my case I installed Web Deploy BEFORE installing the management service..."
Uninstall and then re-install Web Deploy.
This fixed the problem for me -- the 'repair' option in the installer did not.
In my case, I installed Web Deploy BEFORE installing the management service. I tried to do a "change" on the install to include the management service (or you can add the feature from add/remove windows features), but that didn't help (got the error on this post). In the end, a simple uninstall and reinstall of 3.6 was what worked for me. Seems it needs the Web Management Service to be installed FIRST. Typical MS instructions don't even mention this at all.