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