Remove and Add SQL 2005 cluster nodes CHALLENGE!!!

I have a challenge!!!!!!!!!!!
Requirements are:
A. To replace the 2 nodes of SQL 2005 Cluster on Windows 2003 SP1, with a
set of 2 new nodes (hardware).
B. Keep all the settings of SQL 2005, Databases, .etc. the same way they
are.
C. WITH THE SAME IP ADDRESSES (no change to any IP address).
I know the theory is to implement this KB:
http://msdn2.microsoft.com/en-us/library/ms191545.aspx
My question is:
Can I do the following?
1. Remove the second OLD node, using the same ms191545 above.
2. Add (Join) the 1st New node to the cluster.
3. Remove the last OLD node.
4. Add the NEW second node.
Are the above steps feasible?
What are the things I have to be aware about (so I will not break anything).
How can get thru having the same IP addresses with no change on the 2 new
nodes?
Thanks in advance
wit1 wrote:
> I have a challenge!!!!!!!!!!!
> Requirements are:
> A. To replace the 2 nodes of SQL 2005 Cluster on Windows 2003 SP1, with a
> set of 2 new nodes (hardware).
> B. Keep all the settings of SQL 2005, Databases, .etc. the same way they
> are.
> C. WITH THE SAME IP ADDRESSES (no change to any IP address).
Maybe I'm missing something in your 3rd requirement. When you specify
"same IP address," it implies that your requirement is referring to the
cluster _node_, not a cluster group being hosted by the cluster. Why is
that, and what difference does it make?
As the cluster group is moved from one node to another during failure or
intentional move, there should be an IP address for that group that is
separate and unique from the node(s) that own it.
|||I meant that if node 2 (for example) has IP addresses of
1.2.3.4 for the Virtual IP (Cluster group IP)
2.3.4.5 for public (for the NODE itself not the Virtual IP),
and
1.1.1.1 for private (heart beat)
, the new (coming node) that will replace that node 2 should have the same
IP addresses.
So the plan is to un-install SQL from node 2, then evict it, after that join
the NEW node 2 and install SQL with same IP addresses.
Hope that clears things out.
"horseradish" <millardjk@.gmail.com> wrote in message
news:%237hk1iojHHA.5084@.TK2MSFTNGP03.phx.gbl...[vbcol=seagreen]
> wit1 wrote:
with a[vbcol=seagreen]
they
> Maybe I'm missing something in your 3rd requirement. When you specify
> "same IP address," it implies that your requirement is referring to the
> cluster _node_, not a cluster group being hosted by the cluster. Why is
> that, and what difference does it make?
> As the cluster group is moved from one node to another during failure or
> intentional move, there should be an IP address for that group that is
> separate and unique from the node(s) that own it.

Remoting timeout when calling SSIS package execute from a windows service

When running an integration services package from a windows service I get the "Object ... has been disconnected or does not exist at the server." exception after aproximately six minutes of execution.

This is *not* my windows service failing. I can loop indefinately while tracing to a log file within the service and it will run forever. While calling the mypackage.execute(...) method however, after six minutes (give or take) the exception is thrown...

my code looks something like this:
<code>
dim foo as Microsoft.SqlServer.Dts.Runtime.Application
mypackage = foo..LoadPackage(strimportPkgFilename, pkgevents)
results = myPackage.Execute(Nothing, Nothing, pkgevents, Nothing, Nothing)
</code>

<error>
A first chance exception of type 'System.Runtime.Remoting.RemotingException' occurred in mscorlib.dll
Exception in: frmMyForm.DoImports
Message: Object '/b76f98a0_5bd9_49d8_a524_eeb49d55b303/bqbhkjnaofq_ifr_cwz+srid_1.rem' has been disconnected or does not exist at the server.
</error>

oddly, this same code works perfectly if I run it within a windows form application no matter how long it takes.

It also runs fine if the package can complete in under six minutes.

Any suggestions?

Mark

To give a little update, I'm still having this problem despite exhausting works around I've come up with.

* I've threaded the call to package.Execute, checking its status in a while loop every 60 seconds until it finishes. Still encounter the exception. This behaves as though it should work. The status and execution appear to work asynchronously.

* I've threaded the call to my service, calling my own status function which tests the status of shared MyPackage, every 60 seconds. Still encounter the remoting exception after ~6 minutes.

Every piece is busy making requests through the whole chain of accessible interactions frequently enough to maintain all known remoting timeout constraints and the problem persists.

It confuses me why the same code works in a windows form, but does not work in a windows service. The exception is defiantly being thrown from within package.Execute. I can loop indefinitely within the service without calling package Execute. I can also catch and disregard the exception and still provide status to the client within the service.

Looking for suggestions...

|||

SSIS does not use remoting. The exception is caused by remoting however, so you need to find out who introduced remoting? My ideas

1) you use remoting as link between client and server - then the exception is between the client and the service, which does not fit with the statement that it is thrown from within package.Execute and you can catch this exception (but did you try?)

2) you create multiple application domains in the service - if you do this, make sure you only use SSIS from default application domain. If you run the package from non-default application domain, some SSIS objects can be created in that app domain, but some in default app domain (a lot of SSIS is native code, and it is not aware of app-domains), which may cause failures like this one.

Remoting timeout when calling SSIS package execute from a windows service

When running an integration services package from a windows service I get the "Object ... has been disconnected or does not exist at the server." exception after aproximately six minutes of execution.

This is *not* my windows service failing. I can loop indefinately while tracing to a log file within the service and it will run forever. While calling the mypackage.execute(...) method however, after six minutes (give or take) the exception is thrown...

my code looks something like this:
<code>
dim foo as Microsoft.SqlServer.Dts.Runtime.Application
mypackage = foo..LoadPackage(strimportPkgFilename, pkgevents)
results = myPackage.Execute(Nothing, Nothing, pkgevents, Nothing, Nothing)
</code>

<error>
A first chance exception of type 'System.Runtime.Remoting.RemotingException' occurred in mscorlib.dll
Exception in: frmMyForm.DoImports
Message: Object '/b76f98a0_5bd9_49d8_a524_eeb49d55b303/bqbhkjnaofq_ifr_cwz+srid_1.rem' has been disconnected or does not exist at the server.
</error>

oddly, this same code works perfectly if I run it within a windows form application no matter how long it takes.

It also runs fine if the package can complete in under six minutes.

Any suggestions?

Mark

To give a little update, I'm still having this problem despite exhausting works around I've come up with.

* I've threaded the call to package.Execute, checking its status in a while loop every 60 seconds until it finishes. Still encounter the exception. This behaves as though it should work. The status and execution appear to work asynchronously.

* I've threaded the call to my service, calling my own status function which tests the status of shared MyPackage, every 60 seconds. Still encounter the remoting exception after ~6 minutes.

Every piece is busy making requests through the whole chain of accessible interactions frequently enough to maintain all known remoting timeout constraints and the problem persists.

It confuses me why the same code works in a windows form, but does not work in a windows service. The exception is defiantly being thrown from within package.Execute. I can loop indefinitely within the service without calling package Execute. I can also catch and disregard the exception and still provide status to the client within the service.

Looking for suggestions...

|||

SSIS does not use remoting. The exception is caused by remoting however, so you need to find out who introduced remoting? My ideas

1) you use remoting as link between client and server - then the exception is between the client and the service, which does not fit with the statement that it is thrown from within package.Execute and you can catch this exception (but did you try?)

2) you create multiple application domains in the service - if you do this, make sure you only use SSIS from default application domain. If you run the package from non-default application domain, some SSIS objects can be created in that app domain, but some in default app domain (a lot of SSIS is native code, and it is not aware of app-domains), which may cause failures like this one.

Remotely Register SQL Server 2005 Express in Enterprise Manager

I have SQL Server 2005 Express installed on a windows server 2003 standard edition. I have configured the windows firewall to allow exceptions for sqlservr.exe and sqlbrowser.exe. I have enabled remote and local connections using tcp/ip & Named Pipes through the Sql Server Surface Area Connection utility. I am able to telnet into the server with: telnet <server ip> <1433>.

Here is the strange part: I am able to connect to the Sql Server remotely from a development machine via Sql Server Management Studio Express, but I am unable to connect to the Sql Server from the same development machine by registering it in Sql Server Enterprise Manager...Is it possible to register SQL Express through Enterprise Manager?

When registering the SQL Express DB in Enterprise Manager I tried both just the (IP Address) of the server and the (IP Address\SQLExpress) as the server/host but I am getting the following errors from enterprise manager:

Just the (IP Address) as the server/host:

Invalid Connection.

ConnectionOpen( Invalid Instance())

(IP Address\SQLEXPRESS) as the server/host:

