BUG: using FOR XML AUTO

I have installed this software:
- Windows Server 2003, Enterprise Edition.
- SQL Server 2005, Client tools (Server is in an another machine)
- VirusScan Enterprise 8.0.0
When i execute the next query:
USE AdventureWorks
SELECT * FROM Person.Contact
WHERE ContactID = 1 FOR XML AUTO
VirusScan report me this:
Pathname: C:\Documents and Settings\<user>\Local Settings\Temp\tmp5B.tmp
Detected As: Exploit-ObscuredHtml
Detection Type: Trojan
Application: SqlWb.exe
And SQL Server Management Studio:
An error occurred while executing batch. Error message is: Invalid calling
sequence: file stream must be initialized first.
*****
I apreciate any sugestion !
Thank you.I turn off the antivirus and the query work,
I reported the problem to McAfee...
"Ubeimar Vergara" wrote:

> I have installed this software:
> - Windows Server 2003, Enterprise Edition.
> - SQL Server 2005, Client tools (Server is in an another machine)
> - VirusScan Enterprise 8.0.0
> When i execute the next query:
> USE AdventureWorks
> SELECT * FROM Person.Contact
> WHERE ContactID = 1 FOR XML AUTO
> VirusScan report me this:
> Pathname: C:\Documents and Settings\<user>\Local Settings\Temp\tmp5B.tmp
> Detected As: Exploit-ObscuredHtml
> Detection Type: Trojan
> Application: SqlWb.exe
> And SQL Server Management Studio:
> An error occurred while executing batch. Error message is: Invalid calling
> sequence: file stream must be initialized first.
> *****
> I apreciate any sugestion !
> Thank you.

BUG: using FOR XML AUTO

I have installed this software:
- Windows Server 2003, Enterprise Edition.
- SQL Server 2005, Client tools (Server is in an another machine)
- VirusScan Enterprise 8.0.0
When i execute the next query:
USE AdventureWorks
SELECT * FROM Person.Contact
WHERE ContactID = 1 FOR XML AUTO
VirusScan report me this:
Pathname: C:\Documents and Settings\<user>\Local Settings\Temp\tmp5B.tmp
Detected As: Exploit-ObscuredHtml
Detection Type: Trojan
Application: SqlWb.exe
And SQL Server Management Studio:
An error occurred while executing batch. Error message is: Invalid calling
sequence: file stream must be initialized first.
*****
I apreciate any sugestion !
Thank you.TURN OFF anti-virus software on the server!!
A properly configured SQL Server 'should' not need anti-virus software
installed on the server.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Ubeimar Vergara" <Ubeimar Vergara@.discussions.microsoft.com> wrote in
message news:9CD7E5A0-C308-44C6-A3EA-A0B4CC2D346F@.microsoft.com...
>I have installed this software:
> - Windows Server 2003, Enterprise Edition.
> - SQL Server 2005, Client tools (Server is in an another machine)
> - VirusScan Enterprise 8.0.0
> When i execute the next query:
> USE AdventureWorks
> SELECT * FROM Person.Contact
> WHERE ContactID = 1 FOR XML AUTO
> VirusScan report me this:
> Pathname: C:\Documents and Settings\<user>\Local Settings\Temp\tmp5B.tmp
> Detected As: Exploit-ObscuredHtml
> Detection Type: Trojan
> Application: SqlWb.exe
> And SQL Server Management Studio:
> An error occurred while executing batch. Error message is: Invalid calling
> sequence: file stream must be initialized first.
> *****
> I apreciate any sugestion !
> Thank you.|||"Ubeimar Vergara" <Ubeimar Vergara@.discussions.microsoft.com> wrote in
message news:9CD7E5A0-C308-44C6-A3EA-A0B4CC2D346F@.microsoft.com...
>I have installed this software:
> - Windows Server 2003, Enterprise Edition.
> - SQL Server 2005, Client tools (Server is in an another machine)
> - VirusScan Enterprise 8.0.0
> When i execute the next query:
> USE AdventureWorks
> SELECT * FROM Person.Contact
> WHERE ContactID = 1 FOR XML AUTO
> VirusScan report me this:
> Pathname: C:\Documents and Settings\<user>\Local Settings\Temp\tmp5B.tmp
> Detected As: Exploit-ObscuredHtml
> Detection Type: Trojan
> Application: SqlWb.exe
> And SQL Server Management Studio:
> An error occurred while executing batch. Error message is: Invalid calling
> sequence: file stream must be initialized first.
>
Sounds like a bug in your Antivirus program interfering with the operation
of Management Studio on your client computer.
David|||I turn off the antivirus and the query work,
I reported the problem to McAfee...
"Ubeimar Vergara" wrote:
> I have installed this software:
> - Windows Server 2003, Enterprise Edition.
> - SQL Server 2005, Client tools (Server is in an another machine)
> - VirusScan Enterprise 8.0.0
> When i execute the next query:
> USE AdventureWorks
> SELECT * FROM Person.Contact
> WHERE ContactID = 1 FOR XML AUTO
> VirusScan report me this:
> Pathname: C:\Documents and Settings\<user>\Local Settings\Temp\tmp5B.tmp
> Detected As: Exploit-ObscuredHtml
> Detection Type: Trojan
> Application: SqlWb.exe
> And SQL Server Management Studio:
> An error occurred while executing batch. Error message is: Invalid calling
> sequence: file stream must be initialized first.
> *****
> I apreciate any sugestion !
> Thank you.sql

