Without having to recreate this processing in SSIS, I have an existing
Access program
which I can run by commandline. The batch file runs an AccessDB executing a
specific macro.

I created a job in SQL Server 2005 with a step type "Operating system
(CmdExec)" to execute the batch file. When I run the job, the job hangs
reporting the error 1326.

What do I have to do to resolve this? I have tried a few things...
+++++++++++++++++++++++++++++++++++
Greg

Date 7/1/2008 3:00:00 AM
Log Job History (Get Daily)

Step ID 1
Server XMAN
Job Name Get Daily
Step Name Execute GETDAILY
Duration 00:00:03
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0

Message
Executed as user: XMAN\SYSTEM. System error 1326 has occurred. Logon
failure: unknown user name or bad password.The system cannot find the drive
specified. The system cannot find the drive specified. The system cannot
find the drive specified. The system cannot find the drive specified.The
network connection could not be found. More help is available by typing
NET HELPMSG 2250. Process Exit Code 2. The step failed.

On Jul 16, 11:04 pm, "Greg" <nore... (AT) electrorent (DOT) com> wrote:
Hi Greg,
It seems as the user (XMAN\SYSTEM) that executes the job can't find
the drive.
Maybe you have either a mapped network drive or the user hasn't the
correct permissions...
In fact if you type NET HELPMSG 2250 you get the following:
the network connection cannot be found.

On Jul 16, 11:04 pm, "Greg" <nore... (AT) electrorent (DOT) com> wrote:
Hi Greg,
It seems as the user (XMAN\SYSTEM) that executes the job can't find
the drive.
Maybe you have either a mapped network drive or the user hasn't the
correct permissions...
In fact if you type NET HELPMSG 2250 you get the following:
the network connection cannot be found.

On Jul 16, 11:04 pm, "Greg" <nore... (AT) electrorent (DOT) com> wrote:
Hi Greg,
It seems as the user (XMAN\SYSTEM) that executes the job can't find
the drive.
Maybe you have either a mapped network drive or the user hasn't the
correct permissions...
In fact if you type NET HELPMSG 2250 you get the following:
the network connection cannot be found.

On Jul 16, 11:04 pm, "Greg" <nore... (AT) electrorent (DOT) com> wrote:
Hi Greg,
It seems as the user (XMAN\SYSTEM) that executes the job can't find
the drive.
Maybe you have either a mapped network drive or the user hasn't the
correct permissions...
In fact if you type NET HELPMSG 2250 you get the following:
the network connection cannot be found.

On Jul 16, 11:04 pm, "Greg" <nore... (AT) electrorent (DOT) com> wrote:
Hi Greg,
It seems as the user (XMAN\SYSTEM) that executes the job can't find
the drive.
Maybe you have either a mapped network drive or the user hasn't the
correct permissions...
In fact if you type NET HELPMSG 2250 you get the following:
the network connection cannot be found.

On Jul 16, 11:04 pm, "Greg" <nore... (AT) electrorent (DOT) com> wrote:
Hi Greg,
It seems as the user (XMAN\SYSTEM) that executes the job can't find
the drive.
Maybe you have either a mapped network drive or the user hasn't the
correct permissions...
In fact if you type NET HELPMSG 2250 you get the following:
the network connection cannot be found.

On Jul 16, 11:04 pm, "Greg" <nore... (AT) electrorent (DOT) com> wrote:
Hi Greg,
It seems as the user (XMAN\SYSTEM) that executes the job can't find
the drive.
Maybe you have either a mapped network drive or the user hasn't the
correct permissions...
In fact if you type NET HELPMSG 2250 you get the following:
the network connection cannot be found.

On Jul 16, 11:04 pm, "Greg" <nore... (AT) electrorent (DOT) com> wrote:
Hi Greg,
It seems as the user (XMAN\SYSTEM) that executes the job can't find
the drive.
Maybe you have either a mapped network drive or the user hasn't the
correct permissions...
In fact if you type NET HELPMSG 2250 you get the following:
the network connection cannot be found.