We have job that runs on sql server 2000 every mintute, the job logic is to retrieve data from remote sql 2000 server using link server config. 98% of the time the job run sucessfully, but once in while the job fails with the following error:
'SQLOLEDB' reported an error. [SQLSTATE 42000] (Error 7399)
[SQLSTATE 01000] (Error 7312) OLE DB error trace [OLE/DB Provider
'SQLOLEDB' ITransactionJoin::JoinTransaction returned 0x80004005: ].
[SQLSTATE 01000] (Error 7300). The step failed.
Does, anyone know why is this happening?
Thank You,
Jason
Jason,
What version of Windows are you using? If Windows 2000, make sure you
are on SP4. This might solve it. Also, check that there is not a
firewall between the servers, if there is, ensure that RPC traffic is
allowed through.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Jason wrote:
> We have job that runs on sql server 2000 every mintute, the job logic is to retrieve data from remote sql 2000 server using link server config. 98% of the time the job run sucessfully, but once in while the job fails with the following error:
> 'SQLOLEDB' reported an error. [SQLSTATE 42000] (Error 7399)
> [SQLSTATE 01000] (Error 7312) OLE DB error trace [OLE/DB Provider
> 'SQLOLEDB' ITransactionJoin::JoinTransaction returned 0x80004005: ].
> [SQLSTATE 01000] (Error 7300). The step failed.
> Does, anyone know why is this happening?
> Thank You,
> Jason
|||All the server that communiate with each other using link config do have sp4 for windows 2000 and there is no firewall between the servers.
|||Jason,
This looks like a case for Microsoft Support.
http://support.microsoft.com/default...d=fh;EN-US;sql
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
jason wrote:
> All the server that communiate with each other using link config do have sp4 for windows 2000 and there is no firewall between the servers.
Showing posts with label runs. Show all posts
Showing posts with label runs. Show all posts
Thursday, March 29, 2012
error ITransactionJoin::JoinTransaction
We have job that runs on sql server 2000 every mintute, the job logic is to
retrieve data from remote sql 2000 server using link server config. 98% of t
he time the job run sucessfully, but once in while the job fails with the fo
llowing error:
'SQLOLEDB' reported an error. [SQLSTATE 42000] (Error 7399)
[SQLSTATE 01000] (Error 7312) OLE DB error trace [OLE/DB Provider
'SQLOLEDB' ITransactionJoin::JoinTransaction returned 0x80004005: ].
[SQLSTATE 01000] (Error 7300). The step failed.
Does, anyone know why is this happening?
Thank You,
JasonJason,
What version of Windows are you using? If Windows 2000, make sure you
are on SP4. This might solve it. Also, check that there is not a
firewall between the servers, if there is, ensure that RPC traffic is
allowed through.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Jason wrote:
> We have job that runs on sql server 2000 every mintute, the job logic is t
o retrieve data from remote sql 2000 server using link server config. 98% of
the time the job run sucessfully, but once in while the job fails with the
following error:
> 'SQLOLEDB' reported an error. [SQLSTATE 42000] (Error 7399)
> [SQLSTATE 01000] (Error 7312) OLE DB error trace [OLE/DB Provide
r
> 'SQLOLEDB' ITransactionJoin::JoinTransaction returned 0x80004005: ].
> [SQLSTATE 01000] (Error 7300). The step failed.
> Does, anyone know why is this happening?
> Thank You,
> Jason|||All the server that communiate with each other using link config do have sp4
for Windows 2000 and there is no firewall between the servers.|||Jason,
This looks like a case for Microsoft Support.
http://support.microsoft.com/defaul...id=fh;EN-US;sql
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
jason wrote:
> All the server that communiate with each other using link config do have sp4 for w
indows 2000 and there is no firewall between the servers.
retrieve data from remote sql 2000 server using link server config. 98% of t
he time the job run sucessfully, but once in while the job fails with the fo
llowing error:
'SQLOLEDB' reported an error. [SQLSTATE 42000] (Error 7399)
[SQLSTATE 01000] (Error 7312) OLE DB error trace [OLE/DB Provider
'SQLOLEDB' ITransactionJoin::JoinTransaction returned 0x80004005: ].
[SQLSTATE 01000] (Error 7300). The step failed.
Does, anyone know why is this happening?
Thank You,
JasonJason,
What version of Windows are you using? If Windows 2000, make sure you
are on SP4. This might solve it. Also, check that there is not a
firewall between the servers, if there is, ensure that RPC traffic is
allowed through.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Jason wrote:
> We have job that runs on sql server 2000 every mintute, the job logic is t
o retrieve data from remote sql 2000 server using link server config. 98% of
the time the job run sucessfully, but once in while the job fails with the
following error:
> 'SQLOLEDB' reported an error. [SQLSTATE 42000] (Error 7399)
> [SQLSTATE 01000] (Error 7312) OLE DB error trace [OLE/DB Provide
r
> 'SQLOLEDB' ITransactionJoin::JoinTransaction returned 0x80004005: ].
> [SQLSTATE 01000] (Error 7300). The step failed.
> Does, anyone know why is this happening?
> Thank You,
> Jason|||All the server that communiate with each other using link config do have sp4
for Windows 2000 and there is no firewall between the servers.|||Jason,
This looks like a case for Microsoft Support.
http://support.microsoft.com/defaul...id=fh;EN-US;sql
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
jason wrote:
> All the server that communiate with each other using link config do have sp4 for w
indows 2000 and there is no firewall between the servers.
Wednesday, March 21, 2012
Error in SQL Server Database
Hello there,
I have a VB6 application that runs over a SQL Server 2000 Database.
Sometimes (most recently) i get the folowing error:
Run-time error -2147467259 (80004005)
Location: q:\SPHINX\NTDBMS\storeng\drs\include\record.inl:14 47
Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
SPID: 51
Process ID: 732
I have searched and read some posts in some forums, but I have no concret
solution.
Can any body help me? Thank you...
Regards,
Marco Pais
Marco Pais wrote:
> Hello there,
> I have a VB6 application that runs over a SQL Server 2000 Database.
> Sometimes (most recently) i get the folowing error:
> Run-time error -2147467259 (80004005)
> Location: q:\SPHINX\NTDBMS\storeng\drs\include\record.inl:14 47
> Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
> SPID: 51
> Process ID: 732
> I have searched and read some posts in some forums, but I have no
> concret solution.
> Can any body help me? Thank you...
> Regards,
> Marco Pais
See if this thread helps (may require a login - which is free):
http://www.sqlservercentral.com/foru...essageid=12331
David Gugick
Imceda Software
www.imceda.com
|||Marco Pais wrote:
> Hello there,
> I have a VB6 application that runs over a SQL Server 2000 Database.
> Sometimes (most recently) i get the folowing error:
> Run-time error -2147467259 (80004005)
> Location: q:\SPHINX\NTDBMS\storeng\drs\include\record.inl:14 47
> Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
> SPID: 51
> Process ID: 732
> I have searched and read some posts in some forums, but I have no
> concret solution.
> Can any body help me? Thank you...
> Regards,
> Marco Pais
BTW, that's an internal SQL Server error. You don't have a "q" drive.
Some others have corrected the problem by rebuilding the clustered index
on the affected table.
Run dbcc checkdb and dbcc checkalloc to see if any errors are reported.
If you can isolate the table, try rebuilding the clustered index.
It's probably some sort of data corruption, but could also be a disk
failure.
David Gugick
Imceda Software
www.imceda.com
I have a VB6 application that runs over a SQL Server 2000 Database.
Sometimes (most recently) i get the folowing error:
Run-time error -2147467259 (80004005)
Location: q:\SPHINX\NTDBMS\storeng\drs\include\record.inl:14 47
Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
SPID: 51
Process ID: 732
I have searched and read some posts in some forums, but I have no concret
solution.
Can any body help me? Thank you...
Regards,
Marco Pais
Marco Pais wrote:
> Hello there,
> I have a VB6 application that runs over a SQL Server 2000 Database.
> Sometimes (most recently) i get the folowing error:
> Run-time error -2147467259 (80004005)
> Location: q:\SPHINX\NTDBMS\storeng\drs\include\record.inl:14 47
> Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
> SPID: 51
> Process ID: 732
> I have searched and read some posts in some forums, but I have no
> concret solution.
> Can any body help me? Thank you...
> Regards,
> Marco Pais
See if this thread helps (may require a login - which is free):
http://www.sqlservercentral.com/foru...essageid=12331
David Gugick
Imceda Software
www.imceda.com
|||Marco Pais wrote:
> Hello there,
> I have a VB6 application that runs over a SQL Server 2000 Database.
> Sometimes (most recently) i get the folowing error:
> Run-time error -2147467259 (80004005)
> Location: q:\SPHINX\NTDBMS\storeng\drs\include\record.inl:14 47
> Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
> SPID: 51
> Process ID: 732
> I have searched and read some posts in some forums, but I have no
> concret solution.
> Can any body help me? Thank you...
> Regards,
> Marco Pais
BTW, that's an internal SQL Server error. You don't have a "q" drive.
Some others have corrected the problem by rebuilding the clustered index
on the affected table.
Run dbcc checkdb and dbcc checkalloc to see if any errors are reported.
If you can isolate the table, try rebuilding the clustered index.
It's probably some sort of data corruption, but could also be a disk
failure.
David Gugick
Imceda Software
www.imceda.com
Error in SQL Server Database
Hello there,
I have a VB6 application that runs over a SQL Server 2000 Database.
Sometimes (most recently) i get the folowing error:
Run-time error -2147467259 (80004005)
Location: q:\SPHINX\NTDBMS\storeng\drs\include\record.inl:14 47
Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
SPID: 51
Process ID: 732
I have searched and read some posts in some forums, but I have no concret
solution.
Can any body help me? Thank you...
Regards,
Marco Pais
This could be a bug in SQL Server or a corruption caused by hardware.
Please first use "DBCC CHECKDB" to see if your database has any corruptions.
Please also check the windows event log for any suspicious hardware error.
You can then contact Microsoft SQL Server product support if you suspect
this to be a SQL Server bug.
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://weblogs.asp.net/weix
This posting is provided "AS IS" with no warranties, and confers no rights.
"Marco Pais" <mpaisIGNORE@.foruminformatica.pt> wrote in message
news:utzyb4ZzEHA.1196@.TK2MSFTNGP15.phx.gbl...
> Hello there,
> I have a VB6 application that runs over a SQL Server 2000 Database.
> Sometimes (most recently) i get the folowing error:
> Run-time error -2147467259 (80004005)
> Location: q:\SPHINX\NTDBMS\storeng\drs\include\record.inl:14 47
> Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
> SPID: 51
> Process ID: 732
> I have searched and read some posts in some forums, but I have no concret
> solution.
> Can any body help me? Thank you...
> Regards,
> Marco Pais
>
I have a VB6 application that runs over a SQL Server 2000 Database.
Sometimes (most recently) i get the folowing error:
Run-time error -2147467259 (80004005)
Location: q:\SPHINX\NTDBMS\storeng\drs\include\record.inl:14 47
Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
SPID: 51
Process ID: 732
I have searched and read some posts in some forums, but I have no concret
solution.
Can any body help me? Thank you...
Regards,
Marco Pais
This could be a bug in SQL Server or a corruption caused by hardware.
Please first use "DBCC CHECKDB" to see if your database has any corruptions.
Please also check the windows event log for any suspicious hardware error.
You can then contact Microsoft SQL Server product support if you suspect
this to be a SQL Server bug.
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://weblogs.asp.net/weix
This posting is provided "AS IS" with no warranties, and confers no rights.
"Marco Pais" <mpaisIGNORE@.foruminformatica.pt> wrote in message
news:utzyb4ZzEHA.1196@.TK2MSFTNGP15.phx.gbl...
> Hello there,
> I have a VB6 application that runs over a SQL Server 2000 Database.
> Sometimes (most recently) i get the folowing error:
> Run-time error -2147467259 (80004005)
> Location: q:\SPHINX\NTDBMS\storeng\drs\include\record.inl:14 47
> Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
> SPID: 51
> Process ID: 732
> I have searched and read some posts in some forums, but I have no concret
> solution.
> Can any body help me? Thank you...
> Regards,
> Marco Pais
>
Error in SQL Server Database
Hello there,
I have a VB6 application that runs over a SQL Server 2000 Database.
Sometimes (most recently) i get the folowing error:
Run-time error -2147467259 (80004005)
Location: q:\SPHINX\NTDBMS\storeng\drs\include\record.inl:14 47
Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
SPID: 51
Process ID: 732
I have searched and read some posts in some forums, but I have no concret
solution.
Can any body help me? Thank you...
Regards,
Marco Pais
The following is an article with the exact same error:
http://support.microsoft.com/default...b;en-us;827714
Do those conditions apply in your case?
What exactly is the application doing when you get the
error? What T-SQL is being executed?
-Sue
On Thu, 18 Nov 2004 18:39:53 -0000, "Marco Pais"
<mpaisIGNORE@.foruminformatica.pt> wrote:
>Hello there,
>I have a VB6 application that runs over a SQL Server 2000 Database.
>Sometimes (most recently) i get the folowing error:
> Run-time error -2147467259 (80004005)
> Location: q:\SPHINX\NTDBMS\storeng\drs\include\record.inl:14 47
> Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
> SPID: 51
> Process ID: 732
>I have searched and read some posts in some forums, but I have no concret
>solution.
>Can any body help me? Thank you...
>Regards,
>Marco Pais
>
sql
I have a VB6 application that runs over a SQL Server 2000 Database.
Sometimes (most recently) i get the folowing error:
Run-time error -2147467259 (80004005)
Location: q:\SPHINX\NTDBMS\storeng\drs\include\record.inl:14 47
Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
SPID: 51
Process ID: 732
I have searched and read some posts in some forums, but I have no concret
solution.
Can any body help me? Thank you...
Regards,
Marco Pais
The following is an article with the exact same error:
http://support.microsoft.com/default...b;en-us;827714
Do those conditions apply in your case?
What exactly is the application doing when you get the
error? What T-SQL is being executed?
-Sue
On Thu, 18 Nov 2004 18:39:53 -0000, "Marco Pais"
<mpaisIGNORE@.foruminformatica.pt> wrote:
>Hello there,
>I have a VB6 application that runs over a SQL Server 2000 Database.
>Sometimes (most recently) i get the folowing error:
> Run-time error -2147467259 (80004005)
> Location: q:\SPHINX\NTDBMS\storeng\drs\include\record.inl:14 47
> Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
> SPID: 51
> Process ID: 732
>I have searched and read some posts in some forums, but I have no concret
>solution.
>Can any body help me? Thank you...
>Regards,
>Marco Pais
>
sql
Error in SQL Server Database
Hello there,
I have a VB6 application that runs over a SQL Server 2000 Database.
Sometimes (most recently) i get the folowing error:
Run-time error -2147467259 (80004005)
Location: q:\SPHINX\NTDBMS\storeng\drs\include\record.inl:1447
Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
SPID: 51
Process ID: 732
I have searched and read some posts in some forums, but I have no concret
solution.
Can any body help me? Thank you...
Regards,
Marco PaisThis could be a bug in SQL Server or a corruption caused by hardware.
Please first use "DBCC CHECKDB" to see if your database has any corruptions.
Please also check the windows event log for any suspicious hardware error.
You can then contact Microsoft SQL Server product support if you suspect
this to be a SQL Server bug.
--
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://weblogs.asp.net/weix
This posting is provided "AS IS" with no warranties, and confers no rights.
"Marco Pais" <mpaisIGNORE@.foruminformatica.pt> wrote in message
news:utzyb4ZzEHA.1196@.TK2MSFTNGP15.phx.gbl...
> Hello there,
> I have a VB6 application that runs over a SQL Server 2000 Database.
> Sometimes (most recently) i get the folowing error:
> Run-time error -2147467259 (80004005)
> Location: q:\SPHINX\NTDBMS\storeng\drs\include\record.inl:1447
> Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
> SPID: 51
> Process ID: 732
> I have searched and read some posts in some forums, but I have no concret
> solution.
> Can any body help me? Thank you...
> Regards,
> Marco Pais
>
I have a VB6 application that runs over a SQL Server 2000 Database.
Sometimes (most recently) i get the folowing error:
Run-time error -2147467259 (80004005)
Location: q:\SPHINX\NTDBMS\storeng\drs\include\record.inl:1447
Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
SPID: 51
Process ID: 732
I have searched and read some posts in some forums, but I have no concret
solution.
Can any body help me? Thank you...
Regards,
Marco PaisThis could be a bug in SQL Server or a corruption caused by hardware.
Please first use "DBCC CHECKDB" to see if your database has any corruptions.
Please also check the windows event log for any suspicious hardware error.
You can then contact Microsoft SQL Server product support if you suspect
this to be a SQL Server bug.
--
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://weblogs.asp.net/weix
This posting is provided "AS IS" with no warranties, and confers no rights.
"Marco Pais" <mpaisIGNORE@.foruminformatica.pt> wrote in message
news:utzyb4ZzEHA.1196@.TK2MSFTNGP15.phx.gbl...
> Hello there,
> I have a VB6 application that runs over a SQL Server 2000 Database.
> Sometimes (most recently) i get the folowing error:
> Run-time error -2147467259 (80004005)
> Location: q:\SPHINX\NTDBMS\storeng\drs\include\record.inl:1447
> Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
> SPID: 51
> Process ID: 732
> I have searched and read some posts in some forums, but I have no concret
> solution.
> Can any body help me? Thank you...
> Regards,
> Marco Pais
>
Error in SQL Server Database
Hello there,
I have a VB6 application that runs over a SQL Server 2000 Database.
Sometimes (most recently) i get the folowing error:
Run-time error -2147467259 (80004005)
Location: q:\SPHINX\NTDBMS\storeng\drs\include\rec
ord.inl:1447
Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
SPID: 51
Process ID: 732
I have searched and read some posts in some forums, but I have no concret
solution.
Can any body help me? Thank you...
Regards,
Marco PaisThis could be a bug in SQL Server or a corruption caused by hardware.
Please first use "DBCC CHECKDB" to see if your database has any corruptions.
Please also check the windows event log for any suspicious hardware error.
You can then contact Microsoft SQL Server product support if you suspect
this to be a SQL Server bug.
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://weblogs.asp.net/weix
This posting is provided "AS IS" with no warranties, and confers no rights.
"Marco Pais" <mpaisIGNORE@.foruminformatica.pt> wrote in message
news:utzyb4ZzEHA.1196@.TK2MSFTNGP15.phx.gbl...
> Hello there,
> I have a VB6 application that runs over a SQL Server 2000 Database.
> Sometimes (most recently) i get the folowing error:
> Run-time error -2147467259 (80004005)
> Location: q:\SPHINX\NTDBMS\storeng\drs\include\rec
ord.inl:1447
> Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
> SPID: 51
> Process ID: 732
> I have searched and read some posts in some forums, but I have no concret
> solution.
> Can any body help me? Thank you...
> Regards,
> Marco Pais
>
I have a VB6 application that runs over a SQL Server 2000 Database.
Sometimes (most recently) i get the folowing error:
Run-time error -2147467259 (80004005)
Location: q:\SPHINX\NTDBMS\storeng\drs\include\rec
ord.inl:1447
Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
SPID: 51
Process ID: 732
I have searched and read some posts in some forums, but I have no concret
solution.
Can any body help me? Thank you...
Regards,
Marco PaisThis could be a bug in SQL Server or a corruption caused by hardware.
Please first use "DBCC CHECKDB" to see if your database has any corruptions.
Please also check the windows event log for any suspicious hardware error.
You can then contact Microsoft SQL Server product support if you suspect
this to be a SQL Server bug.
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://weblogs.asp.net/weix
This posting is provided "AS IS" with no warranties, and confers no rights.
"Marco Pais" <mpaisIGNORE@.foruminformatica.pt> wrote in message
news:utzyb4ZzEHA.1196@.TK2MSFTNGP15.phx.gbl...
> Hello there,
> I have a VB6 application that runs over a SQL Server 2000 Database.
> Sometimes (most recently) i get the folowing error:
> Run-time error -2147467259 (80004005)
> Location: q:\SPHINX\NTDBMS\storeng\drs\include\rec
ord.inl:1447
> Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
> SPID: 51
> Process ID: 732
> I have searched and read some posts in some forums, but I have no concret
> solution.
> Can any body help me? Thank you...
> Regards,
> Marco Pais
>
Error in Sql Server 2000 sp4
I′ve got a problem with SQL server. The server stops responding and gives me
out an error below.
Anyone can help me. When it runs this select in the database the server
keeps with 80% 100% processor up and stops responding all client requests.
Memory
MemoryLoad = 94%
Total Physical = 2047 MB
Available Physical = 116 MB
Total Page File = 8041 MB
Available Page File = 6246 MB
Total Virtual = 2047 MB
Available Virtual = 281 MB
*Stack Dump being sent to E:\Microsoft SQL Server\MSSQL\log\SQLDump0009.txt
*
************************************************** ***************************
**
*
* BEGIN STACK DUMP:
* 02/23/07 10:17:59 spid 89
*
* Exception Address = 00402836
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred writing address 00000004
* Input Buffer 82 bytes -
* SELECT * from ProdutosParaSiteWeb_ANALISE
Luis,
Is ProdutosParaSiteWeb_ANALISE a view? If so, examine the code for the view
for complexity. Maybe you have uncovered a SQL Server bug, but recrafting
the code could work around the problem.
If ProdutosParaSiteWeb_ANALISE is a table, or the view is very simple, then
you might be concerned with database integrity. Run as DBCC CHECKDB and see
if it reveals any errors.
RLF
"Luis" <Luis@.discussions.microsoft.com> wrote in message
news:D1CA43FA-34B2-4A2A-8D83-529913BB66AB@.microsoft.com...
> Ive got a problem with SQL server. The server stops responding and gives
> me
> out an error below.
> Anyone can help me. When it runs this select in the database the server
> keeps with 80% 100% processor up and stops responding all client requests.
> Memory
> MemoryLoad = 94%
> Total Physical = 2047 MB
> Available Physical = 116 MB
> Total Page File = 8041 MB
> Available Page File = 6246 MB
> Total Virtual = 2047 MB
> Available Virtual = 281 MB
> *Stack Dump being sent to E:\Microsoft SQL
> Server\MSSQL\log\SQLDump0009.txt
> *
> ************************************************** ***************************
> **
> *
> * BEGIN STACK DUMP:
> * 02/23/07 10:17:59 spid 89
> *
> * Exception Address = 00402836
> * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> * Access Violation occurred writing address 00000004
> * Input Buffer 82 bytes -
> * SELECT * from ProdutosParaSiteWeb_ANALISE
>
out an error below.
Anyone can help me. When it runs this select in the database the server
keeps with 80% 100% processor up and stops responding all client requests.
Memory
MemoryLoad = 94%
Total Physical = 2047 MB
Available Physical = 116 MB
Total Page File = 8041 MB
Available Page File = 6246 MB
Total Virtual = 2047 MB
Available Virtual = 281 MB
*Stack Dump being sent to E:\Microsoft SQL Server\MSSQL\log\SQLDump0009.txt
*
************************************************** ***************************
**
*
* BEGIN STACK DUMP:
* 02/23/07 10:17:59 spid 89
*
* Exception Address = 00402836
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred writing address 00000004
* Input Buffer 82 bytes -
* SELECT * from ProdutosParaSiteWeb_ANALISE
Luis,
Is ProdutosParaSiteWeb_ANALISE a view? If so, examine the code for the view
for complexity. Maybe you have uncovered a SQL Server bug, but recrafting
the code could work around the problem.
If ProdutosParaSiteWeb_ANALISE is a table, or the view is very simple, then
you might be concerned with database integrity. Run as DBCC CHECKDB and see
if it reveals any errors.
RLF
"Luis" <Luis@.discussions.microsoft.com> wrote in message
news:D1CA43FA-34B2-4A2A-8D83-529913BB66AB@.microsoft.com...
> Ive got a problem with SQL server. The server stops responding and gives
> me
> out an error below.
> Anyone can help me. When it runs this select in the database the server
> keeps with 80% 100% processor up and stops responding all client requests.
> Memory
> MemoryLoad = 94%
> Total Physical = 2047 MB
> Available Physical = 116 MB
> Total Page File = 8041 MB
> Available Page File = 6246 MB
> Total Virtual = 2047 MB
> Available Virtual = 281 MB
> *Stack Dump being sent to E:\Microsoft SQL
> Server\MSSQL\log\SQLDump0009.txt
> *
> ************************************************** ***************************
> **
> *
> * BEGIN STACK DUMP:
> * 02/23/07 10:17:59 spid 89
> *
> * Exception Address = 00402836
> * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> * Access Violation occurred writing address 00000004
> * Input Buffer 82 bytes -
> * SELECT * from ProdutosParaSiteWeb_ANALISE
>
Error in Sql Server 2000 sp4
I′ve got a problem with SQL server. The server stops responding and gives m
e
out an error below.
Anyone can help me. When it runs this select in the database the server
keeps with 80% 100% processor up and stops responding all client requests.
Memory
MemoryLoad = 94%
Total Physical = 2047 MB
Available Physical = 116 MB
Total Page File = 8041 MB
Available Page File = 6246 MB
Total Virtual = 2047 MB
Available Virtual = 281 MB
*Stack Dump being sent to E:\Microsoft SQL Server\MSSQL\log\SQLDump0009.txt
*
****************************************
************************************
*
**
*
* BEGIN STACK DUMP:
* 02/23/07 10:17:59 spid 89
*
* Exception Address = 00402836
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred writing address 00000004
* Input Buffer 82 bytes -
* SELECT * from ProdutosParaSiteWeb_ANALISELuis,
Is ProdutosParaSiteWeb_ANALISE a view? If so, examine the code for the view
for complexity. Maybe you have uncovered a SQL Server bug, but recrafting
the code could work around the problem.
If ProdutosParaSiteWeb_ANALISE is a table, or the view is very simple, then
you might be concerned with database integrity. Run as DBCC CHECKDB and see
if it reveals any errors.
RLF
"Luis" <Luis@.discussions.microsoft.com> wrote in message
news:D1CA43FA-34B2-4A2A-8D83-529913BB66AB@.microsoft.com...
> Ive got a problem with SQL server. The server stops responding and gives
> me
> out an error below.
> Anyone can help me. When it runs this select in the database the server
> keeps with 80% 100% processor up and stops responding all client requests.
> Memory
> MemoryLoad = 94%
> Total Physical = 2047 MB
> Available Physical = 116 MB
> Total Page File = 8041 MB
> Available Page File = 6246 MB
> Total Virtual = 2047 MB
> Available Virtual = 281 MB
> *Stack Dump being sent to E:\Microsoft SQL
> Server\MSSQL\log\SQLDump0009.txt
> *
> ****************************************
**********************************
***
> **
> *
> * BEGIN STACK DUMP:
> * 02/23/07 10:17:59 spid 89
> *
> * Exception Address = 00402836
> * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> * Access Violation occurred writing address 00000004
> * Input Buffer 82 bytes -
> * SELECT * from ProdutosParaSiteWeb_ANALISE
>
e
out an error below.
Anyone can help me. When it runs this select in the database the server
keeps with 80% 100% processor up and stops responding all client requests.
Memory
MemoryLoad = 94%
Total Physical = 2047 MB
Available Physical = 116 MB
Total Page File = 8041 MB
Available Page File = 6246 MB
Total Virtual = 2047 MB
Available Virtual = 281 MB
*Stack Dump being sent to E:\Microsoft SQL Server\MSSQL\log\SQLDump0009.txt
*
****************************************
************************************
*
**
*
* BEGIN STACK DUMP:
* 02/23/07 10:17:59 spid 89
*
* Exception Address = 00402836
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred writing address 00000004
* Input Buffer 82 bytes -
* SELECT * from ProdutosParaSiteWeb_ANALISELuis,
Is ProdutosParaSiteWeb_ANALISE a view? If so, examine the code for the view
for complexity. Maybe you have uncovered a SQL Server bug, but recrafting
the code could work around the problem.
If ProdutosParaSiteWeb_ANALISE is a table, or the view is very simple, then
you might be concerned with database integrity. Run as DBCC CHECKDB and see
if it reveals any errors.
RLF
"Luis" <Luis@.discussions.microsoft.com> wrote in message
news:D1CA43FA-34B2-4A2A-8D83-529913BB66AB@.microsoft.com...
> Ive got a problem with SQL server. The server stops responding and gives
> me
> out an error below.
> Anyone can help me. When it runs this select in the database the server
> keeps with 80% 100% processor up and stops responding all client requests.
> Memory
> MemoryLoad = 94%
> Total Physical = 2047 MB
> Available Physical = 116 MB
> Total Page File = 8041 MB
> Available Page File = 6246 MB
> Total Virtual = 2047 MB
> Available Virtual = 281 MB
> *Stack Dump being sent to E:\Microsoft SQL
> Server\MSSQL\log\SQLDump0009.txt
> *
> ****************************************
**********************************
***
> **
> *
> * BEGIN STACK DUMP:
> * 02/23/07 10:17:59 spid 89
> *
> * Exception Address = 00402836
> * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> * Access Violation occurred writing address 00000004
> * Input Buffer 82 bytes -
> * SELECT * from ProdutosParaSiteWeb_ANALISE
>
Error in Sql Server 2000 sp4
I´ve got a problem with SQL server. The server stops responding and gives me
out an error below.
Anyone can help me. When it runs this select in the database the server
keeps with 80% 100% processor up and stops responding all client requests.
Memory
MemoryLoad = 94%
Total Physical = 2047 MB
Available Physical = 116 MB
Total Page File = 8041 MB
Available Page File = 6246 MB
Total Virtual = 2047 MB
Available Virtual = 281 MB
*Stack Dump being sent to E:\Microsoft SQL Server\MSSQL\log\SQLDump0009.txt
*
*****************************************************************************
**
*
* BEGIN STACK DUMP:
* 02/23/07 10:17:59 spid 89
*
* Exception Address = 00402836
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred writing address 00000004
* Input Buffer 82 bytes -
* SELECT * from ProdutosParaSiteWeb_ANALISELuis,
Is ProdutosParaSiteWeb_ANALISE a view? If so, examine the code for the view
for complexity. Maybe you have uncovered a SQL Server bug, but recrafting
the code could work around the problem.
If ProdutosParaSiteWeb_ANALISE is a table, or the view is very simple, then
you might be concerned with database integrity. Run as DBCC CHECKDB and see
if it reveals any errors.
RLF
"Luis" <Luis@.discussions.microsoft.com> wrote in message
news:D1CA43FA-34B2-4A2A-8D83-529913BB66AB@.microsoft.com...
> I´ve got a problem with SQL server. The server stops responding and gives
> me
> out an error below.
> Anyone can help me. When it runs this select in the database the server
> keeps with 80% 100% processor up and stops responding all client requests.
> Memory
> MemoryLoad = 94%
> Total Physical = 2047 MB
> Available Physical = 116 MB
> Total Page File = 8041 MB
> Available Page File = 6246 MB
> Total Virtual = 2047 MB
> Available Virtual = 281 MB
> *Stack Dump being sent to E:\Microsoft SQL
> Server\MSSQL\log\SQLDump0009.txt
> *
> *****************************************************************************
> **
> *
> * BEGIN STACK DUMP:
> * 02/23/07 10:17:59 spid 89
> *
> * Exception Address = 00402836
> * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> * Access Violation occurred writing address 00000004
> * Input Buffer 82 bytes -
> * SELECT * from ProdutosParaSiteWeb_ANALISE
>
out an error below.
Anyone can help me. When it runs this select in the database the server
keeps with 80% 100% processor up and stops responding all client requests.
Memory
MemoryLoad = 94%
Total Physical = 2047 MB
Available Physical = 116 MB
Total Page File = 8041 MB
Available Page File = 6246 MB
Total Virtual = 2047 MB
Available Virtual = 281 MB
*Stack Dump being sent to E:\Microsoft SQL Server\MSSQL\log\SQLDump0009.txt
*
*****************************************************************************
**
*
* BEGIN STACK DUMP:
* 02/23/07 10:17:59 spid 89
*
* Exception Address = 00402836
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred writing address 00000004
* Input Buffer 82 bytes -
* SELECT * from ProdutosParaSiteWeb_ANALISELuis,
Is ProdutosParaSiteWeb_ANALISE a view? If so, examine the code for the view
for complexity. Maybe you have uncovered a SQL Server bug, but recrafting
the code could work around the problem.
If ProdutosParaSiteWeb_ANALISE is a table, or the view is very simple, then
you might be concerned with database integrity. Run as DBCC CHECKDB and see
if it reveals any errors.
RLF
"Luis" <Luis@.discussions.microsoft.com> wrote in message
news:D1CA43FA-34B2-4A2A-8D83-529913BB66AB@.microsoft.com...
> I´ve got a problem with SQL server. The server stops responding and gives
> me
> out an error below.
> Anyone can help me. When it runs this select in the database the server
> keeps with 80% 100% processor up and stops responding all client requests.
> Memory
> MemoryLoad = 94%
> Total Physical = 2047 MB
> Available Physical = 116 MB
> Total Page File = 8041 MB
> Available Page File = 6246 MB
> Total Virtual = 2047 MB
> Available Virtual = 281 MB
> *Stack Dump being sent to E:\Microsoft SQL
> Server\MSSQL\log\SQLDump0009.txt
> *
> *****************************************************************************
> **
> *
> * BEGIN STACK DUMP:
> * 02/23/07 10:17:59 spid 89
> *
> * Exception Address = 00402836
> * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> * Access Violation occurred writing address 00000004
> * Input Buffer 82 bytes -
> * SELECT * from ProdutosParaSiteWeb_ANALISE
>
Wednesday, February 15, 2012
Error handling when calling external sql-Files
I am using SQL Server 2000. I have some files with SQL-Statements.
The SQL-Serveragent runs jobs which execute the SQL-Files:
(e.g. osql /E /n /i \\server\d$\lager_pool.sql)
How can I implement an error handling.
If an error occurs, the script stops, and I can't read the variable
@.error
My script - table xy doesnt exist
SELECT * FROM XY
SELECT @.@.error
SELECT 33
The execution stops with an error after the first line
Thanks for your help.
aaapaulHi
Look at using the -b flag when you call osql, there is more information in
Books Online.
John
<lvpaul@.gmx.net> wrote in message
news:1128067412.114048.12840@.g44g2000cwa.googlegro ups.com...
I am using SQL Server 2000. I have some files with SQL-Statements.
The SQL-Serveragent runs jobs which execute the SQL-Files:
(e.g. osql /E /n /i \\server\d$\lager_pool.sql)
How can I implement an error handling.
If an error occurs, the script stops, and I can't read the variable
@.error
My script - table xy doesnt exist
SELECT * FROM XY
SELECT @.@.error
SELECT 33
The execution stops with an error after the first line
Thanks for your help.
aaapaul|||Thanks, but it doesnt work
This is my script - its a file c:\test.sql
declare @.errorcode int
select * from abc
SET @.errorcode = @.@.error
--writing log
insert adaten.dbo.loghist(logdatum,loginfo,logfehler,saet ze)
values (getdate(),'test',@.errorcode,25)
The table "abc" dont exist.
If I call the script
osql /E /n /ic:\test.sql (with or without /b) the insert anweisung
instruction wont be executed.
I want something like ON ERROR RESUME NEXT. Is this possible ?
Thanks
aaapaul|||Hi
You may want to try using EXEC for your select statement
declare @.errorcode int
EXEC ('select * from abc')
SET @.errorcode = @.@.error
--writing log
insert adaten.dbo.loghist(logdatum,loginfo,logfehler,saet ze)
values (getdate(),'test',@.errorcode,25)
John
<lvpaul@.gmx.net> wrote in message
news:1128491173.083475.231000@.o13g2000cwo.googlegr oups.com...
Thanks, but it doesnt work
This is my script - its a file c:\test.sql
declare @.errorcode int
select * from abc
SET @.errorcode = @.@.error
--writing log
insert adaten.dbo.loghist(logdatum,loginfo,logfehler,saet ze)
values (getdate(),'test',@.errorcode,25)
The table "abc" dont exist.
If I call the script
osql /E /n /ic:\test.sql (with or without /b) the insert anweisung
instruction wont be executed.
I want something like ON ERROR RESUME NEXT. Is this possible ?
Thanks
aaapaul
Subscribe to:
Posts (Atom)