[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.".

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

sql

[Vent] SQL Server Upgrade

It just occurred to the suits recently that the 240 GB is not enough, so
what did they do?
Change the RAID configuration?!? NO!
Get more drives for the RAID 10 stack?!? NO!
They bought a SATA drive and wired it to the SQL Server with a USB
connector.
And now there's an email storm going on about how slow the backups are.
<bonking head on desk>
Is it ironic poetry that my computer at home that I designed and built to
play doom has twice the speed and twice the capacity of the Big Momma SQL
Server at work?!? YES!
Suits and computers should never *EVER* mix.
Peace & happy computing,
Mike Labosh, MCSD
"Musha ring dum a doo dum a da!" -- James HetfieldMike,
At some point, you should start thinking about your future. It's going to b
e pretty hard to get another job with this kind of resum stain.
Regards,
Brian Selzer
"Mike Labosh" <mlabosh@.hotmail.com> wrote in message news:uhOzmM#rFHA.3788@.TK2MSFTNGP12.phx
.gbl...
> It just occurred to the suits recently that the 240 GB is not enough, so
> what did they do?
>
> Change the RAID configuration?!? NO!
> Get more drives for the RAID 10 stack?!? NO!
>
> They bought a SATA drive and wired it to the SQL Server with a USB
> connector.
>
> And now there's an email storm going on about how slow the backups are.
>
> <bonking head on desk>
>
> Is it ironic poetry that my computer at home that I designed and built to
> play doom has twice the speed and twice the capacity of the Big Momma SQL
> Server at work?!? YES!
>
> Suits and computers should never *EVER* mix.
>
> --
> Peace & happy computing,
>
> Mike Labosh, MCSD
> "Musha ring dum a doo dum a da!" -- James Hetfield
>
>|||I wanted to change the world. But I have found that the only thing one can
be sure of changing is oneself.
- Aldous Huxley
"Mike Labosh" <mlabosh@.hotmail.com> wrote in message
news:uhOzmM%23rFHA.3788@.TK2MSFTNGP12.phx.gbl...
> It just occurred to the suits recently that the 240 GB is not enough, so
> what did they do?
> Change the RAID configuration?!? NO!
> Get more drives for the RAID 10 stack?!? NO!
> They bought a SATA drive and wired it to the SQL Server with a USB
> connector.
> And now there's an email storm going on about how slow the backups are.
> <bonking head on desk>
> Is it ironic poetry that my computer at home that I designed and built to
> play doom has twice the speed and twice the capacity of the Big Momma SQL
> Server at work?!? YES!
> Suits and computers should never *EVER* mix.
> --
> Peace & happy computing,
> Mike Labosh, MCSD
> "Musha ring dum a doo dum a da!" -- James Hetfield
>|||And this company you're at is actually making money?
How?
ML|||> At some point, you should start thinking about
> your future. It's going to be pretty hard to get
> another job with this kind of resum stain.
Or "shit stain"?
My major malfunction is that I love my work too much to leave it. :( The
only good part is that I have at least identified what my own malfunction
is.
--
Peace & happy computing,
Mike Labosh, MCSD
"Musha ring dum a doo dum a da!" -- James Hetfield|||The 2005 certs will be available soon, so you have something to occupy the
time while you wait for the power systems to come back online. ;-)
"Mike Labosh" <mlabosh@.hotmail.com> wrote in message
news:ez2GQ4%23rFHA.1168@.TK2MSFTNGP11.phx.gbl...
> Or "shit stain"?
> My major malfunction is that I love my work too much to leave it. :( The
> only good part is that I have at least identified what my own malfunction
> is.
> --
> Peace & happy computing,
> Mike Labosh, MCSD
> "Musha ring dum a doo dum a da!" -- James Hetfield
>|||>I wanted to change the world. But I have found that the only thing one can
>be sure of changing is oneself.
> - Aldous Huxley
Whhhooooooo! That was actually quite profound. Who is this Aldous Huxley
person?
--
Peace & happy computing,
Mike Labosh, MCSD
"Musha ring dum a doo dum a da!" -- James Hetfield
"JT" <someone@.microsoft.com> wrote in message
news:uB%23siy%23rFHA.3732@.TK2MSFTNGP11.phx.gbl...
> "Mike Labosh" <mlabosh@.hotmail.com> wrote in message
> news:uhOzmM%23rFHA.3788@.TK2MSFTNGP12.phx.gbl...
>|||> And this company you're at is actually making money?
Who knows?

> How?
Perhaps by sacrificing live chickens over the SQL Server?! (just my guess)
Peace & happy computing,
Mike Labosh, MCSD
"Musha ring dum a doo dum a da!" -- James Hetfield|||http://www.quotationspage.com/quotes/Aldous_Huxley/
http://huxley.net/index.html
http://huxley.net/bnw/index.html
"Mike Labosh" <mlabosh@.hotmail.com> wrote in message
news:%23l6h%23L$rFHA.308@.TK2MSFTNGP10.phx.gbl...
> Whhhooooooo! That was actually quite profound. Who is this Aldous Huxley
> person?
> --
> Peace & happy computing,
> Mike Labosh, MCSD
> "Musha ring dum a doo dum a da!" -- James Hetfield
> "JT" <someone@.microsoft.com> wrote in message
> news:uB%23siy%23rFHA.3732@.TK2MSFTNGP11.phx.gbl...
>|||> Perhaps by sacrificing live chickens over the SQL Server?! (just my guess
)
Aha! That would explain slow backups! Chicken guts in the air vents! Quite
common...
ML

[File System Task] Error: An error occurred with the following error message: "Access to th

Hi -

I have an File System Task that copies a file from one directory ot another. When I hard code the target directory (c:\dir\file.txt) it works fine. When I change it to a virtual directory (\\server\dir\file.txt) I get a security error:

[File System Task] Error: An error occurred with the following error message: "Access to the path '\\grace\hbtest\to\S2TMM_Live_Title_000002.xml' is denied.".

Where do I change the security settings?

Thanks - Grace

Security to network shares is dependent on the user who is running the package. If you are running it yourself, make sure you have permissions to the share. If you are running it from SQL Agent, you might need to use a proxy account (search for SQL Agent Proxy in Books Online) to access it.

[Execute SQL Task] Error: An error occurred while assigning a value to variable...

hi chaps

i m getting the following ERROR:

[Execute SQL Task] Error: An error occurred while assigning a value to variable "JDETimezone": "Unable to find column Timezone in the result set.".

i know what the problem is i.e. no row is returned then what is the problem

here you are.... i want to it work... strange... ok i explain...

actully i have some processign to do with variable JDETimezone even no row is returned.... can u tell me the alternative to do the follwing task...

I want to retrieve a record from some table and do some processing and if no row is present or returned then i want to do seperate processing.... can ne one help me out ?

regards,

Anas

That error usually occurs when you either don't have a column in your select statement named "Timezone", or you didn't name the resultset Timezone. You may want to check your settings.

If you want to do separate processing when no rows are returned then in the Error Flow redirect the rows instead of Failing or Ignoring them.

|||

thanx for your reply

but i sure I have both, column name Timezone in Select statement as well as in Resultset...

problem is that it doesnt return any row and causes error...Sean you are right I can use Error flow but the problem that i dont want any of my task to fail becuase i m doing error handling by Task failure event which then email the failure information to admin group

does ne one have solution of my problem?

regards,

Anas

|||

One way to implement different processing logic based on the result set row count is by having a Execute SQL task that counts the total number of rows returned by a query and assign the count to a variable which can later be used to determine the control flow.

See http://msdn2.microsoft.com/en-US/library/ms140153.aspx

[Execute SQL Task] Error: An error occurred while assigning a value to variable

hello
I have a problem with Sql task
when sql task tried to assing a value to my variable I have this error ""La valeur n'est pas comprise dans la plage attendue."
I'm using ODBC connexion for a csv file

someone can help me ?

thanks
It might help if you translated the error message to english.|||

we can translate as " the value is not included in the correct space " or something like that

|||

Take a look at this - it explains how to set up the Execute SQL task for retrieving values.

http://www.sqlis.com/58.aspx

[BEA][SQLServer JDBC Driver][SQLServer]Warning:Fatal error 605 occurred

Dear group
The following error occured
[BEA][SQLServer JDBC Driver][SQLServer]Warning:Fatal error 605 occurred
and after using DBCC was rectified, but we are not sure the cause of
this problem.
Is it due to SAN installed last month or is there any other reason.
KaranError 605
Severity Level 21
Attempt to fetch logical page %S_PGID in database '%.*ls' belongs to object
'%.*ls', not to object '%.*ls'.
You have corruption in your DB.
Look at http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Karan Lobana" wrote:
>
> Dear group
> The following error occured
> [BEA][SQLServer JDBC Driver][SQLServer]Warning:Fatal error 605 occurred
> and after using DBCC was rectified, but we are not sure the cause of
> this problem.
> Is it due to SAN installed last month or is there any other reason.
>
> Karan
>

[380] Unable to start JobManager thread for job ......

An error occurred on SQL Agent Error Log of my system as follows.
[380] Unable to start JobManager thread for job .....
I have two questions.
1. How can I increase the number of thread allocated to JobManager? Should I
only decrease the number of concurrent job?
2. Is the only solution to restart the SQL Agent service in this case? The
job was not executed after this error.
Thank you
Hanky
Do you know how many jobs are running concurrently ? It could be a thread
issue .. but thats usually another error message that clearly states that
its waiting for a thread... something like that.. It could be that your
server is busy ... You may also consider opening up a PSS case..
"??" <hanky74@.daum.net> wrote in message
news:uU4JWJDgEHA.2916@.TK2MSFTNGP12.phx.gbl...
> An error occurred on SQL Agent Error Log of my system as follows.
> [380] Unable to start JobManager thread for job .....
> I have two questions.
> 1. How can I increase the number of thread allocated to JobManager? Should
I
> only decrease the number of concurrent job?
> 2. Is the only solution to restart the SQL Agent service in this case? The
> job was not executed after this error.
> Thank you
> Hanky
>

[380] Unable to start JobManager thread for job ......

An error occurred on SQL Agent Error Log of my system as follows.
[380] Unable to start JobManager thread for job .....
I have two questions.
1. How can I increase the number of thread allocated to JobManager? Should I
only decrease the number of concurrent job?
2. Is the only solution to restart the SQL Agent service in this case? The
job was not executed after this error.
Thank you
HankyDo you know how many jobs are running concurrently ? It could be a thread
issue .. but thats usually another error message that clearly states that
its waiting for a thread... something like that.. It could be that your
server is busy ... You may also consider opening up a PSS case..
"??" <hanky74@.daum.net> wrote in message
news:uU4JWJDgEHA.2916@.TK2MSFTNGP12.phx.gbl...
> An error occurred on SQL Agent Error Log of my system as follows.
> [380] Unable to start JobManager thread for job .....
> I have two questions.
> 1. How can I increase the number of thread allocated to JobManager? Should
I
> only decrease the number of concurrent job?
> 2. Is the only solution to restart the SQL Agent service in this case? The
> job was not executed after this error.
> Thank you
> Hanky
>

[380] Unable to start JobManager thread for job ......

An error occurred on SQL Agent Error Log of my system as follows.
[380] Unable to start JobManager thread for job .....
I have two questions.
1. How can I increase the number of thread allocated to JobManager? Should I
only decrease the number of concurrent job?
2. Is the only solution to restart the SQL Agent service in this case? The
job was not executed after this error.
Thank you
HankyDo you know how many jobs are running concurrently ? It could be a thread
issue .. but thats usually another error message that clearly states that
its waiting for a thread... something like that.. It could be that your
server is busy ... You may also consider opening up a PSS case..
"Çѱ⿵" <hanky74@.daum.net> wrote in message
news:uU4JWJDgEHA.2916@.TK2MSFTNGP12.phx.gbl...
> An error occurred on SQL Agent Error Log of my system as follows.
> [380] Unable to start JobManager thread for job .....
> I have two questions.
> 1. How can I increase the number of thread allocated to JobManager? Should
I
> only decrease the number of concurrent job?
> 2. Is the only solution to restart the SQL Agent service in this case? The
> job was not executed after this error.
> Thank you
> Hanky
>