Hi Anthony,

Thanks heaps for this information. It makes sense of it all now. I really 
appreciate your time in replying. It had been frustrating not understanding 
why changing pools appeared worked.

Regards
Janette


"Anthony Jones" <Ant@y...> wrote in message 
news:%23XNkWtznGHA.4176@T......
>
> "Janette" <ning@c...> wrote in message
> news:%237CGEbwnGHA.4784@T......
>> Thanks for the assistance. I appear to have fixed the problem. All I did
> was
>> change the site to high isolated in IIS and it worked. If anyone cares to
>> explain to me why this fixed it, that would be great too.
>>
>
> After installing msxml3 did you reboot or perform an iisreset?
> Try iisreset then switching the application protection back to what it 
> was.
>
> The process that was failing to transform had already determined what 
> binary
> component is resolved from the ProgID 'Microsoft.XMLDOM'.  By changing to
> isolated mode you forced IIS to create a separate process for your
> application.  An IISReset will terminate the all the application processes
> and would have fixed the problem.
>
>
>> Regards
>> Janette
>>
>> "Janette" <ning@c...> wrote in message
>> news:eamgWVwnGHA.1808@T......
>> > Hi,
>> >
>> > I installed msxml 3 as suggested, but it am still getting the same
> problem
>> > eg the html looks like
>> >
>> > <xsl:stylesheet version="1.0"
>> > xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
>> > <xsl:output method="xml" omit-xml-declaration="yes" />
>> > <xsl:param name="mode">OPEN</xsl:param>
>> > <xsl:template match="/">
>> > <div id="footer">
>> > Copyright &copy; 2004 &nbsp;&nbsp;ABN 111111
>> > &nbsp;&nbsp;CRICOS Provider No: 1111
>> > <br />
>> > <xsl:apply-templates />
>> > </div></xsl:template>
>> > <xsl:template match="copylink">
>> > <xsl:if test="$mode='OPEN'">
>> > <a>
>> > <xsl:attribute name="href">
>> > <xsl:value-of select="./@href" />
>> > </xsl:attribute>
>> > <xsl:attribute name="class">
>> > <xsl:value-of select="./@class" />
>> > </xsl:attribute>
>> > <xsl:value-of select="." />
>> > </a>&nbsp;|&nbsp;
>> >               </xsl:if>
>> > </xsl:template>
>> > </xsl:stylesheet>
>> >
>> > instead of
>> >
>> > <div id="footer">
>> > Copyright &copy; 2004 &nbsp;&nbsp;ABN 111111
>> > &nbsp;&nbsp;CRICOS Provider No: 1111
>> > <br /><a href="http://websitecontact"
>> > class="dgrey">contact</a>&nbsp;|&nbsp;
>> >               <a href="http://website" class="dgrey">disclaimer &amp;
>> > privacy</a>&nbsp;|&nbsp;
>> >               </div>
>> >
>> > I would appreciate any further help. See my earlier posting for full
> xml,
>> > xsl and vb code that is used to produce the above.
>> >
>> > Regards
>> > Janette
>> >
>> > "Martin Honnen" <mahotrash@y...> wrote in message
>> > news:et$goXpnGHA.1664@T......
>> >>
>> >>
>> >> Janette wrote:
>> >>
>> >>> I have discovered that the server that works has the following dll's
>> >>> that are not on the server that doesn't work
>> >>> msxml2.dll
>> >>> msxml2a.dll
>> >>> msxml2r.dll
>> >>> msxml3.dll
>> >>> msxml3a.dll
>> >>> msxml3r.dll
>> >>
>> >> Forget about msxml2, you only need msxml3, that is MSXML 3 to run XSLT
>> >> transformations. You can download MSXML 3 from
>> >> <http://msdn.microsoft.com/XML/XMLDownloads/default.aspx>
>> >>
>> >> If you want to run XSLT transformations regularly then it might make
>> >> sense to switch to MSXML 4 or MSXML 6 however as they should give you 
>> >> a
>> >> better performance. The ASP code running the transformation needs to 
>> >> be
>> >> changed then to create the proper objects with version specific 
>> >> program
>> >> ids like e.g.
>> >>   Set xmlDocument = CreateObject("Msxml2.DOMDocument.4.0")
>> >> for the DOM document of MSXML 4.
>> >> -- 
>> >>
>> >> Martin Honnen --- MVP XML
>> >> http://JavaScript.FAQTs.com/
>> >
>> >
>>
>>
>
>