About cj_blake

cj_blake · ‎12-02-2024

@gordononline, I'm sorry to hear that you've been having so many issues with your deployments. We resolved an issue at the end of last week that I think may have been affecting many if not all deployments from early November. It's possible that your attempts may have been included in that. If you clear out those old deployments and attempt a new one in a known good region (say, US West), and try again, what do you get? If the deployment fails, and hopefully it doesn't, can you open the details of the error and send them over?

cj_blake · ‎11-28-2024

@paul-blu yes, we're aware of this and will be looking to resolve soon. That shouldn't affect the running of the system though. Those automations are convenience items for managing the deployment (stop, start) but those things can be done manually too.

cj_blake · ‎11-27-2024

@paul-blu this afternoon we have published a change to resolve the deployment issues that you were experiencing. Please try a new deployment from the Marketplace. If you can let me know the result of that deployment, that would be great. Thanks!

cj_blake · ‎11-26-2024

@paul-blu I believe we have found the cause of the deployment failures after being able to replicate the behavior internally. We are working on a fix and will let you know as soon as that is released.

cj_blake · ‎11-25-2024

@paul-blu please see this post from Chris Hemedinger on the support resources available. To help debug your deployment, it would be helpful if you could follow the instructions at this link and post them back to this thread. That should give us more information on the root cause of the deployment failure and timeout.

cj_blake · ‎10-09-2024

Hi @Lillioja - Another user has had this issue before. Perhaps you could review your log events and check whether or not their solution works for you.

cj_blake · ‎10-07-2024

Sorry to hear that you are having this problem. I'd like to check that our default SSH rules have been created as we'd expect. If you are looking at the jump box in the Azure portal, select "Network settings" from the menu on the left-hand side. You should see something like this: You should find your IP or your IP range listed in the "source" column on the same row as a rule ending with "-ssh". Can you confirm that you see this? If your IP is not listed, you can use the AddIPs runbook to add your IP address to the deployment.

cj_blake · ‎09-26-2024

Oh that's interesting. We check for an explicit "False" there. I don't know why that bool would be blank! Have you tried doing another deployment?

cj_blake · ‎09-26-2024

Hi @DQM I wonder whether or not you may have accidentally ticked the "set authorized IP ranges" box, but left an open range? Something like this: That would be enough within our deployment mechanism to switch from using the Let's Encrypt certificate issuer to using self-signed certificates. If you are using restricted IP ranges and you want to make the certificate warnings go away you can follow the instructions that we have published on importing the self-signed CA certificate into a certificate store.

cj_blake · ‎09-25-2024

Hi everyone, we're aware of these deployment failures and are seeing them internally too. We are investigating the problem and are looking into it. I will keep this thread updated when we have more news.

cj_blake · ‎09-25-2024

Hi everyone, we're aware of these deployment failures and are seeing them internally too. We are investigating the problem and are looking into it. I will keep this thread updated when we have more news.

cj_blake · ‎04-15-2024

You will be billed for your use of SAS Viya Pay-As-You-Go by Microsoft and those charges will be visible in the Azure Portal. There are actually two places that you need to go to see these costs, one for the software costs and another for the infrastructure costs. 1. If you do a "cost analysis" on the resource group where you deployed the managed application, you can get the SAS Unit costs: 2. If you click on the Managed Application and then select the "Managed Resource Group", and do a "Cost Analysis" at this level you can get the infrastructure cost breakdown: Hope that helps! Chris

cj_blake · ‎03-27-2024

It looks like the subscription that you are using is not configured correctly. We can see that you are getting the error: The subscription is not registered to use namespace 'Microsoft.Compute' Please see this Microsoft page for more information and instructions on how to configure your subscription to access the resources required: Resource provider registration errors - Azure Resource Manager | Microsoft Learn.

cj_blake · ‎03-27-2024

OK. In this case I would ask you to open "Developer Tools" in your browser and see if you get any errors when you click the download button: Using the DevTools Console in Google Chrome to Identify Errors (interplaylearning.com). Alternatively, if you already have an SSH key pair on your machine, during the purchase process you can select to use an existing key pair. You'll then be provided with a text box into which you can copy your existing public key.

cj_blake · ‎03-27-2024

@surajshindekite thanks for reaching out and I am sorry that you experienced this. I have tried a number of times this morning to replicate what you are seeing but have not been able to. For me, the button to download the key pair is blue: Please can I ask you to start your deployment again? I may help to completely close all windows of the browser that you were using before re-attempting.

Online Status	Offline
Date Last Visited	2 weeks ago