300 Portal with other sites running

I have encountered this problem twice now and really need an answer. Is it possible to run the Portal on an IIS server that is currently hosting other production websites? In two cases I have closely followed the instructions for installing Portal and in both cases the installation program took liberties and redirected certain web services that caused the other sites to stop working.

I have installed it correctly on a stand alone server, but not all clients have that luxury.

Is there an assumption by Sage that Portal will be the only site running on an IIS server? If not, does anyone know what I am doing wrong and what the work around might be? I got no help from Sage on this.


Thanks in advance,

Roger

WAC Solution Partners