I am in Enterprise Manager on ComputerA, logged in as user xyz. I am
attempting to add a new SQL Server registration for the SQL Server on
ComputerB, using SQL Server authentication based on SQL Server login abc. Th
e
registration fails, stating that the SQL Server does not exist or access is
denied. The Security Event Log on ComputerB indicates a login failure to the
account xyz, which does not exist on ComputerB. Why is the registration
attempt trying to log into a non-existent Windows account when I have
requested SQL Server authentication? TIA...Sounds like it could be that it's trying to connect using
named pipes. Check the order of the protocols using the
client network utility and try setting TCP/IP as the first
protocol if it already isn't the first one listed.
Or use the client network utility and create a TCP/IP alias
to ComputerB on ComputerA
-Sue
On Tue, 5 Jul 2005 12:19:05 -0700, "Steve B."
<SteveB@.discussions.microsoft.com> wrote:
>I am in Enterprise Manager on ComputerA, logged in as user xyz. I am
>attempting to add a new SQL Server registration for the SQL Server on
>ComputerB, using SQL Server authentication based on SQL Server login abc. T
he
>registration fails, stating that the SQL Server does not exist or access is
>denied. The Security Event Log on ComputerB indicates a login failure to th
e
>account xyz, which does not exist on ComputerB. Why is the registration
>attempt trying to log into a non-existent Windows account when I have
>requested SQL Server authentication? TIA...|||Thanks for your reply. Per your suggestion, I changed the order of the
protocols listed in the Client Network Utility, and I had already tried
creating the TCP/IP alias for ComputerB, but I tried it again. All to no
avail... :-(
"Sue Hoegemeier" wrote:
> Sounds like it could be that it's trying to connect using
> named pipes. Check the order of the protocols using the
> client network utility and try setting TCP/IP as the first
> protocol if it already isn't the first one listed.
> Or use the client network utility and create a TCP/IP alias
> to ComputerB on ComputerA
> -Sue
> On Tue, 5 Jul 2005 12:19:05 -0700, "Steve B."
> <SteveB@.discussions.microsoft.com> wrote:
>
>|||I thought I'd close this loop, in case others might benefit. The problem was
resolved by creating synchronized accounts on ComputerA and ComputerB.
ComputerB is a W2K3 system, and it appears that account synchronization is
required on W2K3 even when you're using SQL Server authentication. So I
wonder why you'd ever bother with SQL Server authentication on W2K3?
"Steve B." wrote:
[vbcol=seagreen]
> Thanks for your reply. Per your suggestion, I changed the order of the
> protocols listed in the Client Network Utility, and I had already tried
> creating the TCP/IP alias for ComputerB, but I tried it again. All to no
> avail... :-(
> "Sue Hoegemeier" wrote:
>|||It's not a requirement. Synching the accounts and passwords
is in non-domain settings sometimes but it's to allow
Windows authentication. If you are specifying SQL
authentication and Windows is used instead then you have
something else that's a problem. You may want to check what
protocol you are actually connecting with - the net library
is listed in sysprocesses. You may also want to run
component check to verify your MDAC installation. You can
download it from:
http://msdn.microsoft.com/data/mdac...ds/default.aspx
-Sue
On Tue, 12 Jul 2005 08:44:05 -0700, "Steve B."
<SteveB@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>I thought I'd close this loop, in case others might benefit. The problem wa
s
>resolved by creating synchronized accounts on ComputerA and ComputerB.
>ComputerB is a W2K3 system, and it appears that account synchronization is
>required on W2K3 even when you're using SQL Server authentication. So I
>wonder why you'd ever bother with SQL Server authentication on W2K3?
>"Steve B." wrote:
>
Saturday, February 25, 2012
Registration Fails
For years I've had a server registration using sql server auth set up...now it's failing...can't be found not suthed BS...
I can still see mu other boxes in sql mode, and otyhers in mixed, and I can still see my remote boxes in Ireland and Pennysylvania...we're in NJ..
The person next to me does the same thing, had to reboot, but was fine.
I get ice in the winter...
bizzare-o world.
Any ideas?
Never seen anything like it...
I do know that our tech group has been doing some pushes lately...but I checked my settings and they seem fine..but why would I be able to see everything else but this one instance?...are you registering by IP or DNS name? I know that when i've had problems between here and the great state of Maine I had to reregister using the servers IP.|||can you ping its ip? what does a trace do?|||DNS and I can ping it....|||are you able to ping it both by IP and DNS? (if you can't by DNS ya might try and register it by it's IP)...|||Just tried..I can ping by both...I'm gonna go over and bother the other guy who's connecting to see what's different...|||OK, it was suggested that I try an osql connection from dos...
fact is I already tried that...
BUT it is a great point...for some reason the error message are more helpful..it's like QA interferes with the message...
Then I said, what about bcp...and I got a message I never saw before
C:\>bcp northwind.dbo.orders out orders.txt -SNJROS1D15\NJROS1D151DEV -Usa -Ppwd
CTLIB Message: - L6/O8/S5/N3/5/0:ct_connect(): directory service layer: internal directory control layer error: Requested server name not found.
Establishing connection failed.
C:\>
I'm going to try bcp from another box from xp_cmdshell|||Have you installed a Sybase client recently?|||I have a Sybase client AND server running and have no prob.
Brett, did your nw guys push something on the client as well? Try odbcping (of course it'll fail, but try with different security switches) Also, did you happen to do anything in terms of aliasing experimentation? Or maybe in Server Network Configuration on the offending server (sounds like it's offending your intelligence, doesn't it?;)|||The few times I have seen BCP fail with a ct_connect error, it was a Sybase bcp attempting to talk to a MS SQL Server. The problem I always have is that Sybase adds itself to the beginning of the PATH environment variable, so you tend to get it first. I have no doubt you can force the two to get along. Probably only take a couple rolls of duct tape. Here is the error I get for trying to connect to no server:
bcp pubs..authors out auth.txt /Sgarbage /T
SQLState = 08001, NativeError = 17
Error = [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.
SQLState = 01000, NativeError = 53
Warning = [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).|||Another possiblity would be hav eyou gotten a beta version of Windows XP SP2? Rumour has it that this will come with a built-in firewall that will block port 1433 by default.
http://www.microsoft.com/sql/techinfo/administration/2000/security/winxpsp2faq.asp
I think we will all be having to play around with this, before our desktop groups get the idea into their heads that they need to deploy this service pack overnight.|||Yup, you're right, I forgot about common utility names. And CTLIB is very suspicious in the content of your error...aka CTlib API, which is Sybase's new web.sql API. Are you screwing with Sybase, Brett?|||Yup installed sysbase months agao...
I like the combiniation of errors thing...yes I think our server ops pushed something last week...
Got the Alias thing to work with the ip address...
What bugs me is that my other NJ is ok..probably on an isolated domain, as well as PA and Ireland...but that doesn't explain PROD on the same network...|||Are you screwing with Sybase, Brett?
Hey, I bought her a drink...
sybase, oracle, db2, sql server....all the same...just a different dress...
Was looking at mySQL...now that's a wolfer...kinda like acess...and now that I say that is access an rdbms? It's definetley not client server...how about foxpro DBaseIII...man they're just to many of them...
which platform would you like to choose?
It's this gdamn network crap I hate...
EDIT: Does Mac have an RDBMS? :eek:|||I have had intermittent problems with Enterprise Mangler where the connection would timeout under TCP/IP, but would be fine under Named Pipes. I never found a rhyme or reason to it. See what happens when you change your default net library in the Client Network Utility. Pretty much reduced to groping at, er...grasping at straws here.|||EDIT: Does Mac have an RDBMS? :eek:
As a matter of fact...sort of. There is a product called 4th Dimension that is an Access-like application. I am not certain if there are any Mac servers to start with. There very well could be, though.|||My original protocal order was Pipes then TCP/IP...when I switched (to enable the alias so I could get some work done), and then tried the bcp in dos, I then get the standard not found. not authed bullshit message...|||As a matter of fact...sort of. There is a product called 4th Dimension that is an Access-like application. I am not certain if there are any Mac servers to start with. There very well could be, though.
Yes there are, they are referred to as Linux boxes ;)|||Anyone know where ODBCPING is located?
M$ says it ships with 6.5 and higher...can't find it...|||It's on the CD, you need to copy it from there into your BINN directory. Or, as an alternative, I can put it here, let me know.|||Thanks...all of the stuff is on a lan share..have to look...
That said...are you telling me it's not part of the install? I select everything...and then why isn't it available as a download from M$?
I can still see mu other boxes in sql mode, and otyhers in mixed, and I can still see my remote boxes in Ireland and Pennysylvania...we're in NJ..
The person next to me does the same thing, had to reboot, but was fine.
I get ice in the winter...
bizzare-o world.
Any ideas?
Never seen anything like it...
I do know that our tech group has been doing some pushes lately...but I checked my settings and they seem fine..but why would I be able to see everything else but this one instance?...are you registering by IP or DNS name? I know that when i've had problems between here and the great state of Maine I had to reregister using the servers IP.|||can you ping its ip? what does a trace do?|||DNS and I can ping it....|||are you able to ping it both by IP and DNS? (if you can't by DNS ya might try and register it by it's IP)...|||Just tried..I can ping by both...I'm gonna go over and bother the other guy who's connecting to see what's different...|||OK, it was suggested that I try an osql connection from dos...
fact is I already tried that...
BUT it is a great point...for some reason the error message are more helpful..it's like QA interferes with the message...
Then I said, what about bcp...and I got a message I never saw before
C:\>bcp northwind.dbo.orders out orders.txt -SNJROS1D15\NJROS1D151DEV -Usa -Ppwd
CTLIB Message: - L6/O8/S5/N3/5/0:ct_connect(): directory service layer: internal directory control layer error: Requested server name not found.
Establishing connection failed.
C:\>
I'm going to try bcp from another box from xp_cmdshell|||Have you installed a Sybase client recently?|||I have a Sybase client AND server running and have no prob.
Brett, did your nw guys push something on the client as well? Try odbcping (of course it'll fail, but try with different security switches) Also, did you happen to do anything in terms of aliasing experimentation? Or maybe in Server Network Configuration on the offending server (sounds like it's offending your intelligence, doesn't it?;)|||The few times I have seen BCP fail with a ct_connect error, it was a Sybase bcp attempting to talk to a MS SQL Server. The problem I always have is that Sybase adds itself to the beginning of the PATH environment variable, so you tend to get it first. I have no doubt you can force the two to get along. Probably only take a couple rolls of duct tape. Here is the error I get for trying to connect to no server:
bcp pubs..authors out auth.txt /Sgarbage /T
SQLState = 08001, NativeError = 17
Error = [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.
SQLState = 01000, NativeError = 53
Warning = [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).|||Another possiblity would be hav eyou gotten a beta version of Windows XP SP2? Rumour has it that this will come with a built-in firewall that will block port 1433 by default.
http://www.microsoft.com/sql/techinfo/administration/2000/security/winxpsp2faq.asp
I think we will all be having to play around with this, before our desktop groups get the idea into their heads that they need to deploy this service pack overnight.|||Yup, you're right, I forgot about common utility names. And CTLIB is very suspicious in the content of your error...aka CTlib API, which is Sybase's new web.sql API. Are you screwing with Sybase, Brett?|||Yup installed sysbase months agao...
I like the combiniation of errors thing...yes I think our server ops pushed something last week...
Got the Alias thing to work with the ip address...
What bugs me is that my other NJ is ok..probably on an isolated domain, as well as PA and Ireland...but that doesn't explain PROD on the same network...|||Are you screwing with Sybase, Brett?
Hey, I bought her a drink...
sybase, oracle, db2, sql server....all the same...just a different dress...
Was looking at mySQL...now that's a wolfer...kinda like acess...and now that I say that is access an rdbms? It's definetley not client server...how about foxpro DBaseIII...man they're just to many of them...
which platform would you like to choose?
It's this gdamn network crap I hate...
EDIT: Does Mac have an RDBMS? :eek:|||I have had intermittent problems with Enterprise Mangler where the connection would timeout under TCP/IP, but would be fine under Named Pipes. I never found a rhyme or reason to it. See what happens when you change your default net library in the Client Network Utility. Pretty much reduced to groping at, er...grasping at straws here.|||EDIT: Does Mac have an RDBMS? :eek:
As a matter of fact...sort of. There is a product called 4th Dimension that is an Access-like application. I am not certain if there are any Mac servers to start with. There very well could be, though.|||My original protocal order was Pipes then TCP/IP...when I switched (to enable the alias so I could get some work done), and then tried the bcp in dos, I then get the standard not found. not authed bullshit message...|||As a matter of fact...sort of. There is a product called 4th Dimension that is an Access-like application. I am not certain if there are any Mac servers to start with. There very well could be, though.
Yes there are, they are referred to as Linux boxes ;)|||Anyone know where ODBCPING is located?
M$ says it ships with 6.5 and higher...can't find it...|||It's on the CD, you need to copy it from there into your BINN directory. Or, as an alternative, I can put it here, let me know.|||Thanks...all of the stuff is on a lan share..have to look...
That said...are you telling me it's not part of the install? I select everything...and then why isn't it available as a download from M$?
Registration error
Hi,
I am able to register other SQL server instances but when
I try to register one in particular I am getting this
error on the main server to which I need to register all
of the satelite servers. Can anyone help with this
problem? I don't understand why it is using a null
account instead of the guest account to try to log into
this particular instance.
Login failed for user '(null)'. Reason: Not associated
with a Trusted SQl Server connectionthat server is setup for Windows Authentication and you are logging in using
SQL login?
"Narine" <narinep@.siu.edu> wrote in message
news:2379e01c38c41$872a6010$a601280a@.phx.gbl...
> Hi,
> I am able to register other SQL server instances but when
> I try to register one in particular I am getting this
> error on the main server to which I need to register all
> of the satelite servers. Can anyone help with this
> problem? I don't understand why it is using a null
> account instead of the guest account to try to log into
> this particular instance.
>
> Login failed for user '(null)'. Reason: Not associated
> with a Trusted SQl Server connection|||I am just using windows authentication only because I am
using the datbase with MS VB.NET 2002 and I am doing
merge replication with subscribers.
>--Original Message--
>that server is setup for Windows Authentication and you
are logging in using
>SQL login?
>"Narine" <narinep@.siu.edu> wrote in message
>news:2379e01c38c41$872a6010$a601280a@.phx.gbl...
>> Hi,
>> I am able to register other SQL server instances but
when
>> I try to register one in particular I am getting this
>> error on the main server to which I need to register
all
>> of the satelite servers. Can anyone help with this
>> problem? I don't understand why it is using a null
>> account instead of the guest account to try to log into
>> this particular instance.
>>
>> Login failed for user '(null)'. Reason: Not associated
>> with a Trusted SQl Server connection
>
>.
>|||Check if the server you are trying to connect to is set to
Windows Authentication Only and change the security
settings to SQL Server and Windows. It seems that you are
using SQL authentication yourself and the other machine is
set to Windows Authentication only.
Edgardo Valdez
MCSD, MCDBA, MCSE, MCP+I
http://www.edgardovaldez.us/
>--Original Message--
>Hi,
>I am able to register other SQL server instances but when
>I try to register one in particular I am getting this
>error on the main server to which I need to register all
>of the satelite servers. Can anyone help with this
>problem? I don't understand why it is using a null
>account instead of the guest account to try to log into
>this particular instance.
>
>Login failed for user '(null)'. Reason: Not associated
>with a Trusted SQl Server connection
>.
>|||All of the servers are set to use Windows authentication
only originally when I installed them and this is stil so
when i just checked them. Could there be another reason
the main server is using the null account instead of the
guest account to register with the satelite server? How
can I set this parameter?
>--Original Message--
>Check if the server you are trying to connect to is set
to
>Windows Authentication Only and change the security
>settings to SQL Server and Windows. It seems that you
are
>using SQL authentication yourself and the other machine
is
>set to Windows Authentication only.
>
>Edgardo Valdez
>MCSD, MCDBA, MCSE, MCP+I
>http://www.edgardovaldez.us/
>>--Original Message--
>>Hi,
>>I am able to register other SQL server instances but
when
>>I try to register one in particular I am getting this
>>error on the main server to which I need to register
all
>>of the satelite servers. Can anyone help with this
>>problem? I don't understand why it is using a null
>>account instead of the guest account to try to log into
>>this particular instance.
>>
>>Login failed for user '(null)'. Reason: Not associated
>>with a Trusted SQl Server connection
>>.
>.
>|||Check this article and see if it applies to you:
http://support.microsoft.com/default.aspx?scid=kb;en-
us;Q279526
Edgardo Valdez
MCSD, MCDBA, MCSE, MCP+I
http://www.edgardovaldez.us/
>--Original Message--
>All of the servers are set to use Windows authentication
>only originally when I installed them and this is stil so
>when i just checked them. Could there be another reason
>the main server is using the null account instead of the
>guest account to register with the satelite server? How
>can I set this parameter?
>
>>--Original Message--
>>Check if the server you are trying to connect to is set
>to
>>Windows Authentication Only and change the security
>>settings to SQL Server and Windows. It seems that you
>are
>>using SQL authentication yourself and the other machine
>is
>>set to Windows Authentication only.
>>
>>Edgardo Valdez
>>MCSD, MCDBA, MCSE, MCP+I
>>http://www.edgardovaldez.us/
>>--Original Message--
>>Hi,
>>I am able to register other SQL server instances but
>when
>>I try to register one in particular I am getting this
>>error on the main server to which I need to register
>all
>>of the satelite servers. Can anyone help with this
>>problem? I don't understand why it is using a null
>>account instead of the guest account to try to log into
>>this particular instance.
>>
>>Login failed for user '(null)'. Reason: Not associated
>>with a Trusted SQl Server connection
>>.
>>.
>.
>|||I have installed SP3 for MSSQL server for the desktop and
server version of mssql server 2000 and these included
the latest MDAC components. Should I go ahead and install
MDAC 8? could this be an SP3 problem? should I install
SP3a?
>--Original Message--
>Check this article and see if it applies to you:
>http://support.microsoft.com/default.aspx?scid=kb;en-
>us;Q279526
>
>Edgardo Valdez
>MCSD, MCDBA, MCSE, MCP+I
>http://www.edgardovaldez.us/
>>--Original Message--
>>All of the servers are set to use Windows
authentication
>>only originally when I installed them and this is stil
so
>>when i just checked them. Could there be another reason
>>the main server is using the null account instead of
the
>>guest account to register with the satelite server? How
>>can I set this parameter?
>>
>>--Original Message--
>>Check if the server you are trying to connect to is
set
>>to
>>Windows Authentication Only and change the security
>>settings to SQL Server and Windows. It seems that you
>>are
>>using SQL authentication yourself and the other
machine
>>is
>>set to Windows Authentication only.
>>
>>Edgardo Valdez
>>MCSD, MCDBA, MCSE, MCP+I
>>http://www.edgardovaldez.us/
>>--Original Message--
>>Hi,
>>I am able to register other SQL server instances but
>>when
>>I try to register one in particular I am getting this
>>error on the main server to which I need to register
>>all
>>of the satelite servers. Can anyone help with this
>>problem? I don't understand why it is using a null
>>account instead of the guest account to try to log
into
>>this particular instance.
>>
>>Login failed for user '(null)'. Reason: Not
associated
>>with a Trusted SQl Server connection
>>.
>>.
>>.
>.
>
I am able to register other SQL server instances but when
I try to register one in particular I am getting this
error on the main server to which I need to register all
of the satelite servers. Can anyone help with this
problem? I don't understand why it is using a null
account instead of the guest account to try to log into
this particular instance.
Login failed for user '(null)'. Reason: Not associated
with a Trusted SQl Server connectionthat server is setup for Windows Authentication and you are logging in using
SQL login?
"Narine" <narinep@.siu.edu> wrote in message
news:2379e01c38c41$872a6010$a601280a@.phx.gbl...
> Hi,
> I am able to register other SQL server instances but when
> I try to register one in particular I am getting this
> error on the main server to which I need to register all
> of the satelite servers. Can anyone help with this
> problem? I don't understand why it is using a null
> account instead of the guest account to try to log into
> this particular instance.
>
> Login failed for user '(null)'. Reason: Not associated
> with a Trusted SQl Server connection|||I am just using windows authentication only because I am
using the datbase with MS VB.NET 2002 and I am doing
merge replication with subscribers.
>--Original Message--
>that server is setup for Windows Authentication and you
are logging in using
>SQL login?
>"Narine" <narinep@.siu.edu> wrote in message
>news:2379e01c38c41$872a6010$a601280a@.phx.gbl...
>> Hi,
>> I am able to register other SQL server instances but
when
>> I try to register one in particular I am getting this
>> error on the main server to which I need to register
all
>> of the satelite servers. Can anyone help with this
>> problem? I don't understand why it is using a null
>> account instead of the guest account to try to log into
>> this particular instance.
>>
>> Login failed for user '(null)'. Reason: Not associated
>> with a Trusted SQl Server connection
>
>.
>|||Check if the server you are trying to connect to is set to
Windows Authentication Only and change the security
settings to SQL Server and Windows. It seems that you are
using SQL authentication yourself and the other machine is
set to Windows Authentication only.
Edgardo Valdez
MCSD, MCDBA, MCSE, MCP+I
http://www.edgardovaldez.us/
>--Original Message--
>Hi,
>I am able to register other SQL server instances but when
>I try to register one in particular I am getting this
>error on the main server to which I need to register all
>of the satelite servers. Can anyone help with this
>problem? I don't understand why it is using a null
>account instead of the guest account to try to log into
>this particular instance.
>
>Login failed for user '(null)'. Reason: Not associated
>with a Trusted SQl Server connection
>.
>|||All of the servers are set to use Windows authentication
only originally when I installed them and this is stil so
when i just checked them. Could there be another reason
the main server is using the null account instead of the
guest account to register with the satelite server? How
can I set this parameter?
>--Original Message--
>Check if the server you are trying to connect to is set
to
>Windows Authentication Only and change the security
>settings to SQL Server and Windows. It seems that you
are
>using SQL authentication yourself and the other machine
is
>set to Windows Authentication only.
>
>Edgardo Valdez
>MCSD, MCDBA, MCSE, MCP+I
>http://www.edgardovaldez.us/
>>--Original Message--
>>Hi,
>>I am able to register other SQL server instances but
when
>>I try to register one in particular I am getting this
>>error on the main server to which I need to register
all
>>of the satelite servers. Can anyone help with this
>>problem? I don't understand why it is using a null
>>account instead of the guest account to try to log into
>>this particular instance.
>>
>>Login failed for user '(null)'. Reason: Not associated
>>with a Trusted SQl Server connection
>>.
>.
>|||Check this article and see if it applies to you:
http://support.microsoft.com/default.aspx?scid=kb;en-
us;Q279526
Edgardo Valdez
MCSD, MCDBA, MCSE, MCP+I
http://www.edgardovaldez.us/
>--Original Message--
>All of the servers are set to use Windows authentication
>only originally when I installed them and this is stil so
>when i just checked them. Could there be another reason
>the main server is using the null account instead of the
>guest account to register with the satelite server? How
>can I set this parameter?
>
>>--Original Message--
>>Check if the server you are trying to connect to is set
>to
>>Windows Authentication Only and change the security
>>settings to SQL Server and Windows. It seems that you
>are
>>using SQL authentication yourself and the other machine
>is
>>set to Windows Authentication only.
>>
>>Edgardo Valdez
>>MCSD, MCDBA, MCSE, MCP+I
>>http://www.edgardovaldez.us/
>>--Original Message--
>>Hi,
>>I am able to register other SQL server instances but
>when
>>I try to register one in particular I am getting this
>>error on the main server to which I need to register
>all
>>of the satelite servers. Can anyone help with this
>>problem? I don't understand why it is using a null
>>account instead of the guest account to try to log into
>>this particular instance.
>>
>>Login failed for user '(null)'. Reason: Not associated
>>with a Trusted SQl Server connection
>>.
>>.
>.
>|||I have installed SP3 for MSSQL server for the desktop and
server version of mssql server 2000 and these included
the latest MDAC components. Should I go ahead and install
MDAC 8? could this be an SP3 problem? should I install
SP3a?
>--Original Message--
>Check this article and see if it applies to you:
>http://support.microsoft.com/default.aspx?scid=kb;en-
>us;Q279526
>
>Edgardo Valdez
>MCSD, MCDBA, MCSE, MCP+I
>http://www.edgardovaldez.us/
>>--Original Message--
>>All of the servers are set to use Windows
authentication
>>only originally when I installed them and this is stil
so
>>when i just checked them. Could there be another reason
>>the main server is using the null account instead of
the
>>guest account to register with the satelite server? How
>>can I set this parameter?
>>
>>--Original Message--
>>Check if the server you are trying to connect to is
set
>>to
>>Windows Authentication Only and change the security
>>settings to SQL Server and Windows. It seems that you
>>are
>>using SQL authentication yourself and the other
machine
>>is
>>set to Windows Authentication only.
>>
>>Edgardo Valdez
>>MCSD, MCDBA, MCSE, MCP+I
>>http://www.edgardovaldez.us/
>>--Original Message--
>>Hi,
>>I am able to register other SQL server instances but
>>when
>>I try to register one in particular I am getting this
>>error on the main server to which I need to register
>>all
>>of the satelite servers. Can anyone help with this
>>problem? I don't understand why it is using a null
>>account instead of the guest account to try to log
into
>>this particular instance.
>>
>>Login failed for user '(null)'. Reason: Not
associated
>>with a Trusted SQl Server connection
>>.
>>.
>>.
>.
>
Registration edit for replication ?
I have a laptop on a LAN and I have pushed a new subscription to it. Now I
want to move the Laptop to its proper location (in another city for example)
and replicate to it via the internet.
Can I simply edit the server registration at the Publisher?
thank you,
bob
Bob,
assuming you don't intend to reinitialize, AFAIK there is no new
configuration necessarily required on the publisher. However, on the
subscriber there are various stipulations:
It'll need to be set up as a pull subscriber.
On the laptop you'll need to set up an alias in the client network utility
and place an entry in the hosts file to recognise the publisher.
For security, the pull agent will need to be set up to use SQL
authentication or passthrough windows authentication.
If you want to subsequently reinitialize, then changes will be necessary on
the publisher. You'll need to set @.enabled_for_internet = true so that FTP
can be used to download the snapshot.
HTH,
Paul Ibison
|||no. The subscriber in this case is probably set up for an push. Exactly how
is the publisher going to find the subscriber over the internet.
To get this to work you would have to update the lmhosts and/or the hosts
file for the new ip address, Client Network Utiltity for the new ip address.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Robert A. DiFrancesco" <bob.difrancesco@.comcash.com> wrote in message
news:eSDh92DZEHA.2408@.tk2msftngp13.phx.gbl...
> I have a laptop on a LAN and I have pushed a new subscription to it. Now
I
> want to move the Laptop to its proper location (in another city for
example)
> and replicate to it via the internet.
> Can I simply edit the server registration at the Publisher?
>
> thank you,
> bob
>
want to move the Laptop to its proper location (in another city for example)
and replicate to it via the internet.
Can I simply edit the server registration at the Publisher?
thank you,
bob
Bob,
assuming you don't intend to reinitialize, AFAIK there is no new
configuration necessarily required on the publisher. However, on the
subscriber there are various stipulations:
It'll need to be set up as a pull subscriber.
On the laptop you'll need to set up an alias in the client network utility
and place an entry in the hosts file to recognise the publisher.
For security, the pull agent will need to be set up to use SQL
authentication or passthrough windows authentication.
If you want to subsequently reinitialize, then changes will be necessary on
the publisher. You'll need to set @.enabled_for_internet = true so that FTP
can be used to download the snapshot.
HTH,
Paul Ibison
|||no. The subscriber in this case is probably set up for an push. Exactly how
is the publisher going to find the subscriber over the internet.
To get this to work you would have to update the lmhosts and/or the hosts
file for the new ip address, Client Network Utiltity for the new ip address.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Robert A. DiFrancesco" <bob.difrancesco@.comcash.com> wrote in message
news:eSDh92DZEHA.2408@.tk2msftngp13.phx.gbl...
> I have a laptop on a LAN and I have pushed a new subscription to it. Now
I
> want to move the Laptop to its proper location (in another city for
example)
> and replicate to it via the internet.
> Can I simply edit the server registration at the Publisher?
>
> thank you,
> bob
>
Registration card returned by post office.
I recently purchased SQL Server 2000 Developer Edition
here in Canada. I mailed the registration card to the
P.O. Box in San Francisco as indicated on the
accompanying documentation.
The post office has returned the card with a stamp that
says "Box Closed: Forwarding Order Expired".
As I did not get asked to register on-line when I
installed the product, how do I register that I have
acquired this product ?Chris,
The best is to call the local MS subsidiary. Check the numbers at
www.microsoft.com/canada.
--
Dejan Sarka, SQL Server MVP
Please reply only to the newsgroups.
"Chris Smith" <chris.smith@.shaw.ca> wrote in message
news:088701c39fe5$f1774ac0$a001280a@.phx.gbl...
> I recently purchased SQL Server 2000 Developer Edition
> here in Canada. I mailed the registration card to the
> P.O. Box in San Francisco as indicated on the
> accompanying documentation.
> The post office has returned the card with a stamp that
> says "Box Closed: Forwarding Order Expired".
> As I did not get asked to register on-line when I
> installed the product, how do I register that I have
> acquired this product ?
here in Canada. I mailed the registration card to the
P.O. Box in San Francisco as indicated on the
accompanying documentation.
The post office has returned the card with a stamp that
says "Box Closed: Forwarding Order Expired".
As I did not get asked to register on-line when I
installed the product, how do I register that I have
acquired this product ?Chris,
The best is to call the local MS subsidiary. Check the numbers at
www.microsoft.com/canada.
--
Dejan Sarka, SQL Server MVP
Please reply only to the newsgroups.
"Chris Smith" <chris.smith@.shaw.ca> wrote in message
news:088701c39fe5$f1774ac0$a001280a@.phx.gbl...
> I recently purchased SQL Server 2000 Developer Edition
> here in Canada. I mailed the registration card to the
> P.O. Box in San Francisco as indicated on the
> accompanying documentation.
> The post office has returned the card with a stamp that
> says "Box Closed: Forwarding Order Expired".
> As I did not get asked to register on-line when I
> installed the product, how do I register that I have
> acquired this product ?
Registration Benefit Portal - Page Nopt Found
Hi, this text is taken from the FAQ and contains the same link the Registration email I received, which don't work (for me!). The link points to http://go.microsoft.com/fwlink/?LinkId=52054. Does anyone else have this problem?
NOTE: You can directly access the Registration Benefit Portal without need of a first or second benefit e-mail—as long as you have completed the registration process and use the same e-mail to login in to Passport at the benefit porta
Hmm, working now!
registration and Replicatons
Is registration of the subscriber required to configure replications.
I am configuring replications over the internet using a VPN connection
and do not want the Publisher/Distributor (Publisher and Distributor
are the same) to have the Subscriber registered. I know you can add a
subscriber using the system stored procedure but I was wondering if
registration of the subscriber was a requirement to perform
replication.
Thank you in advance for your help.
It is required.
You must register the servers in your hosts file, client configuration utility, and EM. Then you must enable your subscriber using SQL Server authentication.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Gent" wrote:
> Is registration of the subscriber required to configure replications.
> I am configuring replications over the internet using a VPN connection
> and do not want the Publisher/Distributor (Publisher and Distributor
> are the same) to have the Subscriber registered. I know you can add a
> subscriber using the system stored procedure but I was wondering if
> registration of the subscriber was a requirement to perform
> replication.
> Thank you in advance for your help.
>
I am configuring replications over the internet using a VPN connection
and do not want the Publisher/Distributor (Publisher and Distributor
are the same) to have the Subscriber registered. I know you can add a
subscriber using the system stored procedure but I was wondering if
registration of the subscriber was a requirement to perform
replication.
Thank you in advance for your help.
It is required.
You must register the servers in your hosts file, client configuration utility, and EM. Then you must enable your subscriber using SQL Server authentication.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Gent" wrote:
> Is registration of the subscriber required to configure replications.
> I am configuring replications over the internet using a VPN connection
> and do not want the Publisher/Distributor (Publisher and Distributor
> are the same) to have the Subscriber registered. I know you can add a
> subscriber using the system stored procedure but I was wondering if
> registration of the subscriber was a requirement to perform
> replication.
> Thank you in advance for your help.
>
Registration access denied
Am I able to register SQL2005 server in Enterprise Manager of SQL2000, or SQL2000 server in SQL Server Management Studio?
You can use enterprise manager from sql 2005 to administer both sql 2000 and sql 2005 databases.
I doubt that the enterprise manager from sql 2000 would work with a sql 2005 database.
|||How should I use enterprise manager in SQL2005?|||Its Management Studio.
From Management Studio, you can connect to both sql 2000 and sql 2005 databases.
http://www.aspfaq.com/sql2005/show.asp?id=3
|||this SQL Express, is there any stest I can use for SQL 2000?|||Hi
Below is from previous link:
As for connecting to Express from application code, this should not be any different from connecting to a named instance of SQL Server 2000. Your connection string should look like this, assuming local machine and an instance name of SQLEXPRESS (you might need a different instance name, and you may have to use a machine name, rather than "." (which means local)).
Registration access denied
Am I able to register SQL2005 server in Enterprise Manager of SQL2000, or SQL2000 server in SQL Server Management Studio?
you can't use it even if it registers.
here's a story:
i have bothe Enterprise manager and management studio on the same box
what ever i register on the management studio gets registered to EM.
but the problem is i cant open version 9 Db on EM even it i see it on the list of server
Registration
I have a client that is running SQL 2005 Standard edition and they purchased 10 more Cal's, do I have to enter new registration keys, and if so where do you enter them?
Thanks in advance.
Joe
No, you don't have to enter additional reg keys.|||Thank youRegisters 2000 Servers in SS 2005 Management Console
We just set up our first server with SS 2005, and I am getting familiar with the Management Console layout and features. Can someone confirm for me if I can register my SS 2000 databases within the 2005 Management Console and work within that environment on those systems, or whether that will have any consequences or cause harm to the 2000 systems?
Thanks
Judy
Yes you can, and SQL Server 2000 is fully supported as being administered from SQL Server 2005 management studio.|||
Thanks so much Richard. I appreciate the fast reply.
Judy
Registering/licensing DEMO SQLserver....
Hello,
I am new to SQLserver and have installed the DEMO version of SQLserver 2000 on my system. I got it up and running and verified that it was working properly.
I then purchased two CPU's of the standard edition for my system. The software has arrived, but all that arrived are the CD's. I see no key, nor do I see a way to provide a key even if I had one.
I do not know how to proceeed and need help to figure out how to obtain a key or how to enter it if I ever obtain one.
Any help is greatly appreciated!!!!!
Thanks,
JamesActually, your CD's are supposed to be accompanied by invoice where corresponding keys are clearly printed out. If this is not the case you fell victim to some SW scam.|||Ask the vendor for such keys, in general MS software CDs comes with CD key printed on the CD or a paper attached to the CD cover.|||No such keys on the CD or paper. We are trying to get paperwork for the licenses. When I do get it how do I put them in? I saw no place to put a license in the system. I looked at length, but it obviously means I was not looking in the right place!
Anyone know how to put the key into the system?
James|||look in adminstrative tools
open licensing
you can add\update your lic there
when you say DEMO version of SQL Server, what do you mean?|||I take it DEMO means eval version, and Licensing service in Control Panel has nothing to do with Product Key, BTW.|||i didnt think that he was talking about a product key
he mentions
No such keys on the CD or paper. We are trying to get paperwork for the licenses. When I do get it how do I put them in? I saw no place to put a license in the system. I looked at length, but it obviously means I was not looking in the right place!
Anyone know how to put the key into the system?
i assume he is discussing lics and then he mentions keys!!!??
i'm linguistically hogtied.|||I think it is I that is not making myself clear due to the fact that I really do not know. I have never done this before, and I am sure it is a very simple question.
We have ordered two CPU licenses for SQL Server and I have not seen anything that looks like a "key" that I would normally associate as a Microsoft license key. Hence, I think we need the paperwork that goes with the licenses from my vendor as the others have mentioned. I am awaiting that now (I hope).
I think the issues came when I asked how to register (license) the product once I get the license keys. I have found no way to actually put those ubiquitous Microsoft keys in (that I am not in possession of at this time) to any software.
To an old unix person it is a mystery.
Thanks again for putting up with my silliness.
James|||Oh, so you're saying that throughout the installation process you did not have to nor were you asked to enter the Product Key?
Can you send me this CD?|||Are those by any chance "SELECT" CD's? If you work for a corporation with volume licensing, your company may get CDs with their registration number "burned in", and pay for licenses based on inventory rather than buying them at retail.
-PatP|||Yup, that's what it sounds like...unless it's an eval, 90 or 120-day.|||I initially loaded the evaluation version that I downloaded off the web. I was calling this the DEMO version in earlier emails, sorry for that mixup.
I was also told that it was a full copy and all I needed to do was apply my licenses when they arrived. That is where the problem is, both not having the license keys, nor knowing how or being able to find out how to apply them when they do arrive.
I am handling getting the keys, but need to know how to apply them when they come.
James|||So, do you have a CD?|||I do now, but I do not see anything that looks like a Microsoft key anywhere on them. Nor did the paperwork have anything like that.|||Did you buy these CDs from a vendor, or requisition them from some kind of "IT Central" within your organization?
-PatP|||If the CD does NOT have anything like "Evaluation...", then uninstall your eval AFTER BACKING UP MASTER, MSDB, and your own DATABASES (!!!), and proceed with normal installation from the CD. If you do run into "Enter Product Key..." situation, contact your SW vendor or whoever you purchased it from, else - keep going. Once installed, you'll need to restore your master (check Books Online) and msdb, along with your user database. Last, but not least - download and apply SP3.|||Heck, I'm paranoid. I remove the TCP/IP, install SQL 2000, install either sp2 or sp3a, then reboot. Once the box has gone down, then I plug the TCP/IP cable back into it.
-PatP|||Answers:
1) These are licenses we pruchased from a vendor we deal with all the time. I actually got two sets of CD's instead of just one, I guess since I ordered two CPU's worth of licenses.
2) We do not have a site license, we are a small organization and this is the first time we are using SQLserver.
Outlook:
So, it looks like I will need to do the thing I didn't want to do which is de-install the evaluation copy and re-install the real one off CD. Of course I will not do this until I get what looks like Microsoft keys (or the like) in my hands.
Thanks for all the help. Hopefully I can learn more about this stuff and help a few others along the way.
James
I am new to SQLserver and have installed the DEMO version of SQLserver 2000 on my system. I got it up and running and verified that it was working properly.
I then purchased two CPU's of the standard edition for my system. The software has arrived, but all that arrived are the CD's. I see no key, nor do I see a way to provide a key even if I had one.
I do not know how to proceeed and need help to figure out how to obtain a key or how to enter it if I ever obtain one.
Any help is greatly appreciated!!!!!
Thanks,
JamesActually, your CD's are supposed to be accompanied by invoice where corresponding keys are clearly printed out. If this is not the case you fell victim to some SW scam.|||Ask the vendor for such keys, in general MS software CDs comes with CD key printed on the CD or a paper attached to the CD cover.|||No such keys on the CD or paper. We are trying to get paperwork for the licenses. When I do get it how do I put them in? I saw no place to put a license in the system. I looked at length, but it obviously means I was not looking in the right place!
Anyone know how to put the key into the system?
James|||look in adminstrative tools
open licensing
you can add\update your lic there
when you say DEMO version of SQL Server, what do you mean?|||I take it DEMO means eval version, and Licensing service in Control Panel has nothing to do with Product Key, BTW.|||i didnt think that he was talking about a product key
he mentions
No such keys on the CD or paper. We are trying to get paperwork for the licenses. When I do get it how do I put them in? I saw no place to put a license in the system. I looked at length, but it obviously means I was not looking in the right place!
Anyone know how to put the key into the system?
i assume he is discussing lics and then he mentions keys!!!??
i'm linguistically hogtied.|||I think it is I that is not making myself clear due to the fact that I really do not know. I have never done this before, and I am sure it is a very simple question.
We have ordered two CPU licenses for SQL Server and I have not seen anything that looks like a "key" that I would normally associate as a Microsoft license key. Hence, I think we need the paperwork that goes with the licenses from my vendor as the others have mentioned. I am awaiting that now (I hope).
I think the issues came when I asked how to register (license) the product once I get the license keys. I have found no way to actually put those ubiquitous Microsoft keys in (that I am not in possession of at this time) to any software.
To an old unix person it is a mystery.
Thanks again for putting up with my silliness.
James|||Oh, so you're saying that throughout the installation process you did not have to nor were you asked to enter the Product Key?
Can you send me this CD?|||Are those by any chance "SELECT" CD's? If you work for a corporation with volume licensing, your company may get CDs with their registration number "burned in", and pay for licenses based on inventory rather than buying them at retail.
-PatP|||Yup, that's what it sounds like...unless it's an eval, 90 or 120-day.|||I initially loaded the evaluation version that I downloaded off the web. I was calling this the DEMO version in earlier emails, sorry for that mixup.
I was also told that it was a full copy and all I needed to do was apply my licenses when they arrived. That is where the problem is, both not having the license keys, nor knowing how or being able to find out how to apply them when they do arrive.
I am handling getting the keys, but need to know how to apply them when they come.
James|||So, do you have a CD?|||I do now, but I do not see anything that looks like a Microsoft key anywhere on them. Nor did the paperwork have anything like that.|||Did you buy these CDs from a vendor, or requisition them from some kind of "IT Central" within your organization?
-PatP|||If the CD does NOT have anything like "Evaluation...", then uninstall your eval AFTER BACKING UP MASTER, MSDB, and your own DATABASES (!!!), and proceed with normal installation from the CD. If you do run into "Enter Product Key..." situation, contact your SW vendor or whoever you purchased it from, else - keep going. Once installed, you'll need to restore your master (check Books Online) and msdb, along with your user database. Last, but not least - download and apply SP3.|||Heck, I'm paranoid. I remove the TCP/IP, install SQL 2000, install either sp2 or sp3a, then reboot. Once the box has gone down, then I plug the TCP/IP cable back into it.
-PatP|||Answers:
1) These are licenses we pruchased from a vendor we deal with all the time. I actually got two sets of CD's instead of just one, I guess since I ordered two CPU's worth of licenses.
2) We do not have a site license, we are a small organization and this is the first time we are using SQLserver.
Outlook:
So, it looks like I will need to do the thing I didn't want to do which is de-install the evaluation copy and re-install the real one off CD. Of course I will not do this until I get what looks like Microsoft keys (or the like) in my hands.
Thanks for all the help. Hopefully I can learn more about this stuff and help a few others along the way.
James
Registering User changing data
Hello there
I have many tables that i would like to kbow on each record who inserted,
updated data and when it happend?
For this i've learned about function call SUSER_SNAME() that always gives me
the current user who is in the system. For insert case i've solved it
simply: added two fields:
ChangeBy with the SUSER_SNAME() function as default value
ChangeAt with the GETDATE() function as default value
This works fine for Inserting.
But what i need to do for updating: do i have to use a trigger for this?> But what i need to do for updating: do i have to use a trigger for this?
Yes, you can use a trigger. You can also use SQL Profiler for auditing -
check
http://www.sqlservercentral.com/col...ityLearning.com
I have many tables that i would like to kbow on each record who inserted,
updated data and when it happend?
For this i've learned about function call SUSER_SNAME() that always gives me
the current user who is in the system. For insert case i've solved it
simply: added two fields:
ChangeBy with the SUSER_SNAME() function as default value
ChangeAt with the GETDATE() function as default value
This works fine for Inserting.
But what i need to do for updating: do i have to use a trigger for this?> But what i need to do for updating: do i have to use a trigger for this?
Yes, you can use a trigger. You can also use SQL Profiler for auditing -
check
http://www.sqlservercentral.com/col...ityLearning.com
Registering sqldmo.dll
Hi everybody,
I have a problem with registering sqldmo.dll (version 2000) on Win98 on client machine with no sql-server installed.
First I have run the sqlredis.exe and than I have copied all files described in sqlredis.txt into the windows system directory and than I run regsvr32 to register sqldmo.dll. On Win2000 seems to be all OK but on Win98 I got error 0x80040154: DllRegisterServer in sqldmo.dll failed.
Does anybody know what is the source of this problem?Well I have found It!
You have to register atl.dll (for Win9x it have to be ANSI version) before sqldmo.dll - such simply, but Microsoft doesn't mention this nowhere...
I have a problem with registering sqldmo.dll (version 2000) on Win98 on client machine with no sql-server installed.
First I have run the sqlredis.exe and than I have copied all files described in sqlredis.txt into the windows system directory and than I run regsvr32 to register sqldmo.dll. On Win2000 seems to be all OK but on Win98 I got error 0x80040154: DllRegisterServer in sqldmo.dll failed.
Does anybody know what is the source of this problem?Well I have found It!
You have to register atl.dll (for Win9x it have to be ANSI version) before sqldmo.dll - such simply, but Microsoft doesn't mention this nowhere...
Registering SQL Server...
Hi,
I am trying to connect remotely to a client's MSDE database with my SQL
Enterprise Manager so I can administer the database. I have established a
VPN to the client which I can ping and terminal serve into the server but I
cannot register the server with the SQL Enterprise Manager. I have even
tried turning off my Windows Firewall.
What connection property am I missing at either the client site or at my
office that is preventing me from connecting?
Thanks,
Chris
hi Chris,
Chris Marsh wrote:
> Hi,
> I am trying to connect remotely to a client's MSDE database with my
> SQL Enterprise Manager so I can administer the database. I have
> established a VPN to the client which I can ping and terminal serve
> into the server but I cannot register the server with the SQL
> Enterprise Manager. I have even tried turning off my Windows
> Firewall.
> What connection property am I missing at either the client site or at
> my office that is preventing me from connecting?
what kind of exception are you prompted with, at connection try?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I enter the IP into the Server line (leave Windows Auth or switch to SQL
Auth) and then I get the messagebox:
SQL Server registraion failed bause of hte connection falure displayed
below....
SQL Server does not exist or access denied.
ConnectionOpen (Connect())
Yes | No
Thanks!
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3cq5dpF6qk3gpU1@.individual.net...
> hi Chris,
> Chris Marsh wrote:
> what kind of exception are you prompted with, at connection try?
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||Did you make a portscan to see wheter the SQLServer is reachable and
listening on that adress ?
Perhaps the ports are blocked by the VPN Gateway, ping could be reachable
beacuse ICMP is treated in antoher way than ports. Its a own protocol:
http://www.iana.org/assignments/icmp-parameters
Try to use a portscanner.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Chris Marsh" <cmarsh@.synergy-intl.com> schrieb im Newsbeitrag
news:Or8DSspRFHA.3704@.TK2MSFTNGP12.phx.gbl...
>I enter the IP into the Server line (leave Windows Auth or switch to SQL
>Auth) and then I get the messagebox:
> SQL Server registraion failed bause of hte connection falure displayed
> below....
> SQL Server does not exist or access denied.
> ConnectionOpen (Connect())
> Yes | No
> Thanks!
>
> "Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
> news:3cq5dpF6qk3gpU1@.individual.net...
>
|||Chris Marsh wrote:
> I enter the IP into the Server line (leave Windows Auth or switch to
> SQL Auth) and then I get the messagebox:
> SQL Server registraion failed bause of hte connection falure displayed
> below....
> SQL Server does not exist or access denied.
> ConnectionOpen (Connect())
which is a general error reported by the MDAC stack..
please have a look at
http://support.microsoft.com/default...06&Product=sql
for a list of the more common causes of this kind of exception
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Chris, see an earlier post 'Getting to the bottom of ..." in the
subject. (just a few days ago).
If it's running on XP it's an XP login problem which can be cured on
the XP/Msde machine. There's a long explanation of how to cure this
(without re-installing).
It's not an MDAC problem. Come on MVP's you should know this stuff!
-Nick
On Thu, 21 Apr 2005 12:35:05 -0400, "Chris Marsh"
<cmarsh@.synergy-intl.com> wrote:
>Hi,
>I am trying to connect remotely to a client's MSDE database with my SQL
>Enterprise Manager so I can administer the database. I have established a
>VPN to the client which I can ping and terminal serve into the server but I
>cannot register the server with the SQL Enterprise Manager. I have even
>tried turning off my Windows Firewall.
>What connection property am I missing at either the client site or at my
>office that is preventing me from connecting?
>Thanks,
>Chris
>
I am trying to connect remotely to a client's MSDE database with my SQL
Enterprise Manager so I can administer the database. I have established a
VPN to the client which I can ping and terminal serve into the server but I
cannot register the server with the SQL Enterprise Manager. I have even
tried turning off my Windows Firewall.
What connection property am I missing at either the client site or at my
office that is preventing me from connecting?
Thanks,
Chris
hi Chris,
Chris Marsh wrote:
> Hi,
> I am trying to connect remotely to a client's MSDE database with my
> SQL Enterprise Manager so I can administer the database. I have
> established a VPN to the client which I can ping and terminal serve
> into the server but I cannot register the server with the SQL
> Enterprise Manager. I have even tried turning off my Windows
> Firewall.
> What connection property am I missing at either the client site or at
> my office that is preventing me from connecting?
what kind of exception are you prompted with, at connection try?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I enter the IP into the Server line (leave Windows Auth or switch to SQL
Auth) and then I get the messagebox:
SQL Server registraion failed bause of hte connection falure displayed
below....
SQL Server does not exist or access denied.
ConnectionOpen (Connect())
Yes | No
Thanks!
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3cq5dpF6qk3gpU1@.individual.net...
> hi Chris,
> Chris Marsh wrote:
> what kind of exception are you prompted with, at connection try?
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||Did you make a portscan to see wheter the SQLServer is reachable and
listening on that adress ?
Perhaps the ports are blocked by the VPN Gateway, ping could be reachable
beacuse ICMP is treated in antoher way than ports. Its a own protocol:
http://www.iana.org/assignments/icmp-parameters
Try to use a portscanner.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Chris Marsh" <cmarsh@.synergy-intl.com> schrieb im Newsbeitrag
news:Or8DSspRFHA.3704@.TK2MSFTNGP12.phx.gbl...
>I enter the IP into the Server line (leave Windows Auth or switch to SQL
>Auth) and then I get the messagebox:
> SQL Server registraion failed bause of hte connection falure displayed
> below....
> SQL Server does not exist or access denied.
> ConnectionOpen (Connect())
> Yes | No
> Thanks!
>
> "Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
> news:3cq5dpF6qk3gpU1@.individual.net...
>
|||Chris Marsh wrote:
> I enter the IP into the Server line (leave Windows Auth or switch to
> SQL Auth) and then I get the messagebox:
> SQL Server registraion failed bause of hte connection falure displayed
> below....
> SQL Server does not exist or access denied.
> ConnectionOpen (Connect())
which is a general error reported by the MDAC stack..
please have a look at
http://support.microsoft.com/default...06&Product=sql
for a list of the more common causes of this kind of exception
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Chris, see an earlier post 'Getting to the bottom of ..." in the
subject. (just a few days ago).
If it's running on XP it's an XP login problem which can be cured on
the XP/Msde machine. There's a long explanation of how to cure this
(without re-installing).
It's not an MDAC problem. Come on MVP's you should know this stuff!
-Nick
On Thu, 21 Apr 2005 12:35:05 -0400, "Chris Marsh"
<cmarsh@.synergy-intl.com> wrote:
>Hi,
>I am trying to connect remotely to a client's MSDE database with my SQL
>Enterprise Manager so I can administer the database. I have established a
>VPN to the client which I can ping and terminal serve into the server but I
>cannot register the server with the SQL Enterprise Manager. I have even
>tried turning off my Windows Firewall.
>What connection property am I missing at either the client site or at my
>office that is preventing me from connecting?
>Thanks,
>Chris
>
registering sql server problem
Trying to register a sql server in enterprise manager and
the server is on another domain which is trusted. The
server doesn't show up in the 'available servers' list
but I can register with ip address but *not* if I use
Client Network utility with exactly the correct netbios
name. Any ideas? Thanks.If the server isn't appearing in the list of available servers, chances are
that you need to add the IP address and server name to your hosts file. In
Win2k, the hosts file is located in c:\winnt\system32\driver\etc.
Open the hosts file in notepad, go to the end of the file, enter the IP
address, tab once and add the server name as follows:
xxx.xxx.xxx.xxx <tab> servername
John
"Dave Wilce" wrote:
> Trying to register a sql server in enterprise manager and
> the server is on another domain which is trusted. The
> server doesn't show up in the 'available servers' list
> but I can register with ip address but *not* if I use
> Client Network utility with exactly the correct netbios
> name. Any ideas? Thanks.
>|||We have tried 3 things :-
Using the Client Network utility does make the server
show up in the list but it will not register.
Using IP address it will allow registration but we hit
problems later (and we think it's because we use IP
address rather than NETBios name.
Using host file doesn't help...|||"Dave Wilce" wrote:
> We have tried 3 things :-
> Using the Client Network utility does make the server
> show up in the list but it will not register.
> Using IP address it will allow registration but we hit
> problems later (and we think it's because we use IP
> address rather than NETBios name.
> Using host file doesn't help...
Thinking out loud here...
Are you going through a firewall? Are you using the default port in the
Client Network utility (1433), and is the firewall open to that port? Can
you ping the other server using the server name? Can you have the your
network people make sure the server is listed in their DNS database correctly?
John
the server is on another domain which is trusted. The
server doesn't show up in the 'available servers' list
but I can register with ip address but *not* if I use
Client Network utility with exactly the correct netbios
name. Any ideas? Thanks.If the server isn't appearing in the list of available servers, chances are
that you need to add the IP address and server name to your hosts file. In
Win2k, the hosts file is located in c:\winnt\system32\driver\etc.
Open the hosts file in notepad, go to the end of the file, enter the IP
address, tab once and add the server name as follows:
xxx.xxx.xxx.xxx <tab> servername
John
"Dave Wilce" wrote:
> Trying to register a sql server in enterprise manager and
> the server is on another domain which is trusted. The
> server doesn't show up in the 'available servers' list
> but I can register with ip address but *not* if I use
> Client Network utility with exactly the correct netbios
> name. Any ideas? Thanks.
>|||We have tried 3 things :-
Using the Client Network utility does make the server
show up in the list but it will not register.
Using IP address it will allow registration but we hit
problems later (and we think it's because we use IP
address rather than NETBios name.
Using host file doesn't help...|||"Dave Wilce" wrote:
> We have tried 3 things :-
> Using the Client Network utility does make the server
> show up in the list but it will not register.
> Using IP address it will allow registration but we hit
> problems later (and we think it's because we use IP
> address rather than NETBios name.
> Using host file doesn't help...
Thinking out loud here...
Are you going through a firewall? Are you using the default port in the
Client Network utility (1433), and is the firewall open to that port? Can
you ping the other server using the server name? Can you have the your
network people make sure the server is listed in their DNS database correctly?
John
registering sql server problem
Trying to register a sql server in enterprise manager and
the server is on another domain which is trusted. The
server doesn't show up in the 'available servers' list
but I can register with ip address but *not* if I use
Client Network utility with exactly the correct netbios
name. Any ideas? Thanks.
If the server isn't appearing in the list of available servers, chances are
that you need to add the IP address and server name to your hosts file. In
Win2k, the hosts file is located in c:\winnt\system32\driver\etc.
Open the hosts file in notepad, go to the end of the file, enter the IP
address, tab once and add the server name as follows:
xxx.xxx.xxx.xxx <tab> servername
John
"Dave Wilce" wrote:
> Trying to register a sql server in enterprise manager and
> the server is on another domain which is trusted. The
> server doesn't show up in the 'available servers' list
> but I can register with ip address but *not* if I use
> Client Network utility with exactly the correct netbios
> name. Any ideas? Thanks.
>
|||We have tried 3 things :-
Using the Client Network utility does make the server
show up in the list but it will not register.
Using IP address it will allow registration but we hit
problems later (and we think it's because we use IP
address rather than NETBios name.
Using host file doesn't help...
|||"Dave Wilce" wrote:
> We have tried 3 things :-
> Using the Client Network utility does make the server
> show up in the list but it will not register.
> Using IP address it will allow registration but we hit
> problems later (and we think it's because we use IP
> address rather than NETBios name.
> Using host file doesn't help...
Thinking out loud here...
Are you going through a firewall? Are you using the default port in the
Client Network utility (1433), and is the firewall open to that port? Can
you ping the other server using the server name? Can you have the your
network people make sure the server is listed in their DNS database correctly?
John
the server is on another domain which is trusted. The
server doesn't show up in the 'available servers' list
but I can register with ip address but *not* if I use
Client Network utility with exactly the correct netbios
name. Any ideas? Thanks.
If the server isn't appearing in the list of available servers, chances are
that you need to add the IP address and server name to your hosts file. In
Win2k, the hosts file is located in c:\winnt\system32\driver\etc.
Open the hosts file in notepad, go to the end of the file, enter the IP
address, tab once and add the server name as follows:
xxx.xxx.xxx.xxx <tab> servername
John
"Dave Wilce" wrote:
> Trying to register a sql server in enterprise manager and
> the server is on another domain which is trusted. The
> server doesn't show up in the 'available servers' list
> but I can register with ip address but *not* if I use
> Client Network utility with exactly the correct netbios
> name. Any ideas? Thanks.
>
|||We have tried 3 things :-
Using the Client Network utility does make the server
show up in the list but it will not register.
Using IP address it will allow registration but we hit
problems later (and we think it's because we use IP
address rather than NETBios name.
Using host file doesn't help...
|||"Dave Wilce" wrote:
> We have tried 3 things :-
> Using the Client Network utility does make the server
> show up in the list but it will not register.
> Using IP address it will allow registration but we hit
> problems later (and we think it's because we use IP
> address rather than NETBios name.
> Using host file doesn't help...
Thinking out loud here...
Are you going through a firewall? Are you using the default port in the
Client Network utility (1433), and is the firewall open to that port? Can
you ping the other server using the server name? Can you have the your
network people make sure the server is listed in their DNS database correctly?
John
registering sql server problem
Trying to register a sql server in enterprise manager and
the server is on another domain which is trusted. The
server doesn't show up in the 'available servers' list
but I can register with ip address but *not* if I use
Client Network utility with exactly the correct netbios
name. Any ideas? Thanks.If the server isn't appearing in the list of available servers, chances are
that you need to add the IP address and server name to your hosts file. In
Win2k, the hosts file is located in c:\winnt\system32\driver\etc.
Open the hosts file in notepad, go to the end of the file, enter the IP
address, tab once and add the server name as follows:
xxx.xxx.xxx.xxx <tab> servername
John
"Dave Wilce" wrote:
> Trying to register a sql server in enterprise manager and
> the server is on another domain which is trusted. The
> server doesn't show up in the 'available servers' list
> but I can register with ip address but *not* if I use
> Client Network utility with exactly the correct netbios
> name. Any ideas? Thanks.
>|||We have tried 3 things :-
Using the Client Network utility does make the server
show up in the list but it will not register.
Using IP address it will allow registration but we hit
problems later (and we think it's because we use IP
address rather than NETBios name.
Using host file doesn't help...|||"Dave Wilce" wrote:
> We have tried 3 things :-
> Using the Client Network utility does make the server
> show up in the list but it will not register.
> Using IP address it will allow registration but we hit
> problems later (and we think it's because we use IP
> address rather than NETBios name.
> Using host file doesn't help...
Thinking out loud here...
Are you going through a firewall? Are you using the default port in the
Client Network utility (1433), and is the firewall open to that port? Can
you ping the other server using the server name? Can you have the your
network people make sure the server is listed in their DNS database correctl
y?
John
the server is on another domain which is trusted. The
server doesn't show up in the 'available servers' list
but I can register with ip address but *not* if I use
Client Network utility with exactly the correct netbios
name. Any ideas? Thanks.If the server isn't appearing in the list of available servers, chances are
that you need to add the IP address and server name to your hosts file. In
Win2k, the hosts file is located in c:\winnt\system32\driver\etc.
Open the hosts file in notepad, go to the end of the file, enter the IP
address, tab once and add the server name as follows:
xxx.xxx.xxx.xxx <tab> servername
John
"Dave Wilce" wrote:
> Trying to register a sql server in enterprise manager and
> the server is on another domain which is trusted. The
> server doesn't show up in the 'available servers' list
> but I can register with ip address but *not* if I use
> Client Network utility with exactly the correct netbios
> name. Any ideas? Thanks.
>|||We have tried 3 things :-
Using the Client Network utility does make the server
show up in the list but it will not register.
Using IP address it will allow registration but we hit
problems later (and we think it's because we use IP
address rather than NETBios name.
Using host file doesn't help...|||"Dave Wilce" wrote:
> We have tried 3 things :-
> Using the Client Network utility does make the server
> show up in the list but it will not register.
> Using IP address it will allow registration but we hit
> problems later (and we think it's because we use IP
> address rather than NETBios name.
> Using host file doesn't help...
Thinking out loud here...
Are you going through a firewall? Are you using the default port in the
Client Network utility (1433), and is the firewall open to that port? Can
you ping the other server using the server name? Can you have the your
network people make sure the server is listed in their DNS database correctl
y?
John
registering SQL Server not in domain
Hi all,
We have standardized on Hyperion as our reporting tool. So far I have
only set up a couple of Access databases as data sources for it. Now
there is a request to report off our eOn (telephony management) SQL
Server database using Hyperion. The eOn SQL Server box is in a
workgroup that is not part of the rest of our domain. (We only have
one domain because we don't have a "forest", whatever that means.) It
is behind a router owned by eOn along with a PBX and some other stuff.
Setting up a data source for Hyperion requires creating a special data
source file called an .oce on the box where the Hyperion fat client
(required for most administrative tasks) resides, and also setting up a
different special data source file called a .das on the server where
the Hyperion services run. (The analysts and end-users do not have the
fat client, their access is web-based.)
I have to register the eOn SQL Server by using the IP address and SQL
Server authentication. (I was told that I can't use Windows
authentication because it is not in the domain.) From the box on
which the Hyperion fat client resides, I cannot register the eOn SQL
Server. The error message is "timeout expired". Tracerting indicates
there are no intermediate hops when attempting to connect from this
VLAN. From my desktop, which is on a different VLAN, I can connect to
and register it. This trip includes one hop at our 6509. From one of
my servers which is on the same VLAN as the fat-client box, I am able
to connect and register. On the fat-client box I tried deleting and
re-registering another SQL Server and there was no problem.
The IP address I have to use to connect to the eOn SQL Server is *NOT*
the actual IP address of the box it resides on, but rather the eOn
router, which translates it to the address of the server. We have no
control over this, eOn creates this setup. I'm not sure how it knows
which of the devices behind it a given message is for.
Ideas?Hi
Which version of SQL Server is on the telephony management system? At a
guess it is MSDE with no network protocols installed! Use svrnetcn.exe to
enable the network protcols. If they are running you may want to use the
SQLRecon tool to see what servers are available on your network
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=26
John
"Ellen K" wrote:
> Hi all,
> We have standardized on Hyperion as our reporting tool. So far I have
> only set up a couple of Access databases as data sources for it. Now
> there is a request to report off our eOn (telephony management) SQL
> Server database using Hyperion. The eOn SQL Server box is in a
> workgroup that is not part of the rest of our domain. (We only have
> one domain because we don't have a "forest", whatever that means.) It
> is behind a router owned by eOn along with a PBX and some other stuff.
>
> Setting up a data source for Hyperion requires creating a special data
> source file called an .oce on the box where the Hyperion fat client
> (required for most administrative tasks) resides, and also setting up a
> different special data source file called a .das on the server where
> the Hyperion services run. (The analysts and end-users do not have the
> fat client, their access is web-based.)
> I have to register the eOn SQL Server by using the IP address and SQL
> Server authentication. (I was told that I can't use Windows
> authentication because it is not in the domain.) From the box on
> which the Hyperion fat client resides, I cannot register the eOn SQL
> Server. The error message is "timeout expired". Tracerting indicates
> there are no intermediate hops when attempting to connect from this
> VLAN. From my desktop, which is on a different VLAN, I can connect to
> and register it. This trip includes one hop at our 6509. From one of
> my servers which is on the same VLAN as the fat-client box, I am able
> to connect and register. On the fat-client box I tried deleting and
> re-registering another SQL Server and there was no problem.
> The IP address I have to use to connect to the eOn SQL Server is *NOT*
> the actual IP address of the box it resides on, but rather the eOn
> router, which translates it to the address of the server. We have no
> control over this, eOn creates this setup. I'm not sure how it knows
> which of the devices behind it a given message is for.
> Ideas?
>|||Hi John,
Thanks for your response. I will check the version and also check
which network protocols are enabled on it, assuming I can get to the
box. But if the problem were no network protocols installed on the eOn
box then how would the other two boxes that CAN register it be able to
do so?
Thanks,
Ellen|||Hi
I hadn't realised that it could be registered elsewhere! This indicates that
there are network protocols, but they still may not be the same as the ones
on the client that can't register!! You may still want to try running
SQLRecon and also try to telnet into the port being used.
John
"Ellen K" wrote:
> Hi John,
> Thanks for your response. I will check the version and also check
> which network protocols are enabled on it, assuming I can get to the
> box. But if the problem were no network protocols installed on the eOn
> box then how would the other two boxes that CAN register it be able to
> do so?
> Thanks,
> Ellen
>|||Hi John,
Yes, I mentioned in my original post that I could register it from both
my desktop and from one of "my" servers.
The network protocols are the same on the eOn box as on "my" servers:
named pipes and tcp. Since the fat client can connect to "my" servers,
I think it's safe to say this isn't the problem.
I have now succeeded in creating an ODBC connection, which would not
have been my first choice, but right now if it works I'm happy.
Thanks,
Ellen
We have standardized on Hyperion as our reporting tool. So far I have
only set up a couple of Access databases as data sources for it. Now
there is a request to report off our eOn (telephony management) SQL
Server database using Hyperion. The eOn SQL Server box is in a
workgroup that is not part of the rest of our domain. (We only have
one domain because we don't have a "forest", whatever that means.) It
is behind a router owned by eOn along with a PBX and some other stuff.
Setting up a data source for Hyperion requires creating a special data
source file called an .oce on the box where the Hyperion fat client
(required for most administrative tasks) resides, and also setting up a
different special data source file called a .das on the server where
the Hyperion services run. (The analysts and end-users do not have the
fat client, their access is web-based.)
I have to register the eOn SQL Server by using the IP address and SQL
Server authentication. (I was told that I can't use Windows
authentication because it is not in the domain.) From the box on
which the Hyperion fat client resides, I cannot register the eOn SQL
Server. The error message is "timeout expired". Tracerting indicates
there are no intermediate hops when attempting to connect from this
VLAN. From my desktop, which is on a different VLAN, I can connect to
and register it. This trip includes one hop at our 6509. From one of
my servers which is on the same VLAN as the fat-client box, I am able
to connect and register. On the fat-client box I tried deleting and
re-registering another SQL Server and there was no problem.
The IP address I have to use to connect to the eOn SQL Server is *NOT*
the actual IP address of the box it resides on, but rather the eOn
router, which translates it to the address of the server. We have no
control over this, eOn creates this setup. I'm not sure how it knows
which of the devices behind it a given message is for.
Ideas?Hi
Which version of SQL Server is on the telephony management system? At a
guess it is MSDE with no network protocols installed! Use svrnetcn.exe to
enable the network protcols. If they are running you may want to use the
SQLRecon tool to see what servers are available on your network
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=26
John
"Ellen K" wrote:
> Hi all,
> We have standardized on Hyperion as our reporting tool. So far I have
> only set up a couple of Access databases as data sources for it. Now
> there is a request to report off our eOn (telephony management) SQL
> Server database using Hyperion. The eOn SQL Server box is in a
> workgroup that is not part of the rest of our domain. (We only have
> one domain because we don't have a "forest", whatever that means.) It
> is behind a router owned by eOn along with a PBX and some other stuff.
>
> Setting up a data source for Hyperion requires creating a special data
> source file called an .oce on the box where the Hyperion fat client
> (required for most administrative tasks) resides, and also setting up a
> different special data source file called a .das on the server where
> the Hyperion services run. (The analysts and end-users do not have the
> fat client, their access is web-based.)
> I have to register the eOn SQL Server by using the IP address and SQL
> Server authentication. (I was told that I can't use Windows
> authentication because it is not in the domain.) From the box on
> which the Hyperion fat client resides, I cannot register the eOn SQL
> Server. The error message is "timeout expired". Tracerting indicates
> there are no intermediate hops when attempting to connect from this
> VLAN. From my desktop, which is on a different VLAN, I can connect to
> and register it. This trip includes one hop at our 6509. From one of
> my servers which is on the same VLAN as the fat-client box, I am able
> to connect and register. On the fat-client box I tried deleting and
> re-registering another SQL Server and there was no problem.
> The IP address I have to use to connect to the eOn SQL Server is *NOT*
> the actual IP address of the box it resides on, but rather the eOn
> router, which translates it to the address of the server. We have no
> control over this, eOn creates this setup. I'm not sure how it knows
> which of the devices behind it a given message is for.
> Ideas?
>|||Hi John,
Thanks for your response. I will check the version and also check
which network protocols are enabled on it, assuming I can get to the
box. But if the problem were no network protocols installed on the eOn
box then how would the other two boxes that CAN register it be able to
do so?
Thanks,
Ellen|||Hi
I hadn't realised that it could be registered elsewhere! This indicates that
there are network protocols, but they still may not be the same as the ones
on the client that can't register!! You may still want to try running
SQLRecon and also try to telnet into the port being used.
John
"Ellen K" wrote:
> Hi John,
> Thanks for your response. I will check the version and also check
> which network protocols are enabled on it, assuming I can get to the
> box. But if the problem were no network protocols installed on the eOn
> box then how would the other two boxes that CAN register it be able to
> do so?
> Thanks,
> Ellen
>|||Hi John,
Yes, I mentioned in my original post that I could register it from both
my desktop and from one of "my" servers.
The network protocols are the same on the eOn box as on "my" servers:
named pipes and tcp. Since the fat client can connect to "my" servers,
I think it's safe to say this isn't the problem.
I have now succeeded in creating an ODBC connection, which would not
have been my first choice, but right now if it works I'm happy.
Thanks,
Ellen
registering SQL Server not in domain
Hi all,
We have standardized on Hyperion as our reporting tool. So far I have
only set up a couple of Access databases as data sources for it. Now
there is a request to report off our eOn (telephony management) SQL
Server database using Hyperion. The eOn SQL Server box is in a
workgroup that is not part of the rest of our domain. (We only have
one domain because we don't have a "forest", whatever that means.) It
is behind a router owned by eOn along with a PBX and some other stuff.
Setting up a data source for Hyperion requires creating a special data
source file called an .oce on the box where the Hyperion fat client
(required for most administrative tasks) resides, and also setting up a
different special data source file called a .das on the server where
the Hyperion services run. (The analysts and end-users do not have the
fat client, their access is web-based.)
I have to register the eOn SQL Server by using the IP address and SQL
Server authentication. (I was told that I can't use Windows
authentication because it is not in the domain.) From the box on
which the Hyperion fat client resides, I cannot register the eOn SQL
Server. The error message is "timeout expired". Tracerting indicates
there are no intermediate hops when attempting to connect from this
VLAN. From my desktop, which is on a different VLAN, I can connect to
and register it. This trip includes one hop at our 6509. From one of
my servers which is on the same VLAN as the fat-client box, I am able
to connect and register. On the fat-client box I tried deleting and
re-registering another SQL Server and there was no problem.
The IP address I have to use to connect to the eOn SQL Server is *NOT*
the actual IP address of the box it resides on, but rather the eOn
router, which translates it to the address of the server. We have no
control over this, eOn creates this setup. I'm not sure how it knows
which of the devices behind it a given message is for.
Ideas?
Hi
Which version of SQL Server is on the telephony management system? At a
guess it is MSDE with no network protocols installed! Use svrnetcn.exe to
enable the network protcols. If they are running you may want to use the
SQLRecon tool to see what servers are available on your network
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=26
John
"Ellen K" wrote:
> Hi all,
> We have standardized on Hyperion as our reporting tool. So far I have
> only set up a couple of Access databases as data sources for it. Now
> there is a request to report off our eOn (telephony management) SQL
> Server database using Hyperion. The eOn SQL Server box is in a
> workgroup that is not part of the rest of our domain. (We only have
> one domain because we don't have a "forest", whatever that means.) It
> is behind a router owned by eOn along with a PBX and some other stuff.
>
> Setting up a data source for Hyperion requires creating a special data
> source file called an .oce on the box where the Hyperion fat client
> (required for most administrative tasks) resides, and also setting up a
> different special data source file called a .das on the server where
> the Hyperion services run. (The analysts and end-users do not have the
> fat client, their access is web-based.)
> I have to register the eOn SQL Server by using the IP address and SQL
> Server authentication. (I was told that I can't use Windows
> authentication because it is not in the domain.) From the box on
> which the Hyperion fat client resides, I cannot register the eOn SQL
> Server. The error message is "timeout expired". Tracerting indicates
> there are no intermediate hops when attempting to connect from this
> VLAN. From my desktop, which is on a different VLAN, I can connect to
> and register it. This trip includes one hop at our 6509. From one of
> my servers which is on the same VLAN as the fat-client box, I am able
> to connect and register. On the fat-client box I tried deleting and
> re-registering another SQL Server and there was no problem.
> The IP address I have to use to connect to the eOn SQL Server is *NOT*
> the actual IP address of the box it resides on, but rather the eOn
> router, which translates it to the address of the server. We have no
> control over this, eOn creates this setup. I'm not sure how it knows
> which of the devices behind it a given message is for.
> Ideas?
>
|||Hi John,
Thanks for your response. I will check the version and also check
which network protocols are enabled on it, assuming I can get to the
box. But if the problem were no network protocols installed on the eOn
box then how would the other two boxes that CAN register it be able to
do so?
Thanks,
Ellen
|||Hi
I hadn't realised that it could be registered elsewhere! This indicates that
there are network protocols, but they still may not be the same as the ones
on the client that can't register!! You may still want to try running
SQLRecon and also try to telnet into the port being used.
John
"Ellen K" wrote:
> Hi John,
> Thanks for your response. I will check the version and also check
> which network protocols are enabled on it, assuming I can get to the
> box. But if the problem were no network protocols installed on the eOn
> box then how would the other two boxes that CAN register it be able to
> do so?
> Thanks,
> Ellen
>
|||Hi John,
Yes, I mentioned in my original post that I could register it from both
my desktop and from one of "my" servers.
The network protocols are the same on the eOn box as on "my" servers:
named pipes and tcp. Since the fat client can connect to "my" servers,
I think it's safe to say this isn't the problem.
I have now succeeded in creating an ODBC connection, which would not
have been my first choice, but right now if it works I'm happy.
Thanks,
Ellen
We have standardized on Hyperion as our reporting tool. So far I have
only set up a couple of Access databases as data sources for it. Now
there is a request to report off our eOn (telephony management) SQL
Server database using Hyperion. The eOn SQL Server box is in a
workgroup that is not part of the rest of our domain. (We only have
one domain because we don't have a "forest", whatever that means.) It
is behind a router owned by eOn along with a PBX and some other stuff.
Setting up a data source for Hyperion requires creating a special data
source file called an .oce on the box where the Hyperion fat client
(required for most administrative tasks) resides, and also setting up a
different special data source file called a .das on the server where
the Hyperion services run. (The analysts and end-users do not have the
fat client, their access is web-based.)
I have to register the eOn SQL Server by using the IP address and SQL
Server authentication. (I was told that I can't use Windows
authentication because it is not in the domain.) From the box on
which the Hyperion fat client resides, I cannot register the eOn SQL
Server. The error message is "timeout expired". Tracerting indicates
there are no intermediate hops when attempting to connect from this
VLAN. From my desktop, which is on a different VLAN, I can connect to
and register it. This trip includes one hop at our 6509. From one of
my servers which is on the same VLAN as the fat-client box, I am able
to connect and register. On the fat-client box I tried deleting and
re-registering another SQL Server and there was no problem.
The IP address I have to use to connect to the eOn SQL Server is *NOT*
the actual IP address of the box it resides on, but rather the eOn
router, which translates it to the address of the server. We have no
control over this, eOn creates this setup. I'm not sure how it knows
which of the devices behind it a given message is for.
Ideas?
Hi
Which version of SQL Server is on the telephony management system? At a
guess it is MSDE with no network protocols installed! Use svrnetcn.exe to
enable the network protcols. If they are running you may want to use the
SQLRecon tool to see what servers are available on your network
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=26
John
"Ellen K" wrote:
> Hi all,
> We have standardized on Hyperion as our reporting tool. So far I have
> only set up a couple of Access databases as data sources for it. Now
> there is a request to report off our eOn (telephony management) SQL
> Server database using Hyperion. The eOn SQL Server box is in a
> workgroup that is not part of the rest of our domain. (We only have
> one domain because we don't have a "forest", whatever that means.) It
> is behind a router owned by eOn along with a PBX and some other stuff.
>
> Setting up a data source for Hyperion requires creating a special data
> source file called an .oce on the box where the Hyperion fat client
> (required for most administrative tasks) resides, and also setting up a
> different special data source file called a .das on the server where
> the Hyperion services run. (The analysts and end-users do not have the
> fat client, their access is web-based.)
> I have to register the eOn SQL Server by using the IP address and SQL
> Server authentication. (I was told that I can't use Windows
> authentication because it is not in the domain.) From the box on
> which the Hyperion fat client resides, I cannot register the eOn SQL
> Server. The error message is "timeout expired". Tracerting indicates
> there are no intermediate hops when attempting to connect from this
> VLAN. From my desktop, which is on a different VLAN, I can connect to
> and register it. This trip includes one hop at our 6509. From one of
> my servers which is on the same VLAN as the fat-client box, I am able
> to connect and register. On the fat-client box I tried deleting and
> re-registering another SQL Server and there was no problem.
> The IP address I have to use to connect to the eOn SQL Server is *NOT*
> the actual IP address of the box it resides on, but rather the eOn
> router, which translates it to the address of the server. We have no
> control over this, eOn creates this setup. I'm not sure how it knows
> which of the devices behind it a given message is for.
> Ideas?
>
|||Hi John,
Thanks for your response. I will check the version and also check
which network protocols are enabled on it, assuming I can get to the
box. But if the problem were no network protocols installed on the eOn
box then how would the other two boxes that CAN register it be able to
do so?
Thanks,
Ellen
|||Hi
I hadn't realised that it could be registered elsewhere! This indicates that
there are network protocols, but they still may not be the same as the ones
on the client that can't register!! You may still want to try running
SQLRecon and also try to telnet into the port being used.
John
"Ellen K" wrote:
> Hi John,
> Thanks for your response. I will check the version and also check
> which network protocols are enabled on it, assuming I can get to the
> box. But if the problem were no network protocols installed on the eOn
> box then how would the other two boxes that CAN register it be able to
> do so?
> Thanks,
> Ellen
>
|||Hi John,
Yes, I mentioned in my original post that I could register it from both
my desktop and from one of "my" servers.
The network protocols are the same on the eOn box as on "my" servers:
named pipes and tcp. Since the fat client can connect to "my" servers,
I think it's safe to say this isn't the problem.
I have now succeeded in creating an ODBC connection, which would not
have been my first choice, but right now if it works I'm happy.
Thanks,
Ellen
registering SQL Server not in domain
Hi all,
We have standardized on Hyperion as our reporting tool. So far I have
only set up a couple of Access databases as data sources for it. Now
there is a request to report off our eOn (telephony management) SQL
Server database using Hyperion. The eOn SQL Server box is in a
workgroup that is not part of the rest of our domain. (We only have
one domain because we don't have a "forest", whatever that means.) It
is behind a router owned by eOn along with a PBX and some other stuff.
Setting up a data source for Hyperion requires creating a special data
source file called an .oce on the box where the Hyperion fat client
(required for most administrative tasks) resides, and also setting up a
different special data source file called a .das on the server where
the Hyperion services run. (The analysts and end-users do not have the
fat client, their access is web-based.)
I have to register the eOn SQL Server by using the IP address and SQL
Server authentication. (I was told that I can't use Windows
authentication because it is not in the domain.) From the box on
which the Hyperion fat client resides, I cannot register the eOn SQL
Server. The error message is "timeout expired". Tracerting indicates
there are no intermediate hops when attempting to connect from this
VLAN. From my desktop, which is on a different VLAN, I can connect to
and register it. This trip includes one hop at our 6509. From one of
my servers which is on the same VLAN as the fat-client box, I am able
to connect and register. On the fat-client box I tried deleting and
re-registering another SQL Server and there was no problem.
The IP address I have to use to connect to the eOn SQL Server is *NOT*
the actual IP address of the box it resides on, but rather the eOn
router, which translates it to the address of the server. We have no
control over this, eOn creates this setup. I'm not sure how it knows
which of the devices behind it a given message is for.
Ideas?From your description I pulled this sentence.
"From my desktop, which is on a different VLAN, I can connect to
and register it."
This indicates that you have a valid SQL login, password, protocol, and ip
address. Analyse you desktop and figure out what these are. In particular
the protocol.
The protocol, Network routing, and possibly the firewall will be the issue.
The two most common protocols for SQL is Named Pipes and TCP.
If you can get to the SQL Server from your desktop, look at the SQL Server
Log for what protocols are supported.
From the Hyperion services server use this information to configure an ODBC
DSN and test the connection. You may want to install the SQL client only
option on your Hyperion server to give you more control over the connection
setup (AKA a SQL Alias)
"Ellen K" <ekaye2002@.yahoo.com> wrote in message
news:1129150328.960539.76600@.g47g2000cwa.googlegro ups.com...
> Hi all,
> We have standardized on Hyperion as our reporting tool. So far I have
> only set up a couple of Access databases as data sources for it. Now
> there is a request to report off our eOn (telephony management) SQL
> Server database using Hyperion. The eOn SQL Server box is in a
> workgroup that is not part of the rest of our domain. (We only have
> one domain because we don't have a "forest", whatever that means.) It
> is behind a router owned by eOn along with a PBX and some other stuff.
>
> Setting up a data source for Hyperion requires creating a special data
> source file called an .oce on the box where the Hyperion fat client
> (required for most administrative tasks) resides, and also setting up a
> different special data source file called a .das on the server where
> the Hyperion services run. (The analysts and end-users do not have the
> fat client, their access is web-based.)
> I have to register the eOn SQL Server by using the IP address and SQL
> Server authentication. (I was told that I can't use Windows
> authentication because it is not in the domain.) From the box on
> which the Hyperion fat client resides, I cannot register the eOn SQL
> Server. The error message is "timeout expired". Tracerting indicates
> there are no intermediate hops when attempting to connect from this
> VLAN. From my desktop, which is on a different VLAN, I can connect to
> and register it. This trip includes one hop at our 6509. From one of
> my servers which is on the same VLAN as the fat-client box, I am able
> to connect and register. On the fat-client box I tried deleting and
> re-registering another SQL Server and there was no problem.
> The IP address I have to use to connect to the eOn SQL Server is *NOT*
> the actual IP address of the box it resides on, but rather the eOn
> router, which translates it to the address of the server. We have no
> control over this, eOn creates this setup. I'm not sure how it knows
> which of the devices behind it a given message is for.
> Ideas?|||Hi,
Thanks very much for your response. :)
I think network routing has been eliminated as the cause because I was
able to register the eOn server from one of "my" SQL Servers which is
on the same VLAN as the fat client box that can't register it. And it
can't be a firewall issue because the eOn box is behind our firewall,
it's just not in our domain. I did not think to check the protocols,
that is definitely worth a try. It did occur to me to set up the eOn
database as an ODBC connection for Hyperion instead of using the SQL
Server option, which if it works would solve the current problem.
However, I am also concerned because I am meanwhile building a data
warehouse in SQL Server for which Hyperion is supposed to be the
reporting tool and I would hate to have make a choice that I know up
front is going to diminish performance.
Thanks again, I will report back.
Ellen|||Hi again,
Well, it's not the network protocols.
I did notice that the eOn box is running the original version of SQL
Server, i.e. no service packs have been applied. I will take care of
that, but would be surprised if it's causing the problem.
Meanwhile I did succeed in setting up an ODBC connection, so I've
solved my immediate problem.
Thanks again,
Ellen
registering SQL Server not in domain
Hi all,
We have standardized on Hyperion as our reporting tool. So far I have
only set up a couple of Access databases as data sources for it. Now
there is a request to report off our eOn (telephony management) SQL
Server database using Hyperion. The eOn SQL Server box is in a
workgroup that is not part of the rest of our domain. (We only have
one domain because we don't have a "forest", whatever that means.) It
is behind a router owned by eOn along with a PBX and some other stuff.
Setting up a data source for Hyperion requires creating a special data
source file called an .oce on the box where the Hyperion fat client
(required for most administrative tasks) resides, and also setting up a
different special data source file called a .das on the server where
the Hyperion services run. (The analysts and end-users do not have the
fat client, their access is web-based.)
I have to register the eOn SQL Server by using the IP address and SQL
Server authentication. (I was told that I can't use Windows
authentication because it is not in the domain.) From the box on
which the Hyperion fat client resides, I cannot register the eOn SQL
Server. The error message is "timeout expired". Tracerting indicates
there are no intermediate hops when attempting to connect from this
VLAN. From my desktop, which is on a different VLAN, I can connect to
and register it. This trip includes one hop at our 6509. From one of
my servers which is on the same VLAN as the fat-client box, I am able
to connect and register. On the fat-client box I tried deleting and
re-registering another SQL Server and there was no problem.
The IP address I have to use to connect to the eOn SQL Server is *NOT*
the actual IP address of the box it resides on, but rather the eOn
router, which translates it to the address of the server. We have no
control over this, eOn creates this setup. I'm not sure how it knows
which of the devices behind it a given message is for.
Ideas?Hi
Which version of SQL Server is on the telephony management system? At a
guess it is MSDE with no network protocols installed! Use svrnetcn.exe to
enable the network protcols. If they are running you may want to use the
SQLRecon tool to see what servers are available on your network
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=26
John
"Ellen K" wrote:
> Hi all,
> We have standardized on Hyperion as our reporting tool. So far I have
> only set up a couple of Access databases as data sources for it. Now
> there is a request to report off our eOn (telephony management) SQL
> Server database using Hyperion. The eOn SQL Server box is in a
> workgroup that is not part of the rest of our domain. (We only have
> one domain because we don't have a "forest", whatever that means.) It
> is behind a router owned by eOn along with a PBX and some other stuff.
>
> Setting up a data source for Hyperion requires creating a special data
> source file called an .oce on the box where the Hyperion fat client
> (required for most administrative tasks) resides, and also setting up a
> different special data source file called a .das on the server where
> the Hyperion services run. (The analysts and end-users do not have the
> fat client, their access is web-based.)
> I have to register the eOn SQL Server by using the IP address and SQL
> Server authentication. (I was told that I can't use Windows
> authentication because it is not in the domain.) From the box on
> which the Hyperion fat client resides, I cannot register the eOn SQL
> Server. The error message is "timeout expired". Tracerting indicates
> there are no intermediate hops when attempting to connect from this
> VLAN. From my desktop, which is on a different VLAN, I can connect to
> and register it. This trip includes one hop at our 6509. From one of
> my servers which is on the same VLAN as the fat-client box, I am able
> to connect and register. On the fat-client box I tried deleting and
> re-registering another SQL Server and there was no problem.
> The IP address I have to use to connect to the eOn SQL Server is *NOT*
> the actual IP address of the box it resides on, but rather the eOn
> router, which translates it to the address of the server. We have no
> control over this, eOn creates this setup. I'm not sure how it knows
> which of the devices behind it a given message is for.
> Ideas?
>|||Hi John,
Thanks for your response. I will check the version and also check
which network protocols are enabled on it, assuming I can get to the
box. But if the problem were no network protocols installed on the eOn
box then how would the other two boxes that CAN register it be able to
do so?
Thanks,
Ellen|||Hi
I hadn't realised that it could be registered elsewhere! This indicates that
there are network protocols, but they still may not be the same as the ones
on the client that can't register!! You may still want to try running
SQLRecon and also try to telnet into the port being used.
John
"Ellen K" wrote:
> Hi John,
> Thanks for your response. I will check the version and also check
> which network protocols are enabled on it, assuming I can get to the
> box. But if the problem were no network protocols installed on the eOn
> box then how would the other two boxes that CAN register it be able to
> do so?
> Thanks,
> Ellen
>|||Hi John,
Yes, I mentioned in my original post that I could register it from both
my desktop and from one of "my" servers.
The network protocols are the same on the eOn box as on "my" servers:
named pipes and tcp. Since the fat client can connect to "my" servers,
I think it's safe to say this isn't the problem.
I have now succeeded in creating an ODBC connection, which would not
have been my first choice, but right now if it works I'm happy.
Thanks,
Ellen
We have standardized on Hyperion as our reporting tool. So far I have
only set up a couple of Access databases as data sources for it. Now
there is a request to report off our eOn (telephony management) SQL
Server database using Hyperion. The eOn SQL Server box is in a
workgroup that is not part of the rest of our domain. (We only have
one domain because we don't have a "forest", whatever that means.) It
is behind a router owned by eOn along with a PBX and some other stuff.
Setting up a data source for Hyperion requires creating a special data
source file called an .oce on the box where the Hyperion fat client
(required for most administrative tasks) resides, and also setting up a
different special data source file called a .das on the server where
the Hyperion services run. (The analysts and end-users do not have the
fat client, their access is web-based.)
I have to register the eOn SQL Server by using the IP address and SQL
Server authentication. (I was told that I can't use Windows
authentication because it is not in the domain.) From the box on
which the Hyperion fat client resides, I cannot register the eOn SQL
Server. The error message is "timeout expired". Tracerting indicates
there are no intermediate hops when attempting to connect from this
VLAN. From my desktop, which is on a different VLAN, I can connect to
and register it. This trip includes one hop at our 6509. From one of
my servers which is on the same VLAN as the fat-client box, I am able
to connect and register. On the fat-client box I tried deleting and
re-registering another SQL Server and there was no problem.
The IP address I have to use to connect to the eOn SQL Server is *NOT*
the actual IP address of the box it resides on, but rather the eOn
router, which translates it to the address of the server. We have no
control over this, eOn creates this setup. I'm not sure how it knows
which of the devices behind it a given message is for.
Ideas?Hi
Which version of SQL Server is on the telephony management system? At a
guess it is MSDE with no network protocols installed! Use svrnetcn.exe to
enable the network protcols. If they are running you may want to use the
SQLRecon tool to see what servers are available on your network
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=26
John
"Ellen K" wrote:
> Hi all,
> We have standardized on Hyperion as our reporting tool. So far I have
> only set up a couple of Access databases as data sources for it. Now
> there is a request to report off our eOn (telephony management) SQL
> Server database using Hyperion. The eOn SQL Server box is in a
> workgroup that is not part of the rest of our domain. (We only have
> one domain because we don't have a "forest", whatever that means.) It
> is behind a router owned by eOn along with a PBX and some other stuff.
>
> Setting up a data source for Hyperion requires creating a special data
> source file called an .oce on the box where the Hyperion fat client
> (required for most administrative tasks) resides, and also setting up a
> different special data source file called a .das on the server where
> the Hyperion services run. (The analysts and end-users do not have the
> fat client, their access is web-based.)
> I have to register the eOn SQL Server by using the IP address and SQL
> Server authentication. (I was told that I can't use Windows
> authentication because it is not in the domain.) From the box on
> which the Hyperion fat client resides, I cannot register the eOn SQL
> Server. The error message is "timeout expired". Tracerting indicates
> there are no intermediate hops when attempting to connect from this
> VLAN. From my desktop, which is on a different VLAN, I can connect to
> and register it. This trip includes one hop at our 6509. From one of
> my servers which is on the same VLAN as the fat-client box, I am able
> to connect and register. On the fat-client box I tried deleting and
> re-registering another SQL Server and there was no problem.
> The IP address I have to use to connect to the eOn SQL Server is *NOT*
> the actual IP address of the box it resides on, but rather the eOn
> router, which translates it to the address of the server. We have no
> control over this, eOn creates this setup. I'm not sure how it knows
> which of the devices behind it a given message is for.
> Ideas?
>|||Hi John,
Thanks for your response. I will check the version and also check
which network protocols are enabled on it, assuming I can get to the
box. But if the problem were no network protocols installed on the eOn
box then how would the other two boxes that CAN register it be able to
do so?
Thanks,
Ellen|||Hi
I hadn't realised that it could be registered elsewhere! This indicates that
there are network protocols, but they still may not be the same as the ones
on the client that can't register!! You may still want to try running
SQLRecon and also try to telnet into the port being used.
John
"Ellen K" wrote:
> Hi John,
> Thanks for your response. I will check the version and also check
> which network protocols are enabled on it, assuming I can get to the
> box. But if the problem were no network protocols installed on the eOn
> box then how would the other two boxes that CAN register it be able to
> do so?
> Thanks,
> Ellen
>|||Hi John,
Yes, I mentioned in my original post that I could register it from both
my desktop and from one of "my" servers.
The network protocols are the same on the eOn box as on "my" servers:
named pipes and tcp. Since the fat client can connect to "my" servers,
I think it's safe to say this isn't the problem.
I have now succeeded in creating an ODBC connection, which would not
have been my first choice, but right now if it works I'm happy.
Thanks,
Ellen
Registering SQL Server in Enterprise Manager
I have a couple of users that have been using the SQL Server 2000 Enterprise
Manager. They had our production server (as well as a test server)
registered on their machines as valid servers. Yesterday these users started
experiencing a problem with accessing the production server via Enterprise
Manager. When they tried to access the server they would receive the message
"Cannot open user default database. Login Failed". Each of these users is in
an AD group (defined as a user in SQL Server) that has access to our
production database. I verified the access of the group and everything looks
fine. The default database exists and the group is defined as a user. None
of these users are owners of objects in their default database.
The only way I have found to fix this was to go through security on our
production server and add their actual network user name. The whole reason I
have the group set up is so I don't have to add users individually. I also
verified the setup of our test server. This also uses a group instead of
individual network sign ons. They aren't having any problems accessing the
test server from Enterprise Manager.
How do I fix this so I don't have to have individual network sign ons?
Thanks for any help.
Nancy
That sounds pretty strange. Did you try deleting the group's login in SQL
and re-creating it?
-Argenis
"Nancy Kafer" <nkafer@.homesteaderslife.com> wrote in message
news:ONbr4QOIFHA.3628@.TK2MSFTNGP15.phx.gbl...
> I have a couple of users that have been using the SQL Server 2000
Enterprise
> Manager. They had our production server (as well as a test server)
> registered on their machines as valid servers. Yesterday these users
started
> experiencing a problem with accessing the production server via Enterprise
> Manager. When they tried to access the server they would receive the
message
> "Cannot open user default database. Login Failed". Each of these users is
in
> an AD group (defined as a user in SQL Server) that has access to our
> production database. I verified the access of the group and everything
looks
> fine. The default database exists and the group is defined as a user. None
> of these users are owners of objects in their default database.
> The only way I have found to fix this was to go through security on our
> production server and add their actual network user name. The whole reason
I
> have the group set up is so I don't have to add users individually. I also
> verified the setup of our test server. This also uses a group instead of
> individual network sign ons. They aren't having any problems accessing the
> test server from Enterprise Manager.
> How do I fix this so I don't have to have individual network sign ons?
> Thanks for any help.
> Nancy
>
|||I thought about doing that but I hadn't yet because I didn't want to have to
recreate the security for the tables in the database. One thing I did do
though was added a new AD group with these users and then added that to the
SQL Server security. This still didn't fix the problem. I'm thinking the
only way to fix it may be to try deleting the original AD group from SQL
Server and then re-adding it.
Thanks.
Nancy
"Argenis Fernandez" <argenis@.spam.sucks.gmail.com> wrote in message
news:ewrCUZQIFHA.1396@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> That sounds pretty strange. Did you try deleting the group's login in SQL
> and re-creating it?
> -Argenis
> "Nancy Kafer" <nkafer@.homesteaderslife.com> wrote in message
> news:ONbr4QOIFHA.3628@.TK2MSFTNGP15.phx.gbl...
> Enterprise
> started
Enterprise[vbcol=seagreen]
> message
is[vbcol=seagreen]
> in
> looks
None[vbcol=seagreen]
reason[vbcol=seagreen]
> I
also[vbcol=seagreen]
the
>
Manager. They had our production server (as well as a test server)
registered on their machines as valid servers. Yesterday these users started
experiencing a problem with accessing the production server via Enterprise
Manager. When they tried to access the server they would receive the message
"Cannot open user default database. Login Failed". Each of these users is in
an AD group (defined as a user in SQL Server) that has access to our
production database. I verified the access of the group and everything looks
fine. The default database exists and the group is defined as a user. None
of these users are owners of objects in their default database.
The only way I have found to fix this was to go through security on our
production server and add their actual network user name. The whole reason I
have the group set up is so I don't have to add users individually. I also
verified the setup of our test server. This also uses a group instead of
individual network sign ons. They aren't having any problems accessing the
test server from Enterprise Manager.
How do I fix this so I don't have to have individual network sign ons?
Thanks for any help.
Nancy
That sounds pretty strange. Did you try deleting the group's login in SQL
and re-creating it?
-Argenis
"Nancy Kafer" <nkafer@.homesteaderslife.com> wrote in message
news:ONbr4QOIFHA.3628@.TK2MSFTNGP15.phx.gbl...
> I have a couple of users that have been using the SQL Server 2000
Enterprise
> Manager. They had our production server (as well as a test server)
> registered on their machines as valid servers. Yesterday these users
started
> experiencing a problem with accessing the production server via Enterprise
> Manager. When they tried to access the server they would receive the
message
> "Cannot open user default database. Login Failed". Each of these users is
in
> an AD group (defined as a user in SQL Server) that has access to our
> production database. I verified the access of the group and everything
looks
> fine. The default database exists and the group is defined as a user. None
> of these users are owners of objects in their default database.
> The only way I have found to fix this was to go through security on our
> production server and add their actual network user name. The whole reason
I
> have the group set up is so I don't have to add users individually. I also
> verified the setup of our test server. This also uses a group instead of
> individual network sign ons. They aren't having any problems accessing the
> test server from Enterprise Manager.
> How do I fix this so I don't have to have individual network sign ons?
> Thanks for any help.
> Nancy
>
|||I thought about doing that but I hadn't yet because I didn't want to have to
recreate the security for the tables in the database. One thing I did do
though was added a new AD group with these users and then added that to the
SQL Server security. This still didn't fix the problem. I'm thinking the
only way to fix it may be to try deleting the original AD group from SQL
Server and then re-adding it.
Thanks.
Nancy
"Argenis Fernandez" <argenis@.spam.sucks.gmail.com> wrote in message
news:ewrCUZQIFHA.1396@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> That sounds pretty strange. Did you try deleting the group's login in SQL
> and re-creating it?
> -Argenis
> "Nancy Kafer" <nkafer@.homesteaderslife.com> wrote in message
> news:ONbr4QOIFHA.3628@.TK2MSFTNGP15.phx.gbl...
> Enterprise
> started
Enterprise[vbcol=seagreen]
> message
is[vbcol=seagreen]
> in
> looks
None[vbcol=seagreen]
reason[vbcol=seagreen]
> I
also[vbcol=seagreen]
the
>
Registering SQL Server in Enterprise Manager
I have a couple of users that have been using the SQL Server 2000 Enterprise
Manager. They had our production server (as well as a test server)
registered on their machines as valid servers. Yesterday these users started
experiencing a problem with accessing the production server via Enterprise
Manager. When they tried to access the server they would receive the message
"Cannot open user default database. Login Failed". Each of these users is in
an AD group (defined as a user in SQL Server) that has access to our
production database. I verified the access of the group and everything looks
fine. The default database exists and the group is defined as a user. None
of these users are owners of objects in their default database.
The only way I have found to fix this was to go through security on our
production server and add their actual network user name. The whole reason I
have the group set up is so I don't have to add users individually. I also
verified the setup of our test server. This also uses a group instead of
individual network sign ons. They aren't having any problems accessing the
test server from Enterprise Manager.
How do I fix this so I don't have to have individual network sign ons?
Thanks for any help.
NancyThat sounds pretty strange. Did you try deleting the group's login in SQL
and re-creating it?
-Argenis
"Nancy Kafer" <nkafer@.homesteaderslife.com> wrote in message
news:ONbr4QOIFHA.3628@.TK2MSFTNGP15.phx.gbl...
> I have a couple of users that have been using the SQL Server 2000
Enterprise
> Manager. They had our production server (as well as a test server)
> registered on their machines as valid servers. Yesterday these users
started
> experiencing a problem with accessing the production server via Enterprise
> Manager. When they tried to access the server they would receive the
message
> "Cannot open user default database. Login Failed". Each of these users is
in
> an AD group (defined as a user in SQL Server) that has access to our
> production database. I verified the access of the group and everything
looks
> fine. The default database exists and the group is defined as a user. None
> of these users are owners of objects in their default database.
> The only way I have found to fix this was to go through security on our
> production server and add their actual network user name. The whole reason
I
> have the group set up is so I don't have to add users individually. I also
> verified the setup of our test server. This also uses a group instead of
> individual network sign ons. They aren't having any problems accessing the
> test server from Enterprise Manager.
> How do I fix this so I don't have to have individual network sign ons?
> Thanks for any help.
> Nancy
>|||I thought about doing that but I hadn't yet because I didn't want to have to
recreate the security for the tables in the database. One thing I did do
though was added a new AD group with these users and then added that to the
SQL Server security. This still didn't fix the problem. I'm thinking the
only way to fix it may be to try deleting the original AD group from SQL
Server and then re-adding it.
Thanks.
Nancy
"Argenis Fernandez" <argenis@.spam.sucks.gmail.com> wrote in message
news:ewrCUZQIFHA.1396@.TK2MSFTNGP10.phx.gbl...
> That sounds pretty strange. Did you try deleting the group's login in SQL
> and re-creating it?
> -Argenis
> "Nancy Kafer" <nkafer@.homesteaderslife.com> wrote in message
> news:ONbr4QOIFHA.3628@.TK2MSFTNGP15.phx.gbl...
> Enterprise
> started
Enterprise[vbcol=seagreen]
> message
is[vbcol=seagreen]
> in
> looks
None[vbcol=seagreen]
reason[vbcol=seagreen]
> I
also[vbcol=seagreen]
the[vbcol=seagreen]
>
Manager. They had our production server (as well as a test server)
registered on their machines as valid servers. Yesterday these users started
experiencing a problem with accessing the production server via Enterprise
Manager. When they tried to access the server they would receive the message
"Cannot open user default database. Login Failed". Each of these users is in
an AD group (defined as a user in SQL Server) that has access to our
production database. I verified the access of the group and everything looks
fine. The default database exists and the group is defined as a user. None
of these users are owners of objects in their default database.
The only way I have found to fix this was to go through security on our
production server and add their actual network user name. The whole reason I
have the group set up is so I don't have to add users individually. I also
verified the setup of our test server. This also uses a group instead of
individual network sign ons. They aren't having any problems accessing the
test server from Enterprise Manager.
How do I fix this so I don't have to have individual network sign ons?
Thanks for any help.
NancyThat sounds pretty strange. Did you try deleting the group's login in SQL
and re-creating it?
-Argenis
"Nancy Kafer" <nkafer@.homesteaderslife.com> wrote in message
news:ONbr4QOIFHA.3628@.TK2MSFTNGP15.phx.gbl...
> I have a couple of users that have been using the SQL Server 2000
Enterprise
> Manager. They had our production server (as well as a test server)
> registered on their machines as valid servers. Yesterday these users
started
> experiencing a problem with accessing the production server via Enterprise
> Manager. When they tried to access the server they would receive the
message
> "Cannot open user default database. Login Failed". Each of these users is
in
> an AD group (defined as a user in SQL Server) that has access to our
> production database. I verified the access of the group and everything
looks
> fine. The default database exists and the group is defined as a user. None
> of these users are owners of objects in their default database.
> The only way I have found to fix this was to go through security on our
> production server and add their actual network user name. The whole reason
I
> have the group set up is so I don't have to add users individually. I also
> verified the setup of our test server. This also uses a group instead of
> individual network sign ons. They aren't having any problems accessing the
> test server from Enterprise Manager.
> How do I fix this so I don't have to have individual network sign ons?
> Thanks for any help.
> Nancy
>|||I thought about doing that but I hadn't yet because I didn't want to have to
recreate the security for the tables in the database. One thing I did do
though was added a new AD group with these users and then added that to the
SQL Server security. This still didn't fix the problem. I'm thinking the
only way to fix it may be to try deleting the original AD group from SQL
Server and then re-adding it.
Thanks.
Nancy
"Argenis Fernandez" <argenis@.spam.sucks.gmail.com> wrote in message
news:ewrCUZQIFHA.1396@.TK2MSFTNGP10.phx.gbl...
> That sounds pretty strange. Did you try deleting the group's login in SQL
> and re-creating it?
> -Argenis
> "Nancy Kafer" <nkafer@.homesteaderslife.com> wrote in message
> news:ONbr4QOIFHA.3628@.TK2MSFTNGP15.phx.gbl...
> Enterprise
> started
Enterprise[vbcol=seagreen]
> message
is[vbcol=seagreen]
> in
> looks
None[vbcol=seagreen]
reason[vbcol=seagreen]
> I
also[vbcol=seagreen]
the[vbcol=seagreen]
>
Registering SQL Server in Enterprise Manager
I have followed all sugestions for this problem to no avail. I have 2 w2000 boxes connected via local network. Both are running instances of MSSQL8. From Box 2 I can register the MSSQL7 version on box1 and from box1 I can register the MSSQL7 version on box2. However I cannot register the MSSQL8 instancance either way. I can see the instance but get the message
"Specified SQL Server not found ConnectionOpen(Connect())
I have tried registering with the ip address but same problem
I have tried aliases.
In Client Network Utility and Server Network Utility I have both Named pipes(\\.\pipe\sql\query) and tcp/ip (port 1433)
on both machines
Any ideas ??
Regards ClemAre both boxes running both SQL2000 and SQL7? If so, and they are both listening on 1433, then only SQL7 will be accessible since it is not aware of multiple instancing in SQL2000. You may wish to have SQL2k listen on a different port.|||Thanks loach, sounds a likley fix. Excuse my ignorance but what port number can I use? Are port numbers listed somewhere?
Thanks for you time,
Regards Clem|||You can use any port number that is not already in use. It's typically a good idea to use port numbers over 10000 since they are rarely reserved. You can change the port number by starting up the server network utility (in the SQL Server program group), selecting the TCP/IP netowrk library and clicking on properties. To determine which ports are in use on the server, drop to a command prompt and run 'netstat -a'
You must then configure any client that accesses the server to also use that port using either the Client Network Utility or the ODBC connection properties.|||OK did that. Sql log now shows listening on [ip adds]:10000 but still same problem. tried connecting with ip adds but no go and also now on box1 I can't access the local mssql8 (7 is still ok) so i changed back to port 1433. (Is it using this port because it is not 'local'?)
At this stage I think I give up... I have been looking at this problem for about 3 months... so I guess i dont need the 7 databases any more. Any ideas how to remove the original 7 instance?
I am thinking a clean install might be the go?
Regards Clem|||Mmmmmmm clean install *drool* that's definately the way I would go,.. atleast you know where you stand then.|||try using port 1434.
try changing it in MS SQL2k on both machines (both changed at the same time)
is there any form of firewall on the individual computers, or between them? if so, make sure it isn't blocking port 1434 (or whatever port your using)
Try turning off mssql 7.
I don't know the details, but mssql is a registered system process, it integrates to an extent (i believe) with the OS.
Is it possible to successfully run multiple versions on MS SQL server on 1 machine? perhaps it isn't and that is why only ms sql 7 works correctly?
Using ports:
Yes, you can use any port, not in use. If you select a port that is in use, you should find out on the next boot. (something will probably crash, or stop working properly)
Hope this helps,|||Hi Ashleigh,
Yes it is possible to run both instances of mssql on the one server, it is the connecting to the mssql8 version on another machine that is the problem. When doing the connection the target server is even visible as a valid server...
Connecting to mssql7 on either machine is OK and of course both versions are OK if accessed on the local machine.
I believe this problem has been compounded by microsofts slammer virus fixes...
"Specified SQL Server not found ConnectionOpen(Connect())
I have tried registering with the ip address but same problem
I have tried aliases.
In Client Network Utility and Server Network Utility I have both Named pipes(\\.\pipe\sql\query) and tcp/ip (port 1433)
on both machines
Any ideas ??
Regards ClemAre both boxes running both SQL2000 and SQL7? If so, and they are both listening on 1433, then only SQL7 will be accessible since it is not aware of multiple instancing in SQL2000. You may wish to have SQL2k listen on a different port.|||Thanks loach, sounds a likley fix. Excuse my ignorance but what port number can I use? Are port numbers listed somewhere?
Thanks for you time,
Regards Clem|||You can use any port number that is not already in use. It's typically a good idea to use port numbers over 10000 since they are rarely reserved. You can change the port number by starting up the server network utility (in the SQL Server program group), selecting the TCP/IP netowrk library and clicking on properties. To determine which ports are in use on the server, drop to a command prompt and run 'netstat -a'
You must then configure any client that accesses the server to also use that port using either the Client Network Utility or the ODBC connection properties.|||OK did that. Sql log now shows listening on [ip adds]:10000 but still same problem. tried connecting with ip adds but no go and also now on box1 I can't access the local mssql8 (7 is still ok) so i changed back to port 1433. (Is it using this port because it is not 'local'?)
At this stage I think I give up... I have been looking at this problem for about 3 months... so I guess i dont need the 7 databases any more. Any ideas how to remove the original 7 instance?
I am thinking a clean install might be the go?
Regards Clem|||Mmmmmmm clean install *drool* that's definately the way I would go,.. atleast you know where you stand then.|||try using port 1434.
try changing it in MS SQL2k on both machines (both changed at the same time)
is there any form of firewall on the individual computers, or between them? if so, make sure it isn't blocking port 1434 (or whatever port your using)
Try turning off mssql 7.
I don't know the details, but mssql is a registered system process, it integrates to an extent (i believe) with the OS.
Is it possible to successfully run multiple versions on MS SQL server on 1 machine? perhaps it isn't and that is why only ms sql 7 works correctly?
Using ports:
Yes, you can use any port, not in use. If you select a port that is in use, you should find out on the next boot. (something will probably crash, or stop working properly)
Hope this helps,|||Hi Ashleigh,
Yes it is possible to run both instances of mssql on the one server, it is the connecting to the mssql8 version on another machine that is the problem. When doing the connection the target server is even visible as a valid server...
Connecting to mssql7 on either machine is OK and of course both versions are OK if accessed on the local machine.
I believe this problem has been compounded by microsofts slammer virus fixes...
Registering SQL Server in Enterprise Manager
I have a couple of users that have been using the SQL Server 2000 Enterprise
Manager. They had our production server (as well as a test server)
registered on their machines as valid servers. Yesterday these users started
experiencing a problem with accessing the production server via Enterprise
Manager. When they tried to access the server they would receive the message
"Cannot open user default database. Login Failed". Each of these users is in
an AD group (defined as a user in SQL Server) that has access to our
production database. I verified the access of the group and everything looks
fine. The default database exists and the group is defined as a user. None
of these users are owners of objects in their default database.
The only way I have found to fix this was to go through security on our
production server and add their actual network user name. The whole reason I
have the group set up is so I don't have to add users individually. I also
verified the setup of our test server. This also uses a group instead of
individual network sign ons. They aren't having any problems accessing the
test server from Enterprise Manager.
How do I fix this so I don't have to have individual network sign ons?
Thanks for any help.
NancyThat sounds pretty strange. Did you try deleting the group's login in SQL
and re-creating it?
-Argenis
"Nancy Kafer" <nkafer@.homesteaderslife.com> wrote in message
news:ONbr4QOIFHA.3628@.TK2MSFTNGP15.phx.gbl...
> I have a couple of users that have been using the SQL Server 2000
Enterprise
> Manager. They had our production server (as well as a test server)
> registered on their machines as valid servers. Yesterday these users
started
> experiencing a problem with accessing the production server via Enterprise
> Manager. When they tried to access the server they would receive the
message
> "Cannot open user default database. Login Failed". Each of these users is
in
> an AD group (defined as a user in SQL Server) that has access to our
> production database. I verified the access of the group and everything
looks
> fine. The default database exists and the group is defined as a user. None
> of these users are owners of objects in their default database.
> The only way I have found to fix this was to go through security on our
> production server and add their actual network user name. The whole reason
I
> have the group set up is so I don't have to add users individually. I also
> verified the setup of our test server. This also uses a group instead of
> individual network sign ons. They aren't having any problems accessing the
> test server from Enterprise Manager.
> How do I fix this so I don't have to have individual network sign ons?
> Thanks for any help.
> Nancy
>|||I thought about doing that but I hadn't yet because I didn't want to have to
recreate the security for the tables in the database. One thing I did do
though was added a new AD group with these users and then added that to the
SQL Server security. This still didn't fix the problem. I'm thinking the
only way to fix it may be to try deleting the original AD group from SQL
Server and then re-adding it.
Thanks.
Nancy
"Argenis Fernandez" <argenis@.spam.sucks.gmail.com> wrote in message
news:ewrCUZQIFHA.1396@.TK2MSFTNGP10.phx.gbl...
> That sounds pretty strange. Did you try deleting the group's login in SQL
> and re-creating it?
> -Argenis
> "Nancy Kafer" <nkafer@.homesteaderslife.com> wrote in message
> news:ONbr4QOIFHA.3628@.TK2MSFTNGP15.phx.gbl...
> > I have a couple of users that have been using the SQL Server 2000
> Enterprise
> > Manager. They had our production server (as well as a test server)
> > registered on their machines as valid servers. Yesterday these users
> started
> > experiencing a problem with accessing the production server via
Enterprise
> > Manager. When they tried to access the server they would receive the
> message
> > "Cannot open user default database. Login Failed". Each of these users
is
> in
> > an AD group (defined as a user in SQL Server) that has access to our
> > production database. I verified the access of the group and everything
> looks
> > fine. The default database exists and the group is defined as a user.
None
> > of these users are owners of objects in their default database.
> >
> > The only way I have found to fix this was to go through security on our
> > production server and add their actual network user name. The whole
reason
> I
> > have the group set up is so I don't have to add users individually. I
also
> > verified the setup of our test server. This also uses a group instead of
> > individual network sign ons. They aren't having any problems accessing
the
> > test server from Enterprise Manager.
> >
> > How do I fix this so I don't have to have individual network sign ons?
> >
> > Thanks for any help.
> >
> > Nancy
> >
> >
>
Manager. They had our production server (as well as a test server)
registered on their machines as valid servers. Yesterday these users started
experiencing a problem with accessing the production server via Enterprise
Manager. When they tried to access the server they would receive the message
"Cannot open user default database. Login Failed". Each of these users is in
an AD group (defined as a user in SQL Server) that has access to our
production database. I verified the access of the group and everything looks
fine. The default database exists and the group is defined as a user. None
of these users are owners of objects in their default database.
The only way I have found to fix this was to go through security on our
production server and add their actual network user name. The whole reason I
have the group set up is so I don't have to add users individually. I also
verified the setup of our test server. This also uses a group instead of
individual network sign ons. They aren't having any problems accessing the
test server from Enterprise Manager.
How do I fix this so I don't have to have individual network sign ons?
Thanks for any help.
NancyThat sounds pretty strange. Did you try deleting the group's login in SQL
and re-creating it?
-Argenis
"Nancy Kafer" <nkafer@.homesteaderslife.com> wrote in message
news:ONbr4QOIFHA.3628@.TK2MSFTNGP15.phx.gbl...
> I have a couple of users that have been using the SQL Server 2000
Enterprise
> Manager. They had our production server (as well as a test server)
> registered on their machines as valid servers. Yesterday these users
started
> experiencing a problem with accessing the production server via Enterprise
> Manager. When they tried to access the server they would receive the
message
> "Cannot open user default database. Login Failed". Each of these users is
in
> an AD group (defined as a user in SQL Server) that has access to our
> production database. I verified the access of the group and everything
looks
> fine. The default database exists and the group is defined as a user. None
> of these users are owners of objects in their default database.
> The only way I have found to fix this was to go through security on our
> production server and add their actual network user name. The whole reason
I
> have the group set up is so I don't have to add users individually. I also
> verified the setup of our test server. This also uses a group instead of
> individual network sign ons. They aren't having any problems accessing the
> test server from Enterprise Manager.
> How do I fix this so I don't have to have individual network sign ons?
> Thanks for any help.
> Nancy
>|||I thought about doing that but I hadn't yet because I didn't want to have to
recreate the security for the tables in the database. One thing I did do
though was added a new AD group with these users and then added that to the
SQL Server security. This still didn't fix the problem. I'm thinking the
only way to fix it may be to try deleting the original AD group from SQL
Server and then re-adding it.
Thanks.
Nancy
"Argenis Fernandez" <argenis@.spam.sucks.gmail.com> wrote in message
news:ewrCUZQIFHA.1396@.TK2MSFTNGP10.phx.gbl...
> That sounds pretty strange. Did you try deleting the group's login in SQL
> and re-creating it?
> -Argenis
> "Nancy Kafer" <nkafer@.homesteaderslife.com> wrote in message
> news:ONbr4QOIFHA.3628@.TK2MSFTNGP15.phx.gbl...
> > I have a couple of users that have been using the SQL Server 2000
> Enterprise
> > Manager. They had our production server (as well as a test server)
> > registered on their machines as valid servers. Yesterday these users
> started
> > experiencing a problem with accessing the production server via
Enterprise
> > Manager. When they tried to access the server they would receive the
> message
> > "Cannot open user default database. Login Failed". Each of these users
is
> in
> > an AD group (defined as a user in SQL Server) that has access to our
> > production database. I verified the access of the group and everything
> looks
> > fine. The default database exists and the group is defined as a user.
None
> > of these users are owners of objects in their default database.
> >
> > The only way I have found to fix this was to go through security on our
> > production server and add their actual network user name. The whole
reason
> I
> > have the group set up is so I don't have to add users individually. I
also
> > verified the setup of our test server. This also uses a group instead of
> > individual network sign ons. They aren't having any problems accessing
the
> > test server from Enterprise Manager.
> >
> > How do I fix this so I don't have to have individual network sign ons?
> >
> > Thanks for any help.
> >
> > Nancy
> >
> >
>
registering SQL Server behind firewall
We just implemented a SQL Server, that is in a PDMZ
(public facing dmz). It is using a local account to run
the services as it it not on our corporate network. We
cannot register the server. Does anyone know what ports
need to be open, in order to register this SQL Server? In
talking with our network folks, I'm pretty sure 1433 /
1434 are open. Any ideas...Thanks.
Tom.INF: TCP Ports Needed for Communication to SQL Server Through a Firewall
http://support.microsoft.com/?id=287932
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Tom Mongold" <tom.mongold@.stdreg.com> wrote in message
news:024a01c35606$4072e550$a401280a@.phx.gbl...
We just implemented a SQL Server, that is in a PDMZ
(public facing dmz). It is using a local account to run
the services as it it not on our corporate network. We
cannot register the server. Does anyone know what ports
need to be open, in order to register this SQL Server? In
talking with our network folks, I'm pretty sure 1433 /
1434 are open. Any ideas...Thanks.
Tom.
(public facing dmz). It is using a local account to run
the services as it it not on our corporate network. We
cannot register the server. Does anyone know what ports
need to be open, in order to register this SQL Server? In
talking with our network folks, I'm pretty sure 1433 /
1434 are open. Any ideas...Thanks.
Tom.INF: TCP Ports Needed for Communication to SQL Server Through a Firewall
http://support.microsoft.com/?id=287932
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Tom Mongold" <tom.mongold@.stdreg.com> wrote in message
news:024a01c35606$4072e550$a401280a@.phx.gbl...
We just implemented a SQL Server, that is in a PDMZ
(public facing dmz). It is using a local account to run
the services as it it not on our corporate network. We
cannot register the server. Does anyone know what ports
need to be open, in order to register this SQL Server? In
talking with our network folks, I'm pretty sure 1433 /
1434 are open. Any ideas...Thanks.
Tom.
Registering SQL Server
I m having 2 servers i wansted register the SQL server at one node
when i m registering the SQL server through SQL enterprises it showing the
error
"Unable to connect the sql server unavailable of does not exist"
what can be the problem
Yousuf Khan
Programmer
Hi
You could have typed in the wrong name, the server is not using the
protocols you have configured or ports/permissions are not set up correctly
to allow you to connect e.g. a firewall or restricted account.
Can you connect using Query Analyser?
You may want to try specifying the IP address instead if the name?
John
"Yousuf" wrote:
> I m having 2 servers i wansted register the SQL server at one node
> when i m registering the SQL server through SQL enterprises it showing the
> error
> "Unable to connect the sql server unavailable of does not exist"
> what can be the problem
> --
> Yousuf Khan
> Programmer
|||both the systems are using the same prtocols(NetBeui) and i dont have any
firwall
both systems are having win nt and i m able to make turusties for each other
but not able to connect sql
Yousuf Khan
Programmer
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> You could have typed in the wrong name, the server is not using the
> protocols you have configured or ports/permissions are not set up correctly
> to allow you to connect e.g. a firewall or restricted account.
> Can you connect using Query Analyser?
> You may want to try specifying the IP address instead if the name?
> John
>
> "Yousuf" wrote:
when i m registering the SQL server through SQL enterprises it showing the
error
"Unable to connect the sql server unavailable of does not exist"
what can be the problem
Yousuf Khan
Programmer
Hi
You could have typed in the wrong name, the server is not using the
protocols you have configured or ports/permissions are not set up correctly
to allow you to connect e.g. a firewall or restricted account.
Can you connect using Query Analyser?
You may want to try specifying the IP address instead if the name?
John
"Yousuf" wrote:
> I m having 2 servers i wansted register the SQL server at one node
> when i m registering the SQL server through SQL enterprises it showing the
> error
> "Unable to connect the sql server unavailable of does not exist"
> what can be the problem
> --
> Yousuf Khan
> Programmer
|||both the systems are using the same prtocols(NetBeui) and i dont have any
firwall
both systems are having win nt and i m able to make turusties for each other
but not able to connect sql
Yousuf Khan
Programmer
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> You could have typed in the wrong name, the server is not using the
> protocols you have configured or ports/permissions are not set up correctly
> to allow you to connect e.g. a firewall or restricted account.
> Can you connect using Query Analyser?
> You may want to try specifying the IP address instead if the name?
> John
>
> "Yousuf" wrote:
Registering SQL Server
I m having 2 servers i wansted register the SQL server at one node
when i m registering the SQL server through SQL enterprises it showing the
error
"Unable to connect the sql server unavailable of does not exist"
what can be the problem
--
Yousuf Khan
ProgrammerHi
You could have typed in the wrong name, the server is not using the
protocols you have configured or ports/permissions are not set up correctly
to allow you to connect e.g. a firewall or restricted account.
Can you connect using Query Analyser?
You may want to try specifying the IP address instead if the name?
John
"Yousuf" wrote:
> I m having 2 servers i wansted register the SQL server at one node
> when i m registering the SQL server through SQL enterprises it showing the
> error
> "Unable to connect the sql server unavailable of does not exist"
> what can be the problem
> --
> Yousuf Khan
> Programmer|||both the systems are using the same prtocols(NetBeui) and i dont have any
firwall
both systems are having win nt and i m able to make turusties for each other
but not able to connect sql
--
Yousuf Khan
Programmer
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> You could have typed in the wrong name, the server is not using the
> protocols you have configured or ports/permissions are not set up correctl
y
> to allow you to connect e.g. a firewall or restricted account.
> Can you connect using Query Analyser?
> You may want to try specifying the IP address instead if the name?
> John
>
> "Yousuf" wrote:
>
when i m registering the SQL server through SQL enterprises it showing the
error
"Unable to connect the sql server unavailable of does not exist"
what can be the problem
--
Yousuf Khan
ProgrammerHi
You could have typed in the wrong name, the server is not using the
protocols you have configured or ports/permissions are not set up correctly
to allow you to connect e.g. a firewall or restricted account.
Can you connect using Query Analyser?
You may want to try specifying the IP address instead if the name?
John
"Yousuf" wrote:
> I m having 2 servers i wansted register the SQL server at one node
> when i m registering the SQL server through SQL enterprises it showing the
> error
> "Unable to connect the sql server unavailable of does not exist"
> what can be the problem
> --
> Yousuf Khan
> Programmer|||both the systems are using the same prtocols(NetBeui) and i dont have any
firwall
both systems are having win nt and i m able to make turusties for each other
but not able to connect sql
--
Yousuf Khan
Programmer
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> You could have typed in the wrong name, the server is not using the
> protocols you have configured or ports/permissions are not set up correctl
y
> to allow you to connect e.g. a firewall or restricted account.
> Can you connect using Query Analyser?
> You may want to try specifying the IP address instead if the name?
> John
>
> "Yousuf" wrote:
>
Registering SQL SERVER
Hi,
How to register a Remote SQL SERVER from a node in Local Area Network?You need to set up a linked server. See Linked Server in Books Online. If you need more help, let us know.
How to register a Remote SQL SERVER from a node in Local Area Network?You need to set up a linked server. See Linked Server in Books Online. If you need more help, let us know.
Registering SQL Server
I m having 2 servers i wansted register the SQL server at one node
when i m registering the SQL server through SQL enterprises it showing the
error
"Unable to connect the sql server unavailable of does not exist"
what can be the problem
--
Yousuf Khan
ProgrammerHi
You could have typed in the wrong name, the server is not using the
protocols you have configured or ports/permissions are not set up correctly
to allow you to connect e.g. a firewall or restricted account.
Can you connect using Query Analyser?
You may want to try specifying the IP address instead if the name?
John
"Yousuf" wrote:
> I m having 2 servers i wansted register the SQL server at one node
> when i m registering the SQL server through SQL enterprises it showing the
> error
> "Unable to connect the sql server unavailable of does not exist"
> what can be the problem
> --
> Yousuf Khan
> Programmer|||both the systems are using the same prtocols(NetBeui) and i dont have any
firwall
both systems are having win nt and i m able to make turusties for each other
but not able to connect sql
--
Yousuf Khan
Programmer
"John Bell" wrote:
> Hi
> You could have typed in the wrong name, the server is not using the
> protocols you have configured or ports/permissions are not set up correctly
> to allow you to connect e.g. a firewall or restricted account.
> Can you connect using Query Analyser?
> You may want to try specifying the IP address instead if the name?
> John
>
> "Yousuf" wrote:
> > I m having 2 servers i wansted register the SQL server at one node
> > when i m registering the SQL server through SQL enterprises it showing the
> > error
> > "Unable to connect the sql server unavailable of does not exist"
> > what can be the problem
> > --
> > Yousuf Khan
> > Programmer|||Hi,
Can you connect to an administrative share eg \\server_name\c$ ?
Can you launch Enterprise Manager on the server and connect to the local
instance? Can you connect EM on one SQL Server to the other SQL Server?
Do you know which network library SQL Server is using? I didn't know that
it could use NetBEUI so if the servers are communicating only on NetBEUI and
SQL Server is communicating on Named Pipes or TCP/IP, might this not cause a
problem?
Cheers,
IM|||I am able to conncet to local machine EM not able to other server, i am using
netbeui protocol through Win NT i m getting his share and users but not
getting conneted to sql server
--
Yousuf Khan
Programmer
"Ian Murphy" wrote:
> Hi,
> Can you connect to an administrative share eg \\server_name\c$ ?
> Can you launch Enterprise Manager on the server and connect to the local
> instance? Can you connect EM on one SQL Server to the other SQL Server?
> Do you know which network library SQL Server is using? I didn't know that
> it could use NetBEUI so if the servers are communicating only on NetBEUI and
> SQL Server is communicating on Named Pipes or TCP/IP, might this not cause a
> problem?
> Cheers,
> IM
when i m registering the SQL server through SQL enterprises it showing the
error
"Unable to connect the sql server unavailable of does not exist"
what can be the problem
--
Yousuf Khan
ProgrammerHi
You could have typed in the wrong name, the server is not using the
protocols you have configured or ports/permissions are not set up correctly
to allow you to connect e.g. a firewall or restricted account.
Can you connect using Query Analyser?
You may want to try specifying the IP address instead if the name?
John
"Yousuf" wrote:
> I m having 2 servers i wansted register the SQL server at one node
> when i m registering the SQL server through SQL enterprises it showing the
> error
> "Unable to connect the sql server unavailable of does not exist"
> what can be the problem
> --
> Yousuf Khan
> Programmer|||both the systems are using the same prtocols(NetBeui) and i dont have any
firwall
both systems are having win nt and i m able to make turusties for each other
but not able to connect sql
--
Yousuf Khan
Programmer
"John Bell" wrote:
> Hi
> You could have typed in the wrong name, the server is not using the
> protocols you have configured or ports/permissions are not set up correctly
> to allow you to connect e.g. a firewall or restricted account.
> Can you connect using Query Analyser?
> You may want to try specifying the IP address instead if the name?
> John
>
> "Yousuf" wrote:
> > I m having 2 servers i wansted register the SQL server at one node
> > when i m registering the SQL server through SQL enterprises it showing the
> > error
> > "Unable to connect the sql server unavailable of does not exist"
> > what can be the problem
> > --
> > Yousuf Khan
> > Programmer|||Hi,
Can you connect to an administrative share eg \\server_name\c$ ?
Can you launch Enterprise Manager on the server and connect to the local
instance? Can you connect EM on one SQL Server to the other SQL Server?
Do you know which network library SQL Server is using? I didn't know that
it could use NetBEUI so if the servers are communicating only on NetBEUI and
SQL Server is communicating on Named Pipes or TCP/IP, might this not cause a
problem?
Cheers,
IM|||I am able to conncet to local machine EM not able to other server, i am using
netbeui protocol through Win NT i m getting his share and users but not
getting conneted to sql server
--
Yousuf Khan
Programmer
"Ian Murphy" wrote:
> Hi,
> Can you connect to an administrative share eg \\server_name\c$ ?
> Can you launch Enterprise Manager on the server and connect to the local
> instance? Can you connect EM on one SQL Server to the other SQL Server?
> Do you know which network library SQL Server is using? I didn't know that
> it could use NetBEUI so if the servers are communicating only on NetBEUI and
> SQL Server is communicating on Named Pipes or TCP/IP, might this not cause a
> problem?
> Cheers,
> IM
Registering SQL Server
Hi,
I need to register to a SQL Serve that is part of our Network but is on a
different Subnet Mask and Default Gateway IP Range.
This is not working. But I can access the Server remotely using remote login
tools.
Is there anything I need to do on the security side of SQL Server in order
for to be able to register to it? This would make my life a lot easier.
Thanks In Advance,
Kevin.Kevin,
There might be a firewall causing that. Try telnetting <ip_address>:1433, if
that doesn't work you need to open it.
Jon Jahren
"Kevin Humphreys" <khumphreys@.hotmail.com> wrote in message
news:OL7gXi#xEHA.2212@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I need to register to a SQL Serve that is part of our Network but is on a
> different Subnet Mask and Default Gateway IP Range.
> This is not working. But I can access the Server remotely using remote
login
> tools.
> Is there anything I need to do on the security side of SQL Server in order
> for to be able to register to it? This would make my life a lot easier.
> Thanks In Advance,
> Kevin.
>|||Even better how do I register to a SQL Server using the Server's local
system account.
"Kevin Humphreys" <khumphreys@.hotmail.com> wrote in message
news:OL7gXi%23xEHA.2212@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I need to register to a SQL Serve that is part of our Network but is on a
> different Subnet Mask and Default Gateway IP Range.
> This is not working. But I can access the Server remotely using remote
> login tools.
> Is there anything I need to do on the security side of SQL Server in order
> for to be able to register to it? This would make my life a lot easier.
> Thanks In Advance,
> Kevin.
>|||You would do this when logged onto the SQL Server box and it
would work for Enterprise Manager on the SQL Server box
only. It's a local account...local to that box only.
You won't accomplish much with that. What you may be
thinking is another approach where your login is added as a
local administrator on the SQL Server box. Then you register
the SQL Server with your login. That's similar to what it
sounds like you are asking for.
-Sue
On Thu, 11 Nov 2004 13:59:45 -0000, "Kevin Humphreys"
<khumphreys@.hotmail.com> wrote:
>Even better how do I register to a SQL Server using the Server's local
>system account.
>"Kevin Humphreys" <khumphreys@.hotmail.com> wrote in message
>news:OL7gXi%23xEHA.2212@.TK2MSFTNGP15.phx.gbl...
>
I need to register to a SQL Serve that is part of our Network but is on a
different Subnet Mask and Default Gateway IP Range.
This is not working. But I can access the Server remotely using remote login
tools.
Is there anything I need to do on the security side of SQL Server in order
for to be able to register to it? This would make my life a lot easier.
Thanks In Advance,
Kevin.Kevin,
There might be a firewall causing that. Try telnetting <ip_address>:1433, if
that doesn't work you need to open it.
Jon Jahren
"Kevin Humphreys" <khumphreys@.hotmail.com> wrote in message
news:OL7gXi#xEHA.2212@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I need to register to a SQL Serve that is part of our Network but is on a
> different Subnet Mask and Default Gateway IP Range.
> This is not working. But I can access the Server remotely using remote
login
> tools.
> Is there anything I need to do on the security side of SQL Server in order
> for to be able to register to it? This would make my life a lot easier.
> Thanks In Advance,
> Kevin.
>|||Even better how do I register to a SQL Server using the Server's local
system account.
"Kevin Humphreys" <khumphreys@.hotmail.com> wrote in message
news:OL7gXi%23xEHA.2212@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I need to register to a SQL Serve that is part of our Network but is on a
> different Subnet Mask and Default Gateway IP Range.
> This is not working. But I can access the Server remotely using remote
> login tools.
> Is there anything I need to do on the security side of SQL Server in order
> for to be able to register to it? This would make my life a lot easier.
> Thanks In Advance,
> Kevin.
>|||You would do this when logged onto the SQL Server box and it
would work for Enterprise Manager on the SQL Server box
only. It's a local account...local to that box only.
You won't accomplish much with that. What you may be
thinking is another approach where your login is added as a
local administrator on the SQL Server box. Then you register
the SQL Server with your login. That's similar to what it
sounds like you are asking for.
-Sue
On Thu, 11 Nov 2004 13:59:45 -0000, "Kevin Humphreys"
<khumphreys@.hotmail.com> wrote:
>Even better how do I register to a SQL Server using the Server's local
>system account.
>"Kevin Humphreys" <khumphreys@.hotmail.com> wrote in message
>news:OL7gXi%23xEHA.2212@.TK2MSFTNGP15.phx.gbl...
>
Registering SQL Cache Dependency in web.config. Why elsewhere, too?
I have a sqlCacheDependency element registered in web.config that I figured would set the database up to deliver all notifications for all its tables:
<
sqlCacheDependencyenabled="true"><
databases><
addname="MyDb"connectionStringName="MyDbConnnectionString"/></
databases></
sqlCacheDependency>I've seen docs saying that's all I need to do with SQL Server 2005, but that doesn't appear to be the case. I get the error:
The database 'MyDB' is not enabled for SQL cache notification. To enable a database for SQL cache notification, please use the System.Web.Caching.SqlCacheDependencyAdmin.EnableNotifications method, or the command line tool aspnet_regsql. To use the tool, please run 'aspnet_regsql.exe -?' for more information.
Are the docs I read wrong or am I missing something?
I beleive the sytax would be:
<
caching><
sqlCacheDependencyenabled ="true" ><
databases><
addname="MyDb"connectionStringName="MyDbConnnectionString" /></
databases></
sqlCacheDependency></
caching>
And then on your aspx page:
<asp:sqldatasourceid="Whatever"runat="server"connectionstring="<%$ ConnectionStrings:MyDbConnnectionString %>"datasourcemode="DataSet"enablecaching="true"CacheKeyDependency="MyDb"selectcommand="Whatever_SP"selectcommandtype="StoredProcedure">|||
The web.config file is set up correctly, my problem is that I can't get notification services working. I have to resort to polling although I have SQL Server 2005.
To add more detail, I'm using Windows XP Pro and I programatically add the SqlCacheDependency:
SqlCacheDependency myDependency = new SqlCacheDependency( "MyDb", "MyTable" );
Cache.Insert( blah,
blah,
...
myDependency
... );
Everything executes correctly, but unless I use the SqlCacheDependencyAdmin or aspnet_regsql to set up polling, it throws the error displayed in my first post. If I have polling set up, the error goes away, but I'm not taking full advantage of the performance benefits of SQL Server 2005 notification services.
|||Anyone have any ideas on this? I'm perplexed!|||I think most of what you need is covered in the links below because it maybe permissions related. Hope this helps.
http://msdn2.microsoft.com/en-us/library/system.web.caching.sqlcachedependencyadmin.aspx
http://msdn2.microsoft.com/en-us/library/xh507fc5.aspx
|||
I wondered if there might be some permission issues, though I haven't discovered what permissions may be required.
What's curious is that I'd expect the SqlCacheDependency to throw some permissions exception in such a case, however, and I wasn't seeing that.
I'll have to keep digging...
|||Bump! I was hoping the issue would go away when I moved our SQL Server to a development server, but the problem persists.
My progress:
1. I discovered SQL Server can't run under the local machine account for Notification Services to work properly so I switched to Network Service... didn't help.
2. Apparently you need to manually create a Service Broker endpoint and enable the database to use it. Also didn't help...
3. I read a lot of people said they have to call SqlDependency.Start() to get it working... didn't help.
|||When pemissions related problem cannot be traced it usually means the service in this case the Notification service may be SQL Server Agent dependent which means the account that runs the Agent must have Admin permissions. The reason is even to run Replications the Agent needs network access and DTS automation, the list goes on. Hope this helps.|||Okay, the latest in the saga is that a Microsoft support rep is claiming the SQL Server 2005 lost the ability to integrate with SqlCacheDependency through anything other than polling in the release version. This seems fishy, since it contradicts their documentation and a lot of other resources, so I'll see if I can get to the bottom of it.|||As I suspected, query notification-based cache invalidation is alive and well in SQL Server 2005. I did a little digging and ended up finding a couple of issues:1. You can't use the constructor I was using to set up notification-based dependencies (you need to pass in the SqlCommand).
2. You need to exclude the command SET NOCOUNT ON from your stored procedure.
See here:http://forums.asp.net/1353521/ShowThread.aspx#1353521 for more.
Subscribe to:
Posts (Atom)