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