file not found error

haneyr

after compiling I get the following message:

---

Starting NetLinx Compile - Version[2.5.2.20] [06-18-2013 10:12:36]

---

C:\Users\Auvicomm\Desktop\dental btn daegu cr\AMX Files\Device Files\Biamp Audia Flex Main.axs
ERROR: C:\Users\Auvicomm\Desktop\dental btn daegu cr\AMX Files\Device Files\Biamp Audia Flex Main.tko(0): L20206: File [Biamp Audia Flex, Preset UI.tko] could not be found
C:\Users\Auvicomm\Desktop\dental btn daegu cr\AMX Files\Device Files\Biamp Audia Flex Main.axs - 1 error(s), 0 warning(s)
NetLinx Compile Complete [06-18-2013 10:12:36]


I can find it in the directory location so am not sure how to fix the problem.

ericmedley

Just remove it from the project and re-ad it.

AMXJeff

haneyr wrote: »

after compiling I get the following message:

---

Starting NetLinx Compile - Version[2.5.2.20] [06-18-2013 10:12:36]

---

C:\Users\Auvicomm\Desktop\dental btn daegu cr\AMX Files\Device Files\Biamp Audia Flex Main.axs
ERROR: C:\Users\Auvicomm\Desktop\dental btn daegu cr\AMX Files\Device Files\Biamp Audia Flex Main.tko(0): L20206: File [Biamp Audia Flex, Preset UI.tko] could not be found
C:\Users\Auvicomm\Desktop\dental btn daegu cr\AMX Files\Device Files\Biamp Audia Flex Main.axs - 1 error(s), 0 warning(s)
NetLinx Compile Complete [06-18-2013 10:12:36]


I can find it in the directory location so am not sure how to fix the problem.

You have to do a build system, sounds like the NetLinx UI modules need compiling.

haneyr

ericmedley wrote: »

Just remove it from the project and re-ad it.

thanks. done that didn't fix it.

haneyr

AMXJeff wrote: »

You have to do a build system, sounds like the NetLinx UI modules need compiling.

thanks. done that didn't fix it.

jdonachiue@shaw.ca

Does this file exist?
"C:\Users\Auvicomm\Desktop\dental btn daegu cr\AMX Files\Device Files\Biamp Audia Flex, Preset UI.axs"

Do a search for:
"C:\Users\Auvicomm\Desktop\dental btn daegu cr\AMX Files\Device Files\Biamp Audia Flex, Preset UI.*"

RichardHamilton

Myself, I avoid using the desktop and/or 'my documents' for any development. It always seems to create some problem. And you may just be experiencing another one of them.

For me, the hard and fast rule is to have a sub-folder on a data volume that's for work and compiling.

The folder naming should be simple (ie 8.3) and never use spaces. I'm probably sounding like a DOS dinosaur, but historically, sticking to 8.3 naming and no spaces has also proven to avoid hyperlinking and compiling errors.

I know what I'm saying may not help you now, but maybe moving your project to a more reliable folder may help you.

(edit: I just saw someone place a comma in the name as well. Do not complicate file/foler naming with punctuation, as well as sticking to 8.3).

John Gonzales

I've had that issue in the past and I think it was related to being too many subdirectories deep or it was the way a folder was named. Try saving it near root and with simple foldernames like Richard said... something like c:\AMX\ and see if that helps. You can always move it later if it works. If not, maybe check simple things like NTFS security, etc?

-John

pdabrowski

FileMon and AccessEmum from Sysinternals can help with this sort of issue.

http://technet.microsoft.com/en-us/sysinternals/default

AccessEnum lets you scan a directory examine the NT access rights and if run from your profile should show if you can access the required files.

FileMon should be started before compiling and then after the compile fails, stop it and run filters across the output to see where the issue lies.

There is a lot of other utilities in the sysinternals suite that are great diagnosis tools and the nice thing is that they are all free.


I agree with the other posters however that the file location (in mydocs) or punctuation (comma) might be a very likely cause in this instance.

rfletcher

RichardHamilton wrote: »

Myself, I avoid using the desktop and/or 'my documents' for any development. It always seems to create some problem. And you may just be experiencing another one of them.

For me, the hard and fast rule is to have a sub-folder on a data volume that's for work and compiling.

The folder naming should be simple (ie 8.3) and never use spaces. I'm probably sounding like a DOS dinosaur, but historically, sticking to 8.3 naming and no spaces has also proven to avoid hyperlinking and compiling errors.

I know what I'm saying may not help you now, but maybe moving your project to a more reliable folder may help you.

(edit: I just saw someone place a comma in the name as well. Do not complicate file/foler naming with punctuation, as well as sticking to 8.3).

I can say with reasonable certainty that path length is not the issue at least, as I have workspaces with paths that long or longer. Back when I first started programming I vaguely recall managing to choke NetLinx on an excessively long path once, but I haven't had that problem for a long time so I assume they must have upped the supported length at some point.

Long file names have been in Windows for almost 20 years at this point and My Documents has been the appropriate place to store user files in Windows for 17 years or so. Any programs or tools that don't properly deal with them or the long paths they make inevitable deserve to be publicly shamed at this point imo. (let me take this opportunity to shame Brand C's VTProE for breaking in really weird ways if your file's path is too long) Nearly two decades should be enough time to adapt.

ericmedley

Another file oddity that has resulted in file not found errots for me is when I bring in already prepared code that has an include to yet another file. If the 'yet another file' happens to be present in the root folder of he new project the project compiles even though I have actually bothered to import 'yet another file' into the workspace.

Now, copy this project to a new project and it breaks down. I then have to reassemble the whole thing in the project to gt rid of the error.