Absurd project: sp3

Showing posts with label sp3. Show all posts

Monday, March 19, 2012

Help , Several Connections , Port : 1433

Environment:
SQL Server Standard Edition
Microsoft Windows NT - 5.2 (3790)
8.00.760 (SP3)
DOS Command : netstat -n . Results as follows
Find several connections about port 1433
Who can help me ? How to resolve the problem ?
Please , thank you .
..
..
..
..
TCP 202.168.198.117:4941 202.181.68.244:1433 FIN_WAIT_1
TCP 202.168.198.117:4942 202.181.71.66:1433 FIN_WAIT_1
TCP 202.168.198.117:4943 202.168.198.116:1433 TIME_WAIT
TCP 202.168.198.117:4945 202.181.68.123:1433 FIN_WAIT_1
TCP 202.168.198.117:4950 202.181.68.123:1433 FIN_WAIT_1
TCP 202.168.198.117:4959 202.181.70.183:1433 FIN_WAIT_1
TCP 202.168.198.117:4959 202.181.92.3:1433 FIN_WAIT_1
TCP 202.168.198.117:4963 202.181.71.66:1433 FIN_WAIT_1
TCP 202.168.198.117:4964 202.181.95.40:1433 FIN_WAIT_1
TCP 202.168.198.117:4966 202.181.87.84:1433 FIN_WAIT_1
TCP 202.168.198.117:4966 202.181.94.137:1433 FIN_WAIT_1
TCP 202.168.198.117:4968 202.181.66.159:1433 FIN_WAIT_1
TCP 202.168.198.117:4970 202.181.71.66:1433 FIN_WAIT_1
TCP 202.168.198.117:4971 202.181.64.246:1433 FIN_WAIT_1
TCP 202.168.198.117:4976 202.181.94.137:1433 FIN_WAIT_1
TCP 202.168.198.117:4984 202.181.95.40:1433 FIN_WAIT_1
TCP 202.168.198.117:4985 202.181.95.40:1433 FIN_WAIT_1
TCP 202.168.198.117:4989 202.181.90.133:1433 FIN_WAIT_1
TCP 202.168.198.117:4992 202.181.66.159:1433 FIN_WAIT_1
TCP 202.168.198.117:4992 202.181.90.133:1433 FIN_WAIT_1
TCP 202.168.198.117:4996 202.181.88.249:1433 FIN_WAIT_1
TCP 202.168.198.117:4999 202.181.87.238:1433 FIN_WAIT_1
..
..
..
Hi
You may want to do a netstat -n -o to find what process is trying to connect
to the servers. It sounds like some process is browsing the network for
servers and port 1433 is open on the remote servers.
John
"test" wrote:

>
> Environment:
> SQL Server Standard Edition
> Microsoft Windows NT - 5.2 (3790)
> 8.00.760 (SP3)
>
> DOS Command : netstat -n . Results as follows
> Find several connections about port 1433
>
> Who can help me ? How to resolve the problem ?
> Please , thank you .
>
> ..
> ..
> ..
> ..
> TCP 202.168.198.117:4941 202.181.68.244:1433 FIN_WAIT_1
> TCP 202.168.198.117:4942 202.181.71.66:1433 FIN_WAIT_1
> TCP 202.168.198.117:4943 202.168.198.116:1433 TIME_WAIT
> TCP 202.168.198.117:4945 202.181.68.123:1433 FIN_WAIT_1
> TCP 202.168.198.117:4950 202.181.68.123:1433 FIN_WAIT_1
> TCP 202.168.198.117:4959 202.181.70.183:1433 FIN_WAIT_1
> TCP 202.168.198.117:4959 202.181.92.3:1433 FIN_WAIT_1
> TCP 202.168.198.117:4963 202.181.71.66:1433 FIN_WAIT_1
> TCP 202.168.198.117:4964 202.181.95.40:1433 FIN_WAIT_1
> TCP 202.168.198.117:4966 202.181.87.84:1433 FIN_WAIT_1
> TCP 202.168.198.117:4966 202.181.94.137:1433 FIN_WAIT_1
> TCP 202.168.198.117:4968 202.181.66.159:1433 FIN_WAIT_1
> TCP 202.168.198.117:4970 202.181.71.66:1433 FIN_WAIT_1
> TCP 202.168.198.117:4971 202.181.64.246:1433 FIN_WAIT_1
> TCP 202.168.198.117:4976 202.181.94.137:1433 FIN_WAIT_1
> TCP 202.168.198.117:4984 202.181.95.40:1433 FIN_WAIT_1
> TCP 202.168.198.117:4985 202.181.95.40:1433 FIN_WAIT_1
> TCP 202.168.198.117:4989 202.181.90.133:1433 FIN_WAIT_1
> TCP 202.168.198.117:4992 202.181.66.159:1433 FIN_WAIT_1
> TCP 202.168.198.117:4992 202.181.90.133:1433 FIN_WAIT_1
> TCP 202.168.198.117:4996 202.181.88.249:1433 FIN_WAIT_1
> TCP 202.168.198.117:4999 202.181.87.238:1433 FIN_WAIT_1
> ..
> ..
> ..
>
>
>
|||netstat -ano , find : SID = 5664
tasklist , find : 5664 = syswinxp.exe
"syswinxp.exe" maybe a trojan .
Thanks for your help .
"John Bell" <jbellnewsposts@.hotmail.com> glsD:46CCFA26-F813-4A39-8EF9-EF517084BB6E@.microsoft.com...[vbcol=seagreen]
> Hi
> You may want to do a netstat -n -o to find what process is trying to
> connect
> to the servers. It sounds like some process is browsing the network for
> servers and port 1433 is open on the remote servers.
> John
> "test" wrote:

