Prev: SQL 2005 Oddities
Next: Report Services KPI
From: childofthe1980s on 10 Aug 2010 07:14
Hello:

The weekly maintenance plan that runs every week on Sunday morning in SQL
2005 failed for the first time in two years. The SQL error log stated:
"Problems
with the query, "ResultSet" property not set correctly, parameters not set
correctly, or connection not established correctly."

Any ideas?

childofthe1980s
From: John Bell on 10 Aug 2010 15:04
On Tue, 10 Aug 2010 04:14:03 -0700, childofthe1980s
<childofthe1980s(a)discussions.microsoft.com> wrote:

>Hello:
>
>The weekly maintenance plan that runs every week on Sunday morning in SQL
>2005 failed for the first time in two years. The SQL error log stated:
>"Problems
>with the query, "ResultSet" property not set correctly, parameters not set
>correctly, or connection not established correctly."
>
>Any ideas?
>
>childofthe1980s

I google this and it seems that tis is a bit of a generic error
indicating there was some erro that the application has not handled
too well. It could be a dll was unregisters or possibly spurious data
returned.

Try ruinning the maintenance package manually or using BIDS to see if
more information is given, also check the SQL Server and Windows event
logs.

If that doesn't work try creating a similar plan and running that.

John
From: Jeffrey Williams on 10 Aug 2010 22:22
Instead of looking at the job history, right-click on the maintenance plan
and view the maintenance plan history. This will tell you which task
failed. At the bottom, there will be a text box with more information. To
see all of the message - copy/paste all of the text in that box to notepad
(or your favorite text editor).

Jeff

"John Bell" <jbellnewsposts(a)hotmail.com> wrote in message
news:3e8366d7g671a43tmetu2jgqk806pselpp(a)4ax.com...
> On Tue, 10 Aug 2010 04:14:03 -0700, childofthe1980s
> <childofthe1980s(a)discussions.microsoft.com> wrote:
>
>>Hello:
>>
>>The weekly maintenance plan that runs every week on Sunday morning in SQL
>>2005 failed for the first time in two years. The SQL error log stated:
>>"Problems
>>with the query, "ResultSet" property not set correctly, parameters not set
>>correctly, or connection not established correctly."
>>
>>Any ideas?
>>
>>childofthe1980s
>
> I google this and it seems that tis is a bit of a generic error
> indicating there was some erro that the application has not handled
> too well. It could be a dll was unregisters or possibly spurious data
> returned.
>
> Try ruinning the maintenance package manually or using BIDS to see if
> more information is given, also check the SQL Server and Windows event
> logs.
>
> If that doesn't work try creating a similar plan and running that.
>
> John

From: childofthe1980s on 11 Aug 2010 07:26
Thanks, John!

childofthe1980s

"John Bell" wrote:

> On Tue, 10 Aug 2010 04:14:03 -0700, childofthe1980s
> <childofthe1980s(a)discussions.microsoft.com> wrote:
>
> >Hello:
> >
> >The weekly maintenance plan that runs every week on Sunday morning in SQL
> >2005 failed for the first time in two years. The SQL error log stated:
> >"Problems
> >with the query, "ResultSet" property not set correctly, parameters not set
> >correctly, or connection not established correctly."
> >
> >Any ideas?
> >
> >childofthe1980s
>
> I google this and it seems that tis is a bit of a generic error
> indicating there was some erro that the application has not handled
> too well. It could be a dll was unregisters or possibly spurious data
> returned.
>
> Try ruinning the maintenance package manually or using BIDS to see if
> more information is given, also check the SQL Server and Windows event
> logs.
>
> If that doesn't work try creating a similar plan and running that.
>
> John
> .
>
 | 
Pages: 1
Prev: SQL 2005 Oddities
Next: Report Services KPI