The file is there... but "No such file or directory"

Everything was much easier — was not the same architecture... was on the VDS i686, although uname-a showed the x86_64...

While in /usr/local/somedir/sbin refer to the file like this:
# ./filename
Or absolute paths...
\r
Most likely, /usr/local/somedir/sbin not in PATH

Look
\r
ldd /usr/local/somedir/sbin/filename.
\r
It's possible he's just a thread .so libraries are not enough

Or, more likely, that the file starts like this:
\r
#!/usr/bin/someinterpreter
\r
and this someinterpreter no :-) That's ten to one that it is.
\r
> It is possible he just a thread .so libraries are not enough
\r
No, the missing library is another abuse.
\r
> Likely /usr/local/somedir/sbin not in PATH
\r
bash'd say:
\r
\r[~]$ asdasd
bash: asdasd: command not found
\r

Something similar happened with a python script:
\r

$ ls-l -rwxr-xr-x 1 bravebug users 386 Oct 21 00:40 myscript.py* $ ./myscript.py : No such file or directory

The problem was in the type of line — it was a Win (CRLF)

Most likely, it needs some other file.
Run strace /usr/local/somedir/sbin and look at the output.