Sql Server does not exist or access denied. ConnectOpen(Connect()).

Any idea why I can’t register/mount the instance remotely in Enterprise Manager

but I can in Sql Server Management Studio Express?

Thanks,

Greg

You can not use the Enterprise management tools with sql 2005, it is only for sql 2000 and below. The connection layer and management objects are different, but the SQL 2005 Management tools can read the lower version systems. Doing this you will notice that some functions can not be completed on the lower versions due to the differences in connections. For example you can not create a new maintenance plan in the sql 2005 tools to work on sql 2000, but you can edit it after it has been created using the old sql enterprise manager.

Remotely Register SQL Server 2005 Express in Enterprise Manager

I have SQL Server 2005 Express installed on a windows server 2003 standard edition. I have configured the windows firewall to allow exceptions for sqlservr.exe and sqlbrowser.exe. I have enabled remote and local connections using tcp/ip & Named Pipes through the Sql Server Surface Area Connection utility. I am able to telnet into the server with: telnet <server ip> <1433>.

Here is the strange part: I am able to connect to the Sql Server remotely from a development machine via Sql Server Management Studio Express, but I am unable to connect to the Sql Server from the same development machine by registering it in Sql Server Enterprise Manager...Is it possible to register SQL Express through Enterprise Manager?

When registering the SQL Express DB in Enterprise Manager I tried both just the (IP Address) of the server and the (IP Address\SQLExpress) as the server/host but I am getting the following errors from enterprise manager:

Just the (IP Address) as the server/host:

Invalid Connection.

ConnectionOpen( Invalid Instance())

(IP Address\SQLEXPRESS) as the server/host:

Sql Server does not exist or access denied. ConnectOpen(Connect()).

Any idea why I can’t register/mount the instance remotely in Enterprise Manager

but I can in Sql Server Management Studio Express?

Thanks,

Greg

You will not be able to register a sql2k5 on EM. EM uses sql2k dmo which can't be used to manage sql2k5.

You will have to use sql2k5 mgmt tool to manage sqlexpress/sql2k5 instances.|||

Hi OJ,

Thanks for the reply, I was afraid this was going to be the case. Well so here is the follow up to my question.

I am using Sql Server Management Studio Express (SSMSE)...so will I be able to connect/register a sql2k server to SSMSE?

Basically I want to export the data from my sql2K DB into my sql2k5 express DB so will I be able to do that with SSMSE or will I need the full version of Sql Server Management Studio?

Thanks,

Greg

|||I haven't explicitly looked at ssmse. However, I believe it uses smo. Thus, it's capable to connecting to sql2k and manage it.sql

Remotely Connect to MSDE

Hi
I just installed MSDE over my Windows 2003 box and facing an small problem.
I installed it with SQL security mode and also set a password for user "sa".
Everything looks just fine using "osql" as it uses local address.
But I can't connect to my server from another computer using VS.NET Server Explorer.
It seems as MSDE is set to reject connections from outside by default.
My question is how to enable it so I can connect using my "sa" account.
Appreciate your help in advance.OK. are you trying to connect by IP address or server name? do you have a firewall installed?|||Since I am connecting from outside of the server, I am using IP address.
And also I don't have any firewall installed.|||at a guess I'd say you have only windows authentication enabled. not 100% sure how to change that in MSDE, but I'll scout around and see.

remote webwork place

We have a SBS2003 server. And configured remote workplace to allow remote users

access to their workstion. On the windows XP Pro sp2 station I have added the user to the "Remote desktop" list ( control panel-system-remote-allow users to remotely connect this computer - Add .)

Nomal users can pass router and select wanted station then get logon screen. But this error message is showed up:

"The local policy of this system does not permit you to logon interractively."

The administrator can logon to any station remotely. Do I have to give additional permission to normal user?

Thank you for any help or clue.

Peter

THis seems more a Windows problem than a SQL Server (Express) problem. You might try reaching someone on the public newsgroups covering SBS 2003.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

Hi Peter,

Control Panel -> Administrative Tools -> Local Security Policy -> Local Policy -> User Rights Assignments -> Log On Locally

@. here you have to add the Domain Users you wish to grant log on to your system (Remote Server)

Regards

Hemantgiri S. Goswami

|||

Hemantgiri,

Thank you very much. It solved my problem.

Peter

Remote Setup on cluster node fail

Hi,

I've tried to install SQL Server 2005 September CTP as the first named instance on a Windows Server 2003 Enterprise Edition Cluster.

During the setup process a scheduled task is created on the second cluster node, but this task is not able to run.

I received this error message in the scheduled task log file:
0x80070005: Access is denied

The user account I'm using to install SQL Server is member of the administrator on all cluster nodes, it has also the permission to log on as a service and as a batch job. The user is also permitted to access the computer from the network.

Thanks in advance for the help!

Regards,
ClausThis might be caused by a known Windows bug. Task Scheduler service fails to launch setup on a remote node even if Task Scheduler is running. If someone is logged into remote node, they risk of hitting this Windows bug. Thefore log off any Terminal Server sessions from all remote nodes before you start setup. |||Hi Yim,

Yes! That's it - i logged of from the second cluster node and the installation completes successful!

Thanks a lot!

Remote server

Here is a scenario what i want to do:
I have SQL 2000 server on windows 2000 server in two
different locations. I want to setup the local server to
copy the data to the remote server every 30 minutes or
so. In case the local server is down, i want to redirect
users to the other database server. Which way to go
either log shipping or replication? or any othere
suggestion? maybe third party tools.
Thank you.>--Original Message--
>Here is a scenario what i want to do:
>I have SQL 2000 server on windows 2000 server in two
>different locations. I want to setup the local server
to
>copy the data to the remote server every 30 minutes or
>so. In case the local server is down, i want to redirect
>users to the other database server. Which way to go
>either log shipping or replication? or any othere
>suggestion? maybe third party tools.
>Thank you.
1. You can use Double-Take for real-time replication and
failover reasons (when first server is down the
second "take" the ip address and is coming up).
2. Log shipping + scripts. Script must detect if first
server is down and change the ip address of the second
server
Cezar|||I'd be extremely careful with automatically switching the clients to the
warm standby server maintained via log shipping. Unless you carefully wire a
lot of automated and robust checks to ensure that all conditions are in
place as you have agreed with the business, it's too dangerous to let it
happen automatically.
I myself have never recommended or allowed any automatic switch to a warm
standby server. Nor have I heard anybody doing it in a serious production
environment. (I have a feeling that I might just hear from somebody here :-)
--
Linchi Shea
linchi_shea@.NOSPAMml.com
"cezar" <cezar_gheorghe@.hotmail.com> wrote in message
news:0a6601c3817b$e0338860$a401280a@.phx.gbl...
> >--Original Message--
> >Here is a scenario what i want to do:
> >
> >I have SQL 2000 server on windows 2000 server in two
> >different locations. I want to setup the local server
> to
> >copy the data to the remote server every 30 minutes or
> >so. In case the local server is down, i want to redirect
> >users to the other database server. Which way to go
> >either log shipping or replication? or any othere
> >suggestion? maybe third party tools.
> >
> >Thank you.
> 1. You can use Double-Take for real-time replication and
> failover reasons (when first server is down the
> second "take" the ip address and is coming up).
> 2. Log shipping + scripts. Script must detect if first
> server is down and change the ip address of the second
> server
> Cezar

Remote logins for SQL 2000?

Hi all,
A company recently came in and setup SQL 2000 standard edition on our
Windows 2003 server. I've noticed that the password they setup for the SQL
user they created is not very secure. I am new to SQL, and I was wondering
if there is a way to remotely login to it? If not, I'll probably keep the
password the same, but if there is a way to log in remotely, I will
definately have to change it.
The user they created can be found under the Users section of the database
they setup and has the following access:
public
db_datareader
db_datawriterHi
Is it Window Authetntication or Mixed?
> Windows 2003 server. I've noticed that the password they setup for the
> SQL
> user they created is not very secure.
They created logins first to SQL Server and then added them to the database
"supersonic_oasis" <supersonicoasis@.discussions.microsoft.com> wrote in
message news:C9FE03CC-EF5A-414E-A103-B14F50EB13AB@.microsoft.com...
> Hi all,
> A company recently came in and setup SQL 2000 standard edition on our
> Windows 2003 server. I've noticed that the password they setup for the
> SQL
> user they created is not very secure. I am new to SQL, and I was
> wondering
> if there is a way to remotely login to it? If not, I'll probably keep the
> password the same, but if there is a way to log in remotely, I will
> definately have to change it.
> The user they created can be found under the Users section of the database
> they setup and has the following access:
> public
> db_datareader
> db_datawriter|||Yes you can remotely log into it, subject to various network security
issues of course.
J.
On Mon, 1 May 2006 04:22:01 -0700, supersonic_oasis
<supersonicoasis@.discussions.microsoft.com> wrote:
>Hi all,
>A company recently came in and setup SQL 2000 standard edition on our
>Windows 2003 server. I've noticed that the password they setup for the SQL
>user they created is not very secure. I am new to SQL, and I was wondering
>if there is a way to remotely login to it? If not, I'll probably keep the
>password the same, but if there is a way to log in remotely, I will
>definately have to change it.
>The user they created can be found under the Users section of the database
>they setup and has the following access:
>public
>db_datareader
>db_datawriter