Help , Several Connections , Port : 1433

Environment:
SQL Server Standard Edition
Microsoft Windows NT - 5.2 (3790)
8.00.760 (SP3)
DOS Command : netstat -n . Results as follows
Find several connections about port 1433
Who can help me ? How to resolve the problem ?
Please , thank you .
.
.
.
.
TCP 202.168.198.117:4941 202.181.68.244:1433 FIN_WAIT_1
TCP 202.168.198.117:4942 202.181.71.66:1433 FIN_WAIT_1
TCP 202.168.198.117:4943 202.168.198.116:1433 TIME_WAIT
TCP 202.168.198.117:4945 202.181.68.123:1433 FIN_WAIT_1
TCP 202.168.198.117:4950 202.181.68.123:1433 FIN_WAIT_1
TCP 202.168.198.117:4959 202.181.70.183:1433 FIN_WAIT_1
TCP 202.168.198.117:4959 202.181.92.3:1433 FIN_WAIT_1
TCP 202.168.198.117:4963 202.181.71.66:1433 FIN_WAIT_1
TCP 202.168.198.117:4964 202.181.95.40:1433 FIN_WAIT_1
TCP 202.168.198.117:4966 202.181.87.84:1433 FIN_WAIT_1
TCP 202.168.198.117:4966 202.181.94.137:1433 FIN_WAIT_1
TCP 202.168.198.117:4968 202.181.66.159:1433 FIN_WAIT_1
TCP 202.168.198.117:4970 202.181.71.66:1433 FIN_WAIT_1
TCP 202.168.198.117:4971 202.181.64.246:1433 FIN_WAIT_1
TCP 202.168.198.117:4976 202.181.94.137:1433 FIN_WAIT_1
TCP 202.168.198.117:4984 202.181.95.40:1433 FIN_WAIT_1
TCP 202.168.198.117:4985 202.181.95.40:1433 FIN_WAIT_1
TCP 202.168.198.117:4989 202.181.90.133:1433 FIN_WAIT_1
TCP 202.168.198.117:4992 202.181.66.159:1433 FIN_WAIT_1
TCP 202.168.198.117:4992 202.181.90.133:1433 FIN_WAIT_1
TCP 202.168.198.117:4996 202.181.88.249:1433 FIN_WAIT_1
TCP 202.168.198.117:4999 202.181.87.238:1433 FIN_WAIT_1
.
.
.Hi
You may want to do a netstat -n -o to find what process is trying to connect
to the servers. It sounds like some process is browsing the network for
servers and port 1433 is open on the remote servers.
John
"test" wrote:
>
> Environment:
> SQL Server Standard Edition
> Microsoft Windows NT - 5.2 (3790)
> 8.00.760 (SP3)
>
> DOS Command : netstat -n . Results as follows
> Find several connections about port 1433
>
> Who can help me ? How to resolve the problem ?
> Please , thank you .
>
> ..
> ..
> ..
> ..
> TCP 202.168.198.117:4941 202.181.68.244:1433 FIN_WAIT_1
> TCP 202.168.198.117:4942 202.181.71.66:1433 FIN_WAIT_1
> TCP 202.168.198.117:4943 202.168.198.116:1433 TIME_WAIT
> TCP 202.168.198.117:4945 202.181.68.123:1433 FIN_WAIT_1
> TCP 202.168.198.117:4950 202.181.68.123:1433 FIN_WAIT_1
> TCP 202.168.198.117:4959 202.181.70.183:1433 FIN_WAIT_1
> TCP 202.168.198.117:4959 202.181.92.3:1433 FIN_WAIT_1
> TCP 202.168.198.117:4963 202.181.71.66:1433 FIN_WAIT_1
> TCP 202.168.198.117:4964 202.181.95.40:1433 FIN_WAIT_1
> TCP 202.168.198.117:4966 202.181.87.84:1433 FIN_WAIT_1
> TCP 202.168.198.117:4966 202.181.94.137:1433 FIN_WAIT_1
> TCP 202.168.198.117:4968 202.181.66.159:1433 FIN_WAIT_1
> TCP 202.168.198.117:4970 202.181.71.66:1433 FIN_WAIT_1
> TCP 202.168.198.117:4971 202.181.64.246:1433 FIN_WAIT_1
> TCP 202.168.198.117:4976 202.181.94.137:1433 FIN_WAIT_1
> TCP 202.168.198.117:4984 202.181.95.40:1433 FIN_WAIT_1
> TCP 202.168.198.117:4985 202.181.95.40:1433 FIN_WAIT_1
> TCP 202.168.198.117:4989 202.181.90.133:1433 FIN_WAIT_1
> TCP 202.168.198.117:4992 202.181.66.159:1433 FIN_WAIT_1
> TCP 202.168.198.117:4992 202.181.90.133:1433 FIN_WAIT_1
> TCP 202.168.198.117:4996 202.181.88.249:1433 FIN_WAIT_1
> TCP 202.168.198.117:4999 202.181.87.238:1433 FIN_WAIT_1
> ..
> ..
> ..
>
>
>|||netstat -ano , find : SID = 5664
tasklist , find : 5664 = syswinxp.exe
"syswinxp.exe" maybe a trojan .
Thanks for your help .
"John Bell" <jbellnewsposts@.hotmail.com> ¼¶¼g©ó¶l¥ó·s»D:46CCFA26-F813-4A39-8EF9-EF517084BB6E@.microsoft.com...
> Hi
> You may want to do a netstat -n -o to find what process is trying to
> connect
> to the servers. It sounds like some process is browsing the network for
> servers and port 1433 is open on the remote servers.
> John
> "test" wrote:
>>
>> Environment:
>> SQL Server Standard Edition
>> Microsoft Windows NT - 5.2 (3790)
>> 8.00.760 (SP3)
>>
>> DOS Command : netstat -n . Results as follows
>> Find several connections about port 1433
>>
>> Who can help me ? How to resolve the problem ?
>> Please , thank you .
>>
>> ..
>> ..
>> ..
>> ..
>> TCP 202.168.198.117:4941 202.181.68.244:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4942 202.181.71.66:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4943 202.168.198.116:1433 TIME_WAIT
>> TCP 202.168.198.117:4945 202.181.68.123:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4950 202.181.68.123:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4959 202.181.70.183:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4959 202.181.92.3:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4963 202.181.71.66:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4964 202.181.95.40:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4966 202.181.87.84:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4966 202.181.94.137:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4968 202.181.66.159:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4970 202.181.71.66:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4971 202.181.64.246:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4976 202.181.94.137:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4984 202.181.95.40:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4985 202.181.95.40:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4989 202.181.90.133:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4992 202.181.66.159:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4992 202.181.90.133:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4996 202.181.88.249:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4999 202.181.87.238:1433 FIN_WAIT_1
>> ..
>> ..
>> ..
>>
>>
>>

