Wednesday, March 21, 2012
Error: 17883, Severity: 1, State: 0 during DB backup
of day and ran it manually and it occurrs only on this one. THere are 15
other databases on the server. We are running SQL 2000 sp4 on Windows 2003
Dell server raid 5, 2 GB of ram. No external disks.
Any ideas?
There are a lot of possibilities. See here:
http://www.google.com/search?hl=en&l...om+sq l+17883
Andrew J. Kelly SQL MVP
"Stacey" <Stacey@.discussions.microsoft.com> wrote in message
news:3E0F3A50-8A68-4859-AAE1-5C937A03EB36@.microsoft.com...
>I receive this error only when backing up database "a". I have changed
>times
> of day and ran it manually and it occurrs only on this one. THere are 15
> other databases on the server. We are running SQL 2000 sp4 on Windows 2003
> Dell server raid 5, 2 GB of ram. No external disks.
> Any ideas?
>
Error: 17883, Severity: 1, State: 0 during DB backup
of day and ran it manually and it occurrs only on this one. THere are 15
other databases on the server. We are running SQL 2000 sp4 on Windows 2003
Dell server raid 5, 2 GB of ram. No external disks.
Any ideas?There are a lot of possibilities. See here:
[url]http://www.google.com/search?hl=en&lr=&q=site%3Asupport.microsoft.com+sql+17883[/u
rl]
Andrew J. Kelly SQL MVP
"Stacey" <Stacey@.discussions.microsoft.com> wrote in message
news:3E0F3A50-8A68-4859-AAE1-5C937A03EB36@.microsoft.com...
>I receive this error only when backing up database "a". I have changed
>times
> of day and ran it manually and it occurrs only on this one. THere are 15
> other databases on the server. We are running SQL 2000 sp4 on Windows 2003
> Dell server raid 5, 2 GB of ram. No external disks.
> Any ideas?
>sql
Error: 17883, Severity: 1, State: 0 during DB backup
of day and ran it manually and it occurrs only on this one. THere are 15
other databases on the server. We are running SQL 2000 sp4 on Windows 2003
Dell server raid 5, 2 GB of ram. No external disks.
Any ideas?There are a lot of possibilities. See here:
http://www.google.com/search?hl=en&lr=&q=site%3Asupport.microsoft.com+sql+17883
Andrew J. Kelly SQL MVP
"Stacey" <Stacey@.discussions.microsoft.com> wrote in message
news:3E0F3A50-8A68-4859-AAE1-5C937A03EB36@.microsoft.com...
>I receive this error only when backing up database "a". I have changed
>times
> of day and ran it manually and it occurrs only on this one. THere are 15
> other databases on the server. We are running SQL 2000 sp4 on Windows 2003
> Dell server raid 5, 2 GB of ram. No external disks.
> Any ideas?
>
Monday, March 19, 2012
Error: 16954, Severity: 10, State: 1
I ran a trace over our SQL server and picked this error up.
Does anyone have any idea what could be causing this ?
Error: 16954, Severity: 10, State: 1
Our server is SQL2000 SP3a patched to 8.00.818 running on Win2K server.
Any help would be greatly appreciated.
Thanks
AndyHi
This error is connected with the use or no use of cursors.
The message indicated that a server side cursor was requested
(sp_cursoropen) but no cursor was necessary, as the SQL statement was
executed directly.
The error message can be informational.
Do you get timeout or disconnection after this error or any specific issue
on the Server Side?
HTH
Regards
Sadeesh
--
This posting is provided AS IS with no warranties, and confers no rights.
"Andy Hayes" <andyh@.friday-ad.co.uk> wrote in message
news:OjUrMY8bEHA.1000@.TK2MSFTNGP12.phx.gbl...
> Hi there.
> I ran a trace over our SQL server and picked this error up.
> Does anyone have any idea what could be causing this ?
> Error: 16954, Severity: 10, State: 1
> Our server is SQL2000 SP3a patched to 8.00.818 running on Win2K server.
> Any help would be greatly appreciated.
> Thanks
> Andy
>
Error: 16954, Severity: 10, State: 1
I ran a trace over our SQL server and picked this error up.
Does anyone have any idea what could be causing this ?
Error: 16954, Severity: 10, State: 1
Our server is SQL2000 SP3a patched to 8.00.818 running on Win2K server.
Any help would be greatly appreciated.
Thanks
AndyHi
This error is connected with the use or no use of cursors.
The message indicated that a server side cursor was requested
(sp_cursoropen) but no cursor was necessary, as the SQL statement was
executed directly.
The error message can be informational.
Do you get timeout or disconnection after this error or any specific issue
on the Server Side?
HTH
Regards
Sadeesh
--
This posting is provided AS IS with no warranties, and confers no rights.
"Andy Hayes" <andyh@.friday-ad.co.uk> wrote in message
news:OjUrMY8bEHA.1000@.TK2MSFTNGP12.phx.gbl...
> Hi there.
> I ran a trace over our SQL server and picked this error up.
> Does anyone have any idea what could be causing this ?
> Error: 16954, Severity: 10, State: 1
> Our server is SQL2000 SP3a patched to 8.00.818 running on Win2K server.
> Any help would be greatly appreciated.
> Thanks
> Andy
>
Error: 16954, Severity: 10, State: 1
I ran a trace over our SQL server and picked this error up.
Does anyone have any idea what could be causing this ?
Error: 16954, Severity: 10, State: 1
Our server is SQL2000 SP3a patched to 8.00.818 running on Win2K server.
Any help would be greatly appreciated.
Thanks
Andy
Hi
This error is connected with the use or no use of cursors.
The message indicated that a server side cursor was requested
(sp_cursoropen) but no cursor was necessary, as the SQL statement was
executed directly.
The error message can be informational.
Do you get timeout or disconnection after this error or any specific issue
on the Server Side?
HTH
Regards
Sadeesh
This posting is provided AS IS with no warranties, and confers no rights.
"Andy Hayes" <andyh@.friday-ad.co.uk> wrote in message
news:OjUrMY8bEHA.1000@.TK2MSFTNGP12.phx.gbl...
> Hi there.
> I ran a trace over our SQL server and picked this error up.
> Does anyone have any idea what could be causing this ?
> Error: 16954, Severity: 10, State: 1
> Our server is SQL2000 SP3a patched to 8.00.818 running on Win2K server.
> Any help would be greatly appreciated.
> Thanks
> Andy
>
Sunday, February 19, 2012
Error while running Query
SQL Server 7
When i ran a query in query analyzer i am getting the below error.
once i closed and opened the query analyzer and ran the same query it worked fine.
pls the error which i got in first time.
Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server
[Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
[Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
[Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
[Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
[Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
[Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
[Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
[Microsoft][ODBC SQL Server Driver]TDS buffer length too large
[Microsoft][ODBC SQL Server Driver]TDS buffer length too large
[Microsoft][ODBC SQL Server Driver]TDS buffer length too large
[Microsoft][ODBC SQL Server Driver]TDS buffer length too large
[Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server
[Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server
[Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server
[Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server
[Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server
[Microsoft][ODBC SQL Server Driver]TDS buffer length too large
[Microsoft][ODBC SQL Server Driver]TDS buffer length too large
[Microsoft][ODBC SQL Server Driver]TDS buffer length too large
Pls help me in this
TIA
AdilSo, after you reopened QA the same query ran with no errors? Are you suspecting you're going to get it again?|||hi
thanks for the reply
yes, i'm worried if it comes again whats the solution for it.
pls help me out.
TIA|||The problem seems to be that you've got some bits stuck in your network cable. Remove the cable, shake it vigorously in all four cardinal compass points (north, east, south, and west), and plug it back in. Things should work just fine then!
On a slightly more serious note, removing the network cable will actually fix the problem in most cases. There was some kind of communication error, possibly lost data/framing error/digi-voodoo/etc. When you remove the network cable for any significant amount of time (over a few seconds), the NIC resets. When the cable is reattached, the NIC reconnects, and whatever problem there was is magically gone.
If nothing else, the attention that you get when everybody thinks that you've clearly lost what little mind you might have once had, then your bizzare behavior appears to fix the problem will get you lots of digi-voodoo status.
-PatP|||that's an interesting solution, but considering the real reason for the above error actually very precise. now, here's your reference material (http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/q176/2/56.asp&NoWebContent=1) in this regard.|||Pat Phelan, you need to be more carefull about your advice. I followed your intructions and got bits all over my carpet. They are extremely hard to get out, and since the dang things carry a static charge they stick to my cat and he has tracked them all over the house. On a positive note, they seemed to pass through his digestive tract pretty quickly.
Wednesday, February 15, 2012
Error while executing nested DTS Packages...
We ran into a peculiar problem. We copied all of our DTS packages
from one server to another server (both of which run SQL 2000 and are
on the same Service Pack 3/3a). When we execute an embedded DTS
package from within anothe DTS package, we get the following error:
Error Title: Server Busy
Error Description: This action cannot be completed because the othe
program is busy. Choose 'Switch To' to activate the busy program and
correct the problem.
Buttons Available: Swith To..., Retry
Buttons Disabled: Cancel
Does any one know about this error and what to do about it?
Thanks
Jagannathan Santhanam (Jags)"Jagannathan Santhanam" <jags_32@.yahoo.com> wrote in message
news:605df08e.0309081332.73615acb@.posting.google.c om...
> Hello
> We ran into a peculiar problem. We copied all of our DTS packages
> from one server to another server (both of which run SQL 2000 and are
> on the same Service Pack 3/3a). When we execute an embedded DTS
> package from within anothe DTS package, we get the following error:
> Error Title: Server Busy
> Error Description: This action cannot be completed because the othe
> program is busy. Choose 'Switch To' to activate the busy program and
> correct the problem.
> Buttons Available: Swith To..., Retry
> Buttons Disabled: Cancel
> Does any one know about this error and what to do about it?
> Thanks
> Jagannathan Santhanam (Jags)
I've no idea what causes the error, but a search on Google found a few
similar cases. They seem to be related to ActiveX DLL problems. That's not
much to go on, but it might be something to investigate:
http://groups.google.com/groups?hl=...ram&sa=N&tab=wg
Simon