Hi,
I have a couple of DTS job that runs daily. However, for the past three days
a different job has failed every night with very similar looking error
messages that are listed below. When I re-run the job after it fails it runs
fine and completes successfully. Any information to resolve this will be
highly appreciated.
Error: -2147467259 (80004005); Provider Error: 11 (B)
Error string: [DBNETLIB][ConnectionRead (recv()).]General network error.
Check your network documentation.
Error source: Microsoft OLE DB Provider for SQL Server
Error: -2147467259 (80004005); Provider Error: 11 (B)
Error string: [DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General
network error. Check your network documentation.
Error source: Microsoft OLE DB Provider for SQL Server
Error: -2147467259 (80004005); Provider Error: 0 (0)
Error string: Timeout expired
Error source: Microsoft OLE DB Provider for SQL ServerI think there used to be an issue like this due to something related to
connection pooling, and IIRC the workaround was to disable connection
pooling. Not sure if this is the same issue tho.
Did you try doing a search on support.microsoft.com?
--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:21211FD0-C372-436A-9A53-FB5F0B631447@.microsoft.com...
> Hi,
> I have a couple of DTS job that runs daily. However, for the past three
> days
> a different job has failed every night with very similar looking error
> messages that are listed below. When I re-run the job after it fails it
> runs
> fine and completes successfully. Any information to resolve this will be
> highly appreciated.
> Error: -2147467259 (80004005); Provider Error: 11 (B)
> Error string: [DBNETLIB][ConnectionRead (recv()).]General network
> error.
> Check your network documentation.
> Error source: Microsoft OLE DB Provider for SQL Server
>
> Error: -2147467259 (80004005); Provider Error: 11 (B)
> Error string: [DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General
> network error. Check your network documentation.
> Error source: Microsoft OLE DB Provider for SQL Server
>
> Error: -2147467259 (80004005); Provider Error: 0 (0)
> Error string: Timeout expired
> Error source: Microsoft OLE DB Provider for SQL Server
>
>
>|||Have see dozens of these, and almost everytime it was hardware or
connectivity driver related...not SQL Server
Stress test the network with NetMon running. Sorry I can't help on the
Netmon side. The stress test can be as simple as copying a HUGE file from
point A to point B.
I've seen corrupt/mismatched drivers, bad router ports and even crimped
cables cause this.
--
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:21211FD0-C372-436A-9A53-FB5F0B631447@.microsoft.com...
> Hi,
> I have a couple of DTS job that runs daily. However, for the past three
> days
> a different job has failed every night with very similar looking error
> messages that are listed below. When I re-run the job after it fails it
> runs
> fine and completes successfully. Any information to resolve this will be
> highly appreciated.
> Error: -2147467259 (80004005); Provider Error: 11 (B)
> Error string: [DBNETLIB][ConnectionRead (recv()).]General network
> error.
> Check your network documentation.
> Error source: Microsoft OLE DB Provider for SQL Server
>
> Error: -2147467259 (80004005); Provider Error: 11 (B)
> Error string: [DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General
> network error. Check your network documentation.
> Error source: Microsoft OLE DB Provider for SQL Server
>
> Error: -2147467259 (80004005); Provider Error: 0 (0)
> Error string: Timeout expired
> Error source: Microsoft OLE DB Provider for SQL Server
>
>
>
Showing posts with label job. Show all posts
Showing posts with label job. Show all posts
Thursday, March 22, 2012
Error: -2147467259 (80004005); Provider Error: 0 (0)
Hi,
I have a couple of DTS job that runs daily. However, for the past three days
a different job has failed every night with very similar looking error
messages that are listed below. When I re-run the job after it fails it runs
fine and completes successfully. Any information to resolve this will be
highly appreciated.
Error: -2147467259 (80004005); Provider Error: 11 (B)
Error string: [DBNETLIB][ConnectionRead (recv()).]General network error.
Check your network documentation.
Error source: Microsoft OLE DB Provider for SQL Server
Error: -2147467259 (80004005); Provider Error: 11 (B)
Error string: [DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General
network error. Check your network documentation.
Error source: Microsoft OLE DB Provider for SQL Server
Error: -2147467259 (80004005); Provider Error: 0 (0)
Error string: Timeout expired
Error source: Microsoft OLE DB Provider for SQL Server
I think there used to be an issue like this due to something related to
connection pooling, and IIRC the workaround was to disable connection
pooling. Not sure if this is the same issue tho.
Did you try doing a search on support.microsoft.com?
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:21211FD0-C372-436A-9A53-FB5F0B631447@.microsoft.com...
> Hi,
> I have a couple of DTS job that runs daily. However, for the past three
> days
> a different job has failed every night with very similar looking error
> messages that are listed below. When I re-run the job after it fails it
> runs
> fine and completes successfully. Any information to resolve this will be
> highly appreciated.
> Error: -2147467259 (80004005); Provider Error: 11 (B)
> Error string: [DBNETLIB][ConnectionRead (recv()).]General network
> error.
> Check your network documentation.
> Error source: Microsoft OLE DB Provider for SQL Server
>
> Error: -2147467259 (80004005); Provider Error: 11 (B)
> Error string: [DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General
> network error. Check your network documentation.
> Error source: Microsoft OLE DB Provider for SQL Server
>
> Error: -2147467259 (80004005); Provider Error: 0 (0)
> Error string: Timeout expired
> Error source: Microsoft OLE DB Provider for SQL Server
>
>
>
|||Have see dozens of these, and almost everytime it was hardware or
connectivity driver related...not SQL Server
Stress test the network with NetMon running. Sorry I can't help on the
Netmon side. The stress test can be as simple as copying a HUGE file from
point A to point B.
I've seen corrupt/mismatched drivers, bad router ports and even crimped
cables cause this.
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:21211FD0-C372-436A-9A53-FB5F0B631447@.microsoft.com...
> Hi,
> I have a couple of DTS job that runs daily. However, for the past three
> days
> a different job has failed every night with very similar looking error
> messages that are listed below. When I re-run the job after it fails it
> runs
> fine and completes successfully. Any information to resolve this will be
> highly appreciated.
> Error: -2147467259 (80004005); Provider Error: 11 (B)
> Error string: [DBNETLIB][ConnectionRead (recv()).]General network
> error.
> Check your network documentation.
> Error source: Microsoft OLE DB Provider for SQL Server
>
> Error: -2147467259 (80004005); Provider Error: 11 (B)
> Error string: [DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General
> network error. Check your network documentation.
> Error source: Microsoft OLE DB Provider for SQL Server
>
> Error: -2147467259 (80004005); Provider Error: 0 (0)
> Error string: Timeout expired
> Error source: Microsoft OLE DB Provider for SQL Server
>
>
>
I have a couple of DTS job that runs daily. However, for the past three days
a different job has failed every night with very similar looking error
messages that are listed below. When I re-run the job after it fails it runs
fine and completes successfully. Any information to resolve this will be
highly appreciated.
Error: -2147467259 (80004005); Provider Error: 11 (B)
Error string: [DBNETLIB][ConnectionRead (recv()).]General network error.
Check your network documentation.
Error source: Microsoft OLE DB Provider for SQL Server
Error: -2147467259 (80004005); Provider Error: 11 (B)
Error string: [DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General
network error. Check your network documentation.
Error source: Microsoft OLE DB Provider for SQL Server
Error: -2147467259 (80004005); Provider Error: 0 (0)
Error string: Timeout expired
Error source: Microsoft OLE DB Provider for SQL Server
I think there used to be an issue like this due to something related to
connection pooling, and IIRC the workaround was to disable connection
pooling. Not sure if this is the same issue tho.
Did you try doing a search on support.microsoft.com?
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:21211FD0-C372-436A-9A53-FB5F0B631447@.microsoft.com...
> Hi,
> I have a couple of DTS job that runs daily. However, for the past three
> days
> a different job has failed every night with very similar looking error
> messages that are listed below. When I re-run the job after it fails it
> runs
> fine and completes successfully. Any information to resolve this will be
> highly appreciated.
> Error: -2147467259 (80004005); Provider Error: 11 (B)
> Error string: [DBNETLIB][ConnectionRead (recv()).]General network
> error.
> Check your network documentation.
> Error source: Microsoft OLE DB Provider for SQL Server
>
> Error: -2147467259 (80004005); Provider Error: 11 (B)
> Error string: [DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General
> network error. Check your network documentation.
> Error source: Microsoft OLE DB Provider for SQL Server
>
> Error: -2147467259 (80004005); Provider Error: 0 (0)
> Error string: Timeout expired
> Error source: Microsoft OLE DB Provider for SQL Server
>
>
>
|||Have see dozens of these, and almost everytime it was hardware or
connectivity driver related...not SQL Server
Stress test the network with NetMon running. Sorry I can't help on the
Netmon side. The stress test can be as simple as copying a HUGE file from
point A to point B.
I've seen corrupt/mismatched drivers, bad router ports and even crimped
cables cause this.
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:21211FD0-C372-436A-9A53-FB5F0B631447@.microsoft.com...
> Hi,
> I have a couple of DTS job that runs daily. However, for the past three
> days
> a different job has failed every night with very similar looking error
> messages that are listed below. When I re-run the job after it fails it
> runs
> fine and completes successfully. Any information to resolve this will be
> highly appreciated.
> Error: -2147467259 (80004005); Provider Error: 11 (B)
> Error string: [DBNETLIB][ConnectionRead (recv()).]General network
> error.
> Check your network documentation.
> Error source: Microsoft OLE DB Provider for SQL Server
>
> Error: -2147467259 (80004005); Provider Error: 11 (B)
> Error string: [DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General
> network error. Check your network documentation.
> Error source: Microsoft OLE DB Provider for SQL Server
>
> Error: -2147467259 (80004005); Provider Error: 0 (0)
> Error string: Timeout expired
> Error source: Microsoft OLE DB Provider for SQL Server
>
>
>
Wednesday, March 21, 2012
Error: 17968, Severity: 15, State: 1
I am running a job every night. It runs fine until last
saturday. In job we are executing 25 stored procedures.
We are getting error after running 12 procedures and
gives error -- "Line 1: Incorrect syntax near '>'.
[SQLSTATE 42000] (Error 170). The step failed". Actually
There is no syntax error. When I checked error log it
shows -- "Operating system error 170., Line 1: Incorrect
syntax near '>'.2004-08-23 20:33:07.27 logon Login
succeeded for user 'US\dashbrd'. Connection: Trusted.
Error encountered while executing xp_sendmail @.query..
Error: 17968, Severity: 15, State: 1 ".
We are running job again starting with stored procedure
12. It is running fine. I don't understand why it
happens? Can any one help melittle tip , when you Operating System Error x , type NET HELPMSG x to see
what it corresponds to , sometimes a valuable clue to whats going on
ie NET HELPMSG 170 gives you "the requested resource was in use"
Andy.
"kishore" <anonymous@.discussions.microsoft.com> wrote in message
news:10d201c48bd5$fa04a5c0$a301280a@.phx.gbl...
> I am running a job every night. It runs fine until last
> saturday. In job we are executing 25 stored procedures.
> We are getting error after running 12 procedures and
> gives error -- "Line 1: Incorrect syntax near '>'.
> [SQLSTATE 42000] (Error 170). The step failed". Actually
> There is no syntax error. When I checked error log it
> shows -- "Operating system error 170., Line 1: Incorrect
> syntax near '>'.2004-08-23 20:33:07.27 logon Login
> succeeded for user 'US\dashbrd'. Connection: Trusted.
> Error encountered while executing xp_sendmail @.query..
> Error: 17968, Severity: 15, State: 1 ".
> We are running job again starting with stored procedure
> 12. It is running fine. I don't understand why it
> happens? Can any one help me|||In error it shows error occured during xp_Sendmail, but
we are not sending any message at that time. Why it
looking for xp_sendmail?In stored procedure we are
updating temp table and deleting temp table after
inserting data into original table. Is while deleting
temp table causes this problem?
>--Original Message--
>little tip , when you Operating System Error x , type
NET HELPMSG x to see
>what it corresponds to , sometimes a valuable clue to
whats going on
>ie NET HELPMSG 170 gives you "the requested resource was
in use"
>Andy.
>"kishore" <anonymous@.discussions.microsoft.com> wrote in
message
>news:10d201c48bd5$fa04a5c0$a301280a@.phx.gbl...
Actually[vbcol=seagreen]
Incorrect[vbcol=seagreen]
>
>.
>|||check to see if there are any triggers on the tables being updated.
Andy.
"kishore" <anonymous@.discussions.microsoft.com> wrote in message
news:09cd01c48c3b$01e37720$a401280a@.phx.gbl...[vbcol=seagreen]
> In error it shows error occured during xp_Sendmail, but
> we are not sending any message at that time. Why it
> looking for xp_sendmail?In stored procedure we are
> updating temp table and deleting temp table after
> inserting data into original table. Is while deleting
> temp table causes this problem?
> NET HELPMSG x to see
> whats going on
> in use"
> message
> Actually
> Incorrect|||No triggers are firing. Up to last week it ran fine.
>--Original Message--
>check to see if there are any triggers on the tables
being updated.
>Andy.
>"kishore" <anonymous@.discussions.microsoft.com> wrote in
message
>news:09cd01c48c3b$01e37720$a401280a@.phx.gbl...
was[vbcol=seagreen]
in[vbcol=seagreen]
last[vbcol=seagreen]
procedures.[vbcol=seagreen]
it[vbcol=seagreen]
Login[vbcol=seagreen]
Trusted.[vbcol=seagreen]
@.query..[vbcol=seagreen]
procedure[vbcol=seagreen]
>
>.
>|||Hi
You may want to try profiling this and see what is being sent to the server.
It sounds as if it could be an unescaped quote type of problem' Is there
any dynamic SQL being used?
John
"kishore" <anonymous@.discussions.microsoft.com> wrote in message
news:1c0f01c48cfb$58107510$a601280a@.phx.gbl...[vbcol=seagreen]
> No triggers are firing. Up to last week it ran fine.
>
> being updated.
> message
> was
> in
> last
> procedures.
> it
> Login
> Trusted.
> @.query..
> procedure|||Hi
I can't really suggest any more except maybe dropping and recreating all the
procedures and the job.
John
"kishore" <anonymous@.discussions.microsoft.com> wrote in message
news:093a01c48ea5$487d3650$a401280a@.phx.gbl...[vbcol=seagreen]
> Created a trace file using profiler. It doesn't help me.
> There is no dynamic sql. In profiler it shows stored
> procedure is completed successfully. After completing the
> stored proc,it sending message as step is failed. Since
> step fails, it doesn't go to the next step.I don't
> understand what is the cause for this error?
>
> sent to the server.
> problem' Is there
> message
> in
> but
> deleting
> type
> to
> resource
> wrote
> until
> and
> near '>'.
> log
saturday. In job we are executing 25 stored procedures.
We are getting error after running 12 procedures and
gives error -- "Line 1: Incorrect syntax near '>'.
[SQLSTATE 42000] (Error 170). The step failed". Actually
There is no syntax error. When I checked error log it
shows -- "Operating system error 170., Line 1: Incorrect
syntax near '>'.2004-08-23 20:33:07.27 logon Login
succeeded for user 'US\dashbrd'. Connection: Trusted.
Error encountered while executing xp_sendmail @.query..
Error: 17968, Severity: 15, State: 1 ".
We are running job again starting with stored procedure
12. It is running fine. I don't understand why it
happens? Can any one help melittle tip , when you Operating System Error x , type NET HELPMSG x to see
what it corresponds to , sometimes a valuable clue to whats going on
ie NET HELPMSG 170 gives you "the requested resource was in use"
Andy.
"kishore" <anonymous@.discussions.microsoft.com> wrote in message
news:10d201c48bd5$fa04a5c0$a301280a@.phx.gbl...
> I am running a job every night. It runs fine until last
> saturday. In job we are executing 25 stored procedures.
> We are getting error after running 12 procedures and
> gives error -- "Line 1: Incorrect syntax near '>'.
> [SQLSTATE 42000] (Error 170). The step failed". Actually
> There is no syntax error. When I checked error log it
> shows -- "Operating system error 170., Line 1: Incorrect
> syntax near '>'.2004-08-23 20:33:07.27 logon Login
> succeeded for user 'US\dashbrd'. Connection: Trusted.
> Error encountered while executing xp_sendmail @.query..
> Error: 17968, Severity: 15, State: 1 ".
> We are running job again starting with stored procedure
> 12. It is running fine. I don't understand why it
> happens? Can any one help me|||In error it shows error occured during xp_Sendmail, but
we are not sending any message at that time. Why it
looking for xp_sendmail?In stored procedure we are
updating temp table and deleting temp table after
inserting data into original table. Is while deleting
temp table causes this problem?
>--Original Message--
>little tip , when you Operating System Error x , type
NET HELPMSG x to see
>what it corresponds to , sometimes a valuable clue to
whats going on
>ie NET HELPMSG 170 gives you "the requested resource was
in use"
>Andy.
>"kishore" <anonymous@.discussions.microsoft.com> wrote in
message
>news:10d201c48bd5$fa04a5c0$a301280a@.phx.gbl...
Actually[vbcol=seagreen]
Incorrect[vbcol=seagreen]
>
>.
>|||check to see if there are any triggers on the tables being updated.
Andy.
"kishore" <anonymous@.discussions.microsoft.com> wrote in message
news:09cd01c48c3b$01e37720$a401280a@.phx.gbl...[vbcol=seagreen]
> In error it shows error occured during xp_Sendmail, but
> we are not sending any message at that time. Why it
> looking for xp_sendmail?In stored procedure we are
> updating temp table and deleting temp table after
> inserting data into original table. Is while deleting
> temp table causes this problem?
> NET HELPMSG x to see
> whats going on
> in use"
> message
> Actually
> Incorrect|||No triggers are firing. Up to last week it ran fine.
>--Original Message--
>check to see if there are any triggers on the tables
being updated.
>Andy.
>"kishore" <anonymous@.discussions.microsoft.com> wrote in
message
>news:09cd01c48c3b$01e37720$a401280a@.phx.gbl...
was[vbcol=seagreen]
in[vbcol=seagreen]
last[vbcol=seagreen]
procedures.[vbcol=seagreen]
it[vbcol=seagreen]
Login[vbcol=seagreen]
Trusted.[vbcol=seagreen]
@.query..[vbcol=seagreen]
procedure[vbcol=seagreen]
>
>.
>|||Hi
You may want to try profiling this and see what is being sent to the server.
It sounds as if it could be an unescaped quote type of problem' Is there
any dynamic SQL being used?
John
"kishore" <anonymous@.discussions.microsoft.com> wrote in message
news:1c0f01c48cfb$58107510$a601280a@.phx.gbl...[vbcol=seagreen]
> No triggers are firing. Up to last week it ran fine.
>
> being updated.
> message
> was
> in
> last
> procedures.
> it
> Login
> Trusted.
> @.query..
> procedure|||Hi
I can't really suggest any more except maybe dropping and recreating all the
procedures and the job.
John
"kishore" <anonymous@.discussions.microsoft.com> wrote in message
news:093a01c48ea5$487d3650$a401280a@.phx.gbl...[vbcol=seagreen]
> Created a trace file using profiler. It doesn't help me.
> There is no dynamic sql. In profiler it shows stored
> procedure is completed successfully. After completing the
> stored proc,it sending message as step is failed. Since
> step fails, it doesn't go to the next step.I don't
> understand what is the cause for this error?
>
> sent to the server.
> problem' Is there
> message
> in
> but
> deleting
> type
> to
> resource
> wrote
> until
> and
> near '>'.
> log
Error: 17968, Severity: 15, State: 1
I am running a job every night. It runs fine until last
saturday. In job we are executing 25 stored procedures.
We are getting error after running 12 procedures and
gives error -- "Line 1: Incorrect syntax near '>'.
[SQLSTATE 42000] (Error 170). The step failed". Actually
There is no syntax error. When I checked error log it
shows -- "Operating system error 170., Line 1: Incorrect
syntax near '>'.2004-08-23 20:33:07.27 logon Login
succeeded for user 'US\dashbrd'. Connection: Trusted.
Error encountered while executing xp_sendmail @.query..
Error: 17968, Severity: 15, State: 1 ".
We are running job again starting with stored procedure
12. It is running fine. I don't understand why it
happens? Can any one help melittle tip , when you Operating System Error x , type NET HELPMSG x to see
what it corresponds to , sometimes a valuable clue to whats going on
ie NET HELPMSG 170 gives you "the requested resource was in use"
Andy.
"kishore" <anonymous@.discussions.microsoft.com> wrote in message
news:10d201c48bd5$fa04a5c0$a301280a@.phx.gbl...
> I am running a job every night. It runs fine until last
> saturday. In job we are executing 25 stored procedures.
> We are getting error after running 12 procedures and
> gives error -- "Line 1: Incorrect syntax near '>'.
> [SQLSTATE 42000] (Error 170). The step failed". Actually
> There is no syntax error. When I checked error log it
> shows -- "Operating system error 170., Line 1: Incorrect
> syntax near '>'.2004-08-23 20:33:07.27 logon Login
> succeeded for user 'US\dashbrd'. Connection: Trusted.
> Error encountered while executing xp_sendmail @.query..
> Error: 17968, Severity: 15, State: 1 ".
> We are running job again starting with stored procedure
> 12. It is running fine. I don't understand why it
> happens? Can any one help me|||In error it shows error occured during xp_Sendmail, but
we are not sending any message at that time. Why it
looking for xp_sendmail?In stored procedure we are
updating temp table and deleting temp table after
inserting data into original table. Is while deleting
temp table causes this problem?
>--Original Message--
>little tip , when you Operating System Error x , type
NET HELPMSG x to see
>what it corresponds to , sometimes a valuable clue to
whats going on
>ie NET HELPMSG 170 gives you "the requested resource was
in use"
>Andy.
>"kishore" <anonymous@.discussions.microsoft.com> wrote in
message
>news:10d201c48bd5$fa04a5c0$a301280a@.phx.gbl...
>> I am running a job every night. It runs fine until last
>> saturday. In job we are executing 25 stored procedures.
>> We are getting error after running 12 procedures and
>> gives error -- "Line 1: Incorrect syntax near '>'.
>> [SQLSTATE 42000] (Error 170). The step failed".
Actually
>> There is no syntax error. When I checked error log it
>> shows -- "Operating system error 170., Line 1:
Incorrect
>> syntax near '>'.2004-08-23 20:33:07.27 logon Login
>> succeeded for user 'US\dashbrd'. Connection: Trusted.
>> Error encountered while executing xp_sendmail @.query..
>> Error: 17968, Severity: 15, State: 1 ".
>> We are running job again starting with stored procedure
>> 12. It is running fine. I don't understand why it
>> happens? Can any one help me
>
>.
>|||check to see if there are any triggers on the tables being updated.
Andy.
"kishore" <anonymous@.discussions.microsoft.com> wrote in message
news:09cd01c48c3b$01e37720$a401280a@.phx.gbl...
> In error it shows error occured during xp_Sendmail, but
> we are not sending any message at that time. Why it
> looking for xp_sendmail?In stored procedure we are
> updating temp table and deleting temp table after
> inserting data into original table. Is while deleting
> temp table causes this problem?
> >--Original Message--
> >little tip , when you Operating System Error x , type
> NET HELPMSG x to see
> >what it corresponds to , sometimes a valuable clue to
> whats going on
> >
> >ie NET HELPMSG 170 gives you "the requested resource was
> in use"
> >
> >Andy.
> >"kishore" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:10d201c48bd5$fa04a5c0$a301280a@.phx.gbl...
> >> I am running a job every night. It runs fine until last
> >> saturday. In job we are executing 25 stored procedures.
> >> We are getting error after running 12 procedures and
> >> gives error -- "Line 1: Incorrect syntax near '>'.
> >> [SQLSTATE 42000] (Error 170). The step failed".
> Actually
> >> There is no syntax error. When I checked error log it
> >> shows -- "Operating system error 170., Line 1:
> Incorrect
> >> syntax near '>'.2004-08-23 20:33:07.27 logon Login
> >> succeeded for user 'US\dashbrd'. Connection: Trusted.
> >>
> >> Error encountered while executing xp_sendmail @.query..
> >>
> >> Error: 17968, Severity: 15, State: 1 ".
> >>
> >> We are running job again starting with stored procedure
> >> 12. It is running fine. I don't understand why it
> >> happens? Can any one help me
> >
> >
> >.
> >|||No triggers are firing. Up to last week it ran fine.
>--Original Message--
>check to see if there are any triggers on the tables
being updated.
>Andy.
>"kishore" <anonymous@.discussions.microsoft.com> wrote in
message
>news:09cd01c48c3b$01e37720$a401280a@.phx.gbl...
>> In error it shows error occured during xp_Sendmail, but
>> we are not sending any message at that time. Why it
>> looking for xp_sendmail?In stored procedure we are
>> updating temp table and deleting temp table after
>> inserting data into original table. Is while deleting
>> temp table causes this problem?
>> >--Original Message--
>> >little tip , when you Operating System Error x , type
>> NET HELPMSG x to see
>> >what it corresponds to , sometimes a valuable clue to
>> whats going on
>> >
>> >ie NET HELPMSG 170 gives you "the requested resource
was
>> in use"
>> >
>> >Andy.
>> >"kishore" <anonymous@.discussions.microsoft.com> wrote
in
>> message
>> >news:10d201c48bd5$fa04a5c0$a301280a@.phx.gbl...
>> >> I am running a job every night. It runs fine until
last
>> >> saturday. In job we are executing 25 stored
procedures.
>> >> We are getting error after running 12 procedures and
>> >> gives error -- "Line 1: Incorrect syntax near '>'.
>> >> [SQLSTATE 42000] (Error 170). The step failed".
>> Actually
>> >> There is no syntax error. When I checked error log
it
>> >> shows -- "Operating system error 170., Line 1:
>> Incorrect
>> >> syntax near '>'.2004-08-23 20:33:07.27 logon
Login
>> >> succeeded for user 'US\dashbrd'. Connection:
Trusted.
>> >>
>> >> Error encountered while executing xp_sendmail
@.query..
>> >>
>> >> Error: 17968, Severity: 15, State: 1 ".
>> >>
>> >> We are running job again starting with stored
procedure
>> >> 12. It is running fine. I don't understand why it
>> >> happens? Can any one help me
>> >
>> >
>> >.
>> >
>
>.
>|||Hi
You may want to try profiling this and see what is being sent to the server.
It sounds as if it could be an unescaped quote type of problem' Is there
any dynamic SQL being used?
John
"kishore" <anonymous@.discussions.microsoft.com> wrote in message
news:1c0f01c48cfb$58107510$a601280a@.phx.gbl...
> No triggers are firing. Up to last week it ran fine.
>
> >--Original Message--
> >check to see if there are any triggers on the tables
> being updated.
> >
> >Andy.
> >"kishore" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:09cd01c48c3b$01e37720$a401280a@.phx.gbl...
> >> In error it shows error occured during xp_Sendmail, but
> >> we are not sending any message at that time. Why it
> >> looking for xp_sendmail?In stored procedure we are
> >> updating temp table and deleting temp table after
> >> inserting data into original table. Is while deleting
> >> temp table causes this problem?
> >> >--Original Message--
> >> >little tip , when you Operating System Error x , type
> >> NET HELPMSG x to see
> >> >what it corresponds to , sometimes a valuable clue to
> >> whats going on
> >> >
> >> >ie NET HELPMSG 170 gives you "the requested resource
> was
> >> in use"
> >> >
> >> >Andy.
> >> >"kishore" <anonymous@.discussions.microsoft.com> wrote
> in
> >> message
> >> >news:10d201c48bd5$fa04a5c0$a301280a@.phx.gbl...
> >> >> I am running a job every night. It runs fine until
> last
> >> >> saturday. In job we are executing 25 stored
> procedures.
> >> >> We are getting error after running 12 procedures and
> >> >> gives error -- "Line 1: Incorrect syntax near '>'.
> >> >> [SQLSTATE 42000] (Error 170). The step failed".
> >> Actually
> >> >> There is no syntax error. When I checked error log
> it
> >> >> shows -- "Operating system error 170., Line 1:
> >> Incorrect
> >> >> syntax near '>'.2004-08-23 20:33:07.27 logon
> Login
> >> >> succeeded for user 'US\dashbrd'. Connection:
> Trusted.
> >> >>
> >> >> Error encountered while executing xp_sendmail
> @.query..
> >> >>
> >> >> Error: 17968, Severity: 15, State: 1 ".
> >> >>
> >> >> We are running job again starting with stored
> procedure
> >> >> 12. It is running fine. I don't understand why it
> >> >> happens? Can any one help me
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >|||Created a trace file using profiler. It doesn't help me.
There is no dynamic sql. In profiler it shows stored
procedure is completed successfully. After completing the
stored proc,it sending message as step is failed. Since
step fails, it doesn't go to the next step.I don't
understand what is the cause for this error?
>--Original Message--
>Hi
>You may want to try profiling this and see what is being
sent to the server.
>It sounds as if it could be an unescaped quote type of
problem' Is there
>any dynamic SQL being used?
>John
>"kishore" <anonymous@.discussions.microsoft.com> wrote in
message
>news:1c0f01c48cfb$58107510$a601280a@.phx.gbl...
>> No triggers are firing. Up to last week it ran fine.
>>
>> >--Original Message--
>> >check to see if there are any triggers on the tables
>> being updated.
>> >
>> >Andy.
>> >"kishore" <anonymous@.discussions.microsoft.com> wrote
in
>> message
>> >news:09cd01c48c3b$01e37720$a401280a@.phx.gbl...
>> >> In error it shows error occured during xp_Sendmail,
but
>> >> we are not sending any message at that time. Why it
>> >> looking for xp_sendmail?In stored procedure we are
>> >> updating temp table and deleting temp table after
>> >> inserting data into original table. Is while
deleting
>> >> temp table causes this problem?
>> >> >--Original Message--
>> >> >little tip , when you Operating System Error x ,
type
>> >> NET HELPMSG x to see
>> >> >what it corresponds to , sometimes a valuable clue
to
>> >> whats going on
>> >> >
>> >> >ie NET HELPMSG 170 gives you "the requested
resource
>> was
>> >> in use"
>> >> >
>> >> >Andy.
>> >> >"kishore" <anonymous@.discussions.microsoft.com>
wrote
>> in
>> >> message
>> >> >news:10d201c48bd5$fa04a5c0$a301280a@.phx.gbl...
>> >> >> I am running a job every night. It runs fine
until
>> last
>> >> >> saturday. In job we are executing 25 stored
>> procedures.
>> >> >> We are getting error after running 12 procedures
and
>> >> >> gives error -- "Line 1: Incorrect syntax
near '>'.
>> >> >> [SQLSTATE 42000] (Error 170). The step failed".
>> >> Actually
>> >> >> There is no syntax error. When I checked error
log
>> it
>> >> >> shows -- "Operating system error 170., Line 1:
>> >> Incorrect
>> >> >> syntax near '>'.2004-08-23 20:33:07.27 logon
>> Login
>> >> >> succeeded for user 'US\dashbrd'. Connection:
>> Trusted.
>> >> >>
>> >> >> Error encountered while executing xp_sendmail
>> @.query..
>> >> >>
>> >> >> Error: 17968, Severity: 15, State: 1 ".
>> >> >>
>> >> >> We are running job again starting with stored
>> procedure
>> >> >> 12. It is running fine. I don't understand why it
>> >> >> happens? Can any one help me
>> >> >
>> >> >
>> >> >.
>> >> >
>> >
>> >
>> >.
>> >
>
>.
>|||Hi
I can't really suggest any more except maybe dropping and recreating all the
procedures and the job.
John
"kishore" <anonymous@.discussions.microsoft.com> wrote in message
news:093a01c48ea5$487d3650$a401280a@.phx.gbl...
> Created a trace file using profiler. It doesn't help me.
> There is no dynamic sql. In profiler it shows stored
> procedure is completed successfully. After completing the
> stored proc,it sending message as step is failed. Since
> step fails, it doesn't go to the next step.I don't
> understand what is the cause for this error?
>
> >--Original Message--
> >Hi
> >
> >You may want to try profiling this and see what is being
> sent to the server.
> >It sounds as if it could be an unescaped quote type of
> problem' Is there
> >any dynamic SQL being used?
> >
> >John
> >
> >"kishore" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:1c0f01c48cfb$58107510$a601280a@.phx.gbl...
> >> No triggers are firing. Up to last week it ran fine.
> >>
> >>
> >> >--Original Message--
> >> >check to see if there are any triggers on the tables
> >> being updated.
> >> >
> >> >Andy.
> >> >"kishore" <anonymous@.discussions.microsoft.com> wrote
> in
> >> message
> >> >news:09cd01c48c3b$01e37720$a401280a@.phx.gbl...
> >> >> In error it shows error occured during xp_Sendmail,
> but
> >> >> we are not sending any message at that time. Why it
> >> >> looking for xp_sendmail?In stored procedure we are
> >> >> updating temp table and deleting temp table after
> >> >> inserting data into original table. Is while
> deleting
> >> >> temp table causes this problem?
> >> >> >--Original Message--
> >> >> >little tip , when you Operating System Error x ,
> type
> >> >> NET HELPMSG x to see
> >> >> >what it corresponds to , sometimes a valuable clue
> to
> >> >> whats going on
> >> >> >
> >> >> >ie NET HELPMSG 170 gives you "the requested
> resource
> >> was
> >> >> in use"
> >> >> >
> >> >> >Andy.
> >> >> >"kishore" <anonymous@.discussions.microsoft.com>
> wrote
> >> in
> >> >> message
> >> >> >news:10d201c48bd5$fa04a5c0$a301280a@.phx.gbl...
> >> >> >> I am running a job every night. It runs fine
> until
> >> last
> >> >> >> saturday. In job we are executing 25 stored
> >> procedures.
> >> >> >> We are getting error after running 12 procedures
> and
> >> >> >> gives error -- "Line 1: Incorrect syntax
> near '>'.
> >> >> >> [SQLSTATE 42000] (Error 170). The step failed".
> >> >> Actually
> >> >> >> There is no syntax error. When I checked error
> log
> >> it
> >> >> >> shows -- "Operating system error 170., Line 1:
> >> >> Incorrect
> >> >> >> syntax near '>'.2004-08-23 20:33:07.27 logon
> >> Login
> >> >> >> succeeded for user 'US\dashbrd'. Connection:
> >> Trusted.
> >> >> >>
> >> >> >> Error encountered while executing xp_sendmail
> >> @.query..
> >> >> >>
> >> >> >> Error: 17968, Severity: 15, State: 1 ".
> >> >> >>
> >> >> >> We are running job again starting with stored
> >> procedure
> >> >> >> 12. It is running fine. I don't understand why it
> >> >> >> happens? Can any one help me
> >> >> >
> >> >> >
> >> >> >.
> >> >> >
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >
saturday. In job we are executing 25 stored procedures.
We are getting error after running 12 procedures and
gives error -- "Line 1: Incorrect syntax near '>'.
[SQLSTATE 42000] (Error 170). The step failed". Actually
There is no syntax error. When I checked error log it
shows -- "Operating system error 170., Line 1: Incorrect
syntax near '>'.2004-08-23 20:33:07.27 logon Login
succeeded for user 'US\dashbrd'. Connection: Trusted.
Error encountered while executing xp_sendmail @.query..
Error: 17968, Severity: 15, State: 1 ".
We are running job again starting with stored procedure
12. It is running fine. I don't understand why it
happens? Can any one help melittle tip , when you Operating System Error x , type NET HELPMSG x to see
what it corresponds to , sometimes a valuable clue to whats going on
ie NET HELPMSG 170 gives you "the requested resource was in use"
Andy.
"kishore" <anonymous@.discussions.microsoft.com> wrote in message
news:10d201c48bd5$fa04a5c0$a301280a@.phx.gbl...
> I am running a job every night. It runs fine until last
> saturday. In job we are executing 25 stored procedures.
> We are getting error after running 12 procedures and
> gives error -- "Line 1: Incorrect syntax near '>'.
> [SQLSTATE 42000] (Error 170). The step failed". Actually
> There is no syntax error. When I checked error log it
> shows -- "Operating system error 170., Line 1: Incorrect
> syntax near '>'.2004-08-23 20:33:07.27 logon Login
> succeeded for user 'US\dashbrd'. Connection: Trusted.
> Error encountered while executing xp_sendmail @.query..
> Error: 17968, Severity: 15, State: 1 ".
> We are running job again starting with stored procedure
> 12. It is running fine. I don't understand why it
> happens? Can any one help me|||In error it shows error occured during xp_Sendmail, but
we are not sending any message at that time. Why it
looking for xp_sendmail?In stored procedure we are
updating temp table and deleting temp table after
inserting data into original table. Is while deleting
temp table causes this problem?
>--Original Message--
>little tip , when you Operating System Error x , type
NET HELPMSG x to see
>what it corresponds to , sometimes a valuable clue to
whats going on
>ie NET HELPMSG 170 gives you "the requested resource was
in use"
>Andy.
>"kishore" <anonymous@.discussions.microsoft.com> wrote in
message
>news:10d201c48bd5$fa04a5c0$a301280a@.phx.gbl...
>> I am running a job every night. It runs fine until last
>> saturday. In job we are executing 25 stored procedures.
>> We are getting error after running 12 procedures and
>> gives error -- "Line 1: Incorrect syntax near '>'.
>> [SQLSTATE 42000] (Error 170). The step failed".
Actually
>> There is no syntax error. When I checked error log it
>> shows -- "Operating system error 170., Line 1:
Incorrect
>> syntax near '>'.2004-08-23 20:33:07.27 logon Login
>> succeeded for user 'US\dashbrd'. Connection: Trusted.
>> Error encountered while executing xp_sendmail @.query..
>> Error: 17968, Severity: 15, State: 1 ".
>> We are running job again starting with stored procedure
>> 12. It is running fine. I don't understand why it
>> happens? Can any one help me
>
>.
>|||check to see if there are any triggers on the tables being updated.
Andy.
"kishore" <anonymous@.discussions.microsoft.com> wrote in message
news:09cd01c48c3b$01e37720$a401280a@.phx.gbl...
> In error it shows error occured during xp_Sendmail, but
> we are not sending any message at that time. Why it
> looking for xp_sendmail?In stored procedure we are
> updating temp table and deleting temp table after
> inserting data into original table. Is while deleting
> temp table causes this problem?
> >--Original Message--
> >little tip , when you Operating System Error x , type
> NET HELPMSG x to see
> >what it corresponds to , sometimes a valuable clue to
> whats going on
> >
> >ie NET HELPMSG 170 gives you "the requested resource was
> in use"
> >
> >Andy.
> >"kishore" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:10d201c48bd5$fa04a5c0$a301280a@.phx.gbl...
> >> I am running a job every night. It runs fine until last
> >> saturday. In job we are executing 25 stored procedures.
> >> We are getting error after running 12 procedures and
> >> gives error -- "Line 1: Incorrect syntax near '>'.
> >> [SQLSTATE 42000] (Error 170). The step failed".
> Actually
> >> There is no syntax error. When I checked error log it
> >> shows -- "Operating system error 170., Line 1:
> Incorrect
> >> syntax near '>'.2004-08-23 20:33:07.27 logon Login
> >> succeeded for user 'US\dashbrd'. Connection: Trusted.
> >>
> >> Error encountered while executing xp_sendmail @.query..
> >>
> >> Error: 17968, Severity: 15, State: 1 ".
> >>
> >> We are running job again starting with stored procedure
> >> 12. It is running fine. I don't understand why it
> >> happens? Can any one help me
> >
> >
> >.
> >|||No triggers are firing. Up to last week it ran fine.
>--Original Message--
>check to see if there are any triggers on the tables
being updated.
>Andy.
>"kishore" <anonymous@.discussions.microsoft.com> wrote in
message
>news:09cd01c48c3b$01e37720$a401280a@.phx.gbl...
>> In error it shows error occured during xp_Sendmail, but
>> we are not sending any message at that time. Why it
>> looking for xp_sendmail?In stored procedure we are
>> updating temp table and deleting temp table after
>> inserting data into original table. Is while deleting
>> temp table causes this problem?
>> >--Original Message--
>> >little tip , when you Operating System Error x , type
>> NET HELPMSG x to see
>> >what it corresponds to , sometimes a valuable clue to
>> whats going on
>> >
>> >ie NET HELPMSG 170 gives you "the requested resource
was
>> in use"
>> >
>> >Andy.
>> >"kishore" <anonymous@.discussions.microsoft.com> wrote
in
>> message
>> >news:10d201c48bd5$fa04a5c0$a301280a@.phx.gbl...
>> >> I am running a job every night. It runs fine until
last
>> >> saturday. In job we are executing 25 stored
procedures.
>> >> We are getting error after running 12 procedures and
>> >> gives error -- "Line 1: Incorrect syntax near '>'.
>> >> [SQLSTATE 42000] (Error 170). The step failed".
>> Actually
>> >> There is no syntax error. When I checked error log
it
>> >> shows -- "Operating system error 170., Line 1:
>> Incorrect
>> >> syntax near '>'.2004-08-23 20:33:07.27 logon
Login
>> >> succeeded for user 'US\dashbrd'. Connection:
Trusted.
>> >>
>> >> Error encountered while executing xp_sendmail
@.query..
>> >>
>> >> Error: 17968, Severity: 15, State: 1 ".
>> >>
>> >> We are running job again starting with stored
procedure
>> >> 12. It is running fine. I don't understand why it
>> >> happens? Can any one help me
>> >
>> >
>> >.
>> >
>
>.
>|||Hi
You may want to try profiling this and see what is being sent to the server.
It sounds as if it could be an unescaped quote type of problem' Is there
any dynamic SQL being used?
John
"kishore" <anonymous@.discussions.microsoft.com> wrote in message
news:1c0f01c48cfb$58107510$a601280a@.phx.gbl...
> No triggers are firing. Up to last week it ran fine.
>
> >--Original Message--
> >check to see if there are any triggers on the tables
> being updated.
> >
> >Andy.
> >"kishore" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:09cd01c48c3b$01e37720$a401280a@.phx.gbl...
> >> In error it shows error occured during xp_Sendmail, but
> >> we are not sending any message at that time. Why it
> >> looking for xp_sendmail?In stored procedure we are
> >> updating temp table and deleting temp table after
> >> inserting data into original table. Is while deleting
> >> temp table causes this problem?
> >> >--Original Message--
> >> >little tip , when you Operating System Error x , type
> >> NET HELPMSG x to see
> >> >what it corresponds to , sometimes a valuable clue to
> >> whats going on
> >> >
> >> >ie NET HELPMSG 170 gives you "the requested resource
> was
> >> in use"
> >> >
> >> >Andy.
> >> >"kishore" <anonymous@.discussions.microsoft.com> wrote
> in
> >> message
> >> >news:10d201c48bd5$fa04a5c0$a301280a@.phx.gbl...
> >> >> I am running a job every night. It runs fine until
> last
> >> >> saturday. In job we are executing 25 stored
> procedures.
> >> >> We are getting error after running 12 procedures and
> >> >> gives error -- "Line 1: Incorrect syntax near '>'.
> >> >> [SQLSTATE 42000] (Error 170). The step failed".
> >> Actually
> >> >> There is no syntax error. When I checked error log
> it
> >> >> shows -- "Operating system error 170., Line 1:
> >> Incorrect
> >> >> syntax near '>'.2004-08-23 20:33:07.27 logon
> Login
> >> >> succeeded for user 'US\dashbrd'. Connection:
> Trusted.
> >> >>
> >> >> Error encountered while executing xp_sendmail
> @.query..
> >> >>
> >> >> Error: 17968, Severity: 15, State: 1 ".
> >> >>
> >> >> We are running job again starting with stored
> procedure
> >> >> 12. It is running fine. I don't understand why it
> >> >> happens? Can any one help me
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >|||Created a trace file using profiler. It doesn't help me.
There is no dynamic sql. In profiler it shows stored
procedure is completed successfully. After completing the
stored proc,it sending message as step is failed. Since
step fails, it doesn't go to the next step.I don't
understand what is the cause for this error?
>--Original Message--
>Hi
>You may want to try profiling this and see what is being
sent to the server.
>It sounds as if it could be an unescaped quote type of
problem' Is there
>any dynamic SQL being used?
>John
>"kishore" <anonymous@.discussions.microsoft.com> wrote in
message
>news:1c0f01c48cfb$58107510$a601280a@.phx.gbl...
>> No triggers are firing. Up to last week it ran fine.
>>
>> >--Original Message--
>> >check to see if there are any triggers on the tables
>> being updated.
>> >
>> >Andy.
>> >"kishore" <anonymous@.discussions.microsoft.com> wrote
in
>> message
>> >news:09cd01c48c3b$01e37720$a401280a@.phx.gbl...
>> >> In error it shows error occured during xp_Sendmail,
but
>> >> we are not sending any message at that time. Why it
>> >> looking for xp_sendmail?In stored procedure we are
>> >> updating temp table and deleting temp table after
>> >> inserting data into original table. Is while
deleting
>> >> temp table causes this problem?
>> >> >--Original Message--
>> >> >little tip , when you Operating System Error x ,
type
>> >> NET HELPMSG x to see
>> >> >what it corresponds to , sometimes a valuable clue
to
>> >> whats going on
>> >> >
>> >> >ie NET HELPMSG 170 gives you "the requested
resource
>> was
>> >> in use"
>> >> >
>> >> >Andy.
>> >> >"kishore" <anonymous@.discussions.microsoft.com>
wrote
>> in
>> >> message
>> >> >news:10d201c48bd5$fa04a5c0$a301280a@.phx.gbl...
>> >> >> I am running a job every night. It runs fine
until
>> last
>> >> >> saturday. In job we are executing 25 stored
>> procedures.
>> >> >> We are getting error after running 12 procedures
and
>> >> >> gives error -- "Line 1: Incorrect syntax
near '>'.
>> >> >> [SQLSTATE 42000] (Error 170). The step failed".
>> >> Actually
>> >> >> There is no syntax error. When I checked error
log
>> it
>> >> >> shows -- "Operating system error 170., Line 1:
>> >> Incorrect
>> >> >> syntax near '>'.2004-08-23 20:33:07.27 logon
>> Login
>> >> >> succeeded for user 'US\dashbrd'. Connection:
>> Trusted.
>> >> >>
>> >> >> Error encountered while executing xp_sendmail
>> @.query..
>> >> >>
>> >> >> Error: 17968, Severity: 15, State: 1 ".
>> >> >>
>> >> >> We are running job again starting with stored
>> procedure
>> >> >> 12. It is running fine. I don't understand why it
>> >> >> happens? Can any one help me
>> >> >
>> >> >
>> >> >.
>> >> >
>> >
>> >
>> >.
>> >
>
>.
>|||Hi
I can't really suggest any more except maybe dropping and recreating all the
procedures and the job.
John
"kishore" <anonymous@.discussions.microsoft.com> wrote in message
news:093a01c48ea5$487d3650$a401280a@.phx.gbl...
> Created a trace file using profiler. It doesn't help me.
> There is no dynamic sql. In profiler it shows stored
> procedure is completed successfully. After completing the
> stored proc,it sending message as step is failed. Since
> step fails, it doesn't go to the next step.I don't
> understand what is the cause for this error?
>
> >--Original Message--
> >Hi
> >
> >You may want to try profiling this and see what is being
> sent to the server.
> >It sounds as if it could be an unescaped quote type of
> problem' Is there
> >any dynamic SQL being used?
> >
> >John
> >
> >"kishore" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:1c0f01c48cfb$58107510$a601280a@.phx.gbl...
> >> No triggers are firing. Up to last week it ran fine.
> >>
> >>
> >> >--Original Message--
> >> >check to see if there are any triggers on the tables
> >> being updated.
> >> >
> >> >Andy.
> >> >"kishore" <anonymous@.discussions.microsoft.com> wrote
> in
> >> message
> >> >news:09cd01c48c3b$01e37720$a401280a@.phx.gbl...
> >> >> In error it shows error occured during xp_Sendmail,
> but
> >> >> we are not sending any message at that time. Why it
> >> >> looking for xp_sendmail?In stored procedure we are
> >> >> updating temp table and deleting temp table after
> >> >> inserting data into original table. Is while
> deleting
> >> >> temp table causes this problem?
> >> >> >--Original Message--
> >> >> >little tip , when you Operating System Error x ,
> type
> >> >> NET HELPMSG x to see
> >> >> >what it corresponds to , sometimes a valuable clue
> to
> >> >> whats going on
> >> >> >
> >> >> >ie NET HELPMSG 170 gives you "the requested
> resource
> >> was
> >> >> in use"
> >> >> >
> >> >> >Andy.
> >> >> >"kishore" <anonymous@.discussions.microsoft.com>
> wrote
> >> in
> >> >> message
> >> >> >news:10d201c48bd5$fa04a5c0$a301280a@.phx.gbl...
> >> >> >> I am running a job every night. It runs fine
> until
> >> last
> >> >> >> saturday. In job we are executing 25 stored
> >> procedures.
> >> >> >> We are getting error after running 12 procedures
> and
> >> >> >> gives error -- "Line 1: Incorrect syntax
> near '>'.
> >> >> >> [SQLSTATE 42000] (Error 170). The step failed".
> >> >> Actually
> >> >> >> There is no syntax error. When I checked error
> log
> >> it
> >> >> >> shows -- "Operating system error 170., Line 1:
> >> >> Incorrect
> >> >> >> syntax near '>'.2004-08-23 20:33:07.27 logon
> >> Login
> >> >> >> succeeded for user 'US\dashbrd'. Connection:
> >> Trusted.
> >> >> >>
> >> >> >> Error encountered while executing xp_sendmail
> >> @.query..
> >> >> >>
> >> >> >> Error: 17968, Severity: 15, State: 1 ".
> >> >> >>
> >> >> >> We are running job again starting with stored
> >> procedure
> >> >> >> 12. It is running fine. I don't understand why it
> >> >> >> happens? Can any one help me
> >> >> >
> >> >> >
> >> >> >.
> >> >> >
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >
Error: 17968, Severity: 15, State: 1
I am running a job every night. It runs fine until last
saturday. In job we are executing 25 stored procedures.
We are getting error after running 12 procedures and
gives error -- "Line 1: Incorrect syntax near '>'.
[SQLSTATE 42000] (Error 170). The step failed". Actually
There is no syntax error. When I checked error log it
shows -- "Operating system error 170., Line 1: Incorrect
syntax near '>'.2004-08-23 20:33:07.27 logon Login
succeeded for user 'US\dashbrd'. Connection: Trusted.
Error encountered while executing xp_sendmail @.query..
Error: 17968, Severity: 15, State: 1 ".
We are running job again starting with stored procedure
12. It is running fine. I don't understand why it
happens? Can any one help me
little tip , when you Operating System Error x , type NET HELPMSG x to see
what it corresponds to , sometimes a valuable clue to whats going on
ie NET HELPMSG 170 gives you "the requested resource was in use"
Andy.
"kishore" <anonymous@.discussions.microsoft.com> wrote in message
news:10d201c48bd5$fa04a5c0$a301280a@.phx.gbl...
> I am running a job every night. It runs fine until last
> saturday. In job we are executing 25 stored procedures.
> We are getting error after running 12 procedures and
> gives error -- "Line 1: Incorrect syntax near '>'.
> [SQLSTATE 42000] (Error 170). The step failed". Actually
> There is no syntax error. When I checked error log it
> shows -- "Operating system error 170., Line 1: Incorrect
> syntax near '>'.2004-08-23 20:33:07.27 logon Login
> succeeded for user 'US\dashbrd'. Connection: Trusted.
> Error encountered while executing xp_sendmail @.query..
> Error: 17968, Severity: 15, State: 1 ".
> We are running job again starting with stored procedure
> 12. It is running fine. I don't understand why it
> happens? Can any one help me
|||In error it shows error occured during xp_Sendmail, but
we are not sending any message at that time. Why it
looking for xp_sendmail?In stored procedure we are
updating temp table and deleting temp table after
inserting data into original table. Is while deleting
temp table causes this problem?
>--Original Message--
>little tip , when you Operating System Error x , type
NET HELPMSG x to see
>what it corresponds to , sometimes a valuable clue to
whats going on
>ie NET HELPMSG 170 gives you "the requested resource was
in use"
>Andy.
>"kishore" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:10d201c48bd5$fa04a5c0$a301280a@.phx.gbl...
Actually[vbcol=seagreen]
Incorrect
>
>.
>
|||check to see if there are any triggers on the tables being updated.
Andy.
"kishore" <anonymous@.discussions.microsoft.com> wrote in message
news:09cd01c48c3b$01e37720$a401280a@.phx.gbl...[vbcol=seagreen]
> In error it shows error occured during xp_Sendmail, but
> we are not sending any message at that time. Why it
> looking for xp_sendmail?In stored procedure we are
> updating temp table and deleting temp table after
> inserting data into original table. Is while deleting
> temp table causes this problem?
> NET HELPMSG x to see
> whats going on
> in use"
> message
> Actually
> Incorrect
|||No triggers are firing. Up to last week it ran fine.
>--Original Message--
>check to see if there are any triggers on the tables
being updated.
>Andy.
>"kishore" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:09cd01c48c3b$01e37720$a401280a@.phx.gbl...
was[vbcol=seagreen]
in[vbcol=seagreen]
last[vbcol=seagreen]
procedures.[vbcol=seagreen]
it[vbcol=seagreen]
Login[vbcol=seagreen]
Trusted.[vbcol=seagreen]
@.query..[vbcol=seagreen]
procedure
>
>.
>
|||Hi
You may want to try profiling this and see what is being sent to the server.
It sounds as if it could be an unescaped quote type of problem? Is there
any dynamic SQL being used?
John
"kishore" <anonymous@.discussions.microsoft.com> wrote in message
news:1c0f01c48cfb$58107510$a601280a@.phx.gbl...[vbcol=seagreen]
> No triggers are firing. Up to last week it ran fine.
>
> being updated.
> message
> was
> in
> last
> procedures.
> it
> Login
> Trusted.
> @.query..
> procedure
|||Hi
I can't really suggest any more except maybe dropping and recreating all the
procedures and the job.
John
"kishore" <anonymous@.discussions.microsoft.com> wrote in message
news:093a01c48ea5$487d3650$a401280a@.phx.gbl...[vbcol=seagreen]
> Created a trace file using profiler. It doesn't help me.
> There is no dynamic sql. In profiler it shows stored
> procedure is completed successfully. After completing the
> stored proc,it sending message as step is failed. Since
> step fails, it doesn't go to the next step.I don't
> understand what is the cause for this error?
>
> sent to the server.
> problem? Is there
> message
> in
> but
> deleting
> type
> to
> resource
> wrote
> until
> and
> near '>'.
> log
saturday. In job we are executing 25 stored procedures.
We are getting error after running 12 procedures and
gives error -- "Line 1: Incorrect syntax near '>'.
[SQLSTATE 42000] (Error 170). The step failed". Actually
There is no syntax error. When I checked error log it
shows -- "Operating system error 170., Line 1: Incorrect
syntax near '>'.2004-08-23 20:33:07.27 logon Login
succeeded for user 'US\dashbrd'. Connection: Trusted.
Error encountered while executing xp_sendmail @.query..
Error: 17968, Severity: 15, State: 1 ".
We are running job again starting with stored procedure
12. It is running fine. I don't understand why it
happens? Can any one help me
little tip , when you Operating System Error x , type NET HELPMSG x to see
what it corresponds to , sometimes a valuable clue to whats going on
ie NET HELPMSG 170 gives you "the requested resource was in use"
Andy.
"kishore" <anonymous@.discussions.microsoft.com> wrote in message
news:10d201c48bd5$fa04a5c0$a301280a@.phx.gbl...
> I am running a job every night. It runs fine until last
> saturday. In job we are executing 25 stored procedures.
> We are getting error after running 12 procedures and
> gives error -- "Line 1: Incorrect syntax near '>'.
> [SQLSTATE 42000] (Error 170). The step failed". Actually
> There is no syntax error. When I checked error log it
> shows -- "Operating system error 170., Line 1: Incorrect
> syntax near '>'.2004-08-23 20:33:07.27 logon Login
> succeeded for user 'US\dashbrd'. Connection: Trusted.
> Error encountered while executing xp_sendmail @.query..
> Error: 17968, Severity: 15, State: 1 ".
> We are running job again starting with stored procedure
> 12. It is running fine. I don't understand why it
> happens? Can any one help me
|||In error it shows error occured during xp_Sendmail, but
we are not sending any message at that time. Why it
looking for xp_sendmail?In stored procedure we are
updating temp table and deleting temp table after
inserting data into original table. Is while deleting
temp table causes this problem?
>--Original Message--
>little tip , when you Operating System Error x , type
NET HELPMSG x to see
>what it corresponds to , sometimes a valuable clue to
whats going on
>ie NET HELPMSG 170 gives you "the requested resource was
in use"
>Andy.
>"kishore" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:10d201c48bd5$fa04a5c0$a301280a@.phx.gbl...
Actually[vbcol=seagreen]
Incorrect
>
>.
>
|||check to see if there are any triggers on the tables being updated.
Andy.
"kishore" <anonymous@.discussions.microsoft.com> wrote in message
news:09cd01c48c3b$01e37720$a401280a@.phx.gbl...[vbcol=seagreen]
> In error it shows error occured during xp_Sendmail, but
> we are not sending any message at that time. Why it
> looking for xp_sendmail?In stored procedure we are
> updating temp table and deleting temp table after
> inserting data into original table. Is while deleting
> temp table causes this problem?
> NET HELPMSG x to see
> whats going on
> in use"
> message
> Actually
> Incorrect
|||No triggers are firing. Up to last week it ran fine.
>--Original Message--
>check to see if there are any triggers on the tables
being updated.
>Andy.
>"kishore" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:09cd01c48c3b$01e37720$a401280a@.phx.gbl...
was[vbcol=seagreen]
in[vbcol=seagreen]
last[vbcol=seagreen]
procedures.[vbcol=seagreen]
it[vbcol=seagreen]
Login[vbcol=seagreen]
Trusted.[vbcol=seagreen]
@.query..[vbcol=seagreen]
procedure
>
>.
>
|||Hi
You may want to try profiling this and see what is being sent to the server.
It sounds as if it could be an unescaped quote type of problem? Is there
any dynamic SQL being used?
John
"kishore" <anonymous@.discussions.microsoft.com> wrote in message
news:1c0f01c48cfb$58107510$a601280a@.phx.gbl...[vbcol=seagreen]
> No triggers are firing. Up to last week it ran fine.
>
> being updated.
> message
> was
> in
> last
> procedures.
> it
> Login
> Trusted.
> @.query..
> procedure
|||Hi
I can't really suggest any more except maybe dropping and recreating all the
procedures and the job.
John
"kishore" <anonymous@.discussions.microsoft.com> wrote in message
news:093a01c48ea5$487d3650$a401280a@.phx.gbl...[vbcol=seagreen]
> Created a trace file using profiler. It doesn't help me.
> There is no dynamic sql. In profiler it shows stored
> procedure is completed successfully. After completing the
> stored proc,it sending message as step is failed. Since
> step fails, it doesn't go to the next step.I don't
> understand what is the cause for this error?
>
> sent to the server.
> problem? Is there
> message
> in
> but
> deleting
> type
> to
> resource
> wrote
> until
> and
> near '>'.
> log
Sunday, February 19, 2012
Error While Scheduling the SSIS Package
Hello Everyone,
When i try to scedule a job on SQL Server Management Studio it gives the Following Error:
Coz i haven't seen any while installing.
|||Did you manage to find a solution for this problem? I get the same error when trying to create an Agent job. I've repaired the SQL Native Client but to no avail. I still get the error.
|||No, not yet !!! I am still working on it.
One of the forum member advised me to repair the server but for you if it did not work, then i am doubtful.
|||You can repair the application from "Programs and Features" (Vista) or "Add/Remove Programs" (XP) in control panel|||
When i try to scedule a job on SQL Server Management Studio it gives the Following Error:
Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectkey'.(Micorsoft.SqlServer.Smo)
Can anyone tell me why ?
MS SQL Server Details:
Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86) Oct 14 2005 00:33:37 Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
Hi,
Do you have this file?
C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies\Microsoft.SqlServer.Smo.dll
Regards,
Janos
|||Yes, File is there on the specified path.|||
Well, I got the same error one time, as far as I remember, I repaired my installation of SQL Server client tool.
Try to repair it please.
regards,
Janos
|||thanks janos,i have a local server installed on my workstation along with sp2.
Do you really think reinstalling the server will work ?
|||
Well, It worked for me
Maybe you just repair your installation will be enough.
Regards,
Janos
|||Is there any option for repairing the server ?Coz i haven't seen any while installing.
|||Did you manage to find a solution for this problem? I get the same error when trying to create an Agent job. I've repaired the SQL Native Client but to no avail. I still get the error.
|||No, not yet !!! I am still working on it.
One of the forum member advised me to repair the server but for you if it did not work, then i am doubtful.
|||You can repair the application from "Programs and Features" (Vista) or "Add/Remove Programs" (XP) in control panel|||
Hi Vick,
I just realized something. I saw the error message contains the SQL build w/o service pack, but you wrote you have SP2 installed (but maybe just for database services and SSMS or just SSIS). Have you tried to install the SP2 to the SSIS or those, where not installed?
Regards,
Janos
|||No, Its not working even after repairing the server.Thanks
Janos
|||Sorry Vick, I'm out of ideas. I tried to recreate the same error on a virtual machine, but no luck. 
Sp2 is not specific to the service you are using. It upgrades all the services of server (EE, DE, SE, etc).
Check out the link
http://www.microsoft.com/downloads/details.aspx?familyid=d07219b2-1e23-49c8-8f0c-63fa18f26d3a&displaylang=en
|||check out the post.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1793362&SiteID=1
check if you are experiencing the same.
Subscribe to:
Posts (Atom)