cannot locally telnet to 1433 but Mgt Studio ok ?

Hi,
I have a hosted server running win2003, sql express and an app I need to
connect to 1433.
In a cmd prompt I enter "telnet 99.99.99.99 1433" and I cannot connect.
(this works on every other server I have tested).
I CAN open sql mgt studio an connect ok (again on 1433 I guess by default)
and connect to the correct DB using the user my app uses.
My app throws an error as it cannot connect, I think I need to get this
telnet test working before my app will work. (app passes user + pass + IP +
DB).
What would block telnet on 1433 but still allow SQL Mgt Studio to connect on
1433 ?
My server IP is public, and telnet test uses public IP. Is it possible
telnet test is not routed locally and the Mgt Studio connection is routed
locally ?
I tried telnet on ip loop back but that did not work i.e "telnet 127.0.0.1
1433"
Thanks for any advice.
Scottsorry failed to mention Mgt Studio uses netbios name ... when i enter IP i
does not work ... so i guess its the way traffic is routed. must be a
filtered somewhere in security policy or routers. both win + sql
authenrtication work using netbios name but neither with ip.
can someone confirm how traffic in these situations is routed ?|||"Scott" <scott@.> wrote in message
news:eiCIekDIHHA.4688@.TK2MSFTNGP04.phx.gbl...
> sorry failed to mention Mgt Studio uses netbios name ... when i enter IP i
> does not work ... so i guess its the way traffic is routed. must be a
> filtered somewhere in security policy or routers. both win + sql
> authenrtication work using netbios name but neither with ip.
> can someone confirm how traffic in these situations is routed ?
>
SQL Server supports multiple network libraries, TCP/IP is one, but Named
Pipes and Shared Memory are two others. Locally on the box you will often
be using the Shared Memory library.
It sounds like TCP/IP is just not enabled. Check the SQL SErver log to be
sure. IT will tell you on startup all the listener endpoints it starts.
Here's my log
12/15/2006 08:44:40,Server,Unknown,SQL Server is now ready for client
connections. This is an . ..
12/15/2006 08:44:40,Server,Unknown,Server is listening on [ 127.0.0.1 <ipv4>
1434].
12/15/2006 08:44:40,Server,Unknown,Server is listening on [ ::1 <ipv6>
1434].
12/15/2006 08:44:40,Server,Unknown,Server local connection provider is ready
to accept connection on [ \\.\pipe\sql\query ].
12/15/2006 08:44:40,Server,Unknown,Server local connection provider is ready
to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
12/15/2006 08:44:40,Server,Unknown,Server is listening on [ 'any' <ipv4>
1433].
12/15/2006 08:44:40,Server,Unknown,Server is listening on [ 'any' <ipv6>
1433].
You can change the protocols used by your server using the SQL Server
Configuration Manager.
David|||many thanks for reply.
i think you are right about this.
Cheers
Scott

cannot locally telnet to 1433 but Mgt Studio ok ?

