This might seem like a daft question, but if we have a 'non DNN' site running on the same server as our DNN site, do we still need to add the folder directory (of the 'non dnn' site) as a portal alias in our DNN site settings?

Reason being, we have just gone live with a dnn site and older (non dnn) website which was previously working (running off a virtual directory) no longer works - it just gives us a server/runtime error.

(further info: the 2 sites are in a different folder locations and use different SQL server database)

thanks,
mark.

thanks,

We only have one application pool (default app pool)
Both sites use Framework 2.0, So dont think we need to create a new application pool?

p.s.
* we've also tried running from 2 different drives  altogehter, but still get server error (on the non-dnn) site, which works ok independently (when DNN site stopped).
* running IIS 6, DNN 5.1.1, windows server 2003

 

Make sure the virtual directory is an application in IIS to eliminate any web.config inheritance.  Run DNN and yourt other site as two separate sites, two IP addresses, two home folders and no folders contained in the heirarchy of the other.

Jeff