This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(192, 66%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMN%3C/text%3E%3C/svg%3E)
Hi, I have an Azure Function in .Net that connects to Mongo Atlas to download logs. It is deployed in Azure. The function makes multiple calls to Atlas in a raw. It was working fine until about two weeks ago and then started showing an error like -
tackTrace...: at System.Net.HttpWebRequest.GetResponse() at DownloadMongoAtlasLogs.MongoAtlasLogsDlownloader.RunProcess(Uri uri, CloudStorageAccount account, String containerName, String blobName, ILogger log) in D:\a\1\s\DownloadMongoAtlaslogs\MongoAtlasLogsDlownloader.cs:line 155
2022-11-23T02:27:47Z [Information] CatchMessage...: The system detected an invalid pointer address in attempting to use a pointer argument in a call. [::ffff:54.147.76.65]:443 (cloud.mongodb.com:443)
Could you please share if you encountered that type of error.
Thank you,
Maria
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(294.40000000000003, 87%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMU%3C/text%3E%3C/svg%3E)
Hello @Maria Nikolova - Welcome to the MS Q&A, and thanks for posting here!
One of the possibilities from searching around the error message suggests that this could be due to storage becoming full. Do you have a deletion process through which the older log files from previous downloads get cleaned up?
Hi @Maria Nikolova - I'm just checking in to see if you're still having this issue. If you've already resolved it, please consider posting an answer with the solution as it may benefit others visiting this thread.
Hi Mike,
Thank you for bringing great point about deleting the logs. I will do that. The solution was found in this article: https://github.com/dotnet/runtime/issues/55010
After changing the setting to 64 bit from 32 bit in Azure Portal shown the screenshot below, the error has been resolved.