Remote DB - best practices?

We have an application requirement that calls for a local running Windows
Froms application that will need to be connected to a central database over
the internet. Data volumes will be small but latency is a concern. My
first thought is to simply have a connectionstring to the remote db.
Another thought is to connect via web services. I'm thinking that WCF or
Remoting would be too much work.
Anyway, what is the best way? From a development standpoint? From an
operational durability standpoint?
Thanks,
TI think querying your databases using stored procedures via web services is
a good and secure way.
--
Ekrem Önsoy
"Tina" <TinaMSeaburn@.nospamexcite.com> wrote in message
news:exL3RCRBIHA.4836@.TK2MSFTNGP06.phx.gbl...
> We have an application requirement that calls for a local running Windows
> Froms application that will need to be connected to a central database
> over the internet. Data volumes will be small but latency is a concern.
> My first thought is to simply have a connectionstring to the remote db.
> Another thought is to connect via web services. I'm thinking that WCF or
> Remoting would be too much work.
> Anyway, what is the best way? From a development standpoint? From an
> operational durability standpoint?
> Thanks,
> T
>

remote database connection

Hello,

My database stays in a remote site and I have access it through VPN. I would like connect my current Windows based Asp.Net application with this database. What are my options? Can I connect remote database with SqlDataAdaper, will that be slow? Should I sue Web Services to connect database?

If you can Ping the database server from the server running the ASP.NET code, you should be able to connect the exact same way as you can connect to a machine right next to your machine. The speed or slowness depends upon exactly what you are doing. It is likely that using the standard SqlClient classes will be faster and easier than trying to do it using a Web Service.

Remote Connection to SSIS

Hello.

I am trying to remotely connect to SSIS from my PC using windows authentication in SQL mgmt studio and I keep getting the following error message:

Cannot connect to <server>

Additional Information:

Failed to retrieve date for this request. (Microsoft.SqlServer.SmoEnum)

Connect to SSIS service on machine "<server>" failed: The RPC server is unavailable.

I do not get the same error when I connect to the database engine, just SSIS. I don't have a firewall inbetween the machines either so it can't be that.

Has anyone else had a similar problem? if so, I would be grateful if you can you tell me how you got around it

Thanks

See this thread where I answered a similar question regarding not being able to connect to SSIS from Management Studio, I'm assuming this may be your problem:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=254204&SiteID=1

HTH

|||

I get the same RPC error, but one of my co-workers doesn't get the error, and he can connect to SSIS from his desktop, but I cannot. I assume I don't need to change the .i' GAD 0l3/2e3/2 006o Rn the server since he has no problem connecting.

Any other ideas ?

Remote Connection to SSIS

Hello.

I am trying to remotely connect to SSIS from my PC using windows authentication in SQL mgmt studio and I keep getting the following error message:

Cannot connect to <server>

Additional Information:

Failed to retrieve date for this request. (Microsoft.SqlServer.SmoEnum)

Connect to SSIS service on machine "<server>" failed: The RPC server is unavailable.

I do not get the same error when I connect to the database engine, just SSIS. I don't have a firewall inbetween the machines either so it can't be that.

Has anyone else had a similar problem? if so, I would be grateful if you can you tell me how you got around it

Thanks

See this thread where I answered a similar question regarding not being able to connect to SSIS from Management Studio, I'm assuming this may be your problem:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=254204&SiteID=1

HTH

|||

I get the same RPC error, but one of my co-workers doesn't get the error, and he can connect to SSIS from his desktop, but I cannot. I assume I don't need to change the .i' GAD 0l3/2e3/2 006o Rn the server since he has no problem connecting.

Any other ideas ?

Remote connection to SqlServer

