Can someone PLEASE help me? I'm running metaframe 1.8 for windows 2k. I've published outlook, explorer and a database from access successfully. When I go to publish a healthcare related application, it logs in and then flashes the following error: The system cannot file the file specified. This working directory is invalid. The path to the app is correct. WHAT is causing this problem? I've mapped a q drive to the server of the app I want to run and I pointed the published app to it. WHAT AM I DOING WRONG?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Published Apps error
- Thread starter clubleo
- Start date
CitrixEngineer
Technical User
Check that you've set the working directory correctly in the shortcut.
Depending on how the healthcare app works, it may do better if you install the client portion on the MetaFrame server and point the app to the other server for data. This may or may not be possible, depending on the app, but is how I solved many of the issues I had with local authority apps.
Hope this helps CitrixEngineer@yahoo.co.uk
Depending on how the healthcare app works, it may do better if you install the client portion on the MetaFrame server and point the app to the other server for data. This may or may not be possible, depending on the app, but is how I solved many of the issues I had with local authority apps.
Hope this helps CitrixEngineer@yahoo.co.uk
I often have noticed that apps that are not 'Terminal Server' proof, place ini files for example in c:\ or in it's own directory. In the ini-file, it changes the subsequent paths after installation or after running the program for the first time. Unfortunately Citrix uses ini mapping so the ini file is also placed in the users homefolder. Often there it contains the old settings. If you then change these internal settings to the correct folders and paths, it should work.
- Thread starter
- #4
The app I'm trying to publish is called 'Healthpro'. The command line and working directory is as follows:
Q:\BIN\PRORUN.EXE
Q:\BIN
When I put this path in, it comes back with an error that says the working directory is invalid. Is it a profile issue? Is it a rights issue? I've looked at a file that has the path/ip address of the machine that holds the app and it's correct. I've also installed the client portion onto the 2000 metaframe server. This is really critical and any help would be greatly appreciated.
Q:\BIN\PRORUN.EXE
Q:\BIN
When I put this path in, it comes back with an error that says the working directory is invalid. Is it a profile issue? Is it a rights issue? I've looked at a file that has the path/ip address of the machine that holds the app and it's correct. I've also installed the client portion onto the 2000 metaframe server. This is really critical and any help would be greatly appreciated.
I have found that publishing applications running on network shares via mapped drives to be very problematic. There are two ways to work around this that I have found. You can publish the application via \\servername\share\bin\prorun.exe. However, some applications do not like that. The better way to fix this is to create a batch file called prorun.bat or prorunbat.bat (or some similar name). Map the q: drive explicitly in the batch and call the program via a start command ("start q:\bin\prorun.exe"
so that the batch file goes away after calling the program. I have used this technique vastly with no problems. Just publish the batch file instead of the application.
so that the batch file goes away after calling the program. I have used this technique vastly with no problems. Just publish the batch file instead of the application.- Thread starter
- #6
- Status
Similar threads
- Locked
- Question
- Locked
- Question