I have a couple of installs of SQL Server 2005 Express. One thing it doesn't provide is an agent to schedule jobs so I read where you can use Windows job scheduler to execute a batch job to in turn run a sqlcmd file. I have that working on one
server but on the other server I get the dreaded Name Pipes provider error and it goes on to talk about it may not be setup to allow remote connections. If I check using Surface Configurator it is set to allow remote connections using both tcpip and
named pipes. To my knowledge all I want it tcpip but I enabled named pipes in an effort to get things working.
About the only difference I can see is on the working system the database is a named instance (ie. Servername) versus default instance on the non-working system which shows up as (Servername\SQLEXPRESS). Hopefully I have my terminology right here.
Any tips on how to troubleshoot? Does it depend on the username I am using? Domain admin or local server admin or what have you?
I should mention I can execute the backup script and it does work. It is when I run the batch job that it fails.
The batch job just says "sqlcmd -i d:\MSSQL_Jobs\backup.sql -o d:\Logs\sqlbackup_output.txt"
View Complete Post