Whenever I try to mint an NFT from a Candy Machine V2 using the Metaplex Candy Machine UI I receive the error "Mint Failed". From the second try the minting process works flawlessly. How I could interpret this error and how I could fix it? Below you have a ss from my console and the error message that pops on the screen after clicking the mint button.[[[enter image description here](https://i.stack.imgur.com/xPVR4.jpg)](https://i.stack.imgur.com/e7iFg.jpg)](https://i.stack.imgur.com/DkPBe.jpg)
I reinstalled all the dependencies and I imported again the app to vercel from the original repo.
Related
Application Background: Trying to deploy an automation application where user selects *access file and visualize graphs from the python flask backend calculation.
Locally, Downloaded "Access Driver": https://www.microsoft.com/en-us/download/details.aspx?id=54920 [which ran fine]. But unable to deploy on Azure.
Things that I have tried:
I have tried to run this application using Github CI/CD but with Github actions azure can only give option to run on linux os. which will give me the same error (pyodbc connection)
Build Docker image that could eliminate this error however, when selected 'FROM python:slim-buster' under Dockerfile - It generated docker image with linux which gives the same error.
Also, tried adding windows OS in the Dockerfile using FROM microsoft/nanoserver, still received an error while creating an image.
I am new to all these and think might be making mistakes. Any help will be appreciated.
So After a lot of trial and error, I was able to deploy on windows server on Azure.
What worked:
Deploying application on windows server with ODBC driver (AccessDatabaseEngine.exe). Not the 64bit(AccessDatabaseEngine_X64.exe).
One can deploy using Docker image also but ** FROM microsoft/nanoserver ** was not able to build any image. Instead try with ** FROM mcr.microsoft.com/windows/servercore:ltsc2019 **
I'm new to Docker and have installed docker desktop and signed in. I was given instructions from a colleague to pull an image, as follows:
docker pull petebunting/au-eoed-dev
I tried this on both my windows and Mac machines recently and had no issues. Now the image has been updated, but when I try pulling the latest version of the image I keep getting the error:
unauthorized: authentication required
It begins to pull down the updates but then suddenly stops and produces the above error. This update works fine on my Mac but not on my windows machine. I have tried logging in with both docker desktop and by using docker login but this makes no difference.
I am using windows 10 and powershell
I have searched through similar questions but either my question appears to be different or I do not understand the specifics of the question/answer
So my question is, is there a way to overcome the authentication error I am receiving?
This may be caused by your incorrect host clock: https://github.com/DeepVAC/MLab/issues/60
i'm trying to remote debug my windows tablet store app and when i go to debug it on the remote machine i get this error.
i have done both ways it asks me to fix it in the image but i keep getting the same result. the tablet has the remote manager installed on it with the update version downloaded from Microsoft.
I uninstalled the app installation folders on the remote machine and received a different issue. " Could not generate the root folder for app, Illegal characters in path. "
answer was found here
We have a WCF service that generates an Excel file off of a template and feeds it back to the client in a byte array. For some reason, we are getting an error when we try to do this:
sheet.PageSetup.CenterHeader = sheet.PageSetup.CenterHeader.Replace("[customerName]", customerName).Replace("[dateTime]", date.ToShortDateString());
When it hits this line, we get this error message:
No printers are installed. To install a printer:
In Microsoft Windows 2000, click Start, point to Settings, and then click Printers. Double-click Add Printer.
In Microsoft Windows XP, click Start, and then click Printers and Faxes. Under Printer Tasks, click Add a printer.
Follow the instructions in the wizard.
The service runs under the LocalSystem account. When we first deployed this service, it was to an x64 machine and had the same issue. Our dev environment is x86 so we moved the service to another server that was x86 and it worked fine for a while. It recently stopped working and is now giving us this error message again. I am pretty sure it was becuase of a mass windows update that was done on the app server recently.
Funny thing is, I tried changing the service to "allow interaction with the desktop" and it didn't work, but when our sysadmin did that same thing, it worked for one file generation but is not working now.
There are printers installed on the machine, both on domain accounts and local accounts. I've also tried running the service under a different account, but then I wasn't able to connect to the service due to some SSPI error. We tried using the Network Service account but then the app couldn't see the service at all. We've restarted the service after each change also to no avail.
What I do know about the "PageSetup" part of the sheet object is that it needs to have a printer installed to access it at all, even if you aren't printing. I was unable to figure out a way to trick the machine into thinking the LocalSystem account has a printer installed.
We figured out the problem, I had my config file still pointed at the x64 server :(
As to why it won't work on x64 (to my knowledge) - since office 2003 is x86, it needs an x86 print spooler in order to work correctly. I don't know of any way to get an x86 print spooler on an x64 OS so we just stuck it on the x86 server.
This Windows 2008 SP2
The Error:
Message Queuing: Installation failed
Error: Attempt to install Message Queuing Server failed with error code 0x80070643. Fatal error during installation
The following features were not installed:
Message Queuing Services
Message Queuing Server
Found a msdn blog with the following resolution:
Resolution
To resolve this issue follow the steps listed below:
Go to Control panel and click User Accounts
Select User Accounts and click Turn User Account Control on/ Off
Un-check the check box beside User Account Control
Close the User Account Window, reboot the computer and try to install Microsoft Message Queuing (MSMQ) again
Note: Be sure to turn User Account Controll back on when the issue is resolved
After doing that and rebooting I still getting the same error when trying to installing MSMQ.
Maybe try using the Windows Installer Cleanup Utility? http://download.microsoft.com/download/e/9/d/e9d80355-7ab4-45b8-80e8-983a48d5e1bd/msicuu2.exe
create a key called MSMQ in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft and then go and delete HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSMQ. Worked for me on Windows 10 preview and then I was able to install MSMQ.