You will need to use the "Subst Drive" action in your FinalBuilder project before any actions attempt to read from the drive. The reason for this is that subst drives are configured on a per user basis, they are not shared between user accounts.
it seems to be a little bit more tricky. Until now, the problem occurred only a single time. My project looks like: 1. create directory (randomly named via variable) 2. remove mapping from “T:” ( Condition: CreateObject(“Scripting.FileSystemObject”).DriveExists(“t”) ) 3. map directory on “T:” 4. …
The problem was, that the condition (2) failed and the mapping was not removed. But a mapping for “T:” already exists so (3) failed. I could see the mapping for “T:” using “subst” on the command line. But even my new created test script did not found anything. I could remove the mapping by hand using “subst t: /d”. After that, I mapped the same directory by hand and suddently it detected by the script. I tried my windows service a few more times after that, but it worked normal. Weird.
In your case, is it possible that the mapping was created by a different user to the user who tried to delete it? I think this might explain what was going on...