cmdexec subsystem failure

have a scheduled job that has been running fine for 2 years, but this week I keep getting the following error:

0x469A75B7998F8142A910FA7E9983CCDF

has caused an exception in the CmdExec subsystem and has been terminated.

the enterprise manager shows that the job failed, but the app still shows up in task manager.

the .cmd file has a single step in it that calls the .exe file and does an "if errorlevel = 1" option that displays an error message.

if I run the .exe file outside of enterprise manager, it runs just fine.

I searched around on microsoft.com and the only reference to this error I could find was a but that was fixed in Sql Server 6.5. I am running SQL Server 2000, the server that is running the apps has Windows 2000 Advanced Server installed.

does anyone have any suggestions?

Thanks

I too have been receiving this same error and have not been able to find a soloution. Any help out thier in microsoft land?

Gary

|||

Can one of you pass on the job details and that can help us to narrow down the issue ?

Also, please do mention the OS environment and SP of SQL Server so we can try on the same settings in our lab ?

Thanks,

Gops Dwarak

|||

The job that is running is a series of COBOL programs, you would not be able to duplicate the exact process.

the OS is Win 2000 Advanced Server SP 4 build 295

SQL Server 2000 SP 3

Enterprise Mgr is build 2195 SP 4

it is running a .cmd file that has 4 steps in it. the problem usually happens in step 2 which is a Large Cobol Program.

even on reruns of the same exact input file, it happens in different places(so it is not bad data or a size issue)

cmdexec subsystem failure

have a scheduled job that has been running fine for 2 years, but this week I keep getting the following error:

0x469A75B7998F8142A910FA7E9983CCDF

has caused an exception in the CmdExec subsystem and has been terminated.

the enterprise manager shows that the job failed, but the app still shows up in task manager.

the .cmd file has a single step in it that calls the .exe file and does an "if errorlevel = 1" option that displays an error message.

if I run the .exe file outside of enterprise manager, it runs just fine.

I searched around on microsoft.com and the only reference to this error I could find was a but that was fixed in Sql Server 6.5. I am running SQL Server 2000, the server that is running the apps has Windows 2000 Advanced Server installed.

does anyone have any suggestions?

Thanks

I too have been receiving this same error and have not been able to find a soloution. Any help out thier in microsoft land?

Gary

|||

Can one of you pass on the job details and that can help us to narrow down the issue ?

Also, please do mention the OS environment and SP of SQL Server so we can try on the same settings in our lab ?

Thanks,

Gops Dwarak

|||

The job that is running is a series of COBOL programs, you would not be able to duplicate the exact process.

the OS is Win 2000 Advanced Server SP 4 build 295

SQL Server 2000 SP 3

Enterprise Mgr is build 2195 SP 4

it is running a .cmd file that has 4 steps in it. the problem usually happens in step 2 which is a Large Cobol Program.

even on reruns of the same exact input file, it happens in different places(so it is not bad data or a size issue)

cmdexec subsystem failure

I have a scheduled job that has been running fine for 2 years, but this week I keep getting the following error:

0x469A75B7998F8142A910FA7E9983CCDF

has caused an exception in the CmdExec subsystem and has been terminated.

the enterprise manager shows that the job failed, but the app still shows up in task manager.

any suggestions?

thanks

What does the job do?

What technology is it calling?

If its been running 2 years then I doubt you're calling SSIS hence this is the wrong forum for you.

-Jamie

Clustering failure on install

Hi,

Where can I post issues with SQL 2005 clustering. Is there any prereq that needs to be followed before installing SQL 2005 on a windows cluster?

Thanks

go here http://msdn2.microsoft.com/en-us/library/ms189910.aspx|||

You can certainly post here about any clustering issues you may encounter. The SQL Server 2005 Failover Clustering whitepaper will be released soon (and has full install instructions with screen captures). As far as prereqs, the link that was provided is good. But make sure that your Windows level cluster is rock solid and tested before installing SQL Server. The security is a bit different with SQL Server 2005 failover clustering, so pay attention to that.

Other than that, the install itself is straightforward. No real gotchas there except all nodes do not get the full compliment of client tools. If you install the client tools, they will only go on the server which initiated the install and you will need to install them on the other nodes. If you do not need the full compliment of admin tools on eachnode, then you don't have to worry about it.

If you want even more, the Apress book SQL Server 2005 High Availability is due out later this year. The book covers clustering both Windows (from a SQL perspective) & SQL - not just the SQL piece. It is spread out over two chapters and should be 250 - 300 pages for those two chapters alone.

|||adminup, did the article help?|||

Thanks It helped.

Th eonly other question is that before installing the SQL cluster do we need to configure the MSDTC or is there any prereq required after the Windows 2003 cluster is setup?

|||Yes, you should configure the clustered DTC prior to installing SQL Server as per http://support.microsoft.com/kb/301600/en-us and http://support.microsoft.com/kb/817064/en-us.|||

Hi Thanks while actually installing i get this error message I have checked the windows scheduling and it is started.

setup failed to start on the remote machine. Check the task scheduler event log on the reote machine

Why I am getting this error

|||If your other node or nodes do not have access to the CD-ROM or install point, that is a likely cause of this. It could also be a missed configuration step in the preparation, but it's most likely access to the install bits.|||

Thanks it was a share from a remote machine. Now the setup is fine I can SQL directories created on both the machine however it fails on database install there is no error log that corresponds to this.

I have enabled MSDTC and all the prereq but still the setup fails at the database creation points.

Any ideas?

Anup

|||sql setup log might give some clues as why it fails.|||

As OJ says, the logs should be telling and are VERY descriptive in SQL Server 2005.What part of the DB install does it choke on?

|||Thanks I figured it out it was probably a share from network drive to MSDTC service accont which was causing this but all well now set up completed thanks for all the help|||

I had the similar error on 64 bit STD edition installation of default instance , with another named instance already installed without any issues.I had to go ask the Task manager to interact with desktop on but the servers and restart the tast manger service in both. I am still not sure why does the TM needs to interact with desktop on the other (non installation passive node ).

Clustering failure on install

Hi,

Where can I post issues with SQL 2005 clustering. Is there any prereq that needs to be followed before installing SQL 2005 on a windows cluster?

Thanks

go here http://msdn2.microsoft.com/en-us/library/ms189910.aspx|||

You can certainly post here about any clustering issues you may encounter. The SQL Server 2005 Failover Clustering whitepaper will be released soon (and has full install instructions with screen captures). As far as prereqs, the link that was provided is good. But make sure that your Windows level cluster is rock solid and tested before installing SQL Server. The security is a bit different with SQL Server 2005 failover clustering, so pay attention to that.

Other than that, the install itself is straightforward. No real gotchas there except all nodes do not get the full compliment of client tools. If you install the client tools, they will only go on the server which initiated the install and you will need to install them on the other nodes. If you do not need the full compliment of admin tools on eachnode, then you don't have to worry about it.

If you want even more, the Apress book SQL Server 2005 High Availability is due out later this year. The book covers clustering both Windows (from a SQL perspective) & SQL - not just the SQL piece. It is spread out over two chapters and should be 250 - 300 pages for those two chapters alone.

|||adminup, did the article help?|||

Thanks It helped.

Th eonly other question is that before installing the SQL cluster do we need to configure the MSDTC or is there any prereq required after the Windows 2003 cluster is setup?

|||Yes, you should configure the clustered DTC prior to installing SQL Server as per http://support.microsoft.com/kb/301600/en-us and http://support.microsoft.com/kb/817064/en-us.|||

Hi Thanks while actually installing i get this error message I have checked the windows scheduling and it is started.

setup failed to start on the remote machine. Check the task scheduler event log on the reote machine

Why I am getting this error

|||If your other node or nodes do not have access to the CD-ROM or install point, that is a likely cause of this. It could also be a missed configuration step in the preparation, but it's most likely access to the install bits.|||

Thanks it was a share from a remote machine. Now the setup is fine I can SQL directories created on both the machine however it fails on database install there is no error log that corresponds to this.

I have enabled MSDTC and all the prereq but still the setup fails at the database creation points.

Any ideas?

Anup

|||sql setup log might give some clues as why it fails.|||

As OJ says, the logs should be telling and are VERY descriptive in SQL Server 2005.What part of the DB install does it choke on?

|||Thanks I figured it out it was probably a share from network drive to MSDTC service accont which was causing this but all well now set up completed thanks for all the help|||

I had the similar error on 64 bit STD edition installation of default instance , with another named instance already installed without any issues.I had to go ask the Task manager to interact with desktop on but the servers and restart the tast manger service in both. I am still not sure why does the TM needs to interact with desktop on the other (non installation passive node ).

Clustering

If i have an active\passive cluster for SQL Server, under what circumstances would it prompt to automatic changeover to the passive cluster ? Failure of the SQL Server, or let's say 1 user database out of 25 becomes suspect?It would require a failure of the entire SQL Server. Individual databases can be brought online and offline all throughout the day. A failover is only done when one of the cluster resources has failed.