connect to remote sql server failed

I couldn’t connect to the sql server instance (10.192.130.80\development2 and
10.192.130.80\development3) remotely on enterprise manager and query
analyzer. The error is sql server does not exist or access denied. I setup
well in the client network utility and put sever name and port number in it.
But I still got same error. Could someone give me some tips what reason is?
thanks.
Can you ping those servers?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Iter" <Iter@.discussions.microsoft.com> wrote in message
news:39D7F4E4-6CA8-4588-8FB7-2758A1D4A83F@.microsoft.com...
>I couldn't connect to the sql server instance (10.192.130.80\development2
>and
> 10.192.130.80\development3) remotely on enterprise manager and query
> analyzer. The error is sql server does not exist or access denied. I setup
> well in the client network utility and put sever name and port number in
> it.
> But I still got same error. Could someone give me some tips what reason
> is?
> thanks.
>
|||Yes, I can Ping them.
"Arnie Rowland" wrote:

> Can you ping those servers?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to the
> top yourself.
> - H. Norman Schwarzkopf
>
> "Iter" <Iter@.discussions.microsoft.com> wrote in message
> news:39D7F4E4-6CA8-4588-8FB7-2758A1D4A83F@.microsoft.com...
>
>
|||Is the SQL Server listening on TCP?
Check the SQL ERRORLOG for a line like:
SQL Server listening on tcp, shared memory, named pipes
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Iter" <Iter@.discussions.microsoft.com> wrote in message
news:39D7F4E4-6CA8-4588-8FB7-2758A1D4A83F@.microsoft.com...
>I couldn't connect to the sql server instance (10.192.130.80\development2
>and
> 10.192.130.80\development3) remotely on enterprise manager and query
> analyzer. The error is sql server does not exist or access denied. I setup
> well in the client network utility and put sever name and port number in
> it.
> But I still got same error. Could someone give me some tips what reason
> is?
> thanks.
>

connect to remote sql server failed

I couldn’t connect to the sql server instance (10.192.130.80\development2
and
10.192.130.80\development3) remotely on enterprise manager and query
analyzer. The error is sql server does not exist or access denied. I setup
well in the client network utility and put sever name and port number in it.
But I still got same error. Could someone give me some tips what reason is?
thanks.Can you ping those servers?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Iter" <Iter@.discussions.microsoft.com> wrote in message
news:39D7F4E4-6CA8-4588-8FB7-2758A1D4A83F@.microsoft.com...
>I couldn't connect to the sql server instance (10.192.130.80\development2
>and
> 10.192.130.80\development3) remotely on enterprise manager and query
> analyzer. The error is sql server does not exist or access denied. I setup
> well in the client network utility and put sever name and port number in
> it.
> But I still got same error. Could someone give me some tips what reason
> is?
> thanks.
>|||Yes, I can Ping them.
"Arnie Rowland" wrote:

> Can you ping those servers?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to th
e
> top yourself.
> - H. Norman Schwarzkopf
>
> "Iter" <Iter@.discussions.microsoft.com> wrote in message
> news:39D7F4E4-6CA8-4588-8FB7-2758A1D4A83F@.microsoft.com...
>
>|||Is the SQL Server listening on TCP?
Check the SQL ERRORLOG for a line like:
SQL Server listening on tcp, shared memory, named pipes
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Iter" <Iter@.discussions.microsoft.com> wrote in message
news:39D7F4E4-6CA8-4588-8FB7-2758A1D4A83F@.microsoft.com...
>I couldn't connect to the sql server instance (10.192.130.80\development2
>and
> 10.192.130.80\development3) remotely on enterprise manager and query
> analyzer. The error is sql server does not exist or access denied. I setup
> well in the client network utility and put sever name and port number in
> it.
> But I still got same error. Could someone give me some tips what reason
> is?
> thanks.
>sqlsql

Connect to remote server

From Enterprise Manager on my PC, how do I connect to a remote server over
the internet - I have the IP address, User Name and Password.

ThanksWhen creating an SQL connection using SQL Server EM you will need to:

Configure the server alias
Create the SQL connection.

Configure the Server alias

Open SQL Server Client Network Utility.
When Client Network Utility opens, click on the Alias tab.
Click on the Add button.
In the Server Alias text box enter a name for your SQL connection.
Select TCP/IP under Network libraries
Enter the IP address of the Server your SQL database is located on, in
the Server name text box.
Click on the OK button.
Your Server alias will now be configured, click on the Apply button.
Click on the OK button.

Create Connection

