-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: "A duplicate file name exists, or the file cannot be found." #9
Comments
Can you send a screenshot ? |
Here you go:
|
Is this a plain nodered ( running as your user ) or running hosted in a process running as a service? Then try enabling headless |
Plain I think. I am launching node-red manually through the command line. Headless: I see the same error. For non-headless, I see Chrome open, and the flows run correctly. It's just that they all end with that error. |
Tested to make sure I wasn't seeing the same error using just TagUI in the command line. No errors there. The larger issue here is that I don't get a success message even though the tagui module is running successfully. So it's difficult to connect the tagui nodes to my larger plan. |
I was able to test this same issue on another machine and didn't receive the error. So it seems like it may be a configuration issue on my side. Do you have any advice on how to track this down? I'm not sure where to start. |
I just updated NR to 2.2.2 and that appears to have solved the problem. I was on 2.1.7 before, having installed NR a few days before 2.2 was released. Oddly, the other machine I ran the same flow with no errors is only on 2.1.4. 🤷♀️ |
Sorry, I spoke too soon. The error has returned. |
So i was on v2.0.0-beta.2 ( and I'm using nodejs version 16.13.0 ) and using windows 11 I also tested with 2.2.1 and 2.2.2 on Debian GNU/Linux 10 (buster) with nodejs version 16.14.0 In all my tests, using my reproduction of your workflow, it runs without an error and returns an empty payload from the completed output node, as expected. (sorry for the big picture below, from my windows box ) I need a way to re-produce this, in order to troubleshoot. Also, if the error is from tagui I need @autonia to help out |
I have node and tagui installed in my user folder. Could that be significant / possibly help reproduce the issue? I have confirmed that running the same tag with tagui on the command line doesn't result in the same error.
Sorry, I believe it must have been 2.1.4. |
To troubleshoot, I just removed my user folder installed version of Node. I reinstalled using the 64-bit Windows Installer on the Node page to the default Program Files directory. Still returns the same error. I also tried removing the tagui install from my user folder, and let the tagui NR module reinstall it. Same error. Is there any kind of log file written to disk by your module at the conclusion of execution? The error results AFTER the completion of the tagui code... |
I see that error comes from tagui, so I'm going to pass this on to @ruthtxh I have no idea how to "attack" this problem to see why it's giving this error ( personally i would properly go for processmon but i hope there is some verbose logging you can enable in tagui for this ? ) |
I am getting this error on all tagui modules, not sure why.
"A duplicate file name exists, or the file cannot be found."
The text was updated successfully, but these errors were encountered: