Trouble configuring networked published application

I'm pretty new to Citrix and while I've been able to publish a bunch of programs there is one that's giving me a lot of problem.

The app is installed on a network server and all clients run a client install for access to the program. So I've ran the client install and setup the published application just like every other one I've done in the past and while the program starts fine on the citrix server it doesn't start through the web interface as a published application. I get my login script and it goes through the citrix negotiation but the program never starts.

Any ideas would be greatly appreciated.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Publish the program using the UNC path to the executable, and use %Systemroot%\system32 or whatever as working directory.
If you're using a mapped drive to start this, that drive has to be mapped in a logon script for the user logging on; mapped drives are user specific, it doesn't help if yiu've mapped this while testing it.
dak11Author Commented:

I've used UNC paths in both the path and working directory.

//dc01/app/csa/csa.exe - target
//dc01/app/csa - working directory

I've also tried using drive letters instead since when users login they get the usual drive mappings like they would when login in at their desktops in the office.
Just in case: you need backslashes, not forward slashes: \\dc01\app\csa\csa.exe
The working directory can *not* be a UNC path (should have said "use %Systemroot%\system32 or whatever other *local* folder you like", I guess).
The users have enough permissions to run this from the network location?
dak11Author Commented:

There shouldn't be an issue with UNC paths in the working directory.

Finally got word back from the software vender. Seems they had no information about it in their knowledgebase but I had to manually add an exclusion for the executables in the registry because my office uses multiple monitors.

Thanks for giving me some ideas though.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.