cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Could not launch the external application '-w:<name of workspace>'. This can happen if external application is not found or incorrect parameters are passed to the application.

sbanerjee
Newbie

Could not launch the external application '-w:<name of workspace>'. This can happen if external application is not found or incorrect parameters are passed to the application.

Hi,

We are using Pro/ENGINEER with Pro/INTRALINK. Pro/ENGINEER cannot be opened through Pro/INTRALINK. whenever 'Launch Pro/ENGINEER' button in Intralink is clicked then getting the below error stating "Could not launch the external application '-w:<name of workspace>'. This can happen if external application is not found or incorrect parameters are passed to the application." I have checked with local administrator login and it's working fine. Issue is happening only with domain user profile. I have added user in Administrators group and provided administrator access but still facing the same error. Any idea? Please help.

Pro-E_with_Intralink_error.PNG


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.
1 REPLY 1

Re: Could not launch the external application '-w:<name of workspace>'. This can happen if external application is not found or incorrect parameters are passed to the application.

This is a suggestion list I found in our database - but I wonder whether it could be a workspace corruption as well:

1) Ensure the "TMP" variable has a value of a path that does not have spaces in it and that it exists.

2)
If Multiple Pro/ENGINEERs are installed on the machine, make sure that
the Pro/ENGINEER that the user is using with Pro/INTRALINK is listed
first in the "PATH" variable.

3) Run "ptcsetup" for Pro/ENGINEER
and make sure the value for the Pro/INTRALINK installation directory is
correct. Keep in mind that the path should be to the loadpoint. Do NOT
go all the way to the "bin" directory.

4) Ensure that the start-in directory for Pro/INTRALINK does not have spaces in it.

5) Run "ptcsetup" for Pro/INTRALINK and make sure the value for the Pro/ENGINEER installation directory is correct. Keep in mind that the path should be to the loadpoint. Do NOT go all the way to the "bin" directory.

6) Ensure that the Pro/ENGINEER loadpoint does not have spaces in the path.

7) Ensure that the Pro/INTRALINK loadpoint does not have spaces in the path.

😎
If using a custom batch file to launch Pro/INTRALINK, try launching it
from the Pro/INTRALINK_loadpoint\bin directory first using the batch
file created by the Pro/INTRALINK setup and see if that works.

9) Echo the "PATH" Variable in a DOS window. Make sure the path variable has the following paths in it:
a) <Pro/ENGINEER-loadpoint>\bin directory
b) <Pro/INTRALINK-client-loadpoint>\bin directory

10)
Execute ptcsetup for Pro/ENGINEER and Pro/INTRALINK and step through
the entire setup. At times running setup fixes this issue since it
recreates the commands.
 In addition, please right click on the file proi.bat from desktop/open with notepad and check: set proe_mc="x86e_win64" 

Please remove the quotes from this line
Example: set proe_mc=x86e_win64
If the quotes are removed, the saved objects are displayed properly in the workspace


Announcements