sql rowcount: error

Showing posts with label error. Show all posts

Thursday, March 22, 2012

_WA Statistics Error

Hello,
We have had a problem with a table recently where a load had stopped half
with through with an index problem.
After a bit of delving the problem seems to be causes by the system created
Statisitcs for a particial index or at least thats where the error message i
s
pointing to.
The database is set to auto update the statistics and we use this table to
do a lot of loads, truncates and deletes.
My question is this, has anyone seen a problem created by the System created
statisitics and what was the fix.
TIA
PatriciaParticia
What's version are you using?
Havu you ran DBCC SHOW_STATISTICS?
Also take a look at sp_createstats system stored procedure
"Patricia" <Patricia@.discussions.microsoft.com> wrote in message
news:2E80BF08-3146-4749-8142-CC7A7BC1F56D@.microsoft.com...
> Hello,
> We have had a problem with a table recently where a load had stopped half
> with through with an index problem.
> After a bit of delving the problem seems to be causes by the system
> created
> Statisitcs for a particial index or at least thats where the error message
> is
> pointing to.
> The database is set to auto update the statistics and we use this table to
> do a lot of loads, truncates and deletes.
> My question is this, has anyone seen a problem created by the System
> created
> statisitics and what was the fix.
> TIA
> Patricia

_WA Statistics Error

Hello,
We have had a problem with a table recently where a load had stopped half
with through with an index problem.
After a bit of delving the problem seems to be causes by the system created
Statisitcs for a particial index or at least thats where the error message is
pointing to.
The database is set to auto update the statistics and we use this table to
do a lot of loads, truncates and deletes.
My question is this, has anyone seen a problem created by the System created
statisitics and what was the fix.
TIA
PatriciaParticia
What's version are you using?
Havu you ran DBCC SHOW_STATISTICS?
Also take a look at sp_createstats system stored procedure
"Patricia" <Patricia@.discussions.microsoft.com> wrote in message
news:2E80BF08-3146-4749-8142-CC7A7BC1F56D@.microsoft.com...
> Hello,
> We have had a problem with a table recently where a load had stopped half
> with through with an index problem.
> After a bit of delving the problem seems to be causes by the system
> created
> Statisitcs for a particial index or at least thats where the error message
> is
> pointing to.
> The database is set to auto update the statistics and we use this table to
> do a lot of loads, truncates and deletes.
> My question is this, has anyone seen a problem created by the System
> created
> statisitics and what was the fix.
> TIA
> Patricia

_hypmv error

I just tried to update a column type from varchar(32) to varchar(64) in a
table,but got some dependency error like:
The object '_hypmv_0' is dependent on column 'EMAILREFERENCE'.
The object '_hypmv_0_9625' is dependent on column 'EMAILREFERENCE'.
The object '_hypmv_0_7898' is dependent on column 'EMAILREFERENCE'.
The object '_hypmv_0_6539' is dependent on column 'EMAILREFERENCE'.
But,in the dependency listing for the table I cant view any of the above,but
I have
got admin access.What are these dependecies for?any pointer will be greatly
appreciated.
A wild guess is that someone has been running Index Tuning izard which has created "Hypothetical
Materialized Views" (called Indexed Views), and these from some reason haven't been dropped. I'd
check if these are views and if your applications aren't using these, consider dropping them, using
DROP VIEW command.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"c_ani" <cani@.discussions.microsoft.com> wrote in message
news:53B89EB6-C82A-49B2-96C2-84A98CB02FC0@.microsoft.com...
>I just tried to update a column type from varchar(32) to varchar(64) in a
> table,but got some dependency error like:
> The object '_hypmv_0' is dependent on column 'EMAILREFERENCE'.
> The object '_hypmv_0_9625' is dependent on column 'EMAILREFERENCE'.
> The object '_hypmv_0_7898' is dependent on column 'EMAILREFERENCE'.
> The object '_hypmv_0_6539' is dependent on column 'EMAILREFERENCE'.
> But,in the dependency listing for the table I cant view any of the above,but
> I have
> got admin access.What are these dependecies for?any pointer will be greatly
> appreciated.
sql

_hypmv error

I just tried to update a column type from varchar(32) to varchar(64) in a
table,but got some dependency error like:
The object '_hypmv_0' is dependent on column 'EMAILREFERENCE'.
The object '_hypmv_0_9625' is dependent on column 'EMAILREFERENCE'.
The object '_hypmv_0_7898' is dependent on column 'EMAILREFERENCE'.
The object '_hypmv_0_6539' is dependent on column 'EMAILREFERENCE'.
But,in the dependency listing for the table I cant view any of the above,but
I have
got admin access.What are these dependecies for?any pointer will be greatly
appreciated.A wild guess is that someone has been running Index Tuning izard which has created "Hypothetical
Materialized Views" (called Indexed Views), and these from some reason haven't been dropped. I'd
check if these are views and if your applications aren't using these, consider dropping them, using
DROP VIEW command.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"c_ani" <cani@.discussions.microsoft.com> wrote in message
news:53B89EB6-C82A-49B2-96C2-84A98CB02FC0@.microsoft.com...
>I just tried to update a column type from varchar(32) to varchar(64) in a
> table,but got some dependency error like:
> The object '_hypmv_0' is dependent on column 'EMAILREFERENCE'.
> The object '_hypmv_0_9625' is dependent on column 'EMAILREFERENCE'.
> The object '_hypmv_0_7898' is dependent on column 'EMAILREFERENCE'.
> The object '_hypmv_0_6539' is dependent on column 'EMAILREFERENCE'.
> But,in the dependency listing for the table I cant view any of the above,but
> I have
> got admin access.What are these dependecies for?any pointer will be greatly
> appreciated.

