SQL Server Agent - Error 1326

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Greg - 16 Jul 2008 22:03 GMT

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.

Reply to this Message

Ekrem Önsoy - 17 Jul 2008 10:38 GMT

Is the batch file on your local machine where your SQL Server 2005 instance
is installed?

SQL Server service may not have necessary permissions to read\write this
file or to the path where this file is.

Signature

Ekrem Önsoy

> Without having to recreate this processing in SSIS, I have an existing
> Access program
[quoted text clipped - 32 lines]
> available by typing NET HELPMSG 2250. Process Exit Code 2. The step
> failed.

Reply to this Message