I've been asked to make sure that the user account for running xp_cmdshell does not expire. Otherwise I find that I have to reboot the server(s) every 2 months or so.
Can anyone tell me where to check which user account is relevent to run this or where to check if the account expires.
The version of SQL is version 2000 and the servers are running Ms Windows Server 2003.
It's the SQL Server service account. Look in the services applet for this. Actually, in SQL 2000 you can see it in Enterprise Manager, by right-clicking the instance, go to properties.
Hi Russell The actual problem is that if I run any xp_cmdshell command it outputs : NULL When I reboot the server, it fixes this - this why I've been asked to check the SQL accounts. Obviously that can't be the cause.
Would you have any idea why this happens. We find that we have to reboot servers once every two or three months.
The above example using dir.exe is just an example to say that is should output something but if its doesn't then I'm not able to check why some of my companies bespoke exe's are not working and so can never get to the bottom of why the company exe's are not working.
Someone else has come back to me to try this :- http://support.microsoft.com/kb/824422 to increase the non-interactive desktop heap by 256 KB or by 512 KB
I followed this before but I wasn't convinced as server still got the same problem about 2 monthes later again.
Would you know if there is any way to not reboot after following this KB? to prove to myself that this fixes it.