Hi,
After restore i get this error in MSSQL server 2000 (SP4)
Error 913: Could not find database ID119. Database may not be activated or
may be in transitionw
I can not find out wath could be wrong the only thing that is diffrent in
SYSDatabases i that the version column is NULL all other databases have a
version number 539 the status is 1077936153.
We did not get any error during restore the .bak fil is from an other SQL
server SP4 and the database works there. We have moved databases before
without any problem.
Marcin S.
When and where you are getting that error?
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Marcin S." <MarcinS@.discussions.microsoft.com> wrote in message
news:C8A32931-5D30-4B37-9EF9-68280A564AAC@.microsoft.com...
Hi,
After restore i get this error in MSSQL server 2000 (SP4)
Error 913: Could not find database ID119. Database may not be activated or
may be in transitionw
I can not find out wath could be wrong the only thing that is diffrent in
SYSDatabases i that the version column is NULL all other databases have a
version number 539 the status is 1077936153.
We did not get any error during restore the .bak fil is from an other SQL
server SP4 and the database works there. We have moved databases before
without any problem.
Marcin S.
Showing posts with label sp4. Show all posts
Showing posts with label sp4. Show all posts
Thursday, March 29, 2012
Error 913: Could not find database ID119. Database may not be acti
Hi,
After restore i get this error in MSSQL server 2000 (SP4)
Error 913: Could not find database ID119. Database may not be activated or
may be in transitionw
I can not find out wath could be wrong the only thing that is diffrent in
SYSDatabases i that the version column is NULL all other databases have a
version number 539 the status is 1077936153.
We did not get any error during restore the .bak fil is from an other SQL
server SP4 and the database works there. We have moved databases before
without any problem.
--
Marcin S.When and where you are getting that error?
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Marcin S." <MarcinS@.discussions.microsoft.com> wrote in message
news:C8A32931-5D30-4B37-9EF9-68280A564AAC@.microsoft.com...
Hi,
After restore i get this error in MSSQL server 2000 (SP4)
Error 913: Could not find database ID119. Database may not be activated or
may be in transitionw
I can not find out wath could be wrong the only thing that is diffrent in
SYSDatabases i that the version column is NULL all other databases have a
version number 539 the status is 1077936153.
We did not get any error during restore the .bak fil is from an other SQL
server SP4 and the database works there. We have moved databases before
without any problem.
Marcin S.|||I get this error all the time if i try to list tables or when i try to view
propperties, just anywhere when i try to do some thind with this databas.
I can see the database in DB list, it is in the SYSDATABASES but it is
inaccessible
BUT!
When i run : DBCC CHECKDB ('someDB') i then get
Server: Msg 911, Level 16, State 1, Line 1
Could not locate entry in sysdatabases for database 'MSSQL100011'. No entry
found with that name. Make sure that the name is entered correctly.
but a selects in SYSDATABASES says that it exists... strange
And as i wrote i can restore any database that I backup on the serbver but
when moving this from an other Working SQL server. The Restore process is
done successfull without any error.
--
Marcin S.
"Narayana Vyas Kondreddi" wrote:
> When and where you are getting that error?
> --
> HTH,
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "Marcin S." <MarcinS@.discussions.microsoft.com> wrote in message
> news:C8A32931-5D30-4B37-9EF9-68280A564AAC@.microsoft.com...
> Hi,
> After restore i get this error in MSSQL server 2000 (SP4)
> Error 913: Could not find database ID119. Database may not be activated or
> may be in transitionw
> I can not find out wath could be wrong the only thing that is diffrent in
> SYSDatabases i that the version column is NULL all other databases have a
> version number 539 the status is 1077936153.
> We did not get any error during restore the .bak fil is from an other SQL
> server SP4 and the database works there. We have moved databases before
> without any problem.
>
> --
> Marcin S.
>
>sql
After restore i get this error in MSSQL server 2000 (SP4)
Error 913: Could not find database ID119. Database may not be activated or
may be in transitionw
I can not find out wath could be wrong the only thing that is diffrent in
SYSDatabases i that the version column is NULL all other databases have a
version number 539 the status is 1077936153.
We did not get any error during restore the .bak fil is from an other SQL
server SP4 and the database works there. We have moved databases before
without any problem.
--
Marcin S.When and where you are getting that error?
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Marcin S." <MarcinS@.discussions.microsoft.com> wrote in message
news:C8A32931-5D30-4B37-9EF9-68280A564AAC@.microsoft.com...
Hi,
After restore i get this error in MSSQL server 2000 (SP4)
Error 913: Could not find database ID119. Database may not be activated or
may be in transitionw
I can not find out wath could be wrong the only thing that is diffrent in
SYSDatabases i that the version column is NULL all other databases have a
version number 539 the status is 1077936153.
We did not get any error during restore the .bak fil is from an other SQL
server SP4 and the database works there. We have moved databases before
without any problem.
Marcin S.|||I get this error all the time if i try to list tables or when i try to view
propperties, just anywhere when i try to do some thind with this databas.
I can see the database in DB list, it is in the SYSDATABASES but it is
inaccessible
BUT!
When i run : DBCC CHECKDB ('someDB') i then get
Server: Msg 911, Level 16, State 1, Line 1
Could not locate entry in sysdatabases for database 'MSSQL100011'. No entry
found with that name. Make sure that the name is entered correctly.
but a selects in SYSDATABASES says that it exists... strange
And as i wrote i can restore any database that I backup on the serbver but
when moving this from an other Working SQL server. The Restore process is
done successfull without any error.
--
Marcin S.
"Narayana Vyas Kondreddi" wrote:
> When and where you are getting that error?
> --
> HTH,
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "Marcin S." <MarcinS@.discussions.microsoft.com> wrote in message
> news:C8A32931-5D30-4B37-9EF9-68280A564AAC@.microsoft.com...
> Hi,
> After restore i get this error in MSSQL server 2000 (SP4)
> Error 913: Could not find database ID119. Database may not be activated or
> may be in transitionw
> I can not find out wath could be wrong the only thing that is diffrent in
> SYSDatabases i that the version column is NULL all other databases have a
> version number 539 the status is 1077936153.
> We did not get any error during restore the .bak fil is from an other SQL
> server SP4 and the database works there. We have moved databases before
> without any problem.
>
> --
> Marcin S.
>
>sql
Error 913: Could not find database ID119. Database may not be acti
Hi,
After restore i get this error in MSSQL server 2000 (SP4)
Error 913: Could not find database ID119. Database may not be activated or
may be in transitionw
I can not find out wath could be wrong the only thing that is diffrent in
SYSDatabases i that the version column is NULL all other databases have a
version number 539 the status is 1077936153.
We did not get any error during restore the .bak fil is from an other SQL
server SP4 and the database works there. We have moved databases before
without any problem.
Marcin S.When and where you are getting that error?
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Marcin S." <MarcinS@.discussions.microsoft.com> wrote in message
news:C8A32931-5D30-4B37-9EF9-68280A564AAC@.microsoft.com...
Hi,
After restore i get this error in MSSQL server 2000 (SP4)
Error 913: Could not find database ID119. Database may not be activated or
may be in transitionw
I can not find out wath could be wrong the only thing that is diffrent in
SYSDatabases i that the version column is NULL all other databases have a
version number 539 the status is 1077936153.
We did not get any error during restore the .bak fil is from an other SQL
server SP4 and the database works there. We have moved databases before
without any problem.
Marcin S.
After restore i get this error in MSSQL server 2000 (SP4)
Error 913: Could not find database ID119. Database may not be activated or
may be in transitionw
I can not find out wath could be wrong the only thing that is diffrent in
SYSDatabases i that the version column is NULL all other databases have a
version number 539 the status is 1077936153.
We did not get any error during restore the .bak fil is from an other SQL
server SP4 and the database works there. We have moved databases before
without any problem.
Marcin S.When and where you are getting that error?
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Marcin S." <MarcinS@.discussions.microsoft.com> wrote in message
news:C8A32931-5D30-4B37-9EF9-68280A564AAC@.microsoft.com...
Hi,
After restore i get this error in MSSQL server 2000 (SP4)
Error 913: Could not find database ID119. Database may not be activated or
may be in transitionw
I can not find out wath could be wrong the only thing that is diffrent in
SYSDatabases i that the version column is NULL all other databases have a
version number 539 the status is 1077936153.
We did not get any error during restore the .bak fil is from an other SQL
server SP4 and the database works there. We have moved databases before
without any problem.
Marcin S.
Monday, March 26, 2012
Error 823,17903,17951 server 7 sp2- UPDATE
Regarding the above errors, I decided to apply sp4. A copy of the database was made and placed on a test server and now we cannot start the SQL Server. I have checked the registration and all seems fine. Any ideas ?Check the contents of the ERRORLOG file in LOGS directory as well as Application and System errorlog in Event Viewer and let us know what you see there.|||You need to identify what the base cause of this problem is. The first step to doing that is reviewing all errors on the machine in question.|||The above problem is now okay. DBAs from another Department came over and assisted with the problem. Because we had problems moving the data to another location, we decided to make a copy of the database and run DBCC repair on the production database. This fixed the problem and only a few records were lost.
Thanks to all for your assistance.
Thanks to all for your assistance.
Thursday, March 22, 2012
error 8198
sql2k sp3
win2k sp4
Im trying to create a Pull Subscription for replication and get "Error 8198:
Could not obtain information about Windows NT group/ user 'domain/ user'".
I read this:
http://support.microsoft.com/?kbid=834124
But both boxes are in the same domain and the same subnet. Both use the same
domain admin account for SQL Server and the Agent accounts.
I also read this:
http://support.microsoft.com/?kbid=838460
But Im not about to install sp4 Beta on anything.
Is there anything else I can do?
TIA, ChrisRright click on your agent and make the agent owner sa. Restart your job.
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"ChrisR" <noemail@.bla.com> wrote in message
news:OZAuC21SFHA.2256@.tk2msftngp13.phx.gbl...
> sql2k sp3
> win2k sp4
> Im trying to create a Pull Subscription for replication and get "Error
8198:
> Could not obtain information about Windows NT group/ user 'domain/ user'".
> I read this:
> http://support.microsoft.com/?kbid=834124
> But both boxes are in the same domain and the same subnet. Both use the
same
> domain admin account for SQL Server and the Agent accounts.
> I also read this:
> http://support.microsoft.com/?kbid=838460
> But Im not about to install sp4 Beta on anything.
> Is there anything else I can do?
> TIA, ChrisR
>|||Which Agent are you referring too? All of the jobs are owned by SA.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23RPeZF2SFHA.3544@.TK2MSFTNGP12.phx.gbl...
> right click on your agent and make the agent owner sa. Restart your job.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "ChrisR" <noemail@.bla.com> wrote in message
> news:OZAuC21SFHA.2256@.tk2msftngp13.phx.gbl...
>> sql2k sp3
>> win2k sp4
>> Im trying to create a Pull Subscription for replication and get "Error
> 8198:
>> Could not obtain information about Windows NT group/ user 'domain/
>> user'".
>> I read this:
>> http://support.microsoft.com/?kbid=834124
>> But both boxes are in the same domain and the same subnet. Both use the
> same
>> domain admin account for SQL Server and the Agent accounts.
>> I also read this:
>> http://support.microsoft.com/?kbid=838460
>> But Im not about to install sp4 Beta on anything.
>> Is there anything else I can do?
>> TIA, ChrisR
>>
>
win2k sp4
Im trying to create a Pull Subscription for replication and get "Error 8198:
Could not obtain information about Windows NT group/ user 'domain/ user'".
I read this:
http://support.microsoft.com/?kbid=834124
But both boxes are in the same domain and the same subnet. Both use the same
domain admin account for SQL Server and the Agent accounts.
I also read this:
http://support.microsoft.com/?kbid=838460
But Im not about to install sp4 Beta on anything.
Is there anything else I can do?
TIA, ChrisRright click on your agent and make the agent owner sa. Restart your job.
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"ChrisR" <noemail@.bla.com> wrote in message
news:OZAuC21SFHA.2256@.tk2msftngp13.phx.gbl...
> sql2k sp3
> win2k sp4
> Im trying to create a Pull Subscription for replication and get "Error
8198:
> Could not obtain information about Windows NT group/ user 'domain/ user'".
> I read this:
> http://support.microsoft.com/?kbid=834124
> But both boxes are in the same domain and the same subnet. Both use the
same
> domain admin account for SQL Server and the Agent accounts.
> I also read this:
> http://support.microsoft.com/?kbid=838460
> But Im not about to install sp4 Beta on anything.
> Is there anything else I can do?
> TIA, ChrisR
>|||Which Agent are you referring too? All of the jobs are owned by SA.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23RPeZF2SFHA.3544@.TK2MSFTNGP12.phx.gbl...
> right click on your agent and make the agent owner sa. Restart your job.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "ChrisR" <noemail@.bla.com> wrote in message
> news:OZAuC21SFHA.2256@.tk2msftngp13.phx.gbl...
>> sql2k sp3
>> win2k sp4
>> Im trying to create a Pull Subscription for replication and get "Error
> 8198:
>> Could not obtain information about Windows NT group/ user 'domain/
>> user'".
>> I read this:
>> http://support.microsoft.com/?kbid=834124
>> But both boxes are in the same domain and the same subnet. Both use the
> same
>> domain admin account for SQL Server and the Agent accounts.
>> I also read this:
>> http://support.microsoft.com/?kbid=838460
>> But Im not about to install sp4 Beta on anything.
>> Is there anything else I can do?
>> TIA, ChrisR
>>
>
error '800a03eb' Type mismatch
Maintaining database website,its running ASP pages on windows 2003 server with SQL server 2000. I have upgraded SP2 for SQL server to SP4 in maintance process.
The problem accur with some ASP pages are
server_errors [server_Errors] GetErrorMessage [serverSERVER version 1.0.0] error '800a03eb' Type mismatch
/server/asp/cmfls/errorconfirmation.asp, line
There may be permission /security issues related with database.help me to troubleshoot my problem.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=395969&SiteID=1Wednesday, March 21, 2012
Error 7399 When trying to link an Access database to SqlServer 2K
Hi,
I'm trying to add an Access Database as a linked server to an SqlServer 2000
SP4. Both the server and the access database run on the same PC. The Access
database is protected by a Database password. It is no workgroup password
involved.
After a lot of testing with Visual Basic 6 ADO connection strings I reach to
the following string that is able to open the password protected database by
using VB:
"Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\Program
Files\AccessDB\mydatabase.mdb;Jet OLEDB:Database Password=xxxx"
But when using this string in the definition of the linked server in the
Enterprise Manager I get the following error when trying to browser the
tables of the linked server:
Error 7399: OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error
OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
IDBInitialize::Initialize returned 0x80004005: ].
I tryed both running the SqlServer as local system account and as a Windows
domain account with domain admin priviledges.
I found also the article http://support.microsoft.com/kb/814398 that
describes a similar problem but that solution did not worked for me.
Any hint is welcomed
Thanks in advance
SammyHi Sammy
You may want to check through http://ask.support.microsoft.com/kb/306518/
Have you checked if the dropping the password from the database works?
You may want to see if moving the database and the security database to a
different directory helps.
John
"SammyBar" wrote:
> Hi,
> I'm trying to add an Access Database as a linked server to an SqlServer 2000
> SP4. Both the server and the access database run on the same PC. The Access
> database is protected by a Database password. It is no workgroup password
> involved.
> After a lot of testing with Visual Basic 6 ADO connection strings I reach to
> the following string that is able to open the password protected database by
> using VB:
> "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\Program
> Files\AccessDB\mydatabase.mdb;Jet OLEDB:Database Password=xxxx"
> But when using this string in the definition of the linked server in the
> Enterprise Manager I get the following error when trying to browser the
> tables of the linked server:
> Error 7399: OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error
> OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
> IDBInitialize::Initialize returned 0x80004005: ].
> I tryed both running the SqlServer as local system account and as a Windows
> domain account with domain admin priviledges.
> I found also the article http://support.microsoft.com/kb/814398 that
> describes a similar problem but that solution did not worked for me.
> Any hint is welcomed
> Thanks in advance
> Sammy
>
>
I'm trying to add an Access Database as a linked server to an SqlServer 2000
SP4. Both the server and the access database run on the same PC. The Access
database is protected by a Database password. It is no workgroup password
involved.
After a lot of testing with Visual Basic 6 ADO connection strings I reach to
the following string that is able to open the password protected database by
using VB:
"Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\Program
Files\AccessDB\mydatabase.mdb;Jet OLEDB:Database Password=xxxx"
But when using this string in the definition of the linked server in the
Enterprise Manager I get the following error when trying to browser the
tables of the linked server:
Error 7399: OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error
OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
IDBInitialize::Initialize returned 0x80004005: ].
I tryed both running the SqlServer as local system account and as a Windows
domain account with domain admin priviledges.
I found also the article http://support.microsoft.com/kb/814398 that
describes a similar problem but that solution did not worked for me.
Any hint is welcomed
Thanks in advance
SammyHi Sammy
You may want to check through http://ask.support.microsoft.com/kb/306518/
Have you checked if the dropping the password from the database works?
You may want to see if moving the database and the security database to a
different directory helps.
John
"SammyBar" wrote:
> Hi,
> I'm trying to add an Access Database as a linked server to an SqlServer 2000
> SP4. Both the server and the access database run on the same PC. The Access
> database is protected by a Database password. It is no workgroup password
> involved.
> After a lot of testing with Visual Basic 6 ADO connection strings I reach to
> the following string that is able to open the password protected database by
> using VB:
> "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\Program
> Files\AccessDB\mydatabase.mdb;Jet OLEDB:Database Password=xxxx"
> But when using this string in the definition of the linked server in the
> Enterprise Manager I get the following error when trying to browser the
> tables of the linked server:
> Error 7399: OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error
> OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
> IDBInitialize::Initialize returned 0x80004005: ].
> I tryed both running the SqlServer as local system account and as a Windows
> domain account with domain admin priviledges.
> I found also the article http://support.microsoft.com/kb/814398 that
> describes a similar problem but that solution did not worked for me.
> Any hint is welcomed
> Thanks in advance
> Sammy
>
>
Error 7391 when distributed transaction started
Node 1:
Windows 2003 Server Standar Edition SP1
SQL Server 2005 Standar Edition
Node 2:
Windows 2000 Server SP4
SQL Server 2000 Standar Edition SP3a
Node 1 have node 2 like "linked server", node 2 have node 1 like "linked
server" too.
Both nodes use Microsoft OLE DB Provider for SQL Server.
Node 1 begins a distributed transaction vs Node 2.
Transaction KO with
"Server: Msg 7391, Level 16, State 1, Line 1
The operation could not be performed because the OLE DB provider 'SQLOLEDB'
was unable to begin a distributed transaction.
OLE/DB provider returned message: New transaction cannot enlist in the
specified transaction coordinator. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d00a]."
MS DTS is configured in Node 1 like microsoft said in
http://suppport.microsoftl.com/default.aspx?scid=kb;en-us;329332
If I change Node1 with Windows 2000 Server Standard Edition and SQL Server
2000 SP3a, the distribution transaction run OK.
Thanks a lot.Hi
Windows 2003 has more secure defaults than Windows 2000 therefore it is
probably something that has not been configured that is causing the problem
Check out http://support.microsoft.com/kb/839279/
http://support.microsoft.com/kb/191168/
http://support.microsoft.com/kb/306843/
http://support.microsoft.com/kb/306843/
http://support.microsoft.com/kb/329332
http://support.microsoft.com/kb/306212
You can use DTCPing to check it can communicate with the server
http://download.microsoft.com/download/d/0/0/d00c8f6b-135d-4441-a97b-9de16a1935c1/dtcping.exe
John
"FRF" wrote:
> Node 1:
> Windows 2003 Server Standar Edition SP1
> SQL Server 2005 Standar Edition
> Node 2:
> Windows 2000 Server SP4
> SQL Server 2000 Standar Edition SP3a
> Node 1 have node 2 like "linked server", node 2 have node 1 like "linked
> server" too.
> Both nodes use Microsoft OLE DB Provider for SQL Server.
> Node 1 begins a distributed transaction vs Node 2.
> Transaction KO with
> "Server: Msg 7391, Level 16, State 1, Line 1
> The operation could not be performed because the OLE DB provider 'SQLOLEDB'
> was unable to begin a distributed transaction.
> OLE/DB provider returned message: New transaction cannot enlist in the
> specified transaction coordinator. ]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
> ITransactionJoin::JoinTransaction returned 0x8004d00a]."
> MS DTS is configured in Node 1 like microsoft said in
> http://suppport.microsoftl.com/default.aspx?scid=kb;en-us;329332
> If I change Node1 with Windows 2000 Server Standard Edition and SQL Server
> 2000 SP3a, the distribution transaction run OK.
> Thanks a lot.
>
Windows 2003 Server Standar Edition SP1
SQL Server 2005 Standar Edition
Node 2:
Windows 2000 Server SP4
SQL Server 2000 Standar Edition SP3a
Node 1 have node 2 like "linked server", node 2 have node 1 like "linked
server" too.
Both nodes use Microsoft OLE DB Provider for SQL Server.
Node 1 begins a distributed transaction vs Node 2.
Transaction KO with
"Server: Msg 7391, Level 16, State 1, Line 1
The operation could not be performed because the OLE DB provider 'SQLOLEDB'
was unable to begin a distributed transaction.
OLE/DB provider returned message: New transaction cannot enlist in the
specified transaction coordinator. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d00a]."
MS DTS is configured in Node 1 like microsoft said in
http://suppport.microsoftl.com/default.aspx?scid=kb;en-us;329332
If I change Node1 with Windows 2000 Server Standard Edition and SQL Server
2000 SP3a, the distribution transaction run OK.
Thanks a lot.Hi
Windows 2003 has more secure defaults than Windows 2000 therefore it is
probably something that has not been configured that is causing the problem
Check out http://support.microsoft.com/kb/839279/
http://support.microsoft.com/kb/191168/
http://support.microsoft.com/kb/306843/
http://support.microsoft.com/kb/306843/
http://support.microsoft.com/kb/329332
http://support.microsoft.com/kb/306212
You can use DTCPing to check it can communicate with the server
http://download.microsoft.com/download/d/0/0/d00c8f6b-135d-4441-a97b-9de16a1935c1/dtcping.exe
John
"FRF" wrote:
> Node 1:
> Windows 2003 Server Standar Edition SP1
> SQL Server 2005 Standar Edition
> Node 2:
> Windows 2000 Server SP4
> SQL Server 2000 Standar Edition SP3a
> Node 1 have node 2 like "linked server", node 2 have node 1 like "linked
> server" too.
> Both nodes use Microsoft OLE DB Provider for SQL Server.
> Node 1 begins a distributed transaction vs Node 2.
> Transaction KO with
> "Server: Msg 7391, Level 16, State 1, Line 1
> The operation could not be performed because the OLE DB provider 'SQLOLEDB'
> was unable to begin a distributed transaction.
> OLE/DB provider returned message: New transaction cannot enlist in the
> specified transaction coordinator. ]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
> ITransactionJoin::JoinTransaction returned 0x8004d00a]."
> MS DTS is configured in Node 1 like microsoft said in
> http://suppport.microsoftl.com/default.aspx?scid=kb;en-us;329332
> If I change Node1 with Windows 2000 Server Standard Edition and SQL Server
> 2000 SP3a, the distribution transaction run OK.
> Thanks a lot.
>
Monday, March 19, 2012
Error 7102
After installation of the SP4 on SQL Server 2000 I began to receive seldom
error in log-file:
Error 7102 Serverity 20 State 0
SQL Server Internal Error. Text manager cannot continue with current
statement.
OS: Windows 2000 Advanced Server SP4.Hi white,
Welcome to use MSDN Managed Newsgroup Support.
From your description, my understanding of this issue is: You get the Error
7102 in the SQL Server 2000 SP4 Error log. If I misunderstood your concern,
please feel free to point it out.
Error 7102 is a general error. Would you please provide some detail
information to narrow down the issue?
1. Using DBCC CHECKDB to see is there any error messages.
2. What do you get in the Application and System event log? Would your
please post it here?
3. Are you able to trace what the database is doing when you get this
error?
Please let us know the result. I look forward your reply.
Wei Lu
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Lu!
1. DBCC CHECKDB is executed every night. Error messages are absent.
2. There are no error and warning messages in the Application and System
event log. To post there is nothing.
3. 7102 error messages arises seldom. Trace is now turn on.
"Wei Lu" wrote:
> Hi white,
> Welcome to use MSDN Managed Newsgroup Support.
> From your description, my understanding of this issue is: You get the Erro
r
> 7102 in the SQL Server 2000 SP4 Error log. If I misunderstood your concern
,
> please feel free to point it out.
> Error 7102 is a general error. Would you please provide some detail
> information to narrow down the issue?
> 1. Using DBCC CHECKDB to see is there any error messages.
> 2. What do you get in the Application and System event log? Would you
r
> please post it here?
> 3. Are you able to trace what the database is doing when you get this
> error?
> Please let us know the result. I look forward your reply.
> Wei Lu
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ========================================
=============
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>|||Hi white,
Thanks for the update. Please gather the trace and to see what have you
done before these error arised.
Wei Lu
Microsoft Online Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
error in log-file:
Error 7102 Serverity 20 State 0
SQL Server Internal Error. Text manager cannot continue with current
statement.
OS: Windows 2000 Advanced Server SP4.Hi white,
Welcome to use MSDN Managed Newsgroup Support.
From your description, my understanding of this issue is: You get the Error
7102 in the SQL Server 2000 SP4 Error log. If I misunderstood your concern,
please feel free to point it out.
Error 7102 is a general error. Would you please provide some detail
information to narrow down the issue?
1. Using DBCC CHECKDB to see is there any error messages.
2. What do you get in the Application and System event log? Would your
please post it here?
3. Are you able to trace what the database is doing when you get this
error?
Please let us know the result. I look forward your reply.
Wei Lu
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Lu!
1. DBCC CHECKDB is executed every night. Error messages are absent.
2. There are no error and warning messages in the Application and System
event log. To post there is nothing.
3. 7102 error messages arises seldom. Trace is now turn on.
"Wei Lu" wrote:
> Hi white,
> Welcome to use MSDN Managed Newsgroup Support.
> From your description, my understanding of this issue is: You get the Erro
r
> 7102 in the SQL Server 2000 SP4 Error log. If I misunderstood your concern
,
> please feel free to point it out.
> Error 7102 is a general error. Would you please provide some detail
> information to narrow down the issue?
> 1. Using DBCC CHECKDB to see is there any error messages.
> 2. What do you get in the Application and System event log? Would you
r
> please post it here?
> 3. Are you able to trace what the database is doing when you get this
> error?
> Please let us know the result. I look forward your reply.
> Wei Lu
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ========================================
=============
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>|||Hi white,
Thanks for the update. Please gather the trace and to see what have you
done before these error arised.
Wei Lu
Microsoft Online Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
Error 7102
After installation of the SP4 on SQL Server 2000 I began to receive seldom
error in log-file:
Error 7102 Serverity 20 State 0
SQL Server Internal Error. Text manager cannot continue with current
statement.
OS: Windows 2000 Advanced Server SP4.Hi white,
Welcome to use MSDN Managed Newsgroup Support.
From your description, my understanding of this issue is: You get the Error
7102 in the SQL Server 2000 SP4 Error log. If I misunderstood your concern,
please feel free to point it out.
Error 7102 is a general error. Would you please provide some detail
information to narrow down the issue?
1. Using DBCC CHECKDB to see is there any error messages.
2. What do you get in the Application and System event log? Would your
please post it here?
3. Are you able to trace what the database is doing when you get this
error?
Please let us know the result. I look forward your reply.
Wei Lu
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Lu!
1. DBCC CHECKDB is executed every night. Error messages are absent.
2. There are no error and warning messages in the Application and System
event log. To post there is nothing.
3. 7102 error messages arises seldom. Trace is now turn on.
"Wei Lu" wrote:
> Hi white,
> Welcome to use MSDN Managed Newsgroup Support.
> From your description, my understanding of this issue is: You get the Error
> 7102 in the SQL Server 2000 SP4 Error log. If I misunderstood your concern,
> please feel free to point it out.
> Error 7102 is a general error. Would you please provide some detail
> information to narrow down the issue?
> 1. Using DBCC CHECKDB to see is there any error messages.
> 2. What do you get in the Application and System event log? Would your
> please post it here?
> 3. Are you able to trace what the database is doing when you get this
> error?
> Please let us know the result. I look forward your reply.
> Wei Lu
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> =====================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hi white,
Thanks for the update. Please gather the trace and to see what have you
done before these error arised.
Wei Lu
Microsoft Online Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
error in log-file:
Error 7102 Serverity 20 State 0
SQL Server Internal Error. Text manager cannot continue with current
statement.
OS: Windows 2000 Advanced Server SP4.Hi white,
Welcome to use MSDN Managed Newsgroup Support.
From your description, my understanding of this issue is: You get the Error
7102 in the SQL Server 2000 SP4 Error log. If I misunderstood your concern,
please feel free to point it out.
Error 7102 is a general error. Would you please provide some detail
information to narrow down the issue?
1. Using DBCC CHECKDB to see is there any error messages.
2. What do you get in the Application and System event log? Would your
please post it here?
3. Are you able to trace what the database is doing when you get this
error?
Please let us know the result. I look forward your reply.
Wei Lu
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Lu!
1. DBCC CHECKDB is executed every night. Error messages are absent.
2. There are no error and warning messages in the Application and System
event log. To post there is nothing.
3. 7102 error messages arises seldom. Trace is now turn on.
"Wei Lu" wrote:
> Hi white,
> Welcome to use MSDN Managed Newsgroup Support.
> From your description, my understanding of this issue is: You get the Error
> 7102 in the SQL Server 2000 SP4 Error log. If I misunderstood your concern,
> please feel free to point it out.
> Error 7102 is a general error. Would you please provide some detail
> information to narrow down the issue?
> 1. Using DBCC CHECKDB to see is there any error messages.
> 2. What do you get in the Application and System event log? Would your
> please post it here?
> 3. Are you able to trace what the database is doing when you get this
> error?
> Please let us know the result. I look forward your reply.
> Wei Lu
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> =====================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hi white,
Thanks for the update. Please gather the trace and to see what have you
done before these error arised.
Wei Lu
Microsoft Online Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
Error 7102
After installation of the SP4 on SQL Server 2000 I began to receive seldom
error in log-file:
Error 7102 Serverity 20 State 0
SQL Server Internal Error. Text manager cannot continue with current
statement.
OS: Windows 2000 Advanced Server SP4.
Hi white,
Welcome to use MSDN Managed Newsgroup Support.
From your description, my understanding of this issue is: You get the Error
7102 in the SQL Server 2000 SP4 Error log. If I misunderstood your concern,
please feel free to point it out.
Error 7102 is a general error. Would you please provide some detail
information to narrow down the issue?
1. Using DBCC CHECKDB to see is there any error messages.
2. What do you get in the Application and System event log? Would your
please post it here?
3. Are you able to trace what the database is doing when you get this
error?
Please let us know the result. I look forward your reply.
Wei Lu
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi Lu!
1. DBCC CHECKDB is executed every night. Error messages are absent.
2. There are no error and warning messages in the Application and System
event log. To post there is nothing.
3. 7102 error messages arises seldom. Trace is now turn on.
"Wei Lu" wrote:
> Hi white,
> Welcome to use MSDN Managed Newsgroup Support.
> From your description, my understanding of this issue is: You get the Error
> 7102 in the SQL Server 2000 SP4 Error log. If I misunderstood your concern,
> please feel free to point it out.
> Error 7102 is a general error. Would you please provide some detail
> information to narrow down the issue?
> 1. Using DBCC CHECKDB to see is there any error messages.
> 2. What do you get in the Application and System event log? Would your
> please post it here?
> 3. Are you able to trace what the database is doing when you get this
> error?
> Please let us know the result. I look forward your reply.
> Wei Lu
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ================================================== ===
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
|||Hi white,
Thanks for the update. Please gather the trace and to see what have you
done before these error arised.
Wei Lu
Microsoft Online Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
error in log-file:
Error 7102 Serverity 20 State 0
SQL Server Internal Error. Text manager cannot continue with current
statement.
OS: Windows 2000 Advanced Server SP4.
Hi white,
Welcome to use MSDN Managed Newsgroup Support.
From your description, my understanding of this issue is: You get the Error
7102 in the SQL Server 2000 SP4 Error log. If I misunderstood your concern,
please feel free to point it out.
Error 7102 is a general error. Would you please provide some detail
information to narrow down the issue?
1. Using DBCC CHECKDB to see is there any error messages.
2. What do you get in the Application and System event log? Would your
please post it here?
3. Are you able to trace what the database is doing when you get this
error?
Please let us know the result. I look forward your reply.
Wei Lu
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi Lu!
1. DBCC CHECKDB is executed every night. Error messages are absent.
2. There are no error and warning messages in the Application and System
event log. To post there is nothing.
3. 7102 error messages arises seldom. Trace is now turn on.
"Wei Lu" wrote:
> Hi white,
> Welcome to use MSDN Managed Newsgroup Support.
> From your description, my understanding of this issue is: You get the Error
> 7102 in the SQL Server 2000 SP4 Error log. If I misunderstood your concern,
> please feel free to point it out.
> Error 7102 is a general error. Would you please provide some detail
> information to narrow down the issue?
> 1. Using DBCC CHECKDB to see is there any error messages.
> 2. What do you get in the Application and System event log? Would your
> please post it here?
> 3. Are you able to trace what the database is doing when you get this
> error?
> Please let us know the result. I look forward your reply.
> Wei Lu
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ================================================== ===
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
|||Hi white,
Thanks for the update. Please gather the trace and to see what have you
done before these error arised.
Wei Lu
Microsoft Online Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
Sunday, March 11, 2012
Error 605 on SQL Server 6.5
Hello!
I have a problem with two MS SQL Servers 6.5 (Microsoft SQL Server 6.50 -
6.50.416 (Intel X86) ) running on Windows 2000 advanced server(SP4). Every
night I make full backup of the database on â'main serverâ' (using job) and
start job on another MS SQL Server 6.5(â'standby serverâ'). The job on the
another server copies the file with the full backup and restores it. Then I
run dbcc chekdb for this database on the â'standby serverâ' and the following
messages appears:
--8<--
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 519096 in database 'request' belongs to object
'TSign_Request', not to object 'TRoute'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 522672 in database 'request' belongs to object
'TRoute', not to object 'TRequest'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 516440 in database 'request' belongs to object
'TRequest', not to object 'TReport'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 517296 in database 'request' belongs to object
'TSign_Request', not to object 'TRoute'.
--8<--
This message appears periodically _not_every_time_ after restoring this
backup in another database on the main server too.Hello,
This error message indicates database corruption. You may want to run dbcc
checkdb on the original database to make sure it is OK. If so, there might
be issues when copying database.
If original database has problem, corruption issue might be caused by
hardware. Please check the following event log to see if there is any
related events on disk etc.
Please understand SQL 6.5 is out of its lifecycle, and it is recommended
that you upgrade to later version when possible.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
>Thread-Topic: Error 605 on SQL Server 6.5
>thread-index: AcZaG4LgFBOxVaiEQbKF7y0q+hu4HQ==>X-WBNR-Posting-Host: 212.12.3.11
>From: =?Utf-8?B?dmFkaW1t?= <white@.community.nospam>
>Subject: Error 605 on SQL Server 6.5
>Date: Fri, 7 Apr 2006 01:16:03 -0700
>Lines: 30
>Message-ID: <23B8D9AB-AF78-4B48-A0D9-EBCF70011879@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 8bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.server
>Path: TK2MSFTNGXA01.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:427209
>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hello!
>I have a problem with two MS SQL Servers 6.5 (Microsoft SQL Server 6.50 -
>6.50.416 (Intel X86) ) running on Windows 2000 advanced server(SP4). Every
>night I make full backup of the database on â'main serverâ' (using job)
and
>start job on another MS SQL Server 6.5(â'standby serverâ'). The job on
the
>another server copies the file with the full backup and restores it. Then
I
>run dbcc chekdb for this database on the â'standby serverâ' and the
following
>messages appears:
>--8<--
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 519096 in database 'request' belongs to
object
> 'TSign_Request', not to object 'TRoute'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 522672 in database 'request' belongs to
object
> 'TRoute', not to object 'TRequest'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 516440 in database 'request' belongs to
object
> 'TRequest', not to object 'TReport'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 517296 in database 'request' belongs to
object
> 'TSign_Request', not to object 'TRoute'.
>--8<--
>This message appears periodically _not_every_time_ after restoring this
>backup in another database on the main server too.
>
>|||Hello!
""privatenews"" wrote:
> Hello,
> This error message indicates database corruption. You may want to run dbcc
> checkdb on the original database to make sure it is OK. If so, there might
> be issues when copying database.
"Dbcc checkdb" on the original database doesn't report errors.
"Dbcc checkdb" return this error _not_every_time_ only after the backup and
restore operations to another database.
> If original database has problem, corruption issue might be caused by
> hardware. Please check the following event log to see if there is any
> related events on disk etc.
There are no any disk related messages in eventlog.
> Please understand SQL 6.5 is out of its lifecycle, and it is recommended
> that you upgrade to later version when possible.
I understand this. We have to use SQLServer 6.5 because application not
support any other RDMS.
Also, all tables mentioned in dbcc error report has text column.|||Hello White,
If there is no issue for original database, it shall be problem in backup.
Please try to perform another backup, and restore it to different machine
to see if you could consistently reproduce the issue. If so, it seems
backup component on the original server has problems.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
>Thread-Topic: Error 605 on SQL Server 6.5
>thread-index: AcZaL8NuM/HIj/ktT/iS1n2EQghHvA==>X-WBNR-Posting-Host: 212.12.3.11
>From: =?Utf-8?B?dmFkaW1t?= <white@.community.nospam>
>References: <23B8D9AB-AF78-4B48-A0D9-EBCF70011879@.microsoft.com>
<l#ZrWXiWGHA.4708@.TK2MSFTNGXA01.phx.gbl>
>Subject: RE: Error 605 on SQL Server 6.5
>Date: Fri, 7 Apr 2006 03:41:01 -0700
>Lines: 29
>Message-ID: <2A930110-3259-4909-BF34-12A602B20120@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.server
>Path: TK2MSFTNGXA01.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:427225
>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hello!
>""privatenews"" wrote:
>> Hello,
>> This error message indicates database corruption. You may want to run
dbcc
>> checkdb on the original database to make sure it is OK. If so, there
might
>> be issues when copying database.
>"Dbcc checkdb" on the original database doesn't report errors.
>"Dbcc checkdb" return this error _not_every_time_ only after the backup
and
>restore operations to another database.
>> If original database has problem, corruption issue might be caused by
>> hardware. Please check the following event log to see if there is any
>> related events on disk etc.
>There are no any disk related messages in eventlog.
>> Please understand SQL 6.5 is out of its lifecycle, and it is recommended
>> that you upgrade to later version when possible.
>I understand this. We have to use SQLServer 6.5 because application not
>support any other RDMS.
>Also, all tables mentioned in dbcc error report has text column.
>
>
I have a problem with two MS SQL Servers 6.5 (Microsoft SQL Server 6.50 -
6.50.416 (Intel X86) ) running on Windows 2000 advanced server(SP4). Every
night I make full backup of the database on â'main serverâ' (using job) and
start job on another MS SQL Server 6.5(â'standby serverâ'). The job on the
another server copies the file with the full backup and restores it. Then I
run dbcc chekdb for this database on the â'standby serverâ' and the following
messages appears:
--8<--
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 519096 in database 'request' belongs to object
'TSign_Request', not to object 'TRoute'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 522672 in database 'request' belongs to object
'TRoute', not to object 'TRequest'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 516440 in database 'request' belongs to object
'TRequest', not to object 'TReport'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 517296 in database 'request' belongs to object
'TSign_Request', not to object 'TRoute'.
--8<--
This message appears periodically _not_every_time_ after restoring this
backup in another database on the main server too.Hello,
This error message indicates database corruption. You may want to run dbcc
checkdb on the original database to make sure it is OK. If so, there might
be issues when copying database.
If original database has problem, corruption issue might be caused by
hardware. Please check the following event log to see if there is any
related events on disk etc.
Please understand SQL 6.5 is out of its lifecycle, and it is recommended
that you upgrade to later version when possible.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
>Thread-Topic: Error 605 on SQL Server 6.5
>thread-index: AcZaG4LgFBOxVaiEQbKF7y0q+hu4HQ==>X-WBNR-Posting-Host: 212.12.3.11
>From: =?Utf-8?B?dmFkaW1t?= <white@.community.nospam>
>Subject: Error 605 on SQL Server 6.5
>Date: Fri, 7 Apr 2006 01:16:03 -0700
>Lines: 30
>Message-ID: <23B8D9AB-AF78-4B48-A0D9-EBCF70011879@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 8bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.server
>Path: TK2MSFTNGXA01.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:427209
>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hello!
>I have a problem with two MS SQL Servers 6.5 (Microsoft SQL Server 6.50 -
>6.50.416 (Intel X86) ) running on Windows 2000 advanced server(SP4). Every
>night I make full backup of the database on â'main serverâ' (using job)
and
>start job on another MS SQL Server 6.5(â'standby serverâ'). The job on
the
>another server copies the file with the full backup and restores it. Then
I
>run dbcc chekdb for this database on the â'standby serverâ' and the
following
>messages appears:
>--8<--
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 519096 in database 'request' belongs to
object
> 'TSign_Request', not to object 'TRoute'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 522672 in database 'request' belongs to
object
> 'TRoute', not to object 'TRequest'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 516440 in database 'request' belongs to
object
> 'TRequest', not to object 'TReport'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 517296 in database 'request' belongs to
object
> 'TSign_Request', not to object 'TRoute'.
>--8<--
>This message appears periodically _not_every_time_ after restoring this
>backup in another database on the main server too.
>
>|||Hello!
""privatenews"" wrote:
> Hello,
> This error message indicates database corruption. You may want to run dbcc
> checkdb on the original database to make sure it is OK. If so, there might
> be issues when copying database.
"Dbcc checkdb" on the original database doesn't report errors.
"Dbcc checkdb" return this error _not_every_time_ only after the backup and
restore operations to another database.
> If original database has problem, corruption issue might be caused by
> hardware. Please check the following event log to see if there is any
> related events on disk etc.
There are no any disk related messages in eventlog.
> Please understand SQL 6.5 is out of its lifecycle, and it is recommended
> that you upgrade to later version when possible.
I understand this. We have to use SQLServer 6.5 because application not
support any other RDMS.
Also, all tables mentioned in dbcc error report has text column.|||Hello White,
If there is no issue for original database, it shall be problem in backup.
Please try to perform another backup, and restore it to different machine
to see if you could consistently reproduce the issue. If so, it seems
backup component on the original server has problems.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
>Thread-Topic: Error 605 on SQL Server 6.5
>thread-index: AcZaL8NuM/HIj/ktT/iS1n2EQghHvA==>X-WBNR-Posting-Host: 212.12.3.11
>From: =?Utf-8?B?dmFkaW1t?= <white@.community.nospam>
>References: <23B8D9AB-AF78-4B48-A0D9-EBCF70011879@.microsoft.com>
<l#ZrWXiWGHA.4708@.TK2MSFTNGXA01.phx.gbl>
>Subject: RE: Error 605 on SQL Server 6.5
>Date: Fri, 7 Apr 2006 03:41:01 -0700
>Lines: 29
>Message-ID: <2A930110-3259-4909-BF34-12A602B20120@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.server
>Path: TK2MSFTNGXA01.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:427225
>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hello!
>""privatenews"" wrote:
>> Hello,
>> This error message indicates database corruption. You may want to run
dbcc
>> checkdb on the original database to make sure it is OK. If so, there
might
>> be issues when copying database.
>"Dbcc checkdb" on the original database doesn't report errors.
>"Dbcc checkdb" return this error _not_every_time_ only after the backup
and
>restore operations to another database.
>> If original database has problem, corruption issue might be caused by
>> hardware. Please check the following event log to see if there is any
>> related events on disk etc.
>There are no any disk related messages in eventlog.
>> Please understand SQL 6.5 is out of its lifecycle, and it is recommended
>> that you upgrade to later version when possible.
>I understand this. We have to use SQLServer 6.5 because application not
>support any other RDMS.
>Also, all tables mentioned in dbcc error report has text column.
>
>
Error 605 on SQL Server 6.5
Hello!
I have a problem with two MS SQL Servers 6.5 (Microsoft SQL Server 6.50 -
6.50.416 (Intel X86) ) running on Windows 2000 advanced server(SP4). Every
night I make full backup of the database on “main server” (using job) an
d
start job on another MS SQL Server 6.5(“standby server”). The job on the
another server copies the file with the full backup and restores it. Then I
run dbcc chekdb for this database on the “standby server” and the follow
ing
messages appears:
--8<--
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 519096 in database 'request' belongs to object
'TSign_Request', not to object 'TRoute'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 522672 in database 'request' belongs to object
'TRoute', not to object 'TRequest'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 516440 in database 'request' belongs to object
'TRequest', not to object 'TReport'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 517296 in database 'request' belongs to object
'TSign_Request', not to object 'TRoute'.
--8<--
This message appears periodically _not_every_time_ after restoring this
backup in another database on the main server too.Hello,
This error message indicates database corruption. You may want to run dbcc
checkdb on the original database to make sure it is OK. If so, there might
be issues when copying database.
If original database has problem, corruption issue might be caused by
hardware. Please check the following event log to see if there is any
related events on disk etc.
Please understand SQL 6.5 is out of its lifecycle, and it is recommended
that you upgrade to later version when possible.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Error 605 on SQL Server 6.5
>thread-index: AcZaG4LgFBOxVaiEQbKF7y0q+hu4HQ==
>X-WBNR-Posting-Host: 212.12.3.11
>From: examnotes <white@.community.nospam>
>Subject: Error 605 on SQL Server 6.5
>Date: Fri, 7 Apr 2006 01:16:03 -0700
>Lines: 30
>Message-ID: <23B8D9AB-AF78-4B48-A0D9-EBCF70011879@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 8bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.server
>Path: TK2MSFTNGXA01.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:427209
>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hello!
>I have a problem with two MS SQL Servers 6.5 (Microsoft SQL Server 6.50 -
>6.50.416 (Intel X86) ) running on Windows 2000 advanced server(SP4). Every
>night I make full backup of the database on “main server” (using job)
and
>start job on another MS SQL Server 6.5(“standby server”). The job on
the
>another server copies the file with the full backup and restores it. Then
I
>run dbcc chekdb for this database on the “standby server” and the
following
>messages appears:
>--8<--
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 519096 in database 'request' belongs to
object
> 'TSign_Request', not to object 'TRoute'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 522672 in database 'request' belongs to
object
> 'TRoute', not to object 'TRequest'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 516440 in database 'request' belongs to
object
> 'TRequest', not to object 'TReport'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 517296 in database 'request' belongs to
object
> 'TSign_Request', not to object 'TRoute'.
>--8<--
>This message appears periodically _not_every_time_ after restoring this
>backup in another database on the main server too.
>
>|||Hello!
""privatenews"" wrote:
> Hello,
> This error message indicates database corruption. You may want to run dbcc
> checkdb on the original database to make sure it is OK. If so, there might
> be issues when copying database.
"Dbcc checkdb" on the original database doesn't report errors.
"Dbcc checkdb" return this error _not_every_time_ only after the backup and
restore operations to another database.
> If original database has problem, corruption issue might be caused by
> hardware. Please check the following event log to see if there is any
> related events on disk etc.
There are no any disk related messages in eventlog.
> Please understand SQL 6.5 is out of its lifecycle, and it is recommended
> that you upgrade to later version when possible.
I understand this. We have to use SQLServer 6.5 because application not
support any other RDMS.
Also, all tables mentioned in dbcc error report has text column.|||Hello White,
If there is no issue for original database, it shall be problem in backup.
Please try to perform another backup, and restore it to different machine
to see if you could consistently reproduce the issue. If so, it seems
backup component on the original server has problems.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Error 605 on SQL Server 6.5
>thread-index: AcZaL8NuM/HIj/ktT/iS1n2EQghHvA==
>X-WBNR-Posting-Host: 212.12.3.11
>From: examnotes <white@.community.nospam>
>References: <23B8D9AB-AF78-4B48-A0D9-EBCF70011879@.microsoft.com>
<l#ZrWXiWGHA.4708@.TK2MSFTNGXA01.phx.gbl>
>Subject: RE: Error 605 on SQL Server 6.5
>Date: Fri, 7 Apr 2006 03:41:01 -0700
>Lines: 29
>Message-ID: <2A930110-3259-4909-BF34-12A602B20120@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.server
>Path: TK2MSFTNGXA01.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:427225
>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hello!
>""privatenews"" wrote:
>
dbcc[vbcol=seagreen]
might[vbcol=seagreen]
>"Dbcc checkdb" on the original database doesn't report errors.
>"Dbcc checkdb" return this error _not_every_time_ only after the backup
and
>restore operations to another database.
>
>There are no any disk related messages in eventlog.
>
>I understand this. We have to use SQLServer 6.5 because application not
>support any other RDMS.
>Also, all tables mentioned in dbcc error report has text column.
>
>
I have a problem with two MS SQL Servers 6.5 (Microsoft SQL Server 6.50 -
6.50.416 (Intel X86) ) running on Windows 2000 advanced server(SP4). Every
night I make full backup of the database on “main server” (using job) an
d
start job on another MS SQL Server 6.5(“standby server”). The job on the
another server copies the file with the full backup and restores it. Then I
run dbcc chekdb for this database on the “standby server” and the follow
ing
messages appears:
--8<--
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 519096 in database 'request' belongs to object
'TSign_Request', not to object 'TRoute'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 522672 in database 'request' belongs to object
'TRoute', not to object 'TRequest'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 516440 in database 'request' belongs to object
'TRequest', not to object 'TReport'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 517296 in database 'request' belongs to object
'TSign_Request', not to object 'TRoute'.
--8<--
This message appears periodically _not_every_time_ after restoring this
backup in another database on the main server too.Hello,
This error message indicates database corruption. You may want to run dbcc
checkdb on the original database to make sure it is OK. If so, there might
be issues when copying database.
If original database has problem, corruption issue might be caused by
hardware. Please check the following event log to see if there is any
related events on disk etc.
Please understand SQL 6.5 is out of its lifecycle, and it is recommended
that you upgrade to later version when possible.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Error 605 on SQL Server 6.5
>thread-index: AcZaG4LgFBOxVaiEQbKF7y0q+hu4HQ==
>X-WBNR-Posting-Host: 212.12.3.11
>From: examnotes <white@.community.nospam>
>Subject: Error 605 on SQL Server 6.5
>Date: Fri, 7 Apr 2006 01:16:03 -0700
>Lines: 30
>Message-ID: <23B8D9AB-AF78-4B48-A0D9-EBCF70011879@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 8bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.server
>Path: TK2MSFTNGXA01.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:427209
>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hello!
>I have a problem with two MS SQL Servers 6.5 (Microsoft SQL Server 6.50 -
>6.50.416 (Intel X86) ) running on Windows 2000 advanced server(SP4). Every
>night I make full backup of the database on “main server” (using job)
and
>start job on another MS SQL Server 6.5(“standby server”). The job on
the
>another server copies the file with the full backup and restores it. Then
I
>run dbcc chekdb for this database on the “standby server” and the
following
>messages appears:
>--8<--
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 519096 in database 'request' belongs to
object
> 'TSign_Request', not to object 'TRoute'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 522672 in database 'request' belongs to
object
> 'TRoute', not to object 'TRequest'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 516440 in database 'request' belongs to
object
> 'TRequest', not to object 'TReport'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 517296 in database 'request' belongs to
object
> 'TSign_Request', not to object 'TRoute'.
>--8<--
>This message appears periodically _not_every_time_ after restoring this
>backup in another database on the main server too.
>
>|||Hello!
""privatenews"" wrote:
> Hello,
> This error message indicates database corruption. You may want to run dbcc
> checkdb on the original database to make sure it is OK. If so, there might
> be issues when copying database.
"Dbcc checkdb" on the original database doesn't report errors.
"Dbcc checkdb" return this error _not_every_time_ only after the backup and
restore operations to another database.
> If original database has problem, corruption issue might be caused by
> hardware. Please check the following event log to see if there is any
> related events on disk etc.
There are no any disk related messages in eventlog.
> Please understand SQL 6.5 is out of its lifecycle, and it is recommended
> that you upgrade to later version when possible.
I understand this. We have to use SQLServer 6.5 because application not
support any other RDMS.
Also, all tables mentioned in dbcc error report has text column.|||Hello White,
If there is no issue for original database, it shall be problem in backup.
Please try to perform another backup, and restore it to different machine
to see if you could consistently reproduce the issue. If so, it seems
backup component on the original server has problems.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Error 605 on SQL Server 6.5
>thread-index: AcZaL8NuM/HIj/ktT/iS1n2EQghHvA==
>X-WBNR-Posting-Host: 212.12.3.11
>From: examnotes <white@.community.nospam>
>References: <23B8D9AB-AF78-4B48-A0D9-EBCF70011879@.microsoft.com>
<l#ZrWXiWGHA.4708@.TK2MSFTNGXA01.phx.gbl>
>Subject: RE: Error 605 on SQL Server 6.5
>Date: Fri, 7 Apr 2006 03:41:01 -0700
>Lines: 29
>Message-ID: <2A930110-3259-4909-BF34-12A602B20120@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.server
>Path: TK2MSFTNGXA01.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:427225
>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hello!
>""privatenews"" wrote:
>
dbcc[vbcol=seagreen]
might[vbcol=seagreen]
>"Dbcc checkdb" on the original database doesn't report errors.
>"Dbcc checkdb" return this error _not_every_time_ only after the backup
and
>restore operations to another database.
>
>There are no any disk related messages in eventlog.
>
>I understand this. We have to use SQLServer 6.5 because application not
>support any other RDMS.
>Also, all tables mentioned in dbcc error report has text column.
>
>
Error 605 on SQL Server 6.5
Hello!
I have a problem with two MS SQL Servers 6.5 (Microsoft SQL Server 6.50 -
6.50.416 (Intel X86) ) running on Windows 2000 advanced server(SP4). Every
night I make full backup of the database on “main server” (using job) and
start job on another MS SQL Server 6.5(“standby server”). The job on the
another server copies the file with the full backup and restores it. Then I
run dbcc chekdb for this database on the “standby server” and the following
messages appears:
--8<--
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 519096 in database 'request' belongs to object
'TSign_Request', not to object 'TRoute'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 522672 in database 'request' belongs to object
'TRoute', not to object 'TRequest'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 516440 in database 'request' belongs to object
'TRequest', not to object 'TReport'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 517296 in database 'request' belongs to object
'TSign_Request', not to object 'TRoute'.
--8<--
This message appears periodically _not_every_time_ after restoring this
backup in another database on the main server too.
Hello,
This error message indicates database corruption. You may want to run dbcc
checkdb on the original database to make sure it is OK. If so, there might
be issues when copying database.
If original database has problem, corruption issue might be caused by
hardware. Please check the following event log to see if there is any
related events on disk etc.
Please understand SQL 6.5 is out of its lifecycle, and it is recommended
that you upgrade to later version when possible.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Error 605 on SQL Server 6.5
>thread-index: AcZaG4LgFBOxVaiEQbKF7y0q+hu4HQ==
>X-WBNR-Posting-Host: 212.12.3.11
>From: =?Utf-8?B?dmFkaW1t?= <white@.community.nospam>
>Subject: Error 605 on SQL Server 6.5
>Date: Fri, 7 Apr 2006 01:16:03 -0700
>Lines: 30
>Message-ID: <23B8D9AB-AF78-4B48-A0D9-EBCF70011879@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>charset="Utf-8"
>Content-Transfer-Encoding: 8bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.server
>Path: TK2MSFTNGXA01.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:427209
>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hello!
>I have a problem with two MS SQL Servers 6.5 (Microsoft SQL Server 6.50 -
>6.50.416 (Intel X86) ) running on Windows 2000 advanced server(SP4). Every
>night I make full backup of the database on “main server” (using job)
and
>start job on another MS SQL Server 6.5(“standby server”). The job on
the
>another server copies the file with the full backup and restores it. Then
I
>run dbcc chekdb for this database on the “standby server” and the
following
>messages appears:
>--8<--
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 519096 in database 'request' belongs to
object
> 'TSign_Request', not to object 'TRoute'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 522672 in database 'request' belongs to
object
> 'TRoute', not to object 'TRequest'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 516440 in database 'request' belongs to
object
> 'TRequest', not to object 'TReport'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 517296 in database 'request' belongs to
object
> 'TSign_Request', not to object 'TRoute'.
>--8<--
>This message appears periodically _not_every_time_ after restoring this
>backup in another database on the main server too.
>
>
|||Hello!
""privatenews"" wrote:
> Hello,
> This error message indicates database corruption. You may want to run dbcc
> checkdb on the original database to make sure it is OK. If so, there might
> be issues when copying database.
"Dbcc checkdb" on the original database doesn't report errors.
"Dbcc checkdb" return this error _not_every_time_ only after the backup and
restore operations to another database.
> If original database has problem, corruption issue might be caused by
> hardware. Please check the following event log to see if there is any
> related events on disk etc.
There are no any disk related messages in eventlog.
> Please understand SQL 6.5 is out of its lifecycle, and it is recommended
> that you upgrade to later version when possible.
I understand this. We have to use SQLServer 6.5 because application not
support any other RDMS.
Also, all tables mentioned in dbcc error report has text column.
I have a problem with two MS SQL Servers 6.5 (Microsoft SQL Server 6.50 -
6.50.416 (Intel X86) ) running on Windows 2000 advanced server(SP4). Every
night I make full backup of the database on “main server” (using job) and
start job on another MS SQL Server 6.5(“standby server”). The job on the
another server copies the file with the full backup and restores it. Then I
run dbcc chekdb for this database on the “standby server” and the following
messages appears:
--8<--
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 519096 in database 'request' belongs to object
'TSign_Request', not to object 'TRoute'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 522672 in database 'request' belongs to object
'TRoute', not to object 'TRequest'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 516440 in database 'request' belongs to object
'TRequest', not to object 'TReport'.
Error : 605, Severity: 21, State: 1
Attempt to fetch logical page 517296 in database 'request' belongs to object
'TSign_Request', not to object 'TRoute'.
--8<--
This message appears periodically _not_every_time_ after restoring this
backup in another database on the main server too.
Hello,
This error message indicates database corruption. You may want to run dbcc
checkdb on the original database to make sure it is OK. If so, there might
be issues when copying database.
If original database has problem, corruption issue might be caused by
hardware. Please check the following event log to see if there is any
related events on disk etc.
Please understand SQL 6.5 is out of its lifecycle, and it is recommended
that you upgrade to later version when possible.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Error 605 on SQL Server 6.5
>thread-index: AcZaG4LgFBOxVaiEQbKF7y0q+hu4HQ==
>X-WBNR-Posting-Host: 212.12.3.11
>From: =?Utf-8?B?dmFkaW1t?= <white@.community.nospam>
>Subject: Error 605 on SQL Server 6.5
>Date: Fri, 7 Apr 2006 01:16:03 -0700
>Lines: 30
>Message-ID: <23B8D9AB-AF78-4B48-A0D9-EBCF70011879@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>charset="Utf-8"
>Content-Transfer-Encoding: 8bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.server
>Path: TK2MSFTNGXA01.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:427209
>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hello!
>I have a problem with two MS SQL Servers 6.5 (Microsoft SQL Server 6.50 -
>6.50.416 (Intel X86) ) running on Windows 2000 advanced server(SP4). Every
>night I make full backup of the database on “main server” (using job)
and
>start job on another MS SQL Server 6.5(“standby server”). The job on
the
>another server copies the file with the full backup and restores it. Then
I
>run dbcc chekdb for this database on the “standby server” and the
following
>messages appears:
>--8<--
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 519096 in database 'request' belongs to
object
> 'TSign_Request', not to object 'TRoute'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 522672 in database 'request' belongs to
object
> 'TRoute', not to object 'TRequest'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 516440 in database 'request' belongs to
object
> 'TRequest', not to object 'TReport'.
>Error : 605, Severity: 21, State: 1
>Attempt to fetch logical page 517296 in database 'request' belongs to
object
> 'TSign_Request', not to object 'TRoute'.
>--8<--
>This message appears periodically _not_every_time_ after restoring this
>backup in another database on the main server too.
>
>
|||Hello!
""privatenews"" wrote:
> Hello,
> This error message indicates database corruption. You may want to run dbcc
> checkdb on the original database to make sure it is OK. If so, there might
> be issues when copying database.
"Dbcc checkdb" on the original database doesn't report errors.
"Dbcc checkdb" return this error _not_every_time_ only after the backup and
restore operations to another database.
> If original database has problem, corruption issue might be caused by
> hardware. Please check the following event log to see if there is any
> related events on disk etc.
There are no any disk related messages in eventlog.
> Please understand SQL 6.5 is out of its lifecycle, and it is recommended
> that you upgrade to later version when possible.
I understand this. We have to use SQLServer 6.5 because application not
support any other RDMS.
Also, all tables mentioned in dbcc error report has text column.
Error 5172
Hello,
I hava an sql server 2000 sp3a on a win2k sp4 machine running all ok. I tried to build a raid 1 using the hdd where sqlserver was and a new one, but i failed to build it and consecuently i lost all data bases.
Using some programs, i recover the mdf, ldf and ndf files from my old sql server 2000.
I reinstalled all the system exactly the same, win2k sp4 and sql server 2000 with sp3a ( i know sp4 is out ), installed all the apps and overwrites mdf,nfs and ldf files with the old data, and when i tried to put databse online i get this error:
error 5172: header not valid on file "C:\dbtest.mdf". Pageaudit property is not valid.
Any one can help me?http://www.dbforums.com/t749523.html
http://www.lazydba.com/sql/1__728.html
There's lots of stuff out there...just google it...|||well, i've tried this before post with no result. i just ask here becouse i'm very lost.|||I tried command:
exec sp_attach_db @.dbname ... with so meny variation and i get the same error. Can anyone help me?
Thanks.
I hava an sql server 2000 sp3a on a win2k sp4 machine running all ok. I tried to build a raid 1 using the hdd where sqlserver was and a new one, but i failed to build it and consecuently i lost all data bases.
Using some programs, i recover the mdf, ldf and ndf files from my old sql server 2000.
I reinstalled all the system exactly the same, win2k sp4 and sql server 2000 with sp3a ( i know sp4 is out ), installed all the apps and overwrites mdf,nfs and ldf files with the old data, and when i tried to put databse online i get this error:
error 5172: header not valid on file "C:\dbtest.mdf". Pageaudit property is not valid.
Any one can help me?http://www.dbforums.com/t749523.html
http://www.lazydba.com/sql/1__728.html
There's lots of stuff out there...just google it...|||well, i've tried this before post with no result. i just ask here becouse i'm very lost.|||I tried command:
exec sp_attach_db @.dbname ... with so meny variation and i get the same error. Can anyone help me?
Thanks.
Friday, March 9, 2012
Error 4305 - Log-Shipping
Hi-
SQL 2000
Win 2k sp4
We have created a maintenance plan to ship one of our databases to a
secondary server. The initial snapshop shipped fine but we get error 4305
when trying to apply subsequent shipped tran logs.
The error says that the transaction log is too new.
We have another maintenance plan running on this DB that does backing
up(complete and tran logs) and it did do a tran-log backup after the
log-shipping snapshot. The log-shipping plan then made a tran log backup and
shipped it(which is too new).
I am trying to clarify if we can have two maintenance plans on the same
db(one for backup and one for log-shipping). Is this is what is causing this
error since they are overlapping.
I have not been able to find any info on this and am inclined to think they
are and I can only have oneplan that does all the backing up and the
log-shipping.
Can anyone confirm?
Thanks.Hi
With log shipping, you can do a Full and Differential backup at any time,
but transaction logs are sacred. Only log shipping can do the logs, otherwise
you would loose transactions.
Regards
Mike
"Jez" wrote:
> Hi-
> SQL 2000
> Win 2k sp4
> We have created a maintenance plan to ship one of our databases to a
> secondary server. The initial snapshop shipped fine but we get error 4305
> when trying to apply subsequent shipped tran logs.
> The error says that the transaction log is too new.
> We have another maintenance plan running on this DB that does backing
> up(complete and tran logs) and it did do a tran-log backup after the
> log-shipping snapshot. The log-shipping plan then made a tran log backup and
> shipped it(which is too new).
> I am trying to clarify if we can have two maintenance plans on the same
> db(one for backup and one for log-shipping). Is this is what is causing this
> error since they are overlapping.
> I have not been able to find any info on this and am inclined to think they
> are and I can only have oneplan that does all the backing up and the
> log-shipping.
> Can anyone confirm?
> Thanks.
>
>|||Thanks Mike for quick response
jez.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:BD6B7EE8-97DA-4522-B201-0494A27C54F0@.microsoft.com...
> Hi
> With log shipping, you can do a Full and Differential backup at any time,
> but transaction logs are sacred. Only log shipping can do the logs,
> otherwise
> you would loose transactions.
> Regards
> Mike
> "Jez" wrote:
>> Hi-
>> SQL 2000
>> Win 2k sp4
>> We have created a maintenance plan to ship one of our databases to a
>> secondary server. The initial snapshop shipped fine but we get error 4305
>> when trying to apply subsequent shipped tran logs.
>> The error says that the transaction log is too new.
>> We have another maintenance plan running on this DB that does backing
>> up(complete and tran logs) and it did do a tran-log backup after the
>> log-shipping snapshot. The log-shipping plan then made a tran log backup
>> and
>> shipped it(which is too new).
>> I am trying to clarify if we can have two maintenance plans on the same
>> db(one for backup and one for log-shipping). Is this is what is causing
>> this
>> error since they are overlapping.
>> I have not been able to find any info on this and am inclined to think
>> they
>> are and I can only have oneplan that does all the backing up and the
>> log-shipping.
>> Can anyone confirm?
>> Thanks.
>>
SQL 2000
Win 2k sp4
We have created a maintenance plan to ship one of our databases to a
secondary server. The initial snapshop shipped fine but we get error 4305
when trying to apply subsequent shipped tran logs.
The error says that the transaction log is too new.
We have another maintenance plan running on this DB that does backing
up(complete and tran logs) and it did do a tran-log backup after the
log-shipping snapshot. The log-shipping plan then made a tran log backup and
shipped it(which is too new).
I am trying to clarify if we can have two maintenance plans on the same
db(one for backup and one for log-shipping). Is this is what is causing this
error since they are overlapping.
I have not been able to find any info on this and am inclined to think they
are and I can only have oneplan that does all the backing up and the
log-shipping.
Can anyone confirm?
Thanks.Hi
With log shipping, you can do a Full and Differential backup at any time,
but transaction logs are sacred. Only log shipping can do the logs, otherwise
you would loose transactions.
Regards
Mike
"Jez" wrote:
> Hi-
> SQL 2000
> Win 2k sp4
> We have created a maintenance plan to ship one of our databases to a
> secondary server. The initial snapshop shipped fine but we get error 4305
> when trying to apply subsequent shipped tran logs.
> The error says that the transaction log is too new.
> We have another maintenance plan running on this DB that does backing
> up(complete and tran logs) and it did do a tran-log backup after the
> log-shipping snapshot. The log-shipping plan then made a tran log backup and
> shipped it(which is too new).
> I am trying to clarify if we can have two maintenance plans on the same
> db(one for backup and one for log-shipping). Is this is what is causing this
> error since they are overlapping.
> I have not been able to find any info on this and am inclined to think they
> are and I can only have oneplan that does all the backing up and the
> log-shipping.
> Can anyone confirm?
> Thanks.
>
>|||Thanks Mike for quick response
jez.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:BD6B7EE8-97DA-4522-B201-0494A27C54F0@.microsoft.com...
> Hi
> With log shipping, you can do a Full and Differential backup at any time,
> but transaction logs are sacred. Only log shipping can do the logs,
> otherwise
> you would loose transactions.
> Regards
> Mike
> "Jez" wrote:
>> Hi-
>> SQL 2000
>> Win 2k sp4
>> We have created a maintenance plan to ship one of our databases to a
>> secondary server. The initial snapshop shipped fine but we get error 4305
>> when trying to apply subsequent shipped tran logs.
>> The error says that the transaction log is too new.
>> We have another maintenance plan running on this DB that does backing
>> up(complete and tran logs) and it did do a tran-log backup after the
>> log-shipping snapshot. The log-shipping plan then made a tran log backup
>> and
>> shipped it(which is too new).
>> I am trying to clarify if we can have two maintenance plans on the same
>> db(one for backup and one for log-shipping). Is this is what is causing
>> this
>> error since they are overlapping.
>> I have not been able to find any info on this and am inclined to think
>> they
>> are and I can only have oneplan that does all the backing up and the
>> log-shipping.
>> Can anyone confirm?
>> Thanks.
>>
Wednesday, March 7, 2012
Error 3624 again!
SQL 2000 SP3a running on W2K Server SP4. Access 97 front end. Back end was
ported from Access. I get the following two errors several times a day.
Searched in the KB and the only article (827714) that comes close doesn't
seem to address my problem. Unless the hotfix it mentions is the answer...
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
SQL Server Assertion: File: <p:\sql\ntdbms\storeng\drs\include\record.inl>,
line=1447
Failed Assertion = 'm_SizeRec > 0 && m_SizeRec <= MAXDATAROW'.
Has anyone else seen these problems? It is always a query - I've never seen
it on a statement.Hi Ron,
I am not sure what Service Pack level you are on or if you are running into
the same situation as mentioned in the symptom section of article 827714.
Normally you would see this type of assertion when you have corruption in a
database. As a starting point I would like you to run DBCC CHECKDB on your
database. Make sure that you have no corruption in the database by making
sure that DBCC CHECKB shows "0" allocation and "0" consistency errors.
If you do find corruption in the database, restore it from a good backup.
Hope that helps !!!
Thanks,
Fargham Butt
Microsoft - SQL Server
ported from Access. I get the following two errors several times a day.
Searched in the KB and the only article (827714) that comes close doesn't
seem to address my problem. Unless the hotfix it mentions is the answer...
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
SQL Server Assertion: File: <p:\sql\ntdbms\storeng\drs\include\record.inl>,
line=1447
Failed Assertion = 'm_SizeRec > 0 && m_SizeRec <= MAXDATAROW'.
Has anyone else seen these problems? It is always a query - I've never seen
it on a statement.Hi Ron,
I am not sure what Service Pack level you are on or if you are running into
the same situation as mentioned in the symptom section of article 827714.
Normally you would see this type of assertion when you have corruption in a
database. As a starting point I would like you to run DBCC CHECKDB on your
database. Make sure that you have no corruption in the database by making
sure that DBCC CHECKB shows "0" allocation and "0" consistency errors.
If you do find corruption in the database, restore it from a good backup.
Hope that helps !!!
Thanks,
Fargham Butt
Microsoft - SQL Server
Error 3624 again!
SQL 2000 SP3a running on W2K Server SP4. Access 97 front end. Back end was
ported from Access. I get the following two errors several times a day.
Searched in the KB and the only article (827714) that comes close doesn't
seem to address my problem. Unless the hotfix it mentions is the answer...
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
SQL Server Assertion: File: <p:\sql\ntdbms\storeng\drs\include\record.inl>,
line=1447
Failed Assertion = 'm_SizeRec > 0 && m_SizeRec <= MAXDATAROW'.
Has anyone else seen these problems? It is always a query - I've never seen
it on a statement.
Hi Ron,
I am not sure what Service Pack level you are on or if you are running into
the same situation as mentioned in the symptom section of article 827714.
Normally you would see this type of assertion when you have corruption in a
database. As a starting point I would like you to run DBCC CHECKDB on your
database. Make sure that you have no corruption in the database by making
sure that DBCC CHECKB shows "0" allocation and "0" consistency errors.
If you do find corruption in the database, restore it from a good backup.
Hope that helps !!!
Thanks,
Fargham Butt
Microsoft - SQL Server
ported from Access. I get the following two errors several times a day.
Searched in the KB and the only article (827714) that comes close doesn't
seem to address my problem. Unless the hotfix it mentions is the answer...
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
SQL Server Assertion: File: <p:\sql\ntdbms\storeng\drs\include\record.inl>,
line=1447
Failed Assertion = 'm_SizeRec > 0 && m_SizeRec <= MAXDATAROW'.
Has anyone else seen these problems? It is always a query - I've never seen
it on a statement.
Hi Ron,
I am not sure what Service Pack level you are on or if you are running into
the same situation as mentioned in the symptom section of article 827714.
Normally you would see this type of assertion when you have corruption in a
database. As a starting point I would like you to run DBCC CHECKDB on your
database. Make sure that you have no corruption in the database by making
sure that DBCC CHECKB shows "0" allocation and "0" consistency errors.
If you do find corruption in the database, restore it from a good backup.
Hope that helps !!!
Thanks,
Fargham Butt
Microsoft - SQL Server
Error 3624 again!
SQL 2000 SP3a running on W2K Server SP4. Access 97 front end. Back end was
ported from Access. I get the following two errors several times a day.
Searched in the KB and the only article (827714) that comes close doesn't
seem to address my problem. Unless the hotfix it mentions is the answer...
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
SQL Server Assertion: File: < p:\sql\ntdbms\storeng\drs\include\record
.inl>,
line=1447
Failed Assertion = 'm_SizeRec > 0 && m_SizeRec <= MAXDATAROW'.
Has anyone else seen these problems? It is always a query - I've never seen
it on a statement.Hi Ron,
I am not sure what Service Pack level you are on or if you are running into
the same situation as mentioned in the symptom section of article 827714.
Normally you would see this type of assertion when you have corruption in a
database. As a starting point I would like you to run DBCC CHECKDB on your
database. Make sure that you have no corruption in the database by making
sure that DBCC CHECKB shows "0" allocation and "0" consistency errors.
If you do find corruption in the database, restore it from a good backup.
Hope that helps !!!
Thanks,
Fargham Butt
Microsoft - SQL Server
ported from Access. I get the following two errors several times a day.
Searched in the KB and the only article (827714) that comes close doesn't
seem to address my problem. Unless the hotfix it mentions is the answer...
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
SQL Server Assertion: File: < p:\sql\ntdbms\storeng\drs\include\record
.inl>,
line=1447
Failed Assertion = 'm_SizeRec > 0 && m_SizeRec <= MAXDATAROW'.
Has anyone else seen these problems? It is always a query - I've never seen
it on a statement.Hi Ron,
I am not sure what Service Pack level you are on or if you are running into
the same situation as mentioned in the symptom section of article 827714.
Normally you would see this type of assertion when you have corruption in a
database. As a starting point I would like you to run DBCC CHECKDB on your
database. Make sure that you have no corruption in the database by making
sure that DBCC CHECKB shows "0" allocation and "0" consistency errors.
If you do find corruption in the database, restore it from a good backup.
Hope that helps !!!
Thanks,
Fargham Butt
Microsoft - SQL Server
Sunday, February 26, 2012
Error 3013
Got a weird one...
I have 20 databases on one SQL 2000 sp4, .2187 instance.
I also have a backup database and backup log script that I run, which
enumerates the datbase list and runs a backup for each one.
One specific database errors, while the ones before and after it succeed.
It used to work just fine, no changes (especially since I can pinpoint the
failure time to 5:50am, and I know nobody was fooling with the server at
that time).
The error is 3013 - "Backup terminating abnormally" (not the verbatim
error). Error happens for full backup and t-log.
I cannot backup manually through QA or Enterprise manger either. Nor can I
backup to a different location one the same or different drives...
Tried to generate a mini-dump using DBCC DUMPTRIGGER, but got nothing in the
\LOG folder. Plenty of space on the backup drive, running out on the T-Log
drive...
Help?
Thanks,
Kevin Hill
3NF Consulting
http://kevinbhill.powweb.com/NewsGroups.htm
My random SQL Server encounters:
http://kevin3nf.blogspot.com/
Forgot to mention that DBCC CheckAlloc and DBCC CheckDB come up clean
"Kevin3NF" <Kevin@.DontSpamMe3NF-inc.com> wrote in message
news:%23Qybs8kFHHA.1080@.TK2MSFTNGP05.phx.gbl...
> Got a weird one...
> I have 20 databases on one SQL 2000 sp4, .2187 instance.
> I also have a backup database and backup log script that I run, which
> enumerates the datbase list and runs a backup for each one.
> One specific database errors, while the ones before and after it succeed.
> It used to work just fine, no changes (especially since I can pinpoint the
> failure time to 5:50am, and I know nobody was fooling with the server at
> that time).
> The error is 3013 - "Backup terminating abnormally" (not the verbatim
> error). Error happens for full backup and t-log.
> I cannot backup manually through QA or Enterprise manger either. Nor can
> I backup to a different location one the same or different drives...
> Tried to generate a mini-dump using DBCC DUMPTRIGGER, but got nothing in
> the \LOG folder. Plenty of space on the backup drive, running out on the
> T-Log drive...
> Help?
> Thanks,
> Kevin Hill
> 3NF Consulting
> http://kevinbhill.powweb.com/NewsGroups.htm
> My random SQL Server encounters:
> http://kevin3nf.blogspot.com/
>
>
>
|||Kevin3NF wrote:
> Got a weird one...
> I have 20 databases on one SQL 2000 sp4, .2187 instance.
> I also have a backup database and backup log script that I run, which
> enumerates the datbase list and runs a backup for each one.
> One specific database errors, while the ones before and after it succeed.
> It used to work just fine, no changes (especially since I can pinpoint the
> failure time to 5:50am, and I know nobody was fooling with the server at
> that time).
> The error is 3013 - "Backup terminating abnormally" (not the verbatim
> error). Error happens for full backup and t-log.
> I cannot backup manually through QA or Enterprise manger either. Nor can I
> backup to a different location one the same or different drives...
> Tried to generate a mini-dump using DBCC DUMPTRIGGER, but got nothing in the
> \LOG folder. Plenty of space on the backup drive, running out on the T-Log
> drive...
> Help?
> Thanks,
> Kevin Hill
> 3NF Consulting
> http://kevinbhill.powweb.com/NewsGroups.htm
> My random SQL Server encounters:
> http://kevin3nf.blogspot.com/
>
>
>
Anything in the error log?
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Just backup failed
Customer has since changed the db to Simple, and now we cannot change it
back to FULL (3013 and 5069)
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45742818.40402@.realsqlguy.com...
> Kevin3NF wrote:
> Anything in the error log?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
|||Kevin3NF wrote:
> Just backup failed
> Customer has since changed the db to Simple, and now we cannot change it
> back to FULL (3013 and 5069)
>
- Are you able to run queries against this database?
- Are you able to modify data within this database?
- Is something (tape backup, anti-virus software) preventing SQL from
writing to the MDF or LDF file?
- Does the SQL Server service account have proper rights to the MDF and
LDF files?
This sounds to me like something is restricting writes to the
transaction log file...
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||See below...everything appears to be working normally except the backups
This database is a replication publisher and that process is working just
fine..
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45743322.7040206@.realsqlguy.com...
> Kevin3NF wrote:
> - Are you able to run queries against this database?
Yes
> - Are you able to modify data within this database?
Yes
> - Is something (tape backup, anti-virus software) preventing SQL from
> writing to the MDF or LDF file?
Not that I am aware of...failures have been happening since 11/30
> - Does the SQL Server service account have proper rights to the MDF and
> LDF files?
Yes
> This sounds to me like something is restricting writes to the transaction
> log file...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
|||Everything else has failed, so we aer using DTS to send everything to a new
database...
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45743322.7040206@.realsqlguy.com...
> Kevin3NF wrote:
> - Are you able to run queries against this database?
> - Are you able to modify data within this database?
> - Is something (tape backup, anti-virus software) preventing SQL from
> writing to the MDF or LDF file?
> - Does the SQL Server service account have proper rights to the MDF and
> LDF files?
> This sounds to me like something is restricting writes to the transaction
> log file...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
I have 20 databases on one SQL 2000 sp4, .2187 instance.
I also have a backup database and backup log script that I run, which
enumerates the datbase list and runs a backup for each one.
One specific database errors, while the ones before and after it succeed.
It used to work just fine, no changes (especially since I can pinpoint the
failure time to 5:50am, and I know nobody was fooling with the server at
that time).
The error is 3013 - "Backup terminating abnormally" (not the verbatim
error). Error happens for full backup and t-log.
I cannot backup manually through QA or Enterprise manger either. Nor can I
backup to a different location one the same or different drives...
Tried to generate a mini-dump using DBCC DUMPTRIGGER, but got nothing in the
\LOG folder. Plenty of space on the backup drive, running out on the T-Log
drive...
Help?
Thanks,
Kevin Hill
3NF Consulting
http://kevinbhill.powweb.com/NewsGroups.htm
My random SQL Server encounters:
http://kevin3nf.blogspot.com/
Forgot to mention that DBCC CheckAlloc and DBCC CheckDB come up clean
"Kevin3NF" <Kevin@.DontSpamMe3NF-inc.com> wrote in message
news:%23Qybs8kFHHA.1080@.TK2MSFTNGP05.phx.gbl...
> Got a weird one...
> I have 20 databases on one SQL 2000 sp4, .2187 instance.
> I also have a backup database and backup log script that I run, which
> enumerates the datbase list and runs a backup for each one.
> One specific database errors, while the ones before and after it succeed.
> It used to work just fine, no changes (especially since I can pinpoint the
> failure time to 5:50am, and I know nobody was fooling with the server at
> that time).
> The error is 3013 - "Backup terminating abnormally" (not the verbatim
> error). Error happens for full backup and t-log.
> I cannot backup manually through QA or Enterprise manger either. Nor can
> I backup to a different location one the same or different drives...
> Tried to generate a mini-dump using DBCC DUMPTRIGGER, but got nothing in
> the \LOG folder. Plenty of space on the backup drive, running out on the
> T-Log drive...
> Help?
> Thanks,
> Kevin Hill
> 3NF Consulting
> http://kevinbhill.powweb.com/NewsGroups.htm
> My random SQL Server encounters:
> http://kevin3nf.blogspot.com/
>
>
>
|||Kevin3NF wrote:
> Got a weird one...
> I have 20 databases on one SQL 2000 sp4, .2187 instance.
> I also have a backup database and backup log script that I run, which
> enumerates the datbase list and runs a backup for each one.
> One specific database errors, while the ones before and after it succeed.
> It used to work just fine, no changes (especially since I can pinpoint the
> failure time to 5:50am, and I know nobody was fooling with the server at
> that time).
> The error is 3013 - "Backup terminating abnormally" (not the verbatim
> error). Error happens for full backup and t-log.
> I cannot backup manually through QA or Enterprise manger either. Nor can I
> backup to a different location one the same or different drives...
> Tried to generate a mini-dump using DBCC DUMPTRIGGER, but got nothing in the
> \LOG folder. Plenty of space on the backup drive, running out on the T-Log
> drive...
> Help?
> Thanks,
> Kevin Hill
> 3NF Consulting
> http://kevinbhill.powweb.com/NewsGroups.htm
> My random SQL Server encounters:
> http://kevin3nf.blogspot.com/
>
>
>
Anything in the error log?
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Just backup failed
Customer has since changed the db to Simple, and now we cannot change it
back to FULL (3013 and 5069)
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45742818.40402@.realsqlguy.com...
> Kevin3NF wrote:
> Anything in the error log?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
|||Kevin3NF wrote:
> Just backup failed
> Customer has since changed the db to Simple, and now we cannot change it
> back to FULL (3013 and 5069)
>
- Are you able to run queries against this database?
- Are you able to modify data within this database?
- Is something (tape backup, anti-virus software) preventing SQL from
writing to the MDF or LDF file?
- Does the SQL Server service account have proper rights to the MDF and
LDF files?
This sounds to me like something is restricting writes to the
transaction log file...
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||See below...everything appears to be working normally except the backups
This database is a replication publisher and that process is working just
fine..
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45743322.7040206@.realsqlguy.com...
> Kevin3NF wrote:
> - Are you able to run queries against this database?
Yes
> - Are you able to modify data within this database?
Yes
> - Is something (tape backup, anti-virus software) preventing SQL from
> writing to the MDF or LDF file?
Not that I am aware of...failures have been happening since 11/30
> - Does the SQL Server service account have proper rights to the MDF and
> LDF files?
Yes
> This sounds to me like something is restricting writes to the transaction
> log file...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
|||Everything else has failed, so we aer using DTS to send everything to a new
database...
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45743322.7040206@.realsqlguy.com...
> Kevin3NF wrote:
> - Are you able to run queries against this database?
> - Are you able to modify data within this database?
> - Is something (tape backup, anti-virus software) preventing SQL from
> writing to the MDF or LDF file?
> - Does the SQL Server service account have proper rights to the MDF and
> LDF files?
> This sounds to me like something is restricting writes to the transaction
> log file...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
Subscribe to:
Posts (Atom)