Creo 4.0 Distributed Batch won't go beyond status "Unsubmitted"

[KS_10705911]

I am trying to batch convert drw to pdf. I have set the pro_lang=English as suggested by some threads. I have created a config.pro with search paths pointing to the parts of which drawings are to be converted to pdf. However, when I run distributed batch it does not runs, instead it gets stucked at "Unsubmitted" stage. The status colors are all yellow. Even if I stop the process it does not stops, rather I have to force close. I have reconfigured the creo to use creo distributed batch. Tried even from ptcdbatch.bat file. But of no use. Please help me as I need to batch convert more than 300 drawings and would take ages to do that.

[KenFarley]

This comes up all the time. Here's a similar discussion with solution. I've used this "trail file method" in the past and it worked very well for me. Not the solution PTC wants but the one I prefer.

community.ptc.com/t5/System-Administration/PTC-Creo-Distributed-Batch/m-p/596053 

[KS_10705911]

@KenFarley  I fear I cant use that exe file. I am using Creo in my organization, which blocks exe download. 

[KenFarley]

The executable file is an assisting program that helps to create the trail file that will be run in Creo. I did not use it - we, too are under strict download policies and can't install things freely.  I just reference the discussion because it's easier for people who might not have as much experience working with files. When I did this type of thing, I did the following:

(1) Start a fresh session of Creo.

(2) Do the steps needed to process exactly one file in the manner I want to.

(3) Close Creo.

(4) Copy the last trail file created by Creo that recorded the steps I need, saving it to something else like "make-dxfs.txt".

(5) Edit the trail file, taking out any extra stuff I don't need, like navigating our network to get to the directory I'm working in, etc.

(6) Figure out what set of commands is needed to do the task for each file I want to process.

(7) Using a sophisticated editor (that does macros), incorporate a list of the files I want to work on by copying the "action block" of commands in the trail file and changing the name of the file they work on to the next one in the list, etc. Thus I end up with block after block of commands, each working on one file.

(8) Once I've got the necessary trail file built, I run it from within Creo.

Some pointers:

(a) You're processing 100s of files, so it is best to include commands in each "processing block" that will erase the current object from memory. Otherwise you run the chance of the process failing due to too many files open.

(b) Before unleashing the trail file, do a test run with a few files to make sure your logic is correct and you're getting exactly what you want.

(c) You might, if possible, want to copy the files to a temporary directory and work from there, to keep all the files safe from any mishaps. Standard file hygeine stuff.

[MartinHanak]

Hi,

please record video showing steps you did when used ptcdbatch.bat

[KS_10705911]

@MartinHanak Unfortunately, I cannot install any app, neither Xbox game bar is enabled by the admin. So, I cannot record the video. 

[MartinHanak]

Hi,

please read following documents

https://www.ptc.com/en/support/article/CS60575

https://www.ptc.com/en/support/article/CS325222

I tested PDF export in Creo 7.0 successfully.

ptcdbatch.bat

I started Creo, opened some drawing and in PTD export dialog I clicked Options button and saved config_pdf.dop file (it contains PDF Export profile).

I started ptcdbatch.bat and defined PDF export batch and start it

IMPORTANT NOTE:

By default ptcdbatch.bat uses following files located in Parametric\bin subdirectory

parametric.bat

parametric.exe

parametric.psf

[KS_10705911]

@MartinHanak , I followed the process as mentioned by you in the above steps, but still the issue persists. 

Check the configuration files:

Also, I have edited the batch file for ptcdbatch.bat as suggested by you (adding indentations accordingly). 

Is there any way how can I check the backend process, where exactly it is getting stuck, so that I can post the issue to this thread. 

[MartinHanak]

Hi,

path to files contain spaces. This can cause problems. Place files to different directory and test export again.

[KS_10705911]

@MartinHanak , I have kept the files on the desktop and tried. Still with no success. I have also renamed the folder to remove spaces. 

[MartinHanak]

Please provide the list of .psf files located in Parametric\bin subdirectory.

[KS_10705911]

Dear @MartinHanak ,

Please find list of .psf files.

[MartinHanak]

---

@KS_10705911 wrote:

Dear @MartinHanak ,

Please find list of .psf files.

---

Hi,

according to the picture, six Creo startup psf files exist in you installation:

PROE_MechFoundation.psf

PROE_Flex3C.psf

PROE_FoundationAdv.psf

PROE_FAPMDO.psf

PROE_FAPAAX.psf

parametric.psf

Each of these files contain following lines
DESC= ... this line contains description text

ENV=CREOPMA_FEATURE_NAME= ... this line contains license specification

On Desktop create shortcut of C:\Proe\PTC\Creo 4.0\M080\Parametric\bin\parametric.exe

Doubleclick the shortcut and send me picture of startup window similar to the following one

Inside this window you can see DESC values,

Please publish ENV=CREOPMA_FEATURE_NAME values for the above mentioned six psf files. (this information is not secrete I think).

Compare your ptcdbatch.bat with my ... see below

    @echo off
