Link to home
Start Free TrialLog in
Avatar of lostboyinsofla
lostboyinsoflaFlag for United States of America

asked on

Invalid column name 'msx_job_id' (Microsoft SQL Server, Error: 207)

I am trying to create a maint. plan in SQL Server 2005 SP2.  I get the error below:

Maintenance Plan Wizard Progress

- Creating maintenance plan "MaintenancePlan1" (Success)

- Adding tasks to the maintenance plan (Success)

- Adding scheduling options (Error)
Messages
Adding scheduling options failed.

------------------------------
ADDITIONAL INFORMATION:

Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

------------------------------

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

------------------------------

Invalid column name 'msx_job_id'. (Microsoft SQL Server, Error: 207)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.3042&EvtSrc=MSSQLServer&EvtID=207&LinkId=20476
 

- Adding reporting options (Stopped)

- Saving maintenance plan "MaintenancePlan1" (Stopped)

Any ideas?
ASKER CERTIFIED SOLUTION
Avatar of Sirees
Sirees

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of lostboyinsofla

ASKER

I'm having trouble finding the log files.  Do you know where they are?
Ok I finally got the damn thing installed.  Still not sure what was wrong though.  Rebooted the server and it installed fine.
Avatar of MikeLenz
MikeLenz

this problem occurs if some of the stored procedures while installing SP2 has not been applied successfully. So we will manually run one of the stored procedure. And hopefully this issue will get resolved.

1)       First go to the folder Install . The default location is this = C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install  .
2)      Then in this folder find this sysdbupg.sql .
3)      Please open this script with a nodepad.
4)      Then copy the whole script and then paste it in the Query window of the Management studio.
5)      Then execute this script.
6)      Once this script has been successfully executed, The issue should be resolved.
Hi,
 
How safe is it to re-run the "sysdbupg.sql" script on a production SQL Server that has the same error?
I cannot create a maintenance plan either, get the same error. My verion is SP2, I think the person that used to manage the DB before failed to update it correctly.
Any thoughts?
Thanks.