However, I don't get an additional check box described in the post about a Vista user getting the same error. I am not able to continue.

In the Stratatrain documentation, in the troubleshooting area, I saw the link about changing the named pipes string in SQl Server Config Mgr, under Network Configuration. We have named pipes enabled for SQL Native Client Configuration, and another user was able to install with no problems. We do not have Named Pipes enabled for the Network Config.

I am running XP, SQL 2005 and have the sql native client installed. I also did a repair on the sql native client, just in case.

Anybody know what is going on?

Thanks,

Lori Markle

If you are running Windows XP then you are having a legitimate authentication issue within the installation. So it is good you did not continue as you would have other issues down the road.

If you are running SQL Server 2005 Express, then more than likely you are running a named instance (this is the default).  Have you tried to authenticate using the SQLEXPRESS named instance?

Next, is the SQL Server service running?  Last, if you open a command prompt can you telnet to the SQL Server instance on port 1433?

1. Click Start -> Run
2. Type cmd
3. Press Enter
4. Type telnet X.X.X.X 1433

If you get a black screen then you are good, otherwise SQL Server is not listening on port 1433 and may not even be running.

Try this and let me know.  More than likely you are probably just missing the SQLEXPRESS named instance portion of the server name.

I am not running SQL Server 2005 express. I am authenticating to SQL Server 2005 Standard. Another employee is already connected to the same server. The service is running, also.

About the port; Strange. I look at the latest log to see what port the server is listening on and it goes from 1433 to 1434. I'll find out why and let you know if I need more help.

Thanks!