Help , Several Connections , Port : 1433

Monday, March 12, 2012

Help !

Im going mad trying and failing to figure this out . running SQl server 2000
(sp3). I have had code snippets and examples thrown at me, yet im missing
something fundermental .. if i use the following code in TSQL i get a
sucess on the executon of the DTS
Declare @.Packagename varchar(255) -- Gets most recent Version
Declare @.Userpwd Varchar(255) -- Login Password
Declare @.Intsecurity bit
Declare @.pkgpwd varchar(255)
Declare @.hr int
Declare @.Object int
Set @.Intsecurity = 0
Set @.Userpwd = 'MyPassword'
set @.pkgpwd = NULL
Set @.Packagename = 'TESTDTS'
-- Create the Package object
EXEC @.hr = sp_OACreate 'DTS.Package', @.Object OUTPUT
If @.hr <> 0
Begin
Print 'Error Creating Package'
End
Else
Begin
Print 'Package Created'
End
-- Load the package
Declare @.svr varchar(15)
Declare @.login varchar(100)
Select @.login = 'MyUserName'
Select @.svr = @.@.serverName
Declare @.flag int
Select @.flag = 0
if @.intsecurity = 0
if @.userpwd = Null
EXEC @.hr = sp_OAMethod @.object, 'LoadFromSqlServer',NULL,
@.ServerName=@.svr, @.ServerUserName=@.login, @.PackageName=@.packagename,
@.Flags=@.flag, @.PackagePassword = @.pkgPwd
else
EXEC @.hr = sp_OAMethod @.object, 'LoadFromSqlServer',NULL,
@.ServerName=@.svr, @.ServerUserName=@.login, @.PackageName=@.packagename,
@.Flags=@.flag, @.PackagePassword = @.pkgPwd, @.ServerPassword = @.userpwd
else
begin
select @.flag = 256
EXEC @.hr = sp_OAMethod @.object, 'LoadFromSqlServer',NULL,
@.ServerName=@.svr, @.PackageName=@.packagename, @.Flags=@.flag, @.PackagePassword
=
@.pkgPwd
end
If @.hr <> 0
Begin
Print 'Error Loading Package'
End
Else
Begin
Print 'Package loaded'
End
EXEC @.hr = sp_OAMethod @.object, 'Execute'
If @.hr <> 0
Begin
Print 'Error Executing Package'
End
Else
Begin
Print 'Package Executed'
End
-- unitialize the package
EXEC @.hr = sp_OAMethod @.object, 'UnInitialize'
If @.hr <> 0
Begin
Print 'Error UnInitializing Package'
End
Else
Begin
Print 'Package UnInitialized'
End
-- release the package object
EXEC @.hr = sp_OADestroy @.object
If @.hr <> 0
Begin
Print 'Error Releasing Package'
End
Else
Begin
Print 'Package Released'
End
That use's SQL Authentication, however i need to use Wondows Authenticaton.
i can log on query analiser using windows Authentication, yet no matter what
i seem to do to the variables to try and get it to use Windows
Authentication it always fails. The SQL server is currently set for SQl and
Windows Authentication. Can anybody shed any light on what im overlooking ?> if @.userpwd = Null
What's your ansi_nulls setting? Use the standard: "if @.userpwd is Null".
ML|||ML, this code was taken from a help page.. I have amended as you suggested
but the results are still the same . I Log onto the network using my logon
user name and password. I can open a session of T-SQL and log on usoing
windows authentication without a problem.. so i dont understand why the
loadfromsqlserver wont allow me to use windows Authentication
"ML" wrote:

