Deployment to Azure stuck on Copying

[former_member341062]

The deployment of the

SAP BW/4HANA 1.0 SP05 and BPC 11 SP01 including BW/4 Content SP02 image from CAL to MS Azure got stuck at 98% Copying. After waiting 2 hours on 98%, I checked Azure where there was no VM created, only storage and network. I am not able to find a cancel button in CAL, so I tried to delete the resource groups on the Azure side. This caused the copy percentage in CAL to go down to 0%, but the process is still stuck and I cannot cancel it.

How can I reset the deployment operation in CAL?

Best regards,

Ola

[stanimir_eisner]

Hello Ola,

Can you provide the ID of your instance? You can copy the number from the URL when you go to Instance Details.

Then you can terminate the instance and create a new one. It just worked for me and I am not aware of other comlains.

Best regards,

Stanimir

[former_member341062]

Hi Stanimir,

The instance id is 54549759 - my initial question was how to cancel an on-going deployment that gets stuck. There seems to be no cancel button or any other way of terminating the instance at that point.

With this particular error, I've now learned that the reason for the copy operation stopping in the first place was that MS suspended my MSDN subscription, siting that the spending limit had been reached. I have raised a ticket with MS on this, because there were more than a 100 euros left in the account credit for this month, and I do not understand what possible operation the CAL AppId could have started to use all that within 1-2 hours. Especially since the actual VMs were not created. Subscription cost analysis does not provide a clue as of yet at least (there can be some lag).

Best regards,

Ola

[stanimir_eisner]

Hi Ola,

Indeed the root cause of the problem was in the status of your Azure subscription. The error message from Azure was:

ReadOnlyDisabledSubscription - The subscription 'XXXXX' is disabled and therefore marked as read only. You cannot perform any write actions on this subscription until it is re-enabled

Best regards,

Stanimir

[former_member341062]

Hi again Stanimir,

After some rounds with Azure support I now know what was the cause of the problem, and I wanted to mention it here because it could happen to others that use a credits based subscription like a Free account, Azure Pass or an MSDN subscription.

Before I attempted to deploy the Hana Dev image I mistakenly deployed the Trial image. I realized the mistake, stopped and terminated that deployment as soon as it was completed, but the VMs did have time to start, and were allowed to start by Azure. However, unknown to me, the trial image contains a server OS “SUSE Linux Enterprise Server for SAP Priority” payable to SUSE not Microsoft, meaning that Microsoft will not allow you to use Azure credits to pay for this. Azure does not check spending instantly, but as soon as a few cents of charges to a third party was registered the "spending limit" for this was reached since it was technically 0. That there are more than one cause for the spending limit alert and the consequence of this the disabling of the whole subscription is not documented nor is it possible to see in the portal what had happened.

The only way to re-enable the subscription is to remove the limit by adding a credit card and paying the "debt" since it will forever be over the limit. I have mentioned to Microsoft that I do not approve of this draconian approach to debts collection 😉 This kind of error should not be allowed to happen or they / third party vendors should cover the marginal costs that could occure before the spesific resource is throttled.

Best regards