Re: Can't connect to MSDE on SBS 2003

I figured it out. The SBSMONITORING instance was also using port 1433. I
changed the port for the Great Plains instance and it is working great.

I'd still like to find out about if I have to reapply SP4 though

Thanks

--
Kerry
MS-MVP Windows - Shell/User
http://www.vistahelp.ca


Kerry Brown wrote:
I'm trying to install Great Plains 9.0 on a SBS 2003 Standard Edition
server with SP1. I can create an MSDE instance and connect to it with
SQL or Windows authentication on the server. From client workstations
I can connect with Windows authentication but not SQL authentication.
I can install the GP 9.0 client on the server and it works fine. From a
workstation it
won't connect as it uses SQL authentication. Same with setting up
OBDC. It works with SQL authentication on the server but not the
workstations. All the registry entries for the instance look right. I
loaded Enterprise Manager on one of the workstations. It connects
fine with Windows authentication. In the properties it shows the
instance as being set for Mixed Windows and SQL authentication. I
used the MSDE setup.exe that is in the following folder on the SBS
server:
C:\Program Files\Microsoft SQL Server SP4\MSDE\setup.exe

Should I have used this one?

C:\Program Files\Microsoft SQL Server SP4\WMSDE\setup.exe

the command line to install the instance was

setup SAPWD="mypassword" DISABLENETWORKPROTOCOLS=0 SECURITYMODE=SQL

I have used portqry to confirm the server is listening on port 1433.

The only thing I can think of is something in the SBS 2003 security is
blocking the workstations from SQL authentication. Has anyone run
into this before?

I also have a second question. If I install the SQL 2000 client tools
on the server do I have to also reinstall SP4? The SBS 2003 SP1
upgraded the server instances to SP4 already. If I have to reinstall
SP4 which one do I use, for MSDE or SQL? I am testing all this on a
test server until I get it all figured out but I'd still like to make
sure I'm free from slammer etc.


.

Relevant Pages

  • Re: Problems connecting to SQL server on W2K3 from Win 2000 workst
    ... Can you connect to a network share on the SQL server? ... Also I know this isn't as important on 2k machines but is the primary DNS ... >> This is because you are using Windows authentication without a domain ... >> because it tends not to work, use SQL Authentication and you'll always ...
    (microsoft.public.sqlserver.connect)
  • Re: Connection issues
    ... > Each user connected to the server has their own connection to the ... To take advantage of pooling, you would want to use "SQL Authentication" ... that you have to pass the ID+PW to the server from your client Windows Form ...
    (microsoft.public.dotnet.framework.adonet)
  • SQL2005 connection problems from ASP
    ... process that connects to SQL2005 using SQL Authentication. ... this setup no matter what I do in this setup the connection will always ... I am certain that the connection string we are using is valid based on ... even works on Windows 2003 server against SQL2000). ...
    (microsoft.public.inetserver.asp.db)
  • Cant connect to MSDE on SBS 2003
    ... I'm trying to install Great Plains 9.0 on a SBS 2003 Standard Edition server with SP1. ... I can create an MSDE instance and connect to it with SQL or Windows authentication on the server. ... From client workstations I can connect with Windows authentication but not SQL authentication. ...
    (microsoft.public.sqlserver.msde)
  • Re: Problems connecting to SQL server on W2K3 from Win 2000 workstatio
    ... This is because you are using Windows authentication without a domain setup. ... because it tends not to work, use SQL Authentication and you'll always ... > from windows XP machines. ... > to the server using the SA account and Named Pipes from a windows ...
    (microsoft.public.sqlserver.connect)