Community Tip - Learn all about the Community Ranking System, a fun gamification element of the PTC Community. X
I am getting this message when I try to launch Creo 4 M050.
7788@<server>: (-140) Bad message command
The FlexLM admin guide just has the text: Bad message command.
I am running on a server (Windows 2008) and the software is loaded locally.
The license file is valid because I have a shortcut to a network install of Creo 4 F000 on my server desktop pointing to the same license file and it launches fine.
Only the new install of Creo4 M050 fails.
Hi,
I have never met such error message. Can you upload psf file ?
Martin,
That pointed me in the right direction and I checked the parametric.psf and found some extra characters on the feature line. Removed them and it now starts.
Martin,
I thought that had fixed my problem, but it didn't!
This is the .psf file from a new install of Creo 4M050 ona different machine and I still get the Bad Message Command error.
I did see that if all licenses are used, I get the number of licenses exceeded error. If there is a license, then I get the Bad Command Message.
We use the same license server and file for Creo2, Creo3 and Creo4. I will try to get Creo5 also on it as the license file is for version 36.
// PTC - PSF file: parametric
//
PRODUCT=Creo Parametric
DESC=Creo Parametric (default)
SHIPCODE=M050
CREO_COMMON_FILES=Common Files
//
ENV=MECH_LP=%PRO_DIRECTORY%\mech
ENV=MECH_HOME=%MECH_LP%\%PRO_MACHINE_TYPE%
ENV=PRO_MECH_COMMAND="%CREOAPP_DIRECTORY%\bin\parametric.exe" "%CREOAPP_DIRECTORY%\bin\parametric.psf"
ENV=RPC_TIMEOUT=31536000
ENV=MEDI_HOME=%MECH_HOME%
ENV=PATH+=%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\deflib
ENV=PATH-=%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\lib
ENV=PATH-=%INTRALINK_DIR%\%PRO_MACHINE_TYPE%\illib
ENV=PATH+=%PRO_DIRECTORY%\libs\dfor\lib
ENV=PATH+=%CREOAPP_DIRECTORY%\bin
ENV=NMSD_TIMEOUT=300
ENV=PRO_COMM_MSG_EXE=%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\obj\pro_comm_msg.exe
ENV=PROE_START=%CREOAPP_DIRECTORY%\bin\parametric.exe
ENV=CDRS_DATA=%PRO_DIRECTORY%
ENV=PRO_IMAGE_CONVERTER=%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\obj\convert_image.exe
ENV=PROGUIDE_DIRECTORY=%PRO_DIRECTORY%\uifdoc
ENV=SPG_DIRECTORY=%PRO_DIRECTORY%
ENV=PRO_USRMAIN=%PRO_DIRECTORY%\usrprog\umain\usrmain.c
ENV=PROTABLE_DIRECTORY=%PRO_DIRECTORY%\protable
ENV=MOZILLA_FIVE_HOME=%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\obj\MOZILLA
ENV=PROTAB=%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\obj\protab.exe
ENV=ZIP_EXEC=%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\obj\zip.exe
ENV=CLHOME=%PRO_DIRECTORY%\text\pcldata
ENV=PVIEW_PROEPVIEW_HOME=%PRO_DIRECTORY%\apps\prodview
ENV=CV_ENV_HOME=%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\CV140
ENV=DEBUG_HLP_DLL_PATH=%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\lib\dbghelp.dll
ENV=PTC_D_LICENSE_FILE-=7788@xxxxxpdm2
ENV=CREO_APP=PMA
ENV=CREOPMA_FEATURE_NAME=PROE_Flex3C ()
RUN="%MECH_LP%\install\nt\pro_mech_env.bat"
RUN="%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\nms\nmsd.exe" -noservice -timeout %NMSD_TIMEOUT% &
RUN="%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\obj\xtop.exe"
ENV=DBG_NCPOST_PATH=%CREOAPP_DIRECTORY%\bin
ENV=PRO_ALLOW_EARLY_RETURN=TRUE
// USER - PSF
// Add User specific environment or run applications below here
Ben,
I can't see any problem in your psf file.
I asked Google and get following link:
https://www.ptc.com/en/support/article?n=CS259661
It tells that you probably use FLEXnet version older than 11.14. Creo 4.0 M010+ requires FLEXnet 11.14 !!!
See my response (2018-07-31 03:59 PM) in following discussion:
I have flexnet 11.12, so the update to 11.14 may solve it.
Flexnet versions used to come with the creo distribution. PTC should but them back! Being a separate download and nothing in the download software page to directly get to the Flexnet download is a pain.