2 executables with the same name - different paths.

We are evaluating 2X ApplicationServer for Windows Terminal Services on a Windows 2003 Server.
Single server installation of 2x.
Installation worked great from day one.
Client side install and connection were perfect.

Issue is that we have two installations of an application that we wish to serve/publish via 2x.
One is for live entry...and the other is for training (different SQL records databases).

I used the application server console to publish both resources.
The "target" and "start in" are correct... and are different for each published app .
The client can see those two published app shortcuts.
But BOTH client side shortcuts open the SAME executeable. Every time. Even though the shortcuts should be (and are) pointing to different directories.

I have deleted and re-published on the server side.
I have deleted and refreshed new shortcuts on the client side.
As a test I published Notepad and that worked fine.
I have uninstalled and reinstalled on the server side.

But still...in regards to my two published apps with the same executable name (but on different paths)....either of the two client side shortcuts opens just one of the apps. The same one. Every time.

**The app that opens happens to be the very first app that I ever published.
Im starting to think it is a registry thing.

Any input would be appreciated.

Thanks very much.

mporter88

 

Please contact support for direct help on your issue.
Ensure that on the server the application target does not have any environment variable.
The startin only determines the working directory so is not important to determine which process is started.
What are the paths involved?
Is the system 32 or 64 bit?
On the client side are you using the client to start the application or you created shortcuts on desktop or start menu?
What operating system are you using on the client side?

 

OK...Now I have now been bounced back to this forum because I am not yet a paying customer.
I am evaluating the program by using the free version...I thought that was the point.

Anyway...if anyone has any idea about this I would appreciate a hint.
It is a sort of weird situation that may apply only to our infrastructure (i.e...duplicate executable names)
and except for this ...the program works great.

MP

 

if you answer the questions iposted before I might be able to help you