Changes to MSXML is Win 2003 sp1?

Anyone having any problems?

[sullen]

Just wondering if anyone else is having problems with Microsoft's XML parser on Win 2003 sp1 machines.

I suspect that the host uninstalled it when implementing SP1 to be honest, but need to be sure.

[mrMister]

Nope, no problems after the update.

You should specifically reference the version of MSXML that you are using to avoid problems when upgrading.

eg.

Rather than using...

CreateObject("MSXML2.DOMDocument")

You should use...

CreateObject("MSXML2.DOMDocument.4.0")

[sullen]

Yup, that's what I'm using.

Thanks.

[mrMister]

What exactly are you doing with the XML parser? Are you accessing remote machines, or anything like that?

[sullen]

I am accessing remote machines, but it turns out that's not the problem.

The problem is that it seems I can no longer use transct SQL. The page simply fails even if there is no code at all except for the language declaration:
<%@ TRANSACTION=Required Language=VBscript %>

Is that normal for sp1?

[Easy_Coder]

Have you tried removing this at the page level:
@ TRANSACTION=Required

and letting the database manage the transaction

-- pseudo...
use tablename
begin tran

GO
--do some work here...
GO

-- check @@error status
if @@error <> 0
begin
rollback tran
end
else
begin
commit tran
end
GO

[sullen]

Thanks, that may work.

However I still need to know if this is a fundamental change in win2003 sp1 so that I know whether or not I can bill the client for it. Anyone?

[Easy_Coder]

Doesn't @ TRANSACTION=Required actually run in the COM/MTS space?

You may want to look into why that's not working on your new machine as you'll no doubt have other applications that will requires that space to be working.