Done with Actor Framework before I even started...

[X.]

It's the Actor Framework template...

I tried creating a Queued Message Handler project from the template:

and that worked seamlessly.

Tried again with the Actor Framework template:

and I got the same message as before (though a lot quicker than the first time I tried):

[Kyle97330]

Can you try doing it with a path to the local hard drive (C:\Folder) instead of a network path (\\This-PC\Folder\...)?  Or is that not an option?

[X.]

The "network" path is the way the "Mac side" is accessed from the virtual machine so there isn't any other options unless I migrated all my code within the C: drive, which would make it invisible if I did not run my VM (and wouldn't be backed up by Time Machine, etc).

But you found the root of the problem, as, if I save the project in C:\Users\X\My Documents\Untitled Project\, then things proceed smoothly.

Note again that I had no issue with the Queued Message Handler project residing on this "networked" partition...

[mateh]

Could you map the network path to a drive letter instead?

[Kyle97330]

The Actor Framework project is just a template.  You can use it as a testbed for learning about using it.

However, once you've got a handle on it and want to actually use it for something useful, you can just make an empty project and as soon as you put a VI in the project containing a reference to the Actor and Message classes you can inherit from them as needed.

My guess is that somewhere in the "create template" routine it tries to make a relative path between the LabVIEW directory and the project directory and it can't figure out how to do it properly to a network drive within the character length limit.

[X.]

Bingo!

The Mac side is already mapped to a drive letter, but for whatever reason, I still have access to it AS WELL as network path and this appears to be the cause of the problem. If I use the drive letter version of the path, creation of the project works.

Which raises the question of why that specific template is bothered by the network path while the Queued Message Handler is not (which I just verified)...