error message on backup

When trying to do a backup, I come up with this message.
Backup, CHECKALLOC, bulk copy, SELECT INTO, and file
manipulation (such as CREATE FILE) operations on a
database must be serialized. Reissue the statement after
the current backup, CHECKALLOC, or file manipulation
operation is completed. [SQLSTATE 42000] (Error 3023)
Backup or restore operation terminating abnormally.
[SQLSTATE 42000] (Error 3013). The step failed.
What could be causing this failed job?Read the error message closely. You are trying to execute two operations at
the same time, and those operations aren't allowed to execute at the same
time. Check your job schedules etc.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"SQL'''?" <anonymous@.discussions.microsoft.com> wrote in
message news:368b01c3aa26$9a6deb80$a601280a@.phx.gbl...
> When trying to do a backup, I come up with this message.
> Backup, CHECKALLOC, bulk copy, SELECT INTO, and file
> manipulation (such as CREATE FILE) operations on a
> database must be serialized. Reissue the statement after
> the current backup, CHECKALLOC, or file manipulation
> operation is completed. [SQLSTATE 42000] (Error 3023)
> Backup or restore operation terminating abnormally.
> [SQLSTATE 42000] (Error 3013). The step failed.
> What could be causing this failed job?|||Only one job is running during the schedule. I even
killed every job right now and tried to run the backup,
and it came up with the same message.
>--Original Message--
>Read the error message closely. You are trying to execute
two operations at
>the same time, and those operations aren't allowed to
execute at the same
>time. Check your job schedules etc.
>--
>Tibor Karaszi, SQL Server MVP
>Archive at:
>http://groups.google.com/groups?
oi=djq&as_ugroup=microsoft.public.sqlserver
>
>"SQL'''?"
<anonymous@.discussions.microsoft.com> wrote in
>message news:368b01c3aa26$9a6deb80$a601280a@.phx.gbl...
>> When trying to do a backup, I come up with this message.
>> Backup, CHECKALLOC, bulk copy, SELECT INTO, and file
>> manipulation (such as CREATE FILE) operations on a
>> database must be serialized. Reissue the statement after
>> the current backup, CHECKALLOC, or file manipulation
>> operation is completed. [SQLSTATE 42000] (Error 3023)
>> Backup or restore operation terminating abnormally.
>> [SQLSTATE 42000] (Error 3013). The step failed.
>> What could be causing this failed job?
>
>.
>|||Could be an autogrow or autoshrink. You might have to use Profiler and/or
Performance Monitor to determine where the conflict is. If you can hunt it
down, I suggest you open a case with MS (I assume you have searched KB). One
cannot rule out the possibility of some bug in SQL Server.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
<anonymous@.discussions.microsoft.com> wrote in message
news:02e701c3aa2c$eae205f0$a401280a@.phx.gbl...
> Only one job is running during the schedule. I even
> killed every job right now and tried to run the backup,
> and it came up with the same message.
>
> >--Original Message--
> >Read the error message closely. You are trying to execute
> two operations at
> >the same time, and those operations aren't allowed to
> execute at the same
> >time. Check your job schedules etc.
> >
> >--
> >Tibor Karaszi, SQL Server MVP
> >Archive at:
> >http://groups.google.com/groups?
> oi=djq&as_ugroup=microsoft.public.sqlserver
> >
> >
> >"SQL'''?"
> <anonymous@.discussions.microsoft.com> wrote in
> >message news:368b01c3aa26$9a6deb80$a601280a@.phx.gbl...
> >> When trying to do a backup, I come up with this message.
> >>
> >> Backup, CHECKALLOC, bulk copy, SELECT INTO, and file
> >> manipulation (such as CREATE FILE) operations on a
> >> database must be serialized. Reissue the statement after
> >> the current backup, CHECKALLOC, or file manipulation
> >> operation is completed. [SQLSTATE 42000] (Error 3023)
> >> Backup or restore operation terminating abnormally.
> >> [SQLSTATE 42000] (Error 3013). The step failed.
> >>
> >> What could be causing this failed job?
> >
> >
> >.
> >