Hi,
I've set up jobs and output files in SQL2005. When the job is completed, I
would like to check the output file by clicking VIEW button. However, the
button is grey-out.
The owner of the job is sa. What is other permission I missed ?
Thanks.
Hi Johnny
"Johnny" wrote:
> Hi,
> I've set up jobs and output files in SQL2005. When the job is completed, I
> would like to check the output file by clicking VIEW button. However, the
> button is grey-out.
> The owner of the job is sa. What is other permission I missed ?
> Thanks.
According to Books Online it is not available in SQL 2005
From Books Online:
View
In Microsoft SQL Server 2005, this button is disabled for viewing output
files. Instead, use Notepad to view job step output files. In Microsoft SQL
Server 2000, this launches Notepad to view the output file.
John
|||Hi John,
Thank you. Why leave the button there ?
Regards,
Johnny
"John Bell" wrote:
> Hi Johnny
> "Johnny" wrote:
> According to Books Online it is not available in SQL 2005
> From Books Online:
> View
> In Microsoft SQL Server 2005, this button is disabled for viewing output
> files. Instead, use Notepad to view job step output files. In Microsoft SQL
> Server 2000, this launches Notepad to view the output file.
>
> John
>
|||Hi Johnny
"Johnny" wrote:
[vbcol=seagreen]
> Hi John,
> Thank you. Why leave the button there ?
> Regards,
> Johnny
> "John Bell" wrote:
I guess that if you are looking at a SQL 2000 instance of SQL Agent then it
will bring up the log file in Notepad!!!!
John
|||Yes, I always check the output file for any jobs in SQL2000 Agent job.
"John Bell" wrote:
> Hi Johnny
> "Johnny" wrote:
>
> I guess that if you are looking at a SQL 2000 instance of SQL Agent then it
> will bring up the log file in Notepad!!!!
> John
|||"John Bell" wrote:
> I guess that if you are looking at a SQL 2000 instance of SQL Agent then it
> will bring up the log file in Notepad!!!!
> John
And it does!!
John
Showing posts with label jobs. Show all posts
Showing posts with label jobs. Show all posts
Sunday, March 11, 2012
Cannot view log for SQL Agent job (SQL2005)
Hi,
I've set up jobs and output files in SQL2005. When the job is completed, I
would like to check the output file by clicking VIEW button. However, the
button is grey-out.
The owner of the job is sa. What is other permission I missed ?
Thanks.Hi Johnny
"Johnny" wrote:
> Hi,
> I've set up jobs and output files in SQL2005. When the job is completed,
I
> would like to check the output file by clicking VIEW button. However, the
> button is grey-out.
> The owner of the job is sa. What is other permission I missed ?
> Thanks.
According to Books Online it is not available in SQL 2005
From Books Online:
View
In Microsoft SQL Server 2005, this button is disabled for viewing output
files. Instead, use Notepad to view job step output files. In Microsoft SQL
Server 2000, this launches Notepad to view the output file.
John|||Hi John,
Thank you. Why leave the button there ?
Regards,
Johnny
"John Bell" wrote:
> Hi Johnny
> "Johnny" wrote:
>
> According to Books Online it is not available in SQL 2005
> From Books Online:
> View
> In Microsoft SQL Server 2005, this button is disabled for viewing output
> files. Instead, use Notepad to view job step output files. In Microsoft SQ
L
> Server 2000, this launches Notepad to view the output file.
>
> John
>|||Hi Johnny
"Johnny" wrote:
[vbcol=seagreen]
> Hi John,
> Thank you. Why leave the button there ?
> Regards,
> Johnny
> "John Bell" wrote:
>
I guess that if you are looking at a SQL 2000 instance of SQL Agent then it
will bring up the log file in Notepad!!!!
John|||Yes, I always check the output file for any jobs in SQL2000 Agent job.
"John Bell" wrote:
> Hi Johnny
> "Johnny" wrote:
>
> I guess that if you are looking at a SQL 2000 instance of SQL Agent then i
t
> will bring up the log file in Notepad!!!!
> John|||"John Bell" wrote:
> I guess that if you are looking at a SQL 2000 instance of SQL Agent then i
t
> will bring up the log file in Notepad!!!!
> John
And it does!!
John
I've set up jobs and output files in SQL2005. When the job is completed, I
would like to check the output file by clicking VIEW button. However, the
button is grey-out.
The owner of the job is sa. What is other permission I missed ?
Thanks.Hi Johnny
"Johnny" wrote:
> Hi,
> I've set up jobs and output files in SQL2005. When the job is completed,
I
> would like to check the output file by clicking VIEW button. However, the
> button is grey-out.
> The owner of the job is sa. What is other permission I missed ?
> Thanks.
According to Books Online it is not available in SQL 2005
From Books Online:
View
In Microsoft SQL Server 2005, this button is disabled for viewing output
files. Instead, use Notepad to view job step output files. In Microsoft SQL
Server 2000, this launches Notepad to view the output file.
John|||Hi John,
Thank you. Why leave the button there ?
Regards,
Johnny
"John Bell" wrote:
> Hi Johnny
> "Johnny" wrote:
>
> According to Books Online it is not available in SQL 2005
> From Books Online:
> View
> In Microsoft SQL Server 2005, this button is disabled for viewing output
> files. Instead, use Notepad to view job step output files. In Microsoft SQ
L
> Server 2000, this launches Notepad to view the output file.
>
> John
>|||Hi Johnny
"Johnny" wrote:
[vbcol=seagreen]
> Hi John,
> Thank you. Why leave the button there ?
> Regards,
> Johnny
> "John Bell" wrote:
>
I guess that if you are looking at a SQL 2000 instance of SQL Agent then it
will bring up the log file in Notepad!!!!
John|||Yes, I always check the output file for any jobs in SQL2000 Agent job.
"John Bell" wrote:
> Hi Johnny
> "Johnny" wrote:
>
> I guess that if you are looking at a SQL 2000 instance of SQL Agent then i
t
> will bring up the log file in Notepad!!!!
> John|||"John Bell" wrote:
> I guess that if you are looking at a SQL 2000 instance of SQL Agent then i
t
> will bring up the log file in Notepad!!!!
> John
And it does!!
John
Cannot view log for SQL Agent job (SQL2005)
Hi,
I've set up jobs and output files in SQL2005. When the job is completed, I
would like to check the output file by clicking VIEW button. However, the
button is grey-out.
The owner of the job is sa. What is other permission I missed ?
Thanks.Hi Johnny
"Johnny" wrote:
> Hi,
> I've set up jobs and output files in SQL2005. When the job is completed, I
> would like to check the output file by clicking VIEW button. However, the
> button is grey-out.
> The owner of the job is sa. What is other permission I missed ?
> Thanks.
According to Books Online it is not available in SQL 2005
From Books Online:
View
In Microsoft SQL Server 2005, this button is disabled for viewing output
files. Instead, use Notepad to view job step output files. In Microsoft SQL
Server 2000, this launches Notepad to view the output file.
John|||Hi John,
Thank you. Why leave the button there ?
Regards,
Johnny
"John Bell" wrote:
> Hi Johnny
> "Johnny" wrote:
> > Hi,
> >
> > I've set up jobs and output files in SQL2005. When the job is completed, I
> > would like to check the output file by clicking VIEW button. However, the
> > button is grey-out.
> >
> > The owner of the job is sa. What is other permission I missed ?
> >
> > Thanks.
> According to Books Online it is not available in SQL 2005
> From Books Online:
> View
> In Microsoft SQL Server 2005, this button is disabled for viewing output
> files. Instead, use Notepad to view job step output files. In Microsoft SQL
> Server 2000, this launches Notepad to view the output file.
>
> John
>|||Hi Johnny
"Johnny" wrote:
> Hi John,
> Thank you. Why leave the button there ?
> Regards,
> Johnny
> "John Bell" wrote:
> > According to Books Online it is not available in SQL 2005
> >
> > From Books Online:
> >
> > View
> > In Microsoft SQL Server 2005, this button is disabled for viewing output
> > files. Instead, use Notepad to view job step output files. In Microsoft SQL
> > Server 2000, this launches Notepad to view the output file.
> >
> >
> > John
> >
I guess that if you are looking at a SQL 2000 instance of SQL Agent then it
will bring up the log file in Notepad!!!!
John|||Yes, I always check the output file for any jobs in SQL2000 Agent job.
"John Bell" wrote:
> Hi Johnny
> "Johnny" wrote:
> > Hi John,
> >
> > Thank you. Why leave the button there ?
> >
> > Regards,
> > Johnny
> >
> > "John Bell" wrote:
> >
> > > According to Books Online it is not available in SQL 2005
> > >
> > > From Books Online:
> > >
> > > View
> > > In Microsoft SQL Server 2005, this button is disabled for viewing output
> > > files. Instead, use Notepad to view job step output files. In Microsoft SQL
> > > Server 2000, this launches Notepad to view the output file.
> > >
> > >
> > > John
> > >
> I guess that if you are looking at a SQL 2000 instance of SQL Agent then it
> will bring up the log file in Notepad!!!!
> John|||"John Bell" wrote:
> I guess that if you are looking at a SQL 2000 instance of SQL Agent then it
> will bring up the log file in Notepad!!!!
> John
And it does!!
John
I've set up jobs and output files in SQL2005. When the job is completed, I
would like to check the output file by clicking VIEW button. However, the
button is grey-out.
The owner of the job is sa. What is other permission I missed ?
Thanks.Hi Johnny
"Johnny" wrote:
> Hi,
> I've set up jobs and output files in SQL2005. When the job is completed, I
> would like to check the output file by clicking VIEW button. However, the
> button is grey-out.
> The owner of the job is sa. What is other permission I missed ?
> Thanks.
According to Books Online it is not available in SQL 2005
From Books Online:
View
In Microsoft SQL Server 2005, this button is disabled for viewing output
files. Instead, use Notepad to view job step output files. In Microsoft SQL
Server 2000, this launches Notepad to view the output file.
John|||Hi John,
Thank you. Why leave the button there ?
Regards,
Johnny
"John Bell" wrote:
> Hi Johnny
> "Johnny" wrote:
> > Hi,
> >
> > I've set up jobs and output files in SQL2005. When the job is completed, I
> > would like to check the output file by clicking VIEW button. However, the
> > button is grey-out.
> >
> > The owner of the job is sa. What is other permission I missed ?
> >
> > Thanks.
> According to Books Online it is not available in SQL 2005
> From Books Online:
> View
> In Microsoft SQL Server 2005, this button is disabled for viewing output
> files. Instead, use Notepad to view job step output files. In Microsoft SQL
> Server 2000, this launches Notepad to view the output file.
>
> John
>|||Hi Johnny
"Johnny" wrote:
> Hi John,
> Thank you. Why leave the button there ?
> Regards,
> Johnny
> "John Bell" wrote:
> > According to Books Online it is not available in SQL 2005
> >
> > From Books Online:
> >
> > View
> > In Microsoft SQL Server 2005, this button is disabled for viewing output
> > files. Instead, use Notepad to view job step output files. In Microsoft SQL
> > Server 2000, this launches Notepad to view the output file.
> >
> >
> > John
> >
I guess that if you are looking at a SQL 2000 instance of SQL Agent then it
will bring up the log file in Notepad!!!!
John|||Yes, I always check the output file for any jobs in SQL2000 Agent job.
"John Bell" wrote:
> Hi Johnny
> "Johnny" wrote:
> > Hi John,
> >
> > Thank you. Why leave the button there ?
> >
> > Regards,
> > Johnny
> >
> > "John Bell" wrote:
> >
> > > According to Books Online it is not available in SQL 2005
> > >
> > > From Books Online:
> > >
> > > View
> > > In Microsoft SQL Server 2005, this button is disabled for viewing output
> > > files. Instead, use Notepad to view job step output files. In Microsoft SQL
> > > Server 2000, this launches Notepad to view the output file.
> > >
> > >
> > > John
> > >
> I guess that if you are looking at a SQL 2000 instance of SQL Agent then it
> will bring up the log file in Notepad!!!!
> John|||"John Bell" wrote:
> I guess that if you are looking at a SQL 2000 instance of SQL Agent then it
> will bring up the log file in Notepad!!!!
> John
And it does!!
John
Wednesday, March 7, 2012
Cannot take Backup in Tape..............Why ? what is wrong with this tape?
Hi there.
I haver very weird problem. I have installed BackupExec for Windows on our S
taging Server. It run goods with our Backup jobs but when i go to SQL Server
and try to backup and database on tape. It gives me this error :
The media family on device '\\.'Tape0' is incorrectly formed. SQL Server can
not process this media family.
BACKUP DATABASE is terminating abnormally.
What could be wrong ?
What can i do to make my backup run on Tape.
P.S
Tape is DELL (Media Recognition System) 20 GB.
System is Dell PowerEdge.
Thanks for any response
Abid MalikChange \\.Tape0 to
\\.\Tape0 ( you are missing a whack!)
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Abid Malik" <abidmunirmalik@.hotmail.com> wrote in message
news:9859C468-C59D-45FD-A045-D1EAE4BE61BF@.microsoft.com...
> Hi there.
> I haver very weird problem. I have installed BackupExec for Windows on our
Staging Server. It run goods with our Backup jobs but when i go to SQL
Server and try to backup and database on tape. It gives me this error :
> The media family on device '\\.'Tape0' is incorrectly formed. SQL Server
cannot process this media family.
> BACKUP DATABASE is terminating abnormally.
> What could be wrong ?
> What can i do to make my backup run on Tape.
> P.S
> Tape is DELL (Media Recognition System) 20 GB.
> System is Dell PowerEdge.
>
> Thanks for any response
> Abid Malik
>
I haver very weird problem. I have installed BackupExec for Windows on our S
taging Server. It run goods with our Backup jobs but when i go to SQL Server
and try to backup and database on tape. It gives me this error :
The media family on device '\\.'Tape0' is incorrectly formed. SQL Server can
not process this media family.
BACKUP DATABASE is terminating abnormally.
What could be wrong ?
What can i do to make my backup run on Tape.
P.S
Tape is DELL (Media Recognition System) 20 GB.
System is Dell PowerEdge.
Thanks for any response
Abid MalikChange \\.Tape0 to
\\.\Tape0 ( you are missing a whack!)
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Abid Malik" <abidmunirmalik@.hotmail.com> wrote in message
news:9859C468-C59D-45FD-A045-D1EAE4BE61BF@.microsoft.com...
> Hi there.
> I haver very weird problem. I have installed BackupExec for Windows on our
Staging Server. It run goods with our Backup jobs but when i go to SQL
Server and try to backup and database on tape. It gives me this error :
> The media family on device '\\.'Tape0' is incorrectly formed. SQL Server
cannot process this media family.
> BACKUP DATABASE is terminating abnormally.
> What could be wrong ?
> What can i do to make my backup run on Tape.
> P.S
> Tape is DELL (Media Recognition System) 20 GB.
> System is Dell PowerEdge.
>
> Thanks for any response
> Abid Malik
>
Thursday, February 16, 2012
cannot see SQL Jobs on remote server
Hi,
I'm having troubles brining up details of existing SQL Jobs from remote
server. When I double-click existing job, it brings up "New Job" dialog box
instead of job details.
I needed to see and modify steps of a job on my collegue's machine. I can
connect to her SQL Server 2005 all right. But when I find the job I need,
right click it and select "Properties", I get "New Job" dialog box with all
tabs empty. What's interesting is I can still use "Script job as" menu item.
Another thing is that I see error messages like this in my error log:
DCOM was unable to communicate with the computer AAA using any of the
configured protocols.
I looked up this message and verified that I don't have UDP or IPX enabled,
only Connection-oriented TCP/IP and Connection-oriented SPX.
My other collegue can see the jobs fine, so I suppose the configuration
issue is with my machine. We all have WinXP Proferssional SP2 and both SQL
Server 2000 and 2005 on our machines. 2005's version is
Microsoft SQL Server 2005 - 9.00.2047.00 (Intel X86) Apr 14 2006 01:12:25
Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Windows
NT 5.1 (Build 2600: Service Pack 2)
I'd really appreciate if anyone has ideas on that.
thanks,
LucyI think the two errors are separate issues. I've seen the
issue with viewing jobs come up a few times. I suspect that
it's caused by problems with the smo dll - did you install
visual studio service packs to your PC? Try applying SQL
Server 2005 SP2 on your PC. That worked for me a couple of
times that I've run into this.
-Sue
On Fri, 30 Mar 2007 15:06:01 -0700, Lucy
<Lucy@.discussions.microsoft.com> wrote:
>Hi,
>I'm having troubles brining up details of existing SQL Jobs from remote
>server. When I double-click existing job, it brings up "New Job" dialog box
>instead of job details.
>I needed to see and modify steps of a job on my collegue's machine. I can
>connect to her SQL Server 2005 all right. But when I find the job I need,
>right click it and select "Properties", I get "New Job" dialog box with all
>tabs empty. What's interesting is I can still use "Script job as" menu item
.
>Another thing is that I see error messages like this in my error log:
>DCOM was unable to communicate with the computer AAA using any of the
>configured protocols.
>I looked up this message and verified that I don't have UDP or IPX enabled,
>only Connection-oriented TCP/IP and Connection-oriented SPX.
>My other collegue can see the jobs fine, so I suppose the configuration
>issue is with my machine. We all have WinXP Proferssional SP2 and both SQL
>Server 2000 and 2005 on our machines. 2005's version is
>Microsoft SQL Server 2005 - 9.00.2047.00 (Intel X86) Apr 14 2006 01:12:25
> Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Window
s
>NT 5.1 (Build 2600: Service Pack 2)
>I'd really appreciate if anyone has ideas on that.
>thanks,
>Lucy|||Hi Sue, thanks for answering.
I already have SP2, and SMO appears to be ok too.
The errors in the log appear at the time when I try to access the remote
jobs, so there has to be some connection between them...
"Sue Hoegemeier" wrote:
> I think the two errors are separate issues. I've seen the
> issue with viewing jobs come up a few times. I suspect that
> it's caused by problems with the smo dll - did you install
> visual studio service packs to your PC? Try applying SQL
> Server 2005 SP2 on your PC. That worked for me a couple of
> times that I've run into this.
> -Sue
> On Fri, 30 Mar 2007 15:06:01 -0700, Lucy
> <Lucy@.discussions.microsoft.com> wrote:
>
>|||Sorry, Sue, you were right. I looked at it once more and noticed that it was
my Windows that had SP2. Now I installed SP2 for SQL Server and the problem
went away.
Thanks a lot,
Lucy
"Lucy" wrote:
[vbcol=seagreen]
> Hi Sue, thanks for answering.
> I already have SP2, and SMO appears to be ok too.
> The errors in the log appear at the time when I try to access the remote
> jobs, so there has to be some connection between them...
> "Sue Hoegemeier" wrote:
>|||No problem...thanks for posting back.
-Sue
On Mon, 2 Apr 2007 12:32:06 -0700, Lucy
<Lucy@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Sorry, Sue, you were right. I looked at it once more and noticed that it wa
s
>my Windows that had SP2. Now I installed SP2 for SQL Server and the problem
>went away.
>Thanks a lot,
>Lucy
>"Lucy" wrote:
>
I'm having troubles brining up details of existing SQL Jobs from remote
server. When I double-click existing job, it brings up "New Job" dialog box
instead of job details.
I needed to see and modify steps of a job on my collegue's machine. I can
connect to her SQL Server 2005 all right. But when I find the job I need,
right click it and select "Properties", I get "New Job" dialog box with all
tabs empty. What's interesting is I can still use "Script job as" menu item.
Another thing is that I see error messages like this in my error log:
DCOM was unable to communicate with the computer AAA using any of the
configured protocols.
I looked up this message and verified that I don't have UDP or IPX enabled,
only Connection-oriented TCP/IP and Connection-oriented SPX.
My other collegue can see the jobs fine, so I suppose the configuration
issue is with my machine. We all have WinXP Proferssional SP2 and both SQL
Server 2000 and 2005 on our machines. 2005's version is
Microsoft SQL Server 2005 - 9.00.2047.00 (Intel X86) Apr 14 2006 01:12:25
Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Windows
NT 5.1 (Build 2600: Service Pack 2)
I'd really appreciate if anyone has ideas on that.
thanks,
LucyI think the two errors are separate issues. I've seen the
issue with viewing jobs come up a few times. I suspect that
it's caused by problems with the smo dll - did you install
visual studio service packs to your PC? Try applying SQL
Server 2005 SP2 on your PC. That worked for me a couple of
times that I've run into this.
-Sue
On Fri, 30 Mar 2007 15:06:01 -0700, Lucy
<Lucy@.discussions.microsoft.com> wrote:
>Hi,
>I'm having troubles brining up details of existing SQL Jobs from remote
>server. When I double-click existing job, it brings up "New Job" dialog box
>instead of job details.
>I needed to see and modify steps of a job on my collegue's machine. I can
>connect to her SQL Server 2005 all right. But when I find the job I need,
>right click it and select "Properties", I get "New Job" dialog box with all
>tabs empty. What's interesting is I can still use "Script job as" menu item
.
>Another thing is that I see error messages like this in my error log:
>DCOM was unable to communicate with the computer AAA using any of the
>configured protocols.
>I looked up this message and verified that I don't have UDP or IPX enabled,
>only Connection-oriented TCP/IP and Connection-oriented SPX.
>My other collegue can see the jobs fine, so I suppose the configuration
>issue is with my machine. We all have WinXP Proferssional SP2 and both SQL
>Server 2000 and 2005 on our machines. 2005's version is
>Microsoft SQL Server 2005 - 9.00.2047.00 (Intel X86) Apr 14 2006 01:12:25
> Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Window
s
>NT 5.1 (Build 2600: Service Pack 2)
>I'd really appreciate if anyone has ideas on that.
>thanks,
>Lucy|||Hi Sue, thanks for answering.
I already have SP2, and SMO appears to be ok too.
The errors in the log appear at the time when I try to access the remote
jobs, so there has to be some connection between them...
"Sue Hoegemeier" wrote:
> I think the two errors are separate issues. I've seen the
> issue with viewing jobs come up a few times. I suspect that
> it's caused by problems with the smo dll - did you install
> visual studio service packs to your PC? Try applying SQL
> Server 2005 SP2 on your PC. That worked for me a couple of
> times that I've run into this.
> -Sue
> On Fri, 30 Mar 2007 15:06:01 -0700, Lucy
> <Lucy@.discussions.microsoft.com> wrote:
>
>|||Sorry, Sue, you were right. I looked at it once more and noticed that it was
my Windows that had SP2. Now I installed SP2 for SQL Server and the problem
went away.
Thanks a lot,
Lucy
"Lucy" wrote:
[vbcol=seagreen]
> Hi Sue, thanks for answering.
> I already have SP2, and SMO appears to be ok too.
> The errors in the log appear at the time when I try to access the remote
> jobs, so there has to be some connection between them...
> "Sue Hoegemeier" wrote:
>|||No problem...thanks for posting back.
-Sue
On Mon, 2 Apr 2007 12:32:06 -0700, Lucy
<Lucy@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Sorry, Sue, you were right. I looked at it once more and noticed that it wa
s
>my Windows that had SP2. Now I installed SP2 for SQL Server and the problem
>went away.
>Thanks a lot,
>Lucy
>"Lucy" wrote:
>
cannot see SQL Jobs on remote server
Hi,
I'm having troubles brining up details of existing SQL Jobs from remote
server. When I double-click existing job, it brings up "New Job" dialog box
instead of job details.
I needed to see and modify steps of a job on my collegue's machine. I can
connect to her SQL Server 2005 all right. But when I find the job I need,
right click it and select "Properties", I get "New Job" dialog box with all
tabs empty. What's interesting is I can still use "Script job as" menu item.
Another thing is that I see error messages like this in my error log:
DCOM was unable to communicate with the computer AAA using any of the
configured protocols.
I looked up this message and verified that I don't have UDP or IPX enabled,
only Connection-oriented TCP/IP and Connection-oriented SPX.
My other collegue can see the jobs fine, so I suppose the configuration
issue is with my machine. We all have WinXP Proferssional SP2 and both SQL
Server 2000 and 2005 on our machines. 2005's version is
Microsoft SQL Server 2005 - 9.00.2047.00 (Intel X86) Apr 14 2006 01:12:25
Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Windows
NT 5.1 (Build 2600: Service Pack 2)
I'd really appreciate if anyone has ideas on that.
thanks,
Lucy
I think the two errors are separate issues. I've seen the
issue with viewing jobs come up a few times. I suspect that
it's caused by problems with the smo dll - did you install
visual studio service packs to your PC? Try applying SQL
Server 2005 SP2 on your PC. That worked for me a couple of
times that I've run into this.
-Sue
On Fri, 30 Mar 2007 15:06:01 -0700, Lucy
<Lucy@.discussions.microsoft.com> wrote:
>Hi,
>I'm having troubles brining up details of existing SQL Jobs from remote
>server. When I double-click existing job, it brings up "New Job" dialog box
>instead of job details.
>I needed to see and modify steps of a job on my collegue's machine. I can
>connect to her SQL Server 2005 all right. But when I find the job I need,
>right click it and select "Properties", I get "New Job" dialog box with all
>tabs empty. What's interesting is I can still use "Script job as" menu item.
>Another thing is that I see error messages like this in my error log:
>DCOM was unable to communicate with the computer AAA using any of the
>configured protocols.
>I looked up this message and verified that I don't have UDP or IPX enabled,
>only Connection-oriented TCP/IP and Connection-oriented SPX.
>My other collegue can see the jobs fine, so I suppose the configuration
>issue is with my machine. We all have WinXP Proferssional SP2 and both SQL
>Server 2000 and 2005 on our machines. 2005's version is
>Microsoft SQL Server 2005 - 9.00.2047.00 (Intel X86) Apr 14 2006 01:12:25
> Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Windows
>NT 5.1 (Build 2600: Service Pack 2)
>I'd really appreciate if anyone has ideas on that.
>thanks,
>Lucy
|||Hi Sue, thanks for answering.
I already have SP2, and SMO appears to be ok too.
The errors in the log appear at the time when I try to access the remote
jobs, so there has to be some connection between them...
"Sue Hoegemeier" wrote:
> I think the two errors are separate issues. I've seen the
> issue with viewing jobs come up a few times. I suspect that
> it's caused by problems with the smo dll - did you install
> visual studio service packs to your PC? Try applying SQL
> Server 2005 SP2 on your PC. That worked for me a couple of
> times that I've run into this.
> -Sue
> On Fri, 30 Mar 2007 15:06:01 -0700, Lucy
> <Lucy@.discussions.microsoft.com> wrote:
>
>
|||Sorry, Sue, you were right. I looked at it once more and noticed that it was
my Windows that had SP2. Now I installed SP2 for SQL Server and the problem
went away.
Thanks a lot,
Lucy
"Lucy" wrote:
[vbcol=seagreen]
> Hi Sue, thanks for answering.
> I already have SP2, and SMO appears to be ok too.
> The errors in the log appear at the time when I try to access the remote
> jobs, so there has to be some connection between them...
> "Sue Hoegemeier" wrote:
|||No problem...thanks for posting back.
-Sue
On Mon, 2 Apr 2007 12:32:06 -0700, Lucy
<Lucy@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Sorry, Sue, you were right. I looked at it once more and noticed that it was
>my Windows that had SP2. Now I installed SP2 for SQL Server and the problem
>went away.
>Thanks a lot,
>Lucy
>"Lucy" wrote:
I'm having troubles brining up details of existing SQL Jobs from remote
server. When I double-click existing job, it brings up "New Job" dialog box
instead of job details.
I needed to see and modify steps of a job on my collegue's machine. I can
connect to her SQL Server 2005 all right. But when I find the job I need,
right click it and select "Properties", I get "New Job" dialog box with all
tabs empty. What's interesting is I can still use "Script job as" menu item.
Another thing is that I see error messages like this in my error log:
DCOM was unable to communicate with the computer AAA using any of the
configured protocols.
I looked up this message and verified that I don't have UDP or IPX enabled,
only Connection-oriented TCP/IP and Connection-oriented SPX.
My other collegue can see the jobs fine, so I suppose the configuration
issue is with my machine. We all have WinXP Proferssional SP2 and both SQL
Server 2000 and 2005 on our machines. 2005's version is
Microsoft SQL Server 2005 - 9.00.2047.00 (Intel X86) Apr 14 2006 01:12:25
Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Windows
NT 5.1 (Build 2600: Service Pack 2)
I'd really appreciate if anyone has ideas on that.
thanks,
Lucy
I think the two errors are separate issues. I've seen the
issue with viewing jobs come up a few times. I suspect that
it's caused by problems with the smo dll - did you install
visual studio service packs to your PC? Try applying SQL
Server 2005 SP2 on your PC. That worked for me a couple of
times that I've run into this.
-Sue
On Fri, 30 Mar 2007 15:06:01 -0700, Lucy
<Lucy@.discussions.microsoft.com> wrote:
>Hi,
>I'm having troubles brining up details of existing SQL Jobs from remote
>server. When I double-click existing job, it brings up "New Job" dialog box
>instead of job details.
>I needed to see and modify steps of a job on my collegue's machine. I can
>connect to her SQL Server 2005 all right. But when I find the job I need,
>right click it and select "Properties", I get "New Job" dialog box with all
>tabs empty. What's interesting is I can still use "Script job as" menu item.
>Another thing is that I see error messages like this in my error log:
>DCOM was unable to communicate with the computer AAA using any of the
>configured protocols.
>I looked up this message and verified that I don't have UDP or IPX enabled,
>only Connection-oriented TCP/IP and Connection-oriented SPX.
>My other collegue can see the jobs fine, so I suppose the configuration
>issue is with my machine. We all have WinXP Proferssional SP2 and both SQL
>Server 2000 and 2005 on our machines. 2005's version is
>Microsoft SQL Server 2005 - 9.00.2047.00 (Intel X86) Apr 14 2006 01:12:25
> Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Windows
>NT 5.1 (Build 2600: Service Pack 2)
>I'd really appreciate if anyone has ideas on that.
>thanks,
>Lucy
|||Hi Sue, thanks for answering.
I already have SP2, and SMO appears to be ok too.
The errors in the log appear at the time when I try to access the remote
jobs, so there has to be some connection between them...
"Sue Hoegemeier" wrote:
> I think the two errors are separate issues. I've seen the
> issue with viewing jobs come up a few times. I suspect that
> it's caused by problems with the smo dll - did you install
> visual studio service packs to your PC? Try applying SQL
> Server 2005 SP2 on your PC. That worked for me a couple of
> times that I've run into this.
> -Sue
> On Fri, 30 Mar 2007 15:06:01 -0700, Lucy
> <Lucy@.discussions.microsoft.com> wrote:
>
>
|||Sorry, Sue, you were right. I looked at it once more and noticed that it was
my Windows that had SP2. Now I installed SP2 for SQL Server and the problem
went away.
Thanks a lot,
Lucy
"Lucy" wrote:
[vbcol=seagreen]
> Hi Sue, thanks for answering.
> I already have SP2, and SMO appears to be ok too.
> The errors in the log appear at the time when I try to access the remote
> jobs, so there has to be some connection between them...
> "Sue Hoegemeier" wrote:
|||No problem...thanks for posting back.
-Sue
On Mon, 2 Apr 2007 12:32:06 -0700, Lucy
<Lucy@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Sorry, Sue, you were right. I looked at it once more and noticed that it was
>my Windows that had SP2. Now I installed SP2 for SQL Server and the problem
>went away.
>Thanks a lot,
>Lucy
>"Lucy" wrote:
Sunday, February 12, 2012
Cannot run SQLServerAgent jobs after changing SA password
I am new to SQL Server 2000. When I set a password for SA all the SQLServerAgent jobs fail with a login error and will not start. I have tried to change the SQLAgent service login via the Control Panel/Services, but it will not accept SA as a valid login, when I browse logins, only the NT logins seem to appear. The jobs are owned by my normal login and not by SA.
This is probably a simple change, but I am going round in circles trying to locate the 'how to' documentation.SQLServerAgent service needs to run under a Windows account...|||Check your SQL Server connection settings in SQL Server Agent properties (Windows Auth. or SQL server Auth.).|||Thanks. I did not see the SQL agent connection properties with a login and password. All is now well.
This is probably a simple change, but I am going round in circles trying to locate the 'how to' documentation.SQLServerAgent service needs to run under a Windows account...|||Check your SQL Server connection settings in SQL Server Agent properties (Windows Auth. or SQL server Auth.).|||Thanks. I did not see the SQL agent connection properties with a login and password. All is now well.
Friday, February 10, 2012
Cannot Restart SQL Server Agent
This morning when I checked to see if my weekend database jobs ran, I notice
d that the SQL Server Agent was stopped. I tried to restart it several time
s to no avail. I even stopped the SQL Server and restarted it, but the Agen
t will not start. The erro
r log has the following message in it: [241] Startup error: Unable to i
nitialize error reporting system (reason: Access is denied). The setup of t
he database has not changed (Windows 2000 Server/SQL Server 2000). The agen
t and MSSQLServer both login us
ing the same domain account which is in the administrator's group on the box
. The account role is System Administrator in SQL Server.Hi,
Try to change the start up account for SQL Agent to
"Local system account" and try starting the service.
Thanks
Hari
MCDBA
"James_Privett" <anonymous@.discussions.microsoft.com> wrote in message
news:F6066C48-9689-44DA-BA5B-6585E20B7C99@.microsoft.com...
> This morning when I checked to see if my weekend database jobs ran, I
noticed that the SQL Server Agent was stopped. I tried to restart it
several times to no avail. I even stopped the SQL Server and restarted it,
but the Agent will not start. The error log has the following message in
it: [241] Startup error: Unable to initialize error reporting system
(reason: Access is denied). The setup of the database has not changed
(Windows 2000 Server/SQL Server 2000). The agent and MSSQLServer both login
using the same domain account which is in the administrator's group on the
box. The account role is System Administrator in SQL Server.|||Thanks Hari! That worked...but I have no clue why it stopped working after
3 months with no problems...?
d that the SQL Server Agent was stopped. I tried to restart it several time
s to no avail. I even stopped the SQL Server and restarted it, but the Agen
t will not start. The erro
r log has the following message in it: [241] Startup error: Unable to i
nitialize error reporting system (reason: Access is denied). The setup of t
he database has not changed (Windows 2000 Server/SQL Server 2000). The agen
t and MSSQLServer both login us
ing the same domain account which is in the administrator's group on the box
. The account role is System Administrator in SQL Server.Hi,
Try to change the start up account for SQL Agent to
"Local system account" and try starting the service.
Thanks
Hari
MCDBA
"James_Privett" <anonymous@.discussions.microsoft.com> wrote in message
news:F6066C48-9689-44DA-BA5B-6585E20B7C99@.microsoft.com...
> This morning when I checked to see if my weekend database jobs ran, I
noticed that the SQL Server Agent was stopped. I tried to restart it
several times to no avail. I even stopped the SQL Server and restarted it,
but the Agent will not start. The error log has the following message in
it: [241] Startup error: Unable to initialize error reporting system
(reason: Access is denied). The setup of the database has not changed
(Windows 2000 Server/SQL Server 2000). The agent and MSSQLServer both login
using the same domain account which is in the administrator's group on the
box. The account role is System Administrator in SQL Server.|||Thanks Hari! That worked...but I have no clue why it stopped working after
3 months with no problems...?
Subscribe to:
Posts (Atom)