Re: WZZIP returns 1 sometimes

#1

I spoke too soon. The step is still failing.

Seems as though the first time through, the job won't "see" the batch file
until I manually find it using the ellipsis button in the Execute Process
task. After that, the job will run repeatedly from designer mode as long as
I stay in that mode. If I try to schedule the job, the step fails.

Just before the Execute Process task, I am creating the batch file.

"J O Holloway" <jholloway (AT) pinncorp (DOT) com> wrote

Quote:

Figured it out. What I had to do was make sure to have the full paths in
the wzzip line.

"J O Holloway" <jholloway (AT) pinncorp (DOT) com> wrote in message
news:#EpZu2FXDHA.2424 (AT) TK2MSFTNGP12 (DOT) phx.gbl...
SQL Server 2000 rtm on Windows 2000 Server
---
I'm using an Execute Process task to call to a batch file. The batch
file
is a command line call to WZZIP.

Sometimes this step fails, even though the file to be zipped is present
and
the batch file (if run manually) does the job. Also, the Execute
Process
task itself can be manually fired and it works every time as well but
only
if I first use the ellipsis button to "find" the zip batch. It seems to
be
only when the DTS job is fired "from the top" that this error occurs,
and
again, only sometimes.

The return code from WZZIP is 1. I have not been able to find out what
that
means. Does anyone know?

The frustrating thing is that on my machine (W2K Pro) this process is
working perfectly over and over. The error is coming up on the server.

Any help would be much appreciated.

#2

Figured it out. What I had to do was make sure to have the full paths in
the wzzip line.

"J O Holloway" <jholloway (AT) pinncorp (DOT) com> wrote

Quote:

SQL Server 2000 rtm on Windows 2000 Server
---
I'm using an Execute Process task to call to a batch file. The batch file
is a command line call to WZZIP.

Sometimes this step fails, even though the file to be zipped is present
and
the batch file (if run manually) does the job. Also, the Execute Process
task itself can be manually fired and it works every time as well but only
if I first use the ellipsis button to "find" the zip batch. It seems to
be
only when the DTS job is fired "from the top" that this error occurs, and
again, only sometimes.

The return code from WZZIP is 1. I have not been able to find out what
that
means. Does anyone know?

The frustrating thing is that on my machine (W2K Pro) this process is
working perfectly over and over. The error is coming up on the server.

Any help would be much appreciated.

#3

HI,
Ok, make sure include all the paths in batch file, also use UNC path, you
cant use mapped drive.
Example
\\servername\winzip\winzip32.exe "zip options" \\servername\folder\file.zip
\\servername\newFolder
JFB

"J O Holloway" <jholloway (AT) pinncorp (DOT) com> wrote

Quote:

I spoke too soon. The step is still failing.

Seems as though the first time through, the job won't "see" the batch file
until I manually find it using the ellipsis button in the Execute Process
task. After that, the job will run repeatedly from designer mode as long
as
I stay in that mode. If I try to schedule the job, the step fails.

Just before the Execute Process task, I am creating the batch file.

"J O Holloway" <jholloway (AT) pinncorp (DOT) com> wrote in message
news:ufAKtPGXDHA.2212 (AT) TK2MSFTNGP09 (DOT) phx.gbl...
Figured it out. What I had to do was make sure to have the full paths
in
the wzzip line.

"J O Holloway" <jholloway (AT) pinncorp (DOT) com> wrote in message
news:#EpZu2FXDHA.2424 (AT) TK2MSFTNGP12 (DOT) phx.gbl...
SQL Server 2000 rtm on Windows 2000 Server
---
I'm using an Execute Process task to call to a batch file. The batch
file
is a command line call to WZZIP.

Sometimes this step fails, even though the file to be zipped is
present
and
the batch file (if run manually) does the job. Also, the Execute
Process
task itself can be manually fired and it works every time as well but
only
if I first use the ellipsis button to "find" the zip batch. It seems
to
be
only when the DTS job is fired "from the top" that this error occurs,
and
again, only sometimes.

The return code from WZZIP is 1. I have not been able to find out
what
that
means. Does anyone know?

