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

|||

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.