Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
timmy
Master Smack Fu Yak Hacker
1242 Posts |
 Posted - 2007-04-12 : 21:19:47
|
| Hi all, We have an issue on one of our production boxes where we're unable to change the step type on our jobs. When you Edit Job Step, then click on the Type combo, the currently selected type is the only option available. We are able to change the step type on our dev server with no problems. Can anyone enlighten me on why this might be happening?Cheers,Tim |
|
|
SQLServerDBA_Dan
Aged Yak Warrior
752 Posts |
Posted - 2007-04-13 : 10:00:42
|
| O.o That looks like this topic posted yesterday: http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=82004.Have you tried to run: exec sp_enum_sqlagent_subsystems?Seems strange that two people post this back to back. Did you just install any new hotfixes or service packs?There are also registry keys for the types :HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\SQLServerAgent\Subsystems |
 |
|
|
YogeshDesai
Posting Yak Master
136 Posts |
Posted - 2007-04-16 : 02:43:26
|
| Hi Tim, We both are facing same problem.If you get any solution Please share with me.Yogesh V. Desai. | SQLDBA| |
|
|
|
SQLServerDBA_Dan
Aged Yak Warrior
752 Posts |
Posted - 2007-04-16 : 10:08:38
|
quote:
Originally posted by YogeshDesai
Hi Tim, We both are facing same problem.If you get any solution Please share with me.Yogesh V. Desai. | SQLDBA|
And you said you cannot browse to the keys via regedit or regedt32? |
|
|
|
SQLServerDBA_Dan
Aged Yak Warrior
752 Posts |
Posted - 2007-04-16 : 10:15:58
|
| I did find this but it has to do with 2005.http://www.sqljunkies.com/Forums/ShowPost.aspx?PostID=9920SQL Server 2005 - Failure Creating Maintenance PlansThe specified '@subsystem' is invalid (valid values are returned by sp_enum_sqlagent_subsystems). (Microsoft SQL Server, Error: 14234) Am I getting less tolerate or are the error messages getting worse? I think all software suffers from this as it gets more complex it just is harder to give useful messages. This turned out to simply be Integration Services was not installed on the particular SQL Server. This happens on internal software too. How as software continues to get more complex do we give better error messages that keep users of our software and support staff from chasing their tails?This seems to be a common issue when a cluster is setup the first time on SQL 2005. You can read more about the error here on SQL Junkies – Thanks to their forum for heading me to the right place to fix!Did you try to install 2005? |
|
|
|
timmy
Master Smack Fu Yak Hacker
1242 Posts |
Posted - 2007-04-16 : 20:49:10
|
| An update on this one:With info from the other post, I've been able to isolate the registry read statement that's causing the problem. On the server in question I've opened the registry and can't get to the key HKLM\SOFTWARE\Microsoft\MSSQLServer\SQLServerAgent\SubSystems ("error while opening key"). Fair enough. Registry maybe corrupted.But here's the thing: We have another UAT server with 2 instances of SQL on it. The registry key is visible from Regedit and I can see the correct subsystems. On one of the instances the job steps are returning correctly whereas the other one doesn't. Don't know if it makes a difference, but the default instance is the one that works correctly.Will keep digging, but thought I'd update with my progress...Cheers,Timbtw - There have been no recent SP's that I'm aware of, but this problem has been around for a while because one of the other developers has seen it before on that server. |
|
|
|
YogeshDesai
Posting Yak Master
136 Posts |
Posted - 2007-04-20 : 11:28:54
|
| My problem is solved after restartYogesh V. Desai. | SQLDBA| |
|
|
|
timmy
Master Smack Fu Yak Hacker
1242 Posts |
Posted - 2007-04-22 : 21:23:28
|
| Mine too. Although I wouldn't really say it's 'solved'. More 'postponed' |
|
|
|
|
|
|
|
|
SQL Agent Job - can't change step type