I have just updated an existing SQL Server Express server to SQL Server
Developer Edition 9.0.1399. In general this has worked fine, but I cannot
create a Maintenance Plan, either using the Wizard or by using "New
Maintenance Plan..." The latter brings up a dialog saying that:

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.

while the SQL Server log says:

Error: 17828, Severity: 20, State: 3.
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>]

Hi Richard

i would upgrade to sp2 and try to create a MP again.

MMD

"Richard Lanyon" <Richard Lanyon@discussions.microsoft.com> wrote in message
news:0BD1D0B2-F160-4CB0-8668-FAE3618DBDB2@microsoft.com...
>I have just updated an existing SQL Server Express server to SQL Server
> Developer Edition 9.0.1399. In general this has worked fine, but I cannot
> create a Maintenance Plan, either using the Wizard or by using "New
> Maintenance Plan..." The latter brings up a dialog saying that:
>
> 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.
>
> while the SQL Server log says:
>
> Error: 17828, Severity: 20, State: 3.
> 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>]

Hi Richard

i would upgrade to sp2 and try to create a MP again.

MMD

"Richard Lanyon" <Richard Lanyon@discussions.microsoft.com> wrote in message
news:0BD1D0B2-F160-4CB0-8668-FAE3618DBDB2@microsoft.com...
>I have just updated an existing SQL Server Express server to SQL Server
> Developer Edition 9.0.1399. In general this has worked fine, but I cannot
> create a Maintenance Plan, either using the Wizard or by using "New
> Maintenance Plan..." The latter brings up a dialog saying that:
>
> 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.
>
> while the SQL Server log says:
>
> Error: 17828, Severity: 20, State: 3.
> 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>]

"MMD" wrote:

> i would upgrade to sp2 and try to create a MP again.

Thanks for the suggestion, but the database machine in this case is already
running XP Professional SP3 (actually it was upgraded to SP3 at the same time
as I upgraded the database).

Hi Richard

i was talking about upgrading the database engine wich is on build 9.00.1399
(RTM); when you install Sp2 for Sql Server 2005 the build is upgraded to
9.00.3054

Regards
MMD


"Richard Lanyon" <RichardLanyon@discussions.microsoft.com> wrote in message
news:19F03698-F79B-44A2-8AB7-C9973C8804DC@microsoft.com...
> "MMD" wrote:
>
>> i would upgrade to sp2 and try to create a MP again.
>
> Thanks for the suggestion, but the database machine in this case is
> already
> running XP Professional SP3 (actually it was upgraded to SP3 at the same
> time
> as I upgraded the database).

Ah, I'd not realised there was a separate SQL Server service pack (for some
reason I assumed Windows Update would have told me). Many thanks for this -
it appears to be working now!

Cheers,

Richard

"MMD" wrote:

> Hi Richard
>
> i was talking about upgrading the database engine wich is on build 9.00.1399
> (RTM); when you install Sp2 for Sql Server 2005 the build is upgraded to
> 9.00.3054
>
> Regards
> MMD
>
>
> "Richard Lanyon" <RichardLanyon@discussions.microsoft.com> wrote in message
> news:19F03698-F79B-44A2-8AB7-C9973C8804DC@microsoft.com...
> > "MMD" wrote:
> >
> >> i would upgrade to sp2 and try to create a MP again.
> >
> > Thanks for the suggestion, but the database machine in this case is
> > already
> > running XP Professional SP3 (actually it was upgraded to SP3 at the same
> > time
> > as I upgraded the database).
>
>
>