March 4, 2008 at 5:14 pm
We have updated to SP2 with SQL 2005 Server managment studio
i have also applied the post sp2 fixes and still iam receiving errors under management- maitenance plans
iam seeing this-
Failed to recieve data for this request (microsoft.sqlserver.SmoEnum)
An exception occured while excuting a Transact-SQL statement or batch. (microsoft.sqlserver.connection.info)
Invalid column name'from msx', invalid column name 'has targets'. (Microsoft SQL Server, Error: 207)
Any ideas?? any help would be very much appreciated.
the version we are running is 9.00.3159
March 5, 2008 at 4:15 pm
anyone?
March 6, 2008 at 6:38 am
I don't use maintenance plans much ... but it looks like whatever your step is doing, need to bracket the table names as they have spaces ...
[from msx]
[has targets]
March 7, 2008 at 6:24 am
Is both the server and your management studio instance on service pack2 and have you also applied kb933508? You should be at release 9.0.3050 at the very least for the server and for management studio I am at 9.0.3042 on my laptop. Since you are dealing with Maint plans that is the minimum you should be at.
Did you use the scripting tools and/or wizards to create your maint plans or did you script them out?
March 18, 2008 at 7:01 am
Have the same problem. Has you solved?
September 22, 2008 at 4:13 am
I too have same problem!!!
I'm on SQL 2005 Dev edition SP2 build 9.00.3068.00 and I use wizard to create a maintenance plan
September 22, 2008 at 4:47 am
Hi
The problem seems to be fixed atleast for me!!!
The reason for this error is that the Resource Database had not been upgraded to the SP2 version 9.00.3068.00. It was still 9.00.1399. No errors were picked up in the SP2 installation logs. They reported a successful installation/upgrade.
This is a SQL2005 SP2 bug and is resolved in SP3.Although SP3 for 2005 has been officially announced, it is not due to be release soon.
A quick way to tell this is to run the following SQL statement that will tell you the ResourceDB version, when it was last updated and the SQL ServerVersion. The SQL Server Version should be the same as ResourceDB:
SELECT SERVERPROPERTY('ResourceVersion') as ResourceDB, SERVERPROPERTY('ResourceLastUpdateDateTime') as ResourceDBLastUpdate,
SERVERPROPERTY('ProductVersion') as Ver, SERVERPROPERTY ('ProductLevel') as SP;
GO
A workaround for this is :
Run the "sysdbupg" script and it can be found in
"C:\Program Files\Microsoft SQL Server\ MSSQL\Install"
e.g C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install
You will need to open it using notepad and then copy the script into the query editor and execute it.
This fixed the problem for me.
HTH.
Thanks
K
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply