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 |
|
a_janderson
Starting Member
2 Posts |
 Posted - 2009-08-21 : 11:17:58
|
| Hello I am new to the forum but need some advice: I have a Server 2k3 machine that previously had SQL Server 2008 Express on it but our enterprise uses SQL 2005. I uninstalled 2008 Express and installed SQL Server 2005 (enterprise edition) but now I am getting errors that it can't allow xp_cmdshell and am not able to set up sql mail. I am wanting to avoid rebuilding this machine and would appreciate any assistance I can be given. Thank you in advanceEvolve or get left... |
|
|
juancabrera
Starting Member
30 Posts |
Posted - 2009-08-21 : 12:45:37
|
| There is definitely no reason to rebuild the machine. All you have to do is:On SQL Server Surface Aread Configuration --> Surface Area Configuration for Features --> Select SQL Instance Node --> Under this node Select the xp_cmdshell node and enable it by checking the checkbox.I don't recommend using SQL Mail because this feature has been depracated. You are better off using Database Mail. Also xp_cmdshell is not recommended beacause of the security risks that it posses. |
 |
|
|
a_janderson
Starting Member
2 Posts |
Posted - 2009-08-21 : 17:16:59
|
| Just one quick update...here is the error that we are getting in regard to the xp_command shell: Could not load file or assembly 'Microsoft.SqlServer.BatchParser, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified. (Microsoft.SqlServer.ConnectionInfo). To assure that the obvious isn't stated, the file is definitely in the correct directory(c:\windows\assembly). Also we are using Database Mail, I mispoke when I referenced SQL Mail...I will include the error shortly...Evolve or get left... |
|
|
|
juancabrera
Starting Member
30 Posts |
Posted - 2009-08-21 : 17:32:40
|
| On MSDB run the following query:select * from msdb.dbo.syssubsystemsMake sure that all the subystem_dll are pointing to the correct path/filename. |
|
|
|
|
|
|
Error Rolling back to 2005 from 2008