Showing posts with label job. Show all posts
Showing posts with label job. Show all posts

Monday, March 19, 2012

cannot write logfile Error 1059 : Circular service dependency

I have a problem that looks like it has not been discussed before in
these groups.
I have a simple SQLAgent job that runs sp_who (could be anything, but
let's just say sp_who for this example). I have set the jobstep to
write to an output file "T:\out.txt". If the job is owned by an
admin, it runs fine and writes the output file. If it is owned by a
non-admin user, it gets the following error msg:
Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
service dependency was specified. The step failed.
I know about setting up the SQLAgent CMDExec proxy account, and have
done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy use
the same domain account, which is in the administrator group of the
local server. So, I know that security is not the issue.
When a simple job runs and writes to an output file, what service or
service group could it be trying to start or modify? I looked through
the list of Services, and could not find any circular dependencies.
Is there a utility to detect this? Why would running under one
context (as an admin) be ok while the other context (non-admin on SQL,
but using the same admin domain service account) fails?
Thanks in advance for any info you might have.
On Feb 13, 6:33 pm, donn...@.fastmail.fm wrote:
> I have a problem that looks like it has not been discussed before in
> these groups.
> I have a simple SQLAgent job that runs sp_who (could be anything, but
> let's just say sp_who for this example). I have set the jobstep to
> write to an output file "T:\out.txt". If the job is owned by an
> admin, it runs fine and writes the output file. If it is owned by a
> non-admin user, it gets the following error msg:
> Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
> service dependency was specified. The step failed.
> I know about setting up the SQLAgent CMDExec proxy account, and have
> done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy use
> the same domain account, which is in the administrator group of the
> local server. So, I know that security is not the issue.
> When a simple job runs and writes to an output file, what service or
> service group could it be trying to start or modify? I looked through
> the list of Services, and could not find any circular dependencies.
> Is there a utility to detect this? Why would running under one
> context (as an admin) be ok while the other context (non-admin on SQL,
> but using the same admin domain service account) fails?
> Thanks in advance for any info you might have.
Googling it returns:
Circular service dependency was specified.
Explanation:
An application tried to change the service dependency list for a
service. A check of the other service dependency lists in the service
database reveals at least one circular relationship between the
proposed new list and existing lists. For instance, service A must
start before service B in one list, but service B must start before
service A in another list. Your computer has not been configured
properly.
Do both accounts have the same permissions to the directory the file
is output to?
|||There is really only one account, because both SQLAgent and SQLAgent
cmdexec proxy (which is what is used when a non-admin runs a job)
both use this account, which is an admin on the local server. So,
yes, they both have the same permissions. SQLAgent seems to be trying
to start or modify some other service. I looked through services, and
could not find any circular dependencies.
On Feb 13, 9:48 pm, "Steve" <morrisz...@.hotmail.com> wrote:
> Googling it returns:
> Circular service dependency was specified.
> Explanation:
> An application tried to change the service dependency list for a
> service. A check of the other service dependency lists in the service
> database reveals at least one circular relationship between the
> proposed new list and existing lists. For instance, service A must
> start before service B in one list, but service B must start before
> service A in another list. Your computer has not been configured
> properly.
> Do both accounts have the same permissions to the directory the file
> is output to?>
|||Has anyone run into this problem?
I have a simple SQLAgent job that runs sp_who (could be anything, but
let's just say sp_who for this example). I have set the jobstep to
write to an output file "T:\out.txt". If the job is owned by an
admin, it runs fine and writes the output file. If it is owned by a
non-admin user, it gets the following error msg:
Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
service dependency was specified. The step failed.
I know about setting up the SQLAgent CMDExec proxy account, and have
done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy
use
the same domain account, which is in the administrator group of the
local server. So, I know that security is not the issue.
When a simple job runs and writes to an output file, what service or
service group could it be trying to start or modify? I looked
through
the list of Services, and could not find any circular dependencies.
Is there a utility to detect this? Why would running under one
context (as an admin) be ok while the other context (non-admin on
SQL,
but using the same admin domain service account) fails?
Thanks in advance for any info you might have.

cannot write logfile Error 1059 : Circular service dependency

I have a problem that looks like it has not been discussed before in
these groups.
I have a simple SQLAgent job that runs sp_who (could be anything, but
let's just say sp_who for this example). I have set the jobstep to
write to an output file "T:\out.txt". If the job is owned by an
admin, it runs fine and writes the output file. If it is owned by a
non-admin user, it gets the following error msg:
Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
service dependency was specified. The step failed.
I know about setting up the SQLAgent CMDExec proxy account, and have
done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy use
the same domain account, which is in the administrator group of the
local server. So, I know that security is not the issue.
When a simple job runs and writes to an output file, what service or
service group could it be trying to start or modify? I looked through
the list of Services, and could not find any circular dependencies.
Is there a utility to detect this? Why would running under one
context (as an admin) be ok while the other context (non-admin on SQL,
but using the same admin domain service account) fails?
Thanks in advance for any info you might have.On Feb 13, 6:33 pm, donn...@.fastmail.fm wrote:
> I have a problem that looks like it has not been discussed before in
> these groups.
> I have a simple SQLAgent job that runs sp_who (could be anything, but
> let's just say sp_who for this example). I have set the jobstep to
> write to an output file "T:\out.txt". If the job is owned by an
> admin, it runs fine and writes the output file. If it is owned by a
> non-admin user, it gets the following error msg:
> Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
> service dependency was specified. The step failed.
> I know about setting up the SQLAgent CMDExec proxy account, and have
> done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy use
> the same domain account, which is in the administrator group of the
> local server. So, I know that security is not the issue.
> When a simple job runs and writes to an output file, what service or
> service group could it be trying to start or modify? I looked through
> the list of Services, and could not find any circular dependencies.
> Is there a utility to detect this? Why would running under one
> context (as an admin) be ok while the other context (non-admin on SQL,
> but using the same admin domain service account) fails?
> Thanks in advance for any info you might have.
Googling it returns:
Circular service dependency was specified.
Explanation:
An application tried to change the service dependency list for a
service. A check of the other service dependency lists in the service
database reveals at least one circular relationship between the
proposed new list and existing lists. For instance, service A must
start before service B in one list, but service B must start before
service A in another list. Your computer has not been configured
properly.
Do both accounts have the same permissions to the directory the file
is output to?|||There is really only one account, because both SQLAgent and SQLAgent
cmdexec proxy (which is what is used when a non-admin runs a job)
both use this account, which is an admin on the local server. So,
yes, they both have the same permissions. SQLAgent seems to be trying
to start or modify some other service. I looked through services, and
could not find any circular dependencies.
On Feb 13, 9:48 pm, "Steve" <morrisz...@.hotmail.com> wrote:
> Googling it returns:
> Circular service dependency was specified.
> Explanation:
> An application tried to change the service dependency list for a
> service. A check of the other service dependency lists in the service
> database reveals at least one circular relationship between the
> proposed new list and existing lists. For instance, service A must
> start before service B in one list, but service B must start before
> service A in another list. Your computer has not been configured
> properly.
> Do both accounts have the same permissions to the directory the file
> is output to?>|||Has anyone run into this problem'
I have a simple SQLAgent job that runs sp_who (could be anything, but
let's just say sp_who for this example). I have set the jobstep to
write to an output file "T:\out.txt". If the job is owned by an
admin, it runs fine and writes the output file. If it is owned by a
non-admin user, it gets the following error msg:
Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
service dependency was specified. The step failed.
I know about setting up the SQLAgent CMDExec proxy account, and have
done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy
use
the same domain account, which is in the administrator group of the
local server. So, I know that security is not the issue.
When a simple job runs and writes to an output file, what service or
service group could it be trying to start or modify? I looked
through
the list of Services, and could not find any circular dependencies.
Is there a utility to detect this? Why would running under one
context (as an admin) be ok while the other context (non-admin on
SQL,
but using the same admin domain service account) fails?
Thanks in advance for any info you might have.

cannot write logfile Error 1059 : Circular service dependency

I have a problem that looks like it has not been discussed before in
these groups.

I have a simple SQLAgent job that runs sp_who (could be anything, but
let's just say sp_who for this example). I have set the jobstep to
write to an output file "T:\out.txt". If the job is owned by an
admin, it runs fine and writes the output file. If it is owned by a
non-admin user, it gets the following error msg:

Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
service dependency was specified. The step failed.

I know about setting up the SQLAgent CMDExec proxy account, and have
done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy use
the same domain account, which is in the administrator group of the
local server. So, I know that security is not the issue.

When a simple job runs and writes to an output file, what service or
service group could it be trying to start or modify? I looked through
the list of Services, and could not find any circular dependencies.
Is there a utility to detect this? Why would running under one
context (as an admin) be ok while the other context (non-admin on SQL,
but using the same admin domain service account) fails?

Thanks in advance for any info you might have.On Feb 13, 6:33 pm, donn...@.fastmail.fm wrote:

Quote:

Originally Posted by

I have a problem that looks like it has not been discussed before in
these groups.
>
I have a simple SQLAgent job that runs sp_who (could be anything, but
let's just say sp_who for this example). I have set the jobstep to
write to an output file "T:\out.txt". If the job is owned by an
admin, it runs fine and writes the output file. If it is owned by a
non-admin user, it gets the following error msg:
>
Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
service dependency was specified. The step failed.
>
I know about setting up the SQLAgent CMDExec proxy account, and have
done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy use
the same domain account, which is in the administrator group of the
local server. So, I know that security is not the issue.
>
When a simple job runs and writes to an output file, what service or
service group could it be trying to start or modify? I looked through
the list of Services, and could not find any circular dependencies.
Is there a utility to detect this? Why would running under one
context (as an admin) be ok while the other context (non-admin on SQL,
but using the same admin domain service account) fails?
>
Thanks in advance for any info you might have.


Googling it returns:
Circular service dependency was specified.
Explanation:
An application tried to change the service dependency list for a
service. A check of the other service dependency lists in the service
database reveals at least one circular relationship between the
proposed new list and existing lists. For instance, service A must
start before service B in one list, but service B must start before
service A in another list. Your computer has not been configured
properly.

Do both accounts have the same permissions to the directory the file
is output to?|||There is really only one account, because both SQLAgent and SQLAgent
cmdexec proxy (which is what is used when a non-admin runs a job)
both use this account, which is an admin on the local server. So,
yes, they both have the same permissions. SQLAgent seems to be trying
to start or modify some other service. I looked through services, and
could not find any circular dependencies.

On Feb 13, 9:48 pm, "Steve" <morrisz...@.hotmail.comwrote:

Quote:

Originally Posted by

Googling it returns:
Circular service dependency was specified.
Explanation:
An application tried to change the service dependency list for a
service. A check of the other service dependency lists in the service
database reveals at least one circular relationship between the
proposed new list and existing lists. For instance, service A must
start before service B in one list, but service B must start before
service A in another list. Your computer has not been configured
properly.
>
Do both accounts have the same permissions to the directory the file
is output to?>

|||Has anyone run into this problem??

I have a simple SQLAgent job that runs sp_who (could be anything, but
let's just say sp_who for this example). I have set the jobstep to
write to an output file "T:\out.txt". If the job is owned by an
admin, it runs fine and writes the output file. If it is owned by a
non-admin user, it gets the following error msg:

Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
service dependency was specified. The step failed.

I know about setting up the SQLAgent CMDExec proxy account, and have
done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy
use
the same domain account, which is in the administrator group of the
local server. So, I know that security is not the issue.

When a simple job runs and writes to an output file, what service or
service group could it be trying to start or modify? I looked
through
the list of Services, and could not find any circular dependencies.
Is there a utility to detect this? Why would running under one
context (as an admin) be ok while the other context (non-admin on
SQL,
but using the same admin domain service account) fails?

Thanks in advance for any info you might have.

cannot write logfile Error 1059 : Circular service dependency

I have a problem that looks like it has not been discussed before in
these groups.
I have a simple SQLAgent job that runs sp_who (could be anything, but
let's just say sp_who for this example). I have set the jobstep to
write to an output file "T:\out.txt". If the job is owned by an
admin, it runs fine and writes the output file. If it is owned by a
non-admin user, it gets the following error msg:
Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
service dependency was specified. The step failed.
I know about setting up the SQLAgent CMDExec proxy account, and have
done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy use
the same domain account, which is in the administrator group of the
local server. So, I know that security is not the issue.
When a simple job runs and writes to an output file, what service or
service group could it be trying to start or modify? I looked through
the list of Services, and could not find any circular dependencies.
Is there a utility to detect this? Why would running under one
context (as an admin) be ok while the other context (non-admin on SQL,
but using the same admin domain service account) fails?
Thanks in advance for any info you might have.On Feb 13, 6:33 pm, donn...@.fastmail.fm wrote:
> I have a problem that looks like it has not been discussed before in
> these groups.
> I have a simple SQLAgent job that runs sp_who (could be anything, but
> let's just say sp_who for this example). I have set the jobstep to
> write to an output file "T:\out.txt". If the job is owned by an
> admin, it runs fine and writes the output file. If it is owned by a
> non-admin user, it gets the following error msg:
> Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
> service dependency was specified. The step failed.
> I know about setting up the SQLAgent CMDExec proxy account, and have
> done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy use
> the same domain account, which is in the administrator group of the
> local server. So, I know that security is not the issue.
> When a simple job runs and writes to an output file, what service or
> service group could it be trying to start or modify? I looked through
> the list of Services, and could not find any circular dependencies.
> Is there a utility to detect this? Why would running under one
> context (as an admin) be ok while the other context (non-admin on SQL,
> but using the same admin domain service account) fails?
> Thanks in advance for any info you might have.
Googling it returns:
Circular service dependency was specified.
Explanation:
An application tried to change the service dependency list for a
service. A check of the other service dependency lists in the service
database reveals at least one circular relationship between the
proposed new list and existing lists. For instance, service A must
start before service B in one list, but service B must start before
service A in another list. Your computer has not been configured
properly.
Do both accounts have the same permissions to the directory the file
is output to?|||There is really only one account, because both SQLAgent and SQLAgent
cmdexec proxy (which is what is used when a non-admin runs a job)
both use this account, which is an admin on the local server. So,
yes, they both have the same permissions. SQLAgent seems to be trying
to start or modify some other service. I looked through services, and
could not find any circular dependencies.
On Feb 13, 9:48 pm, "Steve" <morrisz...@.hotmail.com> wrote:
> Googling it returns:
> Circular service dependency was specified.
> Explanation:
> An application tried to change the service dependency list for a
> service. A check of the other service dependency lists in the service
> database reveals at least one circular relationship between the
> proposed new list and existing lists. For instance, service A must
> start before service B in one list, but service B must start before
> service A in another list. Your computer has not been configured
> properly.
> Do both accounts have the same permissions to the directory the file
> is output to?>|||Has anyone run into this problem'
I have a simple SQLAgent job that runs sp_who (could be anything, but
let's just say sp_who for this example). I have set the jobstep to
write to an output file "T:\out.txt". If the job is owned by an
admin, it runs fine and writes the output file. If it is owned by a
non-admin user, it gets the following error msg:
Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
service dependency was specified. The step failed.
I know about setting up the SQLAgent CMDExec proxy account, and have
done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy
use
the same domain account, which is in the administrator group of the
local server. So, I know that security is not the issue.
When a simple job runs and writes to an output file, what service or
service group could it be trying to start or modify? I looked
through
the list of Services, and could not find any circular dependencies.
Is there a utility to detect this? Why would running under one
context (as an admin) be ok while the other context (non-admin on
SQL,
but using the same admin domain service account) fails?
Thanks in advance for any info you might have.

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 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

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

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

cannot view job properties. i keep getting "new job" dialog box.

In my installation of sql server 2005, i cannot view any job properties. when i doubble click on a job, i just get the "new job" dialog box. when i right click on a job and select properties, i also get the "new job" dialog box. i have reinstalled sql server workstation components and restarted but it did not fix the issue. anyone ever have this issue

post back the Service Pack in this box

Madhu

|||

i reinstalled sql server completely and it works now. pitty i had to waste so much time doing that. have no idea why it would do what it done. no updates or serivce packs added in weeks and it has worked fine for the last ages.|||

I've seen this error a few times. It has to do with one of the Visual Studio installs or service packs on the PC you are using to view the job properties. Applying SQL Server service pack 2 fixes the problem.

-Sue

|||

Also it may be issue with client tools on this machine, see whether you can reproduce from another machine with similar tools.

|||

Exact same scenario here. I was hoping for a nice clean fix but I guess this one is going to be painful.

|||What service pack of the tools do you have? Did it just start happening or is it an ongoing problem? Did anything change on the server or client?

|||It just started happening. I did install sp2 for sql but that was many weeks ago and it had been working fine. it was just a sudden thing. i was using it one morning and it was fine, and that afternoon it all went pear shaped.
|||Hmmm, nothing in the error log for the machine? And re-applying sp2 to the tools didn't fix it? (i.e. it wasn't a broken DLL somewhere)?

|||

I have the same problem:

SQL Server 2005 sp2 X64 clustered. There are no messages in any of the error logs. I did find this when I traced the server when I tired to view the properties of a job.

Cannot drop the table '#tmp_sp_db_vardecimal_storage_format', because it does not exist or you do not have permission.

I am a sysadmin. I just set this server up.

Thanks,

|||I reinstalled SQL Server SP 2 twice and it seemed to fix the problem Smile

|||

You need to reapply SP2. Just having SP2 installed doesn't mean it's protected from this issue. I've dealt with this one a few times - One of the dlls gets overwritten. I've seen it when SP2 was already installed and reapplying the service pack fixes the issue.

-Sue

|||

I had this same problem and I had to install SQL Server 2005 SP 2 twice and that seem to fix the problem.

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:
>

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:

Sunday, February 12, 2012

Cannot run job created by SMO

I've create a SQL Agent job using C# SMO to process an Analysis Service Database (see code below). When I tried to start job from Management Studio, I get the following error message...any ideas?

TITLE: Microsoft.SqlServer.Smo

Start failed for Job 'Schedule Job OLAPProj'.

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1314.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Start+Job&LinkId=20476


ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

Cannot start the job "Schedule Job OLAPProj" (ID 089BEE15-B060-466E-B59E-7F7DAB1EB8DB) because it does not have any job server or servers defined. Associate the job with a job server by calling sp_add_jobserver. (Microsoft SQL Server, Error: 14256)



Common.ServerConnection l_oServerConn = new Common.ServerConnection();

l_oServerConn.ServerInstance = txtServer.Text;

l_oServerConn.LoginSecure = true;

l_oServerConn.Connect();

Smo.Server l_oServer = new Smo.Server(l_oServerConn);

Agent.Job l_oJob = new Agent.Job(l_oServer.JobServer, "Schedule Job " + cboDB.Text);

l_oJob.IsEnabled = true;

l_oJob.Description = "Schedule Job Processing OLAP Cube: " + cboDB.Text;

l_oJob.OwnerLoginName = @."NT AUTHORITY\SYSTEM";

l_oJob.Create();

Agent.JobStep l_oJobStep = new Agent.JobStep(l_oJob, "Process " + cboDB.Text);

l_oJobStep.SubSystem = Agent.AgentSubSystem.AnalysisCommand;

string l_sCmd = @."<Process xmlns=""http://schemas.microsoft.com/analysisservices/2003/engine"">";

l_sCmd = l_sCmd + "<Object><DatabaseID>" + cboDB.Text + "</DatabaseID></Object><Type>ProcessFull</Type>";

l_sCmd = l_sCmd + "<WriteBackTableCreation>UseExisting</WriteBackTableCreation></Process>";

l_oJobStep.Command = l_sCmd;

l_oJobStep.Server = txtServer.Text;

l_oJobStep.DatabaseName = @."master";

l_oJobStep.JobStepFlags = Agent.JobStepFlags.AppendToJobHistory;

l_oJobStep.OnSuccessAction = Agent.StepCompletionAction.QuitWithSuccess;

l_oJobStep.OnFailAction = Agent.StepCompletionAction.QuitWithFailure;

l_oJobStep.Create();


I have posted a sample here, which should clarify this. Please let me know if you have further issues after reading the sample.

|||Based on your sample, I've added the following which seemed to do the trick:

l_oJob.ApplyToTargetServer("(local)");

Initially I use "localhost\yukon" which is name of my instance but that failed and "(local)" worked. Thanks.