I had a package update today for Microsoft.Rest.ClientRuntime v2.3.12 to v2.3.13 and my search stopped working. The symptoms are that the call to the client search would just hang.
Looking at the data through Fiddler, I can see the request go out and come back, but my output window is showing Exception thrown: 'System.Net.WebException' in System.dll. I am not sure if this is related.
There is no timeout, no error and the call will continue indefinitely without returning anything. This code has been working beautifully without issue until this package update. I've ensured that this is the only package update and all other packages for Azure Search are at their latest versions.
Below is the call that is hanging.
SearchIndexClient.Documents.Search<T>(SearchBuild.ToString(), searchParams);
I'm trying to find out why this would happen and if there is a better way to find the true error. My assumption is that the package is bad for Microsoft.Rest.ClientRuntime
This is using a ASP.NET (not Core) app. Using my class library in a Console app or with LINQPad seems to allow the project to run just fine.
The hang is the result of a bug in Microsoft.Rest.ClientRuntime. The details are captured in this GitHub issue
Updating to the latest Microsoft.Azure.Search 5.0.3 resolves the issue.
Alternatively, updating to the latest Microsoft.Rest.ClientRuntime.Azure 3.3.16 resolves the issue, which brings in Microsoft.Rest.ClientRuntime 2.3.14 as a dependency.
For clarification, this is using a ASP.NET (not Core) app.
I am Nate from Azure Search. I am unable to reproduce the issue unfortunately. I've tested the ClientRuntime v2.3.13 with Azure Search versions v5.0.0, v5.0.1, and the latest stable v5.0.2 using a sample application available at https://github.com/Azure-Samples/search-dotnet-getting-started/tree/master/DotNetHowTo. Can you reproduce the issue with the sample application? Feel free to reach out to me at nateko AT microsoft.com with more details if you'd like us to take a closer look at the service.
Nate
Related
I'm attempting to set myself up with Azure Data Studio on my new M1 Mac Mini, but the SQL Server database project I'm working on refuses to build. This is the (completely useless) error I'm getting:
stdout: /Users/dumasded/.azuredatastudio/extensions/microsoft.sql-database-projects-0.13.0/BuildDirectory/Microsoft.Data.Tools.Schema.SqlTasks.targets(586,5): error MSB4181: The "SqlBuildTask" task returned false but did not log an error. [/Users/dumasded/Projects/db-project/DBProject.sqlproj]
stdout: 0 Warning(s)
stdout: 1 Error(s)
I can neither find nor remember where I got this idea but I somehow got it into my head that this has something to do with the version of the SDK I'm using - I'm currently using 6.0.100, which as far as I can tell is the only one that's arm64 compatible. Every attempt I've made to download, install and run an earlier version of the SDK on this machine has failed. If that is in fact the problem, I can't even get far enough to find out.
Just to be sure it wasn't something to do with the existing project I was trying to set up, I created a brand new one from scratch and attempted to build that. It failed with the same error. It definitely appears to be a system issue and not a project-specific one.
Is there any hope for me? Am I doomed to return to working on my crummy Lenovo Thinkpad? My breath is bated. Thanks in advance.
EDIT
I've just come across the ingenious MSBuild.Sdk.SqlProj as a potential solution to my issue, however my attempts to use it are still running up against SDK version issues:
error : The current SDK bundles target framework 'netcoreapp6.0' which is not supported by MSBuild.Sdk.SqlProj. Either install a .NET Core SDK that supports 2.1, 3.1 or 5.0, or file an issue at https://github.com/rr-wfm/MSBuild.Sdk.SqlProj/ to add support.
This would seem to confirm my initial suspicion that this is an issue of SDK versions.
EDIT 2
Neglected to mention that I'm using Azure Data Studio with the SQL Database Projects extension, which purports to handle the DACPAC creation seamlessly and across platforms. Though that hasn't been my experience thus far.
I'll be dunked. I knew there had to be a deceptively simple answer to this.
It turns out that my attempts to download, install and run an earlier version of the SDK on my machine weren't failing - they were just going into a different directory. Apparently, installing x64 SDKs on an arm64 machine results in the SDKs being created in a dedicated 'x64' subdirectory of the primary dotnet installation. This is painfully obvious to me now - the reason dotnet --list-sdks showed no trace of the earlier SDKs was that they were being installed for a completely isolated instance of dotnet. All I had to do was point the SQL Database Projects extension to that instance of dotnet and it started working:
I hope my publicly blundering my way through the maze of dotnet SDK architectures manages to help someone else. For my part I'm just so relieved I've finally gotten it to work.
After installing Xamarin.Firebase.iOS.Core, I get this error message when trying to build and deploy to iOS simulator:
Error while loading assemblies: /Users/{mac username}/Library/Caches/Xamarin/mtbs/builds/{app name}/{build id}/bin/iPhoneSimulator/Debug/Firebase.Core.dll
It seems that the assembly
Firebase.Core.dll
is the only thing that is causing issues. This is the only error/ warning message I get back from the compiler. In my references node, all packages seem to be intact and in place.
This problem arose while trying to integrate Firebase into my app and so after creating a separate project and simply downloading the Xamarin.Firebase.iOS.Core package through NuGet (without adding any code), I get the error above. I have looked at a plethora of similar issues but none of which have fixed my problem. I am now wondering if it is an issue with the package itself but it seems that I am the only one lucky enough to encounter this error. If anyone has any clue as to what might be happening please help! I am new to Xamarin and know little about c-sharp build processes, but evidently need to start learning more about said processes, so any information is useful!
Note: I am using Xamarin Forms but this seems like a platform-specific error since it is coming from the remote iMac.
Not sure what happened, but by some miracle or by accidental causes the problem went away. It could be that I uninstalled Firebase for the indefinite number of times that I did, then installed a much older version of the iOS.Auth Package (which installed the appropriate iOS.Core package). Seeing that building went through perfectly, I kept increasing the version of the package until I got the most recent and is surprisingly (and frustratingly) working as nothing happened. To anyone else who runs into this problem, may I suggest purging your packages and temporary Mac files? But I'm still not sure what I did correctly.
I have a functionapp that I made in visual studio 2019. I want to publish this app to an azure function that already exists in Azure. But when I try to publish from VS I get the following error:
I tried to update VS to the latest version and updating the Microsoft.NET.Sdk.Functions packet to version 1.0.35 since the following versions require .NetCore 3 and I use .NetCore 2.1. I also tried to do a Webdeploy but got the same error.
When I changed my .NetCore version to 3.1 and do a WebDeploy I now get this error:
I looked this up and people said to change the WEBSITE_RUN_FROM_PACKAGE value to 0, I tried this and even tried deleting this and it still gave the same error.
I also tried ZIP-deploy and then I get this error:
I also edited the runtimesettings when I changed the version.
My project structure:
In the map IntentFunctions are 6 other azure functions.
Even creating a new app service from VS and then publishing doesn't work.
I saw that most other azure function apps have a json file for each function and I do not have this only a host.json file, might this be the problem?
Anyone know a fix?
Thanks in advance
I do not think your problem is the version of the Function. Framework version would be the problem if the application was deployed successfully but could not start. Your problem is that the ZIP package can not make it to the server, according to the logs.
I had a similar problem before when deploying from VS from home, the problem was slow home internet connection.
Here is the link that helped me:
Publish to Azur fails with 500 internal Server Error
Updated Answer
I generally distrust visual studio because it is doing a lot of stuff under the hoods and caches a lot of data to boost performance. You can instead try to use another mean of publishing as explained by Microsoft here https://learn.microsoft.com/en-us/azure/azure-functions/deployment-zip-push , like a rest call or azure cli.
It seems like Azure Functions default to use .Net Core 3. If you want to change the version, according to this link: https://learn.microsoft.com/en-us/azure/azure-functions/functions-versions , you should be able to change the FUNCTIONS_EXTENSION_VERSION application setting to ~2.
Also you can set the AzureFunctionsVersion in your .csproj like so: <AzureFunctionsVersion> v2 </AzureFunctionsVersion>
We have created a Windows Store app and are running into error code(s) 2003 and 1201 while trying to submit the app to the store. Apparently these errors are not documented in the documentation and there is pretty much absolutely nothing that we can find about these online. Hoping somebody have a knowledge about their resolution and is willing to share it here.
I recommend you to contact the Dev Center support, as they will know what is the cause of this error and will assist you with fixing it. I suspect the problem is some kind of backend issue on their side. You can choose either to create a e-mail based incident on chat with the support live.
You can also post the problem on the dedicated forums (same link as above), to see whether someone else has seen it as well.
It looks like error 1201 is a long-standing issue (bug) with the store.
From the link above, it looks like some people have been able to overcome this issue by upgrading (or just changing) UWP .NET CORE to a different version, or changing or updating their version of Visual Studio.
It looks like you have also posted on this link, and are using UWP Platform 6.2.0. I believe this version is currently considered to be a "Preview" version.
If I was you, I would try rolling back to a previous version (via NuGet Package Manager in Visual Studio). I would suggest you try 6.1.4 (latest stable. as of 5/20/2018), or even earlier 6.0.8
In case it is helpful to others, I am sharing my solution that worked on 2021-11-12.
I encountered error 1201:
I deleted the submission and resubmitted exactly the same package and it worked. It appeared to be a Microsoft Store glitch.
I'm trying to get a PNRP based C# application running but I can barely get started with it.
Initially I had to download the .NET framework version 4 to get the correct references available to me.
When the first call is made I get a "pnrp could not be started" exception.
I tried to explore PNRP using netsh, but the command netsh p2p doesnt seem to be available.
Could anyone tell me if there is some add-on I am missing or if I have made a mistake anywhere.
I am running Windows XP Professional, service pack 3.
Resolved.
http://msdn.itags.org/visual-studio/70534/