I was working with Microsoft Azure REST API(https://learn.microsoft.com/en-us/rest/api/deviceupdate/2021-06-01-preview/device-update/get-update#code-try-0) and found that the don't have any proper documentation or may be I was unable to find it. In the end I was unable to find it, so if you can guide me that will be helpful. I need instanceID to be provided in below path
https://{endpoint}/deviceupdate/{instanceId}/updates/providers/{provider}/names/{name}/versions/{version}?api-version=2021-06-01-preview
I have tried using Instance name from below image and also resource id but no use.
I request Microsoft to Please stop providing half Knowledge.
What is meaning of blue here? can I write my favourite colour? Also there should be an error message if something went wrong.
Related
I have been trying to set up a snowpipe to ingest data from blob storage in Azure into snowflake, following this guide, I think I have done everything correctly although I am new to azure and snowflake so may have missed something obvious. Everything seems to have been set up correctly on both sides, but whenever I check the pipe status using SELECT SYSTEM$PIPE_STATUS('azure_pipe');, I get the following:
{"executionState":"RUNNING","pendingFileCount":0,"notificationChannelName":"https://snowflakedata.queue.core.windows.net/snowflakequeue","numOutstandingMessagesOnChannel":2,"lastReceivedMessageTimestamp":"2022-02-18T13:25:12.107Z","channelErrorMessage":"downloadAttributes error:Queue not found for channel Name=https://snowflakedata2.queue.core.windows.net/snowflakequeue, AccountId=6713, NotificationChannelID=2045, IntegrationID=1784764","lastErrorRecordTimestamp":"2022-02-18T17:32:47.854Z"}
I'm not sure what I have done wrong, the snowflake app has the queue contributor role in azure and I'm fairly sure I set everything else up correctly. If anyone could point me in the right direction as to how to troubleshoot this that would be really helpful!
I had the same issue as you did just this week when trying to create a Snowpipe for Azure. Using SELECT SYSTEM$PIPE_STATUS('azure_pipe'); gave the exact same error message as you have shown above. Thankfully, Snowflake Support has provided me with the answer and an explanation.
Answer:
Drop all of the objects relating to the Snowpipe (integrations, pipe, stage, etc). Then recreate them in the exact order and specification as shown in this documentation.
Explanation:
The issue for me was caused because I kept using create or replace on the objects when I was modifying them (eg changing the comment on a pipe). This re-created the object and broke the links between the objects in the Snowpipe and prevented the Snowpipe from working as intended. Dropping and starting again solved it for me.
I have a web .net application, it will read an excel file using the Microsoft Access Database Engine. It works fine , but recently it is giving some error. From the log, these 2 points i think are the highlight, which I still could not find a solution. I have tried reinstalling Microsoft Access Database Engine, but not helping. Google for it, but didn't manage to get a hint as well.
One funny thing is whenever it happened, I recycle the app pool on IIS and issue was resolved. But then the issue will come back very quickly. If anyone had come across this, would appreciate any help. Thanks.
The .Net Framework Data Providers require Microsoft Data Access Components(MDAC). Please install Microsoft Data Access Components(MDAC) version 2.6 or later
Retrieving the COM class factory for component with CLSID {2206CDB2-19C1-11D1-89E0-00C04FD7A829} failed due to the following error: 800703fa Illegal operation attempted on a registry key that has been marked for deletion. (Exception from HRESULT: 0x800703FA)
To resolve this problem, please follow official doc to try.
Method 1
Do not log on to the server for interactive sessions by using a service account.
Method 2
Disable the related Windows User Profile Service feature.
For more details, please read this article.
"800703fa Illegal operation attempted on a registry key" error
I'm trying to make a knowledge base and I'm getting an Http 500 response when I try to test the KB directly in the platform qnamaker.ia furthermore I published and queried with postman but looks like a problem with the service, Does anyone know if there is any general error with the service?
I'm trying to upload a (.PDF) file with a standard S price, I tried with different locations but didn't work.
We are able to create knowledge base and test in the qnamaker.ai. Please find the snapshot for the same. Please feel free to retry.
I'm having an issue with automation script feature in Azure and deployment of automations and the type "SecureObject". Hopefully someone can point me in the right direction here.
My scenario is that I've developed a set of features in a resourcegroup in Azure and now I want to use an automation script to deploy the whole thing in to another resourcegroup for acceptance testing by another team.
The resource group consists of various features and generally all is good apart from an Automation which expects a "secureObject" as an input parameter for the "sku" section which I beleive is some kind of unique identifier, however these are normally just strings but not in this particular case.
My question is, what am I supposed to type into that parameter field at the deployment? I find basically no information regarding this anywhere so I'd be gratefull for any help here, a solution or just a hint to point me in the right direction.
If I leave it blank (null) I am getting the error message:
"The value of deployment parameter 'automationAccounts_MyAutomation_sku' is null. Please specify the value or use the parameter reference. See https://aka.ms/arm-deploy/#parameter-file for details. (Code: InvalidDeploymentParameterValue)"
If I just type something (which I didnt actually expect would work anyway) I'll get the error message:
"Unable to parse the value into type 'secureobject'"
To clarify further, here's a screenshot of the actual generated script
Which at deployment expects an input of "secureObject", and here I am stuck...
Same thing goes for using the Visual Studio resource Group template project without any actual point in the right direction.
Any ideas here, anyone?
EDIT: Big thanks to 4c74356b41 for coming up with a solution which works for deployments inside the Azure portal. However when using the same script in Visual Studio 2015 and a Resource Group Template the problem unfortunately persists. Am investigating this issue but if anyone has a good answer on why it doesnt accept secureObjects (even though that is listen in the options for selectable datatypes in the editor), please let me know
Thanks,
JFM
So if you go to the https://resources.azure.com/ you could examine the actual Automation Account and its "schema":
"sku": {
"name": "Free",
"family": null,
"capacity": null
}
So would you need to pass the expected object to that parameter. It accept JSON input, for example.
For your follow up question, I think that's a bug in Visual Studio where ARM template parameter types are currently case-sensitive. Try SecureObject instead of secureObject
I am trying to attach a cloud drive as described here http://msdn.microsoft.com/en-us/library/gg466226.aspx#bk_Storage but I get the error ERROR_AZURE_DRIVE_DEV_PATH_NOT_SET ?
What does this mean? I've tripled checked my config at it seems ok.
I am trying to connect the cloud drive in a Windows Service on a VM Role.
I discovered that the FixMSI.js script from http://msdn.microsoft.com/en-us/library/gg466226.aspx#bk_Install was failing. For some reason $(BuiltOutputPath) was empty. I did it relative to the $(ProjectDir) instead.
It then failed with a different error (and much earlier). CloudDriveException 0x80070103.
Searching for this gave me this article which basically told me to manually edit the driver inf file for the wa miniport. http://msdn.microsoft.com/en-us/library/windowsazure/hh708321.aspx.
Now it attaches ok. The strange thing now is that the device has a warning when the vm starts (but only when hosted in azure), I have to manually go into the vm on azure and update the driver.
try to change BuiltOutputPath to BuildOutputPath. According to Richard, this is an error in the document. Refer to the Community Content section on the document for more information.