Can't Edit Job in SSMS

We just started having a problem where when we right click on a job in SSMS
and select properties, it doesn't go to Edit Job, it just opens a New Job
window that is all blank. It is happening on several workstations, but not
when we use SSMS on the actual server.
Is this a known issue?Yes, I believe it was fixed with SP2. Get your clients up to date.
"Dan" <dantheriver@.newsgroup.nospam> wrote in message
news:B15DE092-1E07-4D30-A213-C7BA70912629@.microsoft.com...
> We just started having a problem where when we right click on a job in
> SSMS
> and select properties, it doesn't go to Edit Job, it just opens a New Job
> window that is all blank. It is happening on several workstations, but not
> when we use SSMS on the actual server.
> Is this a known issue?|||Hi,
It is hard to say that this is a known issue only according to the issue
appearance. However I do agree with Aaron on that you should install SQL
Server 2005 SP2 first to see if this issue can be resolved. SQL Server 2005
SP2 has many hotfixes for SSMS. You can run SELECT @.@.VERSION to check if
your SQL Server 2005 is with SP2. If the value is less than 9.0.3042, it
indicates that SP2 is not installed.
You can download SQL Server 2005 SP2 from the following link:
http://www.microsoft.com/downloads/details.aspx?FamilyId=d07219b2-1e23-49c8-
8f0c-63fa18f26d3a&displaylang=en
If you have any other questions or concerns, please feel free to post back.
We are very glad to assist you further.
Have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||> SP2 has many hotfixes for SSMS. You can run SELECT @.@.VERSION to check if
> your SQL Server 2005 is with SP2.
Remember that some of the clients may only have the tools installed, so
running @.@.VERSION (against the only server they connect to) is misleading...
the server may very well respond 9.00.3042 while their local tools are in
fact still at 9.00.1399. So they should check Help|About to make sure their
client tools are up to date.|||Yes, Aaron, you have a more considerate thinking. It is the best practice
for checking the tool's version.
Thank you!
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================