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 |
|
YogeshDesai
Posting Yak Master
136 Posts |
 Posted - 2007-04-12 : 09:23:53
|
| Presently we are facing some strange issue related to SQL server jobs. We found that the list of “type” is only showing the “Transact-SQL script(TSQL)” Other options are not visible. On further investigation after running the stored proc exec sp_enum_sqlagent_subsystems in MSDB database returning only a single record.This ideally should return below given rowsActiveScripting Active Scripting SubsystemCmdExec Command-Line SubsystemDistribution Replication Distribution SubsystemLogReader Replication Transaction-Log Reader SubsystemMerge Replication Merge SubsystemQueueReader Replication Transaction Queue Reader SubsystemSnapshot Replication Snapshot SubsystemTSQL Transact-SQL SubsystemBut the actual output is TSQL Transact-SQL SubsystemThe subsystem type in the sysjobsteps is still stored as CmdExec for old jobs. When you try to create a new job you won’t get this option in the drop box as mentioned earlier. When open the job steps it won’t show the CmdExec option it is automatically changed to TSQL. The supporting DLL files [ SQLATXSS.DLL, SQLCMDSS.DLL, SQLREPSS.DLL] are exists in the C:\Program Files (x86)\Microsoft SQL Server\MSSQL\Binn folder.This procedure fetches data from windows registry. When I tried to open the SQL Server agent Key from the windows registry id thrown the below given error" Cannot open Sql Server Agent:Error while opening key"Kindly suggest the method to make those options available. Few of our jobs are directly running by CmdExec options.Yogesh V. Desai. | SQLDBA| |
|
|
YogeshDesai
Posting Yak Master
136 Posts |
Posted - 2007-04-16 : 02:36:44
|
| No one have solution for this ? any body suggest any other resoures to searchYogesh V. Desai. | SQLDBA| |
 |
|
|
|
|
|
problem with exec sp_enum_sqlagent_subsystems