Bad character in the file name or path; a file by the same name is write protected; you don't have access to the destination folder ... just a few things that come immediately to mind.
I've been dealing with this error for about 3 weeks now. If you open your project file in notepad, you'll probably notice that a '\' is missing from the front of one or more of the filepaths. Put it in and save.
None of the above worked. The problem did seem to be in the project file as other projects compiled just fine.
I exported the project to go and then imported it. It works again.
You know...
I'm starting to suspect something more sinister is going on. I'm starting to see all kinds of file issues like this and am seeing people on the forum with similar issues.
I just worked on a project that couldn't upload a file to a master. it kept skipping over it. it was one of the duet files. I looked at the filepath in NS's upload window and it shows it as being in a folder in C:users/ericm/.... etc. There is no folder/path in that directory visible or otherwise.
This is happening on all three of the machines I use NS on and I've recently upgraded them all to the latest version.
It's also only happening on projects that use DUET modules.
Never had the problem until I went to NS3 recently. I should have resisted longer!
The export/import suggestion was from tech support. Other than that, they dunno.
Yeah, they told me to do the same thing. I don't like that suggestion myself as I tend to keep a whole bunch of files in my projects other than the specific NS projects files. (graphics, literature, etc...) I've found limited success with getting all that stuff back consistently with the Pack-n-go method. Not to mention, the whole pathname thing still seems to get botched up still.
I started another thread on file pathway hell over somewhere else where other's chimed in on what to do or not to do.
I'm betting there's an issue and we're starting to see it bubble to the surface.
Weird. I wonder if there's some weird interaction with another piece of software going on, just because neither I nor our service tech have ever experienced this issue and have been using NS3 since very shortly after release, and at least half my projects contain a duet module.
NS3 has been plagued with workspace path issues since release. I've found ways to deal with most of the ... simply be removing the file from the workspace and re-adding it. But I didn't think this particular issue was related. Now it seems clear to me that it is.
Okay,
This is happening enough even on projects I've 'fixed' using my own method or the 'Pack-N-Go' method. It's happening on multiple computers whether or not I'm on projects on my server or my desktop. I just caught it on a file I've edited myself in text edit messing up the filepaths.
Comments
Where woould it go?
in front of mdlRoomSelectioin_1_00.axs.
like so.
<FilePathName>/mdlRoomSelection_1_00.axs</FilePathName>
I exported the project to go and then imported it. It works again.
I'm starting to suspect something more sinister is going on. I'm starting to see all kinds of file issues like this and am seeing people on the forum with similar issues.
I just worked on a project that couldn't upload a file to a master. it kept skipping over it. it was one of the duet files. I looked at the filepath in NS's upload window and it shows it as being in a folder in C:users/ericm/.... etc. There is no folder/path in that directory visible or otherwise.
This is happening on all three of the machines I use NS on and I've recently upgraded them all to the latest version.
It's also only happening on projects that use DUET modules.
The export/import suggestion was from tech support. Other than that, they dunno.
Yeah, they told me to do the same thing. I don't like that suggestion myself as I tend to keep a whole bunch of files in my projects other than the specific NS projects files. (graphics, literature, etc...) I've found limited success with getting all that stuff back consistently with the Pack-n-go method. Not to mention, the whole pathname thing still seems to get botched up still.
I started another thread on file pathway hell over somewhere else where other's chimed in on what to do or not to do.
I'm betting there's an issue and we're starting to see it bubble to the surface.
What OS are ya'll using out of curiosity?
Okay,
This is happening enough even on projects I've 'fixed' using my own method or the 'Pack-N-Go' method. It's happening on multiple computers whether or not I'm on projects on my server or my desktop. I just caught it on a file I've edited myself in text edit messing up the filepaths.
Engineering???