> What's your ansi_nulls setting? Use the standard: "if @.userpwd is Null".
>
> ML|||What about the @.Intsecurity variable? Have you tried setting it to 1 ?
ML|||ML
I have set @.Intsecurity = 1 , @.Userpwd = Null, @.login = SUSER_SNAME() and
@.Flag = 256 . still get an error -2147217843 when loading the package
"ML" wrote:

> What about the @.Intsecurity variable? Have you tried setting it to 1 ?
>
> ML|||Please post the entire error message.
Have you tried contacting the author of the script?
Is there a special reason behind executing the DTS package from T-SQL?
ML|||ML,
Im going to give up on this idea, Ive spent days at this problem with no
solution. I dont seem to be able to get any sort of error message back, onl
y
-2147217843 when i interrigate the value of @.hr. I can not find that error
number in the sql server books online. I have looked in the Server Logs ..
but nothing in there. Im a a total loss as to why this wont work with Window
s
Authentication and more frustrated at the fact that i carnt find out what is
causing the problem. I had origionaly tried to hav this run from a VB6
application that gets fired as an event from a FTP server, but then i was
still having issues on accesss rights across the network when trying to open
a txt file. I will fire a question of to the author of the code... see if he
can help at all .... if not its back to the drawing board
thanks for taking the time out to try and help
"ML" wrote:

> Please post the entire error message.
> Have you tried contacting the author of the script?
> Is there a special reason behind executing the DTS package from T-SQL?
>
> ML

Friday, March 9, 2012

Help - Very Odd Restore Issues

All,
Sql 2000 sp3, Server 2000 sp4
I am trying to restore a db to my testing server. I can
successfully restore it to my development server. But when
I try to restore it to my test server I get the following
error:Server: Msg 3205, Level 16, State 2, Line 1
Too many backup devices specified for backup or restore;
only 64 are allowed.
Both servers are on the same service packs for windows and
sql. I use the same script, only chnging the drive
letters. Any ideas at all? The restore script is below:
restore database member from
disk = 'u:\member_data_1.bak',
disk = 'u:\member_data_2.bak',
disk = 'u:\member_data_3.bak'
with stats = 1,
move 'MemberData00_01' to 'f:\MemberData00_01.MDF',
move 'MemberData01_01' to 'g:\MemberData01_01.NDF',
move 'MemberData01_02' to 'h:\MemberData01_02.NDF',
move 'MemberData01_03' to 'i:\MemberData01_03.NDF',
move 'MemberData01_04' to 'j:\MemberData01_04.NDF',
move 'MemberData01_05' to 'f:\MemberData01_05.NDF',
move 'MemberData01_06' to 'g:\MemberData01_06.NDF',
move 'MemberData01_07' to 'h:\MemberData01_07.NDF',
move 'MemberData01_08' to 'i:\MemberData01_08.NDF',
move 'MemberIndex01_01' to 'j:\MemberIndex01_01.NDF',
move 'MemberIndex01_02' to 'f:\MemberIndex01_02.NDF',
move 'MemberIndex01_03' to 'g:\MemberIndex01_03.NDF',
move 'MemberIndex01_04' to 'h:\MemberIndex01_04.NDF',
move 'MemberData02_01' to 'i:\MemberData02_01.NDF',
move 'MemberData02_02' to 'j:\MemberData02_02.NDF',
move 'MemberData02_03' to 'f:\MemberData02_03.NDF',
move 'MemberData03_01' to 'g:\MemberData03_01.NDF',
move 'MemberData03_02' to 'h:\MemberData03_02.NDF',
move 'MemberData03_03' to 'i:\MemberData03_03.NDF',
move 'MemberData04_01' to 'j:\MemberData04_01.NDF',
move 'MemberData04_02' to 'f:\MemberData04_02.NDF',
move 'MemberData04_03' to 'g:\MemberData04_03.NDF',
move 'MemberIndex02_01' to 'h:\MemberIndex02_01.NDF',
move 'MemberIndex02_02' to 'i:\MemberIndex02_02.NDF',
move 'MemberIndex03_01' to 'j:\MemberIndex03_01.NDF',
move 'MemberIndex03_02' to 'f:\MemberIndex03_02.NDF',
move 'memberIndex04_01' to 'g:\MemberIndex04_01.NDF',
move 'MemberIndex04_02' to 'h:\MemberIndex04_02.NDF',
move 'MemberData05_01' to 'i:\MemberData05_01.NDF',
move 'MemberData05_02' to 'j:\MemberData05_02.NDF',
move 'Member_Log' to 'u:\Member_Log.LDF',
move 'member_1_Log' to 'u:\Member_Log2'
Thanks in advance,
Gary AbbottHi,
Did you tried RESTORE FILELISTONLY command to identify the Logical and
physical names as well
as try RESTORE VERIFYONLY command .
Syntax of both commands:
RESTORE FILELISTONLY FROM disk='c:\backup\dbname.bak'
RESTORE VERIFYONLY FROM disk='c:\backup\dbname.bak'
Thanks
Hari
MCDBA
"Gary Abbott" <anonymous@.discussions.microsoft.com> wrote in message
news:1120901c40f5c$29dd3fb0$a101280a@.phx
.gbl...
> All,
> Sql 2000 sp3, Server 2000 sp4
> I am trying to restore a db to my testing server. I can
> successfully restore it to my development server. But when
> I try to restore it to my test server I get the following
> error:Server: Msg 3205, Level 16, State 2, Line 1
> Too many backup devices specified for backup or restore;
> only 64 are allowed.
> Both servers are on the same service packs for windows and
> sql. I use the same script, only chnging the drive
> letters. Any ideas at all? The restore script is below:
> restore database member from
> disk = 'u:\member_data_1.bak',
> disk = 'u:\member_data_2.bak',
> disk = 'u:\member_data_3.bak'
> with stats = 1,
> move 'MemberData00_01' to 'f:\MemberData00_01.MDF',
> move 'MemberData01_01' to 'g:\MemberData01_01.NDF',
> move 'MemberData01_02' to 'h:\MemberData01_02.NDF',
> move 'MemberData01_03' to 'i:\MemberData01_03.NDF',
> move 'MemberData01_04' to 'j:\MemberData01_04.NDF',
> move 'MemberData01_05' to 'f:\MemberData01_05.NDF',
> move 'MemberData01_06' to 'g:\MemberData01_06.NDF',
> move 'MemberData01_07' to 'h:\MemberData01_07.NDF',
> move 'MemberData01_08' to 'i:\MemberData01_08.NDF',
> move 'MemberIndex01_01' to 'j:\MemberIndex01_01.NDF',
> move 'MemberIndex01_02' to 'f:\MemberIndex01_02.NDF',
> move 'MemberIndex01_03' to 'g:\MemberIndex01_03.NDF',
> move 'MemberIndex01_04' to 'h:\MemberIndex01_04.NDF',
> move 'MemberData02_01' to 'i:\MemberData02_01.NDF',
> move 'MemberData02_02' to 'j:\MemberData02_02.NDF',
> move 'MemberData02_03' to 'f:\MemberData02_03.NDF',
> move 'MemberData03_01' to 'g:\MemberData03_01.NDF',
> move 'MemberData03_02' to 'h:\MemberData03_02.NDF',
> move 'MemberData03_03' to 'i:\MemberData03_03.NDF',
> move 'MemberData04_01' to 'j:\MemberData04_01.NDF',
> move 'MemberData04_02' to 'f:\MemberData04_02.NDF',
> move 'MemberData04_03' to 'g:\MemberData04_03.NDF',
> move 'MemberIndex02_01' to 'h:\MemberIndex02_01.NDF',
> move 'MemberIndex02_02' to 'i:\MemberIndex02_02.NDF',
> move 'MemberIndex03_01' to 'j:\MemberIndex03_01.NDF',
> move 'MemberIndex03_02' to 'f:\MemberIndex03_02.NDF',
> move 'memberIndex04_01' to 'g:\MemberIndex04_01.NDF',
> move 'MemberIndex04_02' to 'h:\MemberIndex04_02.NDF',
> move 'MemberData05_01' to 'i:\MemberData05_01.NDF',
> move 'MemberData05_02' to 'j:\MemberData05_02.NDF',
> move 'Member_Log' to 'u:\Member_Log.LDF',
> move 'member_1_Log' to 'u:\Member_Log2'
> Thanks in advance,
> Gary Abbott
>|||I get the exact same error trying to run anyone of those
commands. I am now doing a new backup to only one backup
file. I'll try that.
Gary

>--Original Message--
>Hi,
>Did you tried RESTORE FILELISTONLY command to identify
the Logical and
>physical names as well
>as try RESTORE VERIFYONLY command .
>Syntax of both commands:
>
> RESTORE FILELISTONLY FROM
disk='c:\backup\dbname.bak'
> RESTORE VERIFYONLY FROM disk='c:\backup\dbname.bak'
>
>
>Thanks
>Hari
>MCDBA
>
>"Gary Abbott" <anonymous@.discussions.microsoft.com> wrote
in message
> news:1120901c40f5c$29dd3fb0$a101280a@.phx
.gbl...
when
following
and
>
>.
>

Wednesday, March 7, 2012

HELP - Redo Log Error

All,
SQL 2000 sp3, Server 2000 sp3
below is the error I got when trying to do a restore. I've read that
going to sp3 should help, but I'm already there. What causes this
problem?
Executed as user: WINFREESTUFF\sqladmin. Deleting database file
'h:\wfsundo.bak'. [SQLSTATE 01000] (Message 3738) Processed 4287 pages
for database 'wfs', file 'wfs_log' on file 1. [SQLSTATE 01000] (Message
4035) Could not redo log record (161973:16059:9), for transaction ID
(0:-2134161807), on page (13:1408224), database 'wfs' (8). Page: LSN = (161973:12114:4), type = 1. Log: OpCode = 3, context 2, PrevPageLSN:
(138073:47239:227). [SQLSTATE HY000] (Error 3456). The step failed.
Thanks All,
Gary
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!I guess this is the same post as yesterday? As no-one has answered, I suggest you first search
KB and if you don't find anything there, open a case with MS PSS. To my understanding of SQL
Server (and with the little info we have), this shouldn't be happening.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Gary Abbott" <snyper@.uniserve.com> wrote in message
news:uxAghk1RDHA.704@.tk2msftngp13.phx.gbl...
> All,
> SQL 2000 sp3, Server 2000 sp3
> below is the error I got when trying to do a restore. I've read that
> going to sp3 should help, but I'm already there. What causes this
> problem?
> Executed as user: WINFREESTUFF\sqladmin. Deleting database file
> 'h:\wfsundo.bak'. [SQLSTATE 01000] (Message 3738) Processed 4287 pages
> for database 'wfs', file 'wfs_log' on file 1. [SQLSTATE 01000] (Message
> 4035) Could not redo log record (161973:16059:9), for transaction ID
> (0:-2134161807), on page (13:1408224), database 'wfs' (8). Page: LSN => (161973:12114:4), type = 1. Log: OpCode = 3, context 2, PrevPageLSN:
> (138073:47239:227). [SQLSTATE HY000] (Error 3456). The step failed.
>
> Thanks All,
> Gary
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!|||Tibor,
Thanks, it is the same post. I have had this before with no clear
resolution from microsoft. This is the fourth time I've had it since
I've been here. Last time they said it was because there was no checkdb
ran in months. So I accepted that, but now I do them every week and
still get the same problem. I'm calling MS again, to see what they
suggest this time. The documentation in KB says its due to an index
being built when the backup runs, I schedule my jobs very carefully. To
avoid such collisions, I only rebuild indexes on the weekends when most
of my users aren't using my servers. I must admit, over the years I have
not run into this problem before and think it may be hardware related.
Thanks All,
Gary
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Monday, February 27, 2012

Help - Corrupted SQL Server 2K Log. Is this serious

Hello,

I have a SS2K (SP3) that is appending very wierd looking error messages
to the SQL Server Log (Current). The messages are not formatted as
other log entries. The messages suggest some kinda dump information.
The messages have the following characteristics:

Date Information is invalid
Source information is invalid
Message information is strange

The following is a message that appear in my current SQL Server Log

DATE:78008454
SOURCE: Module(MSVCRT+
Message (_endthread+000000C1)

There are many messages like this in the log.

Is this serious?

Thanks - CoviCovi (covilc@.earthlink.net) writes:
> I have a SS2K (SP3) that is appending very wierd looking error messages
> to the SQL Server Log (Current). The messages are not formatted as
> other log entries. The messages suggest some kinda dump information.
> The messages have the following characteristics:
> Date Information is invalid
> Source information is invalid
> Message information is strange
> The following is a message that appear in my current SQL Server Log
>
> DATE:78008454
> SOURCE: Module(MSVCRT+
> Message (_endthread+000000C1)
> There are many messages like this in the log.
> Is this serious?

When a connection runs into an execution error, one that really should
not occur, for instance an access violation, SQL Server terminates the
connection and leaves a stack dump in the error log. Most such dumps
are due to bugs in SQL Server, and could come from specific queries.
Hardware errors could be involved too. In the latter case, there is
certainly cause for alarm. If you want to sleep better at night, you
could run a DBCC CHECKDB on the database related to the dumps.

But stackdumps can occur on healthy machines too.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Monday, March 19, 2012

Help , Several Connections , Port : 1433

Help , Several Connections , Port : 1433

Help , Several Connections , Port : 1433

Monday, March 12, 2012

Help !

Friday, March 9, 2012

Help - Very Odd Restore Issues

Wednesday, March 7, 2012

HELP - Redo Log Error

Monday, February 27, 2012

Help - Corrupted SQL Server 2K Log. Is this serious

Absurd project

Blog Archive

About Me