Select the search type
  • Site
  • Web
Search
You are here:  Support/Forums
Support

Bring2mind Forums

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 01/20/2007 12:14 PM by  Peter Donker
Error changing Repository Location to external server
 10 Replies
Sort:
You are not authorized to post a reply.
Author Messages
Bubu Kasur
New Member
New Member
Posts:6


--
01/11/2007 7:57 AM

    I have a new Document Exchange 3 Professional installation on DNN 4.3.7 which is running ok with the repository located on the web server. But when I tried to change the Repository Location to an external server using a UNC path of \\servername\sharename or a mapping drive to the external storage and update the new setting, an error occured: "The specified external directory does not exist".

    I then opened IIS Manager and checked that DNN is using DefaultAppPool application pool with identity of Network Service. I changed the identity to a domain account and give the domain account a Full ACL Permission on the external directory.

    I then restarted IIS, and tried again the new setting, but the same error occured. What is the problem? Thanks

    Rob Ralston
    Basic Member
    Basic Member
    Posts:164


    --
    01/16/2007 9:36 PM
    Hello Bubu,

    Are you using W2K3, .NET 2.0 and Medium Trust? When it worked with the repository on the web server, was the repository located in the default DMX location?

    Depending on your answers, I may be able to help you.

    Rob Ralston
    Bubu Kasur
    New Member
    New Member
    Posts:6


    --
    01/18/2007 9:04 AM

    Hi Rob,

    Thank you for your kind response. Yes, I'm using W2K3 and .NET 2.0, and in the DNN web.config, I found this section under system.web:

       

    I haven't tried it under the default DMX location. It's now under c:\DMX.

    Bubu Kasur
    New Member
    New Member
    Posts:6


    --
    01/18/2007 9:08 AM

    Sorry. There is a section in the web.config under system.web that says:  trust level="Medium" originUrl=".*"

    Peter Donker
    Veteran Member
    Veteran Member
    Posts:4536


    --
    01/18/2007 10:08 AM
    What you see there is probably the default DNN setting in the web.config. To determine whether you're under medium trust you'll need to examine the machine.config. If your Windows installation is a default one, it is running under full trust. If it is 'locked down' it could be running under medium trust and that should be visible in the machine.config.
    Peter
    Bubu Kasur
    New Member
    New Member
    Posts:6


    --
    01/18/2007 11:44 AM

    Yes, my Windows installation is a default one, and I don't see any trust level definition in the machine.config, so I believe it's running under full trust.

    Peter Donker
    Veteran Member
    Veteran Member
    Posts:4536


    --
    01/18/2007 12:01 PM
    OK, I'm not sure what Rob was hinting at, but while waiting for his reply you could Google on the following:
    ASPNET application unable to access remote drive
    Something like that. What you're trying to solve is not really a DMX issue, but a general ASPNET and networking issue. You could change network drive for unc path or some similar term.
    Peter
    Rob Ralston
    Basic Member
    Basic Member
    Posts:164


    --
    01/18/2007 1:33 PM

    Hi,

    Sorry, I did not mean to be cryptic in my first response. In .NET 2, you actually have to look in the top level web.config file to see if the server is forced to be locked down globally. Look for web.config here:

    C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG

        (This determines if an individual app can override the trust level set here, in its own web.config)
           
               
                   
                   
                   
                   
                   
               

                <trust level="Medium" originUrl="" />
           

       

    Anyway, it sounds like you are running in Full Trust if your DMX repository is in C:\DMX and not under the DNN folder structure. In which case, I agree with Peter, it is a networking issue. One point though, is you will need to stick with UNC paths, as a mapped drive will not work for the application pool service account.

    If you were to switch to Medium Trust in the future, you would need to take other steps to allow DMX to access files outside of the DNN structure. My personal recommendation is you should be running in Medium Trust, in particular if this web site will be published on the Internet. Although, it does present other challenges.

    Rob

    Rob Ralston
    Basic Member
    Basic Member
    Posts:164


    --
    01/18/2007 1:37 PM

    I'm not sure what happened to a lot of the text I pasted in. Here it is again:
    From global web.config in C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG

    (if true, individual web.config files can set trust level)

    < SYSTEM.WEB>< BR>< SECURITYPOLICY>< BR>< TRUSTLEVEL name="Full" policyFile="internal" />< BR>< TRUSTLEVEL name="High" policyFile="web_hightrust.config" />< BR>< TRUSTLEVEL name="Medium" policyFile="web_mediumtrust.config" />< BR>< TRUSTLEVEL name="Low" policyFile="web_lowtrust.config" />< BR>< TRUSTLEVEL name="Minimal" policyFile="web_minimaltrust.config" />< BR>< /SECURITYPOLICY>< BR>< BR>< TRUST originUrl="" level="Medium" />(global trust level setting)< BR>< /SYSTEM.WEB>


    Rob

    Rob Ralston
    Basic Member
    Basic Member
    Posts:164


    --
    01/18/2007 1:38 PM
    The web.config lines I am pasting in are not showing up. Just look in that file and you will see them.

    Rob.
    Peter Donker
    Veteran Member
    Veteran Member
    Posts:4536


    --
    01/20/2007 12:14 PM
    Hi Rob,
    xml won't transmit to text unfortunately ... you have to add a space between the < and the (opening/closing) tag
    Peter
    You are not authorized to post a reply.