Hi,
I have a hosted server running win2003, sql express and an app I need to
connect to 1433.
In a cmd prompt I enter "telnet 99.99.99.99 1433" and I cannot connect.
(this works on every other server I have tested).
I CAN open sql mgt studio an connect ok (again on 1433 I guess by default)
and connect to the correct DB using the user my app uses.
My app throws an error as it cannot connect, I think I need to get this
telnet test working before my app will work. (app passes user + pass + IP +
DB).
What would block telnet on 1433 but still allow SQL Mgt Studio to connect on
1433 ?
My server IP is public, and telnet test uses public IP. Is it possible
telnet test is not routed locally and the Mgt Studio connection is routed
locally ?
I tried telnet on ip loop back but that did not work i.e "telnet 127.0.0.1
1433"
Thanks for any advice.
Scott
sorry failed to mention Mgt Studio uses netbios name ... when i enter IP i
does not work ... so i guess its the way traffic is routed. must be a
filtered somewhere in security policy or routers. both win + sql
authenrtication work using netbios name but neither with ip.
can someone confirm how traffic in these situations is routed ?
|||"Scott" <scott@.> wrote in message
news:eiCIekDIHHA.4688@.TK2MSFTNGP04.phx.gbl...
> sorry failed to mention Mgt Studio uses netbios name ... when i enter IP i
> does not work ... so i guess its the way traffic is routed. must be a
> filtered somewhere in security policy or routers. both win + sql
> authenrtication work using netbios name but neither with ip.
> can someone confirm how traffic in these situations is routed ?
>
SQL Server supports multiple network libraries, TCP/IP is one, but Named
Pipes and Shared Memory are two others. Locally on the box you will often
be using the Shared Memory library.
It sounds like TCP/IP is just not enabled. Check the SQL SErver log to be
sure. IT will tell you on startup all the listener endpoints it starts.
Here's my log
12/15/2006 08:44:40,Server,Unknown,SQL Server is now ready for client
connections. This is an . ..
12/15/2006 08:44:40,Server,Unknown,Server is listening on [ 127.0.0.1 <ipv4>
1434].
12/15/2006 08:44:40,Server,Unknown,Server is listening on [ ::1 <ipv6>
1434].
12/15/2006 08:44:40,Server,Unknown,Server local connection provider is ready
to accept connection on [ \\.\pipe\sql\query ].
12/15/2006 08:44:40,Server,Unknown,Server local connection provider is ready
to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
12/15/2006 08:44:40,Server,Unknown,Server is listening on [ 'any' <ipv4>
1433].
12/15/2006 08:44:40,Server,Unknown,Server is listening on [ 'any' <ipv6>
1433].
You can change the protocols used by your server using the SQL Server
Configuration Manager.
David
|||many thanks for reply.
i think you are right about this.
Cheers
Scott

cannot locally telnet to 1433 but Mgt Studio ok ?

Hi,
I have a hosted server running win2003, sql express and an app I need to
connect to 1433.
In a cmd prompt I enter "telnet 99.99.99.99 1433" and I cannot connect.
(this works on every other server I have tested).
I CAN open sql mgt studio an connect ok (again on 1433 I guess by default)
and connect to the correct DB using the user my app uses.
My app throws an error as it cannot connect, I think I need to get this
telnet test working before my app will work. (app passes user + pass + IP +
DB).
What would block telnet on 1433 but still allow SQL Mgt Studio to connect on
1433 ?
My server IP is public, and telnet test uses public IP. Is it possible
telnet test is not routed locally and the Mgt Studio connection is routed
locally ?
I tried telnet on ip loop back but that did not work i.e "telnet 127.0.0.1
1433"
Thanks for any advice.
Scottsorry failed to mention Mgt Studio uses netbios name ... when i enter IP i
does not work ... so i guess its the way traffic is routed. must be a
filtered somewhere in security policy or routers. both win + sql
authenrtication work using netbios name but neither with ip.
can someone confirm how traffic in these situations is routed ?|||"Scott" <scott@.> wrote in message
news:eiCIekDIHHA.4688@.TK2MSFTNGP04.phx.gbl...
> sorry failed to mention Mgt Studio uses netbios name ... when i enter IP i
> does not work ... so i guess its the way traffic is routed. must be a
> filtered somewhere in security policy or routers. both win + sql
> authenrtication work using netbios name but neither with ip.
> can someone confirm how traffic in these situations is routed ?
>
SQL Server supports multiple network libraries, TCP/IP is one, but Named
Pipes and Shared Memory are two others. Locally on the box you will often
be using the Shared Memory library.
It sounds like TCP/IP is just not enabled. Check the SQL SErver log to be
sure. IT will tell you on startup all the listener endpoints it starts.
Here's my log
12/15/2006 08:44:40,Server,Unknown,SQL Server is now ready for client
connections. This is an . ..
12/15/2006 08:44:40,Server,Unknown,Server is listening on [ 127.0.0.1 <i
pv4>
1434].
12/15/2006 08:44:40,Server,Unknown,Server is listening on [ ::1 <ipv6>
1434].
12/15/2006 08:44:40,Server,Unknown,Server local connection provider is ready
to accept connection on [ \\.\pipe\sql\query ].
12/15/2006 08:44:40,Server,Unknown,Server local connection provider is ready
to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
12/15/2006 08:44:40,Server,Unknown,Server is listening on [ 'any' <ipv4>
1433].
12/15/2006 08:44:40,Server,Unknown,Server is listening on [ 'any' <ipv6>
1433].
You can change the protocols used by your server using the SQL Server
Configuration Manager.
David|||many thanks for reply.
i think you are right about this.
Cheers
Scott

