March 21, 2007 at 10:39 am
This is an odd one.
The environment:
- 1 Server running Windows 2003 Server x64, SQL Server 2005 x64, SQL Server Management Studio (SSMS) version 9.00.2047.00.
- 1 Server running Windows 2003 Server x32, SQL Server 2005 x32, SSMS version 9.00.2047.00.
- 1 Server running Windows 2003 Server x32, SQL Server 2000 x32, SQL Server Enterprise Manager version 8.0.
- 2 Workstations running Windows XP – Svc Pk. 2, SSMS version 9.00.2047.00.
- 1 Workstation running Windows XP – Svc Pk. 2, SSMS version 9.00.1399.00.
- All machines have latest Microsoft patches, etc.
- All workstations are connected via SSMS to all three servers.
The problem:
When I attempt to open any SQL Agent job and view the job properties, SSMS opens a “New Job” window as though I had right-clicked on the Jobs folder and selected “New Job…” Regardless of what I try, including rebooting, when using SSMS from my workstation, I cannot view the properties of an existing job. SSMS will only open a New Job window.
This happens with all 3 servers, regardless of the SQL Server version and it happens on all 3 workstations. However, if I log onto the servers running SQL Server 2005 via Remote Desktop Connection and open SSMS on the server, I see all the existing job properties just as I would expect to. I suspect the bug has something to do with the March updates, but can’t put my finger on anything that seems like it might be related so that I’d know what to back out. It would seem that something that spans SQL Server and SSMS versions this completely would generate a lot of attention but I can’t find anything about it in spite of extensive searches. Aargh!
Has anyone else experienced or heard of this problem?
March 21, 2007 at 11:56 am
Make sure there is no access issue...
Looks like your SSMS got corrupted...Try unistall and resintalling work station componenst on the laptop...
March update means SP2 hotfix? I think that hotfix is related to MPs...
MohammedU
Microsoft SQL Server MVP
March 21, 2007 at 3:04 pm
Issue resolved.
Downloading and installing Service Pack 2 for SQL Server 2005 seems to have cured it, although I still don't know what caused it in the first place.
August 27, 2008 at 8:40 am
We have the same issue although reversed. When i used sql locally and connect to our db I can see everything as I would expect.
However, when RD into the prod server running sp2, sql 2005, i look at job properties and the name is gone, schedule is gone, all the necessary information, but the job monitor shows the jobs as running as scheduled.
as i said, your problem was solved with sp2 but we already have sp2 and have for a while. this issue just cropped up suddenly.
February 25, 2009 at 10:22 am
We had this issue in our environment recently, whereby the client tools were installed after SP2. We had to re-run the SP2 install to correct the issue.
September 11, 2009 at 1:50 pm
THANK U....THANK U.....THANK U
September 11, 2009 at 2:05 pm
This issue might arrise, when you have either installed SQL Server tools and sevice pack and top it it you install windows service pack or another hot fixes. you would need to install the SQl server pack on top of all the service packs... If i am correct
Maninder
www.dbanation.com
May 26, 2010 at 9:32 am
Having the same issue with SQL Server 2008. Only this happens on rdp sessions.
August 18, 2010 at 10:32 am
Hello, I found the same problem on my SQL Server 2005 SSMS, and I have installed SP3, and it works.
Thanks all.
October 12, 2010 at 1:24 pm
Thanks, this helped me, too.
October 19, 2011 at 8:23 am
Guys, i am kinda facing similar issue.
Can you please look at the post:
http://www.sqlservercentral.com/Forums/Topic1189494-391-1.aspx#bm1192580
and throw in some ideas.
Thanks
October 25, 2013 at 4:54 am
Hi
I had the same issue, only when i connected using RDP. For some reason, when i installed SP4 , my client tools like SSMS were not updated. I Just reisntall SP4 and everything is OK now.
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply