George,
Are you sure that the SQL Server is on the same machine as the Web server? It may easily have its own IP address.
Cheers,
Andrew
>Sylvain -
>
>>I'd guess the Enterprise Manager is trying to access the SQL Server via named pipes rather than TCP/IP.
>>
>>Start menu, Programs, Microsoft SQLServer 7, Client Network Utility
>>
>>In the General Tab, you can either select TCP/IP as the default network library (but your other registered SQLServer might stop working), or you can add a record for that server and specify to use TCP/IP.
>>
>>Hope this helps!
>>
>
>Thanks, it did help, but we are still not there.
>
>Now, we are getting an error of:
>
>
>A connection could not be established to {ServerName} - login failed for user '{UserName}'..
>
>Please verify SQL Server is running and check your SQL Server registration properties (by right-clicking on the {ServerName} node) and try again.
>
>
>Obviously, I have substituted {ServerName} and {UserName} for security reasons here.
>
>Any ideas? Did they give us the wrong password or user name perhaps?
>
>- George
If we were to introduce Visual FoxBase+, would we be able to work from the dotNet Prompt?
From Top 22 Developer Responses to defects in Software
2. "It’s not a bug, it’s a feature."
1. "I thought I fixed that."
All my FoxTalk and other articles are available on my
web site.
Unless specifically identified otherwise, anthing posted here is purely my opinion and may or may not reflect the policies or practices of Microsoft.