The frustrating thing is that on my machine (W2K Pro) this process is
working perfectly over and over. The error is coming up on the
server.

Any help would be much appreciated.

#4

Thanks for the suggestion.

Unfortunately, it didn't work. I tried running the batch file manually, and
it didn't work at all. Then I opened a command window, and tried using the
commands, only to find that the batch window tells me that UNC isn't
supported.

???

"JFB" <jfb2002 (AT) directvinternet (DOT) com> wrote

Quote:

HI,
Ok, make sure include all the paths in batch file, also use UNC path, you
cant use mapped drive.
Example
\\servername\winzip\winzip32.exe "zip options"
\\servername\folder\file.zip
\\servername\newFolder
JFB

"J O Holloway" <jholloway (AT) pinncorp (DOT) com> wrote in message
news:uFmL2kPXDHA.388 (AT) TK2MSFTNGP10 (DOT) phx.gbl...
I spoke too soon. The step is still failing.

Seems as though the first time through, the job won't "see" the batch
file
until I manually find it using the ellipsis button in the Execute
Process
task. After that, the job will run repeatedly from designer mode as
long
as
I stay in that mode. If I try to schedule the job, the step fails.

Just before the Execute Process task, I am creating the batch file.

"J O Holloway" <jholloway (AT) pinncorp (DOT) com> wrote in message
news:ufAKtPGXDHA.2212 (AT) TK2MSFTNGP09 (DOT) phx.gbl...
Figured it out. What I had to do was make sure to have the full paths
in
the wzzip line.

"J O Holloway" <jholloway (AT) pinncorp (DOT) com> wrote in message
news:#EpZu2FXDHA.2424 (AT) TK2MSFTNGP12 (DOT) phx.gbl...
SQL Server 2000 rtm on Windows 2000 Server
---
I'm using an Execute Process task to call to a batch file. The
batch
file
is a command line call to WZZIP.

Sometimes this step fails, even though the file to be zipped is
present
and
the batch file (if run manually) does the job. Also, the Execute
Process
task itself can be manually fired and it works every time as well
but
only
if I first use the ellipsis button to "find" the zip batch. It
seems
to
be
only when the DTS job is fired "from the top" that this error
occurs,
and
again, only sometimes.

The return code from WZZIP is 1. I have not been able to find out
what
that
means. Does anyone know?

The frustrating thing is that on my machine (W2K Pro) this process
is
working perfectly over and over. The error is coming up on the
server.

Any help would be much appreciated.

#5

Ok, it's working now on my test machine. My error: I had not specified the
full path for the wzzip.

Interestingly enough, although it does work, the commandline window does
still say that it doesn't accept UNC paths, so it then drops into the
Windows directory.

I'll try it out on the production machine and let you know how it goes.
Thanks again.

"JFB" <jfb2002 (AT) directvinternet (DOT) com> wrote

Quote:

HI,
Ok, make sure include all the paths in batch file, also use UNC path, you
cant use mapped drive.
Example
\\servername\winzip\winzip32.exe "zip options"
\\servername\folder\file.zip
\\servername\newFolder
JFB

"J O Holloway" <jholloway (AT) pinncorp (DOT) com> wrote in message
news:uFmL2kPXDHA.388 (AT) TK2MSFTNGP10 (DOT) phx.gbl...
I spoke too soon. The step is still failing.

Seems as though the first time through, the job won't "see" the batch
file
until I manually find it using the ellipsis button in the Execute
Process
task. After that, the job will run repeatedly from designer mode as
long
as
I stay in that mode. If I try to schedule the job, the step fails.

Just before the Execute Process task, I am creating the batch file.

"J O Holloway" <jholloway (AT) pinncorp (DOT) com> wrote in message
news:ufAKtPGXDHA.2212 (AT) TK2MSFTNGP09 (DOT) phx.gbl...
Figured it out. What I had to do was make sure to have the full paths
in
the wzzip line.

