Error 15457

I recently set up a maintenance plan using the MS SQL
Maintenance plan wizard. Every thing seems to be working
fine with one exception I keep getting the following error:
"Error 15457, Severity 0, Configuration option '%ls'
changed from %ld to %ld. Run the RECONFIGURE statement to
install"
Does anyone know how to solver this?It's not a "real" error, since the severity is 0. It's safe to ignore it.
It's just a PITA.
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"john Schuster" <schuster@.llnl.gov> wrote in message
news:2277b01c45d4f$190760d0$a101280a@.phx
.gbl...
I recently set up a maintenance plan using the MS SQL
Maintenance plan wizard. Every thing seems to be working
fine with one exception I keep getting the following error:
"Error 15457, Severity 0, Configuration option '%ls'
changed from %ld to %ld. Run the RECONFIGURE statement to
install"
Does anyone know how to solver this?

Error 15457

I recently set up a maintenance plan using the MS SQL
Maintenance plan wizard. Every thing seems to be working
fine with one exception I keep getting the following error:
"Error 15457, Severity 0, Configuration option '%ls'
changed from %ld to %ld. Run the RECONFIGURE statement to
install"
Does anyone know how to solver this?It's not a "real" error, since the severity is 0. It's safe to ignore it.
It's just a PITA.
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"john Schuster" <schuster@.llnl.gov> wrote in message
news:2277b01c45d4f$190760d0$a101280a@.phx.gbl...
I recently set up a maintenance plan using the MS SQL
Maintenance plan wizard. Every thing seems to be working
fine with one exception I keep getting the following error:
"Error 15457, Severity 0, Configuration option '%ls'
changed from %ld to %ld. Run the RECONFIGURE statement to
install"
Does anyone know how to solver this?

Error 15457

I recently set up a maintenance plan using the MS SQL
Maintenance plan wizard. Every thing seems to be working
fine with one exception I keep getting the following error:
"Error 15457, Severity 0, Configuration option '%ls'
changed from %ld to %ld. Run the RECONFIGURE statement to
install"
Does anyone know how to solver this?
It's not a "real" error, since the severity is 0. It's safe to ignore it.
It's just a PITA.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"john Schuster" <schuster@.llnl.gov> wrote in message
news:2277b01c45d4f$190760d0$a101280a@.phx.gbl...
I recently set up a maintenance plan using the MS SQL
Maintenance plan wizard. Every thing seems to be working
fine with one exception I keep getting the following error:
"Error 15457, Severity 0, Configuration option '%ls'
changed from %ld to %ld. Run the RECONFIGURE statement to
install"
Does anyone know how to solver this?
|||It's not a "real" error, since the severity is 0. It's safe to ignore it.
It's just a PITA.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"john Schuster" <schuster@.llnl.gov> wrote in message
news:2277b01c45d4f$190760d0$a101280a@.phx.gbl...
I recently set up a maintenance plan using the MS SQL
Maintenance plan wizard. Every thing seems to be working
fine with one exception I keep getting the following error:
"Error 15457, Severity 0, Configuration option '%ls'
changed from %ld to %ld. Run the RECONFIGURE statement to
install"
Does anyone know how to solver this?

error 14269

Hi
When i am changing the owner which is the default owner
for SQL Agent Job, I am getting error as
Error 14269: Job 'DB Maintenance Plan ' ia already
targteted at server xxxxxxx.
The jobs are failing becuase of other user created the
jobs.
Thanks,
John.Have you renamed this server? I'd check the value of the
originating_server in msdb..sysjobs to make sure it's
correct.
-Sue
On Wed, 5 Nov 2003 07:04:28 -0800, "John"
<anonymous@.discussions.microsoft.com> wrote:
>Hi
>When i am changing the owner which is the default owner
>for SQL Agent Job, I am getting error as
>Error 14269: Job 'DB Maintenance Plan ' ia already
>targteted at server xxxxxxx.
>The jobs are failing becuase of other user created the
>jobs.
>Thanks,
>John.

Error 14258 SqlServerAgent is Starting

I am running SQL Server 2000. I was trying to implement a Database Maintence Plan to do the reorgznize data and index pages on database 'MYDB' and received the following error:
Error 14258: CAnnot perform this operation while SQLServerAgent is starting. Try again later...
I checked the SQLAGENT.OUT file and it stated:
[393] Waiting for SQL Server to recover databases...
I also checked the ERRORLOG and all databases but didn't see any error message except:
.....
14304 transactions rolled forward in database 'MYDB' (7).
2004-06-29 14:40:12.17 spid11 0 transactions rolled back in database 'MYDB' (7).
2004-06-29 14:40:12.20 spid11 Recovery is checkpointing database 'MYDB' (7)
2004-06-29 14:42:17.98 spid52 Using 'xpstar.dll' version '2000.80.760' to execute extended stored procedure 'sp_MSgetversion'.
The 'MYDB' is one of the main databases and I did bounce the SQL Server prior because of some run aways processes.
How can I fix this problem? Please advise.Hi, Ling
Is your SQL Server running "lightweight pooling" mode and DTC service is started ?
If yes, it is the problem. see KB-Q303287
Johnny|||Thanks, Johnny. I finally reboot the machine and that fixed the problem. Thanks!|||Does anyone know of any way to successfully have DTC running AND have lightweight pooling on, or are the two mutually exclusive?
Also, would there really be that big of a performance difference between thread or fiber mode on a box with 3 processors?
Thanks for any help.
Kristy
--
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.|||You can have erratic problems when using DTC and fiber mode
which is why it's strongly recommended to use thread mode if
you need to have DTC running. See the following:
BUG: DTC Transactions May Fail When SQL Server Is Running in
Lightweight Pooling Mode
http://support.microsoft.com/?id=303287
In terms of the differences, fiber mode is rarely needed and
can cause a lot of problems. It's not necessarily a good
idea to just automatically switch to fiber and assume you
will get better performance. In the rare situations where
you would turn it on, it won't make that much of a
performance difference. See the following for more
information on the setting:
How to determine proper SQL Server configuration settings
http://support.microsoft.com/?id=319942
-Sue
On Mon, 22 Nov 2004 08:21:39 -0800, SqlJunkies User
<User@.-NOSPAM-SqlJunkies.com> wrote:
>Does anyone know of any way to successfully have DTC running AND have lightweight pooling on, or are the two mutually exclusive?
>Also, would there really be that big of a performance difference between thread or fiber mode on a box with 3 processors?
>Thanks for any help.
>Kristy
>--
>Posted using Wimdows.net NntpNews Component -
>Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.

Error 14258 SqlServerAgent is Starting

I am running SQL Server 2000. I was trying to implement a Database Maintenc
e Plan to do the reorgznize data and index pages on database 'MYDB' and rec
eived the following error:
Error 14258: CAnnot perform this operation while SQLServerAgent is starting.
Try again later...
I checked the SQLAGENT.OUT file and it stated:
[393] Waiting for SQL Server to recover databases...
I also checked the ERRORLOG and all databases but didn't see any error messa
ge except:
.....
14304 transactions rolled forward in database 'MYDB' (7).
2004-06-29 14:40:12.17 spid11 0 transactions rolled back in database 'MYD
B' (7).
2004-06-29 14:40:12.20 spid11 Recovery is checkpointing database 'MYDB' (
7)
2004-06-29 14:42:17.98 spid52 Using 'xpstar.dll' version '2000.80.760' to
execute extended stored procedure 'sp_MSgetversion'.
The 'MYDB' is one of the main databases and I did bounce the SQL Server prio
r because of some run aways processes.
How can I fix this problem? Please advise.Hi, Ling
Is your SQL Server running "lightweight pooling" mode and DTC service is st
arted ?
If yes, it is the problem. see KB-Q303287
Johnny|||Thanks, Johnny. I finally reboot the machine and that fixed the problem. T
hanks!|||Does anyone know of any way to successfully have DTC running AND have lightw
eight pooling on, or are the two mutually exclusive?
Also, would there really be that big of a performance difference between thr
ead or fiber mode on a box with 3 processors?
Thanks for any help.
Kristy
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine sup
ports Post Alerts, Ratings, and Searching.|||You can have erratic problems when using DTC and fiber mode
which is why it's strongly recommended to use thread mode if
you need to have DTC running. See the following:
BUG: DTC Transactions May Fail When SQL Server Is Running in
Lightweight Pooling Mode
http://support.microsoft.com/?id=303287
In terms of the differences, fiber mode is rarely needed and
can cause a lot of problems. It's not necessarily a good
idea to just automatically switch to fiber and assume you
will get better performance. In the rare situations where
you would turn it on, it won't make that much of a
performance difference. See the following for more
information on the setting:
How to determine proper SQL Server configuration settings
http://support.microsoft.com/?id=319942
-Sue
On Mon, 22 Nov 2004 08:21:39 -0800, SqlJunkies User
<User@.-NOSPAM-SqlJunkies.com> wrote:

>Does anyone know of any way to successfully have DTC running AND have light
weight pooling on, or are the two mutually exclusive?
>Also, would there really be that big of a performance difference between th
read or fiber mode on a box with 3 processors?
>Thanks for any help.
>Kristy
>--
>Posted using Wimdows.net NntpNews Component -
>Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports P
ost Alerts, Ratings, and Searching.sql

Error 14258 SqlServerAgent is Starting

I am running SQL Server 2000. I was trying to implement a Database Maintence Plan to do the reorgznize data and index pages on database 'MYDB' and received the following error:
Error 14258: CAnnot perform this operation while SQLServerAgent is starting. Try again later...
I checked the SQLAGENT.OUT file and it stated:
[393] Waiting for SQL Server to recover databases...
I also checked the ERRORLOG and all databases but didn't see any error message except:
......
14304 transactions rolled forward in database 'MYDB' (7).
2004-06-29 14:40:12.17 spid11 0 transactions rolled back in database 'MYDB' (7).
2004-06-29 14:40:12.20 spid11 Recovery is checkpointing database 'MYDB' (7)
2004-06-29 14:42:17.98 spid52 Using 'xpstar.dll' version '2000.80.760' to execute extended stored procedure 'sp_MSgetversion'.
The 'MYDB' is one of the main databases and I did bounce the SQL Server prior because of some run aways processes.
How can I fix this problem? Please advise.
Hi, Ling
Is your SQL Server running "lightweight pooling" mode and DTC service is started ?
If yes, it is the problem. see KB-Q303287
Johnny

Error 14258 SqlServerAgent is Starting