Bug using FOR XML AUTO with columns with type char(1)

Hello,
Having some problems with generating xml with "FOR XML AUTO". Rows with
a column with a value char(0) seems to terminate the row!
Try to run the following:
SELECT
*
FROM (
SELECT
1 AS orderItemId,
1 AS orderId,
CHAR(0) AS orderItemStatus --CHAR(0) terminates row!
UNION
SELECT
2 AS orderItemId,
1 AS orderId,
CHAR(49) AS orderItemStatus
) AS orderItem
FOR XML AUTO
Generates:
<orderItem orderItemId="1" orderId="1" orderItemStatus="
Should be(?):
<orderItem orderItemId="1" orderId="1" orderItemStatus=" "/><orderItem
orderItemId="2" orderId="1" orderItemStatus="1"/>
Anyone seen this before?
Regards, Nils
CHAR(0) is not a valid XML character. In FOR XML, we do not detect invalid
characters for performance reasons, so you will pass the XML anyway.
Depending on what the client code uses to read the XML, it may see the
CHAR(0) and decide that it is the end of the string (for instance, if the
client code uses the standard C/C++ string types).
So the recommendation is: Do not generate XML containing invalid characters
such as CHAR(0) since they are not supported by compliant XML parsers and
may result in other unforeseen behaviour.
Best regards
Michael
<nilsflemstrom@.gmail.com> wrote in message
news:1125047051.277443.138730@.z14g2000cwz.googlegr oups.com...
> Hello,
> Having some problems with generating xml with "FOR XML AUTO". Rows with
> a column with a value char(0) seems to terminate the row!
> Try to run the following:
> SELECT
> *
> FROM (
> SELECT
> 1 AS orderItemId,
> 1 AS orderId,
> CHAR(0) AS orderItemStatus --CHAR(0) terminates row!
> UNION
> SELECT
> 2 AS orderItemId,
> 1 AS orderId,
> CHAR(49) AS orderItemStatus
> ) AS orderItem
> FOR XML AUTO
> Generates:
> <orderItem orderItemId="1" orderId="1" orderItemStatus="
> Should be(?):
> <orderItem orderItemId="1" orderId="1" orderItemStatus=" "/><orderItem
> orderItemId="2" orderId="1" orderItemStatus="1"/>
> Anyone seen this before?
> Regards, Nils
>

Bug using FOR XML AUTO with columns with type char(1)

Hello,
Having some problems with generating xml with "FOR XML AUTO". Rows with
a column with a value char(0) seems to terminate the row!
Try to run the following:
SELECT
*
FROM (
SELECT
1 AS orderItemId,
1 AS orderId,
CHAR(0) AS orderItemStatus --CHAR(0) terminates row!
UNION
SELECT
2 AS orderItemId,
1 AS orderId,
CHAR(49) AS orderItemStatus
) AS orderItem
FOR XML AUTO
Generates:
<orderItem orderItemId="1" orderId="1" orderItemStatus="
Should be(?):
<orderItem orderItemId="1" orderId="1" orderItemStatus=" "/><orderItem
orderItemId="2" orderId="1" orderItemStatus="1"/>
Anyone seen this before?
Regards, NilsCHAR(0) is not a valid XML character. In FOR XML, we do not detect invalid
characters for performance reasons, so you will pass the XML anyway.
Depending on what the client code uses to read the XML, it may see the
CHAR(0) and decide that it is the end of the string (for instance, if the
client code uses the standard C/C++ string types).
So the recommendation is: Do not generate XML containing invalid characters
such as CHAR(0) since they are not supported by compliant XML parsers and
may result in other unforeseen behaviour.
Best regards
Michael
<nilsflemstrom@.gmail.com> wrote in message
news:1125047051.277443.138730@.z14g2000cwz.googlegroups.com...
> Hello,
> Having some problems with generating xml with "FOR XML AUTO". Rows with
> a column with a value char(0) seems to terminate the row!
> Try to run the following:
> SELECT
> *
> FROM (
> SELECT
> 1 AS orderItemId,
> 1 AS orderId,
> CHAR(0) AS orderItemStatus --CHAR(0) terminates row!
> UNION
> SELECT
> 2 AS orderItemId,
> 1 AS orderId,
> CHAR(49) AS orderItemStatus
> ) AS orderItem
> FOR XML AUTO
> Generates:
> <orderItem orderItemId="1" orderId="1" orderItemStatus="
> Should be(?):
> <orderItem orderItemId="1" orderId="1" orderItemStatus=" "/><orderItem
> orderItemId="2" orderId="1" orderItemStatus="1"/>
> Anyone seen this before?
> Regards, Nils
>

Bug in Copy database routine

I copied some databases from a SQL 2000 server to a SQL 2005 server. All the tables in the databases with auto incrementing identity columns (not for replication) had the identity information removed from the table definition. I used the SQL Management Object method.This is a known issue in SMO that is expected to be fixed in Server Pack 1.

Peter|||So what is the recommended way to copy databases from SQL 2000 to SQL 2005?