All,
I have the below problem while attaching the database, can
any one assist.
Thanks in advance.
--Error Details
Microsoft SQL-DMO(ODBC SQLState-HY000)
Error 3624
Location : recovery.C:2014
Expression: Curr-->log_length >0
SPID :53
ProcessorId: 1064
below is the last lines from Error Log
2004-06-01 10:27:14.45 spid53 Stack Signature for the
dump is 0x9A8706F6
2004-06-01 10:27:14.46 spid53 SQL Server Assertion:
File: <recovery.c>, line=2014
Failed Assertion = 'curr->log_length > 0'.
2004-06-01 10:27:14.46 spid53 Error: 3624, Severity:
20, State: 1.
2004-06-01 10:27:15.93 spid53 Error: 9004, Severity:
23, State: 7
2004-06-01 10:27:15.93 spid53 An error occurred while
processing the log for database 'UPSSISGR'..
...Mukund.R.L.Mukund.R.L.,
What version of SQL and service pack? Apply SP3a if you have SP2 or
earlier on 2000. Is there a stack dump or information in the Windows
Event log or SQL Server error log? You might be best raising a call with
MS PSS as it looks like you've been having this issue for a while from
my internet research.
SQL Server Support Centre
http://support.microsoft.com/default.aspx?pr=sql
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Mukund.R.L. wrote:
> All,
> I have the below problem while attaching the database, can
> any one assist.
> Thanks in advance.
> --Error Details
> Microsoft SQL-DMO(ODBC SQLState-HY000)
> Error 3624
> Location : recovery.C:2014
> Expression: Curr-->log_length >0
> SPID :53
> ProcessorId: 1064
> below is the last lines from Error Log
> 2004-06-01 10:27:14.45 spid53 Stack Signature for the
> dump is 0x9A8706F6
> 2004-06-01 10:27:14.46 spid53 SQL Server Assertion:
> File: <recovery.c>, line=2014
> Failed Assertion = 'curr->log_length > 0'.
> 2004-06-01 10:27:14.46 spid53 Error: 3624, Severity:
> 20, State: 1.
> 2004-06-01 10:27:15.93 spid53 Error: 9004, Severity:
> 23, State: 7
> 2004-06-01 10:27:15.93 spid53 An error occurred while
> processing the log for database 'UPSSISGR'..
>
> ...Mukund.R.L.
>
>|||Thanks for Your response.
I have SQL 2000 with service pack 3a.
..Mukund.R.L.
>--Original Message--
>Mukund.R.L.,
>What version of SQL and service pack? Apply SP3a if you
have SP2 or
>earlier on 2000. Is there a stack dump or information in
the Windows
>Event log or SQL Server error log? You might be best
raising a call with
>MS PSS as it looks like you've been having this issue for
a while from
>my internet research.
>SQL Server Support Centre
>http://support.microsoft.com/default.aspx?pr=sql
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>Mukund.R.L. wrote:
>> All,
>> I have the below problem while attaching the database,
can
>> any one assist.
>> Thanks in advance.
>> --Error Details
>> Microsoft SQL-DMO(ODBC SQLState-HY000)
>> Error 3624
>> Location : recovery.C:2014
>> Expression: Curr-->log_length >0
>> SPID :53
>> ProcessorId: 1064
>> below is the last lines from Error Log
>> 2004-06-01 10:27:14.45 spid53 Stack Signature for
the
>> dump is 0x9A8706F6
>> 2004-06-01 10:27:14.46 spid53 SQL Server Assertion:
>> File: <recovery.c>, line=2014
>> Failed Assertion = 'curr->log_length > 0'.
>> 2004-06-01 10:27:14.46 spid53 Error: 3624, Severity:
>> 20, State: 1.
>> 2004-06-01 10:27:15.93 spid53 Error: 9004, Severity:
>> 23, State: 7
>> 2004-06-01 10:27:15.93 spid53 An error occurred
while
>> processing the log for database 'UPSSISGR'..
>>
>> ...Mukund.R.L.
>>
>>
>.
>
Sunday, February 26, 2012
Error 3624
All,
I have the below problem while attaching the database, can
any one assist.
Thanks in advance.
--Error Details
Microsoft SQL-DMO(ODBC SQLState-HY000)
Error 3624
Location : recovery.C:2014
Expression: Curr-->log_length >0
SPID :53
ProcessorId: 1064
below is the last lines from Error Log
2004-06-01 10:27:14.45 spid53 Stack Signature for the
dump is 0x9A8706F6
2004-06-01 10:27:14.46 spid53 SQL Server Assertion:
File: <recovery.c>, line=2014
Failed Assertion = 'curr->log_length > 0'.
2004-06-01 10:27:14.46 spid53 Error: 3624, Severity:
20, State: 1.
2004-06-01 10:27:15.93 spid53 Error: 9004, Severity:
23, State: 7
2004-06-01 10:27:15.93 spid53 An error occurred while
processing the log for database 'UPSSISGR'..
....Mukund.R.L.
Mukund.R.L.,
What version of SQL and service pack? Apply SP3a if you have SP2 or
earlier on 2000. Is there a stack dump or information in the Windows
Event log or SQL Server error log? You might be best raising a call with
MS PSS as it looks like you've been having this issue for a while from
my internet research.
SQL Server Support Centre
http://support.microsoft.com/default.aspx?pr=sql
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Mukund.R.L. wrote:
> All,
> I have the below problem while attaching the database, can
> any one assist.
> Thanks in advance.
> --Error Details
> Microsoft SQL-DMO(ODBC SQLState-HY000)
> Error 3624
> Location : recovery.C:2014
> Expression: Curr-->log_length >0
> SPID :53
> ProcessorId: 1064
> below is the last lines from Error Log
> 2004-06-01 10:27:14.45 spid53 Stack Signature for the
> dump is 0x9A8706F6
> 2004-06-01 10:27:14.46 spid53 SQL Server Assertion:
> File: <recovery.c>, line=2014
> Failed Assertion = 'curr->log_length > 0'.
> 2004-06-01 10:27:14.46 spid53 Error: 3624, Severity:
> 20, State: 1.
> 2004-06-01 10:27:15.93 spid53 Error: 9004, Severity:
> 23, State: 7
> 2004-06-01 10:27:15.93 spid53 An error occurred while
> processing the log for database 'UPSSISGR'..
>
> ...Mukund.R.L.
>
>
|||Thanks for Your response.
I have SQL 2000 with service pack 3a.
...Mukund.R.L.
>--Original Message--
>Mukund.R.L.,
>What version of SQL and service pack? Apply SP3a if you
have SP2 or
>earlier on 2000. Is there a stack dump or information in
the Windows
>Event log or SQL Server error log? You might be best
raising a call with
>MS PSS as it looks like you've been having this issue for
a while from[vbcol=seagreen]
>my internet research.
>SQL Server Support Centre
>http://support.microsoft.com/default.aspx?pr=sql
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>Mukund.R.L. wrote:
can[vbcol=seagreen]
the[vbcol=seagreen]
while
>.
>
I have the below problem while attaching the database, can
any one assist.
Thanks in advance.
--Error Details
Microsoft SQL-DMO(ODBC SQLState-HY000)
Error 3624
Location : recovery.C:2014
Expression: Curr-->log_length >0
SPID :53
ProcessorId: 1064
below is the last lines from Error Log
2004-06-01 10:27:14.45 spid53 Stack Signature for the
dump is 0x9A8706F6
2004-06-01 10:27:14.46 spid53 SQL Server Assertion:
File: <recovery.c>, line=2014
Failed Assertion = 'curr->log_length > 0'.
2004-06-01 10:27:14.46 spid53 Error: 3624, Severity:
20, State: 1.
2004-06-01 10:27:15.93 spid53 Error: 9004, Severity:
23, State: 7
2004-06-01 10:27:15.93 spid53 An error occurred while
processing the log for database 'UPSSISGR'..
....Mukund.R.L.
Mukund.R.L.,
What version of SQL and service pack? Apply SP3a if you have SP2 or
earlier on 2000. Is there a stack dump or information in the Windows
Event log or SQL Server error log? You might be best raising a call with
MS PSS as it looks like you've been having this issue for a while from
my internet research.
SQL Server Support Centre
http://support.microsoft.com/default.aspx?pr=sql
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Mukund.R.L. wrote:
> All,
> I have the below problem while attaching the database, can
> any one assist.
> Thanks in advance.
> --Error Details
> Microsoft SQL-DMO(ODBC SQLState-HY000)
> Error 3624
> Location : recovery.C:2014
> Expression: Curr-->log_length >0
> SPID :53
> ProcessorId: 1064
> below is the last lines from Error Log
> 2004-06-01 10:27:14.45 spid53 Stack Signature for the
> dump is 0x9A8706F6
> 2004-06-01 10:27:14.46 spid53 SQL Server Assertion:
> File: <recovery.c>, line=2014
> Failed Assertion = 'curr->log_length > 0'.
> 2004-06-01 10:27:14.46 spid53 Error: 3624, Severity:
> 20, State: 1.
> 2004-06-01 10:27:15.93 spid53 Error: 9004, Severity:
> 23, State: 7
> 2004-06-01 10:27:15.93 spid53 An error occurred while
> processing the log for database 'UPSSISGR'..
>
> ...Mukund.R.L.
>
>
|||Thanks for Your response.
I have SQL 2000 with service pack 3a.
...Mukund.R.L.
>--Original Message--
>Mukund.R.L.,
>What version of SQL and service pack? Apply SP3a if you
have SP2 or
>earlier on 2000. Is there a stack dump or information in
the Windows
>Event log or SQL Server error log? You might be best
raising a call with
>MS PSS as it looks like you've been having this issue for
a while from[vbcol=seagreen]
>my internet research.
>SQL Server Support Centre
>http://support.microsoft.com/default.aspx?pr=sql
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>Mukund.R.L. wrote:
can[vbcol=seagreen]
the[vbcol=seagreen]
while
>.
>
Error 3624
I see in my SQL2K Server logs the following error, at least once a day if
not more often:
Error: 3624, Severity: 20, State: 1.
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
DBCC CHECKDB reports all is well with all of the databases on this server.
The fix outlined in KB317852 gives (almost) the exact same message, but it
says that was fixed in SP3 and I'm using SP3a, which was installed *before*
any of my own databases were created. I have an Access 97 Front End, with
the Default Record Locking set to No Locks. KB827714 seems to address a
similar issue. Does this sound like the problem? Is it something serious
where I should consider the 827714 hotfix? Or should I just ignore it and
wait for the next SP?
Is your situation as described in the symptoms section of the KB?
Tunji
"Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message news:ub5LMGjsEHA.2136@.TK2MSFTNGP11.phx.gbl...
I see in my SQL2K Server logs the following error, at least once a day if
not more often:
Error: 3624, Severity: 20, State: 1.
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
DBCC CHECKDB reports all is well with all of the databases on this server.
The fix outlined in KB317852 gives (almost) the exact same message, but it
says that was fixed in SP3 and I'm using SP3a, which was installed *before*
any of my own databases were created. I have an Access 97 Front End, with
the Default Record Locking set to No Locks. KB827714 seems to address a
similar issue. Does this sound like the problem? Is it something serious
where I should consider the 827714 hotfix? Or should I just ignore it and
wait for the next SP?
|||Yes. The two errors are exactly as described. I looked at the dump file and the query was a SELECT against a table with historical data only (in this instance anyway). Basically it is a sales history table and the query sums the sales for a particular salesman month to date. The table is only updated during the end of day processing, when no one else is using he system.
"TJ" <tunj@.hotmail.com> wrote in message news:uzWMgSlsEHA.2196@.TK2MSFTNGP14.phx.gbl...
Is your situation as described in the symptoms section of the KB?
Tunji
"Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message news:ub5LMGjsEHA.2136@.TK2MSFTNGP11.phx.gbl...
I see in my SQL2K Server logs the following error, at least once a day if
not more often:
Error: 3624, Severity: 20, State: 1.
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
DBCC CHECKDB reports all is well with all of the databases on this server.
The fix outlined in KB317852 gives (almost) the exact same message, but it
says that was fixed in SP3 and I'm using SP3a, which was installed *before*
any of my own databases were created. I have an Access 97 Front End, with
the Default Record Locking set to No Locks. KB827714 seems to address a
similar issue. Does this sound like the problem? Is it something serious
where I should consider the 827714 hotfix? Or should I just ignore it and
wait for the next SP?
not more often:
Error: 3624, Severity: 20, State: 1.
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
DBCC CHECKDB reports all is well with all of the databases on this server.
The fix outlined in KB317852 gives (almost) the exact same message, but it
says that was fixed in SP3 and I'm using SP3a, which was installed *before*
any of my own databases were created. I have an Access 97 Front End, with
the Default Record Locking set to No Locks. KB827714 seems to address a
similar issue. Does this sound like the problem? Is it something serious
where I should consider the 827714 hotfix? Or should I just ignore it and
wait for the next SP?
Is your situation as described in the symptoms section of the KB?
Tunji
"Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message news:ub5LMGjsEHA.2136@.TK2MSFTNGP11.phx.gbl...
I see in my SQL2K Server logs the following error, at least once a day if
not more often:
Error: 3624, Severity: 20, State: 1.
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
DBCC CHECKDB reports all is well with all of the databases on this server.
The fix outlined in KB317852 gives (almost) the exact same message, but it
says that was fixed in SP3 and I'm using SP3a, which was installed *before*
any of my own databases were created. I have an Access 97 Front End, with
the Default Record Locking set to No Locks. KB827714 seems to address a
similar issue. Does this sound like the problem? Is it something serious
where I should consider the 827714 hotfix? Or should I just ignore it and
wait for the next SP?
|||Yes. The two errors are exactly as described. I looked at the dump file and the query was a SELECT against a table with historical data only (in this instance anyway). Basically it is a sales history table and the query sums the sales for a particular salesman month to date. The table is only updated during the end of day processing, when no one else is using he system.
"TJ" <tunj@.hotmail.com> wrote in message news:uzWMgSlsEHA.2196@.TK2MSFTNGP14.phx.gbl...
Is your situation as described in the symptoms section of the KB?
Tunji
"Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message news:ub5LMGjsEHA.2136@.TK2MSFTNGP11.phx.gbl...
I see in my SQL2K Server logs the following error, at least once a day if
not more often:
Error: 3624, Severity: 20, State: 1.
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
DBCC CHECKDB reports all is well with all of the databases on this server.
The fix outlined in KB317852 gives (almost) the exact same message, but it
says that was fixed in SP3 and I'm using SP3a, which was installed *before*
any of my own databases were created. I have an Access 97 Front End, with
the Default Record Locking set to No Locks. KB827714 seems to address a
similar issue. Does this sound like the problem? Is it something serious
where I should consider the 827714 hotfix? Or should I just ignore it and
wait for the next SP?
Error 3624
All,
I have the below problem while attaching the database, can
any one assist.
Thanks in advance.
--Error Details
Microsoft SQL-DMO(ODBC SQLState-HY000)
Error 3624
Location : recovery.C:2014
Expression: Curr-->log_length >0
SPID :53
ProcessorId: 1064
below is the last lines from Error Log
2004-06-01 10:27:14.45 spid53 Stack Signature for the
dump is 0x9A8706F6
2004-06-01 10:27:14.46 spid53 SQL Server Assertion:
File: <recovery.c>, line=2014
Failed Assertion = 'curr->log_length > 0'.
2004-06-01 10:27:14.46 spid53 Error: 3624, Severity:
20, State: 1.
2004-06-01 10:27:15.93 spid53 Error: 9004, Severity:
23, State: 7
2004-06-01 10:27:15.93 spid53 An error occurred while
processing the log for database 'UPSSISGR'..
...Mukund.R.L.Mukund.R.L.,
What version of SQL and service pack? Apply SP3a if you have SP2 or
earlier on 2000. Is there a stack dump or information in the Windows
Event log or SQL Server error log? You might be best raising a call with
MS PSS as it looks like you've been having this issue for a while from
my internet research.
SQL Server Support Centre
http://support.microsoft.com/default.aspx?pr=sql
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Mukund.R.L. wrote:
> All,
> I have the below problem while attaching the database, can
> any one assist.
> Thanks in advance.
> --Error Details
> Microsoft SQL-DMO(ODBC SQLState-HY000)
> Error 3624
> Location : recovery.C:2014
> Expression: Curr-->log_length >0
> SPID :53
> ProcessorId: 1064
> below is the last lines from Error Log
> 2004-06-01 10:27:14.45 spid53 Stack Signature for the
> dump is 0x9A8706F6
> 2004-06-01 10:27:14.46 spid53 SQL Server Assertion:
> File: <recovery.c>, line=2014
> Failed Assertion = 'curr->log_length > 0'.
> 2004-06-01 10:27:14.46 spid53 Error: 3624, Severity:
> 20, State: 1.
> 2004-06-01 10:27:15.93 spid53 Error: 9004, Severity:
> 23, State: 7
> 2004-06-01 10:27:15.93 spid53 An error occurred while
> processing the log for database 'UPSSISGR'..
>
> ...Mukund.R.L.
>
>|||Thanks for Your response.
I have SQL 2000 with service pack 3a.
..Mukund.R.L.
>--Original Message--
>Mukund.R.L.,
>What version of SQL and service pack? Apply SP3a if you
have SP2 or
>earlier on 2000. Is there a stack dump or information in
the Windows
>Event log or SQL Server error log? You might be best
raising a call with
>MS PSS as it looks like you've been having this issue for
a while from
>my internet research.
>SQL Server Support Centre
>http://support.microsoft.com/default.aspx?pr=sql
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>Mukund.R.L. wrote:
can[vbcol=seagreen]
the[vbcol=seagreen]
while[vbcol=seagreen]
>.
>
I have the below problem while attaching the database, can
any one assist.
Thanks in advance.
--Error Details
Microsoft SQL-DMO(ODBC SQLState-HY000)
Error 3624
Location : recovery.C:2014
Expression: Curr-->log_length >0
SPID :53
ProcessorId: 1064
below is the last lines from Error Log
2004-06-01 10:27:14.45 spid53 Stack Signature for the
dump is 0x9A8706F6
2004-06-01 10:27:14.46 spid53 SQL Server Assertion:
File: <recovery.c>, line=2014
Failed Assertion = 'curr->log_length > 0'.
2004-06-01 10:27:14.46 spid53 Error: 3624, Severity:
20, State: 1.
2004-06-01 10:27:15.93 spid53 Error: 9004, Severity:
23, State: 7
2004-06-01 10:27:15.93 spid53 An error occurred while
processing the log for database 'UPSSISGR'..
...Mukund.R.L.Mukund.R.L.,
What version of SQL and service pack? Apply SP3a if you have SP2 or
earlier on 2000. Is there a stack dump or information in the Windows
Event log or SQL Server error log? You might be best raising a call with
MS PSS as it looks like you've been having this issue for a while from
my internet research.
SQL Server Support Centre
http://support.microsoft.com/default.aspx?pr=sql
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Mukund.R.L. wrote:
> All,
> I have the below problem while attaching the database, can
> any one assist.
> Thanks in advance.
> --Error Details
> Microsoft SQL-DMO(ODBC SQLState-HY000)
> Error 3624
> Location : recovery.C:2014
> Expression: Curr-->log_length >0
> SPID :53
> ProcessorId: 1064
> below is the last lines from Error Log
> 2004-06-01 10:27:14.45 spid53 Stack Signature for the
> dump is 0x9A8706F6
> 2004-06-01 10:27:14.46 spid53 SQL Server Assertion:
> File: <recovery.c>, line=2014
> Failed Assertion = 'curr->log_length > 0'.
> 2004-06-01 10:27:14.46 spid53 Error: 3624, Severity:
> 20, State: 1.
> 2004-06-01 10:27:15.93 spid53 Error: 9004, Severity:
> 23, State: 7
> 2004-06-01 10:27:15.93 spid53 An error occurred while
> processing the log for database 'UPSSISGR'..
>
> ...Mukund.R.L.
>
>|||Thanks for Your response.
I have SQL 2000 with service pack 3a.
..Mukund.R.L.
>--Original Message--
>Mukund.R.L.,
>What version of SQL and service pack? Apply SP3a if you
have SP2 or
>earlier on 2000. Is there a stack dump or information in
the Windows
>Event log or SQL Server error log? You might be best
raising a call with
>MS PSS as it looks like you've been having this issue for
a while from
>my internet research.
>SQL Server Support Centre
>http://support.microsoft.com/default.aspx?pr=sql
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>Mukund.R.L. wrote:
can[vbcol=seagreen]
the[vbcol=seagreen]
while[vbcol=seagreen]
>.
>
Error 3624
I see in my SQL2K Server logs the following error, at least once a day if
not more often:
Error: 3624, Severity: 20, State: 1.
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
DBCC CHECKDB reports all is well with all of the databases on this server.
The fix outlined in KB317852 gives (almost) the exact same message, but it
says that was fixed in SP3 and I'm using SP3a, which was installed *before*
any of my own databases were created. I have an Access 97 Front End, with
the Default Record Locking set to No Locks. KB827714 seems to address a
similar issue. Does this sound like the problem? Is it something serious
where I should consider the 827714 hotfix? Or should I just ignore it and
wait for the next SP?Is your situation as described in the symptoms section of the KB?
Tunji
"Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message news:ub5LMGjsEHA.2
136@.TK2MSFTNGP11.phx.gbl...
I see in my SQL2K Server logs the following error, at least once a day if
not more often:
Error: 3624, Severity: 20, State: 1.
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
DBCC CHECKDB reports all is well with all of the databases on this server.
The fix outlined in KB317852 gives (almost) the exact same message, but it
says that was fixed in SP3 and I'm using SP3a, which was installed *before*
any of my own databases were created. I have an Access 97 Front End, with
the Default Record Locking set to No Locks. KB827714 seems to address a
similar issue. Does this sound like the problem? Is it something serious
where I should consider the 827714 hotfix? Or should I just ignore it and
wait for the next SP?|||Yes. The two errors are exactly as described. I looked at the dump file and
the query was a SELECT against a table with historical data only (in this in
stance anyway). Basically it is a sales history table and the query sums the
sales for a particular salesman month to date. The table is only updated du
ring the end of day processing, when no one else is using he system.
"TJ" <tunj@.hotmail.com> wrote in message news:uzWMgSlsEHA.2196@.TK2MSFTNGP14.
phx.gbl...
Is your situation as described in the symptoms section of the KB?
Tunji
"Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message news:ub5LMGjsEHA.2
136@.TK2MSFTNGP11.phx.gbl...
I see in my SQL2K Server logs the following error, at least once a day if
not more often:
Error: 3624, Severity: 20, State: 1.
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
DBCC CHECKDB reports all is well with all of the databases on this server.
The fix outlined in KB317852 gives (almost) the exact same message, but it
says that was fixed in SP3 and I'm using SP3a, which was installed *before*
any of my own databases were created. I have an Access 97 Front End, with
the Default Record Locking set to No Locks. KB827714 seems to address a
similar issue. Does this sound like the problem? Is it something serious
where I should consider the 827714 hotfix? Or should I just ignore it and
wait for the next SP?
not more often:
Error: 3624, Severity: 20, State: 1.
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
DBCC CHECKDB reports all is well with all of the databases on this server.
The fix outlined in KB317852 gives (almost) the exact same message, but it
says that was fixed in SP3 and I'm using SP3a, which was installed *before*
any of my own databases were created. I have an Access 97 Front End, with
the Default Record Locking set to No Locks. KB827714 seems to address a
similar issue. Does this sound like the problem? Is it something serious
where I should consider the 827714 hotfix? Or should I just ignore it and
wait for the next SP?Is your situation as described in the symptoms section of the KB?
Tunji
"Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message news:ub5LMGjsEHA.2
136@.TK2MSFTNGP11.phx.gbl...
I see in my SQL2K Server logs the following error, at least once a day if
not more often:
Error: 3624, Severity: 20, State: 1.
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
DBCC CHECKDB reports all is well with all of the databases on this server.
The fix outlined in KB317852 gives (almost) the exact same message, but it
says that was fixed in SP3 and I'm using SP3a, which was installed *before*
any of my own databases were created. I have an Access 97 Front End, with
the Default Record Locking set to No Locks. KB827714 seems to address a
similar issue. Does this sound like the problem? Is it something serious
where I should consider the 827714 hotfix? Or should I just ignore it and
wait for the next SP?|||Yes. The two errors are exactly as described. I looked at the dump file and
the query was a SELECT against a table with historical data only (in this in
stance anyway). Basically it is a sales history table and the query sums the
sales for a particular salesman month to date. The table is only updated du
ring the end of day processing, when no one else is using he system.
"TJ" <tunj@.hotmail.com> wrote in message news:uzWMgSlsEHA.2196@.TK2MSFTNGP14.
phx.gbl...
Is your situation as described in the symptoms section of the KB?
Tunji
"Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message news:ub5LMGjsEHA.2
136@.TK2MSFTNGP11.phx.gbl...
I see in my SQL2K Server logs the following error, at least once a day if
not more often:
Error: 3624, Severity: 20, State: 1.
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
DBCC CHECKDB reports all is well with all of the databases on this server.
The fix outlined in KB317852 gives (almost) the exact same message, but it
says that was fixed in SP3 and I'm using SP3a, which was installed *before*
any of my own databases were created. I have an Access 97 Front End, with
the Default Record Locking set to No Locks. KB827714 seems to address a
similar issue. Does this sound like the problem? Is it something serious
where I should consider the 827714 hotfix? Or should I just ignore it and
wait for the next SP?
Error 3621
For some reason I'm getting the following error on my MS2000 MSSQl
server. THe message is being written into my logs on the server.
MSSQL Error Msg 3621 The statement has been terminated
THis is then followed by the information message
Connected to DB
THis continues in a over and over again. My DB was working
fine and I could use the query analyzer, now however I cannot
query anything in the DB.
Any help would be great. I really dont want to reinstall this
as a solution.
TIA
dogdog
This message is usually preceded by another message indicating the cause the
error. Are these messages in the SQL Server error log or in a log generated
by your application?
Hope this helps.
Dan Guzman
SQL Server MVP
<dogdog@.noemail.com> wrote in message
news:pan.2006.03.25.15.15.20.194339@.noemail.com...
> For some reason I'm getting the following error on my MS2000 MSSQl
> server. THe message is being written into my logs on the server.
> MSSQL Error Msg 3621 The statement has been terminated
> THis is then followed by the information message
> Connected to DB
> THis continues in a over and over again. My DB was working
> fine and I could use the query analyzer, now however I cannot
> query anything in the DB.
> Any help would be great. I really dont want to reinstall this
> as a solution.
> TIA
> dogdog
|||On Sat, 25 Mar 2006 09:32:12 +0000, Dan Guzman wrote:
> This message is usually preceded by another message indicating the cause the
> error. Are these messages in the SQL Server error log or in a log generated
> by your application?
The next message after the error 3621 is Statement has been terminated
and is then followed by an information message
stating "connected to db" This sequence just keeps going and going
over and over.
Hope that helps. Because it means absolutely nothing to me.
tks
dogdog
|||So these messages are in a log generated by your application? In that case,
it appears your application is reporting only the 3621 warning message and
not the preceding error that caused the statement to be terminated.
For example, below are the messages that are displayed by Query Analyzer
when I get a primary key violation:
Server: Msg 2627, Level 14, State 1, Line 1
Violation of PRIMARY KEY constraint 'PK_Table1'. Cannot insert duplicate key
in object 'Table1'.
The statement has been terminated.
If you have no control over the application logging behavior, I suggest you
run a Profiler trace to capture error events. This should help you identify
the problem SQL statements.
Hope this helps.
Dan Guzman
SQL Server MVP
<dogdog@.noemail.com> wrote in message
news:pan.2006.03.25.20.57.13.800017@.noemail.com...
> On Sat, 25 Mar 2006 09:32:12 +0000, Dan Guzman wrote:
>
> The next message after the error 3621 is Statement has been terminated
> and is then followed by an information message
> stating "connected to db" This sequence just keeps going and going
> over and over.
> Hope that helps. Because it means absolutely nothing to me.
> tks
> dogdog
|||On Sun, 26 Mar 2006 06:27:38 +0000, Dan Guzman wrote:
First off thanks for taking your time on this and explaining things to
me a novice with mssql.
> So these messages are in a log generated by your application? In that case,
> it appears your application is reporting only the 3621 warning message and
> not the preceding error that caused the statement to be terminated.
>
Yes they are being written to the system log by the mssql server. I
guess that was the best idea for this setup rather than having numerous
logs.
> For example, below are the messages that are displayed by Query Analyzer
> when I get a primary key violation:
> Server: Msg 2627, Level 14, State 1, Line 1
> Violation of PRIMARY KEY constraint 'PK_Table1'. Cannot insert duplicate key
> in object 'Table1'.
> The statement has been terminated.
> If you have no control over the application logging behavior, I suggest you
> run a Profiler trace to capture error events. This should help you identify
> the problem SQL statements.
It seems as if the last query ran is "stuck" for lack of a better
understanding and just keeps querying. So it runs (without user
interaction for some reason) then reports the Error 3621 Statement
has been terminated. Then waits and reconnects to the server and
does it again. Seems crazy but I didnt make this stuff and it
makes it really hard to figure out when you inherit something like
this. Unfortunately there are no other logs to help in troubleshooting
and I want to avoid reinstalling the entire database. Luckily it
just came online and we just started testing it (i.e. sending
queries on test data) so if it does come down to reloading there
will be nothing lost. I just want to avoid that.
Thanks again for your help. If you have any other ideas I'll be glad
to try them out. I'm going to give the Profiler trace idea a shot.
Hopefully it will lead to something.
server. THe message is being written into my logs on the server.
MSSQL Error Msg 3621 The statement has been terminated
THis is then followed by the information message
Connected to DB
THis continues in a over and over again. My DB was working
fine and I could use the query analyzer, now however I cannot
query anything in the DB.
Any help would be great. I really dont want to reinstall this
as a solution.
TIA
dogdog
This message is usually preceded by another message indicating the cause the
error. Are these messages in the SQL Server error log or in a log generated
by your application?
Hope this helps.
Dan Guzman
SQL Server MVP
<dogdog@.noemail.com> wrote in message
news:pan.2006.03.25.15.15.20.194339@.noemail.com...
> For some reason I'm getting the following error on my MS2000 MSSQl
> server. THe message is being written into my logs on the server.
> MSSQL Error Msg 3621 The statement has been terminated
> THis is then followed by the information message
> Connected to DB
> THis continues in a over and over again. My DB was working
> fine and I could use the query analyzer, now however I cannot
> query anything in the DB.
> Any help would be great. I really dont want to reinstall this
> as a solution.
> TIA
> dogdog
|||On Sat, 25 Mar 2006 09:32:12 +0000, Dan Guzman wrote:
> This message is usually preceded by another message indicating the cause the
> error. Are these messages in the SQL Server error log or in a log generated
> by your application?
The next message after the error 3621 is Statement has been terminated
and is then followed by an information message
stating "connected to db" This sequence just keeps going and going
over and over.
Hope that helps. Because it means absolutely nothing to me.
tks
dogdog
|||So these messages are in a log generated by your application? In that case,
it appears your application is reporting only the 3621 warning message and
not the preceding error that caused the statement to be terminated.
For example, below are the messages that are displayed by Query Analyzer
when I get a primary key violation:
Server: Msg 2627, Level 14, State 1, Line 1
Violation of PRIMARY KEY constraint 'PK_Table1'. Cannot insert duplicate key
in object 'Table1'.
The statement has been terminated.
If you have no control over the application logging behavior, I suggest you
run a Profiler trace to capture error events. This should help you identify
the problem SQL statements.
Hope this helps.
Dan Guzman
SQL Server MVP
<dogdog@.noemail.com> wrote in message
news:pan.2006.03.25.20.57.13.800017@.noemail.com...
> On Sat, 25 Mar 2006 09:32:12 +0000, Dan Guzman wrote:
>
> The next message after the error 3621 is Statement has been terminated
> and is then followed by an information message
> stating "connected to db" This sequence just keeps going and going
> over and over.
> Hope that helps. Because it means absolutely nothing to me.
> tks
> dogdog
|||On Sun, 26 Mar 2006 06:27:38 +0000, Dan Guzman wrote:
First off thanks for taking your time on this and explaining things to
me a novice with mssql.
> So these messages are in a log generated by your application? In that case,
> it appears your application is reporting only the 3621 warning message and
> not the preceding error that caused the statement to be terminated.
>
Yes they are being written to the system log by the mssql server. I
guess that was the best idea for this setup rather than having numerous
logs.
> For example, below are the messages that are displayed by Query Analyzer
> when I get a primary key violation:
> Server: Msg 2627, Level 14, State 1, Line 1
> Violation of PRIMARY KEY constraint 'PK_Table1'. Cannot insert duplicate key
> in object 'Table1'.
> The statement has been terminated.
> If you have no control over the application logging behavior, I suggest you
> run a Profiler trace to capture error events. This should help you identify
> the problem SQL statements.
It seems as if the last query ran is "stuck" for lack of a better
understanding and just keeps querying. So it runs (without user
interaction for some reason) then reports the Error 3621 Statement
has been terminated. Then waits and reconnects to the server and
does it again. Seems crazy but I didnt make this stuff and it
makes it really hard to figure out when you inherit something like
this. Unfortunately there are no other logs to help in troubleshooting
and I want to avoid reinstalling the entire database. Luckily it
just came online and we just started testing it (i.e. sending
queries on test data) so if it does come down to reloading there
will be nothing lost. I just want to avoid that.
Thanks again for your help. If you have any other ideas I'll be glad
to try them out. I'm going to give the Profiler trace idea a shot.
Hopefully it will lead to something.
Error 3621
For some reason I'm getting the following error on my MS2000 MSSQl
server. THe message is being written into my logs on the server.
MSSQL Error Msg 3621 The statement has been terminated
THis is then followed by the information message
Connected to DB
THis continues in a over and over again. My DB was working
fine and I could use the query analyzer, now however I cannot
query anything in the DB.
Any help would be great. I really dont want to reinstall this
as a solution.
TIA
dogdogThis message is usually preceded by another message indicating the cause the
error. Are these messages in the SQL Server error log or in a log generated
by your application?
Hope this helps.
Dan Guzman
SQL Server MVP
<dogdog@.noemail.com> wrote in message
news:pan.2006.03.25.15.15.20.194339@.noemail.com...
> For some reason I'm getting the following error on my MS2000 MSSQl
> server. THe message is being written into my logs on the server.
> MSSQL Error Msg 3621 The statement has been terminated
> THis is then followed by the information message
> Connected to DB
> THis continues in a over and over again. My DB was working
> fine and I could use the query analyzer, now however I cannot
> query anything in the DB.
> Any help would be great. I really dont want to reinstall this
> as a solution.
> TIA
> dogdog|||On Sat, 25 Mar 2006 09:32:12 +0000, Dan Guzman wrote:
> This message is usually preceded by another message indicating the cause t
he
> error. Are these messages in the SQL Server error log or in a log generat
ed
> by your application?
The next message after the error 3621 is Statement has been terminated
and is then followed by an information message
stating "connected to db" This sequence just keeps going and going
over and over.
Hope that helps. Because it means absolutely nothing to me.
tks
dogdog|||So these messages are in a log generated by your application? In that case,
it appears your application is reporting only the 3621 warning message and
not the preceding error that caused the statement to be terminated.
For example, below are the messages that are displayed by Query Analyzer
when I get a primary key violation:
Server: Msg 2627, Level 14, State 1, Line 1
Violation of PRIMARY KEY constraint 'PK_Table1'. Cannot insert duplicate key
in object 'Table1'.
The statement has been terminated.
If you have no control over the application logging behavior, I suggest you
run a Profiler trace to capture error events. This should help you identify
the problem SQL statements.
Hope this helps.
Dan Guzman
SQL Server MVP
<dogdog@.noemail.com> wrote in message
news:pan.2006.03.25.20.57.13.800017@.noemail.com...
> On Sat, 25 Mar 2006 09:32:12 +0000, Dan Guzman wrote:
>
> The next message after the error 3621 is Statement has been terminated
> and is then followed by an information message
> stating "connected to db" This sequence just keeps going and going
> over and over.
> Hope that helps. Because it means absolutely nothing to me.
> tks
> dogdog|||On Sun, 26 Mar 2006 06:27:38 +0000, Dan Guzman wrote:
First off thanks for taking your time on this and explaining things to
me a novice with mssql.
> So these messages are in a log generated by your application? In that cas
e,
> it appears your application is reporting only the 3621 warning message and
> not the preceding error that caused the statement to be terminated.
>
Yes they are being written to the system log by the mssql server. I
guess that was the best idea for this setup rather than having numerous
logs.
> For example, below are the messages that are displayed by Query Analyzer
> when I get a primary key violation:
> Server: Msg 2627, Level 14, State 1, Line 1
> Violation of PRIMARY KEY constraint 'PK_Table1'. Cannot insert duplicate k
ey
> in object 'Table1'.
> The statement has been terminated.
> If you have no control over the application logging behavior, I suggest yo
u
> run a Profiler trace to capture error events. This should help you identi
fy
> the problem SQL statements.
It seems as if the last query ran is "stuck" for lack of a better
understanding and just keeps querying. So it runs (without user
interaction for some reason) then reports the Error 3621 Statement
has been terminated. Then waits and reconnects to the server and
does it again. Seems crazy but I didnt make this stuff and it
makes it really hard to figure out when you inherit something like
this. Unfortunately there are no other logs to help in troubleshooting
and I want to avoid reinstalling the entire database. Luckily it
just came online and we just started testing it (i.e. sending
queries on test data) so if it does come down to reloading there
will be nothing lost. I just want to avoid that.
Thanks again for your help. If you have any other ideas I'll be glad
to try them out. I'm going to give the Profiler trace idea a shot.
Hopefully it will lead to something.
server. THe message is being written into my logs on the server.
MSSQL Error Msg 3621 The statement has been terminated
THis is then followed by the information message
Connected to DB
THis continues in a over and over again. My DB was working
fine and I could use the query analyzer, now however I cannot
query anything in the DB.
Any help would be great. I really dont want to reinstall this
as a solution.
TIA
dogdogThis message is usually preceded by another message indicating the cause the
error. Are these messages in the SQL Server error log or in a log generated
by your application?
Hope this helps.
Dan Guzman
SQL Server MVP
<dogdog@.noemail.com> wrote in message
news:pan.2006.03.25.15.15.20.194339@.noemail.com...
> For some reason I'm getting the following error on my MS2000 MSSQl
> server. THe message is being written into my logs on the server.
> MSSQL Error Msg 3621 The statement has been terminated
> THis is then followed by the information message
> Connected to DB
> THis continues in a over and over again. My DB was working
> fine and I could use the query analyzer, now however I cannot
> query anything in the DB.
> Any help would be great. I really dont want to reinstall this
> as a solution.
> TIA
> dogdog|||On Sat, 25 Mar 2006 09:32:12 +0000, Dan Guzman wrote:
> This message is usually preceded by another message indicating the cause t
he
> error. Are these messages in the SQL Server error log or in a log generat
ed
> by your application?
The next message after the error 3621 is Statement has been terminated
and is then followed by an information message
stating "connected to db" This sequence just keeps going and going
over and over.
Hope that helps. Because it means absolutely nothing to me.
tks
dogdog|||So these messages are in a log generated by your application? In that case,
it appears your application is reporting only the 3621 warning message and
not the preceding error that caused the statement to be terminated.
For example, below are the messages that are displayed by Query Analyzer
when I get a primary key violation:
Server: Msg 2627, Level 14, State 1, Line 1
Violation of PRIMARY KEY constraint 'PK_Table1'. Cannot insert duplicate key
in object 'Table1'.
The statement has been terminated.
If you have no control over the application logging behavior, I suggest you
run a Profiler trace to capture error events. This should help you identify
the problem SQL statements.
Hope this helps.
Dan Guzman
SQL Server MVP
<dogdog@.noemail.com> wrote in message
news:pan.2006.03.25.20.57.13.800017@.noemail.com...
> On Sat, 25 Mar 2006 09:32:12 +0000, Dan Guzman wrote:
>
> The next message after the error 3621 is Statement has been terminated
> and is then followed by an information message
> stating "connected to db" This sequence just keeps going and going
> over and over.
> Hope that helps. Because it means absolutely nothing to me.
> tks
> dogdog|||On Sun, 26 Mar 2006 06:27:38 +0000, Dan Guzman wrote:
First off thanks for taking your time on this and explaining things to
me a novice with mssql.
> So these messages are in a log generated by your application? In that cas
e,
> it appears your application is reporting only the 3621 warning message and
> not the preceding error that caused the statement to be terminated.
>
Yes they are being written to the system log by the mssql server. I
guess that was the best idea for this setup rather than having numerous
logs.
> For example, below are the messages that are displayed by Query Analyzer
> when I get a primary key violation:
> Server: Msg 2627, Level 14, State 1, Line 1
> Violation of PRIMARY KEY constraint 'PK_Table1'. Cannot insert duplicate k
ey
> in object 'Table1'.
> The statement has been terminated.
> If you have no control over the application logging behavior, I suggest yo
u
> run a Profiler trace to capture error events. This should help you identi
fy
> the problem SQL statements.
It seems as if the last query ran is "stuck" for lack of a better
understanding and just keeps querying. So it runs (without user
interaction for some reason) then reports the Error 3621 Statement
has been terminated. Then waits and reconnects to the server and
does it again. Seems crazy but I didnt make this stuff and it
makes it really hard to figure out when you inherit something like
this. Unfortunately there are no other logs to help in troubleshooting
and I want to avoid reinstalling the entire database. Luckily it
just came online and we just started testing it (i.e. sending
queries on test data) so if it does come down to reloading there
will be nothing lost. I just want to avoid that.
Thanks again for your help. If you have any other ideas I'll be glad
to try them out. I'm going to give the Profiler trace idea a shot.
Hopefully it will lead to something.
error 3520 on sql insert statement from a text file (only happens in 1 location)
I have a program that uses the Microsoft ODBC text driver Driver={Microsoft Text Driver (*.txt; *.csv)} this is used to make a connection to the database and then execute an sql insert to insert data from a flat file into an access database. The code works at hundreds of locations but for some reason it does not work at 1. I have ran an sql trace and found the error 3520 which would mean the data in the text file does not match the table that it is being inserted into but I have checked that and have tried using the same data on my computer and it works fine. I have also ran mdac compenent checker and there are no mismatched files. Any ideas on how to correct this or if anyone else has ever even seen this please help...Moving thread to Data Access Forum.
Error 3449 SQL Server shutdown
SQL Server 2005 X64 Standard running on Windows Server 2003 X64 Htper Threaded Quad processors with 16 GB RAM.
I have had two production servers shut down this week due to Error 3449: SQL Server must shut down in order to recover a database (database ID 1). The database is either a user database that could not be shut down or a system database. Restart SQL Server. If the database fails to recover after another startup, repair or restore the database.
Previous to the shutdown I received multiple Error 3314 & 602: Could not find an entry for table or index with partition ID 491897996509184 in database 2. This error can occur if a stored procedure references a dropped table, or metadata is corrupted. Drop and re-create the stored procedure, or execute DBCC CHECKDB.
Also, Error 9001: During undoing of a logged operation in database 'msdb', an error occurred at log record ID (838:208:1). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
Does anyone have an idea why I have begun receiving these error messages? I have run dbcc checkdb on Master and msdb and they do not show any problems.
I am getting the same error message except ofr the last one (, Error 9001: During undoing of a logged operation in database 'msdb', an error occurred at log record ID (838:208:1). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.)
How did you solve this problem,? and why this error showing up?
Thanks
|||Alright Chaps,
There is a hotfix available from microsoft for the errors that you guys are getting. Please check the below link:
http://support.microsoft.com/kb/916086
regards
Jag
Error 3449 SQL Server shutdown
SQL Server 2005 X64 Standard running on Windows Server 2003 X64 Htper Threaded Quad processors with 16 GB RAM.
I have had two production servers shut down this week due to Error 3449: SQL Server must shut down in order to recover a database (database ID 1). The database is either a user database that could not be shut down or a system database. Restart SQL Server. If the database fails to recover after another startup, repair or restore the database.
Previous to the shutdown I received multiple Error 3314 & 602: Could not find an entry for table or index with partition ID 491897996509184 in database 2. This error can occur if a stored procedure references a dropped table, or metadata is corrupted. Drop and re-create the stored procedure, or execute DBCC CHECKDB.
Also, Error 9001: During undoing of a logged operation in database 'msdb', an error occurred at log record ID (838:208:1). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
Does anyone have an idea why I have begun receiving these error messages? I have run dbcc checkdb on Master and msdb and they do not show any problems.
I am getting the same error message except ofr the last one (, Error 9001: During undoing of a logged operation in database 'msdb', an error occurred at log record ID (838:208:1). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.)
How did you solve this problem,? and why this error showing up?
Thanks
|||Alright Chaps,
There is a hotfix available from microsoft for the errors that you guys are getting. Please check the below link:
http://support.microsoft.com/kb/916086
regards
Jag
Error 3409 when trying to link to SQL Server table
Hi,
We are using SQL Server 2000 (latest SP) on Windows Server 2003.
Recently we made database changes where we deleted a number of columns from
the highest level table in our database hierarchy (every other table is
either a child or grandchild of this table).
Since we did that we can no linker establish links from Access 2003 to this
table. When we try, we get the following error message:
Invalid field definition <STAMP1> in definition of index or relationship.
(Error 3409)
STAMP1 is our Primary Key field.
None of the fields we deleted were index fields, and none were keys. We have
been racking our brains trying to find the issue but to no avail. Please
help. Thank you.A long time ago with access 2003 I ran into a similar problem. What I
had to do was to go into the Access application, delete all of the
linked tables, check the queries/reports, and finally relink the
tables given the names used in the queries and reports. After a
meticulous going over, it worked. I know from using it though, it
seems like everytime you make a change to the strcture (an index, PK,
etc) you have to relink the tables from Access.
Let me know what you find out.
-Sean
On Feb 29, 1:09=A0pm, Berean <Ber...@.discussions.microsoft.com> wrote:
> Hi,
> We are using SQL Server 2000 (latest SP) on Windows Server 2003.
> Recently we made database changes where we deleted a number of columns fro=m
> the highest level table in our database hierarchy (every other table is
> either a child or grandchild of this table).
> Since we did that we can no linker establish links from Access 2003 to thi=s
> table. When we try, we get the following error message:
> Invalid field definition <STAMP1> in definition of index or relationship.
> (Error 3409)
> STAMP1 is our Primary Key field.
> None of the fields we deleted were index fields, and none were keys. We ha=ve
> been racking our brains trying to find the issue but to no avail. Please
> help. Thank you.|||Hi Sean,
The effect is happening when anyone tries to link to the SQL Server table,
whether the link was preexisting or not. Even new link attempts generate the
same error.
We have tried rebuilding the indexes on SQL Server and even tried making a
dummy table with the data but no indexes. We could link to the dummy but not
to the one with indexes.
"Berean" wrote:
> Hi,
> We are using SQL Server 2000 (latest SP) on Windows Server 2003.
> Recently we made database changes where we deleted a number of columns from
> the highest level table in our database hierarchy (every other table is
> either a child or grandchild of this table).
> Since we did that we can no linker establish links from Access 2003 to this
> table. When we try, we get the following error message:
> Invalid field definition <STAMP1> in definition of index or relationship.
> (Error 3409)
> STAMP1 is our Primary Key field.
> None of the fields we deleted were index fields, and none were keys. We have
> been racking our brains trying to find the issue but to no avail. Please
> help. Thank you.|||We recently tried rebuilding and renaming all indexes, and are receiving the
same error.
To restate, this is occuring whether we open existing links to Access or try
to build new ones, and only happens on the table we dropped some columns
from.
"Berean" wrote:
> Hi Sean,
> The effect is happening when anyone tries to link to the SQL Server table,
> whether the link was preexisting or not. Even new link attempts generate the
> same error.
> We have tried rebuilding the indexes on SQL Server and even tried making a
> dummy table with the data but no indexes. We could link to the dummy but not
> to the one with indexes.
> "Berean" wrote:
> > Hi,
> >
> > We are using SQL Server 2000 (latest SP) on Windows Server 2003.
> >
> > Recently we made database changes where we deleted a number of columns from
> > the highest level table in our database hierarchy (every other table is
> > either a child or grandchild of this table).
> >
> > Since we did that we can no linker establish links from Access 2003 to this
> > table. When we try, we get the following error message:
> >
> > Invalid field definition <STAMP1> in definition of index or relationship.
> > (Error 3409)
> >
> > STAMP1 is our Primary Key field.
> >
> > None of the fields we deleted were index fields, and none were keys. We have
> > been racking our brains trying to find the issue but to no avail. Please
> > help. Thank you.
We are using SQL Server 2000 (latest SP) on Windows Server 2003.
Recently we made database changes where we deleted a number of columns from
the highest level table in our database hierarchy (every other table is
either a child or grandchild of this table).
Since we did that we can no linker establish links from Access 2003 to this
table. When we try, we get the following error message:
Invalid field definition <STAMP1> in definition of index or relationship.
(Error 3409)
STAMP1 is our Primary Key field.
None of the fields we deleted were index fields, and none were keys. We have
been racking our brains trying to find the issue but to no avail. Please
help. Thank you.A long time ago with access 2003 I ran into a similar problem. What I
had to do was to go into the Access application, delete all of the
linked tables, check the queries/reports, and finally relink the
tables given the names used in the queries and reports. After a
meticulous going over, it worked. I know from using it though, it
seems like everytime you make a change to the strcture (an index, PK,
etc) you have to relink the tables from Access.
Let me know what you find out.
-Sean
On Feb 29, 1:09=A0pm, Berean <Ber...@.discussions.microsoft.com> wrote:
> Hi,
> We are using SQL Server 2000 (latest SP) on Windows Server 2003.
> Recently we made database changes where we deleted a number of columns fro=m
> the highest level table in our database hierarchy (every other table is
> either a child or grandchild of this table).
> Since we did that we can no linker establish links from Access 2003 to thi=s
> table. When we try, we get the following error message:
> Invalid field definition <STAMP1> in definition of index or relationship.
> (Error 3409)
> STAMP1 is our Primary Key field.
> None of the fields we deleted were index fields, and none were keys. We ha=ve
> been racking our brains trying to find the issue but to no avail. Please
> help. Thank you.|||Hi Sean,
The effect is happening when anyone tries to link to the SQL Server table,
whether the link was preexisting or not. Even new link attempts generate the
same error.
We have tried rebuilding the indexes on SQL Server and even tried making a
dummy table with the data but no indexes. We could link to the dummy but not
to the one with indexes.
"Berean" wrote:
> Hi,
> We are using SQL Server 2000 (latest SP) on Windows Server 2003.
> Recently we made database changes where we deleted a number of columns from
> the highest level table in our database hierarchy (every other table is
> either a child or grandchild of this table).
> Since we did that we can no linker establish links from Access 2003 to this
> table. When we try, we get the following error message:
> Invalid field definition <STAMP1> in definition of index or relationship.
> (Error 3409)
> STAMP1 is our Primary Key field.
> None of the fields we deleted were index fields, and none were keys. We have
> been racking our brains trying to find the issue but to no avail. Please
> help. Thank you.|||We recently tried rebuilding and renaming all indexes, and are receiving the
same error.
To restate, this is occuring whether we open existing links to Access or try
to build new ones, and only happens on the table we dropped some columns
from.
"Berean" wrote:
> Hi Sean,
> The effect is happening when anyone tries to link to the SQL Server table,
> whether the link was preexisting or not. Even new link attempts generate the
> same error.
> We have tried rebuilding the indexes on SQL Server and even tried making a
> dummy table with the data but no indexes. We could link to the dummy but not
> to the one with indexes.
> "Berean" wrote:
> > Hi,
> >
> > We are using SQL Server 2000 (latest SP) on Windows Server 2003.
> >
> > Recently we made database changes where we deleted a number of columns from
> > the highest level table in our database hierarchy (every other table is
> > either a child or grandchild of this table).
> >
> > Since we did that we can no linker establish links from Access 2003 to this
> > table. When we try, we get the following error message:
> >
> > Invalid field definition <STAMP1> in definition of index or relationship.
> > (Error 3409)
> >
> > STAMP1 is our Primary Key field.
> >
> > None of the fields we deleted were index fields, and none were keys. We have
> > been racking our brains trying to find the issue but to no avail. Please
> > help. Thank you.
Error 3409 when trying to link to SQL Server table
Hi,
We are using SQL Server 2000 (latest SP) on Windows Server 2003.
Recently we made database changes where we deleted a number of columns from
the highest level table in our database hierarchy (every other table is
either a child or grandchild of this table).
Since we did that we can no linker establish links from Access 2003 to this
table. When we try, we get the following error message:
Invalid field definition <STAMP1> in definition of index or relationship.
(Error 3409)
STAMP1 is our Primary Key field.
None of the fields we deleted were index fields, and none were keys. We have
been racking our brains trying to find the issue but to no avail. Please
help. Thank you.
A long time ago with access 2003 I ran into a similar problem. What I
had to do was to go into the Access application, delete all of the
linked tables, check the queries/reports, and finally relink the
tables given the names used in the queries and reports. After a
meticulous going over, it worked. I know from using it though, it
seems like everytime you make a change to the strcture (an index, PK,
etc) you have to relink the tables from Access.
Let me know what you find out.
-Sean
On Feb 29, 1:09Xpm, Berean <Ber...@.discussions.microsoft.com> wrote:
> Hi,
> We are using SQL Server 2000 (latest SP) on Windows Server 2003.
> Recently we made database changes where we deleted a number of columns from
> the highest level table in our database hierarchy (every other table is
> either a child or grandchild of this table).
> Since we did that we can no linker establish links from Access 2003 to this
> table. When we try, we get the following error message:
> Invalid field definition <STAMP1> in definition of index or relationship.
> (Error 3409)
> STAMP1 is our Primary Key field.
> None of the fields we deleted were index fields, and none were keys. We have
> been racking our brains trying to find the issue but to no avail. Please
> help. Thank you.
|||Hi Sean,
The effect is happening when anyone tries to link to the SQL Server table,
whether the link was preexisting or not. Even new link attempts generate the
same error.
We have tried rebuilding the indexes on SQL Server and even tried making a
dummy table with the data but no indexes. We could link to the dummy but not
to the one with indexes.
"Berean" wrote:
> Hi,
> We are using SQL Server 2000 (latest SP) on Windows Server 2003.
> Recently we made database changes where we deleted a number of columns from
> the highest level table in our database hierarchy (every other table is
> either a child or grandchild of this table).
> Since we did that we can no linker establish links from Access 2003 to this
> table. When we try, we get the following error message:
> Invalid field definition <STAMP1> in definition of index or relationship.
> (Error 3409)
> STAMP1 is our Primary Key field.
> None of the fields we deleted were index fields, and none were keys. We have
> been racking our brains trying to find the issue but to no avail. Please
> help. Thank you.
|||We recently tried rebuilding and renaming all indexes, and are receiving the
same error.
To restate, this is occuring whether we open existing links to Access or try
to build new ones, and only happens on the table we dropped some columns
from.
"Berean" wrote:
[vbcol=seagreen]
> Hi Sean,
> The effect is happening when anyone tries to link to the SQL Server table,
> whether the link was preexisting or not. Even new link attempts generate the
> same error.
> We have tried rebuilding the indexes on SQL Server and even tried making a
> dummy table with the data but no indexes. We could link to the dummy but not
> to the one with indexes.
> "Berean" wrote:
We are using SQL Server 2000 (latest SP) on Windows Server 2003.
Recently we made database changes where we deleted a number of columns from
the highest level table in our database hierarchy (every other table is
either a child or grandchild of this table).
Since we did that we can no linker establish links from Access 2003 to this
table. When we try, we get the following error message:
Invalid field definition <STAMP1> in definition of index or relationship.
(Error 3409)
STAMP1 is our Primary Key field.
None of the fields we deleted were index fields, and none were keys. We have
been racking our brains trying to find the issue but to no avail. Please
help. Thank you.
A long time ago with access 2003 I ran into a similar problem. What I
had to do was to go into the Access application, delete all of the
linked tables, check the queries/reports, and finally relink the
tables given the names used in the queries and reports. After a
meticulous going over, it worked. I know from using it though, it
seems like everytime you make a change to the strcture (an index, PK,
etc) you have to relink the tables from Access.
Let me know what you find out.
-Sean
On Feb 29, 1:09Xpm, Berean <Ber...@.discussions.microsoft.com> wrote:
> Hi,
> We are using SQL Server 2000 (latest SP) on Windows Server 2003.
> Recently we made database changes where we deleted a number of columns from
> the highest level table in our database hierarchy (every other table is
> either a child or grandchild of this table).
> Since we did that we can no linker establish links from Access 2003 to this
> table. When we try, we get the following error message:
> Invalid field definition <STAMP1> in definition of index or relationship.
> (Error 3409)
> STAMP1 is our Primary Key field.
> None of the fields we deleted were index fields, and none were keys. We have
> been racking our brains trying to find the issue but to no avail. Please
> help. Thank you.
|||Hi Sean,
The effect is happening when anyone tries to link to the SQL Server table,
whether the link was preexisting or not. Even new link attempts generate the
same error.
We have tried rebuilding the indexes on SQL Server and even tried making a
dummy table with the data but no indexes. We could link to the dummy but not
to the one with indexes.
"Berean" wrote:
> Hi,
> We are using SQL Server 2000 (latest SP) on Windows Server 2003.
> Recently we made database changes where we deleted a number of columns from
> the highest level table in our database hierarchy (every other table is
> either a child or grandchild of this table).
> Since we did that we can no linker establish links from Access 2003 to this
> table. When we try, we get the following error message:
> Invalid field definition <STAMP1> in definition of index or relationship.
> (Error 3409)
> STAMP1 is our Primary Key field.
> None of the fields we deleted were index fields, and none were keys. We have
> been racking our brains trying to find the issue but to no avail. Please
> help. Thank you.
|||We recently tried rebuilding and renaming all indexes, and are receiving the
same error.
To restate, this is occuring whether we open existing links to Access or try
to build new ones, and only happens on the table we dropped some columns
from.
"Berean" wrote:
[vbcol=seagreen]
> Hi Sean,
> The effect is happening when anyone tries to link to the SQL Server table,
> whether the link was preexisting or not. Even new link attempts generate the
> same error.
> We have tried rebuilding the indexes on SQL Server and even tried making a
> dummy table with the data but no indexes. We could link to the dummy but not
> to the one with indexes.
> "Berean" wrote:
error 340
When I open up SQL Enterprise Manager (SQL 7) I get the following error
message ''Microsoft SQL-DMO error 340:General error'', i can press OK.
Enterprise is launched but there are no Registered servers. when I go and try
and register a new one this message appears ''Server registration information
cannot be changed on remote registries'.
what is happening and what is the fix.
tgarfitt wrote:
> When I open up SQL Enterprise Manager (SQL 7) I get the following
> error message ''Microsoft SQL-DMO error 340:General error'', i
> can press OK. Enterprise is launched but there are no Registered
> servers. when I go and try and register a new one this message
> appears ''Server registration information cannot be changed on remote
> registries'.
> what is happening and what is the fix.
See if this helps:
http://support.microsoft.com/default...26&Product=sql
David Gugick
Quest Software
www.imceda.com
www.quest.com
message ''Microsoft SQL-DMO error 340:General error'', i can press OK.
Enterprise is launched but there are no Registered servers. when I go and try
and register a new one this message appears ''Server registration information
cannot be changed on remote registries'.
what is happening and what is the fix.
tgarfitt wrote:
> When I open up SQL Enterprise Manager (SQL 7) I get the following
> error message ''Microsoft SQL-DMO error 340:General error'', i
> can press OK. Enterprise is launched but there are no Registered
> servers. when I go and try and register a new one this message
> appears ''Server registration information cannot be changed on remote
> registries'.
> what is happening and what is the fix.
See if this helps:
http://support.microsoft.com/default...26&Product=sql
David Gugick
Quest Software
www.imceda.com
www.quest.com
Error 3271 while doing a backup
Hi I am trying to do a backup of a database and it gives me the following
error
Nonrecoverable I/O error occurred on file 'C:\Program Files\Websense
Reporter\wslogdb61.mdf'. [SQLSTATE 42000] (Error 3271)
I ran dbcc checkdb and it gives consistency errors on one of the table, i
dropped all indexes on the table but its giving me errors while dropping the
last index, i think the index is corrupted . Is there any way to fix the
table or to drop the index without losing the data. I tried dbcc checkalloc
with rebuild and fast option still the same , i am hesitant to try the first
option of dbcc checkalloc which says it will fix the problem but will loose
some of the data. I tried copying the contents of the table to a temporary
table, but it gives I/O error.
Any suggestion '
Thanks
RodgerTry "DBCC CHECKDB"
Thanks & Regards,
P.C Sekhar.
"Rodger" <Rodger@.discussions.microsoft.com> wrote in message
news:78B5EACF-9948-46D6-8D96-C99B6B286E16@.microsoft.com...
> Hi I am trying to do a backup of a database and it gives me the following
> error
> Nonrecoverable I/O error occurred on file 'C:\Program Files\Websense
> Reporter\wslogdb61.mdf'. [SQLSTATE 42000] (Error 3271)
> I ran dbcc checkdb and it gives consistency errors on one of the table, i
> dropped all indexes on the table but its giving me errors while dropping
> the
> last index, i think the index is corrupted . Is there any way to fix the
> table or to drop the index without losing the data. I tried dbcc
> checkalloc
> with rebuild and fast option still the same , i am hesitant to try the
> first
> option of dbcc checkalloc which says it will fix the problem but will
> loose
> some of the data. I tried copying the contents of the table to a
> temporary
> table, but it gives I/O error.
> Any suggestion '
> Thanks
> Rodger
>|||Please read the entire message which i posted, i already tried dbcc checkdb
and tried dbcc checkalloc with 2 options.
Thanks
Rodger
"P.C Sekhar" wrote:
> Try "DBCC CHECKDB"
> Thanks & Regards,
> P.C Sekhar.
> "Rodger" <Rodger@.discussions.microsoft.com> wrote in message
> news:78B5EACF-9948-46D6-8D96-C99B6B286E16@.microsoft.com...
>
>
error
Nonrecoverable I/O error occurred on file 'C:\Program Files\Websense
Reporter\wslogdb61.mdf'. [SQLSTATE 42000] (Error 3271)
I ran dbcc checkdb and it gives consistency errors on one of the table, i
dropped all indexes on the table but its giving me errors while dropping the
last index, i think the index is corrupted . Is there any way to fix the
table or to drop the index without losing the data. I tried dbcc checkalloc
with rebuild and fast option still the same , i am hesitant to try the first
option of dbcc checkalloc which says it will fix the problem but will loose
some of the data. I tried copying the contents of the table to a temporary
table, but it gives I/O error.
Any suggestion '
Thanks
RodgerTry "DBCC CHECKDB"
Thanks & Regards,
P.C Sekhar.
"Rodger" <Rodger@.discussions.microsoft.com> wrote in message
news:78B5EACF-9948-46D6-8D96-C99B6B286E16@.microsoft.com...
> Hi I am trying to do a backup of a database and it gives me the following
> error
> Nonrecoverable I/O error occurred on file 'C:\Program Files\Websense
> Reporter\wslogdb61.mdf'. [SQLSTATE 42000] (Error 3271)
> I ran dbcc checkdb and it gives consistency errors on one of the table, i
> dropped all indexes on the table but its giving me errors while dropping
> the
> last index, i think the index is corrupted . Is there any way to fix the
> table or to drop the index without losing the data. I tried dbcc
> checkalloc
> with rebuild and fast option still the same , i am hesitant to try the
> first
> option of dbcc checkalloc which says it will fix the problem but will
> loose
> some of the data. I tried copying the contents of the table to a
> temporary
> table, but it gives I/O error.
> Any suggestion '
> Thanks
> Rodger
>|||Please read the entire message which i posted, i already tried dbcc checkdb
and tried dbcc checkalloc with 2 options.
Thanks
Rodger
"P.C Sekhar" wrote:
> Try "DBCC CHECKDB"
> Thanks & Regards,
> P.C Sekhar.
> "Rodger" <Rodger@.discussions.microsoft.com> wrote in message
> news:78B5EACF-9948-46D6-8D96-C99B6B286E16@.microsoft.com...
>
>
error 3271
Hi I am trying to do a backup of a database and it gives me the following
error
Nonrecoverable I/O error occurred on file 'C:\Program Files\Websense
Reporter\wslogdb61.mdf'. [SQLSTATE 42000] (Error 3271)
I ran dbcc checkdb and it gives consistency errors on one of the table, i
dropped all indexes on the table but its giving me errors while dropping the
last index, i think the index is corrupted . Is there any way to fix the
table or to drop the index without losing the data. I tried dbcc checkalloc
with rebuild and fast option still the same , i am hesitant to try the first
option of dbcc checkalloc which says it will fix the problem but will loose
some of the data. I tried copying the contents of the table to a temporary
table, but it gives I/O error.
Any suggestion '
Thanks
RodgerI assume you're on sql2k; thus, it's not possible to disable a corrupted
index to rebuild it.
You can try running "dbcc checktable(tb_name,repair_rebuild)". If it still
fails, you can force a drop of the index by deleting it from sysindexes.
(all warnings/disclaimers applied about direct system modification).
Restoring from a known backup is recommended for most corruption issues!
e.g.
exec sp_configure 'allow','1'
reconfigure with override
go
use <db>
go
--create a backup of sysindexes
--in case of mistake
select *
into sysindexes_bak
from sysindexes
go
delete sysindexes
where name='your_index'
go
exec sp_configure 'allow','0'
reconfigure with override
go
-oj
"Rodger" <Rodger@.discussions.microsoft.com> wrote in message
news:7D83EAD0-94D3-4B01-9C7F-7EBAE775450A@.microsoft.com...
> Hi I am trying to do a backup of a database and it gives me the following
> error
> Nonrecoverable I/O error occurred on file 'C:\Program Files\Websense
> Reporter\wslogdb61.mdf'. [SQLSTATE 42000] (Error 3271)
> I ran dbcc checkdb and it gives consistency errors on one of the table, i
> dropped all indexes on the table but its giving me errors while dropping
> the
> last index, i think the index is corrupted . Is there any way to fix the
> table or to drop the index without losing the data. I tried dbcc
> checkalloc
> with rebuild and fast option still the same , i am hesitant to try the
> first
> option of dbcc checkalloc which says it will fix the problem but will
> loose
> some of the data. I tried copying the contents of the table to a
> temporary
> table, but it gives I/O error.
> Any suggestion '
> Thanks
> Rodger
>
error
Nonrecoverable I/O error occurred on file 'C:\Program Files\Websense
Reporter\wslogdb61.mdf'. [SQLSTATE 42000] (Error 3271)
I ran dbcc checkdb and it gives consistency errors on one of the table, i
dropped all indexes on the table but its giving me errors while dropping the
last index, i think the index is corrupted . Is there any way to fix the
table or to drop the index without losing the data. I tried dbcc checkalloc
with rebuild and fast option still the same , i am hesitant to try the first
option of dbcc checkalloc which says it will fix the problem but will loose
some of the data. I tried copying the contents of the table to a temporary
table, but it gives I/O error.
Any suggestion '
Thanks
RodgerI assume you're on sql2k; thus, it's not possible to disable a corrupted
index to rebuild it.
You can try running "dbcc checktable(tb_name,repair_rebuild)". If it still
fails, you can force a drop of the index by deleting it from sysindexes.
(all warnings/disclaimers applied about direct system modification).
Restoring from a known backup is recommended for most corruption issues!
e.g.
exec sp_configure 'allow','1'
reconfigure with override
go
use <db>
go
--create a backup of sysindexes
--in case of mistake
select *
into sysindexes_bak
from sysindexes
go
delete sysindexes
where name='your_index'
go
exec sp_configure 'allow','0'
reconfigure with override
go
-oj
"Rodger" <Rodger@.discussions.microsoft.com> wrote in message
news:7D83EAD0-94D3-4B01-9C7F-7EBAE775450A@.microsoft.com...
> Hi I am trying to do a backup of a database and it gives me the following
> error
> Nonrecoverable I/O error occurred on file 'C:\Program Files\Websense
> Reporter\wslogdb61.mdf'. [SQLSTATE 42000] (Error 3271)
> I ran dbcc checkdb and it gives consistency errors on one of the table, i
> dropped all indexes on the table but its giving me errors while dropping
> the
> last index, i think the index is corrupted . Is there any way to fix the
> table or to drop the index without losing the data. I tried dbcc
> checkalloc
> with rebuild and fast option still the same , i am hesitant to try the
> first
> option of dbcc checkalloc which says it will fix the problem but will
> loose
> some of the data. I tried copying the contents of the table to a
> temporary
> table, but it gives I/O error.
> Any suggestion '
> Thanks
> Rodger
>
Error 3271
Hi,
during a backup of a database with the following command I get an error:
backup database TV_TOPO to disk='d:\Backup.nacher\TV_TOPO.bck'
Server: Nachr.-Nr. 3271, Schweregrad 16, Status 1, Zeile 1
Nonrecoverable I/O error occurred on file 'D:\Database\TV_TOPO.mdf'.
Server: Nachr.-Nr. 3013, Schweregrad 16, Status 1, Zeile 1
BACKUP DATABASE is terminating abnormally.
What can I do to repair the database files ?
Best regards
Axel LanserHi,
See SQL Server error log and Event viewer logs for more informations on this
error.
Run a DBCC CHECKDB on the database to make sure that it doesnt have any
consistency or allocation errors. It is most likely there will be errorr.
In that case you see the DBCC Checkdb with repair options in Books online.
If the database have errors and if it is difficult to solve using repair
options, Best option will be is to RESTORE from last
healthy backup or contact MS Product support.
Thanks
Hari
SQL Server MVP
"ALN" <ALN@.discussions.microsoft.com> wrote in message
news:B471FEE1-F07D-44F5-9150-ABF4C5BF630B@.microsoft.com...
> Hi,
> during a backup of a database with the following command I get an error:
> backup database TV_TOPO to disk='d:\Backup.nacher\TV_TOPO.bck'
> Server: Nachr.-Nr. 3271, Schweregrad 16, Status 1, Zeile 1
> Nonrecoverable I/O error occurred on file 'D:\Database\TV_TOPO.mdf'.
> Server: Nachr.-Nr. 3013, Schweregrad 16, Status 1, Zeile 1
> BACKUP DATABASE is terminating abnormally.
> What can I do to repair the database files ?
> Best regards
> Axel Lanser
during a backup of a database with the following command I get an error:
backup database TV_TOPO to disk='d:\Backup.nacher\TV_TOPO.bck'
Server: Nachr.-Nr. 3271, Schweregrad 16, Status 1, Zeile 1
Nonrecoverable I/O error occurred on file 'D:\Database\TV_TOPO.mdf'.
Server: Nachr.-Nr. 3013, Schweregrad 16, Status 1, Zeile 1
BACKUP DATABASE is terminating abnormally.
What can I do to repair the database files ?
Best regards
Axel LanserHi,
See SQL Server error log and Event viewer logs for more informations on this
error.
Run a DBCC CHECKDB on the database to make sure that it doesnt have any
consistency or allocation errors. It is most likely there will be errorr.
In that case you see the DBCC Checkdb with repair options in Books online.
If the database have errors and if it is difficult to solve using repair
options, Best option will be is to RESTORE from last
healthy backup or contact MS Product support.
Thanks
Hari
SQL Server MVP
"ALN" <ALN@.discussions.microsoft.com> wrote in message
news:B471FEE1-F07D-44F5-9150-ABF4C5BF630B@.microsoft.com...
> Hi,
> during a backup of a database with the following command I get an error:
> backup database TV_TOPO to disk='d:\Backup.nacher\TV_TOPO.bck'
> Server: Nachr.-Nr. 3271, Schweregrad 16, Status 1, Zeile 1
> Nonrecoverable I/O error occurred on file 'D:\Database\TV_TOPO.mdf'.
> Server: Nachr.-Nr. 3013, Schweregrad 16, Status 1, Zeile 1
> BACKUP DATABASE is terminating abnormally.
> What can I do to repair the database files ?
> Best regards
> Axel Lanser
error 3271
Hi everybody,
I'm trying to restore a database (approx. 30 / 50 or 100 GByte) from one
server on a second server.
When nearly reaching the end of the process, the restore stops and I get the
following message:
Server: Msg 3271, Level 16, State 1, Line 1
Nonrecoverable I/O error occurred on file '?'.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
I'm quite sure that the file is ok, because it is restored from tape to
diusk before I start the restore process. I mentioned three different
filesizes because it happens on all of them.
There is also enough space on disk (appro. 360 GB). The disk itself is a
RAID5.
Any ideas ? (tempdb problems / caching?)
thanks in advance
BodoPerhaps the database you did backup on was corrupt? Can you check that with DBCC CHECKDB?
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"msnews.microsoft.com" <bodo.meyer@.web.de> wrote in message
news:uyFxmeprDHA.1760@.TK2MSFTNGP10.phx.gbl...
> Hi everybody,
> I'm trying to restore a database (approx. 30 / 50 or 100 GByte) from one
> server on a second server.
> When nearly reaching the end of the process, the restore stops and I get the
> following message:
> Server: Msg 3271, Level 16, State 1, Line 1
> Nonrecoverable I/O error occurred on file '?'.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
> I'm quite sure that the file is ok, because it is restored from tape to
> diusk before I start the restore process. I mentioned three different
> filesizes because it happens on all of them.
> There is also enough space on disk (appro. 360 GB). The disk itself is a
> RAID5.
> Any ideas ? (tempdb problems / caching?)
> thanks in advance
> Bodo
>|||I have recently restored a db on our backup box. This might seem
elementary but after I received the same I/O level errors. I used a
cleaning tape in the drive and tried the restore again and was
successful. The optics may be dirty causing data to become corrupt. I
am using a Quantum DLT 4000 drive and the use tape light did come on
when I started the tape restore.
msnews.microsoft.com wrote:
> Hi everybody,
> I'm trying to restore a database (approx. 30 / 50 or 100 GByte) from one
> server on a second server.
> When nearly reaching the end of the process, the restore stops and I get the
> following message:
> Server: Msg 3271, Level 16, State 1, Line 1
> Nonrecoverable I/O error occurred on file '?'.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
> I'm quite sure that the file is ok, because it is restored from tape to
> diusk before I start the restore process. I mentioned three different
> filesizes because it happens on all of them.
> There is also enough space on disk (appro. 360 GB). The disk itself is a
> RAID5.
> Any ideas ? (tempdb problems / caching?)
> thanks in advance
> Bodo
>|||Thanks for Your ideas. I think the backup tape is ok, because other restores
work fine. Anyway, I'll try the cleaning. The database corruption must be
verified by another company, that sent me the db. Any idea about different
server language settings? The origin server is a english sqL2K, the target
is german.
Greetings
Bodo
"msnews.microsoft.com" <bodo.meyer@.web.de> schrieb im Newsbeitrag
news:uyFxmeprDHA.1760@.TK2MSFTNGP10.phx.gbl...
> Hi everybody,
> I'm trying to restore a database (approx. 30 / 50 or 100 GByte) from one
> server on a second server.
> When nearly reaching the end of the process, the restore stops and I get
the
> following message:
> Server: Msg 3271, Level 16, State 1, Line 1
> Nonrecoverable I/O error occurred on file '?'.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
> I'm quite sure that the file is ok, because it is restored from tape to
> diusk before I start the restore process. I mentioned three different
> filesizes because it happens on all of them.
> There is also enough space on disk (appro. 360 GB). The disk itself is a
> RAID5.
> Any ideas ? (tempdb problems / caching?)
> thanks in advance
> Bodo
>|||Language setting doesn't cause this type of errors (I'm afraid - in your situation :-) ).
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Bodo R. Meyer" <bodo.meyer@.web.de> wrote in message news:%23L9QphqrDHA.2448@.TK2MSFTNGP12.phx.gbl...
> Thanks for Your ideas. I think the backup tape is ok, because other restores
> work fine. Anyway, I'll try the cleaning. The database corruption must be
> verified by another company, that sent me the db. Any idea about different
> server language settings? The origin server is a english sqL2K, the target
> is german.
> Greetings
> Bodo
> "msnews.microsoft.com" <bodo.meyer@.web.de> schrieb im Newsbeitrag
> news:uyFxmeprDHA.1760@.TK2MSFTNGP10.phx.gbl...
> > Hi everybody,
> >
> > I'm trying to restore a database (approx. 30 / 50 or 100 GByte) from one
> > server on a second server.
> > When nearly reaching the end of the process, the restore stops and I get
> the
> > following message:
> >
> > Server: Msg 3271, Level 16, State 1, Line 1
> > Nonrecoverable I/O error occurred on file '?'.
> > Server: Msg 3013, Level 16, State 1, Line 1
> > RESTORE DATABASE is terminating abnormally.
> >
> > I'm quite sure that the file is ok, because it is restored from tape to
> > diusk before I start the restore process. I mentioned three different
> > filesizes because it happens on all of them.
> >
> > There is also enough space on disk (appro. 360 GB). The disk itself is a
> > RAID5.
> >
> > Any ideas ? (tempdb problems / caching?)
> > thanks in advance
> > Bodo
> >
> >
>
I'm trying to restore a database (approx. 30 / 50 or 100 GByte) from one
server on a second server.
When nearly reaching the end of the process, the restore stops and I get the
following message:
Server: Msg 3271, Level 16, State 1, Line 1
Nonrecoverable I/O error occurred on file '?'.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
I'm quite sure that the file is ok, because it is restored from tape to
diusk before I start the restore process. I mentioned three different
filesizes because it happens on all of them.
There is also enough space on disk (appro. 360 GB). The disk itself is a
RAID5.
Any ideas ? (tempdb problems / caching?)
thanks in advance
BodoPerhaps the database you did backup on was corrupt? Can you check that with DBCC CHECKDB?
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"msnews.microsoft.com" <bodo.meyer@.web.de> wrote in message
news:uyFxmeprDHA.1760@.TK2MSFTNGP10.phx.gbl...
> Hi everybody,
> I'm trying to restore a database (approx. 30 / 50 or 100 GByte) from one
> server on a second server.
> When nearly reaching the end of the process, the restore stops and I get the
> following message:
> Server: Msg 3271, Level 16, State 1, Line 1
> Nonrecoverable I/O error occurred on file '?'.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
> I'm quite sure that the file is ok, because it is restored from tape to
> diusk before I start the restore process. I mentioned three different
> filesizes because it happens on all of them.
> There is also enough space on disk (appro. 360 GB). The disk itself is a
> RAID5.
> Any ideas ? (tempdb problems / caching?)
> thanks in advance
> Bodo
>|||I have recently restored a db on our backup box. This might seem
elementary but after I received the same I/O level errors. I used a
cleaning tape in the drive and tried the restore again and was
successful. The optics may be dirty causing data to become corrupt. I
am using a Quantum DLT 4000 drive and the use tape light did come on
when I started the tape restore.
msnews.microsoft.com wrote:
> Hi everybody,
> I'm trying to restore a database (approx. 30 / 50 or 100 GByte) from one
> server on a second server.
> When nearly reaching the end of the process, the restore stops and I get the
> following message:
> Server: Msg 3271, Level 16, State 1, Line 1
> Nonrecoverable I/O error occurred on file '?'.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
> I'm quite sure that the file is ok, because it is restored from tape to
> diusk before I start the restore process. I mentioned three different
> filesizes because it happens on all of them.
> There is also enough space on disk (appro. 360 GB). The disk itself is a
> RAID5.
> Any ideas ? (tempdb problems / caching?)
> thanks in advance
> Bodo
>|||Thanks for Your ideas. I think the backup tape is ok, because other restores
work fine. Anyway, I'll try the cleaning. The database corruption must be
verified by another company, that sent me the db. Any idea about different
server language settings? The origin server is a english sqL2K, the target
is german.
Greetings
Bodo
"msnews.microsoft.com" <bodo.meyer@.web.de> schrieb im Newsbeitrag
news:uyFxmeprDHA.1760@.TK2MSFTNGP10.phx.gbl...
> Hi everybody,
> I'm trying to restore a database (approx. 30 / 50 or 100 GByte) from one
> server on a second server.
> When nearly reaching the end of the process, the restore stops and I get
the
> following message:
> Server: Msg 3271, Level 16, State 1, Line 1
> Nonrecoverable I/O error occurred on file '?'.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
> I'm quite sure that the file is ok, because it is restored from tape to
> diusk before I start the restore process. I mentioned three different
> filesizes because it happens on all of them.
> There is also enough space on disk (appro. 360 GB). The disk itself is a
> RAID5.
> Any ideas ? (tempdb problems / caching?)
> thanks in advance
> Bodo
>|||Language setting doesn't cause this type of errors (I'm afraid - in your situation :-) ).
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Bodo R. Meyer" <bodo.meyer@.web.de> wrote in message news:%23L9QphqrDHA.2448@.TK2MSFTNGP12.phx.gbl...
> Thanks for Your ideas. I think the backup tape is ok, because other restores
> work fine. Anyway, I'll try the cleaning. The database corruption must be
> verified by another company, that sent me the db. Any idea about different
> server language settings? The origin server is a english sqL2K, the target
> is german.
> Greetings
> Bodo
> "msnews.microsoft.com" <bodo.meyer@.web.de> schrieb im Newsbeitrag
> news:uyFxmeprDHA.1760@.TK2MSFTNGP10.phx.gbl...
> > Hi everybody,
> >
> > I'm trying to restore a database (approx. 30 / 50 or 100 GByte) from one
> > server on a second server.
> > When nearly reaching the end of the process, the restore stops and I get
> the
> > following message:
> >
> > Server: Msg 3271, Level 16, State 1, Line 1
> > Nonrecoverable I/O error occurred on file '?'.
> > Server: Msg 3013, Level 16, State 1, Line 1
> > RESTORE DATABASE is terminating abnormally.
> >
> > I'm quite sure that the file is ok, because it is restored from tape to
> > diusk before I start the restore process. I mentioned three different
> > filesizes because it happens on all of them.
> >
> > There is also enough space on disk (appro. 360 GB). The disk itself is a
> > RAID5.
> >
> > Any ideas ? (tempdb problems / caching?)
> > thanks in advance
> > Bodo
> >
> >
>
Error 3271
Hi,
during a backup of a database with the following command I get an error:
backup database TV_TOPO to disk='d:\Backup.nacher\TV_TOPO.bck'
Server: Nachr.-Nr. 3271, Schweregrad 16, Status 1, Zeile 1
Nonrecoverable I/O error occurred on file 'D:\Database\TV_TOPO.mdf'.
Server: Nachr.-Nr. 3013, Schweregrad 16, Status 1, Zeile 1
BACKUP DATABASE is terminating abnormally.
What can I do to repair the database files ?
Best regards
Axel Lanser
Hi,
See SQL Server error log and Event viewer logs for more informations on this
error.
Run a DBCC CHECKDB on the database to make sure that it doesnt have any
consistency or allocation errors. It is most likely there will be errorr.
In that case you see the DBCC Checkdb with repair options in Books online.
If the database have errors and if it is difficult to solve using repair
options, Best option will be is to RESTORE from last
healthy backup or contact MS Product support.
Thanks
Hari
SQL Server MVP
"ALN" <ALN@.discussions.microsoft.com> wrote in message
news:B471FEE1-F07D-44F5-9150-ABF4C5BF630B@.microsoft.com...
> Hi,
> during a backup of a database with the following command I get an error:
> backup database TV_TOPO to disk='d:\Backup.nacher\TV_TOPO.bck'
> Server: Nachr.-Nr. 3271, Schweregrad 16, Status 1, Zeile 1
> Nonrecoverable I/O error occurred on file 'D:\Database\TV_TOPO.mdf'.
> Server: Nachr.-Nr. 3013, Schweregrad 16, Status 1, Zeile 1
> BACKUP DATABASE is terminating abnormally.
> What can I do to repair the database files ?
> Best regards
> Axel Lanser
during a backup of a database with the following command I get an error:
backup database TV_TOPO to disk='d:\Backup.nacher\TV_TOPO.bck'
Server: Nachr.-Nr. 3271, Schweregrad 16, Status 1, Zeile 1
Nonrecoverable I/O error occurred on file 'D:\Database\TV_TOPO.mdf'.
Server: Nachr.-Nr. 3013, Schweregrad 16, Status 1, Zeile 1
BACKUP DATABASE is terminating abnormally.
What can I do to repair the database files ?
Best regards
Axel Lanser
Hi,
See SQL Server error log and Event viewer logs for more informations on this
error.
Run a DBCC CHECKDB on the database to make sure that it doesnt have any
consistency or allocation errors. It is most likely there will be errorr.
In that case you see the DBCC Checkdb with repair options in Books online.
If the database have errors and if it is difficult to solve using repair
options, Best option will be is to RESTORE from last
healthy backup or contact MS Product support.
Thanks
Hari
SQL Server MVP
"ALN" <ALN@.discussions.microsoft.com> wrote in message
news:B471FEE1-F07D-44F5-9150-ABF4C5BF630B@.microsoft.com...
> Hi,
> during a backup of a database with the following command I get an error:
> backup database TV_TOPO to disk='d:\Backup.nacher\TV_TOPO.bck'
> Server: Nachr.-Nr. 3271, Schweregrad 16, Status 1, Zeile 1
> Nonrecoverable I/O error occurred on file 'D:\Database\TV_TOPO.mdf'.
> Server: Nachr.-Nr. 3013, Schweregrad 16, Status 1, Zeile 1
> BACKUP DATABASE is terminating abnormally.
> What can I do to repair the database files ?
> Best regards
> Axel Lanser
error 3271
Hi I am trying to do a backup of a database and it gives me the following
error
Nonrecoverable I/O error occurred on file 'C:\Program Files\Websense
Reporter\wslogdb61.mdf'. [SQLSTATE 42000] (Error 3271)
I ran dbcc checkdb and it gives consistency errors on one of the table, i
dropped all indexes on the table but its giving me errors while dropping the
last index, i think the index is corrupted . Is there any way to fix the
table or to drop the index without losing the data. I tried dbcc checkalloc
with rebuild and fast option still the same , i am hesitant to try the first
option of dbcc checkalloc which says it will fix the problem but will loose
some of the data. I tried copying the contents of the table to a temporary
table, but it gives I/O error.
Any suggestion '
Thanks
RodgerI assume you're on sql2k; thus, it's not possible to disable a corrupted
index to rebuild it.
You can try running "dbcc checktable(tb_name,repair_rebuild)". If it still
fails, you can force a drop of the index by deleting it from sysindexes.
(all warnings/disclaimers applied about direct system modification).
Restoring from a known backup is recommended for most corruption issues!
e.g.
exec sp_configure 'allow','1'
reconfigure with override
go
use <db>
go
--create a backup of sysindexes
--in case of mistake
select *
into sysindexes_bak
from sysindexes
go
delete sysindexes
where name='your_index'
go
exec sp_configure 'allow','0'
reconfigure with override
go
-oj
"Rodger" <Rodger@.discussions.microsoft.com> wrote in message
news:7D83EAD0-94D3-4B01-9C7F-7EBAE775450A@.microsoft.com...
> Hi I am trying to do a backup of a database and it gives me the following
> error
> Nonrecoverable I/O error occurred on file 'C:\Program Files\Websense
> Reporter\wslogdb61.mdf'. [SQLSTATE 42000] (Error 3271)
> I ran dbcc checkdb and it gives consistency errors on one of the table, i
> dropped all indexes on the table but its giving me errors while dropping
> the
> last index, i think the index is corrupted . Is there any way to fix the
> table or to drop the index without losing the data. I tried dbcc
> checkalloc
> with rebuild and fast option still the same , i am hesitant to try the
> first
> option of dbcc checkalloc which says it will fix the problem but will
> loose
> some of the data. I tried copying the contents of the table to a
> temporary
> table, but it gives I/O error.
> Any suggestion '
> Thanks
> Rodger
>|||I assume you're on sql2k; thus, it's not possible to disable a corrupted
index to rebuild it.
You can try running "dbcc checktable(tb_name,repair_rebuild)". If it still
fails, you can force a drop of the index by deleting it from sysindexes.
(all warnings/disclaimers applied about direct system modification).
Restoring from a known backup is recommended for most corruption issues!
e.g.
exec sp_configure 'allow','1'
reconfigure with override
go
use <db>
go
--create a backup of sysindexes
--in case of mistake
select *
into sysindexes_bak
from sysindexes
go
delete sysindexes
where name='your_index'
go
exec sp_configure 'allow','0'
reconfigure with override
go
-oj
"Rodger" <Rodger@.discussions.microsoft.com> wrote in message
news:7D83EAD0-94D3-4B01-9C7F-7EBAE775450A@.microsoft.com...
> Hi I am trying to do a backup of a database and it gives me the following
> error
> Nonrecoverable I/O error occurred on file 'C:\Program Files\Websense
> Reporter\wslogdb61.mdf'. [SQLSTATE 42000] (Error 3271)
> I ran dbcc checkdb and it gives consistency errors on one of the table, i
> dropped all indexes on the table but its giving me errors while dropping
> the
> last index, i think the index is corrupted . Is there any way to fix the
> table or to drop the index without losing the data. I tried dbcc
> checkalloc
> with rebuild and fast option still the same , i am hesitant to try the
> first
> option of dbcc checkalloc which says it will fix the problem but will
> loose
> some of the data. I tried copying the contents of the table to a
> temporary
> table, but it gives I/O error.
> Any suggestion '
> Thanks
> Rodger
>
error
Nonrecoverable I/O error occurred on file 'C:\Program Files\Websense
Reporter\wslogdb61.mdf'. [SQLSTATE 42000] (Error 3271)
I ran dbcc checkdb and it gives consistency errors on one of the table, i
dropped all indexes on the table but its giving me errors while dropping the
last index, i think the index is corrupted . Is there any way to fix the
table or to drop the index without losing the data. I tried dbcc checkalloc
with rebuild and fast option still the same , i am hesitant to try the first
option of dbcc checkalloc which says it will fix the problem but will loose
some of the data. I tried copying the contents of the table to a temporary
table, but it gives I/O error.
Any suggestion '
Thanks
RodgerI assume you're on sql2k; thus, it's not possible to disable a corrupted
index to rebuild it.
You can try running "dbcc checktable(tb_name,repair_rebuild)". If it still
fails, you can force a drop of the index by deleting it from sysindexes.
(all warnings/disclaimers applied about direct system modification).
Restoring from a known backup is recommended for most corruption issues!
e.g.
exec sp_configure 'allow','1'
reconfigure with override
go
use <db>
go
--create a backup of sysindexes
--in case of mistake
select *
into sysindexes_bak
from sysindexes
go
delete sysindexes
where name='your_index'
go
exec sp_configure 'allow','0'
reconfigure with override
go
-oj
"Rodger" <Rodger@.discussions.microsoft.com> wrote in message
news:7D83EAD0-94D3-4B01-9C7F-7EBAE775450A@.microsoft.com...
> Hi I am trying to do a backup of a database and it gives me the following
> error
> Nonrecoverable I/O error occurred on file 'C:\Program Files\Websense
> Reporter\wslogdb61.mdf'. [SQLSTATE 42000] (Error 3271)
> I ran dbcc checkdb and it gives consistency errors on one of the table, i
> dropped all indexes on the table but its giving me errors while dropping
> the
> last index, i think the index is corrupted . Is there any way to fix the
> table or to drop the index without losing the data. I tried dbcc
> checkalloc
> with rebuild and fast option still the same , i am hesitant to try the
> first
> option of dbcc checkalloc which says it will fix the problem but will
> loose
> some of the data. I tried copying the contents of the table to a
> temporary
> table, but it gives I/O error.
> Any suggestion '
> Thanks
> Rodger
>|||I assume you're on sql2k; thus, it's not possible to disable a corrupted
index to rebuild it.
You can try running "dbcc checktable(tb_name,repair_rebuild)". If it still
fails, you can force a drop of the index by deleting it from sysindexes.
(all warnings/disclaimers applied about direct system modification).
Restoring from a known backup is recommended for most corruption issues!
e.g.
exec sp_configure 'allow','1'
reconfigure with override
go
use <db>
go
--create a backup of sysindexes
--in case of mistake
select *
into sysindexes_bak
from sysindexes
go
delete sysindexes
where name='your_index'
go
exec sp_configure 'allow','0'
reconfigure with override
go
-oj
"Rodger" <Rodger@.discussions.microsoft.com> wrote in message
news:7D83EAD0-94D3-4B01-9C7F-7EBAE775450A@.microsoft.com...
> Hi I am trying to do a backup of a database and it gives me the following
> error
> Nonrecoverable I/O error occurred on file 'C:\Program Files\Websense
> Reporter\wslogdb61.mdf'. [SQLSTATE 42000] (Error 3271)
> I ran dbcc checkdb and it gives consistency errors on one of the table, i
> dropped all indexes on the table but its giving me errors while dropping
> the
> last index, i think the index is corrupted . Is there any way to fix the
> table or to drop the index without losing the data. I tried dbcc
> checkalloc
> with rebuild and fast option still the same , i am hesitant to try the
> first
> option of dbcc checkalloc which says it will fix the problem but will
> loose
> some of the data. I tried copying the contents of the table to a
> temporary
> table, but it gives I/O error.
> Any suggestion '
> Thanks
> Rodger
>
Error 3271
Hi,
during a backup of a database with the following command I get an error:
backup database TV_TOPO to disk='d:\Backup.nacher\TV_TOPO.bck'
Server: Nachr.-Nr. 3271, Schweregrad 16, Status 1, Zeile 1
Nonrecoverable I/O error occurred on file 'D:\Database\TV_TOPO.mdf'.
Server: Nachr.-Nr. 3013, Schweregrad 16, Status 1, Zeile 1
BACKUP DATABASE is terminating abnormally.
What can I do to repair the database files ?
Best regards
Axel LanserHi,
See SQL Server error log and Event viewer logs for more informations on this
error.
Run a DBCC CHECKDB on the database to make sure that it doesnt have any
consistency or allocation errors. It is most likely there will be errorr.
In that case you see the DBCC Checkdb with repair options in Books online.
If the database have errors and if it is difficult to solve using repair
options, Best option will be is to RESTORE from last
healthy backup or contact MS Product support.
Thanks
Hari
SQL Server MVP
"ALN" <ALN@.discussions.microsoft.com> wrote in message
news:B471FEE1-F07D-44F5-9150-ABF4C5BF630B@.microsoft.com...
> Hi,
> during a backup of a database with the following command I get an error:
> backup database TV_TOPO to disk='d:\Backup.nacher\TV_TOPO.bck'
> Server: Nachr.-Nr. 3271, Schweregrad 16, Status 1, Zeile 1
> Nonrecoverable I/O error occurred on file 'D:\Database\TV_TOPO.mdf'.
> Server: Nachr.-Nr. 3013, Schweregrad 16, Status 1, Zeile 1
> BACKUP DATABASE is terminating abnormally.
> What can I do to repair the database files ?
> Best regards
> Axel Lanser
during a backup of a database with the following command I get an error:
backup database TV_TOPO to disk='d:\Backup.nacher\TV_TOPO.bck'
Server: Nachr.-Nr. 3271, Schweregrad 16, Status 1, Zeile 1
Nonrecoverable I/O error occurred on file 'D:\Database\TV_TOPO.mdf'.
Server: Nachr.-Nr. 3013, Schweregrad 16, Status 1, Zeile 1
BACKUP DATABASE is terminating abnormally.
What can I do to repair the database files ?
Best regards
Axel LanserHi,
See SQL Server error log and Event viewer logs for more informations on this
error.
Run a DBCC CHECKDB on the database to make sure that it doesnt have any
consistency or allocation errors. It is most likely there will be errorr.
In that case you see the DBCC Checkdb with repair options in Books online.
If the database have errors and if it is difficult to solve using repair
options, Best option will be is to RESTORE from last
healthy backup or contact MS Product support.
Thanks
Hari
SQL Server MVP
"ALN" <ALN@.discussions.microsoft.com> wrote in message
news:B471FEE1-F07D-44F5-9150-ABF4C5BF630B@.microsoft.com...
> Hi,
> during a backup of a database with the following command I get an error:
> backup database TV_TOPO to disk='d:\Backup.nacher\TV_TOPO.bck'
> Server: Nachr.-Nr. 3271, Schweregrad 16, Status 1, Zeile 1
> Nonrecoverable I/O error occurred on file 'D:\Database\TV_TOPO.mdf'.
> Server: Nachr.-Nr. 3013, Schweregrad 16, Status 1, Zeile 1
> BACKUP DATABASE is terminating abnormally.
> What can I do to repair the database files ?
> Best regards
> Axel Lanser
Error 3205 Restore SQLServer 2005 Express to MSDE
I am trying to restore a database backed up using SQL Server 2005 Express Edition to a server using MSDE. I get an error 3205 "Too many backup devices specified...64 max..."
I'm only specifying one file for the restore.
Ideas?
Once a database has been attached to a 2005 version it can not be restored to a 2000 version.
MSDE is 2000 and Express is 2005.
WesleyB
Visit my SQL Server weblog @. http://dis4ea.blogspot.com
|||Color me sad...
I control my server completely. If I install 2005 (either express or full version) on my server, will it migrate my existing msde database(s) automatically? Is there a way to do that? I have no problem upgrading as long as I can pull my existing db's up with me.
Can you help me?
Again, thanks for your answer. It's the only definitive answer I've received.
Jim
|||More information about upgrading MSDE to SQL Server Express can be found here: http://www.microsoft.com/sql/editions/express/upgrade.mspx.
Migrating your MSDE to the full version is also a viable option.
From 2000 to 2005 is not a problem only the other way around.
WesleyB
Visit my SQL Server weblog @. http://dis4ea.blogspot.com
Error 3205 Restore SQLServer 2005 Express to MSDE
I am trying to restore a database backed up using SQL Server 2005 Express Edition to a server using MSDE. I get an error 3205 "Too many backup devices specified...64 max..."
I'm only specifying one file for the restore.
Ideas?
Once a database has been attached to a 2005 version it can not be restored to a 2000 version.
MSDE is 2000 and Express is 2005.
WesleyB
Visit my SQL Server weblog @. http://dis4ea.blogspot.com
|||Color me sad...
I control my server completely. If I install 2005 (either express or full version) on my server, will it migrate my existing msde database(s) automatically? Is there a way to do that? I have no problem upgrading as long as I can pull my existing db's up with me.
Can you help me?
Again, thanks for your answer. It's the only definitive answer I've received.
Jim
|||More information about upgrading MSDE to SQL Server Express can be found here: http://www.microsoft.com/sql/editions/express/upgrade.mspx.
Migrating your MSDE to the full version is also a viable option.
From 2000 to 2005 is not a problem only the other way around.
WesleyB
Visit my SQL Server weblog @. http://dis4ea.blogspot.com
error 3205
when i restore database, i made an error:
RESTORE DATABASE tkb
I think it is not possible to restore a Sql server 2005 backup to Sql server 2000. So restore the backup to Sql server 2005 environment, it will work.
Server: Msg 3205, Level 16, State 2, Line 3
Too many backup devices specified for backup or restore; only 64 are allowed.
Server: Msg 3013, Level 16, State 1, Line 3
RESTORE DATABASE is terminating abnormally.
* my command:RESTORE DATABASE tkb
FROM DISK=’C:\ Program Files\Microsoft SQL Server\MSSQL\BACKUP\tkb.bak’
WITH FILE = 1,
NORECOVERY,NOUNLOAD, REPLACE, STATS = 10*** Help me, please!
My guess is that there was a typo in your command or script that confused the parser into thinking that you had specified more devices for the restore than you had.
Is this the EXACT command you used? Can you cut and paste from a script?
If it wasn't a script, have you tried re-typing and re-running the command?
|||Hi,I think it is not possible to restore a Sql server 2005 backup to Sql server 2000. So restore the backup to Sql server 2005 environment, it will work.
Error 3154: The backup set holds a backup of a database other than the existing 'xx' database.
HELP!
This is happening with a restore to SS 2005 from a SS2000 backup. This article says to use the 'WITH REPLACE' clause. The SS2005 management studio does not seem to allow this via the GUI.
http://msdn2.microsoft.com/en-us/library/aa238217(sql.80).aspx
Did you use the overwrite flag in the GUI if the database already existed ?HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de|||True and you can use the Query Editior to restore the same using RESTORE DATABASE .... WITH REPLACE, as referred in BOL it is easy.|||asdaf sa gs ga sgasg asg g a
Error 3154: The backup set holds a backup of a database other than the existing 'xx' datab
HELP!
This is happening with a restore to SS 2005 from a SS2000 backup. This article says to use the 'WITH REPLACE' clause. The SS2005 management studio does not seem to allow this via the GUI.
http://msdn2.microsoft.com/en-us/library/aa238217(sql.80).aspx
Did you use the overwrite flag in the GUI if the database already existed ?HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de|||True and you can use the Query Editior to restore the same using RESTORE DATABASE .... WITH REPLACE, as referred in BOL it is easy.
error 3146
Only one user has the problem.
I have given them a new copy of the switchboard but same startup error.
Thank you for your help.
>
> IOSDSQL 664-964 ENTER SQLSetStmtOption
> HSTMT 0A0B1EC8
> UWORD 0 <SQL_QUERY_TIMEOUT>
> SQLPOINTER 0x0000003C
>
> IOSDSQL 664-964 EXIT SQLSetStmtOption with return code 0
> (SQL_SUCCESS)
> HSTMT 0A0B1EC8
> UWORD 0 <SQL_QUERY_TIMEOUT>
> SQLPOINTER 0x0000003C (BADMEM)
>
> IOSDSQL 664-964 ENTER SQLExecDirect
> HSTMT 0A0B1EC8
> UCHAR * 0x09FB18C0 [ -3] "SELECT
> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int:No" FROM
> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
> SDWORD -3
>
> IOSDSQL 664-964 EXIT SQLExecDirect with return code -1
> (SQL_ERROR)
> HSTMT 0A0B1EC8
> UCHAR * 0x09FB18C0 [ -3] "SELECT
> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int:No" FROM
> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
> SDWORD -3
>
> DIAG [37000] [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1:
> Incorrect syntax near '.'. (170)
>Check to make sure QUOTED_IDENTIFIER is ON.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"BrianMultilLanguage" <brian@.clilang.com> wrote in message
news:12kv1p37855g42@.corp.supernews.com...
> Only one user has the problem.
> I have given them a new copy of the switchboard but same startup error.
> Thank you for your help.
>> IOSDSQL 664-964 ENTER SQLSetStmtOption
>> HSTMT 0A0B1EC8
>> UWORD 0 <SQL_QUERY_TIMEOUT>
>> SQLPOINTER 0x0000003C
>> IOSDSQL 664-964 EXIT SQLSetStmtOption with return code 0
>> (SQL_SUCCESS)
>> HSTMT 0A0B1EC8
>> UWORD 0 <SQL_QUERY_TIMEOUT>
>> SQLPOINTER 0x0000003C (BADMEM)
>> IOSDSQL 664-964 ENTER SQLExecDirect
>> HSTMT 0A0B1EC8
>> UCHAR * 0x09FB18C0 [ -3] "SELECT
>> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int:No" FROM
>> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
>> SDWORD -3
>> IOSDSQL 664-964 EXIT SQLExecDirect with return code -1
>> (SQL_ERROR)
>> HSTMT 0A0B1EC8
>> UCHAR * 0x09FB18C0 [ -3] "SELECT
>> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int:No" FROM
>> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
>> SDWORD -3
>> DIAG [37000] [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1:
>> Incorrect syntax near '.'. (170)
>|||BINGO~!
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:59C18CE9-04B5-49E1-87AB-4EA2DAD4E977@.microsoft.com...
> Check to make sure QUOTED_IDENTIFIER is ON.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "BrianMultilLanguage" <brian@.clilang.com> wrote in message
> news:12kv1p37855g42@.corp.supernews.com...
>> Only one user has the problem.
>> I have given them a new copy of the switchboard but same startup error.
>> Thank you for your help.
>>
>> IOSDSQL 664-964 ENTER SQLSetStmtOption
>> HSTMT 0A0B1EC8
>> UWORD 0 <SQL_QUERY_TIMEOUT>
>> SQLPOINTER 0x0000003C
>> IOSDSQL 664-964 EXIT SQLSetStmtOption with return code 0
>> (SQL_SUCCESS)
>> HSTMT 0A0B1EC8
>> UWORD 0 <SQL_QUERY_TIMEOUT>
>> SQLPOINTER 0x0000003C (BADMEM)
>> IOSDSQL 664-964 ENTER SQLExecDirect
>> HSTMT 0A0B1EC8
>> UCHAR * 0x09FB18C0 [ -3] "SELECT
>> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int:No" FROM
>> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
>> SDWORD -3
>> IOSDSQL 664-964 EXIT SQLExecDirect with return code -1
>> (SQL_ERROR)
>> HSTMT 0A0B1EC8
>> UCHAR * 0x09FB18C0 [ -3] "SELECT
>> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int:No" FROM
>> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
>> SDWORD -3
>> DIAG [37000] [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1:
>> Incorrect syntax near '.'. (170)
>>
>
I have given them a new copy of the switchboard but same startup error.
Thank you for your help.
>
> IOSDSQL 664-964 ENTER SQLSetStmtOption
> HSTMT 0A0B1EC8
> UWORD 0 <SQL_QUERY_TIMEOUT>
> SQLPOINTER 0x0000003C
>
> IOSDSQL 664-964 EXIT SQLSetStmtOption with return code 0
> (SQL_SUCCESS)
> HSTMT 0A0B1EC8
> UWORD 0 <SQL_QUERY_TIMEOUT>
> SQLPOINTER 0x0000003C (BADMEM)
>
> IOSDSQL 664-964 ENTER SQLExecDirect
> HSTMT 0A0B1EC8
> UCHAR * 0x09FB18C0 [ -3] "SELECT
> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int:No" FROM
> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
> SDWORD -3
>
> IOSDSQL 664-964 EXIT SQLExecDirect with return code -1
> (SQL_ERROR)
> HSTMT 0A0B1EC8
> UCHAR * 0x09FB18C0 [ -3] "SELECT
> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int:No" FROM
> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
> SDWORD -3
>
> DIAG [37000] [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1:
> Incorrect syntax near '.'. (170)
>Check to make sure QUOTED_IDENTIFIER is ON.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"BrianMultilLanguage" <brian@.clilang.com> wrote in message
news:12kv1p37855g42@.corp.supernews.com...
> Only one user has the problem.
> I have given them a new copy of the switchboard but same startup error.
> Thank you for your help.
>> IOSDSQL 664-964 ENTER SQLSetStmtOption
>> HSTMT 0A0B1EC8
>> UWORD 0 <SQL_QUERY_TIMEOUT>
>> SQLPOINTER 0x0000003C
>> IOSDSQL 664-964 EXIT SQLSetStmtOption with return code 0
>> (SQL_SUCCESS)
>> HSTMT 0A0B1EC8
>> UWORD 0 <SQL_QUERY_TIMEOUT>
>> SQLPOINTER 0x0000003C (BADMEM)
>> IOSDSQL 664-964 ENTER SQLExecDirect
>> HSTMT 0A0B1EC8
>> UCHAR * 0x09FB18C0 [ -3] "SELECT
>> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int:No" FROM
>> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
>> SDWORD -3
>> IOSDSQL 664-964 EXIT SQLExecDirect with return code -1
>> (SQL_ERROR)
>> HSTMT 0A0B1EC8
>> UCHAR * 0x09FB18C0 [ -3] "SELECT
>> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int:No" FROM
>> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
>> SDWORD -3
>> DIAG [37000] [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1:
>> Incorrect syntax near '.'. (170)
>|||BINGO~!
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:59C18CE9-04B5-49E1-87AB-4EA2DAD4E977@.microsoft.com...
> Check to make sure QUOTED_IDENTIFIER is ON.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "BrianMultilLanguage" <brian@.clilang.com> wrote in message
> news:12kv1p37855g42@.corp.supernews.com...
>> Only one user has the problem.
>> I have given them a new copy of the switchboard but same startup error.
>> Thank you for your help.
>>
>> IOSDSQL 664-964 ENTER SQLSetStmtOption
>> HSTMT 0A0B1EC8
>> UWORD 0 <SQL_QUERY_TIMEOUT>
>> SQLPOINTER 0x0000003C
>> IOSDSQL 664-964 EXIT SQLSetStmtOption with return code 0
>> (SQL_SUCCESS)
>> HSTMT 0A0B1EC8
>> UWORD 0 <SQL_QUERY_TIMEOUT>
>> SQLPOINTER 0x0000003C (BADMEM)
>> IOSDSQL 664-964 ENTER SQLExecDirect
>> HSTMT 0A0B1EC8
>> UCHAR * 0x09FB18C0 [ -3] "SELECT
>> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int:No" FROM
>> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
>> SDWORD -3
>> IOSDSQL 664-964 EXIT SQLExecDirect with return code -1
>> (SQL_ERROR)
>> HSTMT 0A0B1EC8
>> UCHAR * 0x09FB18C0 [ -3] "SELECT
>> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int:No" FROM
>> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
>> SDWORD -3
>> DIAG [37000] [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1:
>> Incorrect syntax near '.'. (170)
>>
>
error 3146
Only one user has the problem.
I have given them a new copy of the switchboard but same startup error.
Thank you for your help.
> IOSDSQL 664-964 ENTER SQLSetStmtOption
> HSTMT 0A0B1EC8
> UWORD 0 <SQL_QUERY_TIMEOUT>
> SQLPOINTER 0x0000003C
> IOSDSQL 664-964 EXIT SQLSetStmtOption with return code 0
> (SQL_SUCCESS)
> HSTMT 0A0B1EC8
> UWORD 0 <SQL_QUERY_TIMEOUT>
> SQLPOINTER 0x0000003C (BADMEM)
> IOSDSQL 664-964 ENTER SQLExecDirect
> HSTMT 0A0B1EC8
> UCHAR * 0x09FB18C0 [ -3] "SELECT
> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int: No" FROM
> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
> SDWORD -3
> IOSDSQL 664-964 EXIT SQLExecDirect with return code -1
> (SQL_ERROR)
> HSTMT 0A0B1EC8
> UCHAR * 0x09FB18C0 [ -3] "SELECT
> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int: No" FROM
> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
> SDWORD -3
> DIAG [37000] [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1:
> Incorrect syntax near '.'. (170)
>
Check to make sure QUOTED_IDENTIFIER is ON.
Hope this helps.
Dan Guzman
SQL Server MVP
"BrianMultilLanguage" <brian@.clilang.com> wrote in message
news:12kv1p37855g42@.corp.supernews.com...
> Only one user has the problem.
> I have given them a new copy of the switchboard but same startup error.
> Thank you for your help.
>
>
|||BINGO~!
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:59C18CE9-04B5-49E1-87AB-4EA2DAD4E977@.microsoft.com...
> Check to make sure QUOTED_IDENTIFIER is ON.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "BrianMultilLanguage" <brian@.clilang.com> wrote in message
> news:12kv1p37855g42@.corp.supernews.com...
>
I have given them a new copy of the switchboard but same startup error.
Thank you for your help.
> IOSDSQL 664-964 ENTER SQLSetStmtOption
> HSTMT 0A0B1EC8
> UWORD 0 <SQL_QUERY_TIMEOUT>
> SQLPOINTER 0x0000003C
> IOSDSQL 664-964 EXIT SQLSetStmtOption with return code 0
> (SQL_SUCCESS)
> HSTMT 0A0B1EC8
> UWORD 0 <SQL_QUERY_TIMEOUT>
> SQLPOINTER 0x0000003C (BADMEM)
> IOSDSQL 664-964 ENTER SQLExecDirect
> HSTMT 0A0B1EC8
> UCHAR * 0x09FB18C0 [ -3] "SELECT
> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int: No" FROM
> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
> SDWORD -3
> IOSDSQL 664-964 EXIT SQLExecDirect with return code -1
> (SQL_ERROR)
> HSTMT 0A0B1EC8
> UCHAR * 0x09FB18C0 [ -3] "SELECT
> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int: No" FROM
> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
> SDWORD -3
> DIAG [37000] [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1:
> Incorrect syntax near '.'. (170)
>
Check to make sure QUOTED_IDENTIFIER is ON.
Hope this helps.
Dan Guzman
SQL Server MVP
"BrianMultilLanguage" <brian@.clilang.com> wrote in message
news:12kv1p37855g42@.corp.supernews.com...
> Only one user has the problem.
> I have given them a new copy of the switchboard but same startup error.
> Thank you for your help.
>
>
|||BINGO~!
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:59C18CE9-04B5-49E1-87AB-4EA2DAD4E977@.microsoft.com...
> Check to make sure QUOTED_IDENTIFIER is ON.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "BrianMultilLanguage" <brian@.clilang.com> wrote in message
> news:12kv1p37855g42@.corp.supernews.com...
>
error 3146
Only one user has the problem.
I have given them a new copy of the switchboard but same startup error.
Thank you for your help.
> IOSDSQL 664-964 ENTER SQLSetStmtOption
> HSTMT 0A0B1EC8
> UWORD 0 <SQL_QUERY_TIMEOUT>
> SQLPOINTER 0x0000003C
> IOSDSQL 664-964 EXIT SQLSetStmtOption with return code 0
> (SQL_SUCCESS)
> HSTMT 0A0B1EC8
> UWORD 0 <SQL_QUERY_TIMEOUT>
> SQLPOINTER 0x0000003C (BADMEM)
> IOSDSQL 664-964 ENTER SQLExecDirect
> HSTMT 0A0B1EC8
> UCHAR * 0x09FB18C0 [ -3] "SELECT
> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int:No" FROM
> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
> SDWORD -3
> IOSDSQL 664-964 EXIT SQLExecDirect with return code -1
> (SQL_ERROR)
> HSTMT 0A0B1EC8
> UCHAR * 0x09FB18C0 [ -3] "SELECT
> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int:No" FROM
> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
> SDWORD -3
> DIAG [37000] [Microsoft][ODBC SQL Server Driver][SQL Serv
er]Line 1:
> Incorrect syntax near '.'. (170)
>Check to make sure QUOTED_IDENTIFIER is ON.
Hope this helps.
Dan Guzman
SQL Server MVP
"BrianMultilLanguage" <brian@.clilang.com> wrote in message
news:12kv1p37855g42@.corp.supernews.com...
> Only one user has the problem.
> I have given them a new copy of the switchboard but same startup error.
> Thank you for your help.
>
>|||BINGO~!
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:59C18CE9-04B5-49E1-87AB-4EA2DAD4E977@.microsoft.com...
> Check to make sure QUOTED_IDENTIFIER is ON.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "BrianMultilLanguage" <brian@.clilang.com> wrote in message
> news:12kv1p37855g42@.corp.supernews.com...
>
I have given them a new copy of the switchboard but same startup error.
Thank you for your help.
> IOSDSQL 664-964 ENTER SQLSetStmtOption
> HSTMT 0A0B1EC8
> UWORD 0 <SQL_QUERY_TIMEOUT>
> SQLPOINTER 0x0000003C
> IOSDSQL 664-964 EXIT SQLSetStmtOption with return code 0
> (SQL_SUCCESS)
> HSTMT 0A0B1EC8
> UWORD 0 <SQL_QUERY_TIMEOUT>
> SQLPOINTER 0x0000003C (BADMEM)
> IOSDSQL 664-964 ENTER SQLExecDirect
> HSTMT 0A0B1EC8
> UCHAR * 0x09FB18C0 [ -3] "SELECT
> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int:No" FROM
> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
> SDWORD -3
> IOSDSQL 664-964 EXIT SQLExecDirect with return code -1
> (SQL_ERROR)
> HSTMT 0A0B1EC8
> UCHAR * 0x09FB18C0 [ -3] "SELECT
> "dbo"."New_OnCall"."Lang","dbo"."New_OnCall"."Int:No" FROM
> "dbo"."New_OnCall" ORDER BY "Lang" \ 0"
> SDWORD -3
> DIAG [37000] [Microsoft][ODBC SQL Server Driver][SQL Serv
er]Line 1:
> Incorrect syntax near '.'. (170)
>Check to make sure QUOTED_IDENTIFIER is ON.
Hope this helps.
Dan Guzman
SQL Server MVP
"BrianMultilLanguage" <brian@.clilang.com> wrote in message
news:12kv1p37855g42@.corp.supernews.com...
> Only one user has the problem.
> I have given them a new copy of the switchboard but same startup error.
> Thank you for your help.
>
>|||BINGO~!
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:59C18CE9-04B5-49E1-87AB-4EA2DAD4E977@.microsoft.com...
> Check to make sure QUOTED_IDENTIFIER is ON.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "BrianMultilLanguage" <brian@.clilang.com> wrote in message
> news:12kv1p37855g42@.corp.supernews.com...
>
Error 3140 on SQL Server 2000
When I do shrink trans log file or database error message came out "Error
3140 Could not adjust the space allocation for the file". I search on
Microsoft WEB only show SQL 7.0. Can someone help me please I already
installed SP3 for it.
Bin,
How are you trying to shrink this log? What other steps have you taken before trying to shrink? Are you doing this from enterprise manage or through query analyzer?
Please post the exact error message here and someone may be able to assist.
Tunji O
"BIN YANG" <BINYANG@.discussions.microsoft.com> wrote in message news:8B628FE5-842E-4A14-9331-2BA683E3F97B@.microsoft.com...
When I do shrink trans log file or database error message came out "Error
3140 Could not adjust the space allocation for the file". I search on
Microsoft WEB only show SQL 7.0. Can someone help me please I already
installed SP3 for it.
|||I shrink data through SQL Server Enterprise Manager All Tasks Shrink Database
task the error message as follow:
Microsoft SQL-DMO(ODBC SQLSTATE:42000)
Error 3140:Could not adjust the space allocation for the file'truck_data'.
DBCC execution completeed. If DBCC printed error messages, contact your
system administrator.
"Tunji" wrote:
> Bin,
> How are you trying to shrink this log? What other steps have you taken before trying to shrink? Are you doing this from enterprise manage or through query analyzer?
> Please post the exact error message here and someone may be able to assist.
> Tunji O
> "BIN YANG" <BINYANG@.discussions.microsoft.com> wrote in message news:8B628FE5-842E-4A14-9331-2BA683E3F97B@.microsoft.com...
> When I do shrink trans log file or database error message came out "Error
> 3140 Could not adjust the space allocation for the file". I search on
> Microsoft WEB only show SQL 7.0. Can someone help me please I already
> installed SP3 for it
3140 Could not adjust the space allocation for the file". I search on
Microsoft WEB only show SQL 7.0. Can someone help me please I already
installed SP3 for it.
Bin,
How are you trying to shrink this log? What other steps have you taken before trying to shrink? Are you doing this from enterprise manage or through query analyzer?
Please post the exact error message here and someone may be able to assist.
Tunji O
"BIN YANG" <BINYANG@.discussions.microsoft.com> wrote in message news:8B628FE5-842E-4A14-9331-2BA683E3F97B@.microsoft.com...
When I do shrink trans log file or database error message came out "Error
3140 Could not adjust the space allocation for the file". I search on
Microsoft WEB only show SQL 7.0. Can someone help me please I already
installed SP3 for it.
|||I shrink data through SQL Server Enterprise Manager All Tasks Shrink Database
task the error message as follow:
Microsoft SQL-DMO(ODBC SQLSTATE:42000)
Error 3140:Could not adjust the space allocation for the file'truck_data'.
DBCC execution completeed. If DBCC printed error messages, contact your
system administrator.
"Tunji" wrote:
> Bin,
> How are you trying to shrink this log? What other steps have you taken before trying to shrink? Are you doing this from enterprise manage or through query analyzer?
> Please post the exact error message here and someone may be able to assist.
> Tunji O
> "BIN YANG" <BINYANG@.discussions.microsoft.com> wrote in message news:8B628FE5-842E-4A14-9331-2BA683E3F97B@.microsoft.com...
> When I do shrink trans log file or database error message came out "Error
> 3140 Could not adjust the space allocation for the file". I search on
> Microsoft WEB only show SQL 7.0. Can someone help me please I already
> installed SP3 for it
Error 3140 on SQL Server 2000
When I do shrink trans log file or database error message came out "Error
3140 Could not adjust the space allocation for the file". I search on
Microsoft WEB only show SQL 7.0. Can someone help me please I already
installed SP3 for it.Bin,
How are you trying to shrink this log? What other steps have you taken befor
e trying to shrink? Are you doing this from enterprise manage or through que
ry analyzer?
Please post the exact error message here and someone may be able to assist.
Tunji O
"BIN YANG" <BINYANG@.discussions.microsoft.com> wrote in message news:8B628FE
5-842E-4A14-9331-2BA683E3F97B@.microsoft.com...
When I do shrink trans log file or database error message came out "Error
3140 Could not adjust the space allocation for the file". I search on
Microsoft WEB only show SQL 7.0. Can someone help me please I already
installed SP3 for it.|||I shrink data through SQL Server Enterprise Manager All Tasks Shrink Databas
e
task the error message as follow:
Microsoft SQL-DMO(ODBC SQLSTATE:42000)
Error 3140:Could not adjust the space allocation for the file'truck_data'.
DBCC execution completeed. If DBCC printed error messages, contact your
system administrator.
"Tunji" wrote:
> Bin,
> How are you trying to shrink this log? What other steps have you taken bef
ore trying to shrink? Are you doing this from enterprise manage or through q
uery analyzer?
> Please post the exact error message here and someone may be able to assist
.
> Tunji O
> "BIN YANG" <BINYANG@.discussions.microsoft.com> wrote in message news:8B6
28FE5-842E-4A14-9331-2BA683E3F97B@.microsoft.com...
> When I do shrink trans log file or database error message came out "Erro
r
> 3140 Could not adjust the space allocation for the file". I search on
> Microsoft WEB only show SQL 7.0. Can someone help me please I already
> installed SP3 for it
3140 Could not adjust the space allocation for the file". I search on
Microsoft WEB only show SQL 7.0. Can someone help me please I already
installed SP3 for it.Bin,
How are you trying to shrink this log? What other steps have you taken befor
e trying to shrink? Are you doing this from enterprise manage or through que
ry analyzer?
Please post the exact error message here and someone may be able to assist.
Tunji O
"BIN YANG" <BINYANG@.discussions.microsoft.com> wrote in message news:8B628FE
5-842E-4A14-9331-2BA683E3F97B@.microsoft.com...
When I do shrink trans log file or database error message came out "Error
3140 Could not adjust the space allocation for the file". I search on
Microsoft WEB only show SQL 7.0. Can someone help me please I already
installed SP3 for it.|||I shrink data through SQL Server Enterprise Manager All Tasks Shrink Databas
e
task the error message as follow:
Microsoft SQL-DMO(ODBC SQLSTATE:42000)
Error 3140:Could not adjust the space allocation for the file'truck_data'.
DBCC execution completeed. If DBCC printed error messages, contact your
system administrator.
"Tunji" wrote:
> Bin,
> How are you trying to shrink this log? What other steps have you taken bef
ore trying to shrink? Are you doing this from enterprise manage or through q
uery analyzer?
> Please post the exact error message here and someone may be able to assist
.
> Tunji O
> "BIN YANG" <BINYANG@.discussions.microsoft.com> wrote in message news:8B6
28FE5-842E-4A14-9331-2BA683E3F97B@.microsoft.com...
> When I do shrink trans log file or database error message came out "Erro
r
> 3140 Could not adjust the space allocation for the file". I search on
> Microsoft WEB only show SQL 7.0. Can someone help me please I already
> installed SP3 for it
Error 3140 on SQL Server 2000
When I do shrink trans log file or database error message came out "Error
3140 Could not adjust the space allocation for the file". I search on
Microsoft WEB only show SQL 7.0. Can someone help me please I already
installed SP3 for it.This is a multi-part message in MIME format.
--=_NextPart_000_008A_01C4CCFC.9D0630B0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
Bin,
How are you trying to shrink this log? What other steps have you taken =before trying to shrink? Are you doing this from enterprise manage or =through query analyzer? Please post the exact error message here and someone may be able to =assist.
Tunji O
"BIN YANG" <BINYANG@.discussions.microsoft.com> wrote in message =news:8B628FE5-842E-4A14-9331-2BA683E3F97B@.microsoft.com...
When I do shrink trans log file or database error message came out ="Error 3140 Could not adjust the space allocation for the file". I search on Microsoft WEB only show SQL 7.0. Can someone help me please I already installed SP3 for it.
--=_NextPart_000_008A_01C4CCFC.9D0630B0
Content-Type: text/html;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Bin,
How are you trying to shrink this log? =What other steps have you taken before trying to shrink? Are you doing this from =enterprise manage or through query analyzer?
Please post the exact error message =here and someone may be able to assist.
Tunji O
"BIN YANG" wrote in message news:8B6=28FE5-842E-4A14-9331-2BA683E3F97B@.microsoft.com...When I do shrink trans log file or database error message came out "Error =3140 Could not adjust the space allocation for the file". I search on =Microsoft WEB only show SQL 7.0. Can someone help me please I already =installed SP3 for it.
--=_NextPart_000_008A_01C4CCFC.9D0630B0--|||I shrink data through SQL Server Enterprise Manager All Tasks Shrink Database
task the error message as follow:
Microsoft SQL-DMO(ODBC SQLSTATE:42000)
Error 3140:Could not adjust the space allocation for the file'truck_data'.
DBCC execution completeed. If DBCC printed error messages, contact your
system administrator.
"Tunji" wrote:
> Bin,
> How are you trying to shrink this log? What other steps have you taken before trying to shrink? Are you doing this from enterprise manage or through query analyzer?
> Please post the exact error message here and someone may be able to assist.
> Tunji O
> "BIN YANG" <BINYANG@.discussions.microsoft.com> wrote in message news:8B628FE5-842E-4A14-9331-2BA683E3F97B@.microsoft.com...
> When I do shrink trans log file or database error message came out "Error
> 3140 Could not adjust the space allocation for the file". I search on
> Microsoft WEB only show SQL 7.0. Can someone help me please I already
> installed SP3 for it
3140 Could not adjust the space allocation for the file". I search on
Microsoft WEB only show SQL 7.0. Can someone help me please I already
installed SP3 for it.This is a multi-part message in MIME format.
--=_NextPart_000_008A_01C4CCFC.9D0630B0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
Bin,
How are you trying to shrink this log? What other steps have you taken =before trying to shrink? Are you doing this from enterprise manage or =through query analyzer? Please post the exact error message here and someone may be able to =assist.
Tunji O
"BIN YANG" <BINYANG@.discussions.microsoft.com> wrote in message =news:8B628FE5-842E-4A14-9331-2BA683E3F97B@.microsoft.com...
When I do shrink trans log file or database error message came out ="Error 3140 Could not adjust the space allocation for the file". I search on Microsoft WEB only show SQL 7.0. Can someone help me please I already installed SP3 for it.
--=_NextPart_000_008A_01C4CCFC.9D0630B0
Content-Type: text/html;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Bin,
How are you trying to shrink this log? =What other steps have you taken before trying to shrink? Are you doing this from =enterprise manage or through query analyzer?
Please post the exact error message =here and someone may be able to assist.
Tunji O
"BIN YANG"
--=_NextPart_000_008A_01C4CCFC.9D0630B0--|||I shrink data through SQL Server Enterprise Manager All Tasks Shrink Database
task the error message as follow:
Microsoft SQL-DMO(ODBC SQLSTATE:42000)
Error 3140:Could not adjust the space allocation for the file'truck_data'.
DBCC execution completeed. If DBCC printed error messages, contact your
system administrator.
"Tunji" wrote:
> Bin,
> How are you trying to shrink this log? What other steps have you taken before trying to shrink? Are you doing this from enterprise manage or through query analyzer?
> Please post the exact error message here and someone may be able to assist.
> Tunji O
> "BIN YANG" <BINYANG@.discussions.microsoft.com> wrote in message news:8B628FE5-842E-4A14-9331-2BA683E3F97B@.microsoft.com...
> When I do shrink trans log file or database error message came out "Error
> 3140 Could not adjust the space allocation for the file". I search on
> Microsoft WEB only show SQL 7.0. Can someone help me please I already
> installed SP3 for it
Error 3123 in SQL Restore
Trying to restore a database from a personal edition SQL 2000 to another PC.
I get the following message
The media set for database 'TeamSpiritDataTDB' has 2 family members but only
1 are provided. All members must be provided.
What does this actually mean. Is the file corrupt, or is there a problem
with the way it was backed up? I didn't back it up, but our normal procedure
in this circumstance is just to make a complete back up to a file.
Any ideas gratefully received.
Thanks
Rowland
The backup was take to multiple disks and you have provided only one.
http://forums.databasejournal.com/hi...p/33896-1.html
Nik Marshall-Blank MCSD/MCDBA
"Rowland Costin" <technical@.selven.co.uk> wrote in message
news:eA8CksEwFHA.3400@.TK2MSFTNGP14.phx.gbl...
> Trying to restore a database from a personal edition SQL 2000 to another
> PC. I get the following message
> The media set for database 'TeamSpiritDataTDB' has 2 family members but
> only 1 are provided. All members must be provided.
> What does this actually mean. Is the file corrupt, or is there a problem
> with the way it was backed up? I didn't back it up, but our normal
> procedure in this circumstance is just to make a complete back up to a
> file.
> Any ideas gratefully received.
> Thanks
> Rowland
>
|||Thanks for the reply. The database backup in question was just a couple of
megs and was copied to CD. So I guess it must have been corrupt in some way,
cos it was backed up to file on the hard drive first. Still I guessed
something like this so fortunately as it was just a transfer of database and
not a real backup, we just got it backed up again and all was ok. Weird huh.
Cheers
Rowland
"Nik Marshall-Blank (delete fcom for my email address)"
<NikMB@.fcomiNodefcom.afcomt> wrote in message
news:dx8_e.116793$CC2.95087@.fe08.news.easynews.com ...
> The backup was take to multiple disks and you have provided only one.
> http://forums.databasejournal.com/hi...p/33896-1.html
> --
> Nik Marshall-Blank MCSD/MCDBA
> "Rowland Costin" <technical@.selven.co.uk> wrote in message
> news:eA8CksEwFHA.3400@.TK2MSFTNGP14.phx.gbl...
>
|||The error message clearly states that you striped the backup to two files and now try to restore
from only one of those files. It is easy to stripe by mistake, so instead of saying the backup is
corrupt, you might want to figure out why and who striped the backup by mistake and make sure it
doesn't happen again. If in doubt, you can examine the backup using
RESTORE HEADERONLY
RESTORE FILELISTONLY
RESTORE VERIFYONLY
RESTORE LABELONLY (this will tell you if the backup is striped)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Rowland Costin" <technical@.selven.co.uk> wrote in message
news:%23$mxRm0wFHA.3152@.TK2MSFTNGP10.phx.gbl...
> Thanks for the reply. The database backup in question was just a couple of megs and was copied to
> CD. So I guess it must have been corrupt in some way, cos it was backed up to file on the hard
> drive first. Still I guessed something like this so fortunately as it was just a transfer of
> database and not a real backup, we just got it backed up again and all was ok. Weird huh.
> Cheers
> Rowland
> "Nik Marshall-Blank (delete fcom for my email address)" <NikMB@.fcomiNodefcom.afcomt> wrote in
> message news:dx8_e.116793$CC2.95087@.fe08.news.easynews.com ...
>
|||Thanks Tibor.
I guess I didn't really understand the first reply. I didn't know you could
strip a backup, but I do now. I just tried it in enterprise manager and I
see what you mean. Its an easy mistake to make, if you add your own file and
the previous file is still there, it backs up to both files. Quite a handy
feature if you want to split over multiple media.
Thanks. I'll update our team member accordingly.
Regards
Rowland
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uKiDOx0wFHA.2620@.TK2MSFTNGP09.phx.gbl...
> The error message clearly states that you striped the backup to two files
> and now try to restore from only one of those files. It is easy to stripe
> by mistake, so instead of saying the backup is corrupt, you might want to
> figure out why and who striped the backup by mistake and make sure it
> doesn't happen again. If in doubt, you can examine the backup using
> RESTORE HEADERONLY
> RESTORE FILELISTONLY
> RESTORE VERIFYONLY
> RESTORE LABELONLY (this will tell you if the backup is striped)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Rowland Costin" <technical@.selven.co.uk> wrote in message
> news:%23$mxRm0wFHA.3152@.TK2MSFTNGP10.phx.gbl...
>
I get the following message
The media set for database 'TeamSpiritDataTDB' has 2 family members but only
1 are provided. All members must be provided.
What does this actually mean. Is the file corrupt, or is there a problem
with the way it was backed up? I didn't back it up, but our normal procedure
in this circumstance is just to make a complete back up to a file.
Any ideas gratefully received.
Thanks
Rowland
The backup was take to multiple disks and you have provided only one.
http://forums.databasejournal.com/hi...p/33896-1.html
Nik Marshall-Blank MCSD/MCDBA
"Rowland Costin" <technical@.selven.co.uk> wrote in message
news:eA8CksEwFHA.3400@.TK2MSFTNGP14.phx.gbl...
> Trying to restore a database from a personal edition SQL 2000 to another
> PC. I get the following message
> The media set for database 'TeamSpiritDataTDB' has 2 family members but
> only 1 are provided. All members must be provided.
> What does this actually mean. Is the file corrupt, or is there a problem
> with the way it was backed up? I didn't back it up, but our normal
> procedure in this circumstance is just to make a complete back up to a
> file.
> Any ideas gratefully received.
> Thanks
> Rowland
>
|||Thanks for the reply. The database backup in question was just a couple of
megs and was copied to CD. So I guess it must have been corrupt in some way,
cos it was backed up to file on the hard drive first. Still I guessed
something like this so fortunately as it was just a transfer of database and
not a real backup, we just got it backed up again and all was ok. Weird huh.
Cheers
Rowland
"Nik Marshall-Blank (delete fcom for my email address)"
<NikMB@.fcomiNodefcom.afcomt> wrote in message
news:dx8_e.116793$CC2.95087@.fe08.news.easynews.com ...
> The backup was take to multiple disks and you have provided only one.
> http://forums.databasejournal.com/hi...p/33896-1.html
> --
> Nik Marshall-Blank MCSD/MCDBA
> "Rowland Costin" <technical@.selven.co.uk> wrote in message
> news:eA8CksEwFHA.3400@.TK2MSFTNGP14.phx.gbl...
>
|||The error message clearly states that you striped the backup to two files and now try to restore
from only one of those files. It is easy to stripe by mistake, so instead of saying the backup is
corrupt, you might want to figure out why and who striped the backup by mistake and make sure it
doesn't happen again. If in doubt, you can examine the backup using
RESTORE HEADERONLY
RESTORE FILELISTONLY
RESTORE VERIFYONLY
RESTORE LABELONLY (this will tell you if the backup is striped)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Rowland Costin" <technical@.selven.co.uk> wrote in message
news:%23$mxRm0wFHA.3152@.TK2MSFTNGP10.phx.gbl...
> Thanks for the reply. The database backup in question was just a couple of megs and was copied to
> CD. So I guess it must have been corrupt in some way, cos it was backed up to file on the hard
> drive first. Still I guessed something like this so fortunately as it was just a transfer of
> database and not a real backup, we just got it backed up again and all was ok. Weird huh.
> Cheers
> Rowland
> "Nik Marshall-Blank (delete fcom for my email address)" <NikMB@.fcomiNodefcom.afcomt> wrote in
> message news:dx8_e.116793$CC2.95087@.fe08.news.easynews.com ...
>
|||Thanks Tibor.
I guess I didn't really understand the first reply. I didn't know you could
strip a backup, but I do now. I just tried it in enterprise manager and I
see what you mean. Its an easy mistake to make, if you add your own file and
the previous file is still there, it backs up to both files. Quite a handy
feature if you want to split over multiple media.
Thanks. I'll update our team member accordingly.
Regards
Rowland
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uKiDOx0wFHA.2620@.TK2MSFTNGP09.phx.gbl...
> The error message clearly states that you striped the backup to two files
> and now try to restore from only one of those files. It is easy to stripe
> by mistake, so instead of saying the backup is corrupt, you might want to
> figure out why and who striped the backup by mistake and make sure it
> doesn't happen again. If in doubt, you can examine the backup using
> RESTORE HEADERONLY
> RESTORE FILELISTONLY
> RESTORE VERIFYONLY
> RESTORE LABELONLY (this will tell you if the backup is striped)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Rowland Costin" <technical@.selven.co.uk> wrote in message
> news:%23$mxRm0wFHA.3152@.TK2MSFTNGP10.phx.gbl...
>
Error 3123 in SQL Restore
Trying to restore a database from a personal edition SQL 2000 to another PC.
I get the following message
The media set for database 'TeamSpiritDataTDB' has 2 family members but only
1 are provided. All members must be provided.
What does this actually mean. Is the file corrupt, or is there a problem
with the way it was backed up? I didn't back it up, but our normal procedure
in this circumstance is just to make a complete back up to a file.
Any ideas gratefully received.
Thanks
RowlandThe backup was take to multiple disks and you have provided only one.
http://forums.databasejournal.com/h...hp/33896-1.html
Nik Marshall-Blank MCSD/MCDBA
"Rowland Costin" <technical@.selven.co.uk> wrote in message
news:eA8CksEwFHA.3400@.TK2MSFTNGP14.phx.gbl...
> Trying to restore a database from a personal edition SQL 2000 to another
> PC. I get the following message
> The media set for database 'TeamSpiritDataTDB' has 2 family members but
> only 1 are provided. All members must be provided.
> What does this actually mean. Is the file corrupt, or is there a problem
> with the way it was backed up? I didn't back it up, but our normal
> procedure in this circumstance is just to make a complete back up to a
> file.
> Any ideas gratefully received.
> Thanks
> Rowland
>|||Thanks for the reply. The database backup in question was just a couple of
megs and was copied to CD. So I guess it must have been corrupt in some way,
cos it was backed up to file on the hard drive first. Still I guessed
something like this so fortunately as it was just a transfer of database and
not a real backup, we just got it backed up again and all was ok. Weird huh.
Cheers
Rowland
"Nik Marshall-Blank (delete fcom for my email address)"
<NikMB@.fcomiNodefcom.afcomt> wrote in message
news:dx8_e.116793$CC2.95087@.fe08.news.easynews.com...
> The backup was take to multiple disks and you have provided only one.
> http://forums.databasejournal.com/h...hp/33896-1.html
> --
> Nik Marshall-Blank MCSD/MCDBA
> "Rowland Costin" <technical@.selven.co.uk> wrote in message
> news:eA8CksEwFHA.3400@.TK2MSFTNGP14.phx.gbl...
>|||The error message clearly states that you striped the backup to two files an
d now try to restore
from only one of those files. It is easy to stripe by mistake, so instead of
saying the backup is
corrupt, you might want to figure out why and who striped the backup by mist
ake and make sure it
doesn't happen again. If in doubt, you can examine the backup using
RESTORE HEADERONLY
RESTORE FILELISTONLY
RESTORE VERIFYONLY
RESTORE LABELONLY (this will tell you if the backup is striped)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Rowland Costin" <technical@.selven.co.uk> wrote in message
news:%23$mxRm0wFHA.3152@.TK2MSFTNGP10.phx.gbl...
> Thanks for the reply. The database backup in question was just a couple o
f megs and was copied to
> CD. So I guess it must have been corrupt in some way, cos it was backed up
to file on the hard
> drive first. Still I guessed something like this so fortunately as it was
just a transfer of
> database and not a real backup, we just got it backed up again and all was
ok. Weird huh.
> Cheers
> Rowland
> "Nik Marshall-Blank (delete fcom for my email address)" <NikMB@.fcomiNodefc
om.afcomt> wrote in
> message news:dx8_e.116793$CC2.95087@.fe08.news.easynews.com...
>|||Thanks Tibor.
I guess I didn't really understand the first reply. I didn't know you could
strip a backup, but I do now. I just tried it in enterprise manager and I
see what you mean. Its an easy mistake to make, if you add your own file and
the previous file is still there, it backs up to both files. Quite a handy
feature if you want to split over multiple media.
Thanks. I'll update our team member accordingly.
Regards
Rowland
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uKiDOx0wFHA.2620@.TK2MSFTNGP09.phx.gbl...
> The error message clearly states that you striped the backup to two files
> and now try to restore from only one of those files. It is easy to stripe
> by mistake, so instead of saying the backup is corrupt, you might want to
> figure out why and who striped the backup by mistake and make sure it
> doesn't happen again. If in doubt, you can examine the backup using
> RESTORE HEADERONLY
> RESTORE FILELISTONLY
> RESTORE VERIFYONLY
> RESTORE LABELONLY (this will tell you if the backup is striped)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Rowland Costin" <technical@.selven.co.uk> wrote in message
> news:%23$mxRm0wFHA.3152@.TK2MSFTNGP10.phx.gbl...
>
I get the following message
The media set for database 'TeamSpiritDataTDB' has 2 family members but only
1 are provided. All members must be provided.
What does this actually mean. Is the file corrupt, or is there a problem
with the way it was backed up? I didn't back it up, but our normal procedure
in this circumstance is just to make a complete back up to a file.
Any ideas gratefully received.
Thanks
RowlandThe backup was take to multiple disks and you have provided only one.
http://forums.databasejournal.com/h...hp/33896-1.html
Nik Marshall-Blank MCSD/MCDBA
"Rowland Costin" <technical@.selven.co.uk> wrote in message
news:eA8CksEwFHA.3400@.TK2MSFTNGP14.phx.gbl...
> Trying to restore a database from a personal edition SQL 2000 to another
> PC. I get the following message
> The media set for database 'TeamSpiritDataTDB' has 2 family members but
> only 1 are provided. All members must be provided.
> What does this actually mean. Is the file corrupt, or is there a problem
> with the way it was backed up? I didn't back it up, but our normal
> procedure in this circumstance is just to make a complete back up to a
> file.
> Any ideas gratefully received.
> Thanks
> Rowland
>|||Thanks for the reply. The database backup in question was just a couple of
megs and was copied to CD. So I guess it must have been corrupt in some way,
cos it was backed up to file on the hard drive first. Still I guessed
something like this so fortunately as it was just a transfer of database and
not a real backup, we just got it backed up again and all was ok. Weird huh.
Cheers
Rowland
"Nik Marshall-Blank (delete fcom for my email address)"
<NikMB@.fcomiNodefcom.afcomt> wrote in message
news:dx8_e.116793$CC2.95087@.fe08.news.easynews.com...
> The backup was take to multiple disks and you have provided only one.
> http://forums.databasejournal.com/h...hp/33896-1.html
> --
> Nik Marshall-Blank MCSD/MCDBA
> "Rowland Costin" <technical@.selven.co.uk> wrote in message
> news:eA8CksEwFHA.3400@.TK2MSFTNGP14.phx.gbl...
>|||The error message clearly states that you striped the backup to two files an
d now try to restore
from only one of those files. It is easy to stripe by mistake, so instead of
saying the backup is
corrupt, you might want to figure out why and who striped the backup by mist
ake and make sure it
doesn't happen again. If in doubt, you can examine the backup using
RESTORE HEADERONLY
RESTORE FILELISTONLY
RESTORE VERIFYONLY
RESTORE LABELONLY (this will tell you if the backup is striped)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Rowland Costin" <technical@.selven.co.uk> wrote in message
news:%23$mxRm0wFHA.3152@.TK2MSFTNGP10.phx.gbl...
> Thanks for the reply. The database backup in question was just a couple o
f megs and was copied to
> CD. So I guess it must have been corrupt in some way, cos it was backed up
to file on the hard
> drive first. Still I guessed something like this so fortunately as it was
just a transfer of
> database and not a real backup, we just got it backed up again and all was
ok. Weird huh.
> Cheers
> Rowland
> "Nik Marshall-Blank (delete fcom for my email address)" <NikMB@.fcomiNodefc
om.afcomt> wrote in
> message news:dx8_e.116793$CC2.95087@.fe08.news.easynews.com...
>|||Thanks Tibor.
I guess I didn't really understand the first reply. I didn't know you could
strip a backup, but I do now. I just tried it in enterprise manager and I
see what you mean. Its an easy mistake to make, if you add your own file and
the previous file is still there, it backs up to both files. Quite a handy
feature if you want to split over multiple media.
Thanks. I'll update our team member accordingly.
Regards
Rowland
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uKiDOx0wFHA.2620@.TK2MSFTNGP09.phx.gbl...
> The error message clearly states that you striped the backup to two files
> and now try to restore from only one of those files. It is easy to stripe
> by mistake, so instead of saying the backup is corrupt, you might want to
> figure out why and who striped the backup by mistake and make sure it
> doesn't happen again. If in doubt, you can examine the backup using
> RESTORE HEADERONLY
> RESTORE FILELISTONLY
> RESTORE VERIFYONLY
> RESTORE LABELONLY (this will tell you if the backup is striped)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Rowland Costin" <technical@.selven.co.uk> wrote in message
> news:%23$mxRm0wFHA.3152@.TK2MSFTNGP10.phx.gbl...
>
Error 3123 in SQL Restore
Trying to restore a database from a personal edition SQL 2000 to another PC.
I get the following message
The media set for database 'TeamSpiritDataTDB' has 2 family members but only
1 are provided. All members must be provided.
What does this actually mean. Is the file corrupt, or is there a problem
with the way it was backed up? I didn't back it up, but our normal procedure
in this circumstance is just to make a complete back up to a file.
Any ideas gratefully received.
Thanks
RowlandThe backup was take to multiple disks and you have provided only one.
http://forums.databasejournal.com/history/topic.php/33896-1.html
--
Nik Marshall-Blank MCSD/MCDBA
"Rowland Costin" <technical@.selven.co.uk> wrote in message
news:eA8CksEwFHA.3400@.TK2MSFTNGP14.phx.gbl...
> Trying to restore a database from a personal edition SQL 2000 to another
> PC. I get the following message
> The media set for database 'TeamSpiritDataTDB' has 2 family members but
> only 1 are provided. All members must be provided.
> What does this actually mean. Is the file corrupt, or is there a problem
> with the way it was backed up? I didn't back it up, but our normal
> procedure in this circumstance is just to make a complete back up to a
> file.
> Any ideas gratefully received.
> Thanks
> Rowland
>|||Thanks for the reply. The database backup in question was just a couple of
megs and was copied to CD. So I guess it must have been corrupt in some way,
cos it was backed up to file on the hard drive first. Still I guessed
something like this so fortunately as it was just a transfer of database and
not a real backup, we just got it backed up again and all was ok. Weird huh.
Cheers
Rowland
"Nik Marshall-Blank (delete fcom for my email address)"
<NikMB@.fcomiNodefcom.afcomt> wrote in message
news:dx8_e.116793$CC2.95087@.fe08.news.easynews.com...
> The backup was take to multiple disks and you have provided only one.
> http://forums.databasejournal.com/history/topic.php/33896-1.html
> --
> Nik Marshall-Blank MCSD/MCDBA
> "Rowland Costin" <technical@.selven.co.uk> wrote in message
> news:eA8CksEwFHA.3400@.TK2MSFTNGP14.phx.gbl...
>> Trying to restore a database from a personal edition SQL 2000 to another
>> PC. I get the following message
>> The media set for database 'TeamSpiritDataTDB' has 2 family members but
>> only 1 are provided. All members must be provided.
>> What does this actually mean. Is the file corrupt, or is there a problem
>> with the way it was backed up? I didn't back it up, but our normal
>> procedure in this circumstance is just to make a complete back up to a
>> file.
>> Any ideas gratefully received.
>> Thanks
>> Rowland
>|||The error message clearly states that you striped the backup to two files and now try to restore
from only one of those files. It is easy to stripe by mistake, so instead of saying the backup is
corrupt, you might want to figure out why and who striped the backup by mistake and make sure it
doesn't happen again. If in doubt, you can examine the backup using
RESTORE HEADERONLY
RESTORE FILELISTONLY
RESTORE VERIFYONLY
RESTORE LABELONLY (this will tell you if the backup is striped)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Rowland Costin" <technical@.selven.co.uk> wrote in message
news:%23$mxRm0wFHA.3152@.TK2MSFTNGP10.phx.gbl...
> Thanks for the reply. The database backup in question was just a couple of megs and was copied to
> CD. So I guess it must have been corrupt in some way, cos it was backed up to file on the hard
> drive first. Still I guessed something like this so fortunately as it was just a transfer of
> database and not a real backup, we just got it backed up again and all was ok. Weird huh.
> Cheers
> Rowland
> "Nik Marshall-Blank (delete fcom for my email address)" <NikMB@.fcomiNodefcom.afcomt> wrote in
> message news:dx8_e.116793$CC2.95087@.fe08.news.easynews.com...
>> The backup was take to multiple disks and you have provided only one.
>> http://forums.databasejournal.com/history/topic.php/33896-1.html
>> --
>> Nik Marshall-Blank MCSD/MCDBA
>> "Rowland Costin" <technical@.selven.co.uk> wrote in message
>> news:eA8CksEwFHA.3400@.TK2MSFTNGP14.phx.gbl...
>> Trying to restore a database from a personal edition SQL 2000 to another PC. I get the following
>> message
>> The media set for database 'TeamSpiritDataTDB' has 2 family members but only 1 are provided.
>> All members must be provided.
>> What does this actually mean. Is the file corrupt, or is there a problem with the way it was
>> backed up? I didn't back it up, but our normal procedure in this circumstance is just to make a
>> complete back up to a file.
>> Any ideas gratefully received.
>> Thanks
>> Rowland
>>
>|||Thanks Tibor.
I guess I didn't really understand the first reply. I didn't know you could
strip a backup, but I do now. I just tried it in enterprise manager and I
see what you mean. Its an easy mistake to make, if you add your own file and
the previous file is still there, it backs up to both files. Quite a handy
feature if you want to split over multiple media.
Thanks. I'll update our team member accordingly.
Regards
Rowland
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uKiDOx0wFHA.2620@.TK2MSFTNGP09.phx.gbl...
> The error message clearly states that you striped the backup to two files
> and now try to restore from only one of those files. It is easy to stripe
> by mistake, so instead of saying the backup is corrupt, you might want to
> figure out why and who striped the backup by mistake and make sure it
> doesn't happen again. If in doubt, you can examine the backup using
> RESTORE HEADERONLY
> RESTORE FILELISTONLY
> RESTORE VERIFYONLY
> RESTORE LABELONLY (this will tell you if the backup is striped)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Rowland Costin" <technical@.selven.co.uk> wrote in message
> news:%23$mxRm0wFHA.3152@.TK2MSFTNGP10.phx.gbl...
>> Thanks for the reply. The database backup in question was just a couple
>> of megs and was copied to CD. So I guess it must have been corrupt in
>> some way, cos it was backed up to file on the hard drive first. Still I
>> guessed something like this so fortunately as it was just a transfer of
>> database and not a real backup, we just got it backed up again and all
>> was ok. Weird huh.
>> Cheers
>> Rowland
>> "Nik Marshall-Blank (delete fcom for my email address)"
>> <NikMB@.fcomiNodefcom.afcomt> wrote in message
>> news:dx8_e.116793$CC2.95087@.fe08.news.easynews.com...
>> The backup was take to multiple disks and you have provided only one.
>> http://forums.databasejournal.com/history/topic.php/33896-1.html
>> --
>> Nik Marshall-Blank MCSD/MCDBA
>> "Rowland Costin" <technical@.selven.co.uk> wrote in message
>> news:eA8CksEwFHA.3400@.TK2MSFTNGP14.phx.gbl...
>> Trying to restore a database from a personal edition SQL 2000 to
>> another PC. I get the following message
>> The media set for database 'TeamSpiritDataTDB' has 2 family members but
>> only 1 are provided. All members must be provided.
>> What does this actually mean. Is the file corrupt, or is there a
>> problem with the way it was backed up? I didn't back it up, but our
>> normal procedure in this circumstance is just to make a complete back
>> up to a file.
>> Any ideas gratefully received.
>> Thanks
>> Rowland
>>
>>
>
I get the following message
The media set for database 'TeamSpiritDataTDB' has 2 family members but only
1 are provided. All members must be provided.
What does this actually mean. Is the file corrupt, or is there a problem
with the way it was backed up? I didn't back it up, but our normal procedure
in this circumstance is just to make a complete back up to a file.
Any ideas gratefully received.
Thanks
RowlandThe backup was take to multiple disks and you have provided only one.
http://forums.databasejournal.com/history/topic.php/33896-1.html
--
Nik Marshall-Blank MCSD/MCDBA
"Rowland Costin" <technical@.selven.co.uk> wrote in message
news:eA8CksEwFHA.3400@.TK2MSFTNGP14.phx.gbl...
> Trying to restore a database from a personal edition SQL 2000 to another
> PC. I get the following message
> The media set for database 'TeamSpiritDataTDB' has 2 family members but
> only 1 are provided. All members must be provided.
> What does this actually mean. Is the file corrupt, or is there a problem
> with the way it was backed up? I didn't back it up, but our normal
> procedure in this circumstance is just to make a complete back up to a
> file.
> Any ideas gratefully received.
> Thanks
> Rowland
>|||Thanks for the reply. The database backup in question was just a couple of
megs and was copied to CD. So I guess it must have been corrupt in some way,
cos it was backed up to file on the hard drive first. Still I guessed
something like this so fortunately as it was just a transfer of database and
not a real backup, we just got it backed up again and all was ok. Weird huh.
Cheers
Rowland
"Nik Marshall-Blank (delete fcom for my email address)"
<NikMB@.fcomiNodefcom.afcomt> wrote in message
news:dx8_e.116793$CC2.95087@.fe08.news.easynews.com...
> The backup was take to multiple disks and you have provided only one.
> http://forums.databasejournal.com/history/topic.php/33896-1.html
> --
> Nik Marshall-Blank MCSD/MCDBA
> "Rowland Costin" <technical@.selven.co.uk> wrote in message
> news:eA8CksEwFHA.3400@.TK2MSFTNGP14.phx.gbl...
>> Trying to restore a database from a personal edition SQL 2000 to another
>> PC. I get the following message
>> The media set for database 'TeamSpiritDataTDB' has 2 family members but
>> only 1 are provided. All members must be provided.
>> What does this actually mean. Is the file corrupt, or is there a problem
>> with the way it was backed up? I didn't back it up, but our normal
>> procedure in this circumstance is just to make a complete back up to a
>> file.
>> Any ideas gratefully received.
>> Thanks
>> Rowland
>|||The error message clearly states that you striped the backup to two files and now try to restore
from only one of those files. It is easy to stripe by mistake, so instead of saying the backup is
corrupt, you might want to figure out why and who striped the backup by mistake and make sure it
doesn't happen again. If in doubt, you can examine the backup using
RESTORE HEADERONLY
RESTORE FILELISTONLY
RESTORE VERIFYONLY
RESTORE LABELONLY (this will tell you if the backup is striped)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Rowland Costin" <technical@.selven.co.uk> wrote in message
news:%23$mxRm0wFHA.3152@.TK2MSFTNGP10.phx.gbl...
> Thanks for the reply. The database backup in question was just a couple of megs and was copied to
> CD. So I guess it must have been corrupt in some way, cos it was backed up to file on the hard
> drive first. Still I guessed something like this so fortunately as it was just a transfer of
> database and not a real backup, we just got it backed up again and all was ok. Weird huh.
> Cheers
> Rowland
> "Nik Marshall-Blank (delete fcom for my email address)" <NikMB@.fcomiNodefcom.afcomt> wrote in
> message news:dx8_e.116793$CC2.95087@.fe08.news.easynews.com...
>> The backup was take to multiple disks and you have provided only one.
>> http://forums.databasejournal.com/history/topic.php/33896-1.html
>> --
>> Nik Marshall-Blank MCSD/MCDBA
>> "Rowland Costin" <technical@.selven.co.uk> wrote in message
>> news:eA8CksEwFHA.3400@.TK2MSFTNGP14.phx.gbl...
>> Trying to restore a database from a personal edition SQL 2000 to another PC. I get the following
>> message
>> The media set for database 'TeamSpiritDataTDB' has 2 family members but only 1 are provided.
>> All members must be provided.
>> What does this actually mean. Is the file corrupt, or is there a problem with the way it was
>> backed up? I didn't back it up, but our normal procedure in this circumstance is just to make a
>> complete back up to a file.
>> Any ideas gratefully received.
>> Thanks
>> Rowland
>>
>|||Thanks Tibor.
I guess I didn't really understand the first reply. I didn't know you could
strip a backup, but I do now. I just tried it in enterprise manager and I
see what you mean. Its an easy mistake to make, if you add your own file and
the previous file is still there, it backs up to both files. Quite a handy
feature if you want to split over multiple media.
Thanks. I'll update our team member accordingly.
Regards
Rowland
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uKiDOx0wFHA.2620@.TK2MSFTNGP09.phx.gbl...
> The error message clearly states that you striped the backup to two files
> and now try to restore from only one of those files. It is easy to stripe
> by mistake, so instead of saying the backup is corrupt, you might want to
> figure out why and who striped the backup by mistake and make sure it
> doesn't happen again. If in doubt, you can examine the backup using
> RESTORE HEADERONLY
> RESTORE FILELISTONLY
> RESTORE VERIFYONLY
> RESTORE LABELONLY (this will tell you if the backup is striped)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Rowland Costin" <technical@.selven.co.uk> wrote in message
> news:%23$mxRm0wFHA.3152@.TK2MSFTNGP10.phx.gbl...
>> Thanks for the reply. The database backup in question was just a couple
>> of megs and was copied to CD. So I guess it must have been corrupt in
>> some way, cos it was backed up to file on the hard drive first. Still I
>> guessed something like this so fortunately as it was just a transfer of
>> database and not a real backup, we just got it backed up again and all
>> was ok. Weird huh.
>> Cheers
>> Rowland
>> "Nik Marshall-Blank (delete fcom for my email address)"
>> <NikMB@.fcomiNodefcom.afcomt> wrote in message
>> news:dx8_e.116793$CC2.95087@.fe08.news.easynews.com...
>> The backup was take to multiple disks and you have provided only one.
>> http://forums.databasejournal.com/history/topic.php/33896-1.html
>> --
>> Nik Marshall-Blank MCSD/MCDBA
>> "Rowland Costin" <technical@.selven.co.uk> wrote in message
>> news:eA8CksEwFHA.3400@.TK2MSFTNGP14.phx.gbl...
>> Trying to restore a database from a personal edition SQL 2000 to
>> another PC. I get the following message
>> The media set for database 'TeamSpiritDataTDB' has 2 family members but
>> only 1 are provided. All members must be provided.
>> What does this actually mean. Is the file corrupt, or is there a
>> problem with the way it was backed up? I didn't back it up, but our
>> normal procedure in this circumstance is just to make a complete back
>> up to a file.
>> Any ideas gratefully received.
>> Thanks
>> Rowland
>>
>>
>
Subscribe to:
Posts (Atom)