I am running SQL Server 2000. I was trying to implement a Database Maintence Plan to do the reorgznize data and index pages on database 'MYDB' and received the following error:
Error 14258: CAnnot perform this operation while SQLServerAgent is starting. Try again later...
I checked the SQLAGENT.OUT file and it stated:
[393] Waiting for SQL Server to recover databases...
I also checked the ERRORLOG and all databases but didn't see any error message except:
......
14304 transactions rolled forward in database 'MYDB' (7).
2004-06-29 14:40:12.17 spid11 0 transactions rolled back in database 'MYDB' (7).
2004-06-29 14:40:12.20 spid11 Recovery is checkpointing database 'MYDB' (7)
2004-06-29 14:42:17.98 spid52 Using 'xpstar.dll' version '2000.80.760' to execute extended stored procedure 'sp_MSgetversion'.
The 'MYDB' is one of the main databases and I did bounce the SQL Server prior because of some run aways processes.
How can I fix this problem? Please advise.
Hi, Ling
Is your SQL Server running "lightweight pooling" mode and DTC service is started ?
If yes, it is the problem. see KB-Q303287
Johnny
|||Thanks, Johnny. I finally reboot the machine and that fixed the problem. Thanks!
|||Does anyone know of any way to successfully have DTC running AND have lightweight pooling on, or are the two mutually exclusive?
Also, would there really be that big of a performance difference between thread or fiber mode on a box with 3 processors?
Thanks for any help.
Kristy
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
|||You can have erratic problems when using DTC and fiber mode
which is why it's strongly recommended to use thread mode if
you need to have DTC running. See the following:
BUG: DTC Transactions May Fail When SQL Server Is Running in
Lightweight Pooling Mode
http://support.microsoft.com/?id=303287
In terms of the differences, fiber mode is rarely needed and
can cause a lot of problems. It's not necessarily a good
idea to just automatically switch to fiber and assume you
will get better performance. In the rare situations where
you would turn it on, it won't make that much of a
performance difference. See the following for more
information on the setting:
How to determine proper SQL Server configuration settings
http://support.microsoft.com/?id=319942
-Sue
On Mon, 22 Nov 2004 08:21:39 -0800, SqlJunkies User
<User@.-NOSPAM-SqlJunkies.com> wrote:

>Does anyone know of any way to successfully have DTC running AND have lightweight pooling on, or are the two mutually exclusive?
>Also, would there really be that big of a performance difference between thread or fiber mode on a box with 3 processors?
>Thanks for any help.
>Kristy
>--
>Posted using Wimdows.net NntpNews Component -
>Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.

Error 12291 in Event Log

We have a maintainance plan for full/diff/log backups of selected databases
running at regular intervals through SQLAgent. The backups are working; I ca
n
restore the databases. But starting a few weeks ago we've been getting error
messages in the system event log.
First, there's an entry confirming the successful completion of the backups
with ID 18265 (source MSSQL$...)
Then comes the error: ID 12291 "Error in package ..." (source SQLISPackage)
followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
Error ..." (source SQLAgent$...)
As I said, the backups themselves seem to be successful, and the SQL Server
"ERRORLOG" text file also contains no error messages in connection with the
plans.
This is still worrying us a bit, because we fear there might be a good
reason for these error messages, and obviously we want to be quite certain
that our backups are working properly and will be available if and when we
need them.
Does anyone have any insight/advice on Error 12291?
Thanks
Tom JuergensHi Tom,
Since some maintenance plans are very easy to create, have you tried
creating a new or very similar maintenance plan and see if you still have th
e
same problem? Or maybe deleting the existing maintenance plan and creating i
t
again?
Also, since the maintenance plan is an SSIS package, have you tried running
the package manually from SSIS (like using the Execute Package Utility) and
check for errors or warnings? Have you tried Logging on this SSIS package?
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Tom Juergens" wrote:

> We have a maintainance plan for full/diff/log backups of selected database
s
> running at regular intervals through SQLAgent. The backups are working; I
can
> restore the databases. But starting a few weeks ago we've been getting err
or
> messages in the system event log.
> First, there's an entry confirming the successful completion of the backup
s
> with ID 18265 (source MSSQL$...)
> Then comes the error: ID 12291 "Error in package ..." (source SQLISPackage
)
> followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
> Error ..." (source SQLAgent$...)
> As I said, the backups themselves seem to be successful, and the SQL Serve
r
> "ERRORLOG" text file also contains no error messages in connection with th
e
> plans.
> This is still worrying us a bit, because we fear there might be a good
> reason for these error messages, and obviously we want to be quite certain
> that our backups are working properly and will be available if and when we
> need them.
> Does anyone have any insight/advice on Error 12291?
> Thanks
> Tom Juergens|||You would need to post the whole log to get a full analysis. The plan should
be generating a log file, not the error log, which may help. If not,
configure it to generate a detailed log.
Also check the package has no reference to mapped drives as the mappings may
not be available to SQL Agent.
Nigel Ainscoe
"Tom Juergens" <antaeus@.newsgroup.nospam> wrote in message
news:9A9C2F9C-A3E6-4131-9BC8-16196C1E6733@.microsoft.com...
> We have a maintainance plan for full/diff/log backups of selected
> databases
> running at regular intervals through SQLAgent. The backups are working; I
> can
> restore the databases. But starting a few weeks ago we've been getting
> error
> messages in the system event log.
> First, there's an entry confirming the successful completion of the
> backups
> with ID 18265 (source MSSQL$...)
> Then comes the error: ID 12291 "Error in package ..." (source
> SQLISPackage)
> followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
> Error ..." (source SQLAgent$...)
> As I said, the backups themselves seem to be successful, and the SQL
> Server
> "ERRORLOG" text file also contains no error messages in connection with
> the
> plans.
> This is still worrying us a bit, because we fear there might be a good
> reason for these error messages, and obviously we want to be quite certain
> that our backups are working properly and will be available if and when we
> need them.
> Does anyone have any insight/advice on Error 12291?
> Thanks
> Tom Juergens|||Thanks to you both for the pointers and good ideas. I'll try your suggestion
s
and post again here if I don't find a solution.
Tom
"Ben Nevarez" wrote:
[vbcol=seagreen]
> Hi Tom,
> Since some maintenance plans are very easy to create, have you tried
> creating a new or very similar maintenance plan and see if you still have
the
> same problem? Or maybe deleting the existing maintenance plan and creating
it
> again?
> Also, since the maintenance plan is an SSIS package, have you tried runnin
g
> the package manually from SSIS (like using the Execute Package Utility) an
d
> check for errors or warnings? Have you tried Logging on this SSIS package?
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Tom Juergens" wrote:
>|||Hi Tom,
To let us better understand your issue, could you please let us know the
following questions:
1. What is the version of your SQL Server? (Run SELECT @.@.VERSION.)
2. Did the maintainance plan only backup your databases?
3. Could you please post all the event error messages here for more
effective research? You may also mail me (changliw_at_microsoft_dot_com)
the event error logs.
Best regards,
Charles Wang
Microsoft Online Community Support
========================================
==============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============|||My client has decided to reinstall the server, which is a good option since
there are some other things that aren't quite right as well... So we just
have to live with this behavior for another couple of weeks and I won't be
investing much more time in finding a solution. Consider this case closed.
Thanks
Tom
"Charles Wang[MSFT]" wrote:

> Hi Tom,
> To let us better understand your issue, could you please let us know the
> following questions:
> 1. What is the version of your SQL Server? (Run SELECT @.@.VERSION.)
> 2. Did the maintainance plan only backup your databases?
> 3. Could you please post all the event error messages here for more
> effective research? You may also mail me (changliw_at_microsoft_dot_com)
> the event error logs.
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ========================================
==============
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ========================================
==============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> ========================================
==============
>
>
>

Error 12291 in Event Log

We have a maintainance plan for full/diff/log backups of selected databases
running at regular intervals through SQLAgent. The backups are working; I can
restore the databases. But starting a few weeks ago we've been getting error
messages in the system event log.
First, there's an entry confirming the successful completion of the backups
with ID 18265 (source MSSQL$...)
Then comes the error: ID 12291 "Error in package ..." (source SQLISPackage)
followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
Error ..." (source SQLAgent$...)
As I said, the backups themselves seem to be successful, and the SQL Server
"ERRORLOG" text file also contains no error messages in connection with the
plans.
This is still worrying us a bit, because we fear there might be a good
reason for these error messages, and obviously we want to be quite certain
that our backups are working properly and will be available if and when we
need them.
Does anyone have any insight/advice on Error 12291?
Thanks
Tom JuergensHi Tom,
Since some maintenance plans are very easy to create, have you tried
creating a new or very similar maintenance plan and see if you still have the
same problem? Or maybe deleting the existing maintenance plan and creating it
again?
Also, since the maintenance plan is an SSIS package, have you tried running
the package manually from SSIS (like using the Execute Package Utility) and
check for errors or warnings? Have you tried Logging on this SSIS package?
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Tom Juergens" wrote:
> We have a maintainance plan for full/diff/log backups of selected databases
> running at regular intervals through SQLAgent. The backups are working; I can
> restore the databases. But starting a few weeks ago we've been getting error
> messages in the system event log.
> First, there's an entry confirming the successful completion of the backups
> with ID 18265 (source MSSQL$...)
> Then comes the error: ID 12291 "Error in package ..." (source SQLISPackage)
> followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
> Error ..." (source SQLAgent$...)
> As I said, the backups themselves seem to be successful, and the SQL Server
> "ERRORLOG" text file also contains no error messages in connection with the
> plans.
> This is still worrying us a bit, because we fear there might be a good
> reason for these error messages, and obviously we want to be quite certain
> that our backups are working properly and will be available if and when we
> need them.
> Does anyone have any insight/advice on Error 12291?
> Thanks
> Tom Juergens|||You would need to post the whole log to get a full analysis. The plan should
be generating a log file, not the error log, which may help. If not,
configure it to generate a detailed log.
Also check the package has no reference to mapped drives as the mappings may
not be available to SQL Agent.
Nigel Ainscoe
"Tom Juergens" <antaeus@.newsgroup.nospam> wrote in message
news:9A9C2F9C-A3E6-4131-9BC8-16196C1E6733@.microsoft.com...
> We have a maintainance plan for full/diff/log backups of selected
> databases
> running at regular intervals through SQLAgent. The backups are working; I
> can
> restore the databases. But starting a few weeks ago we've been getting
> error
> messages in the system event log.
> First, there's an entry confirming the successful completion of the
> backups
> with ID 18265 (source MSSQL$...)
> Then comes the error: ID 12291 "Error in package ..." (source
> SQLISPackage)
> followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
> Error ..." (source SQLAgent$...)
> As I said, the backups themselves seem to be successful, and the SQL
> Server
> "ERRORLOG" text file also contains no error messages in connection with
> the
> plans.
> This is still worrying us a bit, because we fear there might be a good
> reason for these error messages, and obviously we want to be quite certain
> that our backups are working properly and will be available if and when we
> need them.
> Does anyone have any insight/advice on Error 12291?
> Thanks
> Tom Juergens|||Thanks to you both for the pointers and good ideas. I'll try your suggestions
and post again here if I don't find a solution.
Tom
"Ben Nevarez" wrote:
> Hi Tom,
> Since some maintenance plans are very easy to create, have you tried
> creating a new or very similar maintenance plan and see if you still have the
> same problem? Or maybe deleting the existing maintenance plan and creating it
> again?
> Also, since the maintenance plan is an SSIS package, have you tried running
> the package manually from SSIS (like using the Execute Package Utility) and
> check for errors or warnings? Have you tried Logging on this SSIS package?
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Tom Juergens" wrote:
> > We have a maintainance plan for full/diff/log backups of selected databases
> > running at regular intervals through SQLAgent. The backups are working; I can
> > restore the databases. But starting a few weeks ago we've been getting error
> > messages in the system event log.
> >
> > First, there's an entry confirming the successful completion of the backups
> > with ID 18265 (source MSSQL$...)
> > Then comes the error: ID 12291 "Error in package ..." (source SQLISPackage)
> > followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
> > Error ..." (source SQLAgent$...)
> >
> > As I said, the backups themselves seem to be successful, and the SQL Server
> > "ERRORLOG" text file also contains no error messages in connection with the
> > plans.
> >
> > This is still worrying us a bit, because we fear there might be a good
> > reason for these error messages, and obviously we want to be quite certain
> > that our backups are working properly and will be available if and when we
> > need them.
> >
> > Does anyone have any insight/advice on Error 12291?
> >
> > Thanks
> > Tom Juergens|||Hi Tom,
To let us better understand your issue, could you please let us know the
following questions:
1. What is the version of your SQL Server? (Run SELECT @.@.VERSION.)
2. Did the maintainance plan only backup your databases?
3. Could you please post all the event error messages here for more
effective research? You may also mail me (changliw_at_microsoft_dot_com)
the event error logs.
Best regards,
Charles Wang
Microsoft Online Community Support
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||My client has decided to reinstall the server, which is a good option since
there are some other things that aren't quite right as well... So we just
have to live with this behavior for another couple of weeks and I won't be
investing much more time in finding a solution. Consider this case closed.
Thanks
Tom
"Charles Wang[MSFT]" wrote:
> Hi Tom,
> To let us better understand your issue, could you please let us know the
> following questions:
> 1. What is the version of your SQL Server? (Run SELECT @.@.VERSION.)
> 2. Did the maintainance plan only backup your databases?
> 3. Could you please post all the event error messages here for more
> effective research? You may also mail me (changliw_at_microsoft_dot_com)
> the event error logs.
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ======================================================> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ======================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
> ======================================================>
>
>

Error 12291 in Event Log

We have a maintainance plan for full/diff/log backups of selected databases
running at regular intervals through SQLAgent. The backups are working; I can
restore the databases. But starting a few weeks ago we've been getting error
messages in the system event log.
First, there's an entry confirming the successful completion of the backups
with ID 18265 (source MSSQL$...)
Then comes the error: ID 12291 "Error in package ..." (source SQLISPackage)
followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
Error ..." (source SQLAgent$...)
As I said, the backups themselves seem to be successful, and the SQL Server
"ERRORLOG" text file also contains no error messages in connection with the
plans.
This is still worrying us a bit, because we fear there might be a good
reason for these error messages, and obviously we want to be quite certain
that our backups are working properly and will be available if and when we
need them.
Does anyone have any insight/advice on Error 12291?
Thanks
Tom Juergens
Hi Tom,
Since some maintenance plans are very easy to create, have you tried
creating a new or very similar maintenance plan and see if you still have the
same problem? Or maybe deleting the existing maintenance plan and creating it
again?
Also, since the maintenance plan is an SSIS package, have you tried running
the package manually from SSIS (like using the Execute Package Utility) and
check for errors or warnings? Have you tried Logging on this SSIS package?
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Tom Juergens" wrote:

> We have a maintainance plan for full/diff/log backups of selected databases
> running at regular intervals through SQLAgent. The backups are working; I can
> restore the databases. But starting a few weeks ago we've been getting error
> messages in the system event log.
> First, there's an entry confirming the successful completion of the backups
> with ID 18265 (source MSSQL$...)
> Then comes the error: ID 12291 "Error in package ..." (source SQLISPackage)
> followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
> Error ..." (source SQLAgent$...)
> As I said, the backups themselves seem to be successful, and the SQL Server
> "ERRORLOG" text file also contains no error messages in connection with the
> plans.
> This is still worrying us a bit, because we fear there might be a good
> reason for these error messages, and obviously we want to be quite certain
> that our backups are working properly and will be available if and when we
> need them.
> Does anyone have any insight/advice on Error 12291?
> Thanks
> Tom Juergens
|||You would need to post the whole log to get a full analysis. The plan should
be generating a log file, not the error log, which may help. If not,
configure it to generate a detailed log.
Also check the package has no reference to mapped drives as the mappings may
not be available to SQL Agent.
Nigel Ainscoe
"Tom Juergens" <antaeus@.newsgroup.nospam> wrote in message
news:9A9C2F9C-A3E6-4131-9BC8-16196C1E6733@.microsoft.com...
> We have a maintainance plan for full/diff/log backups of selected
> databases
> running at regular intervals through SQLAgent. The backups are working; I
> can
> restore the databases. But starting a few weeks ago we've been getting
> error
> messages in the system event log.
> First, there's an entry confirming the successful completion of the
> backups
> with ID 18265 (source MSSQL$...)
> Then comes the error: ID 12291 "Error in package ..." (source
> SQLISPackage)
> followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
> Error ..." (source SQLAgent$...)
> As I said, the backups themselves seem to be successful, and the SQL
> Server
> "ERRORLOG" text file also contains no error messages in connection with
> the
> plans.
> This is still worrying us a bit, because we fear there might be a good
> reason for these error messages, and obviously we want to be quite certain
> that our backups are working properly and will be available if and when we
> need them.
> Does anyone have any insight/advice on Error 12291?
> Thanks
> Tom Juergens
|||Thanks to you both for the pointers and good ideas. I'll try your suggestions
and post again here if I don't find a solution.
Tom
"Ben Nevarez" wrote:
[vbcol=seagreen]
> Hi Tom,
> Since some maintenance plans are very easy to create, have you tried
> creating a new or very similar maintenance plan and see if you still have the
> same problem? Or maybe deleting the existing maintenance plan and creating it
> again?
> Also, since the maintenance plan is an SSIS package, have you tried running
> the package manually from SSIS (like using the Execute Package Utility) and
> check for errors or warnings? Have you tried Logging on this SSIS package?
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Tom Juergens" wrote:
|||Hi Tom,
To let us better understand your issue, could you please let us know the
following questions:
1. What is the version of your SQL Server? (Run SELECT @.@.VERSION.)
2. Did the maintainance plan only backup your databases?
3. Could you please post all the event error messages here for more
effective research? You may also mail me (changliw_at_microsoft_dot_com)
the event error logs.
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||My client has decided to reinstall the server, which is a good option since
there are some other things that aren't quite right as well... So we just
have to live with this behavior for another couple of weeks and I won't be
investing much more time in finding a solution. Consider this case closed.
Thanks
Tom
"Charles Wang[MSFT]" wrote:

> Hi Tom,
> To let us better understand your issue, could you please let us know the
> following questions:
> 1. What is the version of your SQL Server? (Run SELECT @.@.VERSION.)
> 2. Did the maintainance plan only backup your databases?
> 3. Could you please post all the event error messages here for more
> effective research? You may also mail me (changliw_at_microsoft_dot_com)
> the event error logs.
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ================================================== ====
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ================================================== ====
> This posting is provided "AS IS" with no warranties, and confers no rights.
> ================================================== ====
>
>
>

Error 1105: 'PRIMARY' filegroup is full

I get the following error when attempting to run the
Database Maintenance Plan Optimization job for a database:
Rebuilding indexes for table 'WebLog'
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1105:
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not
allocate space for object '(SYSTEM table id: -933813458)'
in database 'svc2000WebLog' because the 'PRIMARY'
filegroup is full.
I am running SQL Server 2000 (SP3) on a Windows 2000 (SP4)
machine. There is plenty of disk space on the server. Do
I need to expand the database before running this job?SQL Server need working space in the db for DBCC DBREINDEX. Also, autogrow
doesn't catch up in some situations. See below. Consider pre-allocating
storage or using DBCC INDEXDEFRAG instead.
http://support.microsoft.com/default.aspx?scid=kb;en-us;305635
--
Tibor Karaszi
"Tom Griffin" <griffin@.co.santa-barbara.ca.us> wrote in message
news:042601c3a23d$5e190a70$a301280a@.phx.gbl...
> I get the following error when attempting to run the
> Database Maintenance Plan Optimization job for a database:
> Rebuilding indexes for table 'WebLog'
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1105:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Could not
> allocate space for object '(SYSTEM table id: -933813458)'
> in database 'svc2000WebLog' because the 'PRIMARY'
> filegroup is full.
> I am running SQL Server 2000 (SP3) on a Windows 2000 (SP4)
> machine. There is plenty of disk space on the server. Do
> I need to expand the database before running this job?
>

Error

I tryed to execute the maintenace plan, but it failed... the second time I
tryed to execute it it gave me this error message:
Execute Maintenance Plan
An exception occured while executing a Transact-SQL statement or batch
(Microsoft.SqlServer.ConnectInfo)
SqlServerAgent Error: Request to run job backup_db (from <domain>\Jeff)
refused because the job is already running from a request by User
<domain>\Jeff (Microsft Sql Server, Error 22022)
I'm not sure how the first error message was (I tryed to execute the
maintenance plan twice)...
strange if I should get an error that the job is already running...
well, maybe it was caused by my user account, which not a member of the
local administrator on that server, but I'm a member of the administrators
in the domain
any suggestions?Hi
Did you try to execute the job or the maintenance plan? If you look at the
view history of the plan it may have something in for the last run, if it is
still running then it would be incomplete information.
John
"Jeff" wrote:

> I tryed to execute the maintenace plan, but it failed... the second time I
> tryed to execute it it gave me this error message:
> Execute Maintenance Plan
> An exception occured while executing a Transact-SQL statement or batch
> (Microsoft.SqlServer.ConnectInfo)
> SqlServerAgent Error: Request to run job backup_db (from <domain>\Jeff)
> refused because the job is already running from a request by User
> <domain>\Jeff (Microsft Sql Server, Error 22022)
> I'm not sure how the first error message was (I tryed to execute the
> maintenance plan twice)...
> strange if I should get an error that the job is already running...
> well, maybe it was caused by my user account, which not a member of the
> local administrator on that server, but I'm a member of the administrators
> in the domain
> any suggestions?
>
>|||It fails because as the error message refers it's already running. You
should check the history for any detailed error messages about the running
job if there is any.
Ekrem nsoy
"Jeff" <donot@.spam.me> wrote in message
news:enncutLQIHA.5184@.TK2MSFTNGP05.phx.gbl...
>I tryed to execute the maintenace plan, but it failed... the second time I
>tryed to execute it it gave me this error message:
> Execute Maintenance Plan
> An exception occured while executing a Transact-SQL statement or batch
> (Microsoft.SqlServer.ConnectInfo)
> SqlServerAgent Error: Request to run job backup_db (from <domain>\Jeff)
> refused because the job is already running from a request by User
> <domain>\Jeff (Microsft Sql Server, Error 22022)
> I'm not sure how the first error message was (I tryed to execute the
> maintenance plan twice)...
> strange if I should get an error that the job is already running...
> well, maybe it was caused by my user account, which not a member of the
> local administrator on that server, but I'm a member of the administrators
> in the domain
> any suggestions?
>

Error

When attempting to adjust the maitenance plan on one of my SQL Servers I get
the followign error message after adjusting how long logs and reports are
kept.
Microsoft SQL - DMO (ODBC SQLState: 42000)
Error 8114: Error converting data type int to tinyint.
What does all this mean?Hi George,
Welcome to use MSDN Managed Newsgroup!
From your descriptions, I understood you encounter the error message "Error
converting data type int to tinyint" when re-saving the maintenance plan.
If I have misunderstood your concern, please feel free to point it out.
Yes, this is a known issue when you tried to edit an existing maintenance
plan in MSDE and then click on "Apply" button or "OK" button. You may work
around with the method below
1) Add the BackupDirectory registry value for the instance SQL server in
registry, you will be able to re-save and edit the maintenance job without
problem.
For example, (if you have a named instance), put it in
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\<instance name>\MSSQLServer.
The String value is "BackupDirectory" and the data value is "C:\Program
Files\Microsoft SQL Server\MSSQL$nameinstance\BACKUP"
- or -
2) Delete the original existing maint plan and re-create a new one with
your desired changes.
Sincerely yours,
Michael Cheng
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.|||On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> On Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
>
>
>
>
>
>
> Hi
> Are you running DTSRun from a command prompt?
> Why are you using a DSN?
> Have you tried creating the package using the Import Wizard?
> John
I am trying to run the schedule the package from using .xp_cmdshell
and DTSRun , The package will run if execute it from Enterprise Manager|||On Jun 11, 6:20 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
> I am trying to run the schedule the package from using .xp_cmdshell
> and DTSRun , The package will run if execute it from Enterprise Manager- H
ide quoted text -
> - Show quoted text -
Hi
If you manually run the command from a command prompt does it work?
If xp_cmdshell is running from a job, then make sure service accounts
have access to the directory/file.
John|||On Jun 11, 1:30 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> On Jun 11, 6:20 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Hi
> If you manually run the command from a command prompt does it work?
> If xp_cmdshell is running from a job, then make sure service accounts
> have access to the directory/file.
> John
Thanks, If I manually run the command from the command prompt it does
work, however if I try and run using xp_cmdshell I receive the error.
Both SQLAgent and MSSQL services have access to the directory/file|||When you are running it from EM, the package will use your logon to
determine the right and security to access a file but this will not be the
case when running it from a service (xp_cmdshell, DTS_Run or any other
service like SQL-Agent).
Also, if you are not using a UNC pathway but a drive letter (such as C:\);
many of these drive letters will be unknown to system accounts and other
accounts other than your own login. If you have used a driver letter, you
should replace with its full UNC name.
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)
<mtatlow@.gmail.com> wrote in message
news:1181582401.465253.261890@.w5g2000hsg.googlegroups.com...
> On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> I am trying to run the schedule the package from using .xp_cmdshell
> and DTSRun , The package will run if execute it from Enterprise Manager
>|||On Jun 11, 9:20 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> On Jun 11, 1:30 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Thanks, If I manually run the command from the command prompt it does
> work, however if I try and run using xp_cmdshell I receive the error.
> Both SQLAgent and MSSQL services have access to the directory/file- Hide q
uoted text -
> - Show quoted text -
Hi
You don't say what the service accounts are. The LOCALSYSTEM will not
have access to network resources, so it would have to be a domain
account. Try logging in as this account and run the package from the
command prompt.
John|||I am using a domain account that has access to the file. I am using
the [ODBC Text Driver] which does not allow you to use a UNC in the
pathway.
On Jun 11, 5:36 pm, "Sylvain Lafontaine" <sylvain aei ca (fill the
blanks, no spam please)> wrote:[vbcol=seagreen]
> When you are running it from EM, the package will use your logon to
> determine the right and security to access a file but this will not be the
> case when running it from a service (xp_cmdshell, DTS_Run or any other
> service like SQL-Agent).
> Also, if you are not using a UNC pathway but a drive letter (such as C:\);
> many of these drive letters will be unknown to system accounts and other
> accounts other than your own login. If you have used a driver letter, you
> should replace with its full UNC name.
> --
> Sylvain Lafontaine, ing.
> MVP - Technologies Virtual-PC
> E-mail: sylvain aei ca (fill the blanks, no spam please)
> <mtat...@.gmail.com> wrote in message
> news:1181582401.465253.261890@.w5g2000hsg.googlegroups.com...
>
>
>
>
>
>
>
>
>
>
>
>|||On Jun 12, 12:58 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> I am using a domain account that has access to the file. I am using
> the [ODBC Text Driver] which does not allow you to use a UNC in the
> pathway.
> On Jun 11, 5:36 pm, "Sylvain Lafontaine" <sylvain aei ca (fill the
> blanks, no spam please)> wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> - Show quoted text -
Hi
So logging in as this account, you can run the job/package
sucessfully? Have you used the /L command to log output to a file?
John|||On Jun 12, 9:05 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
> On Jun 12, 12:58 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Hi
> So logging in as this account, you can run the job/package
> sucessfully? Have you used the /L command to log output to a file?
> John
This is the output that I get when I use xp_cmdshell
DTSRun: Loading...
DTSRun: Executing...
DTSRun OnStart: DTSStep_DTSDataPumpTask_1
DTSRun OnError: DTSStep_DTSDataPumpTask_1, Error = -2147467259
(80004005)
Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
valid path. Make sure that the path name is spelled correctly and
that you are connected to the server on which the file resides.
Error source: Microsoft OLE DB Provider for ODBC Drivers
Help file:
Help context: 0
Error Detail Records:
Error: -2147467259 (80004005); Provider Error: 1023 (3FF)
Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
valid path. Make sure that the path name is spelled correctly and
that you are connected to the server on which the file resides.
Error source: Microsoft OLE DB Provider for ODBC Drivers
Help file:
Help context: 0
DTSRun OnFinish: DTSStep_DTSDataPumpTask_1
DTSRun: Package execution complete.
NULL
this is the output when I run from the cmd prompt
The execution of the following DTS Package succeeded:
Package Name: test
Package Description: (null)
Package ID: {28220C92-CA63-4664-B356-2155FC002749}
Package Version: {D70556AF-1AE9-4175-83C7-B623FC755314}
Package Execution Lineage: {5DD5E480-8567-43F2-BBAA-7F9F9C9E994D}
Executed On: SERVERNAME
Executed By: username
Execution Started: 6/12/2007 9:31:01 AM
Execution Completed: 6/12/2007 9:31:01 AM
Total Execution Time: 0.64 seconds
Package Steps execution information:
Step 'DTSStep_DTSDataPumpTask_1' succeeded
Step Execution Started: 6/12/2007 9:31:01 AM
Step Execution Completed: 6/12/2007 9:31:01 AM
Total Step Execution Time: 0.593 seconds
Progress count in Step: 1672
****************************************
************************************
************************

Error

When attempting to adjust the maitenance plan on one of my SQL Servers I get
the followign error message after adjusting how long logs and reports are
kept.
Microsoft SQL - DMO (ODBC SQLState: 42000)
Error 8114: Error converting data type int to tinyint.
What does all this mean?Hi George,
Welcome to use MSDN Managed Newsgroup!
From your descriptions, I understood you encounter the error message "Error
converting data type int to tinyint" when re-saving the maintenance plan.
If I have misunderstood your concern, please feel free to point it out.
Yes, this is a known issue when you tried to edit an existing maintenance
plan in MSDE and then click on "Apply" button or "OK" button. You may work
around with the method below
1) Add the BackupDirectory registry value for the instance SQL server in
registry, you will be able to re-save and edit the maintenance job without
problem.
For example, (if you have a named instance), put it in
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\<instance name>\MSSQLServer.
The String value is "BackupDirectory" and the data value is "C:\Program
Files\Microsoft SQL Server\MSSQL$nameinstance\BACKUP"
- or -
2) Delete the original existing maint plan and re-create a new one with
your desired changes.
Sincerely yours,
Michael Cheng
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.

Error

When attempting to adjust the maitenance plan on one of my SQL Servers I get
the followign error message after adjusting how long logs and reports are
kept.
Microsoft SQL - DMO (ODBC SQLState: 42000)
Error 8114: Error converting data type int to tinyint.
What does all this mean?
Hi George,
Welcome to use MSDN Managed Newsgroup!
From your descriptions, I understood you encounter the error message "Error
converting data type int to tinyint" when re-saving the maintenance plan.
If I have misunderstood your concern, please feel free to point it out.
Yes, this is a known issue when you tried to edit an existing maintenance
plan in MSDE and then click on "Apply" button or "OK" button. You may work
around with the method below
1) Add the BackupDirectory registry value for the instance SQL server in
registry, you will be able to re-save and edit the maintenance job without
problem.
For example, (if you have a named instance), put it in
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\<instance name>\MSSQLServer.
The String value is "BackupDirectory" and the data value is "C:\Program
Files\Microsoft SQL Server\MSSQL$nameinstance\BACKUP"
- or -
2) Delete the original existing maint plan and re-create a new one with
your desired changes.
Sincerely yours,
Michael Cheng
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.