We've been working with this over in MSDN. Here's my latest response, in case anyone is still following this thread:

-----------------------------

> So the command should be:

>

>telnet XP_SERVER 1261.

I found from the...

>> The only problem we have encountered with this method is the sorting of textual data according the the appropriate alphabet sort of the language you are reporting in

Confounding the...

We have the data storage question answered by using nvarchar, nchar, etc. I have a whole lot of work ahead of me in figuring out how to do collations that...

Well, after a lot of trial and error, I discovered this worked, using Allen Cui's messages:

1. Bring up Client Network Utility.

2. Go to the Alias tab.

3. Add...

4. Make an Alias...

Is that the SQL Server Central Newsletter Brian was talking about?

You might want the exclusive for a few months, but the truth is that no software mag I know...

Not necessarily print media. I have an article or two I want to publish.

Steve

>> Open the client network utility from your machine, choose alias tab and click add button

Allen, I tried this and it didn't work. From what I'm reading on Books On...

Wouldn't ya know it, I can't connect with Query Analyzer on my own machine now. In fact, I can't connect to anyone's machine with QA anymore.

I used the Client Network...

>> When you say the server is XP, it's XP Pro or a .Net RC server?

Sorry. All machines in this case are XP Pro.

>> I'm going to ask a...

I'm sorry, I don't really understand the suggestion.

Books On Line says: "Most users will never need to use the Client Network utility. To connect to Microsoft® SQL Server™ 2000, users...

We've discovered that we can connect with Explorer to the server before attempting the connect with Query Analyzer, but not after. In other words, the error with the Query Analyzer...

Thanks for the quick response.

>> Can your system ping the server?

I'm getting an error with Explorer that I can't access the server, but another computer can access it fine, and...

Well, I suppose I "got my day". I had originally thought the problem was on the front end, but was convinced otherwise. It was a relief knowing otherwise.

I can't answer...

The problem isn't on the release XML. I ran Profiler trace against the code above. The exception was thrown against:

exec sp_xml_preparedocument @iXmlDoc output, @vcXml

Now I suppose...

>> Which SQL Version is this

SQL Server 2000, SP2

>> Have you rebooted and are able to run it at least once

The error is reproduceable after rebooting.

If I use my XP...