Open SQL Server Enterprise Manager
When Enterprise Manager opens, right click SQL Server Group and select
New SQL Server Registration.
The Register SQL Server wizard will now open.
Click on the Next button.
>From the Available Servers drop down menu, select the server alias you
created earlier.
Click on the Add button.
The server should now be listed under Added servers, click on the Next
button.
When the next dialog box appears select 'The SQL Server login
information that was assigned to me by the system administrator' (see
above).
Click on the Next button.
Enter your Login name and Password - this will be used every time you
connect to your SQL server. Click on the Next button.
Ensure that 'Add the SQL Server(s) to an existing SQL Server group' is
selected and 'SQL Server Group' is selected for Group name.

Click on the Next button.
When the next dialog box opens you can click on the Finish button.
Your SQL Connection will now be created.

HTH
Paul|||Paul

That works fine, thanks.

<stpaul_71@.yahoo.com> wrote in message
news:1102537081.548714.60980@.z14g2000cwz.googlegro ups.com...
> When creating an SQL connection using SQL Server EM you will need to:
> Configure the server alias
> Create the SQL connection.
> Configure the Server alias
> Open SQL Server Client Network Utility.
> When Client Network Utility opens, click on the Alias tab.
> Click on the Add button.
> In the Server Alias text box enter a name for your SQL connection.
> Select TCP/IP under Network libraries
> Enter the IP address of the Server your SQL database is located on, in
> the Server name text box.
> Click on the OK button.
> Your Server alias will now be configured, click on the Apply button.
> Click on the OK button.
>
> Create Connection
> Open SQL Server Enterprise Manager
> When Enterprise Manager opens, right click SQL Server Group and select
> New SQL Server Registration.
> The Register SQL Server wizard will now open.
> Click on the Next button.
>>From the Available Servers drop down menu, select the server alias you
> created earlier.
> Click on the Add button.
> The server should now be listed under Added servers, click on the Next
> button.
> When the next dialog box appears select 'The SQL Server login
> information that was assigned to me by the system administrator' (see
> above).
> Click on the Next button.
> Enter your Login name and Password - this will be used every time you
> connect to your SQL server. Click on the Next button.
> Ensure that 'Add the SQL Server(s) to an existing SQL Server group' is
> selected and 'SQL Server Group' is selected for Group name.
> Click on the Next button.
> When the next dialog box opens you can click on the Finish button.
> Your SQL Connection will now be created.
>
> HTH
> Paul

Connect to Oracle8i Enterprise Edition Release 8.1.7.4.0 - Product

I want to fetch data from Oracle 8i,
so how do I connect with SQL Server 2005?
I want to use the connection in SQL IS, RS & AS and also perhaps using a
Linked Server.
And what do I need to install on my server?
Any good/bad experience out there?
Please help!
Search for
SQL Server 2005 64-bit - Fetch data from Oracle
in microsoft.public.sqlserver.dts
"Olof" wrote:

> I want to fetch data from Oracle 8i,
> so how do I connect with SQL Server 2005?
> I want to use the connection in SQL IS, RS & AS and also perhaps using a
> Linked Server.
> And what do I need to install on my server?
> Any good/bad experience out there?
> Please help!

Connect to Oracle8i Enterprise Edition Release 8.1.7.4.0 - Product

I want to fetch data from Oracle 8i,
so how do I connect with SQL Server 2005?
I want to use the connection in SQL IS, RS & AS and also perhaps using a
Linked Server.
And what do I need to install on my server?
Any good/bad experience out there'
Please help!Search for
SQL Server 2005 64-bit - Fetch data from Oracle
in microsoft.public.sqlserver.dts
"Olof" wrote:

> I want to fetch data from Oracle 8i,
> so how do I connect with SQL Server 2005?
> I want to use the connection in SQL IS, RS & AS and also perhaps using a
> Linked Server.
> And what do I need to install on my server?
> Any good/bad experience out there'
> Please help!

connect to named instance in a cluster

Windows 2003 N+1 cluster, SQL2005 enterprise + sp2
I have a N+1 cluster and installed default sql instance and one named
instance. SQL Browser service is running on the node which owns the named
instance; UDP port 1434 is opened on the firewall.
I had problem connecting to the named instance. Then I found the port number
in the sql error log which the named instance listens on. Opening this port
in firewall solved the connection problem.
My questions:
1. What's the best/secure way to connect to the named instance in a cluster?
Why does it not work with UDP opened and SQL Browser running before the
specific port is opened?
2. Will the port number change when the sql instance restarts? If yes, how
to assign a static port number?
Thanks.
Claudia
The short answer is that the behavior you observed is perfectly normal.
SQL will decide on a port when the service restarts unless it is a default
instance or you have locked SQL to a specific port number.
You can use the SQL Server Configuration Tool to "lock" the instance to a
specific port. This is done whenever a client needs a static port to
connect to.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Claudia" <Claudia@.discussions.microsoft.com> wrote in message
news:17766F0D-BF9B-4DA1-9D1A-126B57E422B4@.microsoft.com...
> Windows 2003 N+1 cluster, SQL2005 enterprise + sp2
> I have a N+1 cluster and installed default sql instance and one named
> instance. SQL Browser service is running on the node which owns the named
> instance; UDP port 1434 is opened on the firewall.
> I had problem connecting to the named instance. Then I found the port
> number
> in the sql error log which the named instance listens on. Opening this
> port
> in firewall solved the connection problem.
> My questions:
> 1. What's the best/secure way to connect to the named instance in a
> cluster?
> Why does it not work with UDP opened and SQL Browser running before the
> specific port is opened?
> 2. Will the port number change when the sql instance restarts? If yes, how
> to assign a static port number?
> Thanks.
> Claudia

Connect to enterprise manager

WIthin out network were all having issues connecting to SQL server, e.g. it
would allows connection when we can intermitadley connect.
Are the any know firewall issues or other known bugs?Hi,
Might be because of slow network, Try executing the below command from your
cleint PC
Ping <SQL Server IP Address> -t
If you get contineous "Request time out", then inform ur system / network
admin.
Thanks
Hari
MCDBA
"Matthew Burgess" <MatthewBurgess@.discussions.microsoft.com> wrote in
message news:E9A0AF8C-618F-4ECC-9775-0427625883B1@.microsoft.com...
> WIthin out network were all having issues connecting to SQL server, e.g.
> it
> would allows connection when we can intermitadley connect.
> Are the any know firewall issues or other known bugs?|||Hari,
Seems as if it could be that. DB on on internal netowrk are fine. But the
problem db is with our hositng compnay: we have a 2 Meg brodband line
(operating a 1.6mbit/sec).
Any suggest of what I can say to our hositng company? I know our IP are in
there firewall, and thus sometimes we can connect; would a firewall with an
ISP tend to stop ping's?
Other options could be our router or our ISP.
THanks for you help on this!
regards
MAtthew.
"Hari Prasad" wrote:
> Hi,
> Might be because of slow network, Try executing the below command from your
> cleint PC
> Ping <SQL Server IP Address> -t
> If you get contineous "Request time out", then inform ur system / network
> admin.
> Thanks
> Hari
> MCDBA
> "Matthew Burgess" <MatthewBurgess@.discussions.microsoft.com> wrote in
> message news:E9A0AF8C-618F-4ECC-9775-0427625883B1@.microsoft.com...
> > WIthin out network were all having issues connecting to SQL server, e.g.
> > it
> > would allows connection when we can intermitadley connect.
> >
> > Are the any know firewall issues or other known bugs?
>
>|||Hi Matthew
If you're trying to ping a server at your ISP, it can very well be that they
don't allow pinging. In most cases pinging is blocked from outside a
firewall - not only on ISP's but also on most other companies.
I'd suggest that you call your ISP and talk to them about this issue because
you'd need to have the proper ports open to get into your SQL server. I
don't know if they will allow this or not, but if not you might be able to
do it via a VPN connection.
Regards
Steen
Matthew Burgess wrote:
> Hari,
> Seems as if it could be that. DB on on internal netowrk are fine. But
> the problem db is with our hositng compnay: we have a 2 Meg brodband
> line (operating a 1.6mbit/sec).
> Any suggest of what I can say to our hositng company? I know our IP
> are in there firewall, and thus sometimes we can connect; would a
> firewall with an ISP tend to stop ping's?
> Other options could be our router or our ISP.
> THanks for you help on this!
> regards
> MAtthew.
> "Hari Prasad" wrote:
>> Hi,
>> Might be because of slow network, Try executing the below command
>> from your cleint PC
>> Ping <SQL Server IP Address> -t
>> If you get contineous "Request time out", then inform ur system /
>> network admin.
>> Thanks
>> Hari
>> MCDBA
>> "Matthew Burgess" <MatthewBurgess@.discussions.microsoft.com> wrote in
>> message news:E9A0AF8C-618F-4ECC-9775-0427625883B1@.microsoft.com...
>> WIthin out network were all having issues connecting to SQL server,
>> e.g. it
>> would allows connection when we can intermitadley connect.
>> Are the any know firewall issues or other known bugs?|||I got a similar problem in my network but in my case the network connection
goes well until the user opens Enterprise Manager and start working. In some
moment the network connection is lost, PINGing the server will not respond.
My network is not a slow one. This problems occurs for more than one user.
Will you please indicate me how you resolved the problem or any workaround
for this? I am almost decided to format that server with all the work that it
implies and its impact on my users
Thanks
César
> Hi Matthew
> If you're trying to ping a server at your ISP, it can very well be that they
> don't allow pinging. In most cases pinging is blocked from outside a
> firewall - not only on ISP's but also on most other companies.
> I'd suggest that you call your ISP and talk to them about this issue because
> you'd need to have the proper ports open to get into your SQL server. I
> don't know if they will allow this or not, but if not you might be able to
> do it via a VPN connection.
> Regards
> Steen
>
> Matthew Burgess wrote:
> > Hari,
> >
> > Seems as if it could be that. DB on on internal netowrk are fine. But
> > the problem db is with our hositng compnay: we have a 2 Meg brodband
> > line (operating a 1.6mbit/sec).
> >
> > Any suggest of what I can say to our hositng company? I know our IP
> > are in there firewall, and thus sometimes we can connect; would a
> > firewall with an ISP tend to stop ping's?
> >
> > Other options could be our router or our ISP.
> >
> > THanks for you help on this!
> >
> > regards
> >
> > MAtthew.
> >
> > "Hari Prasad" wrote:
> >
> >> Hi,
> >>
> >> Might be because of slow network, Try executing the below command
> >> from your cleint PC
> >>
> >> Ping <SQL Server IP Address> -t
> >>
> >> If you get contineous "Request time out", then inform ur system /
> >> network admin.
> >>
> >> Thanks
> >> Hari
> >> MCDBA
> >>
> >> "Matthew Burgess" <MatthewBurgess@.discussions.microsoft.com> wrote in
> >> message news:E9A0AF8C-618F-4ECC-9775-0427625883B1@.microsoft.com...
> >> WIthin out network were all having issues connecting to SQL server,
> >> e.g. it
> >> would allows connection when we can intermitadley connect.
> >>
> >> Are the any know firewall issues or other known bugs?
>
>|||I have a similar problem. The network connection is OK but when the user
enters Enterprise manager and starts working with some DTS, the connection
with the server is lost. PINGing the server do not respond. It happens in
more than one user. I have changed the redundant NIC but it remains the same.
Will you please give me a hint how did you manage to solve it or if you
tried any workaround for this?
"Steen Persson" wrote:
> Hi Matthew
> If you're trying to ping a server at your ISP, it can very well be that they
> don't allow pinging. In most cases pinging is blocked from outside a
> firewall - not only on ISP's but also on most other companies.
> I'd suggest that you call your ISP and talk to them about this issue because
> you'd need to have the proper ports open to get into your SQL server. I
> don't know if they will allow this or not, but if not you might be able to
> do it via a VPN connection.
> Regards
> Steen
>
> Matthew Burgess wrote:
> > Hari,
> >
> > Seems as if it could be that. DB on on internal netowrk are fine. But
> > the problem db is with our hositng compnay: we have a 2 Meg brodband
> > line (operating a 1.6mbit/sec).
> >
> > Any suggest of what I can say to our hositng company? I know our IP
> > are in there firewall, and thus sometimes we can connect; would a
> > firewall with an ISP tend to stop ping's?
> >
> > Other options could be our router or our ISP.
> >
> > THanks for you help on this!
> >
> > regards
> >
> > MAtthew.
> >
> > "Hari Prasad" wrote:
> >
> >> Hi,
> >>
> >> Might be because of slow network, Try executing the below command
> >> from your cleint PC
> >>
> >> Ping <SQL Server IP Address> -t
> >>
> >> If you get contineous "Request time out", then inform ur system /
> >> network admin.
> >>
> >> Thanks
> >> Hari
> >> MCDBA
> >>
> >> "Matthew Burgess" <MatthewBurgess@.discussions.microsoft.com> wrote in
> >> message news:E9A0AF8C-618F-4ECC-9775-0427625883B1@.microsoft.com...
> >> WIthin out network were all having issues connecting to SQL server,
> >> e.g. it
> >> would allows connection when we can intermitadley connect.
> >>
> >> Are the any know firewall issues or other known bugs?
>
>

Connect to enterprise manager

WIthin out network were all having issues connecting to SQL server, e.g. it
would allows connection when we can intermitadley connect.
Are the any know firewall issues or other known bugs?
Hi,
Might be because of slow network, Try executing the below command from your
cleint PC
Ping <SQL Server IP Address> -t
If you get contineous "Request time out", then inform ur system / network
admin.
Thanks
Hari
MCDBA
"Matthew Burgess" <MatthewBurgess@.discussions.microsoft.com> wrote in
message news:E9A0AF8C-618F-4ECC-9775-0427625883B1@.microsoft.com...
> WIthin out network were all having issues connecting to SQL server, e.g.
> it
> would allows connection when we can intermitadley connect.
> Are the any know firewall issues or other known bugs?
|||Hari,
Seems as if it could be that. DB on on internal netowrk are fine. But the
problem db is with our hositng compnay: we have a 2 Meg brodband line
(operating a 1.6mbit/sec).
Any suggest of what I can say to our hositng company? I know our IP are in
there firewall, and thus sometimes we can connect; would a firewall with an
ISP tend to stop ping's?
Other options could be our router or our ISP.
THanks for you help on this!
regards
MAtthew.
"Hari Prasad" wrote:

> Hi,
> Might be because of slow network, Try executing the below command from your
> cleint PC
> Ping <SQL Server IP Address> -t
> If you get contineous "Request time out", then inform ur system / network
> admin.
> Thanks
> Hari
> MCDBA
> "Matthew Burgess" <MatthewBurgess@.discussions.microsoft.com> wrote in
> message news:E9A0AF8C-618F-4ECC-9775-0427625883B1@.microsoft.com...
>
>
|||Hi Matthew
If you're trying to ping a server at your ISP, it can very well be that they
don't allow pinging. In most cases pinging is blocked from outside a
firewall - not only on ISP's but also on most other companies.
I'd suggest that you call your ISP and talk to them about this issue because
you'd need to have the proper ports open to get into your SQL server. I
don't know if they will allow this or not, but if not you might be able to
do it via a VPN connection.
Regards
Steen
Matthew Burgess wrote:[vbcol=seagreen]
> Hari,
> Seems as if it could be that. DB on on internal netowrk are fine. But
> the problem db is with our hositng compnay: we have a 2 Meg brodband
> line (operating a 1.6mbit/sec).
> Any suggest of what I can say to our hositng company? I know our IP
> are in there firewall, and thus sometimes we can connect; would a
> firewall with an ISP tend to stop ping's?
> Other options could be our router or our ISP.
> THanks for you help on this!
> regards
> MAtthew.
> "Hari Prasad" wrote:
|||I got a similar problem in my network but in my case the network connection
goes well until the user opens Enterprise Manager and start working. In some
moment the network connection is lost, PINGing the server will not respond.
My network is not a slow one. This problems occurs for more than one user.
Will you please indicate me how you resolved the problem or any workaround
for this? I am almost decided to format that server with all the work that it
implies and its impact on my users
Thanks
César
> Hi Matthew
> If you're trying to ping a server at your ISP, it can very well be that they
> don't allow pinging. In most cases pinging is blocked from outside a
> firewall - not only on ISP's but also on most other companies.
> I'd suggest that you call your ISP and talk to them about this issue because
> you'd need to have the proper ports open to get into your SQL server. I
> don't know if they will allow this or not, but if not you might be able to
> do it via a VPN connection.
> Regards
> Steen
>
> Matthew Burgess wrote:
>
>
|||I have a similar problem. The network connection is OK but when the user
enters Enterprise manager and starts working with some DTS, the connection
with the server is lost. PINGing the server do not respond. It happens in
more than one user. I have changed the redundant NIC but it remains the same.
Will you please give me a hint how did you manage to solve it or if you
tried any workaround for this?
"Steen Persson" wrote:

> Hi Matthew
> If you're trying to ping a server at your ISP, it can very well be that they
> don't allow pinging. In most cases pinging is blocked from outside a
> firewall - not only on ISP's but also on most other companies.
> I'd suggest that you call your ISP and talk to them about this issue because
> you'd need to have the proper ports open to get into your SQL server. I
> don't know if they will allow this or not, but if not you might be able to
> do it via a VPN connection.
> Regards
> Steen
>
> Matthew Burgess wrote:
>
>

Connect to database without showing the "Connect to Server" dialog box?

Is it possible to configure the SQL Server Management Studio to behave like good old Enterprise Manager, so that it automatically connects to my configured servers without showing the "Connect to Server" dialog box every time upon startup?

After successlessly searching Google and these forums, I still found no suitable answer to this question (maybe beside this one).

Thanks
Uwe

You ae right this is not possible, perhaps you can suggest that as a feature request on connect.microsoft.com ?

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de|||Done:

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=180590

Thanks, Jens .|||You got my vote.

-Jens.|||Strange - they marked the ticket as "closed" and "solved", but no further comments.

Anyone knows what this actually means? IS it already present and I did not found it? Or will it be implemented in a further version?

Thanks
Uwe

connect to cluster server issue

Hi,
I had SQL 2000 client, and tried to register to SQL 7 cluster server in Enterprise Manager. But the registering process hang.
Does anyone know the issue? It happen to other users as well.
Thanks.
yuling
Hi,
Acturally, I tried to connect to SQL 2000 cluster server in Enterprise Manager. But, the process hangs. I am able to register this SQL server from any of my sql server machine. BTW, I can connect by using Query Analyzer without any issue as well. What
's the issue?
Thank you if anyone has this issue. Tks.
Yuling
sqlsql

connect to cluster server issue

Hi,
I had SQL 2000 client, and tried to register to SQL 7 cluster server in Ente
rprise Manager. But the registering process hang.
Does anyone know the issue? It happen to other users as well.
Thanks.
yulingHi,
Acturally, I tried to connect to SQL 2000 cluster server in Enterprise Manag
er. But, the process hangs. I am able to register this SQL server from any
of my sql server machine. BTW, I can connect by using Query Analyzer witho
ut any issue as well. What
's the issue?
Thank you if anyone has this issue. Tks.
Yuling

Connect to Analysis Manager over HTTPS and non domain account

Please, I need your help... I`m desperate...

I`m trying to connect to the Analysis Services (AS 2000 Enterprise Edition SP4 on Windows Server 2003 EE, respository is in Access DB) throught Analysis Manager over HTTPS(HTTP) connection. I dont want to use domain account.

I need to specify USER_ID and PASSWORD to the Analysis Manager, but in registration of new server is only IP address or HTTP adress (for http://server) - but it doesnt work - it says Unauthorized. But I`ve tried to use Anonymous account and it doesn`t work (client wan`t able to make connection)... I would like to use Basic Authentification... Thise account is member of OLAP_Administrators... but the problem is where should I put USER_ID and PASSWORD?

It works perfect in Excel 2003... MSOLAP.asp work fine in IE...

Thanks very much for your advise

RicmondIs it due to "BUG: Analysis Manager Does Not Support HTTP or HTTPS onnections"

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q311310

Ricmond

Connect to a remote SQL Server

How can I connect to a online SQL Server with Enterprise Manager?just specify the IP addrss or DNS name in your 'new SQL Server registration' properties.

I used to do this all the time till recently when we discovered that EM uses a hell of a lot of network chatter between client and server, which seemed to cause trouble with our router. now we connect to the server with terminal services and use the local EM. You might be OK though.

It also requires that the remote SQL Server is not hiding behind a firewall, as a large number are (more since the slammer worm, actually)|||Another handy way to do it, particularly if you've just got the IP address but would rather use a name, is to create an alias using the Sql Server Client Network Utility:

1. Click Start->Programs->Microsoft Sql Server->Client Network Utility
2. Select the Alias tab and click the Add button.
3. Provide the Server alias name in the top text box. This will be the name you will eventually see in Enterprise Manager.
4. In the Network libraries radio box select TCP/IP (which is probably what you want).
5. For the Server Name enter the IP address of the server to which you're trying to connect.
6. Click OK.
7. Go back to Enteprise Manager and select "New Sql Server Registration". For the server click the "..." button and you should see the Alias on the list. Select it and continue with the registration (passwords and so on).|||Thank you... :)

I already obtained the connection to the server.

connect the SQL Server in different domains

HI ALL
I have tow domains, in the same forest. From one domain, which has a SQL Ser
ver A , I want to use the Enterprise manager or the Query Analyzer to connec
t the SQL Server B in the other domain and vise versa. Could any one elabora
te all the method to do tha
t.
thank you very much.I'm assuming this is more than just opening Query Analyzer and connecting to
a server name. What you probably want to do is add a linked server -- go to
SQL Enterprise Manager and add a new linked server under the security
section. That will let you run queries such as
select * from serverb.<database>.<owner>.<table>
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"ALLEN" <anonymous@.discussions.microsoft.com> wrote in message
news:3F57F4DF-7BB7-4C66-A362-5C112F850ABE@.microsoft.com...
> HI ALL
> I have tow domains, in the same forest. From one domain, which has a SQL
Server A , I want to use the Enterprise manager or the Query Analyzer to
connect the SQL Server B in the other domain and vise versa. Could any one
elaborate all the method to do that.
> thank you very much.|||You should not find any difference in normal connectivity, but there is one
thing that you might want to be aware of in this particular scenario. If you
want to use Kerberos Authenticatin then you will have to register an SPN for
the SQL Server using NETBIOS name.
Generally SPN should be registered in the following format
MSSQLSvc/sqlmachine.domain.net:1433 sqlserviceact
But to enable Kerberos protocol in this inter domain scenario, you will also
need to register an SPN using the NETBIOS name
MSSQLSvc/sqlmachine:1433 sqlserviceact
Thanks,
Bala.
This posting is provided "AS IS" with no warranties, and confers no
rights.
"ALLEN" <anonymous@.discussions.microsoft.com> wrote in message
news:3F57F4DF-7BB7-4C66-A362-5C112F850ABE@.microsoft.com...
> HI ALL
> I have tow domains, in the same forest. From one domain, which has a SQL
Server A , I want to use the Enterprise manager or the Query Analyzer to
connect the SQL Server B in the other domain and vise versa. Could any one
elaborate all the method to do that.
> thank you very much.

Connect at only One port

When connecting to sql 2000 Enterprise manager opens multiple ports.
For example
Proto Local Address Foreign Address State
TCP 192.168.7.12:1433 192.168.7.12:3275 ESTABLISHED
TCP 192.168.7.12:1433 192.168.7.12:3634 ESTABLISHED
TCP 192.168.7.12:3634 192.168.7.12:1433 ESTABLISHED
How can I force sql to connect only at 1433 or other single port. I facts
is there such posibility?
Hi -
If you analyze the entries in the SQL Server error log file, you can verify
that the instance of SQL Server is listening on the correct IP address and on
the correct port. By default, a default instance of SQL Server listens on the
port 1433. You can also use Server Network Utility to verify the protocol
settings for SQL Server and to change the properties in SQL Server, including
the protocols that can connect to SQL Server and the ports that can be used.
For more information about using Server Network Utility, see the "SQL Server
Network Utility" topic in SQL Server Books Online.
Sometimes, SQL Server 2000 may not bind to port 1433 or any other specified
port. This problem may occur if the port is being used by another application
or if you are trying to connect by using an IP address that is not correct.
Therefore, the TCP/IP connections to SQL Server may not be successful and you
may receive the following error message in the SQL Server error log file:
2001-11-14 15:49:14.12 server SuperSocket Info: Bind failed on TCP port 1433.
Please check the below link :
http://support.microsoft.com/default.aspx?kbid=307197
Let me know if it helps you.
"Radin" wrote:

> When connecting to sql 2000 Enterprise manager opens multiple ports.
> For example
> Proto Local Address Foreign Address State
> TCP 192.168.7.12:1433 192.168.7.12:3275 ESTABLISHED
> TCP 192.168.7.12:1433 192.168.7.12:3634 ESTABLISHED
> TCP 192.168.7.12:3634 192.168.7.12:1433 ESTABLISHED
> How can I force sql to connect only at 1433 or other single port. I facts
> is there such posibility?
>

Connect at only One port

When connecting to sql 2000 Enterprise manager opens multiple ports.
For example
Proto Local Address Foreign Address State
TCP 192.168.7.12:1433 192.168.7.12:3275 ESTABLISHED
TCP 192.168.7.12:1433 192.168.7.12:3634 ESTABLISHED
TCP 192.168.7.12:3634 192.168.7.12:1433 ESTABLISHED
How can I force sql to connect only at 1433 or other single port. I facts
is there such posibility?Hi -
If you analyze the entries in the SQL Server error log file, you can verify
that the instance of SQL Server is listening on the correct IP address and o
n
the correct port. By default, a default instance of SQL Server listens on th
e
port 1433. You can also use Server Network Utility to verify the protocol
settings for SQL Server and to change the properties in SQL Server, includin
g
the protocols that can connect to SQL Server and the ports that can be used.
For more information about using Server Network Utility, see the "SQL Server
Network Utility" topic in SQL Server Books Online.
Sometimes, SQL Server 2000 may not bind to port 1433 or any other specified
port. This problem may occur if the port is being used by another applicatio
n
or if you are trying to connect by using an IP address that is not correct.
Therefore, the TCP/IP connections to SQL Server may not be successful and yo
u
may receive the following error message in the SQL Server error log file:
2001-11-14 15:49:14.12 server SuperSocket Info: Bind failed on TCP port 1433
.
Please check the below link :
http://support.microsoft.com/default.aspx?kbid=307197
Let me know if it helps you.
"Radin" wrote:

> When connecting to sql 2000 Enterprise manager opens multiple ports.
> For example
> Proto Local Address Foreign Address State
> TCP 192.168.7.12:1433 192.168.7.12:3275 ESTABLISHED
> TCP 192.168.7.12:1433 192.168.7.12:3634 ESTABLISHED
> TCP 192.168.7.12:3634 192.168.7.12:1433 ESTABLISHED
> How can I force sql to connect only at 1433 or other single port. I facts
> is there such posibility?
>

Connect across Internet through NAT router

I am attempting to use Enterprise Manager to connect to SS 2000 across the
Internet. The machine running SQL Server is behind a NAT router.
Enterprise manager shows that the TCP/IP port that SQL Server is using is
1061. I have forwared port 1061 on the router to the machine running SQL
Server. When I attempt to register the server in Enterprise Manager I use
the WAN IP address of the router as the server name. However, registration
fails with the message "SQL Server does not exist or access denied."
What am I doing wrong?
Bill ToddI found an article in BOL saying that UDP port 1434 must also be
forwarded, however, doing so did not help.
Bill Todd

Connect across Internet through NAT router

I am attempting to use Enterprise Manager to connect to SS 2000 across the
Internet. The machine running SQL Server is behind a NAT router.
Enterprise manager shows that the TCP/IP port that SQL Server is using is
1061. I have forwared port 1061 on the router to the machine running SQL
Server. When I attempt to register the server in Enterprise Manager I use
the WAN IP address of the router as the server name. However, registration
fails with the message "SQL Server does not exist or access denied."
What am I doing wrong?
Bill Todd
I found an article in BOL saying that UDP port 1434 must also be
forwarded, however, doing so did not help.
Bill Todd

Confusing arithmetic overflow error

I have a numeric column whoose precision is 7 and scale is 3.
My first question is how come the length is reported as 5 in Enterprise
Managaer?
Secondly, whilst trying to update values in these columns I get
Server: Msg 8115, Level 16, State 8, Line 1
Arithmetic overflow error converting numeric to data type numeric.
The statement has been terminated.
...for values such as -16942.18, -16939.59, 16935.46, 16939.59. Surely, any
of these values should fit nicely into my defined data type? Why is this
occuring?
--
Cheers,
elzikoThe length is reported as 5 because that's the number of bytes that the
datatype occupies.
Precision 7, scale 3 = XXXX.YYY
4 digits to the left of the decimal point, 3 to the right.
-16942.18 has 5 to the left, 2 to the right. That's why it's failing.
"elziko" <elziko@.NOTSPAMMINGyahoo.co.uk> wrote in message
news:OC9W741jEHA.592@.TK2MSFTNGP11.phx.gbl...
> I have a numeric column whoose precision is 7 and scale is 3.
> My first question is how come the length is reported as 5 in Enterprise
> Managaer?
> Secondly, whilst trying to update values in these columns I get
> Server: Msg 8115, Level 16, State 8, Line 1
> Arithmetic overflow error converting numeric to data type numeric.
> The statement has been terminated.
> ...for values such as -16942.18, -16939.59, 16935.46, 16939.59. Surely,
any
> of these values should fit nicely into my defined data type? Why is this
> occuring?
> --
> Cheers,
> elziko
>|||Oh it appears I counted four to the left... stupid me! Sorry & thanks!|||If you read in BOL (decimal and numeric) there is a table that specifies how
many bytes to store numeric data based on the precision.
As for your overflow this is occurring, because you ask for 3 digits to the
right of the decimal point to be stored (scale), but the total length of the
the number to only be 7 digits long (precision). Therefore the numbers you
are trying to use really have 8 digit precision (i.e -16942.18, is
really -16942.180).
--
----
----
-
Need SQL Server Examples check out my website
http://www.geocities.com/sqlserverexamples
"elziko" <elziko@.NOTSPAMMINGyahoo.co.uk> wrote in message
news:OC9W741jEHA.592@.TK2MSFTNGP11.phx.gbl...
> I have a numeric column whoose precision is 7 and scale is 3.
> My first question is how come the length is reported as 5 in Enterprise
> Managaer?
> Secondly, whilst trying to update values in these columns I get
> Server: Msg 8115, Level 16, State 8, Line 1
> Arithmetic overflow error converting numeric to data type numeric.
> The statement has been terminated.
> ...for values such as -16942.18, -16939.59, 16935.46, 16939.59. Surely,
any
> of these values should fit nicely into my defined data type? Why is this
> occuring?
> --
> Cheers,
> elziko
>

Conflict Resolution options disabled

I am using SQL Server 2000 and Enterprise Manager. I have a publication and
I am trying to follow some instructions for configuring conflict resolution.
I open the Publication properties, go to the Articles tab, open an Article by
clicking the ellipses, and then go to the Resolver tab. All of the controls
on the Resolver tab are disabled. Is there something else I must do first to
enable conflict resolution on at the Database or Publication level?
Some settings are database specific. Most likely what has happened is the
article you are trying to change the resolver type to is published in a
different publication. To make this work you will have to drop it from
existing publication, change the resolver type and then put it back in.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Michael" <Michael@.discussions.microsoft.com> wrote in message
news:454325A9-2D83-4664-9ECB-9143C5257BDF@.microsoft.com...
>I am using SQL Server 2000 and Enterprise Manager. I have a publication
>and
> I am trying to follow some instructions for configuring conflict
> resolution.
> I open the Publication properties, go to the Articles tab, open an Article
> by
> clicking the ellipses, and then go to the Resolver tab. All of the
> controls
> on the Resolver tab are disabled. Is there something else I must do first
> to
> enable conflict resolution on at the Database or Publication level?