Steve Erbach
erbachs at gmail.com
Wed Dec 9 09:43:14 CST 2009
Michael, After about six hours on the phone with Microsoft, my wife got things working again. The server's registry had to be re-built and SQL Server re-installed. So the use of a workstation copy of SQL Server is now moot. However, it would be VERY interesting to see about getting that capability working in case the server ever puked again. I will keep your suggestion handy and forward it to my wife. Thank you. Steve Erbach Neenah, WI On Tue, Dec 8, 2009 at 4:44 PM, Michael Maddison < michael at ddisolutions.com.au> wrote: > Steve, > > Try this... > > Open SQL Server Configuration Manager on the workstation. > Expand Native Client Config. > Make sure TCP/IP is enabled. > Check the Default Port in the properties. > Check your firewall that the port is set as an exemption. > > Cheers > > Michael M > > > > Dear Group, > > I'm trying to help my wife who is the de facto network administrator for > the > small company she works for. The main order processing application uses > SQL > Server 2005 on the domain server. That SQL Server is having problems. > > What we've tried is to copy the MDF and log file to a workstation that > has > SQL Server 2005 installed on it. The application is an Access MDB > connected > via ODBC to the SQL Server database. We can connect to the SQL Server > database just fine if we run the Access application on that workstation. > > The problem comes in when we try to connect to the database from another > workstation on the LAN. We keep getting "SQL Server not found". I > can't > get the System ODBC connection to "see" the SQL Server on the > workstation...nor can I get Access 2003 to create an ADP project to > connect > directly to SQL Server 2005 on that other workstation. > >