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

Community Tip - When posting, your subject should be specific and summarize your question. Here are some additional tips on asking a great question. X

ProWorkspaceRegister return PRO_TK_BAD_INPUT

stefano.berrett
1-Newbie

ProWorkspaceRegister return PRO_TK_BAD_INPUT

Hi everybody,

I'm fighting against a strange problem with ProWorskpaceRegister(). On
my computer is working well, but on the final user's computer, it
returns PRO_TK_BAD_INPUT.

It is a Pro/INTRALINK 3.4 M030 + Wildfire 2.0 M270 asynchronous application.

I have already checked both Pro/ENGINEER and Pro/INTRALINK installation
path using ptcsetup "Other product interoperability" and all is correct.

Any suggestions?

Thank you very much
-Stefano

--
CAD.I.TECH - CAD Integration Technology s.r.l.
via Montevideo, 7/11, I-16129 Genova (Italy)
tel: (+39) 010 3626266
fax: (+39) 010 3626267
www.caditech.it

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.
2 REPLIES 2

Stefano,

In order for that function to work properly you must have the
PDM_LDB_PATH environment variable set.



//Setup environment variables

ProUtilPrint("Setting environment variables\n");

sprintf(szTemp, "PRO_COMM_MSG_EXE=%s", g_szProCommMsgExe);

_putenv(szTemp);

ProUtilPrint(" %-16.16s = %s\n", "PRO_COMM_MSG_EXE",
g_szProCommMsgExe);

sprintf(szTemp, "PDM_LDB_PATH=%s\\%s", g_szInstallDir, ds_szTaskId);

_putenv(szTemp);

ProUtilPrint(" %-16.16s = %s\\%s\n", "PDM_LDB_PATH", g_szInstallDir,
ds_szTaskId);



It must point to the path where the local.ddb file exists.



Patrick Williams | Sr. Application Engineer | Engineering Systems |
Steelcase Inc. | 616.698.4078


Hi everybody

thanks to all.
The Pro/INTRALINK installation path in Pro/ENGINEER configuration was
incorrect: it included the final '\bin'. I could see it in the
proe1.psf file.

It is a a good test to launch pro/ENGINEER from command prompt with
-w<workspace> flag: if this doesn't work, the configuration is not correct.

Thanks again
-Stefano

jan.zwijsen@agfa.com ha scritto:
>
> Don't know if this is causing your problem, but in the past I also
> found that following setting was needed:
> set PRO_COMM_MSG_EXE=<loadpoint pro=" e=">\i486_nt\obj\pro_comm_msg.exe
> Best regards,
> Jan
>
>
> *Stefano Berretta <stefano.berretta@caditech.it>*
>
> 06/08/2008 16:10
>
>
> To
> Jan Zwijsen/AMFGM/AGFA@AGFA
> cc
>
> Subject
> Re: [proecus] - ProWorkspaceRegister return PRO_TK_BAD_INPUT
>
>
>
>
>
>
>
>
>
>
> Thanks a lot,
> but PDM_LDB_PATH was set properly, in fact the procedure checks out
> models correctly.
>
> The ILINK_TK_ACCESS_FEATURE_NAME variable is not set but I see it is
> assigned in the proilinktk3.4.bat.
>
> ...but the procedure doesn't work on the end user's PC
>
> Best regards
> -Stefano
> _
> __jan.zwijsen@agfa.com_ <">mailto:jan.zwijsen@agfa.com> ha scritto:
>
> Check that the environment settings
> PDM_LDB_PATH (should point to the users working directory)
> and
> ILINK_TK_ACCESS_FEATURE_NAME (should be name of license to access
> Intralink (use ptc_status.bat to find correct name of license).
> are set correctly on the final user's computer.
> Kind regards,
> Jan
>
> *"Stefano Berretta" **_<stefano.berretta@caditech.it>_*
> <">mailto:stefano.berretta@caditech.it>
>
> 05/08/2008 14:13
> Please respond to
> "Stefano Berretta" _<stefano.berretta@caditech.it>_
> <">mailto:stefano.berretta@caditech.it>
>
>
> To
> -_ <">mailtoSmiley Tongue->
> cc
>
> Subject
> [proecus] - ProWorkspaceRegister return PRO_TK_BAD_INPUT
>
>
>
>
>
>
>
>
>
>
>
>
> Hi everybody,
>
> I'm fighting against a strange problem with ProWorskpaceRegister(). On
> my computer is working well, but on the final user's computer, it
> returns PRO_TK_BAD_INPUT.
>
> It is a Pro/INTRALINK 3.4 M030 + Wildfire 2.0 M270 asynchronous
> application.
>
> I have already checked both Pro/ENGINEER and Pro/INTRALINK installation
> path using ptcsetup "Other product interoperability" and all is correct.
>
> Any suggestions?
>
> Thank you very much
> -Stefano
>
> --
> CAD.I.TECH - CAD Integration Technology s.r.l.
> via Montevideo, 7/11, I-16129 Genova (Italy)
> tel: (+39) 010 3626266
> fax: (+39) 010 3626267_
> __www.caditech.it_