DSXchange

Hello,

I'm getting a weird behaviour with my Server Jobs.

If I run them, they finish OK, if I schedule them, they abort.

I tried to figure out why and I realized that the parameter (with the source path) appears between double quote when scheduled:

Log of a normal Run:

Project:formateur (SERVER)
Job name:lkpEmployeeBonus
Event #:152
Timestamp:22/01/2010 16:02:00
Event type:Control
User:SERVER\formateur
Message:
Starting Job lkpEmployeeBonus.
FILE_DIR = D:\formation DS\Formateur\Solutions\DS324

Log of a Scheduled Run:

Project:formateur (SERVER)
Job name:lkpEmployeeBonus
Event #:139
Timestamp:22/01/2010 15:39:00
Event type:Control
User:NT AUTHORITY\system
Message:
Starting Job lkpEmployeeBonus.
FILE_DIR = "D:\formation DS\Formateur\Solutions\DS324"

Can anyone explain me why does this happen and how to fix it?

Thank you

Double-quoting pathnames with spaces is standard Windows stuff so shouldn't be an issue. What are the actual aborts that you get?

Definitely something wrong with the parameter value you typed while scheduling. Post the actual error from log.

One more question before I can talk on that.

What is the scheduling tool that you are using, where is that loaded on unix? or Windows?

Regards,

Windows, it would seem from both the parameters being used and the OS type as originally posted. Another assumption would be via Director, so "at" on a Windows server. Please let us know if that's not the case.

Still don't think the quotes are the issue and want to see the abort messages.

chulett wrote: Still don't think the quotes are the issue and want to see the abort messages.

Quotes are definitely not the issue as we have scheduled Sequences that passed pathnames to the jobs on a Windows NT.
OP - please post the exact error you are getting and the possible iterations you had while solving it, as suggested.

Sorry, I couldn't connect to the server during the weekend.

Here's the error:

Project:formateur (SERVER)
Job name:lkpEmployeeBonus
Event #:148
Timestamp:22/01/2010 16:01:44
Event type:Warning
User:SERVER\formateur
Message:
lkpEmployeeBonus..RecentEmployees.EmployeesIn: DSD.SEQOpen Failed to open RecentEmployees.txt in directory "D:\formation DS\Formateur\Solutions\DS324"
STATUS = 22.

Project:formateur (SERVER)
Job name:lkpEmployeeBonus
Event #:149
Timestamp:22/01/2010 16:01:44
Event type:Fatal
User:SERVER\formateur
Message:
lkpEmployeeBonus..GetEmployeeBonus: |lkpEmployeeBonus..RecentEmployees.EmployeesIn: DSD.SEQOpen Failed to open RecentEmployees.txt in directory "D:\formation DS\Formateur\Solutions\DS324"
STATUS = 22.|

I'm scheduling the job directly from Director.

What are the access rights to that file; since when running a scheduled job from Windows I think it uses different userid.

The access right to the file are :

Full Control for System and Administrators
Read and execute for Users.

The user Formateur is an Administrator.

I've already tried to change the user on the Projet properties, but I always get the same error, no matter the user.

Is drive "D" a local disk, or a network mapped drive?

Here is why Arnd is asking that:

http://stanislavs.org/helppc/dos_error_codes.html

ArndW wrote:Is drive "D" a local disk, or a network mapped drive? ...

It's a local disk in the server

That DOS 22 error is more of a "bug" error than a user type error, in my opinion. You may need to take this up with your official support provider if nothing comes of it here.

I just realized where the problem was:

In the path, there was a space and has I had some troubles to run an OS Command also over this folder, I tried to move the files to another folder which has no spaces in its name, and everything works just fine.

Thank you all and I hope this post will be helpful for others.

Hmmm... as noted, that's why the quotes are there - they are needed for a Windows "Long Filename" when it has spaces in it. The workaround of renaming any directories to remove the spaces was pretty obvious and one that I didn't really see the need to mention, thinking that you'd want to work towards a resolution instead and get this working in all cases.

Still think its worth putting in front of your official support provider.