If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > Microsoft SQL Server > Can't see job steps in 2005.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old
World Class Flame Warrior
 
Join Date: Jun 2003
Location: Ohio
Posts: 12,561
Can't see job steps in 2005.

I've created SQL Server Agent jobs through management studio on SQL Server 2005. I can view and edit these jobs when I am logged into the server via remote desktop, but when trying to administer these jobs through Management Studio on a different machine, the steps do not appear in the job properties window.
Anybody else see this behavior? Know why it occurs? Is it a bug, or another wonderful "feature" of Manglement Studio?
__________________
If it's not practically useful, then it's practically useless.

blindman
www.chess.com: "sqlblindman"
www.LobsterShot.blogspot.com
Reply With Quote
  #2 (permalink)  
Old
another indirection layer
 
Join Date: May 2004
Location: Seattle
Posts: 1,313
are the client tools on the other machine up to date?
__________________
elsasoft.org
Reply With Quote
  #3 (permalink)  
Old
World Class Flame Warrior
 
Join Date: Jun 2003
Location: Ohio
Posts: 12,561
Which client tools?
__________________
If it's not practically useful, then it's practically useless.

blindman
www.chess.com: "sqlblindman"
www.LobsterShot.blogspot.com
Reply With Quote
  #4 (permalink)  
Old
World Class Flame Warrior
 
Join Date: Jun 2003
Location: Ohio
Posts: 12,561
Code:
Microsoft SQL Server Management Studio		9.00.1399.00
Microsoft Analysis Services Client Tools	2005.090.1399.00
Microsoft Data Access Components (MDAC)		2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML					2.6 3.0 4.0 5.0 6.0 
Microsoft Internet Explorer			6.0.2900.2180
Microsoft .NET Framework			2.0.50727.832
Operating System				5.1.2600
__________________
If it's not practically useful, then it's practically useless.

blindman
www.chess.com: "sqlblindman"
www.LobsterShot.blogspot.com
Reply With Quote
  #5 (permalink)  
Old
Registered User
 
Join Date: Jan 2003
Location: Massachusetts
Posts: 5,470
I just applied SP2 to my laptop. Only client tools installed there;
Code:
Microsoft SQL Server Management Studio						9.00.3042.00
Microsoft Analysis Services Client Tools						2005.090.3042.00
Microsoft Data Access Components (MDAC)						2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML						2.6 3.0 4.0 5.0 6.0 
Microsoft Internet Explorer						6.0.2900.2180
Microsoft .NET Framework						2.0.50727.832
Operating System						5.1.2600
Not sure if that will fix the problem, but it can't hurt too much....I think
Reply With Quote
  #6 (permalink)  
Old
Registered User
 
Join Date: Aug 2005
Posts: 75
yeah, apply SP2 (actually, I make a habit of applying whatever SP and hotfixes on the server on my client machine). 9.00.1399.00 is the RTM version of SQL 2005 (and the Client tools). SP2 adds a lot of fixes (I actually apply the post-SP2 hotfix that revs it up to 3054).
Reply With Quote
  #7 (permalink)  
Old
World Class Flame Warrior
 
Join Date: Jun 2003
Location: Ohio
Posts: 12,561
So I take it nobody else is having this problem?
__________________
If it's not practically useful, then it's practically useless.

blindman
www.chess.com: "sqlblindman"
www.LobsterShot.blogspot.com
Reply With Quote
  #8 (permalink)  
Old
Registered User
 
Join Date: Aug 2005
Posts: 75
Quote:
Originally Posted by blindman
So I take it nobody else is having this problem?

not that exact issue, but I run into all sorts of issues when I'm trying to look at maintenance plans (the biggest one being that it won't let me save) and jobs if I'm using an RTM client on a SP2 server. From what I've read, there's a lot of stuff related to SQL Agent and the pieces that use it that has changed since RTM and SP2.
Reply With Quote
  #9 (permalink)  
Old
another indirection layer
 
Join Date: May 2004
Location: Seattle
Posts: 1,313
Quote:
Originally Posted by blindman
Which client tools?
I'd venture that this old build is to blame:

Microsoft SQL Server Management Studio 9.00.1399.00
__________________
elsasoft.org
Reply With Quote
  #10 (permalink)  
Old
Registered User
 
Join Date: Jan 2003
Location: Massachusetts
Posts: 5,470
Honestly, I have not tried to replicate the issue myself.
Reply With Quote
  #11 (permalink)  
Old
Registered User
 
Join Date: Aug 2005
Location: D/FW, Texas, USA
Posts: 78
I haven't had the exact same problem, but one that was similar. We had created jobs that used the Output file option for a logging on a couple of SSIS Steps. On machines that were running pre-SP2 clients all of the steps were there, but the options weren't all available. Once we upgraded the Client Tools on the offending machine, all of the steps had full options again.
__________________
--wayne
SELECT * FROM Users WHERE Clue>0
0 rows returned
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On