Hello Guys
We are developing a CRM application using Delphi Front end &
Sqlserver as back end which is
residing on Windows 2000 server. I need a best possible solution,
if this CRM app fornt end is installed in different Location and
making connection to the Sqlserver which is altogether in different site...
Thanks
Chandru
There is usually no problem at all using the OLEDB SQL-Server driver over
the internet if the port 1433 is not blocked by a firewall or if you are
able to setup a proxy server. The transport layer will be totally
transparent to your application.
S. L.
"Chandru" <chandru@.knigthoodcorporate.com> wrote in message
news:%23OnHId0xEHA.1168@.TK2MSFTNGP10.phx.gbl...
> Hello Guys
> We are developing a CRM application using Delphi Front end &
> Sqlserver as back end which is
> residing on Windows 2000 server. I need a best possible solution,
> if this CRM app fornt end is installed in different Location and
> making connection to the Sqlserver which is altogether in different
> site...
>
> Thanks
> Chandru
>
>
>

Remote connection to SqlServer

Hello Guys
We are developing a CRM application using Delphi Front end &
Sqlserver as back end which is
residing on Windows 2000 server. I need a best possible solution,
if this CRM app fornt end is installed in different Location and
making connection to the Sqlserver which is altogether in different site...
Thanks
ChandruThere is usually no problem at all using the OLEDB SQL-Server driver over
the internet if the port 1433 is not blocked by a firewall or if you are
able to setup a proxy server. The transport layer will be totally
transparent to your application.
S. L.
"Chandru" <chandru@.knigthoodcorporate.com> wrote in message
news:%23OnHId0xEHA.1168@.TK2MSFTNGP10.phx.gbl...
> Hello Guys
> We are developing a CRM application using Delphi Front end &
> Sqlserver as back end which is
> residing on Windows 2000 server. I need a best possible solution,
> if this CRM app fornt end is installed in different Location and
> making connection to the Sqlserver which is altogether in different
> site...
>
> Thanks
> Chandru
>
>
>

remote connection to sql server express

I have installed SQL server 2005 express on my main server.

It has been installed with windows authentication.

I can use sqlcmd -S machinename\instancename to connect to the server, but when I try to connect from another machine on my lan, I get the error about user not part of trusted sql connection msg 18452 level 14 state 1

I have tried using a windows username and password from my server to access it but that fails also.

Any help would be appreciated

Hi,

I don′t know if you specified the Windows username and password , because you can′t specify this within SQLCMD; if you use Username and password with SQLCMD you always switch to SQL Server authentication which can be not allowed on the server. If you want to use Windows authewntication, you have to log on as the appropiate user and then use SQLCMD or otherwise you can use the runas command of WIndows to impersonate yourself as the user while executing SQLCMD. Otherwise you can′t use Windows authentication.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

Remote Connection to SQL Server 2005 over Windows Server 2003

Hi Fellows!
I am trying to establish a connection between SQL Server 2005 Server
which is setup on Windows Server 2003 along with Visual Studio 2005.
The problem is that when i try to connect it through management
studio using <servername>/databasename method , i become successfull
and got everything. However , if i use ipaddress scheme like
<ipaddress>/databasename , it failed by saying popular error "Error no
:26 Server is not available , ....." along with description "sqr
server might be need to enable for remote access"
I have checked all the ip configuration and also allowed the port
1433, 1444, 1500 (my own named isntance port) and 1743 (the port i
found from the Log of the server).
now the problem is that i am still unable to connect my client to my
server using ipaddress.
Can somebody sugggest me about this porblem.
i am really greatfull to you for this.
Regards,
UsmanBy <servername>/databasename, I suppose you meant
<servername>\<instancename>. The former should not have worked.
If <servername>\<instancename> works, <ipaddress>\<instancename> should work
too unless (1) <ipaddress> is not really the IP address of the server, (2)
<servername> is resolved by DNS/WINS/Host file to something other than
<ipaddress>, or (3) you have an alias <ipaddress>\<instancename> that points
to a nonexistent/nonactive instance.
BTW, I'm curious as to why you would want to use <ipaddress>\<instancename>?
I don't believe this is a common approach.
Linchi
"gripusa" wrote:

