|
|
I'm doing a fresh install of WSUS 3 on a new server and I'm trying set up the
database on a remote server running SQL 2005. We are using the default
instance name but whenever I try to install I keep getting the following
error:
[DBNETLIB][ConnectionOpen (ParseConnectParams()).]Invalid connection.
I'm not a SQL guy so this error makes no sense to me. What am I missing?
|
|
What did you put there as the remote sql server name?
--
Fei Cao
Microsoft, WSUS
This posting is provided "As Is" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Rob" <Rob[ at ]discussions.microsoft.com> wrote in message
news:26B8B255-A3AD-4FA9-9E47-CCD514FB9D9F[ at ]microsoft.com...
[Quoted Text] > I'm doing a fresh install of WSUS 3 on a new server and I'm trying set up
> the
> database on a remote server running SQL 2005. We are using the default
> instance name but whenever I try to install I keep getting the following
> error:
> [DBNETLIB][ConnectionOpen (ParseConnectParams()).]Invalid connection.
>
> I'm not a SQL guy so this error makes no sense to me. What am I missing?
|
|
The machine name. That didn't work. I did machinename\MSSQLSERVER and that
didn't work either.
"Fei Cao (MSFT)" wrote:
[Quoted Text] > What did you put there as the remote sql server name? > > -- > Fei Cao > Microsoft, WSUS > > This posting is provided "As Is" with no warranties, and confers no rights. > Use of included script samples are subject to the terms specified at > http://www.microsoft.com/info/cpyright.htm> > "Rob" <Rob[ at ]discussions.microsoft.com> wrote in message > news:26B8B255-A3AD-4FA9-9E47-CCD514FB9D9F[ at ]microsoft.com... > > I'm doing a fresh install of WSUS 3 on a new server and I'm trying set up > > the > > database on a remote server running SQL 2005. We are using the default > > instance name but whenever I try to install I keep getting the following > > error: > > [DBNETLIB][ConnectionOpen (ParseConnectParams()).]Invalid connection. > > > > I'm not a SQL guy so this error makes no sense to me. What am I missing? > > > |
|
I entered the machine name. That didn't work. I entered
machinename\MSSQLSERVER and that didn't work either.
"Fei Cao (MSFT)" wrote:
[Quoted Text] > What did you put there as the remote sql server name? > > -- > Fei Cao > Microsoft, WSUS > > This posting is provided "As Is" with no warranties, and confers no rights. > Use of included script samples are subject to the terms specified at > http://www.microsoft.com/info/cpyright.htm> > "Rob" <Rob[ at ]discussions.microsoft.com> wrote in message > news:26B8B255-A3AD-4FA9-9E47-CCD514FB9D9F[ at ]microsoft.com... > > I'm doing a fresh install of WSUS 3 on a new server and I'm trying set up > > the > > database on a remote server running SQL 2005. We are using the default > > instance name but whenever I try to install I keep getting the following > > error: > > [DBNETLIB][ConnectionOpen (ParseConnectParams()).]Invalid connection. > > > > I'm not a SQL guy so this error makes no sense to me. What am I missing? > > > |
|
Is your remote sql configured to allow remote connections?
If you are using Sql Server 2005, you should be able to configure that using
MS sql server 2005/Configuration Tools/Sql Server Surface Area
Configuration, from there select "Surface Area Configuration for Services
and Connections", then on the left panel, click "View by Instance" tab to
configure "Remote Connections"
--
Fei Cao
Microsoft, WSUS
This posting is provided "As Is" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Rob" <Rob[ at ]discussions.microsoft.com> wrote in message
news:6A6CA70A-86C2-4A43-AB48-9FD0FD51BCBA[ at ]microsoft.com...
[Quoted Text] > The machine name. That didn't work. I did machinename\MSSQLSERVER and that > didn't work either. > > "Fei Cao (MSFT)" wrote: > >> What did you put there as the remote sql server name? >> >> -- >> Fei Cao >> Microsoft, WSUS >> >> This posting is provided "As Is" with no warranties, and confers no >> rights. >> Use of included script samples are subject to the terms specified at >> http://www.microsoft.com/info/cpyright.htm>> >> "Rob" <Rob[ at ]discussions.microsoft.com> wrote in message >> news:26B8B255-A3AD-4FA9-9E47-CCD514FB9D9F[ at ]microsoft.com... >> > I'm doing a fresh install of WSUS 3 on a new server and I'm trying set >> > up >> > the >> > database on a remote server running SQL 2005. We are using the default >> > instance name but whenever I try to install I keep getting the >> > following >> > error: >> > [DBNETLIB][ConnectionOpen (ParseConnectParams()).]Invalid connection. >> > >> > I'm not a SQL guy so this error makes no sense to me. What am I >> > missing? >> >> >>
|
|
Yes, it is configured to allow remote connections.
"Fei Cao (MSFT)" wrote:
[Quoted Text] > Is your remote sql configured to allow remote connections? > > If you are using Sql Server 2005, you should be able to configure that using > MS sql server 2005/Configuration Tools/Sql Server Surface Area > Configuration, from there select "Surface Area Configuration for Services > and Connections", then on the left panel, click "View by Instance" tab to > configure "Remote Connections" > > -- > Fei Cao > Microsoft, WSUS > > This posting is provided "As Is" with no warranties, and confers no rights. > Use of included script samples are subject to the terms specified at > http://www.microsoft.com/info/cpyright.htm> > "Rob" <Rob[ at ]discussions.microsoft.com> wrote in message > news:6A6CA70A-86C2-4A43-AB48-9FD0FD51BCBA[ at ]microsoft.com... > > The machine name. That didn't work. I did machinename\MSSQLSERVER and that > > didn't work either. > > > > "Fei Cao (MSFT)" wrote: > > > >> What did you put there as the remote sql server name? > >> > >> -- > >> Fei Cao > >> Microsoft, WSUS > >> > >> This posting is provided "As Is" with no warranties, and confers no > >> rights. > >> Use of included script samples are subject to the terms specified at > >> http://www.microsoft.com/info/cpyright.htm> >> > >> "Rob" <Rob[ at ]discussions.microsoft.com> wrote in message > >> news:26B8B255-A3AD-4FA9-9E47-CCD514FB9D9F[ at ]microsoft.com... > >> > I'm doing a fresh install of WSUS 3 on a new server and I'm trying set > >> > up > >> > the > >> > database on a remote server running SQL 2005. We are using the default > >> > instance name but whenever I try to install I keep getting the > >> > following > >> > error: > >> > [DBNETLIB][ConnectionOpen (ParseConnectParams()).]Invalid connection. > >> > > >> > I'm not a SQL guy so this error makes no sense to me. What am I > >> > missing? > >> > >> > >> > > > |
|
Just to clarfiy--if the remote machine name is "Alex" with default instance
name, then you should just put "Alex" there, not \\Alex or anything else. Is
this how you input the name?
Also is that remote sql server in the same domain?
--
Fei Cao
Microsoft, WSUS
This posting is provided "As Is" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Rob" <Rob[ at ]discussions.microsoft.com> wrote in message
news:0C86FFCB-7D2B-49DE-8405-83237FA528D4[ at ]microsoft.com...
[Quoted Text] > Yes, it is configured to allow remote connections. > > "Fei Cao (MSFT)" wrote: > >> Is your remote sql configured to allow remote connections? >> >> If you are using Sql Server 2005, you should be able to configure that >> using >> MS sql server 2005/Configuration Tools/Sql Server Surface Area >> Configuration, from there select "Surface Area Configuration for Services >> and Connections", then on the left panel, click "View by Instance" tab to >> configure "Remote Connections" >> >> -- >> Fei Cao >> Microsoft, WSUS >> >> This posting is provided "As Is" with no warranties, and confers no >> rights. >> Use of included script samples are subject to the terms specified at >> http://www.microsoft.com/info/cpyright.htm>> >> "Rob" <Rob[ at ]discussions.microsoft.com> wrote in message >> news:6A6CA70A-86C2-4A43-AB48-9FD0FD51BCBA[ at ]microsoft.com... >> > The machine name. That didn't work. I did machinename\MSSQLSERVER and >> > that >> > didn't work either. >> > >> > "Fei Cao (MSFT)" wrote: >> > >> >> What did you put there as the remote sql server name? >> >> >> >> -- >> >> Fei Cao >> >> Microsoft, WSUS >> >> >> >> This posting is provided "As Is" with no warranties, and confers no >> >> rights. >> >> Use of included script samples are subject to the terms specified at >> >> http://www.microsoft.com/info/cpyright.htm>> >> >> >> "Rob" <Rob[ at ]discussions.microsoft.com> wrote in message >> >> news:26B8B255-A3AD-4FA9-9E47-CCD514FB9D9F[ at ]microsoft.com... >> >> > I'm doing a fresh install of WSUS 3 on a new server and I'm trying >> >> > set >> >> > up >> >> > the >> >> > database on a remote server running SQL 2005. We are using the >> >> > default >> >> > instance name but whenever I try to install I keep getting the >> >> > following >> >> > error: >> >> > [DBNETLIB][ConnectionOpen (ParseConnectParams()).]Invalid >> >> > connection. >> >> > >> >> > I'm not a SQL guy so this error makes no sense to me. What am I >> >> > missing? >> >> >> >> >> >> >> >> >>
|
|
Also, is your remote sql configured such that it allows current logon (the
logon role that is installing WSUS on another machine) to have access to
the Sql server?
--
Fei Cao
Microsoft, WSUS
This posting is provided "As Is" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Rob" <Rob[ at ]discussions.microsoft.com> wrote in message
news:0C86FFCB-7D2B-49DE-8405-83237FA528D4[ at ]microsoft.com...
[Quoted Text] > Yes, it is configured to allow remote connections. > > "Fei Cao (MSFT)" wrote: > >> Is your remote sql configured to allow remote connections? >> >> If you are using Sql Server 2005, you should be able to configure that >> using >> MS sql server 2005/Configuration Tools/Sql Server Surface Area >> Configuration, from there select "Surface Area Configuration for Services >> and Connections", then on the left panel, click "View by Instance" tab to >> configure "Remote Connections" >> >> -- >> Fei Cao >> Microsoft, WSUS >> >> This posting is provided "As Is" with no warranties, and confers no >> rights. >> Use of included script samples are subject to the terms specified at >> http://www.microsoft.com/info/cpyright.htm>> >> "Rob" <Rob[ at ]discussions.microsoft.com> wrote in message >> news:6A6CA70A-86C2-4A43-AB48-9FD0FD51BCBA[ at ]microsoft.com... >> > The machine name. That didn't work. I did machinename\MSSQLSERVER and >> > that >> > didn't work either. >> > >> > "Fei Cao (MSFT)" wrote: >> > >> >> What did you put there as the remote sql server name? >> >> >> >> -- >> >> Fei Cao >> >> Microsoft, WSUS >> >> >> >> This posting is provided "As Is" with no warranties, and confers no >> >> rights. >> >> Use of included script samples are subject to the terms specified at >> >> http://www.microsoft.com/info/cpyright.htm>> >> >> >> "Rob" <Rob[ at ]discussions.microsoft.com> wrote in message >> >> news:26B8B255-A3AD-4FA9-9E47-CCD514FB9D9F[ at ]microsoft.com... >> >> > I'm doing a fresh install of WSUS 3 on a new server and I'm trying >> >> > set >> >> > up >> >> > the >> >> > database on a remote server running SQL 2005. We are using the >> >> > default >> >> > instance name but whenever I try to install I keep getting the >> >> > following >> >> > error: >> >> > [DBNETLIB][ConnectionOpen (ParseConnectParams()).]Invalid >> >> > connection. >> >> > >> >> > I'm not a SQL guy so this error makes no sense to me. What am I >> >> > missing? >> >> >> >> >> >> >> >> >>
|
|
I put just the machine name. No backslashes or anything.
Both servers are in the same domain. See my frustration?
"Fei Cao (MSFT)" wrote:
[Quoted Text] > Just to clarfiy--if the remote machine name is "Alex" with default instance > name, then you should just put "Alex" there, not \\Alex or anything else. Is > this how you input the name? > Also is that remote sql server in the same domain? > > -- > Fei Cao > Microsoft, WSUS > > This posting is provided "As Is" with no warranties, and confers no rights. > Use of included script samples are subject to the terms specified at > http://www.microsoft.com/info/cpyright.htm> > "Rob" <Rob[ at ]discussions.microsoft.com> wrote in message > news:0C86FFCB-7D2B-49DE-8405-83237FA528D4[ at ]microsoft.com... > > Yes, it is configured to allow remote connections. > > > > "Fei Cao (MSFT)" wrote: > > > >> Is your remote sql configured to allow remote connections? > >> > >> If you are using Sql Server 2005, you should be able to configure that > >> using > >> MS sql server 2005/Configuration Tools/Sql Server Surface Area > >> Configuration, from there select "Surface Area Configuration for Services > >> and Connections", then on the left panel, click "View by Instance" tab to > >> configure "Remote Connections" > >> > >> -- > >> Fei Cao > >> Microsoft, WSUS > >> > >> This posting is provided "As Is" with no warranties, and confers no > >> rights. > >> Use of included script samples are subject to the terms specified at > >> http://www.microsoft.com/info/cpyright.htm> >> > >> "Rob" <Rob[ at ]discussions.microsoft.com> wrote in message > >> news:6A6CA70A-86C2-4A43-AB48-9FD0FD51BCBA[ at ]microsoft.com... > >> > The machine name. That didn't work. I did machinename\MSSQLSERVER and > >> > that > >> > didn't work either. > >> > > >> > "Fei Cao (MSFT)" wrote: > >> > > >> >> What did you put there as the remote sql server name? > >> >> > >> >> -- > >> >> Fei Cao > >> >> Microsoft, WSUS > >> >> > >> >> This posting is provided "As Is" with no warranties, and confers no > >> >> rights. > >> >> Use of included script samples are subject to the terms specified at > >> >> http://www.microsoft.com/info/cpyright.htm> >> >> > >> >> "Rob" <Rob[ at ]discussions.microsoft.com> wrote in message > >> >> news:26B8B255-A3AD-4FA9-9E47-CCD514FB9D9F[ at ]microsoft.com... > >> >> > I'm doing a fresh install of WSUS 3 on a new server and I'm trying > >> >> > set > >> >> > up > >> >> > the > >> >> > database on a remote server running SQL 2005. We are using the > >> >> > default > >> >> > instance name but whenever I try to install I keep getting the > >> >> > following > >> >> > error: > >> >> > [DBNETLIB][ConnectionOpen (ParseConnectParams()).]Invalid > >> >> > connection. > >> >> > > >> >> > I'm not a SQL guy so this error makes no sense to me. What am I > >> >> > missing? > >> >> > >> >> > >> >> > >> > >> > >> > > > |
|
I am using my logon (I'm a domain admin.) I'm getting this error when I put
in machinename\mssqlserver. When I try machine name by itself, all I get is
"Failed to connect to SQL server."
"Fei Cao (MSFT)" wrote:
[Quoted Text] > Also, is your remote sql configured such that it allows current logon (the > logon role that is installing WSUS on another machine) to have access to > the Sql server? > > -- > Fei Cao > Microsoft, WSUS > > This posting is provided "As Is" with no warranties, and confers no rights. > Use of included script samples are subject to the terms specified at > http://www.microsoft.com/info/cpyright.htm> > "Rob" <Rob[ at ]discussions.microsoft.com> wrote in message > news:0C86FFCB-7D2B-49DE-8405-83237FA528D4[ at ]microsoft.com... > > Yes, it is configured to allow remote connections. > > > > "Fei Cao (MSFT)" wrote: > > > >> Is your remote sql configured to allow remote connections? > >> > >> If you are using Sql Server 2005, you should be able to configure that > >> using > >> MS sql server 2005/Configuration Tools/Sql Server Surface Area > >> Configuration, from there select "Surface Area Configuration for Services > >> and Connections", then on the left panel, click "View by Instance" tab to > >> configure "Remote Connections" > >> > >> -- > >> Fei Cao > >> Microsoft, WSUS > >> > >> This posting is provided "As Is" with no warranties, and confers no > >> rights. > >> Use of included script samples are subject to the terms specified at > >> http://www.microsoft.com/info/cpyright.htm> >> > >> "Rob" <Rob[ at ]discussions.microsoft.com> wrote in message > >> news:6A6CA70A-86C2-4A43-AB48-9FD0FD51BCBA[ at ]microsoft.com... > >> > The machine name. That didn't work. I did machinename\MSSQLSERVER and > >> > that > >> > didn't work either. > >> > > >> > "Fei Cao (MSFT)" wrote: > >> > > >> >> What did you put there as the remote sql server name? > >> >> > >> >> -- > >> >> Fei Cao > >> >> Microsoft, WSUS > >> >> > >> >> This posting is provided "As Is" with no warranties, and confers no > >> >> rights. > >> >> Use of included script samples are subject to the terms specified at > >> >> http://www.microsoft.com/info/cpyright.htm> >> >> > >> >> "Rob" <Rob[ at ]discussions.microsoft.com> wrote in message > >> >> news:26B8B255-A3AD-4FA9-9E47-CCD514FB9D9F[ at ]microsoft.com... > >> >> > I'm doing a fresh install of WSUS 3 on a new server and I'm trying > >> >> > set > >> >> > up > >> >> > the > >> >> > database on a remote server running SQL 2005. We are using the > >> >> > default > >> >> > instance name but whenever I try to install I keep getting the > >> >> > following > >> >> > error: > >> >> > [DBNETLIB][ConnectionOpen (ParseConnectParams()).]Invalid > >> >> > connection. > >> >> > > >> >> > I'm not a SQL guy so this error makes no sense to me. What am I > >> >> > missing? > >> >> > >> >> > >> >> > >> > >> > >> > > > |
|
Hi Rob,
Can you check the permissions of your remote sql server and verify that your
current logong is indeed allowed to have access to that remote sql server?
thanks,
--
Fei Cao
Microsoft, WSUS
This posting is provided "As Is" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Rob" <Rob[ at ]discussions.microsoft.com> wrote in message
news:4E72FAEC-BA26-4DCE-B0C1-6F63B3C56258[ at ]microsoft.com...
[Quoted Text] >I am using my logon (I'm a domain admin.) I'm getting this error when I put > in machinename\mssqlserver. When I try machine name by itself, all I get > is > "Failed to connect to SQL server." > > "Fei Cao (MSFT)" wrote: > >> Also, is your remote sql configured such that it allows current logon >> (the >> logon role that is installing WSUS on another machine) to have access to >> the Sql server? >> >> -- >> Fei Cao >> Microsoft, WSUS >> >> This posting is provided "As Is" with no warranties, and confers no >> rights. >> Use of included script samples are subject to the terms specified at >> http://www.microsoft.com/info/cpyright.htm>> >> "Rob" <Rob[ at ]discussions.microsoft.com> wrote in message >> news:0C86FFCB-7D2B-49DE-8405-83237FA528D4[ at ]microsoft.com... >> > Yes, it is configured to allow remote connections. >> > >> > "Fei Cao (MSFT)" wrote: >> > >> >> Is your remote sql configured to allow remote connections? >> >> >> >> If you are using Sql Server 2005, you should be able to configure that >> >> using >> >> MS sql server 2005/Configuration Tools/Sql Server Surface Area >> >> Configuration, from there select "Surface Area Configuration for >> >> Services >> >> and Connections", then on the left panel, click "View by Instance" tab >> >> to >> >> configure "Remote Connections" >> >> >> >> -- >> >> Fei Cao >> >> Microsoft, WSUS >> >> >> >> This posting is provided "As Is" with no warranties, and confers no >> >> rights. >> >> Use of included script samples are subject to the terms specified at >> >> http://www.microsoft.com/info/cpyright.htm>> >> >> >> "Rob" <Rob[ at ]discussions.microsoft.com> wrote in message >> >> news:6A6CA70A-86C2-4A43-AB48-9FD0FD51BCBA[ at ]microsoft.com... >> >> > The machine name. That didn't work. I did machinename\MSSQLSERVER >> >> > and >> >> > that >> >> > didn't work either. >> >> > >> >> > "Fei Cao (MSFT)" wrote: >> >> > >> >> >> What did you put there as the remote sql server name? >> >> >> >> >> >> -- >> >> >> Fei Cao >> >> >> Microsoft, WSUS >> >> >> >> >> >> This posting is provided "As Is" with no warranties, and confers no >> >> >> rights. >> >> >> Use of included script samples are subject to the terms specified >> >> >> at >> >> >> http://www.microsoft.com/info/cpyright.htm>> >> >> >> >> >> "Rob" <Rob[ at ]discussions.microsoft.com> wrote in message >> >> >> news:26B8B255-A3AD-4FA9-9E47-CCD514FB9D9F[ at ]microsoft.com... >> >> >> > I'm doing a fresh install of WSUS 3 on a new server and I'm >> >> >> > trying >> >> >> > set >> >> >> > up >> >> >> > the >> >> >> > database on a remote server running SQL 2005. We are using the >> >> >> > default >> >> >> > instance name but whenever I try to install I keep getting the >> >> >> > following >> >> >> > error: >> >> >> > [DBNETLIB][ConnectionOpen (ParseConnectParams()).]Invalid >> >> >> > connection. >> >> >> > >> >> >> > I'm not a SQL guy so this error makes no sense to me. What am I >> >> >> > missing? >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >>
|
|
I am an administrator of the machine and a sysadmin in SQL.
"Fei Cao (MSFT)" wrote:
[Quoted Text] > Hi Rob, > > Can you check the permissions of your remote sql server and verify that your > current logong is indeed allowed to have access to that remote sql server? > > thanks, > -- > Fei Cao > Microsoft, WSUS > > This posting is provided "As Is" with no warranties, and confers no rights. > Use of included script samples are subject to the terms specified at > http://www.microsoft.com/info/cpyright.htm> > "Rob" <Rob[ at ]discussions.microsoft.com> wrote in message > news:4E72FAEC-BA26-4DCE-B0C1-6F63B3C56258[ at ]microsoft.com... > >I am using my logon (I'm a domain admin.) I'm getting this error when I put > > in machinename\mssqlserver. When I try machine name by itself, all I get > > is > > "Failed to connect to SQL server." > > > > "Fei Cao (MSFT)" wrote: > > > >> Also, is your remote sql configured such that it allows current logon > >> (the > >> logon role that is installing WSUS on another machine) to have access to > >> the Sql server? > >> > >> -- > >> Fei Cao > >> Microsoft, WSUS > >> > >> This posting is provided "As Is" with no warranties, and confers no > >> rights. > >> Use of included script samples are subject to the terms specified at > >> http://www.microsoft.com/info/cpyright.htm> >> > >> "Rob" <Rob[ at ]discussions.microsoft.com> wrote in message > >> news:0C86FFCB-7D2B-49DE-8405-83237FA528D4[ at ]microsoft.com... > >> > Yes, it is configured to allow remote connections. > >> > > >> > "Fei Cao (MSFT)" wrote: > >> > > >> >> Is your remote sql configured to allow remote connections? > >> >> > >> >> If you are using Sql Server 2005, you should be able to configure that > >> >> using > >> >> MS sql server 2005/Configuration Tools/Sql Server Surface Area > >> >> Configuration, from there select "Surface Area Configuration for > >> >> Services > >> >> and Connections", then on the left panel, click "View by Instance" tab > >> >> to > >> >> configure "Remote Connections" > >> >> > >> >> -- > >> >> Fei Cao > >> >> Microsoft, WSUS > >> >> > >> >> This posting is provided "As Is" with no warranties, and confers no > >> >> rights. > >> >> Use of included script samples are subject to the terms specified at > >> >> http://www.microsoft.com/info/cpyright.htm> >> >> > >> >> "Rob" <Rob[ at ]discussions.microsoft.com> wrote in message > >> >> news:6A6CA70A-86C2-4A43-AB48-9FD0FD51BCBA[ at ]microsoft.com... > >> >> > The machine name. That didn't work. I did machinename\MSSQLSERVER > >> >> > and > >> >> > that > >> >> > didn't work either. > >> >> > > >> >> > "Fei Cao (MSFT)" wrote: > >> >> > > >> >> >> What did you put there as the remote sql server name? > >> >> >> > >> >> >> -- > >> >> >> Fei Cao > >> >> >> Microsoft, WSUS > >> >> >> > >> >> >> This posting is provided "As Is" with no warranties, and confers no > >> >> >> rights. > >> >> >> Use of included script samples are subject to the terms specified > >> >> >> at > >> >> >> http://www.microsoft.com/info/cpyright.htm> >> >> >> > >> >> >> "Rob" <Rob[ at ]discussions.microsoft.com> wrote in message > >> >> >> news:26B8B255-A3AD-4FA9-9E47-CCD514FB9D9F[ at ]microsoft.com... > >> >> >> > I'm doing a fresh install of WSUS 3 on a new server and I'm > >> >> >> > trying > >> >> >> > set > >> >> >> > up > >> >> >> > the > >> >> >> > database on a remote server running SQL 2005. We are using the > >> >> >> > default > >> >> >> > instance name but whenever I try to install I keep getting the > >> >> >> > following > >> >> >> > error: > >> >> >> > [DBNETLIB][ConnectionOpen (ParseConnectParams()).]Invalid > >> >> >> > connection. > >> >> >> > > >> >> >> > I'm not a SQL guy so this error makes no sense to me. What am I > >> >> >> > missing? > >> >> >> > >> >> >> > >> >> >> > >> >> > >> >> > >> >> > >> > >> > >> > > > |
|
I've banged my head against the wall several times trying to figure this out
too. Here are the steps I usually will perform, in order, to make sure this
is a SQL issue and not a WSUS issue:
• On the SQL machine make sure you're actually able to connect to the SQL
server via sqlcmd. Make sure to use the same server\instance name (whatever
is after the -S (see below)) you plan on using on the remote machine
• Make sure that the SQL server is running at least SP1. The version number
should be at least 9.00.2047. Once connected run the following, hitting
enter after each line
select [ at ][ at ]version
go
• Make sure that SQL is set up to allow remote connections (using SQL
Surface Area Configuration)
• Make sure there isn't a firewall that will block the remote SQL
connections
• On the remote machine you plan on installing WSUS try to connect to the
SQL server (using sqlcmd)
• If this succeeds you should be able to use the same server\instance name
to tell WSUS where to find the server
sqlcmd can be downloaded here:
http://go.microsoft.com/fwlink/?LinkId=70728
You’ll also need to download “Microsoft SQL Server Native Client†onto the
WSUS machine to allow sqlcmd to run
For the default SQL instance the connection string you'd want to use would
look like:
sqlcmd -E -S %computername%
Where %computername% is the name of the computer hosting the SQL server
If the connection succeeds you'll see a prompt like the following:
1>
Hope this helps.
--
Dan Albrecht
Microsoft, WSUS
This posting is provided "As Is" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Rob" <Rob[ at ]discussions.microsoft.com> wrote in message
news:05EE7FB4-D42C-45C8-B0D4-86DD1F706E1C[ at ]microsoft.com...
[Quoted Text] >I put just the machine name. No backslashes or anything. > > Both servers are in the same domain. See my frustration? > > "Fei Cao (MSFT)" wrote: > >> Just to clarfiy--if the remote machine name is "Alex" with default >> instance >> name, then you should just put "Alex" there, not \\Alex or anything else. >> Is >> this how you input the name? >> Also is that remote sql server in the same domain? >> >> -- >> Fei Cao >> Microsoft, WSUS >> >> This posting is provided "As Is" with no warranties, and confers no >> rights. >> Use of included script samples are subject to the terms specified at >> http://www.microsoft.com/info/cpyright.htm>> >> "Rob" <Rob[ at ]discussions.microsoft.com> wrote in message >> news:0C86FFCB-7D2B-49DE-8405-83237FA528D4[ at ]microsoft.com... >> > Yes, it is configured to allow remote connections. >> > >> > "Fei Cao (MSFT)" wrote: >> > >> >> Is your remote sql configured to allow remote connections? >> >> >> >> If you are using Sql Server 2005, you should be able to configure that >> >> using >> >> MS sql server 2005/Configuration Tools/Sql Server Surface Area >> >> Configuration, from there select "Surface Area Configuration for >> >> Services >> >> and Connections", then on the left panel, click "View by Instance" tab >> >> to >> >> configure "Remote Connections" >> >> >> >> -- >> >> Fei Cao >> >> Microsoft, WSUS >> >> >> >> This posting is provided "As Is" with no warranties, and confers no >> >> rights. >> >> Use of included script samples are subject to the terms specified at >> >> http://www.microsoft.com/info/cpyright.htm>> >> >> >> "Rob" <Rob[ at ]discussions.microsoft.com> wrote in message >> >> news:6A6CA70A-86C2-4A43-AB48-9FD0FD51BCBA[ at ]microsoft.com... >> >> > The machine name. That didn't work. I did machinename\MSSQLSERVER >> >> > and >> >> > that >> >> > didn't work either. >> >> > >> >> > "Fei Cao (MSFT)" wrote: >> >> > >> >> >> What did you put there as the remote sql server name? >> >> >> >> >> >> -- >> >> >> Fei Cao >> >> >> Microsoft, WSUS >> >> >> >> >> >> This posting is provided "As Is" with no warranties, and confers no >> >> >> rights. >> >> >> Use of included script samples are subject to the terms specified >> >> >> at >> >> >> http://www.microsoft.com/info/cpyright.htm>> >> >> >> >> >> "Rob" <Rob[ at ]discussions.microsoft.com> wrote in message >> >> >> news:26B8B255-A3AD-4FA9-9E47-CCD514FB9D9F[ at ]microsoft.com... >> >> >> > I'm doing a fresh install of WSUS 3 on a new server and I'm >> >> >> > trying >> >> >> > set >> >> >> > up >> >> >> > the >> >> >> > database on a remote server running SQL 2005. We are using the >> >> >> > default >> >> >> > instance name but whenever I try to install I keep getting the >> >> >> > following >> >> >> > error: >> >> >> > [DBNETLIB][ConnectionOpen (ParseConnectParams()).]Invalid >> >> >> > connection. >> >> >> > >> >> >> > I'm not a SQL guy so this error makes no sense to me. What am I >> >> >> > missing? >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >>
|
|
Hi
I had the same problem. Thanks to Microsoft for not putting the
following in the instructions. You need to create a Service Principal
Name for the account that SQL server runs under. It appears that when
a service running as "Network Service" tries to connect to a remote
SQL 2005, it actually uses kerberos for the individual servce it is
trying to connect to. Also, ensure the SUSDB database has an account
for YOUR WSUS computer in it (eg, DOMAIN\WSUSPC$) and it is a member
of wSusService and Public roles in that database.
http://support.microsoft.com/kb/909801
Basically, the command I gave was:
SetSPN -A MSSQLSvc/my_wsus_server.full.domain.com:1433 domain
\account_sql_runs_under
So, if your SQL servers full host name is mysql2005.mycompany.com and
the account it runs under is WORK\sqlacct
SetSPN -A MSSQLSvc/mysql2005.mycompany.com:1433 WORK\sqlacct
(the 1433 is the default port SQL server listens on by the way, change
if necessary)
Do that as a domain administrator, wait (or force) your ADs to sync
and the SoftwareDistribution.log in WSUS logfiles should show the
service now connects.
Hth
AW
On May 3, 12:14 am, Rob <R...[ at ]discussions.microsoft.com> wrote:
[Quoted Text] > I entered the machine name. That didn't work. I entered > machinename\MSSQLSERVER and that didn't work either. > > "Fei Cao (MSFT)" wrote: > > What did you put there as the remote sql server name? > > > -- > > Fei Cao > > Microsoft, WSUS > > > This posting is provided "As Is" with no warranties, and confers no rights. > > Use of included script samples are subject to the terms specified at > > http://www.microsoft.com/info/cpyright.htm> > > "Rob" <R...[ at ]discussions.microsoft.com> wrote in message > >news:26B8B255-A3AD-4FA9-9E47-CCD514FB9D9F[ at ]microsoft.com... > > > I'm doing a fresh install of WSUS 3 on a new server and I'm trying set up > > > the > > > database on a remote server running SQL 2005. We are using the default > > > instance name but whenever I try to install I keep getting the following > > > error: > > > [DBNETLIB][ConnectionOpen (ParseConnectParams()).]Invalid connection. > > > > I'm not a SQL guy so this error makes no sense to me. What am I missing?
|
|
|
|
Thanks for that note Lawrence. I'm not the installs-SQL-Server guy. We
had noticed on occasion an info-warning type thing in event viewer
about that. Guess someone took the view at the time that as it didn't
cause a problem it, well, wasn't a problem and so left it as-was.
Will drop a note to our SQL chaps, advising them of this.
AW
On May 9, 11:11 pm, "Lawrence Garvin \(MVP\)"
<onsit...[ at ]community.nospam> wrote:
[Quoted Text]
|
|
|