we are running a maintainance plan on sql 2000 standard edition, got the error,
[2] Database db_source: Check Data Linkage...
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8928: [Microsoft][ODBC SQL
Server Driver][SQL Server]Object ID 1221579390, index ID 0: Page (1:197116)
could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
1221579390, index ID 0, page (1:197116).
Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057
and -1.
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
errors and 2 consistency errors in table 'xxx'(object ID 1221579390).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
errors and 2 consistency errors in database 'db_source'.
[Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is the
minimum repair level for the errors found by DBCC CHECKDB (db_source noindex).
when i run query on anlyzer select * from xxx, i got the error
Server: Msg 823, Level 24, State 2, Line 1
I/O error (torn page) detected during read at offset 0x000000603f8000 in
file 'F:\Program Files\Microsoft SQL Server\MSSQL\data\db_Data.MDF'.
Connection Broken
please help. thanks
Unless this is a nonclustered index your best bet is to restore from the
last known good backup. Do you have Torn Page Detection turned on for that
db? If not you should so you can spot issues like this sooner. In any case
have a look at this series from Paul Randal on checkdb and what your options
are.
[url]http://www.sqlskills.com/blogs/paul/CategoryView,category,CHECKDB%2BFrom%2BEvery%2BAng le.aspx[/url]
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"tulip" <tulip@.discussions.microsoft.com> wrote in message
news:DF042B2B-3DE5-455A-90C2-038534D6CEC7@.microsoft.com...
> we are running a maintainance plan on sql 2000 standard edition, got the
> error,
> [2] Database db_source: Check Data Linkage...
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8928: [Microsoft][ODBC
> SQL
> Server Driver][SQL Server]Object ID 1221579390, index ID 0: Page
> (1:197116)
> could not be processed. See other errors for details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
> 1221579390, index ID 0, page (1:197116).
> Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are
> 2057
> and -1.
> [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
> errors and 2 consistency errors in table 'xxx'(object ID 1221579390).
> [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
> errors and 2 consistency errors in database 'db_source'.
> [Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is
> the
> minimum repair level for the errors found by DBCC CHECKDB (db_source
> noindex).
> when i run query on anlyzer select * from xxx, i got the error
> Server: Msg 823, Level 24, State 2, Line 1
> I/O error (torn page) detected during read at offset 0x000000603f8000 in
> file 'F:\Program Files\Microsoft SQL Server\MSSQL\data\db_Data.MDF'.
> Connection Broken
> please help. thanks
>
|||i found that the error is dated back to 2006, so the backup since then won't
be valid, right?
what does this mean: repair_allow_data_loss is the minimum repair level for
the errors found by DBCC CHECKDB (db_source noindex).
thank you
"Andrew J. Kelly" wrote:
> Unless this is a nonclustered index your best bet is to restore from the
> last known good backup. Do you have Torn Page Detection turned on for that
> db? If not you should so you can spot issues like this sooner. In any case
> have a look at this series from Paul Randal on checkdb and what your options
> are.
> [url]http://www.sqlskills.com/blogs/paul/CategoryView,category,CHECKDB%2BFrom%2BEvery%2BAng le.aspx[/url]
>
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "tulip" <tulip@.discussions.microsoft.com> wrote in message
> news:DF042B2B-3DE5-455A-90C2-038534D6CEC7@.microsoft.com...
>
|||> what does this mean: repair_allow_data_loss is the minimum repair level
> for
> the errors found by DBCC CHECKDB (db_source noindex).
It means that an attempt to repair the table may result in data loss, but
the only way you can try at all, is to allow for that to happen.
Showing posts with label plan. Show all posts
Showing posts with label plan. Show all posts
Monday, March 26, 2012
I/O error (torn page) detected during read
we are running a maintainance plan on sql 2000 standard edition, got the error,
[2] Database db_source: Check Data Linkage...
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8928: [Microsoft][ODBC SQL
Server Driver][SQL Server]Object ID 1221579390, index ID 0: Page (1:197116)
could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
1221579390, index ID 0, page (1:197116).
Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057
and -1.
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
errors and 2 consistency errors in table 'xxx'(object ID 1221579390).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
errors and 2 consistency errors in database 'db_source'.
[Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is the
minimum repair level for the errors found by DBCC CHECKDB (db_source noindex).
when i run query on anlyzer select * from xxx, i got the error
Server: Msg 823, Level 24, State 2, Line 1
I/O error (torn page) detected during read at offset 0x000000603f8000 in
file 'F:\Program Files\Microsoft SQL Server\MSSQL\data\db_Data.MDF'.
Connection Broken
please help. thanksUnless this is a nonclustered index your best bet is to restore from the
last known good backup. Do you have Torn Page Detection turned on for that
db? If not you should so you can spot issues like this sooner. In any case
have a look at this series from Paul Randal on checkdb and what your options
are.
http://www.sqlskills.com/blogs/paul/CategoryView,category,CHECKDB%2BFrom%2BEvery%2BAngle.aspx
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"tulip" <tulip@.discussions.microsoft.com> wrote in message
news:DF042B2B-3DE5-455A-90C2-038534D6CEC7@.microsoft.com...
> we are running a maintainance plan on sql 2000 standard edition, got the
> error,
> [2] Database db_source: Check Data Linkage...
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8928: [Microsoft][ODBC
> SQL
> Server Driver][SQL Server]Object ID 1221579390, index ID 0: Page
> (1:197116)
> could not be processed. See other errors for details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
> 1221579390, index ID 0, page (1:197116).
> Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are
> 2057
> and -1.
> [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
> errors and 2 consistency errors in table 'xxx'(object ID 1221579390).
> [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
> errors and 2 consistency errors in database 'db_source'.
> [Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is
> the
> minimum repair level for the errors found by DBCC CHECKDB (db_source
> noindex).
> when i run query on anlyzer select * from xxx, i got the error
> Server: Msg 823, Level 24, State 2, Line 1
> I/O error (torn page) detected during read at offset 0x000000603f8000 in
> file 'F:\Program Files\Microsoft SQL Server\MSSQL\data\db_Data.MDF'.
> Connection Broken
> please help. thanks
>|||i found that the error is dated back to 2006, so the backup since then won't
be valid, right?
what does this mean: repair_allow_data_loss is the minimum repair level for
the errors found by DBCC CHECKDB (db_source noindex).
thank you
"Andrew J. Kelly" wrote:
> Unless this is a nonclustered index your best bet is to restore from the
> last known good backup. Do you have Torn Page Detection turned on for that
> db? If not you should so you can spot issues like this sooner. In any case
> have a look at this series from Paul Randal on checkdb and what your options
> are.
> http://www.sqlskills.com/blogs/paul/CategoryView,category,CHECKDB%2BFrom%2BEvery%2BAngle.aspx
>
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "tulip" <tulip@.discussions.microsoft.com> wrote in message
> news:DF042B2B-3DE5-455A-90C2-038534D6CEC7@.microsoft.com...
> > we are running a maintainance plan on sql 2000 standard edition, got the
> > error,
> >
> > [2] Database db_source: Check Data Linkage...
> > [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8928: [Microsoft][ODBC
> > SQL
> > Server Driver][SQL Server]Object ID 1221579390, index ID 0: Page
> > (1:197116)
> > could not be processed. See other errors for details.
> > [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
> > 1221579390, index ID 0, page (1:197116).
> > Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are
> > 2057
> > and -1.
> > [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
> > errors and 2 consistency errors in table 'xxx'(object ID 1221579390).
> > [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
> > errors and 2 consistency errors in database 'db_source'.
> > [Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is
> > the
> > minimum repair level for the errors found by DBCC CHECKDB (db_source
> > noindex).
> >
> > when i run query on anlyzer select * from xxx, i got the error
> > Server: Msg 823, Level 24, State 2, Line 1
> > I/O error (torn page) detected during read at offset 0x000000603f8000 in
> > file 'F:\Program Files\Microsoft SQL Server\MSSQL\data\db_Data.MDF'.
> >
> > Connection Broken
> >
> > please help. thanks
> >
> >
>|||> what does this mean: repair_allow_data_loss is the minimum repair level
> for
> the errors found by DBCC CHECKDB (db_source noindex).
It means that an attempt to repair the table may result in data loss, but
the only way you can try at all, is to allow for that to happen.
[2] Database db_source: Check Data Linkage...
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8928: [Microsoft][ODBC SQL
Server Driver][SQL Server]Object ID 1221579390, index ID 0: Page (1:197116)
could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
1221579390, index ID 0, page (1:197116).
Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057
and -1.
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
errors and 2 consistency errors in table 'xxx'(object ID 1221579390).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
errors and 2 consistency errors in database 'db_source'.
[Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is the
minimum repair level for the errors found by DBCC CHECKDB (db_source noindex).
when i run query on anlyzer select * from xxx, i got the error
Server: Msg 823, Level 24, State 2, Line 1
I/O error (torn page) detected during read at offset 0x000000603f8000 in
file 'F:\Program Files\Microsoft SQL Server\MSSQL\data\db_Data.MDF'.
Connection Broken
please help. thanksUnless this is a nonclustered index your best bet is to restore from the
last known good backup. Do you have Torn Page Detection turned on for that
db? If not you should so you can spot issues like this sooner. In any case
have a look at this series from Paul Randal on checkdb and what your options
are.
http://www.sqlskills.com/blogs/paul/CategoryView,category,CHECKDB%2BFrom%2BEvery%2BAngle.aspx
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"tulip" <tulip@.discussions.microsoft.com> wrote in message
news:DF042B2B-3DE5-455A-90C2-038534D6CEC7@.microsoft.com...
> we are running a maintainance plan on sql 2000 standard edition, got the
> error,
> [2] Database db_source: Check Data Linkage...
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8928: [Microsoft][ODBC
> SQL
> Server Driver][SQL Server]Object ID 1221579390, index ID 0: Page
> (1:197116)
> could not be processed. See other errors for details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
> 1221579390, index ID 0, page (1:197116).
> Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are
> 2057
> and -1.
> [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
> errors and 2 consistency errors in table 'xxx'(object ID 1221579390).
> [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
> errors and 2 consistency errors in database 'db_source'.
> [Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is
> the
> minimum repair level for the errors found by DBCC CHECKDB (db_source
> noindex).
> when i run query on anlyzer select * from xxx, i got the error
> Server: Msg 823, Level 24, State 2, Line 1
> I/O error (torn page) detected during read at offset 0x000000603f8000 in
> file 'F:\Program Files\Microsoft SQL Server\MSSQL\data\db_Data.MDF'.
> Connection Broken
> please help. thanks
>|||i found that the error is dated back to 2006, so the backup since then won't
be valid, right?
what does this mean: repair_allow_data_loss is the minimum repair level for
the errors found by DBCC CHECKDB (db_source noindex).
thank you
"Andrew J. Kelly" wrote:
> Unless this is a nonclustered index your best bet is to restore from the
> last known good backup. Do you have Torn Page Detection turned on for that
> db? If not you should so you can spot issues like this sooner. In any case
> have a look at this series from Paul Randal on checkdb and what your options
> are.
> http://www.sqlskills.com/blogs/paul/CategoryView,category,CHECKDB%2BFrom%2BEvery%2BAngle.aspx
>
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "tulip" <tulip@.discussions.microsoft.com> wrote in message
> news:DF042B2B-3DE5-455A-90C2-038534D6CEC7@.microsoft.com...
> > we are running a maintainance plan on sql 2000 standard edition, got the
> > error,
> >
> > [2] Database db_source: Check Data Linkage...
> > [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8928: [Microsoft][ODBC
> > SQL
> > Server Driver][SQL Server]Object ID 1221579390, index ID 0: Page
> > (1:197116)
> > could not be processed. See other errors for details.
> > [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
> > 1221579390, index ID 0, page (1:197116).
> > Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are
> > 2057
> > and -1.
> > [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
> > errors and 2 consistency errors in table 'xxx'(object ID 1221579390).
> > [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
> > errors and 2 consistency errors in database 'db_source'.
> > [Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is
> > the
> > minimum repair level for the errors found by DBCC CHECKDB (db_source
> > noindex).
> >
> > when i run query on anlyzer select * from xxx, i got the error
> > Server: Msg 823, Level 24, State 2, Line 1
> > I/O error (torn page) detected during read at offset 0x000000603f8000 in
> > file 'F:\Program Files\Microsoft SQL Server\MSSQL\data\db_Data.MDF'.
> >
> > Connection Broken
> >
> > please help. thanks
> >
> >
>|||> what does this mean: repair_allow_data_loss is the minimum repair level
> for
> the errors found by DBCC CHECKDB (db_source noindex).
It means that an attempt to repair the table may result in data loss, but
the only way you can try at all, is to allow for that to happen.
Friday, March 23, 2012
I want to work with SQL RS 2000, what do I need on server and dev workstation?
Can anyone simply spell out what I need on each machine? I have an SQL server(2000) that I plan on installing the RS 2000 on. I know it needs the framework 1.1 and vs 2003(on order). Is this correct? And what do I need to install on my development workstations? VS 2003 and ... ? Component Prerequisites Report server Web server with ASP.NET and Internet Information Services (IIS) 5.0 or higher. Report Manager Web server with ASP.NET. Report server database Server with SQL Server 2000 SP3a. Report Designer Client workstation with Microsoft Visual Studio? .NET 2003 and MDAC 2.6 or higher. Administrative tools and utilities Client workstation with access to a report server. Reporting Services Books Online Client workstation, no prerequisites. Sample reports , applications, and sample database Client workstation, no prerequisites. |||
Thanks,
Fred
MDAC 2.6 or higher.
Connection to SQL Server 2000 SP3a instance.
Default website accessible through http://<servername>.
For Windows 2003, the computer must be configured as an application server.
For Windows 2003 to use the network service account to run the ReportServer service, you need SQL Server QFE 859. To download the QFE, go to Microsoft Support.
IIS 5.0 or later installed and configured.
Default website accessible through http://<servername>.
Hallo,
do you have any idea where I can donwload the SQL Server QFE 859? Because the all links I found are not reffering to any donloadable software.
Thanks
|||SQL Server 2000 SP4 should work just fine for this case (and include QFE 859).
-- Robert
I want to work with SQL RS 2000, what do I need on server and dev workstation?
Can anyone simply spell out what I need on each machine? I have an SQL server(2000) that I plan on installing the RS 2000 on. I know it needs the framework 1.1 and vs 2003(on order). Is this correct? And what do I need to install on my development workstations? VS 2003 and ... ? Component Prerequisites Report server Web server with ASP.NET and Internet Information Services (IIS) 5.0 or higher. Report Manager Web server with ASP.NET. Report server database Server with SQL Server 2000 SP3a. Report Designer Client workstation with Microsoft Visual Studio? .NET 2003 and MDAC 2.6 or higher. Administrative tools and utilities Client workstation with access to a report server. Reporting Services Books Online Client workstation, no prerequisites. Sample reports , applications, and sample database Client workstation, no prerequisites. |||
Thanks,
Fred
MDAC 2.6 or higher.
Connection to SQL Server 2000 SP3a instance.
Default website accessible through http://<servername>.
For Windows 2003, the computer must be configured as an application server.
For Windows 2003 to use the network service account to run the ReportServer service, you need SQL Server QFE 859. To download the QFE, go to Microsoft Support.
IIS 5.0 or later installed and configured.
Default website accessible through http://<servername>.
Hallo,
do you have any idea where I can donwload the SQL Server QFE 859? Because the all links I found are not reffering to any donloadable software.
Thanks
|||SQL Server 2000 SP4 should work just fine for this case (and include QFE 859).
-- Robert
Monday, March 19, 2012
I try to create a maintenance plan I am getting the error
TITLE: Microsoft SQL Server Management Studio
Exception has been thrown by the target of an invocation. (mscorlib)
ADDITIONAL INFORMATION:
An OLE DB error 0x80004005 (Client unable to establish connection) occurred while enumerating packages. A SQL statement was issued
and failed.
An OLE DB error 0x80004005 (Client unable to establish connection) occurred while enumerating packages. A SQL statement was issued
and failed.
And evenlog message
The prelogin packet used to open the connection is structurally invalid; the connection has been closed. Please contact the vendor
of the client library. [CLIENT: <local machine>]
I am using Sql Server 2005 Developer Edition 9.0.1399.
I have searched around but cannot find.
Thank you for your help.
ZaferHi Zafer,
Welcome to use MSDN Managed Newsgroup Support.
From your description, my understanding of this issue is: When you create a
Maintenance plan in SQL Server Management Studio, you get the following
error:
An OLE DB error 0x80004005 (Client unable to establish connection) occurred
while enumerating packages. A SQL statement was issued and failed.
If I misunderstood your concern, please feel free to point it out.
Please verify that your server has a valid cert stored in
computer->personal.
On the SQL Server computer, create a Microsoft Management Console (MMC)
snap-in for the Certificates tool. To do this, follow these steps:
a. Click "Start", click "Run", type "mmc" (without the quotation marks)
in the
"Open" box, and then click "OK".
b. On the "File" menu, click "Add/Remove Snap-in".
c. Click "Add", click "Certificates", click "Add", click "Computer
account",
click "Next", click "Finish", click "Close", and then click "OK".
Also, you may check your SQL Server Service Account. If you run SQL Server
as local system, is this issue occur?
Hope this will be helpful!
Sincerely yours,
Wei Lu
Microsoft Online Partner Support
======================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
Exception has been thrown by the target of an invocation. (mscorlib)
ADDITIONAL INFORMATION:
An OLE DB error 0x80004005 (Client unable to establish connection) occurred while enumerating packages. A SQL statement was issued
and failed.
An OLE DB error 0x80004005 (Client unable to establish connection) occurred while enumerating packages. A SQL statement was issued
and failed.
And evenlog message
The prelogin packet used to open the connection is structurally invalid; the connection has been closed. Please contact the vendor
of the client library. [CLIENT: <local machine>]
I am using Sql Server 2005 Developer Edition 9.0.1399.
I have searched around but cannot find.
Thank you for your help.
ZaferHi Zafer,
Welcome to use MSDN Managed Newsgroup Support.
From your description, my understanding of this issue is: When you create a
Maintenance plan in SQL Server Management Studio, you get the following
error:
An OLE DB error 0x80004005 (Client unable to establish connection) occurred
while enumerating packages. A SQL statement was issued and failed.
If I misunderstood your concern, please feel free to point it out.
Please verify that your server has a valid cert stored in
computer->personal.
On the SQL Server computer, create a Microsoft Management Console (MMC)
snap-in for the Certificates tool. To do this, follow these steps:
a. Click "Start", click "Run", type "mmc" (without the quotation marks)
in the
"Open" box, and then click "OK".
b. On the "File" menu, click "Add/Remove Snap-in".
c. Click "Add", click "Certificates", click "Add", click "Computer
account",
click "Next", click "Finish", click "Close", and then click "OK".
Also, you may check your SQL Server Service Account. If you run SQL Server
as local system, is this issue occur?
Hope this will be helpful!
Sincerely yours,
Wei Lu
Microsoft Online Partner Support
======================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
I try to create a maintenance plan I am getting the error
TITLE: Microsoft SQL Server Management Studio
Exception has been thrown by the target of an invocation. (mscorlib)
ADDITIONAL INFORMATION:
An OLE DB error 0x80004005 (Client unable to establish connection) occurred while enumerating packages. A SQL statement was issued
and failed.
An OLE DB error 0x80004005 (Client unable to establish connection) occurred while enumerating packages. A SQL statement was issued
and failed.
And evenlog message
The prelogin packet used to open the connection is structurally invalid; the connection has been closed. Please contact the vendor
of the client library. [CLIENT: <local machine>]
I am using Sql Server 2005 Developer Edition 9.0.1399.
I have searched around but cannot find.
Thank you for your help.
Zafer
Hi Zafer,
Welcome to use MSDN Managed Newsgroup Support.
From your description, my understanding of this issue is: When you create a
Maintenance plan in SQL Server Management Studio, you get the following
error:
An OLE DB error 0x80004005 (Client unable to establish connection) occurred
while enumerating packages. A SQL statement was issued and failed.
If I misunderstood your concern, please feel free to point it out.
Please verify that your server has a valid cert stored in
computer->personal.
On the SQL Server computer, create a Microsoft Management Console (MMC)
snap-in for the Certificates tool. To do this, follow these steps:
a. Click "Start", click "Run", type "mmc" (without the quotation marks)
in the
"Open" box, and then click "OK".
b. On the "File" menu, click "Add/Remove Snap-in".
c. Click "Add", click "Certificates", click "Add", click "Computer
account",
click "Next", click "Finish", click "Close", and then click "OK".
Also, you may check your SQL Server Service Account. If you run SQL Server
as local system, is this issue occur?
Hope this will be helpful!
Sincerely yours,
Wei Lu
Microsoft Online Partner Support
================================================== ====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
Exception has been thrown by the target of an invocation. (mscorlib)
ADDITIONAL INFORMATION:
An OLE DB error 0x80004005 (Client unable to establish connection) occurred while enumerating packages. A SQL statement was issued
and failed.
An OLE DB error 0x80004005 (Client unable to establish connection) occurred while enumerating packages. A SQL statement was issued
and failed.
And evenlog message
The prelogin packet used to open the connection is structurally invalid; the connection has been closed. Please contact the vendor
of the client library. [CLIENT: <local machine>]
I am using Sql Server 2005 Developer Edition 9.0.1399.
I have searched around but cannot find.
Thank you for your help.
Zafer
Hi Zafer,
Welcome to use MSDN Managed Newsgroup Support.
From your description, my understanding of this issue is: When you create a
Maintenance plan in SQL Server Management Studio, you get the following
error:
An OLE DB error 0x80004005 (Client unable to establish connection) occurred
while enumerating packages. A SQL statement was issued and failed.
If I misunderstood your concern, please feel free to point it out.
Please verify that your server has a valid cert stored in
computer->personal.
On the SQL Server computer, create a Microsoft Management Console (MMC)
snap-in for the Certificates tool. To do this, follow these steps:
a. Click "Start", click "Run", type "mmc" (without the quotation marks)
in the
"Open" box, and then click "OK".
b. On the "File" menu, click "Add/Remove Snap-in".
c. Click "Add", click "Certificates", click "Add", click "Computer
account",
click "Next", click "Finish", click "Close", and then click "OK".
Also, you may check your SQL Server Service Account. If you run SQL Server
as local system, is this issue occur?
Hope this will be helpful!
Sincerely yours,
Wei Lu
Microsoft Online Partner Support
================================================== ====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
I try to create a maintenance plan I am getting the error
TITLE: Microsoft SQL Server Management Studio
Exception has been thrown by the target of an invocation. (mscorlib)
ADDITIONAL INFORMATION:
An OLE DB error 0x80004005 (Client unable to establish connection) occurred
while enumerating packages. A SQL statement was issued
and failed.
An OLE DB error 0x80004005 (Client unable to establish connection) occurred
while enumerating packages. A SQL statement was issued
and failed.
And evenlog message
The prelogin packet used to open the connection is structurally invalid; the
connection has been closed. Please contact the vendor
of the client library. [CLIENT: <local machine>]
I am using Sql Server 2005 Developer Edition 9.0.1399.
I have searched around but cannot find.
Thank you for your help.
ZaferHi Zafer,
Welcome to use MSDN Managed Newsgroup Support.
From your description, my understanding of this issue is: When you create a
Maintenance plan in SQL Server Management Studio, you get the following
error:
An OLE DB error 0x80004005 (Client unable to establish connection) occurred
while enumerating packages. A SQL statement was issued and failed.
If I misunderstood your concern, please feel free to point it out.
Please verify that your server has a valid cert stored in
computer->personal.
On the SQL Server computer, create a Microsoft Management Console (MMC)
snap-in for the Certificates tool. To do this, follow these steps:
a. Click "Start", click "Run", type "mmc" (without the quotation marks)
in the
"Open" box, and then click "OK".
b. On the "File" menu, click "Add/Remove Snap-in".
c. Click "Add", click "Certificates", click "Add", click "Computer
account",
click "Next", click "Finish", click "Close", and then click "OK".
Also, you may check your SQL Server Service Account. If you run SQL Server
as local system, is this issue occur?
Hope this will be helpful!
Sincerely yours,
Wei Lu
Microsoft Online Partner Support
========================================
==============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
Exception has been thrown by the target of an invocation. (mscorlib)
ADDITIONAL INFORMATION:
An OLE DB error 0x80004005 (Client unable to establish connection) occurred
while enumerating packages. A SQL statement was issued
and failed.
An OLE DB error 0x80004005 (Client unable to establish connection) occurred
while enumerating packages. A SQL statement was issued
and failed.
And evenlog message
The prelogin packet used to open the connection is structurally invalid; the
connection has been closed. Please contact the vendor
of the client library. [CLIENT: <local machine>]
I am using Sql Server 2005 Developer Edition 9.0.1399.
I have searched around but cannot find.
Thank you for your help.
ZaferHi Zafer,
Welcome to use MSDN Managed Newsgroup Support.
From your description, my understanding of this issue is: When you create a
Maintenance plan in SQL Server Management Studio, you get the following
error:
An OLE DB error 0x80004005 (Client unable to establish connection) occurred
while enumerating packages. A SQL statement was issued and failed.
If I misunderstood your concern, please feel free to point it out.
Please verify that your server has a valid cert stored in
computer->personal.
On the SQL Server computer, create a Microsoft Management Console (MMC)
snap-in for the Certificates tool. To do this, follow these steps:
a. Click "Start", click "Run", type "mmc" (without the quotation marks)
in the
"Open" box, and then click "OK".
b. On the "File" menu, click "Add/Remove Snap-in".
c. Click "Add", click "Certificates", click "Add", click "Computer
account",
click "Next", click "Finish", click "Close", and then click "OK".
Also, you may check your SQL Server Service Account. If you run SQL Server
as local system, is this issue occur?
Hope this will be helpful!
Sincerely yours,
Wei Lu
Microsoft Online Partner Support
========================================
==============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
Wednesday, March 7, 2012
I need to create maintenance plans on SQL 2005 without using the wizard
I have several hundred SQl installations I need to change or create a maintenance plan and i don't want to touch every box. I need the step by step process to load the tables myself.
If you want to run the maintenance from a single seat, you could create a set of maintenance tasks in Integration Services, and create multiple connections for them. If you want to have the same plan on multiple servers run from each server, I'd create an Integration Services package again and ship it to the other servers. Use (local) as the connection string, assuming the same account can access each server.
Buck Woody
http://www.buckwoody.com
|||It sounds like you're already familiar with maintenance plans in SQL 2K5, but just in case you're not:
http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=33&rl=1
Again, if you're a pro on this, my apologies.
Buck Woody
|||Thanks! Thought about the distribution of a services package but that doesn't initilize the maintenance folder in th SQL Enterprise tree. I know that sounds trivial but I got to follow standards.|||If this answers the question, you can mark it "answered". If you need anything else, just let us know!Buck Woody|||Just in case you're interested in the process, you can import and export you maintenance plans. You can right click on one of your maintenance plans and then select import or export. Export from one, import to the other.
You can also "pull" your maintenance plan to another server. To do this, on the target server connect to Integration Services on the server where you created your original maintenance plan. Then go to Stored Packages - MSDB - Maintenance Plans. Right click on Maintenance Plans and then select Import.
Buck
|||Thanks
Subscribe to:
Posts (Atom)