> Hi Fellows!
> I am trying to establish a connection between SQL Server 2005 Server
> which is setup on Windows Server 2003 along with Visual Studio 2005.
> The problem is that when i try to connect it through management
> studio using <servername>/databasename method , i become successfull
> and got everything. However , if i use ipaddress scheme like
> <ipaddress>/databasename , it failed by saying popular error "Error no
> :26 Server is not available , ....." along with description "sqr
> server might be need to enable for remote access"
> I have checked all the ip configuration and also allowed the port
> 1433, 1444, 1500 (my own named isntance port) and 1743 (the port i
> found from the Log of the server).
> now the problem is that i am still unable to connect my client to my
> server using ipaddress.
> Can somebody sugggest me about this porblem.
> i am really greatfull to you for this.
> Regards,
> Usman
>

Remote Connection to SQL Server 2005 over Windows Server 2003

Hi Fellows!
I am trying to establish a connection between SQL Server 2005 Server
which is setup on Windows Server 2003 along with Visual Studio 2005.
The problem is that when i try to connect it through management
studio using <servername>/databasename method , i become successfull
and got everything. However , if i use ipaddress scheme like
<ipaddress>/databasename , it failed by saying popular error "Error no
:26 Server is not available , ....." along with description "sqr
server might be need to enable for remote access"
I have checked all the ip configuration and also allowed the port
1433, 1444, 1500 (my own named isntance port) and 1743 (the port i
found from the Log of the server).
now the problem is that i am still unable to connect my client to my
server using ipaddress.
Can somebody sugggest me about this porblem.
i am really greatfull to you for this.
Regards,
UsmanBy <servername>/databasename, I suppose you meant
<servername>\<instancename>. The former should not have worked.
If <servername>\<instancename> works, <ipaddress>\<instancename> should work
too unless (1) <ipaddress> is not really the IP address of the server, (2)
<servername> is resolved by DNS/WINS/Host file to something other than
<ipaddress>, or (3) you have an alias <ipaddress>\<instancename> that points
to a nonexistent/nonactive instance.
BTW, I'm curious as to why you would want to use <ipaddress>\<instancename>?
I don't believe this is a common approach.
Linchi
"gripusa" wrote:
> Hi Fellows!
> I am trying to establish a connection between SQL Server 2005 Server
> which is setup on Windows Server 2003 along with Visual Studio 2005.
> The problem is that when i try to connect it through management
> studio using <servername>/databasename method , i become successfull
> and got everything. However , if i use ipaddress scheme like
> <ipaddress>/databasename , it failed by saying popular error "Error no
> :26 Server is not available , ....." along with description "sqr
> server might be need to enable for remote access"
> I have checked all the ip configuration and also allowed the port
> 1433, 1444, 1500 (my own named isntance port) and 1743 (the port i
> found from the Log of the server).
> now the problem is that i am still unable to connect my client to my
> server using ipaddress.
> Can somebody sugggest me about this porblem.
> i am really greatfull to you for this.
> Regards,
> Usman
>

Remote Connection to SQL Server 2005 on Windows 2003

Hi Fellows!
I am trying to connect a SQL Server 2005 Server setup on Windows Server 2003 and failing. I have checked few other related posts but i think so i am still unable to find the solution.
My configuration and problem is following;
I want to enable access for my SQL Server to my network as well as through internet using our Fix IP address server.
Configurations:
Server: Win XP Server 2003 along with VS 2005 and SQL Server 2005
Clients : WinXP Laptops (home addition) installed SQL Server Connectivity tools and Express addition and also community edition of Management Studio for Express edition.
I am able to connect the server when i try to use my servername but failed when i try to use ipaddress in the connection.
i tired with telnet, the same problem occurs as i can login by using the network machine name but unable to login by using the local or external ip address.
I have checked with my router configuration and i have allowd both the standard ip and the ip i have given to my named instance and also the port which i have seen in the server log , so i am still unable to find why i am not able to connect it.
Can some one will guide me, i will be really thankfull to him.

start>program>microsoft sqlserver 2005>configuration tools>sql server surface area configuration

>configuration for service and connection>remote connections

>check local and remote

>check both tcp/ip and named pipes

|||Thanks for your reply, i tried to use Surface area tool for my client but it is unable to connect to that client. Especially it also becomes difficult when i am gona operate across the network . (Actually server is in our headquarter and client is in other office).|||

hi,

kindly check if port 1433 is left opened in your firewall

regards,

joey

|||

Try adding sqlservr.exe (present in \MSSQL\Binn directory for the default instance and \MSSQL$instance_name\Binn directory for the named instance) in the list of allowed firewall exceptions on the Windows 2003 box.

Regards,

Rajesh