Cannot install SQL Express on a French Win2003 Server OS

This one has me scratching my head. We can install SQL Express on many different English OS without problems, but when we try it on a French OS it doesn't work. We have several French systems and SQL Express does not install on any of them. Even just running the SQLEXPR32.EXE without paramaters give the same error. We have yet to try it on other foreign OS. The command line we use to install is:

SQLEXPR32.EXE /qb INSTANCENAME="TESTINSTANCE" ADDLOCAL=ALL SECURITYMODE=SQL SAPWD=<StrongPassword> DISABLENETWORKPROTOCOLS=0

I've tried various solutions from these links:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=136496&SiteID=1 http://www.developersdex.com/sql/message.asp?p=1870&r=4699024&Page=1 http://www.developersdex.com/sql/message.asp?p=1870&r=4699024&page=2

However, none of them work. Has Microsoft actually tested the installer on a foreign OS? Below is the details of the setup log file:

Microsoft SQL Server 2005 Setup beginning at Thu Mar 29 14:09:31 2007
Process ID : 2232
c:\f66fbb131aeb0b5e04aed9ecb936c1\setup.exe Version: 2005.90.3042.0
Running: LoadResourcesAction at: 2007/2/29 14:9:31
Complete: LoadResourcesAction at: 2007/2/29 14:9:31, returned true
Running: ParseBootstrapOptionsAction at: 2007/2/29 14:9:31
Loaded DLL:c:\f66fbb131aeb0b5e04aed9ecb936c1\xmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2007/2/29 14:9:31, returned false
Error: Action "ParseBootstrapOptionsAction" failed during execution. Error information reported during run:
Could not parse command line due to datastore exception.
Source File Name: utillib\persisthelpers.cpp
Compiler Timestamp: Wed Jun 14 16:30:14 2006
Function Name: writeEncryptedString
Source Line Number: 124
-
writeEncryptedString() failed
Source File Name: utillib\persisthelpers.cpp
Compiler Timestamp: Wed Jun 14 16:30:14 2006
Function Name: writeEncryptedString
Source Line Number: 123
-
Error Code: 0x80070002 (2)
Windows Error Text: Le fichier spcifi est introuvable.

Source File Name: cryptohelper\cryptsameusersamemachine.cpp
Compiler Timestamp: Wed Jun 14 16:28:04 2006
Function Name: sqls::CryptSameUserSameMachine:rotectData
Source Line Number: 50

2
Could not skip Component update due to datastore exception.
Source File Name: datastore\cachedpropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:27:59 2006
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
-
Failed to find property "InstallMediaPath" {"SetupBootstrapOptionsScope", "", "2232"} in cache
Source File Name: datastore\propertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:28:01 2006
Function Name: SetupBootstrapOptionsScope.InstallMediaPath
Source Line Number: 44
-
No collector registered for scope: "SetupBootstrapOptionsScope"
Running: ValidateWinNTAction at: 2007/2/29 14:9:31
Complete: ValidateWinNTAction at: 2007/2/29 14:9:31, returned true
Running: ValidateMinOSAction at: 2007/2/29 14:9:31
Complete: ValidateMinOSAction at: 2007/2/29 14:9:31, returned true
Running: PerformSCCAction at: 2007/2/29 14:9:31
Complete: PerformSCCAction at: 2007/2/29 14:9:31, returned true
Running: ActivateLoggingAction at: 2007/2/29 14:9:31
Error: Action "ActivateLoggingAction" threw an exception during execution. Error information reported during run:
Datastore exception while trying to write logging properties.
Source File Name: datastore\cachedpropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:27:59 2006
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
-
Failed to find property "primaryLogFiles" {"SetupStateScope", "", ""} in cache
Source File Name: datastore\propertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:28:01 2006
Function Name: SetupStateScope.primaryLogFiles
Source Line Number: 44
-
No collector registered for scope: "SetupStateScope"
00CBCFC4Unable to proceed with setup, there was a command line parsing error. : 2
Error Code: 0x80070002 (2)
Windows Error Text: Le fichier spcifi est introuvable.

Source File Name: datastore\propertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:28:01 2006
Function Name: SetupBootstrapOptionsScope.InstallMediaPath
Source Line Number: 44

Class not registered.
Failed to create CAB file due to datastore exception
Source File Name: datastore\cachedpropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:27:59 2006
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
-
Failed to find property "HostSetup" {"SetupBootstrapOptionsScope", "", "2232"} in cache
Source File Name: datastore\propertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:28:01 2006
Function Name: SetupBootstrapOptionsScope.HostSetup
Source Line Number: 44
-
No collector registered for scope: "SetupBootstrapOptionsScope"
Message pump returning: 2

We really need to get this resolved. Thanks! Jon.

No one has any idea?

Thanks - Jon.

Cannot install SP1

Hi folks,
My Win2003 server won't let me install RS SP1.
It gets about two thirds of the way through the initial progress bar, then tells me this:
SQL Setup failed to connect to the database service for server configuration. Refer to the Server error logs and setup logs for more detailed error information.
I am logged into the server as the same user (a Domain Admin) that installed RS in the first place. I've even tried using the rssetupaccount and rssetuppassword parameters to make it install as the 'sqlservice' user on our domain (the one that runs the SQL Server service).
Our 'Domain Admins' group, as well as the 'sqlservice' user, has dbo rights to the ReportServer database. I've even tried adding 'BUILTIN\Administrators' to the user-list of the db and giving it dbo rights, then logging in as the local Administrator user on the server - still get the same error.
What else can I try?
Thanks in advance,
MattTry using a sql account when passing in the rssetupaccount and
rssetuppassword.
Do you have Terminal services for applications turned on? That may be
causing this issue as well. Even so, using a sql account during setup
should solve the issue.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Matt Hamilton" <Matt Hamilton@.discussions.microsoft.com> wrote in message
news:F34F7448-4D94-468C-A362-E809BE1B56EE@.microsoft.com...
> Hi folks,
> My Win2003 server won't let me install RS SP1.
> It gets about two thirds of the way through the initial progress bar, then
tells me this:
> SQL Setup failed to connect to the database service for server
configuration. Refer to the Server error logs and setup logs for more
detailed error information.
> I am logged into the server as the same user (a Domain Admin) that
installed RS in the first place. I've even tried using the rssetupaccount
and rssetuppassword parameters to make it install as the 'sqlservice' user
on our domain (the one that runs the SQL Server service).
> Our 'Domain Admins' group, as well as the 'sqlservice' user, has dbo
rights to the ReportServer database. I've even tried adding
'BUILTIN\Administrators' to the user-list of the db and giving it dbo
rights, then logging in as the local Administrator user on the server -
still get the same error.
> What else can I try?
> Thanks in advance,
> Matt|||"Daniel Reib [MSFT]" wrote:
> Try using a sql account when passing in the rssetupaccount and
> rssetuppassword.
> Do you have Terminal services for applications turned on? That may be
> causing this issue as well. Even so, using a sql account during setup
> should solve the issue.
The only TS thing we're using is the Remote Desktop functionality.
I tried running this:
e:\rssp1\sp1setup.exe rssetupaccount=sa rssetuppassword=<our sa password>
And it still threw the same error.
Interestingly, it also brings up a prompt to send an error report to MS when I click OK on the error dialog.
I've installed SP1 with no problems at all on one of our other servers (running Win2k rather than Win2003). Argh! Please help!
Matt|||The parameters are case sensitive. Did you use RSSETUPACCOUNT &
RSSETUPPASSWORD?
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Matt Hamilton" <Matt Hamilton@.discussions.microsoft.com> wrote in message
news:13231C67-50A3-4A59-9D15-040E24183592@.microsoft.com...
> "Daniel Reib [MSFT]" wrote:
> > Try using a sql account when passing in the rssetupaccount and
> > rssetuppassword.
> >
> > Do you have Terminal services for applications turned on? That may be
> > causing this issue as well. Even so, using a sql account during setup
> > should solve the issue.
> The only TS thing we're using is the Remote Desktop functionality.
> I tried running this:
> e:\rssp1\sp1setup.exe rssetupaccount=sa rssetuppassword=<our sa password>
> And it still threw the same error.
> Interestingly, it also brings up a prompt to send an error report to MS
when I click OK on the error dialog.
> I've installed SP1 with no problems at all on one of our other servers
(running Win2k rather than Win2003). Argh! Please help!
> Matt|||No! I didn't!
I'll try that next. Thanks, Daniel.
Case-sensitive parameters, eh? That's a first.
"Daniel Reib [MSFT]" wrote:
> The parameters are case sensitive. Did you use RSSETUPACCOUNT &
> RSSETUPPASSWORD?
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Matt Hamilton" <Matt Hamilton@.discussions.microsoft.com> wrote in message
> news:13231C67-50A3-4A59-9D15-040E24183592@.microsoft.com...
> > "Daniel Reib [MSFT]" wrote:
> >
> > > Try using a sql account when passing in the rssetupaccount and
> > > rssetuppassword.
> > >
> > > Do you have Terminal services for applications turned on? That may be
> > > causing this issue as well. Even so, using a sql account during setup
> > > should solve the issue.
> >
> > The only TS thing we're using is the Remote Desktop functionality.
> >
> > I tried running this:
> >
> > e:\rssp1\sp1setup.exe rssetupaccount=sa rssetuppassword=<our sa password>
> >
> > And it still threw the same error.
> >
> > Interestingly, it also brings up a prompt to send an error report to MS
> when I click OK on the error dialog.
> >
> > I've installed SP1 with no problems at all on one of our other servers
> (running Win2k rather than Win2003). Argh! Please help!
> >
> > Matt
>
>|||Actually not for Windows Installer. They use case to determine scope.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Matt Hamilton" <MattHamilton@.discussions.microsoft.com> wrote in message
news:AD74DFAD-9735-465F-B75C-214E982D07AB@.microsoft.com...
> No! I didn't!
> I'll try that next. Thanks, Daniel.
> Case-sensitive parameters, eh? That's a first.
> "Daniel Reib [MSFT]" wrote:
> > The parameters are case sensitive. Did you use RSSETUPACCOUNT &
> > RSSETUPPASSWORD?
> >
> > --
> > -Daniel
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "Matt Hamilton" <Matt Hamilton@.discussions.microsoft.com> wrote in
message
> > news:13231C67-50A3-4A59-9D15-040E24183592@.microsoft.com...
> > > "Daniel Reib [MSFT]" wrote:
> > >
> > > > Try using a sql account when passing in the rssetupaccount and
> > > > rssetuppassword.
> > > >
> > > > Do you have Terminal services for applications turned on? That may
be
> > > > causing this issue as well. Even so, using a sql account during
setup
> > > > should solve the issue.
> > >
> > > The only TS thing we're using is the Remote Desktop functionality.
> > >
> > > I tried running this:
> > >
> > > e:\rssp1\sp1setup.exe rssetupaccount=sa rssetuppassword=<our sa
password>
> > >
> > > And it still threw the same error.
> > >
> > > Interestingly, it also brings up a prompt to send an error report to
MS
> > when I click OK on the error dialog.
> > >
> > > I've installed SP1 with no problems at all on one of our other servers
> > (running Win2k rather than Win2003). Argh! Please help!
> > >
> > > Matt
> >
> >
> >|||In case anyone's interested:
One of our techies, when trying to resolve something else, uninstalled and reinstalled IIS on our server the other day, breaking RS.
So I uninstalled and reinstalled RS ... and then (thinking, "what the hell?") tried installing SP1 - and this time it worked.
We changed nothing, so I have no idea what was stopping us from installing SP1 in the first place.
So if you have similar problems, try uninstalling & reinstalling.
Cheers,
Matt|||In case anyone's interested:
One of our techies, when trying to resolve something else, uninstalled and reinstalled IIS on our server the other day, breaking RS.
So I uninstalled and reinstalled RS ... and then (thinking, "what the hell?") tried installing SP1 - and this time it worked.
We changed nothing, so I have no idea what was stopping us from installing SP1 in the first place.
So if you have similar problems, try uninstalling & reinstalling.
Cheers,
Matt|||In case anyone's interested:
One of our techies, when trying to resolve something else, uninstalled and reinstalled IIS on our server the other day, breaking RS.
So I uninstalled and reinstalled RS ... and then (thinking, "what the hell?") tried installing SP1 - and this time it worked.
We changed nothing, so I have no idea what was stopping us from installing SP1 in the first place.
So if you have similar problems, try uninstalling & reinstalling.
Cheers,
Matt