I don't use SQL Server 2005, but I vaguely remember from the Road Show
that remote access is turned off by default; perhaps the following web
link will help:

http://www.aquesthosting.com/HowTo/Sql2005/SQLError26.aspx

Stu

Hi all
I have taken on a project from another developer and am experiencing some
problems.
To give some background, the application was running smoothly (client talks
to web service, web service goes to database, web service returns data,
client displays data).
We then upgraded to SQL Server 2005. The machine is a new box.
Now when I run the application, if the web service is running on my local
machine, under localhost, I do not have a problem, if it is running on a
webserver, it does not seem to connect to the database at all.
A query accessing the database from the client application works fine, and a
trace shows it up.
When the web service queries the database, nothing appears in the trace on
the SQL Server box.
I am running in a mixed mode, Windows 2003 environment. The connection from
the web service is via a SQL login. I have setup delegation between the web
server and the SQL box. I have checked the permissions and these seem fine
(as testified by the fact that it works when the web service is running
locally)
Anyone have any thoughts? I'll try pretty much anything at the moment.

TIA
Saira

Thanks Stu
remote access is on for TCPIP and Named Pipes.
Any other thoughts?


[quoted text, click to view]

Hi Saira,

Do you not see any error in your application?

Are you sure the web server is pointing to the correct Sql box (i.e.
the one that you are tracing?)

Josh
http://www.thejoyofcode.com/