The good news is that I no longer receive the error 1039--hence the new thread. The bad news is that I receive highly inconsistent behavior. I have a simple test vi that checks the exec.state of an application launcher, reporting whether or not it is broken. I use the following command to do this:
This is successful when I command directly from a terminal about 85% of the time. When I use the exact same command as an Execute Windows batch command Build Step in Jenkins, I get an error -35000 returned about 85% of the time. Calling this directly from the terminal demonstrate VI Server connectivity is not the issue here but I'm at a loss. Any help here would greatly help my future sanity.
One relevant delta occurs to me between the two scenarios presented: whereas manually keying the command into a terminal necessarily requires the operation to be conducted under my user account--which has an LV license associated with it--I have Jenkins configured to run as a service on the system account which does not have a license associated with it. As such, LV never starts when commanded by Jenkins--the -35000 error is indeed accurate but the returned error in this scenario could be made more precise or at the very minimum the Verbose option should indicate that LV never makes it past the registration screen.
Having Jenkins run as a service under an LV licensed user account does indeed allow Jenkins to execute the command successfully.