"J O Holloway" <jholloway (AT) pinncorp (DOT) com> wrote in message
news:#EpZu2FXDHA.2424 (AT) TK2MSFTNGP12 (DOT) phx.gbl...
SQL Server 2000 rtm on Windows 2000 Server
---
I'm using an Execute Process task to call to a batch file. The
batch
file
is a command line call to WZZIP.

Sometimes this step fails, even though the file to be zipped is
present
and
the batch file (if run manually) does the job. Also, the Execute
Process
task itself can be manually fired and it works every time as well
but
only
if I first use the ellipsis button to "find" the zip batch. It
seems
to
be
only when the DTS job is fired "from the top" that this error
occurs,
and
again, only sometimes.

The return code from WZZIP is 1. I have not been able to find out
what
that
means. Does anyone know?

The frustrating thing is that on my machine (W2K Pro) this process
is
working perfectly over and over. The error is coming up on the
server.

Any help would be much appreciated.

#6

Also you can use winzip command line executables (wzzip.exe and wzunzip.exe)
They work better in dts pkg.
JFB

"J O Holloway" <jholloway (AT) pinncorp (DOT) com> wrote

Quote:

Ok, it's working now on my test machine. My error: I had not specified
the
full path for the wzzip.

Interestingly enough, although it does work, the commandline window does
still say that it doesn't accept UNC paths, so it then drops into the
Windows directory.

I'll try it out on the production machine and let you know how it goes.
Thanks again.

"JFB" <jfb2002 (AT) directvinternet (DOT) com> wrote in message
news:ubooZJQXDHA.2464 (AT) TK2MSFTNGP09 (DOT) phx.gbl...
HI,
Ok, make sure include all the paths in batch file, also use UNC path,
you
cant use mapped drive.
Example
\\servername\winzip\winzip32.exe "zip options"
\\servername\folder\file.zip
\\servername\newFolder
JFB

"J O Holloway" <jholloway (AT) pinncorp (DOT) com> wrote in message
news:uFmL2kPXDHA.388 (AT) TK2MSFTNGP10 (DOT) phx.gbl...
I spoke too soon. The step is still failing.

Seems as though the first time through, the job won't "see" the batch
file
until I manually find it using the ellipsis button in the Execute
Process
task. After that, the job will run repeatedly from designer mode as
long
as
I stay in that mode. If I try to schedule the job, the step fails.

Just before the Execute Process task, I am creating the batch file.

"J O Holloway" <jholloway (AT) pinncorp (DOT) com> wrote in message
news:ufAKtPGXDHA.2212 (AT) TK2MSFTNGP09 (DOT) phx.gbl...
Figured it out. What I had to do was make sure to have the full
paths
in
the wzzip line.

"J O Holloway" <jholloway (AT) pinncorp (DOT) com> wrote in message
news:#EpZu2FXDHA.2424 (AT) TK2MSFTNGP12 (DOT) phx.gbl...
SQL Server 2000 rtm on Windows 2000 Server
---
I'm using an Execute Process task to call to a batch file. The
batch
file
is a command line call to WZZIP.

Sometimes this step fails, even though the file to be zipped is
present
and
the batch file (if run manually) does the job. Also, the Execute
Process
task itself can be manually fired and it works every time as well
but
only
if I first use the ellipsis button to "find" the zip batch. It
seems
to
be
only when the DTS job is fired "from the top" that this error
occurs,
and
again, only sometimes.

The return code from WZZIP is 1. I have not been able to find out
what
that
means. Does anyone know?

The frustrating thing is that on my machine (W2K Pro) this process
is
working perfectly over and over. The error is coming up on the
server.

Any help would be much appreciated.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Re: WZZIP returns 1 sometimes

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts

Re: WZZIP returns 1 sometimes - 08-06-2003 , 10:32 AM

Re: WZZIP returns 1 sometimes - 08-06-2003 , 04:43 PM

Re: WZZIP returns 1 sometimes - 08-07-2003 , 11:38 AM

Re: WZZIP returns 1 sometimes - 08-07-2003 , 12:23 PM

Re: WZZIP returns 1 sometimes - 08-07-2003 , 12:35 PM

Re: WZZIP returns 1 sometimes - 08-07-2003 , 12:44 PM