Results 1 to 6 of 6
  1. #1
    Join Date
    Sep 2003
    Posts
    16

    Unanswered: Error opening datafile: The filename, directory name, or volume labe syntax incorrect

    I receive this error message when I try and run my DTS package:

    "Error opening datafile: The filename, directory name, or volume labe syntax is incorrect."

    I set the file name property of the Text File (Source) to a valid file, but when I run the package and it returns the above error message, it sets the file name property to <not displayable>.

    Does anyone have any experience with such a problem? If so please help!!! Thanks

  2. #2
    Join Date
    Nov 2002
    Location
    Jersey
    Posts
    10,322
    Running scheduled or manual?
    Brett
    8-)

    It's a Great Day for America everybody!

    dbforums Yak CorralRadio 'Rita
    dbForums Member List
    I'm Good Once as I ever was

    The physical order of data in a database has no meaning.

  3. #3
    Join Date
    Sep 2003
    Posts
    16
    it's run manually triggerred from an ASP page.

  4. #4
    Join Date
    Sep 2003
    Posts
    16
    bump

  5. #5
    Join Date
    Nov 2002
    Location
    Jersey
    Posts
    10,322
    Well...

    It's running under the context of the login that calls it...but how are you executing from an asp page?

    From a job or sproc?

    Usually when it runs under the contect of the server the file paths and names have to exists ON the server, not the client.

    Is that your understanding?
    Brett
    8-)

    It's a Great Day for America everybody!

    dbforums Yak CorralRadio 'Rita
    dbForums Member List
    I'm Good Once as I ever was

    The physical order of data in a database has no meaning.

  6. #6
    Join Date
    Sep 2003
    Posts
    16
    It throws the afforementioned error when I call it from ASP or from the Enterprise Manager.

    I'm executing it from asp like:
    Set oPkg = Server.CreateObject("DTS.Package")
    oPkg.Execute

    But the fact that it throws the error from EM on the server is most alarming. I just returned from vacation and I have no idea what could be causing this.

    The file names do exist on the local server, but when the package is run it sets the file name property to "<not displayable>"

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •