Thursday, March 22, 2012
Error 8198: Could not obtain information about Windows NT group/user
ago it stopped sending out an e-mail once the processing is done.
However, the job still runs and shows that it has been sucessful. I
have traced the problem to the select statement in the xp_sendmail
command below. When I comment out he query line, the command works
fine. The error I get is also below. Thanks in advance.
EXEC master..xp_sendmail
@.recipients = 'me@.company.com',
@.query = 'select COUNT(1) FROM DPEVENTD',
@.width = 160, @.no_header = 'TRUE',
@.subject = 'Test'
ODBC error 8198 (42000) Could not obtain information about Windows NT
group/user 'DOMAINNAME\me.
BTW, we have SQL2000 on Win2000/SP4. Thanks again.Is the job owner sa or a windows account ? That error usually means that SQL
could not get info back from a domain controller about the windows account.
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Joe Kim" <palestine2000bc@.yahoo.com> wrote in message
news:386f7047.0307251717.323ab1a6@.posting.google.com...
Hi, we have a job that has been running for over 1 year. A few days
ago it stopped sending out an e-mail once the processing is done.
However, the job still runs and shows that it has been sucessful. I
have traced the problem to the select statement in the xp_sendmail
command below. When I comment out he query line, the command works
fine. The error I get is also below. Thanks in advance.
EXEC master..xp_sendmail
@.recipients = 'me@.company.com',
@.query = 'select COUNT(1) FROM DPEVENTD',
@.width = 160, @.no_header = 'TRUE',
@.subject = 'Test'
ODBC error 8198 (42000) Could not obtain information about Windows NT
group/user 'DOMAINNAME\me.
BTW, we have SQL2000 on Win2000/SP4. Thanks again.|||This error caused because of the mixed Windows NT and
Windows 2000 domain environment. You probably have both
Windows 2000 and NT servers in the same domain. You need
to have your account to be added into the 'Pre-Windows
2000 Compatible Access' group in the domain. The server
has to be rebooted after the change is made to take effect.
I have ran into the same issue some time ago.
Hope it helps.
>--Original Message--
>Hi Jasper, I set the user to sa on Friday and yes, the
xp_sendmail
>works now. However, if I run xp_sendmail code from my
desktop, I
>still get the same message. I would leave things the way
they are,
>but my manager wants me to fix this problem. Any idea
what I should
>do next? Microsoft has close to nothing on this. Thanks
for your
>help!
>"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in
message news:<uD4uYu5UDHA.2268@.TK2MSFTNGP11.phx.gbl>...
>> Is the job owner sa or a windows account ? That error
usually means that SQL
>> could not get info back from a domain controller about
the windows account.
>> --
>> HTH
>> Jasper Smith (SQL Server MVP)
>> I support PASS - the definitive, global
>> community for SQL Server professionals -
>> http://www.sqlpass.org
>> "Joe Kim" <palestine2000bc@.yahoo.com> wrote in message
>> news:386f7047.0307251717.323ab1a6@.posting.google.com...
>> Hi, we have a job that has been running for over 1
year. A few days
>> ago it stopped sending out an e-mail once the
processing is done.
>> However, the job still runs and shows that it has been
sucessful. I
>> have traced the problem to the select statement in the
xp_sendmail
>> command below. When I comment out he query line, the
command works
>> fine. The error I get is also below. Thanks in advance.
>> EXEC master..xp_sendmail
>> @.recipients = 'me@.company.com',
>> @.query = 'select COUNT(1) FROM DPEVENTD',
>> @.width = 160, @.no_header = 'TRUE',
>> @.subject = 'Test'
>> ODBC error 8198 (42000) Could not obtain information
about Windows NT
>> group/user 'DOMAINNAME\me.
>> BTW, we have SQL2000 on Win2000/SP4. Thanks again.
>.
>|||Your suggestion certainly did the job. Thanks for your help.
BTW, for those who are going through the same problem, you need to
restart your database server for it to be able to detect the changes
on the Domain Controller.
"Coskun" <cxd349@.yahoo.com> wrote in message news:<000701c355eb$e8525050$a401280a@.phx.gbl>...
> This error caused because of the mixed Windows NT and
> Windows 2000 domain environment. You probably have both
> Windows 2000 and NT servers in the same domain. You need
> to have your account to be added into the 'Pre-Windows
> 2000 Compatible Access' group in the domain. The server
> has to be rebooted after the change is made to take effect.
> I have ran into the same issue some time ago.
> Hope it helps.
>
> >--Original Message--
> >Hi Jasper, I set the user to sa on Friday and yes, the
> xp_sendmail
> >works now. However, if I run xp_sendmail code from my
> desktop, I
> >still get the same message. I would leave things the way
> they are,
> >but my manager wants me to fix this problem. Any idea
> what I should
> >do next? Microsoft has close to nothing on this. Thanks
> for your
> >help!
> >
> >"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in
> message news:<uD4uYu5UDHA.2268@.TK2MSFTNGP11.phx.gbl>...
> >> Is the job owner sa or a windows account ? That error
> usually means that SQL
> >> could not get info back from a domain controller about
> the windows account.
> >>
> >> --
> >> HTH
> >>
> >> Jasper Smith (SQL Server MVP)
> >>
> >> I support PASS - the definitive, global
> >> community for SQL Server professionals -
> >> http://www.sqlpass.org
> >>
> >> "Joe Kim" <palestine2000bc@.yahoo.com> wrote in message
> >> news:386f7047.0307251717.323ab1a6@.posting.google.com...
> >> Hi, we have a job that has been running for over 1
> year. A few days
> >> ago it stopped sending out an e-mail once the
> processing is done.
> >> However, the job still runs and shows that it has been
> sucessful. I
> >> have traced the problem to the select statement in the
> xp_sendmail
> >> command below. When I comment out he query line, the
> command works
> >> fine. The error I get is also below. Thanks in advance.
> >>
> >> EXEC master..xp_sendmail
> >> @.recipients = 'me@.company.com',
> >> @.query = 'select COUNT(1) FROM DPEVENTD',
> >> @.width = 160, @.no_header = 'TRUE',
> >> @.subject = 'Test'
> >>
> >> ODBC error 8198 (42000) Could not obtain information
> about Windows NT
> >> group/user 'DOMAINNAME\me.
> >>
> >> BTW, we have SQL2000 on Win2000/SP4. Thanks again.
> >.
> >
Wednesday, March 21, 2012
error 7410
Executed as user: Job Owner. SQL Web Assistant: Could not execute the SQL
statement. SQLSTATE 42000 (Error 16805) Associated statement is not prepared
SQLSTATE
HY007 (Error 0). The step failed.
any good ideas on how to solve?
Hi!
Do please check http://support.microsoft.com/kb/823429 and
http://support.microsoft.com/default...;en-us;834116.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"Fab" <flazzaro@.tac.infostream.ca> wrote in message
news:%23pS25NcfFHA.2372@.TK2MSFTNGP14.phx.gbl...
>I get the following error when i try to run a query on a linked server.
> Executed as user: Job Owner. SQL Web Assistant: Could not execute the SQL
> statement. SQLSTATE 42000 (Error 16805) Associated statement is not
> prepared SQLSTATE
> HY007 (Error 0). The step failed.
> any good ideas on how to solve?
>
>
error 7410
Executed as user: Job Owner. SQL Web Assistant: Could not execute the SQL
statement. SQLSTATE 42000 (Error 16805) Associated statement is not prepared
SQLSTATE
HY007 (Error 0). The step failed.
any good ideas on how to solve?Hi!
Do please check http://support.microsoft.com/kb/823429 and
http://support.microsoft.com/defaul...b;en-us;834116.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"Fab" <flazzaro@.tac.infostream.ca> wrote in message
news:%23pS25NcfFHA.2372@.TK2MSFTNGP14.phx.gbl...
>I get the following error when i try to run a query on a linked server.
> Executed as user: Job Owner. SQL Web Assistant: Could not execute the SQL
> statement. SQLSTATE 42000 (Error 16805) Associated statement is not
> prepared SQLSTATE
> HY007 (Error 0). The step failed.
> any good ideas on how to solve?
>
>
error 7410
Executed as user: Job Owner. SQL Web Assistant: Could not execute the SQL
statement. SQLSTATE 42000 (Error 16805) Associated statement is not prepared
SQLSTATE
HY007 (Error 0). The step failed.
any good ideas on how to solve?Hi!
Do please check http://support.microsoft.com/kb/823429 and
http://support.microsoft.com/default.aspx?scid=kb;en-us;834116.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"Fab" <flazzaro@.tac.infostream.ca> wrote in message
news:%23pS25NcfFHA.2372@.TK2MSFTNGP14.phx.gbl...
>I get the following error when i try to run a query on a linked server.
> Executed as user: Job Owner. SQL Web Assistant: Could not execute the SQL
> statement. SQLSTATE 42000 (Error 16805) Associated statement is not
> prepared SQLSTATE
> HY007 (Error 0). The step failed.
> any good ideas on how to solve?
>
>
Sunday, February 26, 2012
Error 3013
Executed as user: HACIEXXWVNDA\MH-GAGI-WEB01$. Operation on device '\\.\Tape0' exceeded retry count. [SQLSTATE 42000] (Error 3230) BACKUP DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
Does anyone know why this happened? Any help is appreciated.
Thanks
Hi ..
I'm getting the same error; please anyone can help in the matter ASAP.
Thanks and regards.
|||I'd check out the hardware, but in the mean time why don't you back up to a file instead of to tape, then backup the files to tape. It's a safer way to back up, and you're not relying on that particular tape drive to be available when you need to restore, should that need arise.
Error 3013
Executed as user: HACIEXXWVNDA\MH-GAGI-WEB01$. Operation on device '\\.\Tape0' exceeded retry count. [SQLSTATE 42000] (Error 3230) BACKUP DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
Does anyone know why this happened? Any help is appreciated.
Thanks
Hi ..
I'm getting the same error; please anyone can help in the matter ASAP.
Thanks and regards.
|||I'd check out the hardware, but in the mean time why don't you back up to a file instead of to tape, then backup the files to tape. It's a safer way to back up, and you're not relying on that particular tape drive to be available when you need to restore, should that need arise.
Sunday, February 19, 2012
Error 222022 When Starting a Job
Error: Job oXxxxxxxxxx does not exist in the job cache."
Any ideas?
Correction: that error number should be 22022
|||What's in the SQL Server Agent log? Have you tried
restarting SQL Server Agent service?
-Sue
On Mon, 4 Oct 2004 08:41:01 -0700, "Ed"
<Ed@.discussions.microsoft.com> wrote:
>When trying to run any job, I am now getting "Errror 22202: SQL Server Job
>Error: Job oXxxxxxxxxx does not exist in the job cache."
>Any ideas?
|||Yes, I've tried restarting everything, even going so far as to reboot. Here
are the messages from SQLAGENT.OUT.
2004-10-05 08:20:35 - ! [291] An unresolved problem exists with the download
instructions (sysdownloadlist) for target server 'D6YLQF51' at MSX 'D6YLQF51'
2004-10-05 08:20:58 - ! [156] Job 0xB54D1C8D1F41994D9CE870C7083ABAC1 does
not exist in the job cache: attempting to re-acquire it from the server...
2004-10-05 08:20:58 - ! [000] Job 0xB54D1C8D1F41994D9CE870C7083ABAC1 does
not exist in the job cache
"Sue Hoegemeier" wrote:
> What's in the SQL Server Agent log? Have you tried
> restarting SQL Server Agent service?
> -Sue
> On Mon, 4 Oct 2004 08:41:01 -0700, "Ed"
> <Ed@.discussions.microsoft.com> wrote:
>
>
|||So was this server set up for MSX (multiserver administration)? Is it
still suppose to be set up for this? Or did you rename the server?
-Sue
On Tue, 5 Oct 2004 05:29:07 -0700, "Ed" <Ed@.discussions.microsoft.com>
wrote:
[vbcol=seagreen]
>Yes, I've tried restarting everything, even going so far as to reboot. Here
>are the messages from SQLAGENT.OUT.
>2004-10-05 08:20:35 - ! [291] An unresolved problem exists with the download
>instructions (sysdownloadlist) for target server 'D6YLQF51' at MSX 'D6YLQF51'
>2004-10-05 08:20:58 - ! [156] Job 0xB54D1C8D1F41994D9CE870C7083ABAC1 does
>not exist in the job cache: attempting to re-acquire it from the server...
>2004-10-05 08:20:58 - ! [000] Job 0xB54D1C8D1F41994D9CE870C7083ABAC1 does
>not exist in the job cache
>
>"Sue Hoegemeier" wrote:
|||I might have done something at one point (not sure what), but the server is
NOT now supposed to be set up for MSX. In Enterprise Manger, the Sql Server
Agent label does NOT have "(MSX)" appended to it. However, under Sql Server
Agent properties, in the Job System tab, in the Job Execution box, an MSX
server is named.
"Sue Hoegemeier" wrote:
> So was this server set up for MSX (multiserver administration)? Is it
> still suppose to be set up for this? Or did you rename the server?
> -Sue
> On Tue, 5 Oct 2004 05:29:07 -0700, "Ed" <Ed@.discussions.microsoft.com>
> wrote:
>
>
|||Try Right clicking on SQL Server Agent, select Multi Server
Administration, and then select Defect from MSX.
This should remove the server as a target server from the master
server. That's basically where your problems are - the server is setup
as a target server for MSX.
-Sue
On Tue, 5 Oct 2004 08:39:12 -0700, "Ed" <Ed@.discussions.microsoft.com>
wrote:
[vbcol=seagreen]
>I might have done something at one point (not sure what), but the server is
>NOT now supposed to be set up for MSX. In Enterprise Manger, the Sql Server
>Agent label does NOT have "(MSX)" appended to it. However, under Sql Server
>Agent properties, in the Job System tab, in the Job Execution box, an MSX
>server is named.
>"Sue Hoegemeier" wrote:
|||Unfortunately, the only options listed are "Make this a Master" or "Make this
a Target". The option you suggested is not presented.
"Sue Hoegemeier" wrote:
> Try Right clicking on SQL Server Agent, select Multi Server
> Administration, and then select Defect from MSX.
> This should remove the server as a target server from the master
> server. That's basically where your problems are - the server is setup
> as a target server for MSX.
> -Sue
> On Tue, 5 Oct 2004 08:39:12 -0700, "Ed" <Ed@.discussions.microsoft.com>
> wrote:
>
>
Error 22029
The job failed. The Job was invoked by Schedule 9 (Schedule 1). The last step to run was step 1 (Step 1).
Executed as user: NT AUTHORITY\SYSTEM. sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.
This problem i found in Maintenance Plan & error log file:
Maintenance Plan:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 927: [Microsoft][ODBC SQL Server Driver][SQL Server]Database 'restore_test' cannot be opened. It is in the middle of a restore.
[Microsoft][ODBC SQL Server Driver][SQL
Error Log file:
BACKUP failed to complete the command BACKUP DATABASE [restore_test] TO DISK = N'E:\SQL_Backups\restore_test\restore_test_db_2006 04160200.BAK' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
Please help me in find out the solutionverify if the "NT AUTHORITY\SYSTEM" has access to the database and proper rights assigned.|||[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 927: [Microsoft][ODBC SQL Server Driver][SQL Server]Database 'restore_test' cannot be opened. It is in the middle of a restore.
[Microsoft][ODBC SQL Server Driver][SQL
Ummm ... what is the status of the database 'restore_test'?
Loading perhaps? Or suspect?|||Ummm ... what is the status of the database 'restore_test'?
Loading perhaps? Or suspect?
Yes its keep loading|||Yes 'restore_test' database is loading, please provide me help on this.
Regards,
Sumit|||If it is still loading after this much time has past, you might have a corrupt database or bad storage media.
Stop the backup. Stop the restore.
You might try RESTORE VERIFYONLY on the backup file to see if that completes.
If it does complete, it will let you know whether or not the backup file you are using for your restore is viable.
If it does not complete, then that would lead you to your storage device and it's connections to your database server.|||hi tomh,
Thanks for your suggestions, it really works.
Regards,
Sumit|||Hi,
The Problem is solved, Thanks for your valuable time.
Regards,
Sumit
Friday, February 17, 2012
Error 22022
g
that SQLAgent is not running. I have restarted the service serval times, bu
t
seem to be having the same issue. Anyone know why?
Thankshttp://support.microsoft.com/kb/870674/en-us
"Munch" <Munch@.discussions.microsoft.com> wrote in message
news:BB3CCC70-CAD1-4AA5-B0BA-7D9F181D702D@.microsoft.com...
>I am trying to run a job, but SQL Server keeps popping error 22022 and
>saying
> that SQLAgent is not running. I have restarted the service serval times,
> but
> seem to be having the same issue. Anyone know why?
> Thanks
>|||Both outlook and MS OFFICE are not installed on the server. Its not a
problem with POP3 and SQLAGENT
"Raymond D'Anjou" wrote:
> http://support.microsoft.com/kb/870674/en-us
> "Munch" <Munch@.discussions.microsoft.com> wrote in message
> news:BB3CCC70-CAD1-4AA5-B0BA-7D9F181D702D@.microsoft.com...
>
>|||What's the SQLAgent startup account and what account was used to create the
job?
You could try to change the Job Account to SA.
Check see if an MSX server is named in
Sql Server Agent properties/Job System tab/Job Execution box
"Munch" <Munch@.discussions.microsoft.com> wrote in message
news:158A948F-4FC4-49E9-970B-A24E55089C5D@.microsoft.com...
> Both outlook and MS OFFICE are not installed on the server. Its not a
> problem with POP3 and SQLAGENT
> "Raymond D'Anjou" wrote:
>
Error 22022
Server 2000, and I have created the job to perform the
backups. But, when I try to run the backup to test it, I
get the following error:
Error 22022: SQLServerAgent is not currently running so it
cannot be notified of this action.
I have checked, SQLServerAgent is running and if I stop
and start SQLServerAgent I get the same error.
What is wrong and how do I fix it?Some things to check - Are you running SQL Server in fiber
mode (lightweight pooling)? Have you ensured that SQL Agent
is truly running and not hung up in a starting status? Have
you checked your sqlagent.out file?
In addition to lightweight pooling being enabled, Agent can
also get hung up due to a bad mail profile.
-Sue
On Tue, 11 May 2004 11:04:14 -0700, "Rob Simac"
<anonymous@.discussions.microsoft.com> wrote:
>I'm attempting to create a backup schedule for my SQL
>Server 2000, and I have created the job to perform the
>backups. But, when I try to run the backup to test it, I
>get the following error:
>Error 22022: SQLServerAgent is not currently running so it
>cannot be notified of this action.
>I have checked, SQLServerAgent is running and if I stop
>and start SQLServerAgent I get the same error.
>What is wrong and how do I fix it?|||Thanks Sue for your reply. I have checked and SQL Mail is
not configured, but I have checked on an older NT systems
and its SQL Mail is not configured either and the backups
work fine. My current system is Windows 2003 server,
could this be causing the problem? Also, is there a way
to configure MSServerAgent to not bother with mail? I
would rather have it configured so no mail is sent out.
Ciao,
Rob.
>--Original Message--
>Some things to check - Are you running SQL Server in fiber
>mode (lightweight pooling)? Have you ensured that SQL
Agent
>is truly running and not hung up in a starting status?
Have
>you checked your sqlagent.out file?
>In addition to lightweight pooling being enabled, Agent
can
>also get hung up due to a bad mail profile.
>-Sue
>On Tue, 11 May 2004 11:04:14 -0700, "Rob Simac"
><anonymous@.discussions.microsoft.com> wrote:
>>I'm attempting to create a backup schedule for my SQL
>>Server 2000, and I have created the job to perform the
>>backups. But, when I try to run the backup to test it,
I
>>get the following error:
>>Error 22022: SQLServerAgent is not currently running so
it
>>cannot be notified of this action.
>>I have checked, SQLServerAgent is running and if I stop
>>and start SQLServerAgent I get the same error.
>>What is wrong and how do I fix it?
>.
>|||If you don't set a mail profile for SQL Agent then it won't
do anything with mail.
In terms of SQL Agent, you still need to check if the
service is actually running (vs starting), if your server is
configured for lightweight pooling and you need to check
your sqlagent.out file for any errors or problems in
starting SQL Agent.
-Sue
On Wed, 12 May 2004 10:12:18 -0700, "Rob Simac"
<anonymous@.discussions.microsoft.com> wrote:
>Thanks Sue for your reply. I have checked and SQL Mail is
>not configured, but I have checked on an older NT systems
>and its SQL Mail is not configured either and the backups
>work fine. My current system is Windows 2003 server,
>could this be causing the problem? Also, is there a way
>to configure MSServerAgent to not bother with mail? I
>would rather have it configured so no mail is sent out.
> Ciao,
> Rob.
>>--Original Message--
>>Some things to check - Are you running SQL Server in fiber
>>mode (lightweight pooling)? Have you ensured that SQL
>Agent
>>is truly running and not hung up in a starting status?
>Have
>>you checked your sqlagent.out file?
>>In addition to lightweight pooling being enabled, Agent
>can
>>also get hung up due to a bad mail profile.
>>-Sue
>>On Tue, 11 May 2004 11:04:14 -0700, "Rob Simac"
>><anonymous@.discussions.microsoft.com> wrote:
>>I'm attempting to create a backup schedule for my SQL
>>Server 2000, and I have created the job to perform the
>>backups. But, when I try to run the backup to test it,
>I
>>get the following error:
>>Error 22022: SQLServerAgent is not currently running so
>it
>>cannot be notified of this action.
>>I have checked, SQLServerAgent is running and if I stop
>>and start SQLServerAgent I get the same error.
>>What is wrong and how do I fix it?
>>.|||Hello Rob,
Did you ever get this problem figured out? I'm having the exact same issue and I have verified that SQL Agent is running but still having the error.
Let me know.
Regards,
-greg
"Rob Simac" wrote:
> Thanks Sue for your reply. I have checked and SQL Mail is
> not configured, but I have checked on an older NT systems
> and its SQL Mail is not configured either and the backups
> work fine. My current system is Windows 2003 server,
> could this be causing the problem? Also, is there a way
> to configure MSServerAgent to not bother with mail? I
> would rather have it configured so no mail is sent out.
> Ciao,
> Rob.
> >--Original Message--
> >Some things to check - Are you running SQL Server in fiber
> >mode (lightweight pooling)? Have you ensured that SQL
> Agent
> >is truly running and not hung up in a starting status?
> Have
> >you checked your sqlagent.out file?
> >In addition to lightweight pooling being enabled, Agent
> can
> >also get hung up due to a bad mail profile.
> >
> >-Sue
> >
> >On Tue, 11 May 2004 11:04:14 -0700, "Rob Simac"
> ><anonymous@.discussions.microsoft.com> wrote:
> >
> >>I'm attempting to create a backup schedule for my SQL
> >>Server 2000, and I have created the job to perform the
> >>backups. But, when I try to run the backup to test it,
> I
> >>get the following error:
> >>
> >>Error 22022: SQLServerAgent is not currently running so
> it
> >>cannot be notified of this action.
> >>
> >>I have checked, SQLServerAgent is running and if I stop
> >>and start SQLServerAgent I get the same error.
> >>
> >>What is wrong and how do I fix it?
> >
> >.
> >
>
Error 22022
Server 2000, and I have created the job to perform the
backups. But, when I try to run the backup to test it, I
get the following error:
Error 22022: SQLServerAgent is not currently running so it
cannot be notified of this action.
I have checked, SQLServerAgent is running and if I stop
and start SQLServerAgent I get the same error.
What is wrong and how do I fix it?
Hi Rob,
What is the startup account for the SQLAgent ?
What is the account used to create the Job ?
Try changing the Account for Job to SA and then try.
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.
Error 22022
Server 2000, and I have created the job to perform the
backups. But, when I try to run the backup to test it, I
get the following error:
Error 22022: SQLServerAgent is not currently running so it
cannot be notified of this action.
I have checked, SQLServerAgent is running and if I stop
and start SQLServerAgent I get the same error.
What is wrong and how do I fix it?
Some things to check - Are you running SQL Server in fiber
mode (lightweight pooling)? Have you ensured that SQL Agent
is truly running and not hung up in a starting status? Have
you checked your sqlagent.out file?
In addition to lightweight pooling being enabled, Agent can
also get hung up due to a bad mail profile.
-Sue
On Tue, 11 May 2004 11:04:14 -0700, "Rob Simac"
<anonymous@.discussions.microsoft.com> wrote:
>I'm attempting to create a backup schedule for my SQL
>Server 2000, and I have created the job to perform the
>backups. But, when I try to run the backup to test it, I
>get the following error:
>Error 22022: SQLServerAgent is not currently running so it
>cannot be notified of this action.
>I have checked, SQLServerAgent is running and if I stop
>and start SQLServerAgent I get the same error.
>What is wrong and how do I fix it?
|||Thanks Sue for your reply. I have checked and SQL Mail is
not configured, but I have checked on an older NT systems
and its SQL Mail is not configured either and the backups
work fine. My current system is Windows 2003 server,
could this be causing the problem? Also, is there a way
to configure MSServerAgent to not bother with mail? I
would rather have it configured so no mail is sent out.
Ciao,
Rob.
>--Original Message--
>Some things to check - Are you running SQL Server in fiber
>mode (lightweight pooling)? Have you ensured that SQL
Agent
>is truly running and not hung up in a starting status?
Have
>you checked your sqlagent.out file?
>In addition to lightweight pooling being enabled, Agent
can[vbcol=seagreen]
>also get hung up due to a bad mail profile.
>-Sue
>On Tue, 11 May 2004 11:04:14 -0700, "Rob Simac"
><anonymous@.discussions.microsoft.com> wrote:
I[vbcol=seagreen]
it
>.
>
|||If you don't set a mail profile for SQL Agent then it won't
do anything with mail.
In terms of SQL Agent, you still need to check if the
service is actually running (vs starting), if your server is
configured for lightweight pooling and you need to check
your sqlagent.out file for any errors or problems in
starting SQL Agent.
-Sue
On Wed, 12 May 2004 10:12:18 -0700, "Rob Simac"
<anonymous@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Thanks Sue for your reply. I have checked and SQL Mail is
>not configured, but I have checked on an older NT systems
>and its SQL Mail is not configured either and the backups
>work fine. My current system is Windows 2003 server,
>could this be causing the problem? Also, is there a way
>to configure MSServerAgent to not bother with mail? I
>would rather have it configured so no mail is sent out.
> Ciao,
> Rob.
>Agent
>Have
>can
>I
>it
|||Hello Rob,
Did you ever get this problem figured out? I'm having the exact same issue and I have verified that SQL Agent is running but still having the error.
Let me know.
Regards,
-greg
"Rob Simac" wrote:
> Thanks Sue for your reply. I have checked and SQL Mail is
> not configured, but I have checked on an older NT systems
> and its SQL Mail is not configured either and the backups
> work fine. My current system is Windows 2003 server,
> could this be causing the problem? Also, is there a way
> to configure MSServerAgent to not bother with mail? I
> would rather have it configured so no mail is sent out.
> Ciao,
> Rob.
> Agent
> Have
> can
> I
> it
>
Error 22022
Server 2000, and I have created the job to perform the
backups. But, when I try to run the backup to test it, I
get the following error:
Error 22022: SQLServerAgent is not currently running so it
cannot be notified of this action.
I have checked, SQLServerAgent is running and if I stop
and start SQLServerAgent I get the same error.
What is wrong and how do I fix it?Some things to check - Are you running SQL Server in fiber
mode (lightweight pooling)? Have you ensured that SQL Agent
is truly running and not hung up in a starting status? Have
you checked your sqlagent.out file?
In addition to lightweight pooling being enabled, Agent can
also get hung up due to a bad mail profile.
-Sue
On Tue, 11 May 2004 11:04:14 -0700, "Rob Simac"
<anonymous@.discussions.microsoft.com> wrote:
>I'm attempting to create a backup schedule for my SQL
>Server 2000, and I have created the job to perform the
>backups. But, when I try to run the backup to test it, I
>get the following error:
>Error 22022: SQLServerAgent is not currently running so it
>cannot be notified of this action.
>I have checked, SQLServerAgent is running and if I stop
>and start SQLServerAgent I get the same error.
>What is wrong and how do I fix it?|||Thanks Sue for your reply. I have checked and SQL Mail is
not configured, but I have checked on an older NT systems
and its SQL Mail is not configured either and the backups
work fine. My current system is Windows 2003 server,
could this be causing the problem? Also, is there a way
to configure MSServerAgent to not bother with mail? I
would rather have it configured so no mail is sent out.
Ciao,
Rob.
>--Original Message--
>Some things to check - Are you running SQL Server in fiber
>mode (lightweight pooling)? Have you ensured that SQL
Agent
>is truly running and not hung up in a starting status?
Have
>you checked your sqlagent.out file?
>In addition to lightweight pooling being enabled, Agent
can
>also get hung up due to a bad mail profile.
>-Sue
>On Tue, 11 May 2004 11:04:14 -0700, "Rob Simac"
><anonymous@.discussions.microsoft.com> wrote:
>
I[vbcol=seagreen]
it[vbcol=seagreen]
>.
>|||If you don't set a mail profile for SQL Agent then it won't
do anything with mail.
In terms of SQL Agent, you still need to check if the
service is actually running (vs starting), if your server is
configured for lightweight pooling and you need to check
your sqlagent.out file for any errors or problems in
starting SQL Agent.
-Sue
On Wed, 12 May 2004 10:12:18 -0700, "Rob Simac"
<anonymous@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Thanks Sue for your reply. I have checked and SQL Mail is
>not configured, but I have checked on an older NT systems
>and its SQL Mail is not configured either and the backups
>work fine. My current system is Windows 2003 server,
>could this be causing the problem? Also, is there a way
>to configure MSServerAgent to not bother with mail? I
>would rather have it configured so no mail is sent out.
> Ciao,
> Rob.
>
>Agent
>Have
>can
>I
>it|||Hello Rob,
Did you ever get this problem figured out? I'm having the exact same issue
and I have verified that SQL Agent is running but still having the error.
Let me know.
Regards,
-greg
"Rob Simac" wrote:
> Thanks Sue for your reply. I have checked and SQL Mail is
> not configured, but I have checked on an older NT systems
> and its SQL Mail is not configured either and the backups
> work fine. My current system is Windows 2003 server,
> could this be causing the problem? Also, is there a way
> to configure MSServerAgent to not bother with mail? I
> would rather have it configured so no mail is sent out.
> Ciao,
> Rob.
>
> Agent
> Have
> can
> I
> it
>
Wednesday, February 15, 2012
error 207 when trying to add a new job
"error sqlstate: 42s33"
error 207: invalid column name 'category_id'
invalid column name 'netsend_address'
invalid column name 'last_netsend_date'
invalid column name 'last_netsend_time.
Hi,
Did you upgraded your SQL server from older version. If yes then the MSDB
upgrade was not done fully. See the below old post for the step by step
solution.
http://groups.google.com/groups?hl=e...lm=0TDE0%23ZdB
HA.187%40cppssbbsa01.microsoft.com
Thanks
Hari
MCDBA
"ed" <ed@.discussions.microsoft.com> wrote in message
news:99EECA57-E7CC-4F36-A248-F97616029E50@.microsoft.com...
> when trying to add a new job via sql agent server, receiving a message:
> "error sqlstate: 42s33"
> error 207: invalid column name 'category_id'
> invalid column name 'netsend_address'
> invalid column name 'last_netsend_date'
> invalid column name 'last_netsend_time.
|||Hi
-As per SQL Server Books Online "This error (error 207) occurs when a column
referenced in a Transact-SQL statement was not found in any table specified
in
the FROM clause of the query.
-Table msdb..sysoperators didn't have the following columns 'category_id', '
netsend_address',' last_netsend_date',' last_netsend_time'
Looks like some problem with MSDB, try and rebuild as suggested in previous
post.
HTH
Regards
Sadeesh
This posting is provided AS IS with no warranties, and confers no rights.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:OBuR4L6cEHA.3512@.TK2MSFTNGP12.phx.gbl...
> Hi,
> Did you upgraded your SQL server from older version. If yes then the MSDB
> upgrade was not done fully. See the below old post for the step by step
> solution.
>
> http://groups.google.com/groups?hl=e...lm=0TDE0%23ZdB
> HA.187%40cppssbbsa01.microsoft.com
> Thanks
> Hari
> MCDBA
> "ed" <ed@.discussions.microsoft.com> wrote in message
> news:99EECA57-E7CC-4F36-A248-F97616029E50@.microsoft.com...
>
error 207 when trying to add a new job
"error sqlstate: 42s33"
error 207: invalid column name 'category_id'
invalid column name 'netsend_address'
invalid column name 'last_netsend_date'
invalid column name 'last_netsend_time.Hi,
Did you upgraded your SQL server from older version. If yes then the MSDB
upgrade was not done fully. See the below old post for the step by step
solution.
http://groups.google.com/groups?hl=...elm=0TDE0%23ZdB
HA.187%40cppssbbsa01.microsoft.com
Thanks
Hari
MCDBA
"ed" <ed@.discussions.microsoft.com> wrote in message
news:99EECA57-E7CC-4F36-A248-F97616029E50@.microsoft.com...
> when trying to add a new job via sql agent server, receiving a message:
> "error sqlstate: 42s33"
> error 207: invalid column name 'category_id'
> invalid column name 'netsend_address'
> invalid column name 'last_netsend_date'
> invalid column name 'last_netsend_time.|||Hi
-As per SQL Server Books Online "This error (error 207) occurs when a column
referenced in a Transact-SQL statement was not found in any table specified
in
the FROM clause of the query.
-Table msdb..sysoperators didn't have the following columns 'category_id', '
netsend_address',' last_netsend_date',' last_netsend_time'
Looks like some problem with MSDB, try and rebuild as suggested in previous
post.
HTH
Regards
Sadeesh
--
This posting is provided AS IS with no warranties, and confers no rights.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:OBuR4L6cEHA.3512@.TK2MSFTNGP12.phx.gbl...
> Hi,
> Did you upgraded your SQL server from older version. If yes then the MSDB
> upgrade was not done fully. See the below old post for the step by step
> solution.
>
> [url]http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=0TDE0%23ZdB[/ur
l]
> HA.187%40cppssbbsa01.microsoft.com
> Thanks
> Hari
> MCDBA
> "ed" <ed@.discussions.microsoft.com> wrote in message
> news:99EECA57-E7CC-4F36-A248-F97616029E50@.microsoft.com...
>|||hi,
i didn't upgrage but i restored msdb from backup and it was ok.
thanks.
"Hari Prasad" wrote:
> Hi,
> Did you upgraded your SQL server from older version. If yes then the MSDB
> upgrade was not done fully. See the below old post for the step by step
> solution.
>
> [url]http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=0TDE0%23ZdB[/ur
l]
> HA.187%40cppssbbsa01.microsoft.com
> Thanks
> Hari
> MCDBA
> "ed" <ed@.discussions.microsoft.com> wrote in message
> news:99EECA57-E7CC-4F36-A248-F97616029E50@.microsoft.com...
>
>|||yep some of the columns were missing from the system tables in msdb? resto
red msdb from an old backup.
thanks for your help.
"Sadeesh[MSFT]" wrote:
> Hi
> -As per SQL Server Books Online "This error (error 207) occurs when a colu
mn
> referenced in a Transact-SQL statement was not found in any table specifie
d
> in
> the FROM clause of the query.
> -Table msdb..sysoperators didn't have the following columns 'category_id',
'
> netsend_address',' last_netsend_date',' last_netsend_time'
> Looks like some problem with MSDB, try and rebuild as suggested in previou
s
> post.
> HTH
> Regards
> Sadeesh
> --
> This posting is provided AS IS with no warranties, and confers no rights.
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:OBuR4L6cEHA.3512@.TK2MSFTNGP12.phx.gbl...
>
>