Error CONVERT: incomplete command

[jgreve]

This is a deploy-only to a remote machine.
The job deploys and runs clean when processed 100% locally (e.g. the QSDesigner & QSServer are both installed on this workstation).
For our exercise, we're trying to make the same job run on a remote QSServer.

QSDesinger running in winxp.
QSServer running in win2003.
note: The server-box also has datastage, profilestage installed on it,
as well as cygwin (which I mention just in case it fights w/mks).
manual ftp conections work fine (e.g. workstation to the remote server).

When we launch the Deploy-only, "run from start to end", we get the following results:
1) script_mkproj runs fine (and creates the project subdirectories on the remote machine).
2) Files ftp up to QSServer fine (at least without errors in the desinger-client).
3) Client comes back with an error message:
Error CONVERT: incomplete command

Looking at the log-file (aka the -2 option), we see this:

Code: Select all

child task(4472):2/20/2007 11:54:14 AM LOG: srv_command( client socket 1912,
   our port 23819 )
child task(4472):2/20/2007 11:54:14 AM LOG: about to srv_do_command
child task(4472):2/20/2007 11:54:14 AM LOG: received: v32 616C70696E653132 CONVERT /WINNCRM/Scripts/STAN.env C:/Ascential/QualityStageServer75/ WINNCRM STAN
child task(4472):2/20/2007 11:54:14 AM LOG: produced errpath of C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\.convert.4472
child task(4472):2/20/2007 11:54:14 AM LOG: Error CONVERT: incomplete command
child task(4472):2/20/2007 11:54:14 AM LOG: Completed srv_command

It can run *some* srv_command things: earlier in the log, this ran fine:

Code: Select all

child task(2896):2/20/2007 11:54:01 AM LOG: received: v32 616C70696E653132 MKPROJ C:/Ascential/QualityStageServer75/  WINNCRM /WINNCRM/Scripts /WINNCRM/Data /WINNCRM/Controls /WINNCRM/Temp /WINNCRM/Logs /WINNCRM/DIC

It looks like the error message is coming from ipe_srv.exe, in particular:

Code: Select all

$ strings ipe_srv.exe | grep -i "incomplete command"
Error EXEC: incomplete command
Error WRAP: incomplete command
[b]Error CONVERT: incomplete command[/b]

This suggests it is not actually launching the script_convert shell script
(or #! /bin/vsh - whatver a "v-shell" is).

At any rate, I'd welcome trouble shooting ideas.

[ray.wurlod]

Did you check the error log (C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\.convert.4472)?

I'm guessing here, but I suspect that the "v" in "vsh" stems from Vality, the name of the company which was acquired by Ascential. Their product was called INTEGRITY, which Ascential renamed QualityStage.

[jgreve]

Did you check the error log (C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\.convert.4472)?

I looked (on the qs-server machine); no such file.
I looked for the msg "produced errpath", because that is the msg in the log output, and I got hits on these files:
ipe_srv.exe
qsserv.exe
Digging into qsserv.exe, the actual string is:
"produced errpath of %s"

Turns out there are also a few "2>&1" characer sequences in qsserv.exe, so I'm guessing they have something inside like this:

Code: Select all

   char cmd[1024];
   char err_log[4096];
   sprintf(err_log, "%s/convert.%d", temp_path, pid );
   sprintf(cmd, "./script_convert ..... > %s 2>&1", err_log );
   system( cmd );
   fopen( err_log ... )

Its been too long since I've done C to hack that up from
memory, but... probably something like the above.

Based on this, I'm pretty sure theyr'e running this as
a catch-all wrapper that is copied back to the QSDesigner client
as the followup-message for display to the user.

I would bet that the content of ".convert.4472" is
our client's error msg: "incomplete command".

I'm guessing here, but I suspect that the "v" in "vsh" stems from Vality, the name of the company which was acquired by Ascential. Their product was called INTEGRITY, which Ascential renamed QualityStage.

That is interesting; thanks!
John G.

[Alexander]

Hi,

When I look to that error messages, it look like your are running a STAN operation? Correct?

Try to deploy only, and look to the files wich have the definition of the operation you are running, and see if is something missing.

It seems the file with the operation definition sent to the remote machine is incomplete, wich cause the abnormal termination when it is creating the definition files.

I don't have acess to QS rigth now, and i don't remember the name of the files that are use to pass by ftp to the server, sorry!!!