Hi,
We have moved our site from a Windows Server 2000 and SLQ Server 2000
environment to Windows Server 2003 and SQL 2000 and everything is working
fine except an app that uses XML and OLE.
The script was working fine up to a recent point and the only way we can
resolve the problem is by restarting IIS. The script just streams the xml
many successful times and then out of nowhere just sits there and appears to
be timing out but the process has been sitting on the server for over 4 hour
s
without timing out.
Has there been anything that has changed in Windows Server 2003 that would
cause this?
Thanks,
FredHi Fred,
Can you give a little more detail on what the script is doing? Which XML
interfaces/objects are you using in the script?
Thanks,
Adam Wiener [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"FredPope" <FredPope@.discussions.microsoft.com> wrote in message
news:1C900FAD-0510-4C50-9DCC-BF7A84902BA4@.microsoft.com...
> Hi,
> We have moved our site from a Windows Server 2000 and SLQ Server 2000
> environment to Windows Server 2003 and SQL 2000 and everything is working
> fine except an app that uses XML and OLE.
> The script was working fine up to a recent point and the only way we can
> resolve the problem is by restarting IIS. The script just streams the xml
> many successful times and then out of nowhere just sits there and appears
to
> be timing out but the process has been sitting on the server for over 4
hours
> without timing out.
> Has there been anything that has changed in Windows Server 2003 that would
> cause this?
> Thanks,
> Fred
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment