Skip to main content
K
KN7136560
Participant
January 27, 2009
Question

java.io.FileNotFoundException

  • January 27, 2009
  • 1 reply
  • 2842 views
We seem to have an issue with write permissions. If CFFILE is used from within a standard CF template it writes without any problems. When encapsulated within something such as a custom tag or even used with cfmodule it no longer has permission to write. We are trying to understand what specifically needs to be granted in order for MX to have the permissions it needs for file access using custom tags, components or other methods.

java.io.FileNotFoundException
    This topic has been closed for replies.

    1 reply

    N
    Newsgroup_User
    Inspiring
    January 27, 2009
    KN wrote:
    > We are trying to understand what specifically needs to be granted in order for MX to have the permissions it needs for file access
    > using custom tags, components or other methods.


    Normally ColdFusion would. There is nothing special about using
    <cffile...> inside a custom tag, component or any other reusable
    ColdFusion code.

    What environment, Unix or Windows?

    What user is ColdFusion running under?

    Where do these custom tags and components reside in relation to the
    website root?
    N
    Newsgroup_User
    Inspiring
    January 28, 2009
    KN wrote:
    > I'm having someone check to see if perms can be lifted
    > so CF can access *another drive letter*. The custom tags are located on one
    > drive and the content on the other.
    >

    "Another Drive Letter", that is what I was looking for. Are these drive
    letters local or network?

    By default ColdFusion runs under a 'localSystem' user on Windows
    Servers. This 'localSystem' user, again by default, has access to all
    local drives, but *NO* access to any networked resources, even mapped
    drives.

    To get the latter you have to change the default configuration of
    ColdFusion to run under a user with the desired permissions.

    K
    KN7136560Author
    Participant
    January 28, 2009
    They are local drives which is why it was rather unusual, unless 2003 is limiting processes from accessing other resources by default. Again, if CFFILE is used within a local template it works fine, but as soon as CFMODULE or a custom tag are in play it runs into that error.
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices