SEO

Having just rebuilt a server with Win 2000 OS (NOT using active
directory) and UDB WSE v8 FP 5, I am now setting up database backup
processing scripts. Reports are created and sent to a network printer
upon completion of various processing stages. The problem is the
reports are failing to print. A bat file which is called from the
Task Center, Command Script tab will successfully execute all the DOS
and DB2 commands in it BUT fail when the report file is sent to the
printer using the DOS 'copy' cmd. The error is 'Logon failure:
Unknown user name or bad password'. If I use the xcopy cmd, I get the
error 'Invalid drive specification'. Next I put the DOS and DB2
commands directly in the Task Center, Command Script. Again, all the
commands ran successfully until the 'copy' to the printer which
reported no error but also did not produce a paper report. If I send
the report file to LPT1 instead of a network printer the report
prints. I think I am facing some security issue, but can't put my
finger on the resolution. The id that runs the scripts is the same id
that is used to log on to the machine and is an Administrator. Under
Computer Management, Local user and groups, this id is listed in both
the Administrators and Users groups. I would be very grateful to
anyone who can offer me a solution to this problem?! Thank you!

Definitely a security problem. Also XCOPY isn't usable for devices.
On the server, grant PRINT rights on the printer to the domain userid under
which the DB2 backup script is running.
If you're using a local userid for backups, change to a domain userid -
local userids have no rights to nonlocal systems.

"R. Clausen" <randi_clausen@ins.state.il.us> wrote in message
news:44515df0.0407091415.2752bb55@posting.google.c om...
> Having just rebuilt a server with Win 2000 OS (NOT using active
> directory) and UDB WSE v8 FP 5, I am now setting up database backup
> processing scripts. Reports are created and sent to a network printer
> upon completion of various processing stages. The problem is the
> reports are failing to print. A bat file which is called from the
> Task Center, Command Script tab will successfully execute all the DOS
> and DB2 commands in it BUT fail when the report file is sent to the
> printer using the DOS 'copy' cmd. The error is 'Logon failure:
> Unknown user name or bad password'. If I use the xcopy cmd, I get the
> error 'Invalid drive specification'. Next I put the DOS and DB2
> commands directly in the Task Center, Command Script. Again, all the
> commands ran successfully until the 'copy' to the printer which
> reported no error but also did not produce a paper report. If I send
> the report file to LPT1 instead of a network printer the report
> prints. I think I am facing some security issue, but can't put my
> finger on the resolution. The id that runs the scripts is the same id
> that is used to log on to the machine and is an Administrator. Under
> Computer Management, Local user and groups, this id is listed in both
> the Administrators and Users groups. I would be very grateful to
> anyone who can offer me a solution to this problem?! Thank you!

randi_clausen@ins.state.il.us (R. Clausen) wrote in message news:<44515df0.0407091415.2752bb55@posting.google. com>...
> Having just rebuilt a server with Win 2000 OS (NOT using active
> directory) and UDB WSE v8 FP 5, I am now setting up database backup
> processing scripts. Reports are created and sent to a network printer
> upon completion of various processing stages. The problem is the
> reports are failing to print. A bat file which is called from the
> Task Center, Command Script tab will successfully execute all the DOS
> and DB2 commands in it BUT fail when the report file is sent to the
> printer using the DOS 'copy' cmd. The error is 'Logon failure:
> Unknown user name or bad password'. If I use the xcopy cmd, I get the
> error 'Invalid drive specification'. Next I put the DOS and DB2
> commands directly in the Task Center, Command Script. Again, all the
> commands ran successfully until the 'copy' to the printer which
> reported no error but also did not produce a paper report. If I send
> the report file to LPT1 instead of a network printer the report
> prints. I think I am facing some security issue, but can't put my
> finger on the resolution. The id that runs the scripts is the same id
> that is used to log on to the machine and is an Administrator. Under
> Computer Management, Local user and groups, this id is listed in both
> the Administrators and Users groups. I would be very grateful to
> anyone who can offer me a solution to this problem?! Thank you!

Thanks Mark for offering a suggestion. Here is more pertinent
information. I failed to mention that the id I am using has full
administrator rights both locally and on the domain. Also, the 'copy'
cmd that fails to produce a hard copy report can be copied directly
out from the script (without the ! and end ; characters) and pasted
onto a DOS command line which prints just fine. Any good ideas?!
Thank you!