Problem scheduling to a destination 'unmanaged disk'...

[bessebo]

We recently completed an implementation of Crystal Enterprise migrating from Seagate Info 7. I have one job that I am having issues with and this is the only one that actually schedules to the destination 'unmanaged disk'. I am scheduling to a location e:\sunkist\ but when I put in the above destination directory during scheduling and click on Update it changes it to e:/sunkist/. I use a specified filename of sunkistinv.txt. When the program runs it is successful and I get the message as seen below when I click on Success. When I look for the file I cannot find it anywhere on the Crystal Enterprise server but it looks like it ran. Any help here would be appreciated. Do I have to create a share on the Crystal Enterprise server and use that share as the destination directory?

Status: Success
Printer: The instance is not printed.
External Destination: File copy the instance with the filename: "sunkistinv.txt" to the directory: "e:/sunkist/".
Creation Time: 12/15/2003 10:40:29 PM
Start Time: 12/22/2003 10:39:14 PM
End Time: 12/22/2003 10:39:15 PM
Server Used: CRYSTAL1.report


Regards,
Bessebo

 

[Bobbber]

Do you have the unmanaged disk option enabled in the Enterprise admin manager?

Rob

Stay Blue, Bob. x

 

[bessebo]

Yes. And I have put in defaults for the destination directory and file name. If I run it with the system defaults then it runs fine. It's just that I only have one scheduled job that goes to the destination unmanaged disk right now. But if I ever have any more then I want the ability to schedule to different locations. Right now the job appears to run when I choose the E:\Sunkist folder as the destination but the file doesn't get put there and I can't find where it goes (even though it is successful).

Regards,
Bessebo

 

[Bobbber]

What if you set E:\sunkist as the default location?

Does it work ok then? Just testing that Enterprise can send to this location successfully.

Is the 'E' drive Novell or something like that? You may be failing due to the ambiguous statement 'unmanaged'

Rob

Stay Blue, Bob. x

 

[bessebo]

Actually it appears to be working fine. I had originally thought that the file was not getting to the directory but I found out since that our Systems group was moving it onto another location and deleting the file. I apologize for the post but thanks for the effort.

Regards,
Bessebo

 

[Bobbber]

AHH!!!! Those mysterious pixies who move files around uninvited.... I think we have them here too!

Rob

Stay Blue, Bob. x