\minint\system32\biosinfo.inf error code 263

I have an HP with Windows XP. I've been gone for a few days and when i came home i tried to start up my PC, but I got:

A disk read error occurred

press ctrl+alt+del to restart

when i do i tap the f10 for system restore, and get the message in the subject line.

When i tap that it send me back to the a disk read error....

I'm not computer literate, but could follow directions or turn it over to my son who is an IT guy.

help, Deuby

Hi,

First of all if you could refer BIOS setting , are you able to see the HDD ? Reset BIOS to default. Check for the Data Cable also.

Hemantgiri S. Goswami

|||

How is this related to SQL Server Security?

Will try to move to a different forum.

Laurentiu

|||

Try the following in order, one at a time - no multi tasking. This was taken from another Forum and has worked at different points on different machines with the same error.

Safest and easiest to try (in order of ease)
-:
*(1) Reset BIOS with "safe" defaults
(2) Yank BIOS battery for about 10 minutes
(3) Disable HD S.M.A.R.T. setting in BIOS
*(4) Disable bus mastering in BIOS
*(5) Disable Ultra DMA (UDMA) moder in BIOS (or at least change the UDMA mode)
(6) Set correct memory settings in BIOS
(7) Test memory to see if it is faulty (MemTest86 from memtest.org is free)
(8) Set HD jumper(s) to Master rather than Cable Select (or even Master w/Slave Present)
(9) Replace HD cable
*(10) Update BIOS
(11) Use FIXBOOT utility on Win XP recovery
*(12) Use chkdsk /r /p
(13) Virus scan (good luck, because that probably isn't the problem)

Medium difficulty and some danger of Data Loss

*(14) Defragment (requires use of second computer or boot to defrag program on CD)
*(15) Use Partition Table Doctor from the Ultimate Boot CD (search on Google)
(16) Use FIXMBR utility on Win XP recovery (DO NOT use if utility indicates non-standard partition if you want to preserve your data!)
(17) Change drive ID from 1 to 0 (if it is 1) or vice versa (personally I don't think this is a good idea); if problem with drive ID, reset ID by powering system on while HD cable is plugged but power unplugged
(18) Resize NTFS Clusters to 4K using partition manager
*(19) Change NTFS to FAT32 using partition manager (and optionally change back to NTFS--although this may cause the problem to recur)

Time-consuming and may not work; definite data loss:

(20) Resize partition below 137 Gb
(21) Perform low-level format on HD (using manufacturer's tools)

Good Luck.

\minint\system32\biosinfo.inf error code 263

I have an HP with Windows XP. I've been gone for a few days and when i came home i tried to start up my PC, but I got:

A disk read error occurred

press ctrl+alt+del to restart

when i do i tap the f10 for system restore, and get the message in the subject line.

When i tap that it send me back to the a disk read error....

I'm not computer literate, but could follow directions or turn it over to my son who is an IT guy.

help, Deuby

Hi,

First of all if you could refer BIOS setting , are you able to see the HDD ? Reset BIOS to default. Check for the Data Cable also.

Hemantgiri S. Goswami

|||

How is this related to SQL Server Security?

Will try to move to a different forum.

Laurentiu

|||

Try the following in order, one at a time - no multi tasking. This was taken from another Forum and has worked at different points on different machines with the same error.

Medium difficulty and some danger of Data Loss

Time-consuming and may not work; definite data loss:

(20) Resize partition below 137 Gb
(21) Perform low-level format on HD (using manufacturer's tools)

Good Luck.

\\.\Tape0 is not a vaild Microsoft Tape format backup set

hi all
I am using Sql server 2000 with sp3 on Win 2003. Recently all of my nightly
sql server backups have started failing. Here is the error message I get with
it
The file on device '\\.\Tape0' is not a vaild Microsoft Tape format backup
set. Backup Database is terminating abnormally.
I am using HP dds-4 cartridges (40 GB)
How can I fix that?
Also how do I format my tapes?
regards,
AndreHi
Have you tried dropping the backup device and re-creating it? Will the NT
Backup recognise this tape device?
John
"Andre Gibson" wrote:
> hi all
> I am using Sql server 2000 with sp3 on Win 2003. Recently all of my nightly
> sql server backups have started failing. Here is the error message I get with
> it
> The file on device '\\.\Tape0' is not a vaild Microsoft Tape format backup
> set. Backup Database is terminating abnormally.
> I am using HP dds-4 cartridges (40 GB)
> How can I fix that?
> Also how do I format my tapes?
> regards,
> Andre|||No NT Backup doesn't recognize the tape. How do I drop and re-create the
device?
"John Bell" wrote:
> Hi
> Have you tried dropping the backup device and re-creating it? Will the NT
> Backup recognise this tape device?
> John
> "Andre Gibson" wrote:
> > hi all
> >
> > I am using Sql server 2000 with sp3 on Win 2003. Recently all of my nightly
> > sql server backups have started failing. Here is the error message I get with
> > it
> >
> > The file on device '\\.\Tape0' is not a vaild Microsoft Tape format backup
> > set. Backup Database is terminating abnormally.
> >
> > I am using HP dds-4 cartridges (40 GB)
> >
> > How can I fix that?
> > Also how do I format my tapes?
> >
> > regards,
> >
> > Andre|||Hi Andre
If the NT backup does not recognise the tape, then it may not be SQL Server
that is the problem. Have you tried different tapes or re-installing the tape
drive?
John
"Andre Gibson" wrote:
> No NT Backup doesn't recognize the tape. How do I drop and re-create the
> device?
> "John Bell" wrote:
> > Hi
> >
> > Have you tried dropping the backup device and re-creating it? Will the NT
> > Backup recognise this tape device?
> >
> > John
> >
> > "Andre Gibson" wrote:
> >
> > > hi all
> > >
> > > I am using Sql server 2000 with sp3 on Win 2003. Recently all of my nightly
> > > sql server backups have started failing. Here is the error message I get with
> > > it
> > >
> > > The file on device '\\.\Tape0' is not a vaild Microsoft Tape format backup
> > > set. Backup Database is terminating abnormally.
> > >
> > > I am using HP dds-4 cartridges (40 GB)
> > >
> > > How can I fix that?
> > > Also how do I format my tapes?
> > >
> > > regards,
> > >
> > > Andre|||John,
You were correct. It was my tapes.
Thanks so much for your assistance.
regards,
Andre
"John Bell" wrote:
> Hi Andre
> If the NT backup does not recognise the tape, then it may not be SQL Server
> that is the problem. Have you tried different tapes or re-installing the tape
> drive?
> John
> "Andre Gibson" wrote:
> > No NT Backup doesn't recognize the tape. How do I drop and re-create the
> > device?
> >
> > "John Bell" wrote:
> >
> > > Hi
> > >
> > > Have you tried dropping the backup device and re-creating it? Will the NT
> > > Backup recognise this tape device?
> > >
> > > John
> > >
> > > "Andre Gibson" wrote:
> > >
> > > > hi all
> > > >
> > > > I am using Sql server 2000 with sp3 on Win 2003. Recently all of my nightly
> > > > sql server backups have started failing. Here is the error message I get with
> > > > it
> > > >
> > > > The file on device '\\.\Tape0' is not a vaild Microsoft Tape format backup
> > > > set. Backup Database is terminating abnormally.
> > > >
> > > > I am using HP dds-4 cartridges (40 GB)
> > > >
> > > > How can I fix that?
> > > > Also how do I format my tapes?
> > > >
> > > > regards,
> > > >
> > > > Andre

Tuesday, March 20, 2012

\\.\Tape0 is not a vaild Microsoft Tape format backup set

[XML Task] Error: An error occurred with the following error message: There are multiple root el

I'm trying to use an XML Task to do a simple XSLT operation, but it fails with this error message:

[XML Task] Error: An error occurred with the following error message: "There are multiple root elements. Line 5, position 2.".

The source XML file validates fine and I've successfully used it as the XML Source in a data flow task to load some SQL Server tables. It has very few line breaks, so the first 5 lines are pretty long: almost 4000 characters, including 34 start-tags, 19 end-tags, and 2 empty element tags. Here's the very beginning of it:

<?xml version="1.0" encoding="UTF-8"?>
<ESDU releaselevel="2006-02" createdate="26 May 2006"><package id="1" title="_standard" shorttitle="_standard" filename="pk_stan" supplementdate="01/05/2005" supplementlevel="1"><abstract><![CDATA[This package contains the standard ESDU Series.]]></abstract>

There is only 1 ESDU root element and only 1 package element.

Of course, the XSLT stylesheet is also an XML document in its own right. I specify it directly in the XML Task:

<?xml version="1.0" encoding="UTF-8"?>

<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"/>

<xsl:template name="identity" match="@.*|node()">
<xsl:copy>
<xsl:apply-templates select="@.*|node()"/>
</xsl:copy>
</xsl:template>

<xsl:template match="kw">
<xsl:copy>
<xsl:apply-templates select="@.*"/>
<xsl:attribute name="ihs_cats_seq" select="position()"/>
<xsl:apply-templates select="node()"/>
</xsl:copy>
</xsl:template>

</xsl:stylesheet>

Its 5th line is the first xsl:template element.

What is going on here? I do not see multiple root elements in either the XML document or the XSLT stylesheet.

Thanks!

Kevin Rodgers wrote:

I'm trying to use an XML Task to do a simple XSLT operation, but it fails with this error message:
[XML Task] Error: An error occurred with the following error message: "There are multiple root elements. Line 5, position 2.".
The source XML file validates fine and I've successfully used it as the XML Source in a data flow task to load some SQL Server tables. It has very few line breaks, so the first 5 lines are pretty long: almost 4000 characters, including 34 start-tags, 19 end-tags, and 2 empty element tags. Here's the very beginning of it:
<?xml version="1.0" encoding="UTF-8"?>
<ESDU releaselevel="2006-02" createdate="26 May 2006"><package id="1" title="_standard" shorttitle="_standard" filename="pk_stan" supplementdate="01/05/2005" supplementlevel="1"><abstract><![CDATA[This package contains the standard ESDU Series.]]></abstract>
There is only 1 ESDU root element and only 1 package element.
Of course, the XSLT stylesheet is also an XML document in its own right. I specify it directly in the XML Task:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"/>
<xsl:template name="identity" match="@.*|node()">
<xsl:copy>
<xsl:apply-templates select="@.*|node()"/>
</xsl:copy>
</xsl:template>
<xsl:template match="kw">
<xsl:copy>
<xsl:apply-templates select="@.*"/>
<xsl:attribute name="ihs_cats_seq" select="position()"/>
<xsl:apply-templates select="node()"/>
</xsl:copy>
</xsl:template>
</xsl:stylesheet>
Its 5th line is the first xsl:template element.
What is going on here? I do not see multiple root elements in either the XML document or the XSLT stylesheet.
Thanks!

Well of course as soon as I posted that I found an obvious bug: the xsl:stylesheet start tag should not be an empty element tag. But fixing that to:

<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

leads to an even more obscure error message:

[XML Task] Error: An error occurred with the following error message: "XSLT compile error.".

|||

Kevin Rodgers wrote:

Kevin Rodgers wrote:
I'm trying to use an XML Task to do a simple XSLT operation, but it fails with this error message:
[XML Task] Error: An error occurred with the following error message: "There are multiple root elements. Line 5, position 2.".
The source XML file validates fine and I've successfully used it as the XML Source in a data flow task to load some SQL Server tables. It has very few line breaks, so the first 5 lines are pretty long: almost 4000 characters, including 34 start-tags, 19 end-tags, and 2 empty element tags. Here's the very beginning of it:
<?xml version="1.0" encoding="UTF-8"?>
<ESDU releaselevel="2006-02" createdate="26 May 2006"><package id="1" title="_standard" shorttitle="_standard" filename="pk_stan" supplementdate="01/05/2005" supplementlevel="1"><abstract><![CDATA[This package contains the standard ESDU Series.]]></abstract>
There is only 1 ESDU root element and only 1 package element.
Of course, the XSLT stylesheet is also an XML document in its own right. I specify it directly in the XML Task:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"/>
<xsl:template name="identity" match="@.*|node()">
<xsl:copy>
<xsl:apply-templates select="@.*|node()"/>
</xsl:copy>
</xsl:template>
<xsl:template match="kw">
<xsl:copy>
<xsl:apply-templates select="@.*"/>
<xsl:attribute name="ihs_cats_seq" select="position()"/>
<xsl:apply-templates select="node()"/>
</xsl:copy>
</xsl:template>
</xsl:stylesheet>
Its 5th line is the first xsl:template element.
What is going on here? I do not see multiple root elements in either the XML document or the XSLT stylesheet.
Thanks!
Well of course as soon as I posted that I found an obvious bug: the <xsl:stylesheet> start tag should not be an empty element tag. But fixing that to:
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
leads to an even more obscure error message:
[XML Task] Error: An error occurred with the following error message: "XSLT compile error.".

Sorry to follow up again to my own question, but when I tried to run the transformation via Saxon (the free, open-source, fully compliant XSLT processor) it helpfully reported:

Warning: Running an XSLT 1.0 stylesheet with an XSLT 2.0 processor

And changing the xsl:stylesheet start tag to:

<xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

did indeed allow SSIS to execute the XML task succesfully. But(!) the stylesheet did not work correctly. With Saxon, it correctly adds ihs_cats_seq attributes to each kw element, e.g.

<keywords><kw ihs_cats_seq="1">AERODYNAMICS</kw><kw ihs_cats_seq="2">AMENDMENT</kw><kw ihs_cats_seq="3">LOCATION</kw><kw ihs_cats_seq="4">ORGANISATION</kw><kw ihs_cats_seq="5">RECORD</kw><kw ihs_cats_seq="6">SCHEDULE</kw><kw ihs_cats_seq="7">SERIES</kw></keywords>

But SSIS adds ihs_cats_seq="" to each kw start-tag. Is there a known bug with the position() XPath function?

|||

I was able to get an answer in a different forum:

http://forums.microsoft.com/msdn/showpost.aspx?postid=654370

[XML Task] Error: An error occurred with the following error message: There are multiple roo

I'm trying to use an XML Task to do a simple XSLT operation, but it fails with this error message:

[XML Task] Error: An error occurred with the following error message: "There are multiple root elements. Line 5, position 2.".

There is only 1 ESDU root element and only 1 package element.

Of course, the XSLT stylesheet is also an XML document in its own right. I specify it directly in the XML Task:

<?xml version="1.0" encoding="UTF-8"?>

<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"/>

<xsl:template name="identity" match="@.*|node()">
<xsl:copy>
<xsl:apply-templates select="@.*|node()"/>
</xsl:copy>
</xsl:template>

<xsl:template match="kw">
<xsl:copy>
<xsl:apply-templates select="@.*"/>
<xsl:attribute name="ihs_cats_seq" select="position()"/>
<xsl:apply-templates select="node()"/>
</xsl:copy>
</xsl:template>

</xsl:stylesheet>

Its 5th line is the first xsl:template element.

What is going on here? I do not see multiple root elements in either the XML document or the XSLT stylesheet.

Thanks!

Kevin Rodgers wrote:

I'm trying to use an XML Task to do a simple XSLT operation, but it fails with this error message:
[XML Task] Error: An error occurred with the following error message: "There are multiple root elements. Line 5, position 2.".
The source XML file validates fine and I've successfully used it as the XML Source in a data flow task to load some SQL Server tables. It has very few line breaks, so the first 5 lines are pretty long: almost 4000 characters, including 34 start-tags, 19 end-tags, and 2 empty element tags. Here's the very beginning of it:
<?xml version="1.0" encoding="UTF-8"?>
<ESDU releaselevel="2006-02" createdate="26 May 2006"><package id="1" title="_standard" shorttitle="_standard" filename="pk_stan" supplementdate="01/05/2005" supplementlevel="1"><abstract><![CDATA[This package contains the standard ESDU Series.]]></abstract>
There is only 1 ESDU root element and only 1 package element.
Of course, the XSLT stylesheet is also an XML document in its own right. I specify it directly in the XML Task:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"/>
<xsl:template name="identity" match="@.*|node()">
<xsl:copy>
<xsl:apply-templates select="@.*|node()"/>
</xsl:copy>
</xsl:template>
<xsl:template match="kw">
<xsl:copy>
<xsl:apply-templates select="@.*"/>
<xsl:attribute name="ihs_cats_seq" select="position()"/>
<xsl:apply-templates select="node()"/>
</xsl:copy>
</xsl:template>
</xsl:stylesheet>
Its 5th line is the first xsl:template element.
What is going on here? I do not see multiple root elements in either the XML document or the XSLT stylesheet.
Thanks!

Well of course as soon as I posted that I found an obvious bug: the xsl:stylesheet start tag should not be an empty element tag. But fixing that to:

<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

leads to an even more obscure error message:

[XML Task] Error: An error occurred with the following error message: "XSLT compile error.".

|||

Kevin Rodgers wrote:

Kevin Rodgers wrote:
I'm trying to use an XML Task to do a simple XSLT operation, but it fails with this error message:
[XML Task] Error: An error occurred with the following error message: "There are multiple root elements. Line 5, position 2.".
The source XML file validates fine and I've successfully used it as the XML Source in a data flow task to load some SQL Server tables. It has very few line breaks, so the first 5 lines are pretty long: almost 4000 characters, including 34 start-tags, 19 end-tags, and 2 empty element tags. Here's the very beginning of it:
<?xml version="1.0" encoding="UTF-8"?>
<ESDU releaselevel="2006-02" createdate="26 May 2006"><package id="1" title="_standard" shorttitle="_standard" filename="pk_stan" supplementdate="01/05/2005" supplementlevel="1"><abstract><![CDATA[This package contains the standard ESDU Series.]]></abstract>
There is only 1 ESDU root element and only 1 package element.
Of course, the XSLT stylesheet is also an XML document in its own right. I specify it directly in the XML Task:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"/>
<xsl:template name="identity" match="@.*|node()">
<xsl:copy>
<xsl:apply-templates select="@.*|node()"/>
</xsl:copy>
</xsl:template>
<xsl:template match="kw">
<xsl:copy>
<xsl:apply-templates select="@.*"/>
<xsl:attribute name="ihs_cats_seq" select="position()"/>
<xsl:apply-templates select="node()"/>
</xsl:copy>
</xsl:template>
</xsl:stylesheet>
Its 5th line is the first xsl:template element.
What is going on here? I do not see multiple root elements in either the XML document or the XSLT stylesheet.
Thanks!
Well of course as soon as I posted that I found an obvious bug: the <xsl:stylesheet> start tag should not be an empty element tag. But fixing that to:
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
leads to an even more obscure error message:
[XML Task] Error: An error occurred with the following error message: "XSLT compile error.".

Sorry to follow up again to my own question, but when I tried to run the transformation via Saxon (the free, open-source, fully compliant XSLT processor) it helpfully reported:

Warning: Running an XSLT 1.0 stylesheet with an XSLT 2.0 processor

And changing the xsl:stylesheet start tag to:

<xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

did indeed allow SSIS to execute the XML task succesfully. But(!) the stylesheet did not work correctly. With Saxon, it correctly adds ihs_cats_seq attributes to each kw element, e.g.

But SSIS adds ihs_cats_seq="" to each kw start-tag. Is there a known bug with the position() XPath function?

|||

I was able to get an answer in a different forum:

http://forums.microsoft.com/msdn/showpost.aspx?postid=654370

sql

[Ugent] attach Database error in SQL 7.0

Dear All
I have try to detach and re-attach database from SQL7.0 (Production Server).
The detach process was success, but re-attach database occur a error. There
is a Error message show on my screen.
Changed Language setting to us_english.
Server: Msg 3624, Level 20, State 1, Line 1
Location: pageref.cpp:3882
Expression: pPage->GetLsn () == lp -> GetPrevPageLsn ()
SPID: 9
Process ID: 148
Connection Broken
Do anyone got experience to fix it ? Thanks very much
Gary
Hi Gary
"Gary" wrote:

> Dear All
> I have try to detach and re-attach database from SQL7.0 (Production Server).
> The detach process was success, but re-attach database occur a error. There
> is a Error message show on my screen.
> ----
> Changed Language setting to us_english.
> Server: Msg 3624, Level 20, State 1, Line 1
> Location: pageref.cpp:3882
> Expression: pPage->GetLsn () == lp -> GetPrevPageLsn ()
> SPID: 9
> Process ID: 148
> Connection Broken
> ----
> Do anyone got experience to fix it ? Thanks very much
I have not seen the error, but you may want to try renaming the log file and
using sp_attach_single_file_db. I would also check that this disc if fine
(CHKDSK or similar) and that no errors are being reported in the System Event
log.

> Gary
>
John

[Ugent] attach Database error in SQL 7.0

Dear All
I have try to detach and re-attach database from SQL7.0 (Production Server).
The detach process was success, but re-attach database occur a error. There
is a Error message show on my screen.
----
--
Changed Language setting to us_english.
Server: Msg 3624, Level 20, State 1, Line 1
Location: pageref.cpp:3882
Expression: pPage->GetLsn () == lp -> GetPrevPageLsn ()
SPID: 9
Process ID: 148
Connection Broken
----
--
Do anyone got experience to fix it ? Thanks very much
GaryHi Gary
"Gary" wrote:

> Dear All
> I have try to detach and re-attach database from SQL7.0 (Production Server
).
> The detach process was success, but re-attach database occur a error. Ther
e
> is a Error message show on my screen.
> ----
--
> Changed Language setting to us_english.
> Server: Msg 3624, Level 20, State 1, Line 1
> Location: pageref.cpp:3882
> Expression: pPage->GetLsn () == lp -> GetPrevPageLsn ()
> SPID: 9
> Process ID: 148
> Connection Broken
> ----
--
> Do anyone got experience to fix it ? Thanks very much
I have not seen the error, but you may want to try renaming the log file and
using sp_attach_single_file_db. I would also check that this disc if fine
(CHKDSK or similar) and that no errors are being reported in the System Even
t
log.

> Gary
>
John

[Transfer SQL Server Objects Task] Error: Table does not exist at the source.

Hello,

I am running a package that used to transfers data from one SQL2005 to another SQL2005. There are multiple schemas associated with the database. Until recently, this pacakage would work. Now I am getting the following error for all the tables not owned by dbo:

Any help on this would be appreciated.

Thanks, sck10

[Transfer SQL Server Objects Task] Error: Table "tblAudiocast" does not exist at the source.

Microsoft SQL Server Management Studio 9.00.3042.00
Microsoft Analysis Services Client Tools 2005.090.3042.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 7.0.5730.11
Microsoft .NET Framework 2.0.50727.832
Operating System 5.1.2600

May be it;s a direct error that in the source "tblAudiocast" table may not be exisiting or renamed!!!

Or check the connection strings if it's pointing to the correct data base!!

Dev

|||

Thanks Dev, but all the tables exist. We copy the schema from the production database to the local database, so they are duplicates. And it works for tables that belong to dbo only, but fails for all other tables.

sck10

|||

This thread describes the same problem - it's a known bug. It may have been fixed in SP2, but I'm not positive.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=207812&SiteID=1

|||

Thanks jwelch,

My SSIS package was working until recently.

sck10

sql

[Transfer SQL Server Objects Task] Error: Table does not exist at the source.

Hello,

Any help on this would be appreciated.

Thanks, sck10

[Transfer SQL Server Objects Task] Error: Table "tblAudiocast" does not exist at the source.

May be it;s a direct error that in the source "tblAudiocast" table may not be exisiting or renamed!!!

Or check the connection strings if it's pointing to the correct data base!!

Dev

|||

sck10

|||

This thread describes the same problem - it's a known bug. It may have been fixed in SP2, but I'm not positive.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=207812&SiteID=1

|||

Thanks jwelch,

My SSIS package was working until recently.

sck10

[Transfer SQL Server Objects Task] Error: Table "XXXXXXX" does not exist at the source

Does anyone know what could be causing the error on Transfer SQL Server Objects Task? I tried to develope a SSIS project in the Business Intelligence studio to transfer table between databases on the same server. However, I have been getting the following error:

[Transfer SQL Server Objects Task] Error: Table "XXXXXX" does not exist at the source.

Is there a setting that I need to change to make this work? Thank you for your help.

Is the table you've specified to move on the task in the source database?|||

Yes. It is in there. I can see it in the selection list after I select the database. Thanks.

And Transfer SQL Server Objecdts Task is the only task in that SSIS package.

|||I think your problem is related to the schema of the table you are trying to copy.

I created table "testtable" in testdb1. The schema was "dbo". I could transfer this table to another database named testdb2 in the same server using Transfer SQL Server Objects Task.

Then, I changed the schema of "testtable" to "guest". When I executed the same task, I got the error message "[Transfer SQL Server Objects Task] Error: Table "testtable" does not exist at the source. "|||

Thanks for your response. Where di you create the "Transfer SQL Server Objects Task"? Is it under control flow or data flow? When I had the error to only task I had was the "Transfer SQL SErver Obejcts Task" under Control Flow.

Thanks.

|||Transfer SQL Server Objects is a Control Flow task. I had my task in the control flow tab and the task I have explained above was the only task I had in the package.|||I had the exact issue when I transfer the data (both table and xml schema) from my dev. box to the production server. It seemed to me that this particular control task recognizes only the dbo schema. Is this bug fixed in SP1?|||No. We are looking to fix this issue in one of the future releases.|||I am trying to figure out exactly what the issue is here -- can we not copy tables from one database to another at all at this time? I had both tables as dbo schemas, and I had a different error, this time about the destination not being available. I set the schema owner of the tables to be the same as the authenticated user, and then I received the error that it does not exist at the source.

At this time (10/2006), is there any way to copy tables from one server to another via SSIS? I would think this basic of a task would be the first to work on a newer DTS... ?

Thanks in advance

-Chris Rasmussen|||

I am hoping someone will answer the last question. I cannot beleive you would release a product with such a simple task not working. As a workaround, I suppose I can create an SMO task to handle this, but that is more development time than I had expected to use. Please fix this with your NEXT release, not an undetermined FUTURE release. This type of missing functionality is hard to point at and convince anyone in the position of making decisions to migrate to 2005. Come on guys and gals.

Your frustrated supporter...

|||

Hi Cliff!

I'd like to share my frustration with Transfer SQL Server Object Task. I am trying to do something very simple - transfer 3 tables with primary/foreign keys, referential ingegrity and some data and spent hours of fruitless tweaking of the task. If someone offers a very simple step by step process on how to configure the "Transfer SQL Server Object task" to do that, I would be very grateful.

|||Are you planning on fixing this in SP2?|||Hi

I'd like to add my vote for this feature request. Can someone from the dev team tell if the decision of fixing this has already been taken somehow ?

Any insight will be most welcome, and will help us pick the right solution.

Thibaut Barrère|||

Hi,

I am also having problems with the "Transfer SQL Server Objects" task. It simply does not work.

The editor interface is sweet, however, and looks very promising. My issue is that I cannot debug this task. I cannot see the code that is generated by the task, and logging does not reveal what I want: the SQL code or whatever code is generated by the task. I want to see the actual table name syntax contained in the resultant command sent over, with the assumption that there is something wrong there.

The documentation is very clear, promising effective results. The reality is different, however. This is simply a management issue. The product was released too early, and the testing regimen must have been inadequate or mismatched with the document.

I have the Evaluation Version of Enterprise. The SMO connectors all test properly, and there is no other problem. The wizard works fine from SSMS, and when I save the output from the wizard to a package, the package does not use the "Transfer SQL Server Objects" task.

So, guys, what we have here is a defect.

This is very annoying, and I will write a letter to Bill Gates requesting immediate attention to this issue.

|||The fix is not released yet.

[Transfer SQL Server Objects Task] Error: Table "XXXXXXX" does not exist at the source

[Transfer SQL Server Objects Task] Error: Table "XXXXXX" does not exist at the source.

Is there a setting that I need to change to make this work? Thank you for your help.

Is the table you've specified to move on the task in the source database?|||

Yes. It is in there. I can see it in the selection list after I select the database. Thanks.

And Transfer SQL Server Objecdts Task is the only task in that SSIS package.

|||I think your problem is related to the schema of the table you are trying to copy.

I created table "testtable" in testdb1. The schema was "dbo". I could transfer this table to another database named testdb2 in the same server using Transfer SQL Server Objects Task.

Thanks.

At this time (10/2006), is there any way to copy tables from one server to another via SSIS? I would think this basic of a task would be the first to work on a newer DTS... ?

Thanks in advance

-Chris Rasmussen
|||

Your frustrated supporter...

|||

Hi Cliff!

|||Are you planning on fixing this in SP2?|||Hi

I'd like to add my vote for this feature request. Can someone from the dev team tell if the decision of fixing this has already been taken somehow ?

Any insight will be most welcome, and will help us pick the right solution.

Thibaut Barrère

|||

Hi,

I am also having problems with the "Transfer SQL Server Objects" task. It simply does not work.

So, guys, what we have here is a defect.

This is very annoying, and I will write a letter to Bill Gates requesting immediate attention to this issue.

|||The fix is not released yet.

[Transfer SQL Server Objects Task] Error: Table "XXXXXXX" does not exist at the so

[Transfer SQL Server Objects Task] Error: Table "XXXXXX" does not exist at the source.

Is there a setting that I need to change to make this work? Thank you for your help.

Is the table you've specified to move on the task in the source database?|||

Yes. It is in there. I can see it in the selection list after I select the database. Thanks.

And Transfer SQL Server Objecdts Task is the only task in that SSIS package.

|||I think your problem is related to the schema of the table you are trying to copy.

I created table "testtable" in testdb1. The schema was "dbo". I could transfer this table to another database named testdb2 in the same server using Transfer SQL Server Objects Task.

Thanks.

At this time (10/2006), is there any way to copy tables from one server to another via SSIS? I would think this basic of a task would be the first to work on a newer DTS... ?

Thanks in advance

-Chris Rasmussen|||

Your frustrated supporter...

|||

Hi Cliff!

|||Are you planning on fixing this in SP2?|||Hi

I'd like to add my vote for this feature request. Can someone from the dev team tell if the decision of fixing this has already been taken somehow ?

Any insight will be most welcome, and will help us pick the right solution.

Thibaut Barrère|||

Hi,

I am also having problems with the "Transfer SQL Server Objects" task. It simply does not work.

So, guys, what we have here is a defect.

This is very annoying, and I will write a letter to Bill Gates requesting immediate attention to this issue.

|||The fix is not released yet.

[Transfer SQL Server Objects Task] Error: Table "XXXXXXX" does not exist at the so

[Transfer SQL Server Objects Task] Error: Table "XXXXXX" does not exist at the source.

Is there a setting that I need to change to make this work? Thank you for your help.

Is the table you've specified to move on the task in the source database?|||

Yes. It is in there. I can see it in the selection list after I select the database. Thanks.

And Transfer SQL Server Objecdts Task is the only task in that SSIS package.

|||I think your problem is related to the schema of the table you are trying to copy.

I created table "testtable" in testdb1. The schema was "dbo". I could transfer this table to another database named testdb2 in the same server using Transfer SQL Server Objects Task.

Thanks.

At this time (10/2006), is there any way to copy tables from one server to another via SSIS? I would think this basic of a task would be the first to work on a newer DTS... ?

Thanks in advance

-Chris Rasmussen|||

Your frustrated supporter...

|||

Hi Cliff!

|||Are you planning on fixing this in SP2?|||Hi

I'd like to add my vote for this feature request. Can someone from the dev team tell if the decision of fixing this has already been taken somehow ?

Any insight will be most welcome, and will help us pick the right solution.

Thibaut Barrère|||

Hi,

I am also having problems with the "Transfer SQL Server Objects" task. It simply does not work.

So, guys, what we have here is a defect.

This is very annoying, and I will write a letter to Bill Gates requesting immediate attention to this issue.

|||The fix is not released yet.sql

[Transfer SQL Server Objects Task] Error: Table "XXXXXXX" does not exist at the so

[Transfer SQL Server Objects Task] Error: Table "XXXXXX" does not exist at the source.

Is there a setting that I need to change to make this work? Thank you for your help.

Is the table you've specified to move on the task in the source database?|||

Yes. It is in there. I can see it in the selection list after I select the database. Thanks.

And Transfer SQL Server Objecdts Task is the only task in that SSIS package.

|||I think your problem is related to the schema of the table you are trying to copy.

I created table "testtable" in testdb1. The schema was "dbo". I could transfer this table to another database named testdb2 in the same server using Transfer SQL Server Objects Task.

Thanks.

At this time (10/2006), is there any way to copy tables from one server to another via SSIS? I would think this basic of a task would be the first to work on a newer DTS... ?

Thanks in advance

-Chris Rasmussen|||

Your frustrated supporter...

|||

Hi Cliff!

|||Are you planning on fixing this in SP2?|||Hi

I'd like to add my vote for this feature request. Can someone from the dev team tell if the decision of fixing this has already been taken somehow ?

Any insight will be most welcome, and will help us pick the right solution.

Thibaut Barrère|||

Hi,

I am also having problems with the "Transfer SQL Server Objects" task. It simply does not work.

So, guys, what we have here is a defect.

This is very annoying, and I will write a letter to Bill Gates requesting immediate attention to this issue.

|||The fix is not released yet.

[Transfer SQL Server Objects Task] Error: Table "MySchema.MyTableName" does not ex

[Transfer SQL Server Objects Task] Error: Table "XXXXXX" does not exist at the source.

Is there a setting that I need to change to make this work? Thank you for your help.

Is the table you've specified to move on the task in the source database?|||

Yes. It is in there. I can see it in the selection list after I select the database. Thanks.

And Transfer SQL Server Objecdts Task is the only task in that SSIS package.

|||I think your problem is related to the schema of the table you are trying to copy.

I created table "testtable" in testdb1. The schema was "dbo". I could transfer this table to another database named testdb2 in the same server using Transfer SQL Server Objects Task.

Thanks.

At this time (10/2006), is there any way to copy tables from one server to another via SSIS? I would think this basic of a task would be the first to work on a newer DTS... ?

Thanks in advance

-Chris Rasmussen|||

Your frustrated supporter...

|||

Hi Cliff!

|||Are you planning on fixing this in SP2?|||Hi

I'd like to add my vote for this feature request. Can someone from the dev team tell if the decision of fixing this has already been taken somehow ?

Any insight will be most welcome, and will help us pick the right solution.

Thibaut Barrère|||

Hi,

I am also having problems with the "Transfer SQL Server Objects" task. It simply does not work.

So, guys, what we have here is a defect.

This is very annoying, and I will write a letter to Bill Gates requesting immediate attention to this issue.

|||The fix is not released yet.

Thursday, March 22, 2012

_WA Statistics Error

_WA Statistics Error

_hypmv error

_hypmv error

\minint\system32\biosinfo.inf error code 263

\minint\system32\biosinfo.inf error code 263

\\.\Tape0 is not a vaild Microsoft Tape format backup set

Tuesday, March 20, 2012

\\.\Tape0 is not a vaild Microsoft Tape format backup set

[XML Task] Error: An error occurred with the following error message: There are multiple root el

[XML Task] Error: An error occurred with the following error message: There are multiple roo

[Ugent] attach Database error in SQL 7.0

[Ugent] attach Database error in SQL 7.0

[Transfer SQL Server Objects Task] Error: Table does not exist at the source.

[Transfer SQL Server Objects Task] Error: Table does not exist at the source.

[Transfer SQL Server Objects Task] Error: Table "XXXXXXX" does not exist at the source

[Transfer SQL Server Objects Task] Error: Table "XXXXXXX" does not exist at the source

[Transfer SQL Server Objects Task] Error: Table "XXXXXXX" does not exist at the so

[Transfer SQL Server Objects Task] Error: Table "XXXXXXX" does not exist at the so

[Transfer SQL Server Objects Task] Error: Table "XXXXXXX" does not exist at the so

[Transfer SQL Server Objects Task] Error: Table "MySchema.MyTableName" does not ex

sql rowcount

Blog Archive

About Me