DB Maintenance Plans (SQL 7.0) Error 207 1

[LF4055]

Hi,

I am a newbie to this site. I did search the archieves as well as my MSDN Library and the SQL books online and cannot seem to find the answer to my problem. I do however know it has been seen by others and there is a solution but I cannot seem to find this solution. I truly hope someone here can point me in the right direction.

We have an SQL 7.0 server with SP3 running on NT 4.0 with SP6.0a. When I try a click on the my DB maintenance plan I get the following error:

Microsoft SQL-DMO (ODBC SQL State: 42S22)

Error 207: Invalid column name 'category_id'
Invalid column name 'netsend_address'
Invalid column name 'last_netsend_date'
Invalid column name 'last_netsend_time'

The actual maintenance plan works fine, although it will not allow me to view the properties.

Any help with this would be greatly appreciated. I have been searching for a solution for a long time now with no success.

Thank you
LFawcett

 

[tlbroadbent]

Is the login you are using a system adminstrator? If not, have you tried to view the jobs using a SA login? Can you view the jobs with an SA login?

The columns listed as invalid should exist in msdb..sysoperators. Does the sysoperators table exist in msdb? If it doesn't exist you'll need to restore it from a backup.

If it exists, can you query it using the same login you are using to view the job? Do the columns in question exist on the table? If not you'll need to restore the table.

If you can see the columns, the problem may be in one of the stored procedures that Enterprise Manager uses when viewing and updating jobs. It may be necessary for you to restore a backup of msdb to replace a corrupted SP.

Good luck. Terry

http://members.home.net/tlbroadbent/index.htm

 

[Bernadette]

Hi There

Do you have permissions on the tables that these columns belong do, for the login that you are using ? Hope This Helps
Bernadette

 

[LF4055]

Hi Terry,

Thank you for your information it was what I needed to know. I do have all the proper permissions that was not an issue here. This server was upgraded from 6.5 to 7.0 and for some reason the msdb...sysoperators was missing the 4 fields I mentioned. I have another SQL 7.0 running with no problems I checked the msdb...sysoperators table from this server and re-created the missing fields on the server with the missing tables. It works fine now I have been looking at this error for a long time. I thank you again for the information it was of great help to me.

Linda