Tuesday, March 27, 2012
Error 8909 in job...is it?
Enterprise Edition on Windows NT 5.2 (Build 3790: )
I received the following error the last two nights in a row while running
the gui created maintanence job. I just ran DBCC CHECKDB WITH NO_INFOMSGS
and DBCC CHECKTABLE ('TblPhoneNote') on the tables listed in QA and returned
no errors. I am alarmed but why the errors one way and not the other. Is
there some switches that I enable prior to running in QA to get more info?
[5] Database XXDB: Check Data and Index Linkage...
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8909: [Microsoft][ODBC SQL
Server Driver][SQL Server]Table error: Object ID 10944512, index ID 0, page
ID (1:948331). The PageId in the page header = (55:939524096).
The following errors were found:
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
10944512, index ID 0, page ID (1:948331). The PageId in the page header =
(55:939524096).
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
2005582183, index ID 7, page (1:948329). Test (sorted [i].offset >=
PAGEHEADSIZE) failed. Slot 427, offset 0x2 is invalid.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
2005582183, index ID 7, page (1:948329). Test (sorted[i].offset >= max)
failed. Slot 0, offset 0x1ab overlaps with the prior row.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
ID 7: Page (1:948330) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
ID 7: Page (1:948331) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
ID 7: Page (1:948332) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
ID 7: Page (1:948333) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
ID 7: Page (1:948334) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
ID 7: Page (1:948335) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
ID 7: Page (1:948336) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
ID 7: Page (1:948337) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
2031398356, index ID 14, page (1:948330). Test (sorted [i].offset >=
PAGEHEADSIZE) failed. Slot 233, offset 0x2e is invalid.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
2031398356, index ID 14, page (1:948330). Test (sorted[i].offset >= max)
failed. Slot 0, offset 0xe9 overlaps with the prior row.
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
errors and 11 consistency errors in table 'TblLab' (object ID 2005582183).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
errors and 2 consistency errors in table 'TblPhoneNote' (object ID
2031398356).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
errors and 20 consistency errors in database 'XXDB'.
[Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is the
minimum repair level for the errors found by DBCC CHECKDB (XXDB ).
** Execution Time: 0 hrs, 33 mins, 26 secs **
TIA
CD
Time to open a call to Microsoft PSS.. It costs $249 I think... If the data
is important, don't risk it..
Also, do not overwrite any backups until you get this resolved..
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"CD" <mcdye1@.hotmail.nospam.com> wrote in message
news:OfSshe1uEHA.3872@.TK2MSFTNGP11.phx.gbl...
> Microsoft SQL Server 2000 - 8.00.923 (Intel X86)
> Enterprise Edition on Windows NT 5.2 (Build 3790: )
> I received the following error the last two nights in a row while running
> the gui created maintanence job. I just ran DBCC CHECKDB WITH NO_INFOMSGS
> and DBCC CHECKTABLE ('TblPhoneNote') on the tables listed in QA and
returned
> no errors. I am alarmed but why the errors one way and not the other. Is
> there some switches that I enable prior to running in QA to get more info?
> [5] Database XXDB: Check Data and Index Linkage...
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8909: [Microsoft][ODBC
SQL
> Server Driver][SQL Server]Table error: Object ID 10944512, index ID 0,
page
> ID (1:948331). The PageId in the page header = (55:939524096).
> The following errors were found:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
> 10944512, index ID 0, page ID (1:948331). The PageId in the page header =
> (55:939524096).
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
> 2005582183, index ID 7, page (1:948329). Test (sorted [i].offset >=
> PAGEHEADSIZE) failed. Slot 427, offset 0x2 is invalid.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
> 2005582183, index ID 7, page (1:948329). Test (sorted[i].offset >= max)
> failed. Slot 0, offset 0x1ab overlaps with the prior row.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948330) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948331) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948332) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948333) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948334) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948335) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948336) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948337) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
> 2031398356, index ID 14, page (1:948330). Test (sorted [i].offset >=
> PAGEHEADSIZE) failed. Slot 233, offset 0x2e is invalid.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
> 2031398356, index ID 14, page (1:948330). Test (sorted[i].offset >= max)
> failed. Slot 0, offset 0xe9 overlaps with the prior row.
> [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
> errors and 11 consistency errors in table 'TblLab' (object ID 2005582183).
> [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
> errors and 2 consistency errors in table 'TblPhoneNote' (object ID
> 2031398356).
> [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
> errors and 20 consistency errors in database 'XXDB'.
> [Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is
the
> minimum repair level for the errors found by DBCC CHECKDB (XXDB ).
> ** Execution Time: 0 hrs, 33 mins, 26 secs **
> TIA
> CD
>
|||It is possible for hardware problems to show up as 'transient' corruption issues in DBCC. Issues like caching controllers can cause the buffer pool to read stale data and feed that stale data to DBCC, which detects a corruption. If the page is flushed back out of the cache and then read back in later on, there could be no problem with the read (and thus no corruption as far as DBCC is concerned).
As Wayne correctly suggests, CSS is probabaly your best alternative at this point, but they are probably going to request that you do some hardware diagnostics too. You might be preemptive and have them ready.
Thanks,
Ryan Stonecipher
SQL Server Storage Engine, DBCC
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message news:ehsYVw1uEHA.4028@.TK2MSFTNGP15.phx.gbl...
Time to open a call to Microsoft PSS.. It costs $249 I think... If the data
is important, don't risk it..
Also, do not overwrite any backups until you get this resolved..
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"CD" <mcdye1@.hotmail.nospam.com> wrote in message
news:OfSshe1uEHA.3872@.TK2MSFTNGP11.phx.gbl...
> Microsoft SQL Server 2000 - 8.00.923 (Intel X86)
> Enterprise Edition on Windows NT 5.2 (Build 3790: )
> I received the following error the last two nights in a row while running
> the gui created maintanence job. I just ran DBCC CHECKDB WITH NO_INFOMSGS
> and DBCC CHECKTABLE ('TblPhoneNote') on the tables listed in QA and
returned
> no errors. I am alarmed but why the errors one way and not the other. Is
> there some switches that I enable prior to running in QA to get more info?
> [5] Database XXDB: Check Data and Index Linkage...
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8909: [Microsoft][ODBC
SQL
> Server Driver][SQL Server]Table error: Object ID 10944512, index ID 0,
page
> ID (1:948331). The PageId in the page header = (55:939524096).
> The following errors were found:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
> 10944512, index ID 0, page ID (1:948331). The PageId in the page header =
> (55:939524096).
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
> 2005582183, index ID 7, page (1:948329). Test (sorted [i].offset >=
> PAGEHEADSIZE) failed. Slot 427, offset 0x2 is invalid.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
> 2005582183, index ID 7, page (1:948329). Test (sorted[i].offset >= max)
> failed. Slot 0, offset 0x1ab overlaps with the prior row.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948330) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948331) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948332) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948333) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948334) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948335) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948336) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948337) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
> 2031398356, index ID 14, page (1:948330). Test (sorted [i].offset >=
> PAGEHEADSIZE) failed. Slot 233, offset 0x2e is invalid.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
> 2031398356, index ID 14, page (1:948330). Test (sorted[i].offset >= max)
> failed. Slot 0, offset 0xe9 overlaps with the prior row.
> [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
> errors and 11 consistency errors in table 'TblLab' (object ID 2005582183).
> [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
> errors and 2 consistency errors in table 'TblPhoneNote' (object ID
> 2031398356).
> [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
> errors and 20 consistency errors in database 'XXDB'.
> [Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is
the
> minimum repair level for the errors found by DBCC CHECKDB (XXDB ).
> ** Execution Time: 0 hrs, 33 mins, 26 secs **
> TIA
> CD
>
Error 8909 in job...is it?
Enterprise Edition on Windows NT 5.2 (Build 3790: )
I received the following error the last two nights in a row while running
the gui created maintanence job. I just ran DBCC CHECKDB WITH NO_INFOMSGS
and DBCC CHECKTABLE ('TblPhoneNote') on the tables listed in QA and returned
no errors. I am alarmed but why the errors one way and not the other. Is
there some switches that I enable prior to running in QA to get more info?
[5] Database XXDB: Check Data and Index Linkage...
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8909: [Microsoft][ODBC SQL
Server Driver][SQL Server]Table error: Object ID 10944512, index ID 0, page
ID (1:948331). The PageId in the page header = (55:939524096).
The following errors were found:
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
10944512, index ID 0, page ID (1:948331). The PageId in the page header = (55:939524096).
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
2005582183, index ID 7, page (1:948329). Test (sorted [i].offset >= PAGEHEADSIZE) failed. Slot 427, offset 0x2 is invalid.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
2005582183, index ID 7, page (1:948329). Test (sorted[i].offset >= max)
failed. Slot 0, offset 0x1ab overlaps with the prior row.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
ID 7: Page (1:948330) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
ID 7: Page (1:948331) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
ID 7: Page (1:948332) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
ID 7: Page (1:948333) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
ID 7: Page (1:948334) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
ID 7: Page (1:948335) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
ID 7: Page (1:948336) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
ID 7: Page (1:948337) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
2031398356, index ID 14, page (1:948330). Test (sorted [i].offset >= PAGEHEADSIZE) failed. Slot 233, offset 0x2e is invalid.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
2031398356, index ID 14, page (1:948330). Test (sorted[i].offset >= max)
failed. Slot 0, offset 0xe9 overlaps with the prior row.
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
errors and 11 consistency errors in table 'TblLab' (object ID 2005582183).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
errors and 2 consistency errors in table 'TblPhoneNote' (object ID
2031398356).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
errors and 20 consistency errors in database 'XXDB'.
[Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is the
minimum repair level for the errors found by DBCC CHECKDB (XXDB ).
** Execution Time: 0 hrs, 33 mins, 26 secs **
TIA
CDTime to open a call to Microsoft PSS.. It costs $249 I think... If the data
is important, don't risk it..
Also, do not overwrite any backups until you get this resolved..
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"CD" <mcdye1@.hotmail.nospam.com> wrote in message
news:OfSshe1uEHA.3872@.TK2MSFTNGP11.phx.gbl...
> Microsoft SQL Server 2000 - 8.00.923 (Intel X86)
> Enterprise Edition on Windows NT 5.2 (Build 3790: )
> I received the following error the last two nights in a row while running
> the gui created maintanence job. I just ran DBCC CHECKDB WITH NO_INFOMSGS
> and DBCC CHECKTABLE ('TblPhoneNote') on the tables listed in QA and
returned
> no errors. I am alarmed but why the errors one way and not the other. Is
> there some switches that I enable prior to running in QA to get more info?
> [5] Database XXDB: Check Data and Index Linkage...
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8909: [Microsoft][ODBC
SQL
> Server Driver][SQL Server]Table error: Object ID 10944512, index ID 0,
page
> ID (1:948331). The PageId in the page header = (55:939524096).
> The following errors were found:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
> 10944512, index ID 0, page ID (1:948331). The PageId in the page header => (55:939524096).
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
> 2005582183, index ID 7, page (1:948329). Test (sorted [i].offset >=> PAGEHEADSIZE) failed. Slot 427, offset 0x2 is invalid.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
> 2005582183, index ID 7, page (1:948329). Test (sorted[i].offset >= max)
> failed. Slot 0, offset 0x1ab overlaps with the prior row.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948330) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948331) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948332) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948333) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948334) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948335) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948336) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948337) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
> 2031398356, index ID 14, page (1:948330). Test (sorted [i].offset >=> PAGEHEADSIZE) failed. Slot 233, offset 0x2e is invalid.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
> 2031398356, index ID 14, page (1:948330). Test (sorted[i].offset >= max)
> failed. Slot 0, offset 0xe9 overlaps with the prior row.
> [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
> errors and 11 consistency errors in table 'TblLab' (object ID 2005582183).
> [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
> errors and 2 consistency errors in table 'TblPhoneNote' (object ID
> 2031398356).
> [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
> errors and 20 consistency errors in database 'XXDB'.
> [Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is
the
> minimum repair level for the errors found by DBCC CHECKDB (XXDB ).
> ** Execution Time: 0 hrs, 33 mins, 26 secs **
> TIA
> CD
>|||This is a multi-part message in MIME format.
--=_NextPart_000_0043_01C4BB41.E7258280
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
It is possible for hardware problems to show up as 'transient' =corruption issues in DBCC. Issues like caching controllers can cause =the buffer pool to read stale data and feed that stale data to DBCC, =which detects a corruption. If the page is flushed back out of the =cache and then read back in later on, there could be no problem with the =read (and thus no corruption as far as DBCC is concerned).
As Wayne correctly suggests, CSS is probabaly your best alternative at =this point, but they are probably going to request that you do some =hardware diagnostics too. You might be preemptive and have them ready.
Thanks,
Ryan Stonecipher
SQL Server Storage Engine, DBCC
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message =news:ehsYVw1uEHA.4028@.TK2MSFTNGP15.phx.gbl...
Time to open a call to Microsoft PSS.. It costs $249 I think... If the =data
is important, don't risk it..
Also, do not overwrite any backups until you get this resolved..
-- Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"CD" <mcdye1@.hotmail.nospam.com> wrote in message
news:OfSshe1uEHA.3872@.TK2MSFTNGP11.phx.gbl...
> Microsoft SQL Server 2000 - 8.00.923 (Intel X86)
> Enterprise Edition on Windows NT 5.2 (Build 3790: )
>
> I received the following error the last two nights in a row while =running
> the gui created maintanence job. I just ran DBCC CHECKDB WITH =NO_INFOMSGS
> and DBCC CHECKTABLE ('TblPhoneNote') on the tables listed in QA and
returned
> no errors. I am alarmed but why the errors one way and not the =other. Is
> there some switches that I enable prior to running in QA to get more =info?
>
> [5] Database XXDB: Check Data and Index Linkage...
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8909: =[Microsoft][ODBC
SQL
> Server Driver][SQL Server]Table error: Object ID 10944512, index ID =0,
page
> ID (1:948331). The PageId in the page header =3D (55:939524096).
>
> The following errors were found:
>
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object =ID
> 10944512, index ID 0, page ID (1:948331). The PageId in the page =header =3D
> (55:939524096).
>
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object =ID
> 2005582183, index ID 7, page (1:948329). Test (sorted [i].offset =>=3D
> PAGEHEADSIZE) failed. Slot 427, offset 0x2 is invalid.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object =ID
> 2005582183, index ID 7, page (1:948329). Test (sorted[i].offset >=3D =max)
> failed. Slot 0, offset 0x1ab overlaps with the prior row.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, =index
> ID 7: Page (1:948330) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, =index
> ID 7: Page (1:948331) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, =index
> ID 7: Page (1:948332) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, =index
> ID 7: Page (1:948333) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, =index
> ID 7: Page (1:948334) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, =index
> ID 7: Page (1:948335) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, =index
> ID 7: Page (1:948336) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, =index
> ID 7: Page (1:948337) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object =ID
> 2031398356, index ID 14, page (1:948330). Test (sorted [i].offset =>=3D
> PAGEHEADSIZE) failed. Slot 233, offset 0x2e is invalid.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object =ID
> 2031398356, index ID 14, page (1:948330). Test (sorted[i].offset =>=3D max)
> failed. Slot 0, offset 0xe9 overlaps with the prior row.
> [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 =allocation
> errors and 11 consistency errors in table 'TblLab' (object ID =2005582183).
> [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 =allocation
> errors and 2 consistency errors in table 'TblPhoneNote' (object ID
> 2031398356).
> [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 =allocation
> errors and 20 consistency errors in database 'XXDB'.
> [Microsoft][ODBC SQL Server Driver][SQL =Server]repair_allow_data_loss is
the
> minimum repair level for the errors found by DBCC CHECKDB (XXDB ).
> ** Execution Time: 0 hrs, 33 mins, 26 secs **
>
> TIA
> CD
>
>
--=_NextPart_000_0043_01C4BB41.E7258280
Content-Type: text/html;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
It is possible for hardware problems to show up as ='transient' corruption issues in DBCC. Issues like caching controllers can =cause the buffer pool to read stale data and feed that stale data to DBCC, which =detects a corruption. If the page is flushed back out of the cache and then =read back in later on, there could be no problem with the read (and thus no corruption as far as DBCC is concerned).
As Wayne correctly suggests, CSS is probabaly your =best alternative at this point, but they are probably going to request that =you do some hardware diagnostics too. You might be preemptive and have =them ready.
Thanks,
Ryan Stonecipher
SQL Server Storage Engine, DBCC
"Wayne Snyder"
--=_NextPart_000_0043_01C4BB41.E7258280--
Error 8909 in job...is it?
Enterprise Edition on Windows NT 5.2 (Build 3790: )
I received the following error the last two nights in a row while running
the gui created maintanence job. I just ran DBCC CHECKDB WITH NO_INFOMSGS
and DBCC CHECKTABLE ('TblPhoneNote') on the tables listed in QA and returned
no errors. I am alarmed but why the errors one way and not the other. Is
there some switches that I enable prior to running in QA to get more info?
[5] Database XXDB: Check Data and Index Linkage...
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8909: [Microsoft]
91;ODBC SQL
Server Driver][SQL Server]Table error: Object ID 10944512, index ID 0, p
age
ID (1:948331). The PageId in the page header = (55:939524096).
The following errors were found:
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Obje
ct ID
10944512, index ID 0, page ID (1:948331). The PageId in the page header =
(55:939524096).
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Obje
ct ID
2005582183, index ID 7, page (1:948329). Test (sorted [i].offset >=
PAGEHEADSIZE) failed. Slot 427, offset 0x2 is invalid.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Obje
ct ID
2005582183, index ID 7, page (1:948329). Test (sorted[i].offset >= max)
failed. Slot 0, offset 0x1ab overlaps with the prior row.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582
183, index
ID 7: Page (1:948330) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582
183, index
ID 7: Page (1:948331) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582
183, index
ID 7: Page (1:948332) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582
183, index
ID 7: Page (1:948333) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582
183, index
ID 7: Page (1:948334) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582
183, index
ID 7: Page (1:948335) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582
183, index
ID 7: Page (1:948336) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582
183, index
ID 7: Page (1:948337) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Obje
ct ID
2031398356, index ID 14, page (1:948330). Test (sorted [i].offset >=
PAGEHEADSIZE) failed. Slot 233, offset 0x2e is invalid.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Obje
ct ID
2031398356, index ID 14, page (1:948330). Test (sorted[i].offset >= max)
failed. Slot 0, offset 0xe9 overlaps with the prior row.
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 a
llocation
errors and 11 consistency errors in table 'TblLab' (object ID 2005582183).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 a
llocation
errors and 2 consistency errors in table 'TblPhoneNote' (object ID
2031398356).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 a
llocation
errors and 20 consistency errors in database 'XXDB'.
[Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data
_loss is the
minimum repair level for the errors found by DBCC CHECKDB (XXDB ).
** Execution Time: 0 hrs, 33 mins, 26 secs **
TIA
CDTime to open a call to Microsoft PSS.. It costs $249 I think... If the data
is important, don't risk it..
Also, do not overwrite any backups until you get this resolved..
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"CD" <mcdye1@.hotmail.nospam.com> wrote in message
news:OfSshe1uEHA.3872@.TK2MSFTNGP11.phx.gbl...
> Microsoft SQL Server 2000 - 8.00.923 (Intel X86)
> Enterprise Edition on Windows NT 5.2 (Build 3790: )
> I received the following error the last two nights in a row while running
> the gui created maintanence job. I just ran DBCC CHECKDB WITH NO_INFOMSGS
> and DBCC CHECKTABLE ('TblPhoneNote') on the tables listed in QA and
returned
> no errors. I am alarmed but why the errors one way and not the other. Is
> there some switches that I enable prior to running in QA to get more info?
> [5] Database XXDB: Check Data and Index Linkage...
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8909: [Microsoft][ODB
C
SQL
> Server Driver][SQL Server]Table error: Object ID 10944512, index ID 0,
page
> ID (1:948331). The PageId in the page header = (55:939524096).
> The following errors were found:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Ob
ject ID
> 10944512, index ID 0, page ID (1:948331). The PageId in the page header =
> (55:939524096).
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Ob
ject ID
> 2005582183, index ID 7, page (1:948329). Test (sorted [i].offset >=
> PAGEHEADSIZE) failed. Slot 427, offset 0x2 is invalid.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Ob
ject ID
> 2005582183, index ID 7, page (1:948329). Test (sorted[i].offset >= max
)
> failed. Slot 0, offset 0x1ab overlaps with the prior row.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948330) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948331) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948332) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948333) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948334) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948335) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948336) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948337) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Ob
ject ID
> 2031398356, index ID 14, page (1:948330). Test (sorted [i].offset >=
> PAGEHEADSIZE) failed. Slot 233, offset 0x2e is invalid.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Ob
ject ID
> 2031398356, index ID 14, page (1:948330). Test (sorted[i].offset >= ma
x)
> failed. Slot 0, offset 0xe9 overlaps with the prior row.
> [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0
allocation
> errors and 11 consistency errors in table 'TblLab' (object ID 2005582183).
> [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0
allocation
> errors and 2 consistency errors in table 'TblPhoneNote' (object ID
> 2031398356).
> [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0
allocation
> errors and 20 consistency errors in database 'XXDB'.
> [Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss
is
the
> minimum repair level for the errors found by DBCC CHECKDB (XXDB ).
> ** Execution Time: 0 hrs, 33 mins, 26 secs **
> TIA
> CD
>|||It is possible for hardware problems to show up as 'transient' corruption is
sues in DBCC. Issues like caching controllers can cause the buffer pool to
read stale data and feed that stale data to DBCC, which detects a corruption
. If the page is flushed back out of the cache and then read back in later
on, there could be no problem with the read (and thus no corruption as far a
s DBCC is concerned).
As Wayne correctly suggests, CSS is probabaly your best alternative at this
point, but they are probably going to request that you do some hardware diag
nostics too. You might be preemptive and have them ready.
Thanks,
Ryan Stonecipher
SQL Server Storage Engine, DBCC
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message news:e
hsYVw1uEHA.4028@.TK2MSFTNGP15.phx.gbl...
Time to open a call to Microsoft PSS.. It costs $249 I think... If the data
is important, don't risk it..
Also, do not overwrite any backups until you get this resolved..
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"CD" <mcdye1@.hotmail.nospam.com> wrote in message
news:OfSshe1uEHA.3872@.TK2MSFTNGP11.phx.gbl...
> Microsoft SQL Server 2000 - 8.00.923 (Intel X86)
> Enterprise Edition on Windows NT 5.2 (Build 3790: )
> I received the following error the last two nights in a row while running
> the gui created maintanence job. I just ran DBCC CHECKDB WITH NO_INFOMSGS
> and DBCC CHECKTABLE ('TblPhoneNote') on the tables listed in QA and
returned
> no errors. I am alarmed but why the errors one way and not the other. Is
> there some switches that I enable prior to running in QA to get more info?
> [5] Database XXDB: Check Data and Index Linkage...
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8909: [Microsoft][ODB
C
SQL
> Server Driver][SQL Server]Table error: Object ID 10944512, index ID 0,
page
> ID (1:948331). The PageId in the page header = (55:939524096).
> The following errors were found:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Ob
ject ID
> 10944512, index ID 0, page ID (1:948331). The PageId in the page header =
> (55:939524096).
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Ob
ject ID
> 2005582183, index ID 7, page (1:948329). Test (sorted [i].offset >=
> PAGEHEADSIZE) failed. Slot 427, offset 0x2 is invalid.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Ob
ject ID
> 2005582183, index ID 7, page (1:948329). Test (sorted[i].offset >= max
)
> failed. Slot 0, offset 0x1ab overlaps with the prior row.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948330) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948331) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948332) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948333) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948334) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948335) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948336) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948337) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Ob
ject ID
> 2031398356, index ID 14, page (1:948330). Test (sorted [i].offset >=
> PAGEHEADSIZE) failed. Slot 233, offset 0x2e is invalid.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Ob
ject ID
> 2031398356, index ID 14, page (1:948330). Test (sorted[i].offset >= ma
x)
> failed. Slot 0, offset 0xe9 overlaps with the prior row.
> [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0
allocation
> errors and 11 consistency errors in table 'TblLab' (object ID 2005582183).
> [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0
allocation
> errors and 2 consistency errors in table 'TblPhoneNote' (object ID
> 2031398356).
> [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0
allocation
> errors and 20 consistency errors in database 'XXDB'.
> [Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss
is
the
> minimum repair level for the errors found by DBCC CHECKDB (XXDB ).
> ** Execution Time: 0 hrs, 33 mins, 26 secs **
> TIA
> CD
>sql
Error 87 while installing SQL Server 2005
Hi everyone!
I'm not sure if this is an old issue, but I couldn't find it in any thread. Here I go:
I downloaded SQL Server 2005 Enterprise Edition from the MSDN site; but when I run the installation wizard I get this error:
Errors occurred during the installation
Error 87 installing .NET Framework 2.0
The parameter is incorrect
And then I have to cancel the installation. This machine meets the hardware requirements, and it already has the .NET framework 2.0 installed. Humm, what else? It's a Windows 2003 Server SP1 machine...let me know if you need more information.
I've been trying to figure out a solution, but I finally gave up
I'm trying to install Team Foundation Server, but first I have to install IIS 6.0 (done), SQL Server 2005, Share Point Services....and I'm afraid that the TFS Installation Wizard will ask me to dance 'Macarena' or something like that ??
Ejem, sorry for the whining. Well, does anyone out there know what can I do in order to successfully install SQL Server 2005? Any help will be appreciated
Thanks in advance!
This issue is solved. It was all about the way I burned the DVD.|||Hello,
I've got the same error. How do you resolve it?
What different way must I take to burn the dvd right and get to install the SQL succesfully?
thank you very much in advance. I'm deseperate.
Naiara
|||I'll give you more details.
I'm trying to install BizTalk Server 2006 in a PC with windows 2000 professional sp4, and first I must install Visual Studio 2005 and Sql 2005 Server among others. The three aplicactions are trial versions downloaded from the MSDN site and the three are spanish versions.
Both (Visual and SQL) uses .NET framework 2.0. I've been succesful installing the Visual, which comes with NET framework 2.0, but when I've run the installation wizard of SQL 2005 from the dvd, I've got the same error above (error 87) and the unique exit is to cancel the installation.
First I've searched for a solution in msdn soporter. I've found this article
Error message when you install SQL Server 2005: "Beta components detected"
View products that this article applies to.
Bug #: 449253 (SQLBUDT)
SYMPTOMS
When you install Microsoft SQL Server 2005, you may receive the following error message:
Beta components detected.
This problem is likely to occur when you install SQL Server 2005 on a computer that has a beta version of Microsoft Visual Studio 2005 installed.
CAUSE
This problem occurs because the Microsoft .NET Framework installer (Dotnetfx.exe) detects beta components that block the installation. The SQL Server 2005 Setup program does not detect the components that may prevent the .NET Framework installation. For example, if you have installed a beta version of Visual J# 2005, you experience this problem when you install SQL Server 2005.
WORKAROUND
To work around this problem, you must uninstall the beta components. Then, try to install SQL Server 2005 again. To find whether beta components that prevent the installation have been installed on your computer, run the Dotnetfx.exe program. The Dotnetfx.exe program displays a dialog box that contains the name of the beta components that prevent installation.
Note The Dotnetfx.exe file is located in the Servers\Redist\2.0 folder on the SQL Server 2005 Setup media
I've tried this solution but when I've run Dotnetfx.exe, nothing has happened: the console has appeared for a while and then it has disappeared without showing any components to unistall.
Can anyone there help me?
Thank you very much.
Naiara
|||I faced the same issuemy work around is exactly the same...it already has the .NET framework 2.0 isntalled...Windows 2k3 Server SP1...pls let me know how to resolve this issue ASAP
|||
Whoa, this was more than 1 year ago. I don't even work for that company anymore.
Well...going back to my issue, as far as I remember I had to re-burn de DVD using another dvd-burner (a different pc). If that doesn't work then you can try by mounting the .iso (you'll may have to download another software in order to perform this action)
And if you're talking about the beta/old versions then you only have to uninstall it.
I hope this helps.
|||I am having this same issue with a new build of server 2003, and sql server 2005 on a VMware virtual machine.SQL server has installed, and works ok. But i need to install some additional components. When i run the install to add the new components i get the Error 87 while installing .NET 2.0
I have tried uninstalling .net, and running setup again but it does the same thing.
There are lots of posts on the internet but no definitive solutions. Re-burning a DVD doesnt make sense to me, its the same ISO i used to install it that i'm using to add components and its still doing it. Does anyone have a definitive answer to solve this? Its driving me nuts!!
Error 87 while installing SQL Server 2005
Hi everyone!
I'm not sure if this is an old issue, but I couldn't find it in any thread. Here I go:
I downloaded SQL Server 2005 Enterprise Edition from the MSDN site; but when I run the installation wizard I get this error:
Errors occurred during the installation
Error 87 installing .NET Framework 2.0
The parameter is incorrect
And then I have to cancel the installation. This machine meets the hardware requirements, and it already has the .NET framework 2.0 installed. Humm, what else? It's a Windows 2003 Server SP1 machine...let me know if you need more information.
I've been trying to figure out a solution, but I finally gave up
I'm trying to install Team Foundation Server, but first I have to install IIS 6.0 (done), SQL Server 2005, Share Point Services....and I'm afraid that the TFS Installation Wizard will ask me to dance 'Macarena' or something like that ??
Ejem, sorry for the whining. Well, does anyone out there know what can I do in order to successfully install SQL Server 2005? Any help will be appreciated
Thanks in advance!
This issue is solved. It was all about the way I burned the DVD.|||Hello,
I've got the same error. How do you resolve it?
What different way must I take to burn the dvd right and get to install the SQL succesfully?
thank you very much in advance. I'm deseperate.
Naiara
|||I'll give you more details.
I'm trying to install BizTalk Server 2006 in a PC with windows 2000 professional sp4, and first I must install Visual Studio 2005 and Sql 2005 Server among others. The three aplicactions are trial versions downloaded from the MSDN site and the three are spanish versions.
Both (Visual and SQL) uses .NET framework 2.0. I've been succesful installing the Visual, which comes with NET framework 2.0, but when I've run the installation wizard of SQL 2005 from the dvd, I've got the same error above (error 87) and the unique exit is to cancel the installation.
First I've searched for a solution in msdn soporter. I've found this article
Error message when you install SQL Server 2005: "Beta components detected"
View products that this article applies to.
Bug #: 449253 (SQLBUDT)
SYMPTOMS
When you install Microsoft SQL Server 2005, you may receive the following error message:
Beta components detected.
This problem is likely to occur when you install SQL Server 2005 on a computer that has a beta version of Microsoft Visual Studio 2005 installed.
CAUSE
This problem occurs because the Microsoft .NET Framework installer (Dotnetfx.exe) detects beta components that block the installation. The SQL Server 2005 Setup program does not detect the components that may prevent the .NET Framework installation. For example, if you have installed a beta version of Visual J# 2005, you experience this problem when you install SQL Server 2005.
WORKAROUND
To work around this problem, you must uninstall the beta components. Then, try to install SQL Server 2005 again. To find whether beta components that prevent the installation have been installed on your computer, run the Dotnetfx.exe program. The Dotnetfx.exe program displays a dialog box that contains the name of the beta components that prevent installation.
Note The Dotnetfx.exe file is located in the Servers\Redist\2.0 folder on the SQL Server 2005 Setup media
I've tried this solution but when I've run Dotnetfx.exe, nothing has happened: the console has appeared for a while and then it has disappeared without showing any components to unistall.
Can anyone there help me?
Thank you very much.
Naiara
|||I faced the same issuemy work around is exactly the same...it already has the .NET framework 2.0 isntalled...Windows 2k3 Server SP1...pls let me know how to resolve this issue ASAP
|||
Whoa, this was more than 1 year ago. I don't even work for that company anymore.
Well...going back to my issue, as far as I remember I had to re-burn de DVD using another dvd-burner (a different pc). If that doesn't work then you can try by mounting the .iso (you'll may have to download another software in order to perform this action)
And if you're talking about the beta/old versions then you only have to uninstall it.
I hope this helps.
|||I am having this same issue with a new build of server 2003, and sql server 2005 on a VMware virtual machine.SQL server has installed, and works ok. But i need to install some additional components. When i run the install to add the new components i get the Error 87 while installing .NET 2.0
I have tried uninstalling .net, and running setup again but it does the same thing.
There are lots of posts on the internet but no definitive solutions. Re-burning a DVD doesnt make sense to me, its the same ISO i used to install it that i'm using to add components and its still doing it. Does anyone have a definitive answer to solve this? Its driving me nuts!!
sql
Error 87 while installing SQL Server 2005
Hi everyone!
I'm not sure if this is an old issue, but I couldn't find it in any thread. Here I go:
I downloaded SQL Server 2005 Enterprise Edition from the MSDN site; but when I run the installation wizard I get this error:
Errors occurred during the installation
Error 87 installing .NET Framework 2.0
The parameter is incorrect
And then I have to cancel the installation. This machine meets the hardware requirements, and it already has the .NET framework 2.0 installed. Humm, what else? It's a Windows 2003 Server SP1 machine...let me know if you need more information.
I've been trying to figure out a solution, but I finally gave up
I'm trying to install Team Foundation Server, but first I have to install IIS 6.0 (done), SQL Server 2005, Share Point Services....and I'm afraid that the TFS Installation Wizard will ask me to dance 'Macarena' or something like that ??
Ejem, sorry for the whining. Well, does anyone out there know what can I do in order to successfully install SQL Server 2005? Any help will be appreciated
Thanks in advance!
This issue is solved. It was all about the way I burned the DVD.|||Hello,
I've got the same error. How do you resolve it?
What different way must I take to burn the dvd right and get to install the SQL succesfully?
thank you very much in advance. I'm deseperate.
Naiara
|||I'll give you more details.
I'm trying to install BizTalk Server 2006 in a PC with windows 2000 professional sp4, and first I must install Visual Studio 2005 and Sql 2005 Server among others. The three aplicactions are trial versions downloaded from the MSDN site and the three are spanish versions.
Both (Visual and SQL) uses .NET framework 2.0. I've been succesful installing the Visual, which comes with NET framework 2.0, but when I've run the installation wizard of SQL 2005 from the dvd, I've got the same error above (error 87) and the unique exit is to cancel the installation.
First I've searched for a solution in msdn soporter. I've found this article
Error message when you install SQL Server 2005: "Beta components detected"
View products that this article applies to.
Bug #: 449253 (SQLBUDT)
SYMPTOMS
When you install Microsoft SQL Server 2005, you may receive the following error message:
Beta components detected.
This problem is likely to occur when you install SQL Server 2005 on a computer that has a beta version of Microsoft Visual Studio 2005 installed.
CAUSE
This problem occurs because the Microsoft .NET Framework installer (Dotnetfx.exe) detects beta components that block the installation. The SQL Server 2005 Setup program does not detect the components that may prevent the .NET Framework installation. For example, if you have installed a beta version of Visual J# 2005, you experience this problem when you install SQL Server 2005.
WORKAROUND
To work around this problem, you must uninstall the beta components. Then, try to install SQL Server 2005 again. To find whether beta components that prevent the installation have been installed on your computer, run the Dotnetfx.exe program. The Dotnetfx.exe program displays a dialog box that contains the name of the beta components that prevent installation.
Note The Dotnetfx.exe file is located in the Servers\Redist\2.0 folder on the SQL Server 2005 Setup media
I've tried this solution but when I've run Dotnetfx.exe, nothing has happened: the console has appeared for a while and then it has disappeared without showing any components to unistall.
Can anyone there help me?
Thank you very much.
Naiara
|||I faced the same issuemy work around is exactly the same...it already has the .NET framework 2.0 isntalled...Windows 2k3 Server SP1...pls let me know how to resolve this issue ASAP
|||
Whoa, this was more than 1 year ago. I don't even work for that company anymore.
Well...going back to my issue, as far as I remember I had to re-burn de DVD using another dvd-burner (a different pc). If that doesn't work then you can try by mounting the .iso (you'll may have to download another software in order to perform this action)
And if you're talking about the beta/old versions then you only have to uninstall it.
I hope this helps.
|||I am having this same issue with a new build of server 2003, and sql server 2005 on a VMware virtual machine.SQL server has installed, and works ok. But i need to install some additional components. When i run the install to add the new components i get the Error 87 while installing .NET 2.0
I have tried uninstalling .net, and running setup again but it does the same thing.
There are lots of posts on the internet but no definitive solutions. Re-burning a DVD doesnt make sense to me, its the same ISO i used to install it that i'm using to add components and its still doing it. Does anyone have a definitive answer to solve this? Its driving me nuts!!
Error 87 while installing SQL Server 2005
Hi everyone!
I'm not sure if this is an old issue, but I couldn't find it in any thread. Here I go:
I downloaded SQL Server 2005 Enterprise Edition from the MSDN site; but when I run the installation wizard I get this error:
Errors occurred during the installation
Error 87 installing .NET Framework 2.0
The parameter is incorrect
And then I have to cancel the installation. This machine meets the hardware requirements, and it already has the .NET framework 2.0 installed. Humm, what else? It's a Windows 2003 Server SP1 machine...let me know if you need more information.
I've been trying to figure out a solution, but I finally gave up
I'm trying to install Team Foundation Server, but first I have to install IIS 6.0 (done), SQL Server 2005, Share Point Services....and I'm afraid that the TFS Installation Wizard will ask me to dance 'Macarena' or something like that ??
Ejem, sorry for the whining. Well, does anyone out there know what can I do in order to successfully install SQL Server 2005? Any help will be appreciated
Thanks in advance!
This issue is solved. It was all about the way I burned the DVD.|||Hello,
I've got the same error. How do you resolve it?
What different way must I take to burn the dvd right and get to install the SQL succesfully?
thank you very much in advance. I'm deseperate.
Naiara
|||I'll give you more details.
I'm trying to install BizTalk Server 2006 in a PC with windows 2000 professional sp4, and first I must install Visual Studio 2005 and Sql 2005 Server among others. The three aplicactions are trial versions downloaded from the MSDN site and the three are spanish versions.
Both (Visual and SQL) uses .NET framework 2.0. I've been succesful installing the Visual, which comes with NET framework 2.0, but when I've run the installation wizard of SQL 2005 from the dvd, I've got the same error above (error 87) and the unique exit is to cancel the installation.
First I've searched for a solution in msdn soporter. I've found this article
Error message when you install SQL Server 2005: "Beta components detected"
View products that this article applies to.
Bug #: 449253 (SQLBUDT)
SYMPTOMS
When you install Microsoft SQL Server 2005, you may receive the following error message:
Beta components detected.
This problem is likely to occur when you install SQL Server 2005 on a computer that has a beta version of Microsoft Visual Studio 2005 installed.CAUSE
This problem occurs because the Microsoft .NET Framework installer (Dotnetfx.exe) detects beta components that block the installation. The SQL Server 2005 Setup program does not detect the components that may prevent the .NET Framework installation. For example, if you have installed a beta version of Visual J# 2005, you experience this problem when you install SQL Server 2005.
WORKAROUND
To work around this problem, you must uninstall the beta components. Then, try to install SQL Server 2005 again. To find whether beta components that prevent the installation have been installed on your computer, run the Dotnetfx.exe program. The Dotnetfx.exe program displays a dialog box that contains the name of the beta components that prevent installation.
Note The Dotnetfx.exe file is located in the Servers\Redist\2.0 folder on the SQL Server 2005 Setup media
I've tried this solution but when I've run Dotnetfx.exe, nothing has happened: the console has appeared for a while and then it has disappeared without showing any components to unistall.
Can anyone there help me?
Thank you very much.
Naiara
|||I faced the same issuemy work around is exactly the same...it already has the .NET framework 2.0 isntalled...Windows 2k3 Server SP1...pls let me know how to resolve this issue ASAP
Whoa, this was more than 1 year ago. I don't even work for that company anymore.
Well...going back to my issue, as far as I remember I had to re-burn de DVD using another dvd-burner (a different pc). If that doesn't work then you can try by mounting the .iso (you'll may have to download another software in order to perform this action)
And if you're talking about the beta/old versions then you only have to uninstall it.
I hope this helps.
|||I am having this same issue with a new build of server 2003, and sql server 2005 on a VMware virtual machine.SQL server has installed, and works ok. But i need to install some additional components. When i run the install to add the new components i get the Error 87 while installing .NET 2.0
I have tried uninstalling .net, and running setup again but it does the same thing.
There are lots of posts on the internet but no definitive solutions. Re-burning a DVD doesnt make sense to me, its the same ISO i used to install it that i'm using to add components and its still doing it. Does anyone have a definitive answer to solve this? Its driving me nuts!!
Wednesday, March 21, 2012
Error 7391 when distributed transaction started
Windows 2003 Server Standar Edition SP1
SQL Server 2005 Standar Edition
Node 2:
Windows 2000 Server SP4
SQL Server 2000 Standar Edition SP3a
Node 1 have node 2 like "linked server", node 2 have node 1 like "linked
server" too.
Both nodes use Microsoft OLE DB Provider for SQL Server.
Node 1 begins a distributed transaction vs Node 2.
Transaction KO with
"Server: Msg 7391, Level 16, State 1, Line 1
The operation could not be performed because the OLE DB provider 'SQLOLEDB'
was unable to begin a distributed transaction.
OLE/DB provider returned message: New transaction cannot enlist in the
specified transaction coordinator. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d00a]."
MS DTS is configured in Node 1 like microsoft said in
http://suppport.microsoftl.com/defa...kb;en-us;329332
If I change Node1 with Windows 2000 Server Standard Edition and SQL Server
2000 SP3a, the distribution transaction run OK.
Thanks a lot.Hi
Windows 2003 has more secure defaults than Windows 2000 therefore it is
probably something that has not been configured that is causing the problem
Check out http://support.microsoft.com/kb/839279/
http://support.microsoft.com/kb/191168/
http://support.microsoft.com/kb/306843/
http://support.microsoft.com/kb/306843/
http://support.microsoft.com/kb/329332
http://support.microsoft.com/kb/306212
You can use DTCPing to check it can communicate with the server
http://download.microsoft.com/downl.../>
dtcping.exe
John
"FRF" wrote:
> Node 1:
> Windows 2003 Server Standar Edition SP1
> SQL Server 2005 Standar Edition
> Node 2:
> Windows 2000 Server SP4
> SQL Server 2000 Standar Edition SP3a
> Node 1 have node 2 like "linked server", node 2 have node 1 like "linked
> server" too.
> Both nodes use Microsoft OLE DB Provider for SQL Server.
> Node 1 begins a distributed transaction vs Node 2.
> Transaction KO with
> "Server: Msg 7391, Level 16, State 1, Line 1
> The operation could not be performed because the OLE DB provider 'SQLOLEDB
'
> was unable to begin a distributed transaction.
> OLE/DB provider returned message: New transaction cannot enlist in the
> specified transaction coordinator. ]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
> ITransactionJoin::JoinTransaction returned 0x8004d00a]."
> MS DTS is configured in Node 1 like microsoft said in
> http://suppport.microsoftl.com/defa...kb;en-us;329332
> If I change Node1 with Windows 2000 Server Standard Edition and SQL Server
> 2000 SP3a, the distribution transaction run OK.
> Thanks a lot.
>
Error 7391 when distributed transaction started
Windows 2003 Server Standar Edition SP1
SQL Server 2005 Standar Edition
Node 2:
Windows 2000 Server SP4
SQL Server 2000 Standar Edition SP3a
Node 1 have node 2 like "linked server", node 2 have node 1 like "linked
server" too.
Both nodes use Microsoft OLE DB Provider for SQL Server.
Node 1 begins a distributed transaction vs Node 2.
Transaction KO with
"Server: Msg 7391, Level 16, State 1, Line 1
The operation could not be performed because the OLE DB provider 'SQLOLEDB'
was unable to begin a distributed transaction.
OLE/DB provider returned message: New transaction cannot enlist in the
specified transaction coordinator. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d00a]."
MS DTS is configured in Node 1 like microsoft said in
http://suppport.microsoftl.com/defau...b;en-us;329332
If I change Node1 with Windows 2000 Server Standard Edition and SQL Server
2000 SP3a, the distribution transaction run OK.
Thanks a lot.
Hi
Windows 2003 has more secure defaults than Windows 2000 therefore it is
probably something that has not been configured that is causing the problem
Check out http://support.microsoft.com/kb/839279/
http://support.microsoft.com/kb/191168/
http://support.microsoft.com/kb/306843/
http://support.microsoft.com/kb/306843/
http://support.microsoft.com/kb/329332
http://support.microsoft.com/kb/306212
You can use DTCPing to check it can communicate with the server
http://download.microsoft.com/downlo...c1/dtcping.exe
John
"FRF" wrote:
> Node 1:
> Windows 2003 Server Standar Edition SP1
> SQL Server 2005 Standar Edition
> Node 2:
> Windows 2000 Server SP4
> SQL Server 2000 Standar Edition SP3a
> Node 1 have node 2 like "linked server", node 2 have node 1 like "linked
> server" too.
> Both nodes use Microsoft OLE DB Provider for SQL Server.
> Node 1 begins a distributed transaction vs Node 2.
> Transaction KO with
> "Server: Msg 7391, Level 16, State 1, Line 1
> The operation could not be performed because the OLE DB provider 'SQLOLEDB'
> was unable to begin a distributed transaction.
> OLE/DB provider returned message: New transaction cannot enlist in the
> specified transaction coordinator. ]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
> ITransactionJoin::JoinTransaction returned 0x8004d00a]."
> MS DTS is configured in Node 1 like microsoft said in
> http://suppport.microsoftl.com/defau...b;en-us;329332
> If I change Node1 with Windows 2000 Server Standard Edition and SQL Server
> 2000 SP3a, the distribution transaction run OK.
> Thanks a lot.
>
sql
Error 7391 when distributed transaction started
Windows 2003 Server Standar Edition SP1
SQL Server 2005 Standar Edition
Node 2:
Windows 2000 Server SP4
SQL Server 2000 Standar Edition SP3a
Node 1 have node 2 like "linked server", node 2 have node 1 like "linked
server" too.
Both nodes use Microsoft OLE DB Provider for SQL Server.
Node 1 begins a distributed transaction vs Node 2.
Transaction KO with
"Server: Msg 7391, Level 16, State 1, Line 1
The operation could not be performed because the OLE DB provider 'SQLOLEDB'
was unable to begin a distributed transaction.
OLE/DB provider returned message: New transaction cannot enlist in the
specified transaction coordinator. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d00a]."
MS DTS is configured in Node 1 like microsoft said in
http://suppport.microsoftl.com/default.aspx?scid=kb;en-us;329332
If I change Node1 with Windows 2000 Server Standard Edition and SQL Server
2000 SP3a, the distribution transaction run OK.
Thanks a lot.Hi
Windows 2003 has more secure defaults than Windows 2000 therefore it is
probably something that has not been configured that is causing the problem
Check out http://support.microsoft.com/kb/839279/
http://support.microsoft.com/kb/191168/
http://support.microsoft.com/kb/306843/
http://support.microsoft.com/kb/306843/
http://support.microsoft.com/kb/329332
http://support.microsoft.com/kb/306212
You can use DTCPing to check it can communicate with the server
http://download.microsoft.com/download/d/0/0/d00c8f6b-135d-4441-a97b-9de16a1935c1/dtcping.exe
John
"FRF" wrote:
> Node 1:
> Windows 2003 Server Standar Edition SP1
> SQL Server 2005 Standar Edition
> Node 2:
> Windows 2000 Server SP4
> SQL Server 2000 Standar Edition SP3a
> Node 1 have node 2 like "linked server", node 2 have node 1 like "linked
> server" too.
> Both nodes use Microsoft OLE DB Provider for SQL Server.
> Node 1 begins a distributed transaction vs Node 2.
> Transaction KO with
> "Server: Msg 7391, Level 16, State 1, Line 1
> The operation could not be performed because the OLE DB provider 'SQLOLEDB'
> was unable to begin a distributed transaction.
> OLE/DB provider returned message: New transaction cannot enlist in the
> specified transaction coordinator. ]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
> ITransactionJoin::JoinTransaction returned 0x8004d00a]."
> MS DTS is configured in Node 1 like microsoft said in
> http://suppport.microsoftl.com/default.aspx?scid=kb;en-us;329332
> If I change Node1 with Windows 2000 Server Standard Edition and SQL Server
> 2000 SP3a, the distribution transaction run OK.
> Thanks a lot.
>
Monday, March 19, 2012
Error 627:Cannot use SAVE TRANSACTION within a distributed transac
SQL Server 2000 Enterprise Edition
Server Pack 3a
Server Edition is Windows 2000 Advanced Server
Replication Type is Transactional
I am trying to drop a publication. I am getting the error:
Error 627:Cannot use SAVE TRANSACTION within a distributed transaction
This error also is generated when trying to drop the individual subscription.
Can anyone provide insight as to what could be causing this error?
Thank you in advance.
Robert M.Check the "remote proc trans" value from sp_configure. If it's 1, you need
to change it to 0.
"Robert M." <RobertM@.discussions.microsoft.com> wrote in message
news:28E165FE-67B2-44F1-98DC-1F2CB3EA0B7E@.microsoft.com...
> Information:
> SQL Server 2000 Enterprise Edition
> Server Pack 3a
> Server Edition is Windows 2000 Advanced Server
> Replication Type is Transactional
> I am trying to drop a publication. I am getting the error:
> Error 627:Cannot use SAVE TRANSACTION within a distributed transaction
> This error also is generated when trying to drop the individual
subscription.
> Can anyone provide insight as to what could be causing this error?
> Thank you in advance.
> Robert M.
>|||I am assuming that the 'remote proc trans' setting needs to be set to zero on
the publisher (i have separate servers for distributor/publisher/subscriber).
Thanks...Robert M.
"Richard Ding" wrote:
> Check the "remote proc trans" value from sp_configure. If it's 1, you need
> to change it to 0.
>
> "Robert M." <RobertM@.discussions.microsoft.com> wrote in message
> news:28E165FE-67B2-44F1-98DC-1F2CB3EA0B7E@.microsoft.com...
> > Information:
> > SQL Server 2000 Enterprise Edition
> > Server Pack 3a
> > Server Edition is Windows 2000 Advanced Server
> > Replication Type is Transactional
> >
> > I am trying to drop a publication. I am getting the error:
> > Error 627:Cannot use SAVE TRANSACTION within a distributed transaction
> >
> > This error also is generated when trying to drop the individual
> subscription.
> >
> > Can anyone provide insight as to what could be causing this error?
> >
> > Thank you in advance.
> >
> > Robert M.
> >
> >
>
>|||Actually, I believe it should be set to 0 on the subscriber. No need to
touch the values on publisher or distributor.
"Robert M." <RobertM@.discussions.microsoft.com> wrote in message
news:4A56EC3F-0537-441C-990E-0C7D43BD972C@.microsoft.com...
> I am assuming that the 'remote proc trans' setting needs to be set to zero
on
> the publisher (i have separate servers for
distributor/publisher/subscriber).
> Thanks...Robert M.
> "Richard Ding" wrote:
> > Check the "remote proc trans" value from sp_configure. If it's 1, you
need
> > to change it to 0.
> >
> >
> > "Robert M." <RobertM@.discussions.microsoft.com> wrote in message
> > news:28E165FE-67B2-44F1-98DC-1F2CB3EA0B7E@.microsoft.com...
> > > Information:
> > > SQL Server 2000 Enterprise Edition
> > > Server Pack 3a
> > > Server Edition is Windows 2000 Advanced Server
> > > Replication Type is Transactional
> > >
> > > I am trying to drop a publication. I am getting the error:
> > > Error 627:Cannot use SAVE TRANSACTION within a distributed transaction
> > >
> > > This error also is generated when trying to drop the individual
> > subscription.
> > >
> > > Can anyone provide insight as to what could be causing this error?
> > >
> > > Thank you in advance.
> > >
> > > Robert M.
> > >
> > >
> >
> >
> >
Wednesday, March 7, 2012
Error 40: could not open a connection to Mssql server
Hi,
I'm using sql server 2005 express edition. I have created a database using sql server management studio express edition. Now I'm trying to connect it in visual studio 2005. It show following error.
An error has occurred while establishing a connection to the server. When connections to SQL 5erver 2005, this failure may be caused by the fact under the server's default settings SQL Server does not allow remote connections, (provider: Named Pipes Provider, error: 40- Could not open a connection to SQL Server)
I have enables named pipes from Sql services configuration manager.
Hi,
Named Pipes Provider, error: 40 - Could not open a connection to SQL Server
Is just a basic connectivity error meaning the client could not connect to the target SQL Server. So just follow the basic connectivity troubleshooting guidelines on our SQL Protocols blog, see:
SQL Server 2005 Connectivity Issue Troubleshoot - Part I
http://blogs.msdn.com/sql_protocols/archive/2005/10/22/483684.aspx
and
SQL Server 2005 Connectivity Issue Troubleshoot - Part II
http://blogs.msdn.com/sql_protocols/archive/2005/10/29/486861.aspx
This should help you debug the problem.
Sunday, February 26, 2012
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 3123 in SQL Restore
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
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...
>