set PRO_LANG=english
    set MC=unset
    if "%PROCESSOR%" == "INTEL_64" set MC=ia64_nt
    if "%PROCESSOR%" == "INTEL_486" set MC=i486_nt
    if "%PROCESSOR_ARCHITECTURE%" == "IA64" set MC=ia64_nt
    if "%PROCESSOR_ARCHITECTURE%" == "AMD64" set MC=x86e_win64
    if "%PROCESSOR_ARCHITECTURE%" == "x86" set MC=i486_nt
    REM cygwin sets this on 64bit OS
    if "%PROCESSOR_ARCHITEW6432%" == "AMD64" set MC=x86e_win64
    if not "%MC%" == "unset" goto mc_done
    echo ERROR Cannot detect what machine type you have.
    echo Please make one of the following settings:
    echo.
    echo set PROCESSOR=INTEL_486     - For Windows NT Intel based machines.
    echo.
    echo set PROCESSOR=INTEL_64      - For Windows Intel Itanium based machines.
    echo.
    echo set PROCESSOR_ARCHITECTURE=AMD64 - For Windows AMD 64 based machines.
    echo.
    exit
    :mc_done

    if NOT "%CREO_DIRECTORY%" == "" goto creoset
    set APPDIR=%~dp0..
    set cf=%~dp0..\..
    set PRODIR=%cf%\Common Files
	set PRODIR_UIEDITOR=%cf%

    goto pdirset
    :creoset
    set PRODIR=%CREO_DIRECTORY%\Common Files
    :pdirset

    set PRO_MACHINE_TYPE=%MC%

    set start_cmd=start ""

    set PRO_DIRECTORY=%PRODIR%
    set CREOAPP_DIRECTORY=%APPDIR%
    if NOT "%PTCPATH%" == "" goto ptcpathset

    set path=%PRO_DIRECTORY%\bin;%path%

    set PTCPATH=true
    :ptcpathset

  
      set DCAD_TEMP=C:\ProgramData
      set path=%PRO_DIRECTORY%\%MC%\lib;%path%

      set NMSD_PATH=%PRO_DIRECTORY%\%MC%\nms\nmsd.exe
      
      set PROE_START=%APPDIR%\bin\parametric.bat
      set PROE_STARTUP_EXE=%APPDIR%\bin\parametric.exe
      set PROE_STARTUP_PSF=%APPDIR%\bin\parametric.psf
      
      set MECH_LP=%PRO_DIRECTORY%\mech
      set MECH_HOME=%MECH_LP%\%PRO_MACHINE_TYPE%
      set MECH_STARTUP_EXE=%APPDIR%\..\Simulate\bin\simulate.exe
      set MECH_STARTUP_PSF=%APPDIR%\..\Simulate\bin\simulate.psf
      set PRO_MECH_COMMAND="%MECH_STARTUP_EXE%"

      set DB_CLIENT_DIRECTORY=%PRO_DIRECTORY%
      set DBC_TEXT_RESOURCE=%PRO_DIRECTORY%\text\resource
      set DBC_UITOOLS_RESOURCE=%PRO_DIRECTORY%\proe\uitools\text\resource
      set MOZILLA_FIVE_HOME=%PRO_DIRECTORY%\%MC%\obj\MOZILLA

      if NOT "%PTC_D_LICENSE_FILE%" == "" set PTC_D_LICENSE_FILE=7788@martin;%PTC_D_LICENSE_FILE%
      if "%PTC_D_LICENSE_FILE%" == "" set PTC_D_LICENSE_FILE=7788@martin

      set ZIP_EXEC=%PRO_DIRECTORY%\%mc%\obj\zip.exe
      set PRO_COMM_MSG_EXE=%PRO_DIRECTORY%\%MC%\obj\pro_comm_msg.exe

      if exist "%PRO_DIRECTORY%\ptc_startup.bat" call "%PRO_DIRECTORY%\ptc_startup.bat"
      if exist "%HOMEDRIVE%\%HOMEPATH%\ptc_startup.bat" call "%HOMEDRIVE%\%HOMEPATH%\ptc_startup.bat"
      if exist ".\ptc_startup.bat" call ".\ptc_startup.bat"

      %start_cmd% "%PRO_DIRECTORY%\%MC%\obj\dbatchc.exe" %1 %2 %3 %4 %5 %6 %7 %8 %9
      :ptc_end
      exit /B %ERRORLEVEL%
    

If your ptcdbatch.bat is the same as mine then we have to check ENV=CREOPMA_FEATURE_NAME value in parametric.psf file.

• the only one expected difference is related to 7788@martin

Note: I hope you did not create ptc_startup.bat file mentioned at the end of ptcdbatch.bat.

Note: We have to check whether you are able to start Creo using parametric.psf.

Note: License mentioned in parametric.psf must be free ... you can use ptcstatus.bat to verify it.

[KS_10705911]

ENV=CREOPMA_FEATURE_NAME=PROE_FAPAAX PROE_FAPMDO PROE_FAPMDOG PROE_Flex3C PROE_FlexAdvMDO PROE_FoundationAdv PROE_FoundationAdvG PROE_MechFoundation ()

This is the value

The value of ptcdbatch.bat is exactly same as yours. 

[MartinHanak]

Hi,

1.] OK. The contents of ptcdbatch.bat is correct.

2.] I expected table similar to the following one

3.] Please send me picture of startup window.

On Desktop create shortcut of C:\Proe\PTC\Creo 4.0\M080\Parametric\bin\parametric.exe

Doubleclick the shortcut and send me picture of startup window similar to the following one

[KS_10705911]

Please find below snap

[KS_10705911]

Is there any issue log finder, just to check if there is something wrong with the product ?

[MartinHanak]

---

@KS_10705911 wrote:

Is there any issue log finder, just to check if there is something wrong with the product ?

---

Hi,

I don't know about any log file.

[MartinHanak]

---

@KS_10705911 wrote:

Please find below snap

---

Hi,

I give up. In order to help you, I would have to have access to your computer.

[MartinHanak]

Hi,

see uploaded video. It shows that creo distributed batch works in CR4 M080.

[KS_10705911]

I followed the exact steps in video, but with no success.