Hi knights, do you get error "Invalid Instance" ?

I create 2 instances SQL Server in the same server using port 1433, unluckily when i connect they from the remote pc, it doesn't connect and alert "Invalid Instance". How can i use many instances? And what special when i replicate them?Check out KB #287932 (http://support.microsoft.com/default.aspx?scid=kb;en-us;287932). It explains what you need in more detail than I care to retype!

-PatP|||What a pity PatP, it happens even all clients and the server in a Lan group with a hub without firewall on server.|||So it isn't the remote clients as you originally posted? Did the local clients work and then stop, or never work at all? Can you connect from any machine except the server itself? Can you connect to the instances on the server itself?

-PatP|||All clients can't connect to but the server can.|||I suspect that the problem may be because you've set up two instances to use the same TCP port. If you check the KB article I cited, each instance normally has its own port, and the port usages are arbitrated by port 1434. Only the default (unnamed) instance of SQL Server should use port 1433.

I'd suggest that you try to reconfigure the server that way to see if it works.

-PatP

Help-me with this error

TITLE: Connect to Database Engine
--
Cannot connect to VEGAS-W-DV-02.
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (Microsoft SQL Server, Error: 233)
For help, click:
http://go.microsoft.com/fwlink?Prod...33&LinkId=20476
BUTTONS:
OK
--Can you ping the box?
Have you tried a different protocol, like TCP for instance?
Is your server even listening on named pipes?
Are you on the same subnet as the server?
Can you establish a client connection from the server itself?
*mike hodgson*
http://sqlnerd.blogspot.com
Retf wrote:

>TITLE: Connect to Database Engine
>--
>Cannot connect to VEGAS-W-DV-02.
>--
>ADDITIONAL INFORMATION:
>An error has occurred while establishing a connection to the server. When
>connecting to SQL Server 2005, this failure may be caused by the fact that
>under the default settings SQL Server does not allow remote connections.
>(provider: Named Pipes Provider, error: 40 - Could not open a connection to
>SQL Server) (Microsoft SQL Server, Error: 233)
>For help, click:
>http://go.microsoft.com/fwlink?Prod...33&LinkId=20476
>--
>BUTTONS:
>OK
>--
>
>|||yes
no, how I do this?
I dont know
yes
yes
Thanks to all...
"Mike Hodgson" <e1minst3r@.gmail.com> escreveu na mensagem news:%23OJa$NvcGHA
.3908@.TK2MSFTNGP04.phx.gbl...
Can you ping the box?
Have you tried a different protocol, like TCP for instance?
Is your server even listening on named pipes?
Are you on the same subnet as the server?
Can you establish a client connection from the server itself?
mike hodgson
http://sqlnerd.blogspot.com
Retf wrote:
TITLE: Connect to Database Engine
--
Cannot connect to VEGAS-W-DV-02.
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (Microsoft SQL Server, Error: 233)
For help, click:
http://go.microsoft.com/fwlink?Prod...33&LinkId=20476
BUTTONS:
OK
--|||I'm guessing that your server is not listening on any named pipes. You
can change the network protocols in the SQL Server 2005 Surface Area
Configuration tool (in Start | Programs | Microsoft SQL Server 2005 |
Configuration Tools) or in the "SQL Server 2005 Network Configuration"
section of the SQL Server Configuration Manager tool (also in Start |
Programs | Microsoft SQL Server 2005 | Configuration Tools).
Personally, I would turn on TCP, set the port to something other than
1433, make sure named pipes is turned off and always use TCP to connect
to the SQL instance (either by moving the TCP protocol above Named Pipes
in the "SQL Native Client Configuration" section of the SQL Server
Configuration Manager on the client machine (ie. protocol priority) or
by specifying the TCP protocol in the client connection when connecting
to the SQL instance (either in an alias or by explicitly specifying
"tcp:servername,portnum" for the server name in the connection strings)).
*mike hodgson*
http://sqlnerd.blogspot.com
retf wrote:
[vbcol=seagreen]
> yes
> no, how I do this?
> I dont know
> yes
> yes
> Thanks to all...
> "Mike Hodgson" <e1minst3r@.gmail.com <mailto:e1minst3r@.gmail.com>>
> escreveu na mensagem news:%23OJa$NvcGHA.3908@.TK2MSFTNGP04.phx.gbl...
> Can you ping the box?
> Have you tried a different protocol, like TCP for instance?
> Is your server even listening on named pipes?
> Are you on the same subnet as the server?
> Can you establish a client connection from the server itself?
> --
> *mike hodgson*
> http://sqlnerd.blogspot.com
>
> Retf wrote:
>|||Hi,
Thanks for help.
How I change the port 1433 to 1436 (ex)?
Thanks
"Mike Hodgson" <e1minst3r@.gmail.com> escreveu na mensagem news:u86$LbwcGHA.4
932@.TK2MSFTNGP03.phx.gbl...
I'm guessing that your server is not listening on any named pipes. You can
change the network protocols in the SQL Server 2005 Surface Area Configurati
on tool (in Start | Programs | Microsoft SQL Server 2005 | Configuration Too
ls) or in the "SQL Server 2005 Network Configuration" section of the SQL Ser
ver Configuration Manager tool (also in Start | Programs | Microsoft SQL Ser
ver 2005 | Configuration Tools).
Personally, I would turn on TCP, set the port to something other than 1433,
make sure named pipes is turned off and always use TCP to connect to the SQL
instance (either by moving the TCP protocol above Named Pipes in the "SQL N
ative Client Configuration" section of the SQL Server Configuration Manager
on the client machine (ie. protocol priority) or by specifying the TCP proto
col in the client connection when connecting to the SQL instance (either in
an alias or by explicitly specifying "tcp:servername,portnum" for the server
name in the connection strings)).
mike hodgson
http://sqlnerd.blogspot.com
retf wrote:
yes
no, how I do this?
I dont know
yes
yes
Thanks to all...
"Mike Hodgson" <e1minst3r@.gmail.com> escreveu na mensagem news:%23OJa$NvcGHA
.3908@.TK2MSFTNGP04.phx.gbl...
Can you ping the box?
Have you tried a different protocol, like TCP for instance?
Is your server even listening on named pipes?
Are you on the same subnet as the server?
Can you establish a client connection from the server itself?
mike hodgson
http://sqlnerd.blogspot.com
Retf wrote:
TITLE: Connect to Database Engine
--
Cannot connect to VEGAS-W-DV-02.
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (Microsoft SQL Server, Error: 233)
For help, click:
http://go.microsoft.com/fwlink?Prod...33&LinkId=20476
BUTTONS:
OK
--|||Other thing , If I have firewall (basic firewam of windows 2003) I need open
this port, ane any else more?
"Mike Hodgson" <e1minst3r@.gmail.com> escreveu na mensagem news:u86$LbwcGHA.4
932@.TK2MSFTNGP03.phx.gbl...
I'm guessing that your server is not listening on any named pipes. You can
change the network protocols in the SQL Server 2005 Surface Area Configurati
on tool (in Start | Programs | Microsoft SQL Server 2005 | Configuration Too
ls) or in the "SQL Server 2005 Network Configuration" section of the SQL Ser
ver Configuration Manager tool (also in Start | Programs | Microsoft SQL Ser
ver 2005 | Configuration Tools).
Personally, I would turn on TCP, set the port to something other than 1433,
make sure named pipes is turned off and always use TCP to connect to the SQL
instance (either by moving the TCP protocol above Named Pipes in the "SQL N
ative Client Configuration" section of the SQL Server Configuration Manager
on the client machine (ie. protocol priority) or by specifying the TCP proto
col in the client connection when connecting to the SQL instance (either in
an alias or by explicitly specifying "tcp:servername,portnum" for the server
name in the connection strings)).
mike hodgson
http://sqlnerd.blogspot.com
retf wrote:
yes
no, how I do this?
I dont know
yes
yes
Thanks to all...
"Mike Hodgson" <e1minst3r@.gmail.com> escreveu na mensagem news:%23OJa$NvcGHA
.3908@.TK2MSFTNGP04.phx.gbl...
Can you ping the box?
Have you tried a different protocol, like TCP for instance?
Is your server even listening on named pipes?
Are you on the same subnet as the server?
Can you establish a client connection from the server itself?
mike hodgson
http://sqlnerd.blogspot.com
Retf wrote:
TITLE: Connect to Database Engine
--
Cannot connect to VEGAS-W-DV-02.
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (Microsoft SQL Server, Error: 233)
For help, click:
http://go.microsoft.com/fwlink?Prod...33&LinkId=20476
BUTTONS:
OK
--|||Use the SQL Server Configuration Manager mentioned in my previous reply
(SQL Server 2005 Network Configuration section).
*mike hodgson*
http://sqlnerd.blogspot.com
Retf wrote:
[vbcol=seagreen]
> Hi,
> Thanks for help.
> How I change the port 1433 to 1436 (ex)?
> Thanks
> "Mike Hodgson" <e1minst3r@.gmail.com <mailto:e1minst3r@.gmail.com>>
> escreveu na mensagem news:u86$LbwcGHA.4932@.TK2MSFTNGP03.phx.gbl...
> I'm guessing that your server is not listening on any named
> pipes. You can change the network protocols in the SQL Server
> 2005 Surface Area Configuration tool (in Start | Programs |
> Microsoft SQL Server 2005 | Configuration Tools) or in the "SQL
> Server 2005 Network Configuration" section of the SQL Server
> Configuration Manager tool (also in Start | Programs | Microsoft
> SQL Server 2005 | Configuration Tools).
> Personally, I would turn on TCP, set the port to something other
> than 1433, make sure named pipes is turned off and always use TCP
> to connect to the SQL instance (either by moving the TCP protocol
> above Named Pipes in the "SQL Native Client Configuration" section
> of the SQL Server Configuration Manager on the client machine (ie.
> protocol priority) or by specifying the TCP protocol in the client
> connection when connecting to the SQL instance (either in an alias
> or by explicitly specifying "tcp:servername,portnum" for the
> server name in the connection strings)).
> --
> *mike hodgson*
> http://sqlnerd.blogspot.com
>
> retf wrote:
>|||That's the only incoming port you'll need to open (assuming you don't
need the SQL Server Browser service, which you shouldn't - you may as
well disable that browser service as you won't need it). SQL Server
opens an outgoing connection back to the client, I think, using a high
port but most firewalls allow all outgoing connections by default. And,
in fact, I think the Windows firewall only deals with incoming traffic
so I don't think there's even an option to mess around with outbound ports.
*mike hodgson*
http://sqlnerd.blogspot.com
Retf wrote:
[vbcol=seagreen]
> Other thing , If I have firewall (basic firewam of windows 2003) I
> need open this port, ane any else more?
>
> "Mike Hodgson" <e1minst3r@.gmail.com <mailto:e1minst3r@.gmail.com>>
> escreveu na mensagem news:u86$LbwcGHA.4932@.TK2MSFTNGP03.phx.gbl...
> I'm guessing that your server is not listening on any named
> pipes. You can change the network protocols in the SQL Server
> 2005 Surface Area Configuration tool (in Start | Programs |
> Microsoft SQL Server 2005 | Configuration Tools) or in the "SQL
> Server 2005 Network Configuration" section of the SQL Server
> Configuration Manager tool (also in Start | Programs | Microsoft
> SQL Server 2005 | Configuration Tools).
> Personally, I would turn on TCP, set the port to something other
> than 1433, make sure named pipes is turned off and always use TCP
> to connect to the SQL instance (either by moving the TCP protocol
> above Named Pipes in the "SQL Native Client Configuration" section
> of the SQL Server Configuration Manager on the client machine (ie.
> protocol priority) or by specifying the TCP protocol in the client
> connection when connecting to the SQL instance (either in an alias
> or by explicitly specifying "tcp:servername,portnum" for the
> server name in the connection strings)).
> --
> *mike hodgson*
> http://sqlnerd.blogspot.com
>
> retf wrote:
>|||Hi,
You may also want to check on client machine to make sure both TCPIP and
named pipes are enabled via client network utility or configuration
manager. Port configuration is only valid for TCPIP protocol. Named pipies
is usually based on netbios connection via port 135/138/139 etc.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.

Help-me with this error

TITLE: Connect to Database Engine
--
Cannot connect to VEGAS-W-DV-02.
--
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (Microsoft SQL Server, Error: 233)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476
--
BUTTONS:
OK
--This is a multi-part message in MIME format.
--050904010205030506090301
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Can you ping the box?
Have you tried a different protocol, like TCP for instance?
Is your server even listening on named pipes?
Are you on the same subnet as the server?
Can you establish a client connection from the server itself?
--
*mike hodgson*
http://sqlnerd.blogspot.com
Retf wrote:
>TITLE: Connect to Database Engine
>--
>Cannot connect to VEGAS-W-DV-02.
>--
>ADDITIONAL INFORMATION:
>An error has occurred while establishing a connection to the server. When
>connecting to SQL Server 2005, this failure may be caused by the fact that
>under the default settings SQL Server does not allow remote connections.
>(provider: Named Pipes Provider, error: 40 - Could not open a connection to
>SQL Server) (Microsoft SQL Server, Error: 233)
>For help, click:
>http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476
>--
>BUTTONS:
>OK
>--
>
>
--050904010205030506090301
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>Can you ping the box?<br>
Have you tried a different protocol, like TCP for instance?<br>
Is your server even listening on named pipes?<br>
Are you on the same subnet as the server?<br>
Can you establish a client connection from the server itself?</tt><br>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span> <b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2"><a href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
Retf wrote:
<blockquote cite="mideDkSG6tcGHA.3344@.TK2MSFTNGP03.phx.gbl" type="cite">
<pre wrap="">TITLE: Connect to Database Engine
--
Cannot connect to VEGAS-W-DV-02.
--
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (Microsoft SQL Server, Error: 233)
For help, click:
<a class="moz-txt-link-freetext" href="http://links.10026.com/?link=http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476</a>">http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476">http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476</a>
--
BUTTONS:
OK
--
</pre>
</blockquote>
</body>
</html>
--050904010205030506090301--|||This is a multi-part message in MIME format.
--=_NextPart_000_0010_01C672E4.16296780
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
yes
no, how I do this?
I dont know
yes
yes
Thanks to all...
"Mike Hodgson" <e1minst3r@.gmail.com> escreveu na mensagem =news:%23OJa$NvcGHA.3908@.TK2MSFTNGP04.phx.gbl...
Can you ping the box?
Have you tried a different protocol, like TCP for instance?
Is your server even listening on named pipes?
Are you on the same subnet as the server?
Can you establish a client connection from the server itself?
--
mike hodgson
http://sqlnerd.blogspot.com=20
Retf wrote: TITLE: Connect to Database Engine
--
Cannot connect to VEGAS-W-DV-02.
--
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. =When connecting to SQL Server 2005, this failure may be caused by the fact =that under the default settings SQL Server does not allow remote connections. =
(provider: Named Pipes Provider, error: 40 - Could not open a connection =to SQL Server) (Microsoft SQL Server, Error: 233)
For help, click: http://go.microsoft.com/fwlink?ProdName=3DMicrosoft+SQL+Server&EvtSrc=3DM=
SSQLServer&EvtID=3D233&LinkId=3D20476
--
BUTTONS:
OK
--
--=_NextPart_000_0010_01C672E4.16296780
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

---

yes
no, how I do this?
I dont know
yes
yes
Thanks to all...
"Mike Hodgson" =escreveu na mensagem news:%23OJa$NvcGHA.=3908@.TK2MSFTNGP04.phx.gbl...Can you ping the box?Have you tried a different protocol, like TCP for = instance?Is your server even listening on named pipes?Are you =on the same subnet as the server?Can you establish a client connection =from the server itself?
--mike =hodgsonhttp://sqlnerd.blogspot.com Retf wrote: TITLE: Connect to Database Engine
--
Cannot connect to VEGAS-W-DV-02.
--
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. =When connecting to SQL Server 2005, this failure may be caused by the fact =that under the default settings SQL Server does not allow remote connections. =(provider: Named Pipes Provider, error: 40 - Could not open a connection =to SQL Server) (Microsoft SQL Server, Error: 233)
For help, click: http://go.micr=osoft.com/fwlink?ProdName=3DMicrosoft+SQL+Server&EvtSrc=3DMSSQLServer=&EvtID=3D233&LinkId=3D20476
--
BUTTONS:
OK
--

---

--=_NextPart_000_0010_01C672E4.16296780--|||This is a multi-part message in MIME format.
--030303010405060404030702
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
I'm guessing that your server is not listening on any named pipes. You
can change the network protocols in the SQL Server 2005 Surface Area
Configuration tool (in Start | Programs | Microsoft SQL Server 2005 |
Configuration Tools) or in the "SQL Server 2005 Network Configuration"
section of the SQL Server Configuration Manager tool (also in Start |
Programs | Microsoft SQL Server 2005 | Configuration Tools).
Personally, I would turn on TCP, set the port to something other than
1433, make sure named pipes is turned off and always use TCP to connect
to the SQL instance (either by moving the TCP protocol above Named Pipes
in the "SQL Native Client Configuration" section of the SQL Server
Configuration Manager on the client machine (ie. protocol priority) or
by specifying the TCP protocol in the client connection when connecting
to the SQL instance (either in an alias or by explicitly specifying
"tcp:servername,portnum" for the server name in the connection strings)).
--
*mike hodgson*
http://sqlnerd.blogspot.com
retf wrote:
> yes
> no, how I do this?
> I dont know
> yes
> yes
> Thanks to all...
> "Mike Hodgson" <e1minst3r@.gmail.com <mailto:e1minst3r@.gmail.com>>
> escreveu na mensagem news:%23OJa$NvcGHA.3908@.TK2MSFTNGP04.phx.gbl...
> Can you ping the box?
> Have you tried a different protocol, like TCP for instance?
> Is your server even listening on named pipes?
> Are you on the same subnet as the server?
> Can you establish a client connection from the server itself?
> --
> *mike hodgson*
> http://sqlnerd.blogspot.com
>
> Retf wrote:
>>TITLE: Connect to Database Engine
>>--
>>Cannot connect to VEGAS-W-DV-02.
>>--
>>ADDITIONAL INFORMATION:
>>An error has occurred while establishing a connection to the server. When
>>connecting to SQL Server 2005, this failure may be caused by the fact that
>>under the default settings SQL Server does not allow remote connections.
>>(provider: Named Pipes Provider, error: 40 - Could not open a connection to
>>SQL Server) (Microsoft SQL Server, Error: 233)
>>For help, click:
>>http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476
>>--
>>BUTTONS:
>>OK
>>--
>>
>>
--030303010405060404030702
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>I'm guessing that your server is not listening on any named pipes.
You can change the network protocols in the SQL Server 2005 Surface
Area Configuration tool (in Start | Programs | Microsoft SQL Server
2005 | Configuration Tools) or in the "SQL Server 2005 Network
Configuration" section of the SQL Server Configuration Manager tool
(also in </tt><tt>Start | Programs | Microsoft SQL Server 2005 |
Configuration Tools</tt><tt>).<br>
<br>
Personally, I would turn on TCP, set the port to something other than
1433, make sure named pipes is turned off and always use TCP to connect
to the SQL instance (either by moving the TCP protocol above Named
Pipes in the "SQL Native Client Configuration" section of the SQL
Server Configuration Manager on the client machine (ie. protocol
priority) or by specifying the TCP protocol in the client connection
when connecting to the SQL instance (either in an alias or by
explicitly specifying "tcp:servername,portnum" for the server name in
the connection strings)).<br>
</tt>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span> <b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2"><a href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
retf wrote:
<blockquote cite="mide2u6CyvcGHA.4108@.TK2MSFTNGP03.phx.gbl" type="cite">
<title></title>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<meta content="MSHTML 6.00.2900.2873" name="GENERATOR">
<style></style>
<div><font face="Arial" size="2">yes</font></div>
<div><font face="Arial" size="2">no, how I do this?</font></div>
<div><font face="Arial" size="2">I dont know</font></div>
<div><font face="Arial" size="2">yes</font></div>
<div><font face="Arial" size="2">yes</font></div>
<div> </div>
<div><font face="Arial" size="2">Thanks to all...</font></div>
<blockquote
style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;"
dir="ltr">
<div>"Mike Hodgson" <<a href="http://links.10026.com/?link=mailto:e1minst3r@.gmail.com">e1minst3r@.gmail.com</a>>
escreveu na mensagem <a
href="http://links.10026.com/?link=news:%23OJa$NvcGHA.3908@.TK2MSFTNGP04.phx.gbl">news:%23OJa$NvcGHA.3908@.TK2MSFTNGP04.phx.gbl</a>...</div>
<tt>Can you ping the box?<br>
Have you tried a different protocol, like TCP for instance?<br>
Is your server even listening on named pipes?<br>
Are you on the same subnet as the server?<br>
Can you establish a client connection from the server itself?</tt><br>
<div class="moz-signature">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span><b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2"><a href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
Retf wrote:
<blockquote cite="mideDkSG6tcGHA.3344@.TK2MSFTNGP03.phx.gbl"
type="cite">
<pre wrap="">TITLE: Connect to Database Engine
--
Cannot connect to VEGAS-W-DV-02.
--
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (Microsoft SQL Server, Error: 233)
For help, click:
<a class="moz-txt-link-freetext"
href="http://links.10026.com/?link=http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476</a>">http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476">http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476</a>
--
BUTTONS:
OK
--
</pre>
</blockquote>
</blockquote>
</blockquote>
</body>
</html>
--030303010405060404030702--|||This is a multi-part message in MIME format.
--=_NextPart_000_0008_01C6736D.DFE53D90
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi,
Thanks for help.
How I change the port 1433 to 1436 (ex)?
Thanks
"Mike Hodgson" <e1minst3r@.gmail.com> escreveu na mensagem =news:u86$LbwcGHA.4932@.TK2MSFTNGP03.phx.gbl...
I'm guessing that your server is not listening on any named pipes. =You can change the network protocols in the SQL Server 2005 Surface Area =Configuration tool (in Start | Programs | Microsoft SQL Server 2005 | =Configuration Tools) or in the "SQL Server 2005 Network Configuration" =section of the SQL Server Configuration Manager tool (also in Start | =Programs | Microsoft SQL Server 2005 | Configuration Tools).
Personally, I would turn on TCP, set the port to something other than =1433, make sure named pipes is turned off and always use TCP to connect =to the SQL instance (either by moving the TCP protocol above Named Pipes =in the "SQL Native Client Configuration" section of the SQL Server =Configuration Manager on the client machine (ie. protocol priority) or =by specifying the TCP protocol in the client connection when connecting =to the SQL instance (either in an alias or by explicitly specifying ="tcp:servername,portnum" for the server name in the connection =strings)).
--
mike hodgson
http://sqlnerd.blogspot.com=20
retf wrote: yes
no, how I do this?
I dont know
yes
yes
Thanks to all...
"Mike Hodgson" <e1minst3r@.gmail.com> escreveu na mensagem =news:%23OJa$NvcGHA.3908@.TK2MSFTNGP04.phx.gbl...
Can you ping the box?
Have you tried a different protocol, like TCP for instance?
Is your server even listening on named pipes?
Are you on the same subnet as the server?
Can you establish a client connection from the server itself?
--
mike hodgson
http://sqlnerd.blogspot.com=20
Retf wrote: TITLE: Connect to Database Engine
--
Cannot connect to VEGAS-W-DV-02.
--
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. =When connecting to SQL Server 2005, this failure may be caused by the fact =that under the default settings SQL Server does not allow remote connections. =
(provider: Named Pipes Provider, error: 40 - Could not open a connection =to SQL Server) (Microsoft SQL Server, Error: 233)
For help, click: http://go.microsoft.com/fwlink?ProdName=3DMicrosoft+SQL+Server&EvtSrc=3DM=
SSQLServer&EvtID=3D233&LinkId=3D20476
--
BUTTONS:
OK
--
--=_NextPart_000_0008_01C6736D.DFE53D90
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

---

Hi,
Thanks for help.
How I change the port 1433 to 1436 (ex)?
Thanks
"Mike Hodgson" =escreveu na mensagem news:u86$LbwcGHA.4932=@.TK2MSFTNGP03.phx.gbl...I'm guessing that your server is not listening on any named pipes. =You can change the network protocols in the SQL Server 2005 Surface Area =Configuration tool (in Start | Programs | Microsoft SQL Server 2005 | Configuration =Tools) or in the "SQL Server 2005 Network Configuration" section of the SQL =Server Configuration Manager tool (also in Start | Programs | =Microsoft SQL Server 2005 | Configuration Tools).Personally, I =would turn on TCP, set the port to something other than 1433, make sure named =pipes is turned off and always use TCP to connect to the SQL instance (either =by moving the TCP protocol above Named Pipes in the "SQL Native Client =Configuration" section of the SQL Server Configuration Manager on the client machine =(ie. protocol priority) or by specifying the TCP protocol in the client =connection when connecting to the SQL instance (either in an alias or by =explicitly specifying "tcp:servername,portnum" for the server name in the =connection strings)).
--mike =hodgsonhttp://sqlnerd.blogspot.com retf wrote:
yes
no, how I do this?
I dont know
yes
yes

Thanks to all...
"Mike Hodgson" =escreveu na mensagem news:%23OJa$NvcGHA.=3908@.TK2MSFTNGP04.phx.gbl...Can you ping the box?Have you tried a different protocol, like TCP =for instance?Is your server even listening on named pipes?Are =you on the same subnet as the server?Can you establish a client =connection from the server itself?
--mike =hodgsonhttp://sqlnerd.blogspot.com Retf wrote: TITLE: Connect to Database Engine
--
Cannot connect to VEGAS-W-DV-02.
--
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. =When connecting to SQL Server 2005, this failure may be caused by the fact =that under the default settings SQL Server does not allow remote connections. =(provider: Named Pipes Provider, error: 40 - Could not open a connection =to SQL Server) (Microsoft SQL Server, Error: 233)
For help, click: http://go.micr=osoft.com/fwlink?ProdName=3DMicrosoft+SQL+Server&EvtSrc=3DMSSQLServer=&EvtID=3D233&LinkId=3D20476
--
BUTTONS:
OK
--
=

---

--=_NextPart_000_0008_01C6736D.DFE53D90--|||This is a multi-part message in MIME format.
--=_NextPart_000_0015_01C6736E.0C39CFF0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Other thing , If I have firewall (basic firewam of windows 2003) I need =open this port, ane any else more?
"Mike Hodgson" <e1minst3r@.gmail.com> escreveu na mensagem =news:u86$LbwcGHA.4932@.TK2MSFTNGP03.phx.gbl...
I'm guessing that your server is not listening on any named pipes. =You can change the network protocols in the SQL Server 2005 Surface Area =Configuration tool (in Start | Programs | Microsoft SQL Server 2005 | =Configuration Tools) or in the "SQL Server 2005 Network Configuration" =section of the SQL Server Configuration Manager tool (also in Start | =Programs | Microsoft SQL Server 2005 | Configuration Tools).
Personally, I would turn on TCP, set the port to something other than =1433, make sure named pipes is turned off and always use TCP to connect =to the SQL instance (either by moving the TCP protocol above Named Pipes =in the "SQL Native Client Configuration" section of the SQL Server =Configuration Manager on the client machine (ie. protocol priority) or =by specifying the TCP protocol in the client connection when connecting =to the SQL instance (either in an alias or by explicitly specifying ="tcp:servername,portnum" for the server name in the connection =strings)).
--
mike hodgson
http://sqlnerd.blogspot.com=20
retf wrote: yes
no, how I do this?
I dont know
yes
yes
Thanks to all...
"Mike Hodgson" <e1minst3r@.gmail.com> escreveu na mensagem =news:%23OJa$NvcGHA.3908@.TK2MSFTNGP04.phx.gbl...
Can you ping the box?
Have you tried a different protocol, like TCP for instance?
Is your server even listening on named pipes?
Are you on the same subnet as the server?
Can you establish a client connection from the server itself?
--
mike hodgson
http://sqlnerd.blogspot.com=20
Retf wrote: TITLE: Connect to Database Engine
--
Cannot connect to VEGAS-W-DV-02.
--
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. =When connecting to SQL Server 2005, this failure may be caused by the fact =that under the default settings SQL Server does not allow remote connections. =
(provider: Named Pipes Provider, error: 40 - Could not open a connection =to SQL Server) (Microsoft SQL Server, Error: 233)
For help, click: http://go.microsoft.com/fwlink?ProdName=3DMicrosoft+SQL+Server&EvtSrc=3DM=
SSQLServer&EvtID=3D233&LinkId=3D20476
--
BUTTONS:
OK
--
--=_NextPart_000_0015_01C6736E.0C39CFF0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

---

Other thing , If I have firewall (basic =firewam of windows 2003) I need open this port, ane any else =more?
"Mike Hodgson" =escreveu na mensagem news:u86$LbwcGHA.4932=@.TK2MSFTNGP03.phx.gbl...I'm guessing that your server is not listening on any named pipes. =You can change the network protocols in the SQL Server 2005 Surface Area =Configuration tool (in Start | Programs | Microsoft SQL Server 2005 | Configuration =Tools) or in the "SQL Server 2005 Network Configuration" section of the SQL =Server Configuration Manager tool (also in Start | Programs | =Microsoft SQL Server 2005 | Configuration Tools).Personally, I =would turn on TCP, set the port to something other than 1433, make sure named =pipes is turned off and always use TCP to connect to the SQL instance (either =by moving the TCP protocol above Named Pipes in the "SQL Native Client =Configuration" section of the SQL Server Configuration Manager on the client machine =(ie. protocol priority) or by specifying the TCP protocol in the client =connection when connecting to the SQL instance (either in an alias or by =explicitly specifying "tcp:servername,portnum" for the server name in the =connection strings)).
--mike =hodgsonhttp://sqlnerd.blogspot.com retf wrote:
yes
no, how I do this?
I dont know
yes
yes

Thanks to all...
"Mike Hodgson" =escreveu na mensagem news:%23OJa$NvcGHA.=3908@.TK2MSFTNGP04.phx.gbl...Can you ping the box?Have you tried a different protocol, like TCP =for instance?Is your server even listening on named pipes?Are =you on the same subnet as the server?Can you establish a client =connection from the server itself?
--mike =hodgsonhttp://sqlnerd.blogspot.com Retf wrote: TITLE: Connect to Database Engine
--
Cannot connect to VEGAS-W-DV-02.
--
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. =When connecting to SQL Server 2005, this failure may be caused by the fact =that under the default settings SQL Server does not allow remote connections. =(provider: Named Pipes Provider, error: 40 - Could not open a connection =to SQL Server) (Microsoft SQL Server, Error: 233)
For help, click: http://go.micr=osoft.com/fwlink?ProdName=3DMicrosoft+SQL+Server&EvtSrc=3DMSSQLServer=&EvtID=3D233&LinkId=3D20476
--
BUTTONS:
OK
--
=

---

--=_NextPart_000_0015_01C6736E.0C39CFF0--|||This is a multi-part message in MIME format.
--020209000101090301080006
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Use the SQL Server Configuration Manager mentioned in my previous reply
(SQL Server 2005 Network Configuration section).
--
*mike hodgson*
http://sqlnerd.blogspot.com
Retf wrote:
> Hi,
> Thanks for help.
> How I change the port 1433 to 1436 (ex)?
> Thanks
> "Mike Hodgson" <e1minst3r@.gmail.com <mailto:e1minst3r@.gmail.com>>
> escreveu na mensagem news:u86$LbwcGHA.4932@.TK2MSFTNGP03.phx.gbl...
> I'm guessing that your server is not listening on any named
> pipes. You can change the network protocols in the SQL Server
> 2005 Surface Area Configuration tool (in Start | Programs |
> Microsoft SQL Server 2005 | Configuration Tools) or in the "SQL
> Server 2005 Network Configuration" section of the SQL Server
> Configuration Manager tool (also in Start | Programs | Microsoft
> SQL Server 2005 | Configuration Tools).
> Personally, I would turn on TCP, set the port to something other
> than 1433, make sure named pipes is turned off and always use TCP
> to connect to the SQL instance (either by moving the TCP protocol
> above Named Pipes in the "SQL Native Client Configuration" section
> of the SQL Server Configuration Manager on the client machine (ie.
> protocol priority) or by specifying the TCP protocol in the client
> connection when connecting to the SQL instance (either in an alias
> or by explicitly specifying "tcp:servername,portnum" for the
> server name in the connection strings)).
> --
> *mike hodgson*
> http://sqlnerd.blogspot.com
>
> retf wrote:
>> yes
>> no, how I do this?
>> I dont know
>> yes
>> yes
>> Thanks to all...
>> "Mike Hodgson" <e1minst3r@.gmail.com
>> <mailto:e1minst3r@.gmail.com>> escreveu na mensagem
>> news:%23OJa$NvcGHA.3908@.TK2MSFTNGP04.phx.gbl...
>> Can you ping the box?
>> Have you tried a different protocol, like TCP for instance?
>> Is your server even listening on named pipes?
>> Are you on the same subnet as the server?
>> Can you establish a client connection from the server itself?
>> --
>> *mike hodgson*
>> http://sqlnerd.blogspot.com
>>
>> Retf wrote:
>>TITLE: Connect to Database Engine
>>--
>>Cannot connect to VEGAS-W-DV-02.
>>--
>>ADDITIONAL INFORMATION:
>>An error has occurred while establishing a connection to the server. When
>>connecting to SQL Server 2005, this failure may be caused by the fact that
>>under the default settings SQL Server does not allow remote connections.
>>(provider: Named Pipes Provider, error: 40 - Could not open a connection to
>>SQL Server) (Microsoft SQL Server, Error: 233)
>>For help, click:
>>http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476
>>--
>>BUTTONS:
>>OK
>>--
>>
>>
--020209000101090301080006
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>Use the SQL Server Configuration Manager mentioned in my previous
reply (SQL Server 2005 Network Configuration section).</tt><br>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span> <b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2"><a href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
Retf wrote:
<blockquote cite="midO6VlMZ4cGHA.3712@.TK2MSFTNGP03.phx.gbl" type="cite">
<title></title>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<meta content="MSHTML 6.00.2900.2873" name="GENERATOR">
<div><font face="Arial" size="2">Hi,</font></div>
<div> </div>
<div><font face="Arial" size="2">Thanks for help.</font></div>
<div> </div>
<div><font face="Arial" size="2">How I change the port <font
face="Courier New" size="3">1433 to 1436 (ex)?</font></font></div>
<div> </div>
<div><font face="Courier New">Thanks</font></div>
<blockquote
style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;"
dir="ltr">
<div>"Mike Hodgson" <<a href="http://links.10026.com/?link=mailto:e1minst3r@.gmail.com">e1minst3r@.gmail.com</a>>
escreveu na mensagem <a
href="http://links.10026.com/?link=news:u86$LbwcGHA.4932@.TK2MSFTNGP03.phx.gbl">news:u86$LbwcGHA.4932@.TK2MSFTNGP03.phx.gbl</a>...</div>
<tt>I'm guessing that your server is not listening on any named
pipes. You can change the network protocols in the SQL Server 2005
Surface Area Configuration tool (in Start | Programs | Microsoft SQL
Server 2005 | Configuration Tools) or in the "SQL Server 2005 Network
Configuration" section of the SQL Server Configuration Manager tool
(also in </tt><tt>Start | Programs | Microsoft SQL Server 2005 |
Configuration Tools</tt><tt>).<br>
<br>
Personally, I would turn on TCP, set the port to something other than
1433, make sure named pipes is turned off and always use TCP to connect
to the SQL instance (either by moving the TCP protocol above Named
Pipes in the "SQL Native Client Configuration" section of the SQL
Server Configuration Manager on the client machine (ie. protocol
priority) or by specifying the TCP protocol in the client connection
when connecting to the SQL instance (either in an alias or by
explicitly specifying "tcp:servername,portnum" for the server name in
the connection strings)).<br>
</tt>
<div class="moz-signature">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span><b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2"><a href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
retf wrote:
<blockquote cite="mide2u6CyvcGHA.4108@.TK2MSFTNGP03.phx.gbl"
type="cite">
<meta content="MSHTML 6.00.2900.2873" name="GENERATOR">
<style></style>
<div><font face="Arial" size="2">yes</font></div>
<div><font face="Arial" size="2">no, how I do this?</font></div>
<div><font face="Arial" size="2">I dont know</font></div>
<div><font face="Arial" size="2">yes</font></div>
<div><font face="Arial" size="2">yes</font></div>
<div> </div>
<div><font face="Arial" size="2">Thanks to all...</font></div>
<blockquote
style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;"
dir="ltr">
<div>"Mike Hodgson" <<a href="http://links.10026.com/?link=mailto:e1minst3r@.gmail.com">e1minst3r@.gmail.com</a>>
escreveu na mensagem <a
href="http://links.10026.com/?link=news:%23OJa$NvcGHA.3908@.TK2MSFTNGP04.phx.gbl">news:%23OJa$NvcGHA.3908@.TK2MSFTNGP04.phx.gbl</a>...</div>
<tt>Can you ping the box?<br>
Have you tried a different protocol, like TCP for instance?<br>
Is your server even listening on named pipes?<br>
Are you on the same subnet as the server?<br>
Can you establish a client connection from the server itself?</tt><br>
<div class="moz-signature">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span><b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2"><a
href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
Retf wrote:
<blockquote cite="mideDkSG6tcGHA.3344@.TK2MSFTNGP03.phx.gbl"
type="cite">
<pre wrap="">TITLE: Connect to Database Engine
--
Cannot connect to VEGAS-W-DV-02.
--
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (Microsoft SQL Server, Error: 233)
For help, click:
<a class="moz-txt-link-freetext"
href="http://links.10026.com/?link=http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476</a>">http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476">http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476</a>
--
BUTTONS:
OK
--
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</body>
</html>
--020209000101090301080006--|||This is a multi-part message in MIME format.
--060104020209090202010800
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
That's the only incoming port you'll need to open (assuming you don't
need the SQL Server Browser service, which you shouldn't - you may as
well disable that browser service as you won't need it). SQL Server
opens an outgoing connection back to the client, I think, using a high
port but most firewalls allow all outgoing connections by default. And,
in fact, I think the Windows firewall only deals with incoming traffic
so I don't think there's even an option to mess around with outbound ports.
--
*mike hodgson*
http://sqlnerd.blogspot.com
Retf wrote:
> Other thing , If I have firewall (basic firewam of windows 2003) I
> need open this port, ane any else more?
>
> "Mike Hodgson" <e1minst3r@.gmail.com <mailto:e1minst3r@.gmail.com>>
> escreveu na mensagem news:u86$LbwcGHA.4932@.TK2MSFTNGP03.phx.gbl...
> I'm guessing that your server is not listening on any named
> pipes. You can change the network protocols in the SQL Server
> 2005 Surface Area Configuration tool (in Start | Programs |
> Microsoft SQL Server 2005 | Configuration Tools) or in the "SQL
> Server 2005 Network Configuration" section of the SQL Server
> Configuration Manager tool (also in Start | Programs | Microsoft
> SQL Server 2005 | Configuration Tools).
> Personally, I would turn on TCP, set the port to something other
> than 1433, make sure named pipes is turned off and always use TCP
> to connect to the SQL instance (either by moving the TCP protocol
> above Named Pipes in the "SQL Native Client Configuration" section
> of the SQL Server Configuration Manager on the client machine (ie.
> protocol priority) or by specifying the TCP protocol in the client
> connection when connecting to the SQL instance (either in an alias
> or by explicitly specifying "tcp:servername,portnum" for the
> server name in the connection strings)).
> --
> *mike hodgson*
> http://sqlnerd.blogspot.com
>
> retf wrote:
>> yes
>> no, how I do this?
>> I dont know
>> yes
>> yes
>> Thanks to all...
>> "Mike Hodgson" <e1minst3r@.gmail.com
>> <mailto:e1minst3r@.gmail.com>> escreveu na mensagem
>> news:%23OJa$NvcGHA.3908@.TK2MSFTNGP04.phx.gbl...
>> Can you ping the box?
>> Have you tried a different protocol, like TCP for instance?
>> Is your server even listening on named pipes?
>> Are you on the same subnet as the server?
>> Can you establish a client connection from the server itself?
>> --
>> *mike hodgson*
>> http://sqlnerd.blogspot.com
>>
>> Retf wrote:
>>TITLE: Connect to Database Engine
>>--
>>Cannot connect to VEGAS-W-DV-02.
>>--
>>ADDITIONAL INFORMATION:
>>An error has occurred while establishing a connection to the server. When
>>connecting to SQL Server 2005, this failure may be caused by the fact that
>>under the default settings SQL Server does not allow remote connections.
>>(provider: Named Pipes Provider, error: 40 - Could not open a connection to
>>SQL Server) (Microsoft SQL Server, Error: 233)
>>For help, click:
>>http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476
>>--
>>BUTTONS:
>>OK
>>--
>>
>>
--060104020209090202010800
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>That's the only incoming port you'll need to open (assuming you
don't need the SQL Server Browser service, which you shouldn't - you
may as well disable that browser service as you won't need it). SQL
Server opens an outgoing connection back to the client, I think, using
a high port but most firewalls allow all outgoing connections by
default. And, in fact, I think the Windows firewall only deals with
incoming traffic so I don't think there's even an option to mess around
with outbound ports.</tt><br>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span> <b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2"><a href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
Retf wrote:
<blockquote cite="mid%23Fc74Z4cGHA.2456@.TK2MSFTNGP04.phx.gbl"
type="cite">
<title></title>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<meta content="MSHTML 6.00.2900.2873" name="GENERATOR">
<div><font face="Arial" size="2">Other thing , If I have firewall
(basic firewam of windows 2003) I need open this port, ane any else
more?</font></div>
<div> </div>
<blockquote
style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;"
dir="ltr">
<div>"Mike Hodgson" <<a href="http://links.10026.com/?link=mailto:e1minst3r@.gmail.com">e1minst3r@.gmail.com</a>>
escreveu na mensagem <a
href="http://links.10026.com/?link=news:u86$LbwcGHA.4932@.TK2MSFTNGP03.phx.gbl">news:u86$LbwcGHA.4932@.TK2MSFTNGP03.phx.gbl</a>...</div>
<tt>I'm guessing that your server is not listening on any named
pipes. You can change the network protocols in the SQL Server 2005
Surface Area Configuration tool (in Start | Programs | Microsoft SQL
Server 2005 | Configuration Tools) or in the "SQL Server 2005 Network
Configuration" section of the SQL Server Configuration Manager tool
(also in </tt><tt>Start | Programs | Microsoft SQL Server 2005 |
Configuration Tools</tt><tt>).<br>
<br>
Personally, I would turn on TCP, set the port to something other than
1433, make sure named pipes is turned off and always use TCP to connect
to the SQL instance (either by moving the TCP protocol above Named
Pipes in the "SQL Native Client Configuration" section of the SQL
Server Configuration Manager on the client machine (ie. protocol
priority) or by specifying the TCP protocol in the client connection
when connecting to the SQL instance (either in an alias or by
explicitly specifying "tcp:servername,portnum" for the server name in
the connection strings)).<br>
</tt>
<div class="moz-signature">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span><b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2"><a href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
retf wrote:
<blockquote cite="mide2u6CyvcGHA.4108@.TK2MSFTNGP03.phx.gbl"
type="cite">
<meta content="MSHTML 6.00.2900.2873" name="GENERATOR">
<style></style>
<div><font face="Arial" size="2">yes</font></div>
<div><font face="Arial" size="2">no, how I do this?</font></div>
<div><font face="Arial" size="2">I dont know</font></div>
<div><font face="Arial" size="2">yes</font></div>
<div><font face="Arial" size="2">yes</font></div>
<div> </div>
<div><font face="Arial" size="2">Thanks to all...</font></div>
<blockquote
style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;"
dir="ltr">
<div>"Mike Hodgson" <<a href="http://links.10026.com/?link=mailto:e1minst3r@.gmail.com">e1minst3r@.gmail.com</a>>
escreveu na mensagem <a
href="http://links.10026.com/?link=news:%23OJa$NvcGHA.3908@.TK2MSFTNGP04.phx.gbl">news:%23OJa$NvcGHA.3908@.TK2MSFTNGP04.phx.gbl</a>...</div>
<tt>Can you ping the box?<br>
Have you tried a different protocol, like TCP for instance?<br>
Is your server even listening on named pipes?<br>
Are you on the same subnet as the server?<br>
Can you establish a client connection from the server itself?</tt><br>
<div class="moz-signature">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span><b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2"><a
href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
Retf wrote:
<blockquote cite="mideDkSG6tcGHA.3344@.TK2MSFTNGP03.phx.gbl"
type="cite">
<pre wrap="">TITLE: Connect to Database Engine
--
Cannot connect to VEGAS-W-DV-02.
--
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (Microsoft SQL Server, Error: 233)
For help, click:
<a class="moz-txt-link-freetext"
href="http://links.10026.com/?link=http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476</a>">http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476">http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476</a>
--
BUTTONS:
OK
--
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</body>
</html>
--060104020209090202010800--|||Hi,
You may also want to check on client machine to make sure both TCPIP and
named pipes are enabled via client network utility or configuration
manager. Port configuration is only valid for TCPIP protocol. Named pipies
is usually based on netbios connection via port 135/138/139 etc.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

help-login failed for MACHINE_NAME\IUSR_MACHINE_NAME

HI,
i have some problem,

one database 'SMS' is installed in sql server which instance is
BARODA\EMIS.

now i want to connect my web app to this database.
for that
my connectionstring is
--
conn.ConnectionString = "workstation id=BARODA;packet size=4096;integrated security=SSPI;data source=BARODA\EMIS;persist security info=True;initial catalog=SMS"
--

but when i run this error occur

--
login failed for 'MERIDIAN\IUSR_BARODA'
--

for that what should i do?
give any solution.

it's urgent.

thanks in advance.Hi,

This blog might help you:http://weblogs.asp.net/coltk/archive/2003/07/10/9920.aspx

Colt|||hey, colt

my problem,

i want to creat user in MSDE.

how to create user in MSDE?
how to create user in MSDE during app. installation?

give any solution.
it's urgent.

thanks in advance.

HELP:SQL Port lost or never set on new install

I just installed SQL Server on XP (SP2) attempted to access the Server
through JDBC and got a error abut the socket connect. After much searching I
find that the port is not active even though all app that would set the port
have port 1433 set. If you follow. I ran netstat -ano and tasklist /svc. SQL
service is running in the tasklist but the port doesn't show in netstat.
I turned all firewalls off, disconnected the internet and still no port. The
problem doesn't seem to be with the Firewall but XP SP2 & SQLServer.its not SQL Server 2005 is it ? Most versions (Dev, Express, Eval) have
remote access turned off by default
http://msdn2.microsoft.com/en-us/library/ms178763.aspx
is SQL2k check the SQL Errorlog \ Windows Application for Errors
cheers,
Andy.
"jlopes151" <jlopes151@.discussions.microsoft.com> wrote in message
news:363D1BB3-69C2-49E3-A77B-660117628D48@.microsoft.com...
>I just installed SQL Server on XP (SP2) attempted to access the Server
> through JDBC and got a error abut the socket connect. After much searching
> I
> find that the port is not active even though all app that would set the
> port
> have port 1433 set. If you follow. I ran netstat -ano and tasklist /svc.
> SQL
> service is running in the tasklist but the port doesn't show in netstat.
> I turned all firewalls off, disconnected the internet and still no port.
> The
> problem doesn't seem to be with the Firewall but XP SP2 & SQLServer.
>|||The errorlog has it listening on Shared Memory, & Named Pipes even though
Named Pipes & TCP/IP protocols are enabled in the SQL Network Server Utility
.
I tried to scrambble the protocols by disabling and restarting the server,
but the TCP/IP protocol doesn't show.
"Andy Ball" wrote:

> its not SQL Server 2005 is it ? Most versions (Dev, Express, Eval) have
> remote access turned off by default
> http://msdn2.microsoft.com/en-us/library/ms178763.aspx
> is SQL2k check the SQL Errorlog \ Windows Application for Errors
> cheers,
> Andy.
>
> "jlopes151" <jlopes151@.discussions.microsoft.com> wrote in message
> news:363D1BB3-69C2-49E3-A77B-660117628D48@.microsoft.com...
>
>|||Problem solved with the SP4 update.
"jlopes151" wrote:
[vbcol=seagreen]
> The errorlog has it listening on Shared Memory, & Named Pipes even though
> Named Pipes & TCP/IP protocols are enabled in the SQL Network Server Utili
ty.
> I tried to scrambble the protocols by disabling and restarting the server,
> but the TCP/IP protocol doesn't show.
> "Andy Ball" wrote:
>

HELP:SQL Port lost or never set on new install

I just installed SQL Server on XP (SP2) attempted to access the Server
through JDBC and got a error abut the socket connect. After much searching I
find that the port is not active even though all app that would set the port
have port 1433 set. If you follow. I ran netstat -ano and tasklist /svc. SQL
service is running in the tasklist but the port doesn't show in netstat.
I turned all firewalls off, disconnected the internet and still no port. The
problem doesn't seem to be with the Firewall but XP SP2 & SQLServer.
its not SQL Server 2005 is it ? Most versions (Dev, Express, Eval) have
remote access turned off by default
http://msdn2.microsoft.com/en-us/library/ms178763.aspx
is SQL2k check the SQL Errorlog \ Windows Application for Errors
cheers,
Andy.
"jlopes151" <jlopes151@.discussions.microsoft.com> wrote in message
news:363D1BB3-69C2-49E3-A77B-660117628D48@.microsoft.com...
>I just installed SQL Server on XP (SP2) attempted to access the Server
> through JDBC and got a error abut the socket connect. After much searching
> I
> find that the port is not active even though all app that would set the
> port
> have port 1433 set. If you follow. I ran netstat -ano and tasklist /svc.
> SQL
> service is running in the tasklist but the port doesn't show in netstat.
> I turned all firewalls off, disconnected the internet and still no port.
> The
> problem doesn't seem to be with the Firewall but XP SP2 & SQLServer.
>
|||The errorlog has it listening on Shared Memory, & Named Pipes even though
Named Pipes & TCP/IP protocols are enabled in the SQL Network Server Utility.
I tried to scrambble the protocols by disabling and restarting the server,
but the TCP/IP protocol doesn't show.
"Andy Ball" wrote:

> its not SQL Server 2005 is it ? Most versions (Dev, Express, Eval) have
> remote access turned off by default
> http://msdn2.microsoft.com/en-us/library/ms178763.aspx
> is SQL2k check the SQL Errorlog \ Windows Application for Errors
> cheers,
> Andy.
>
> "jlopes151" <jlopes151@.discussions.microsoft.com> wrote in message
> news:363D1BB3-69C2-49E3-A77B-660117628D48@.microsoft.com...
>
>
|||Problem solved with the SP4 update.
"jlopes151" wrote:
[vbcol=seagreen]
> The errorlog has it listening on Shared Memory, & Named Pipes even though
> Named Pipes & TCP/IP protocols are enabled in the SQL Network Server Utility.
> I tried to scrambble the protocols by disabling and restarting the server,
> but the TCP/IP protocol doesn't show.
> "Andy Ball" wrote:

Help:how can i use sql server 2000 in Windows 2003

Windows 2003,sql server
How can i connect sql server 2000?
Unable to get a linked server working.
Please help me,thanks
gouki-- gouki wrote: --
Windows 2003,sql server
How can i connect sql server 2000?
Unable to get a linked server working.
Please help me,thanks
gouki
You should explain it in details, how did you installed it and how did you s
et it up?
How are we supposed to answer you if we don't have details?|||MS SQL 2000 with Service Pack 3 is a minimum requirement to run on
Win2003.
Further problem, please explain it in detail
kennethgoh
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message735124.html

Help:how can i use sql server 2000 in Windows 2003

Windows 2003,sql server
How can i connect sql server 2000?
Unable to get a linked server working.
Please help me,thanks
gouki
-- gouki wrote: --
Windows 2003,sql server
How can i connect sql server 2000?
Unable to get a linked server working.
Please help me,thanks
gouki
You should explain it in details, how did you installed it and how did you set it up?
How are we supposed to answer you if we don't have details?
|||MS SQL 2000 with Service Pack 3 is a minimum requirement to run on Win2003.
Further problem, please explain it in detail

Help: SQL 2000 connection error(.NET 2.0, VS 2005)

Moderated by XIII, please use a normal font size for better readability:

for some reason, my web application can not connect to my SQL 2000

my application is based on .net 2.0 (IIS 5.1) using vs 2005workstation does not install any sql serversql 2000 locates at the remote server.the sql server can be connected via vs environment (data connnection), therefore, i think the connection string, server name and instance name is correcti have tried all the solution i can find online, but it is not workingLocalSQLServer connection string has been removed in GobalSettingalso remove all default connection string in web.config (<clear />)aspnet_regsql can register the sql 2000 db successfulvs 2005 can access and display the data in sql 2000 quite wellhas been reboot lots of times.still bug out

any body have any idea? thanks, it already costs me the whole day

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

Can you telnet to the remote server (test TCP/IP)? And how about "net use\\servername\IPC$" the remote server (test Named pipe)? You can take a look at this post:

http://forums.asp.net/thread/1266057.aspx

|||

Thank Jay,

I can telnet to the remote server. Actually, I think the connection to the remote server is correct (in VS 2005 environment the data can be display quite well), the only problem is .NET 2.0 always think the remote server is SQL 2005. I have removed the localSQLServer connection string in web.config file (<clear />) but still not working.

|||

Then how about force to use TCP/IP to connect? You can do this by usingtcp:myinstance,portas Data Source, where port is the tcp port used the SQL instance service. Actually there should be no difference when connect to SQL2005 or SQL2000, you can take a look at this article which shows how to place membership on SQL2000:

http://weblogs.asp.net/scottgu/archive/2005/08/25/423703.aspx

Help: I can open my database in Management Studio, but can't connect it in Integration Services

Received error tip:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

I'm using the Evaluation Edition of SQL Server 2005, Windows XP SP2 Home Edition.

I have disabled the firewall.

You need to enable remote connections:

http://www.sqlserver2005.de/Sharedfiles/remoteconnection.jpg

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

Yes, I have enable remote connections, but still wrong.

Can the Home Edition of Windows XP support SQL Server?

|||

Hi, only the developer edition and the express edition are supposed to work on Windows XP Home (as of the offical system requirements, didn′t tested that out yet). Let me hear some feedback if that worked for you.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||I have installed SQL Server Evaluation Edition on Windows XP Home Edition. It can work. In the Management Studio, the database can be opened and executed. The only one problem is that in the reporting services, the database can't be connetcted.

HELP: How do I pass variables from Control Flow to Data Flow

I have an Execute SQL Task that returns a Full Rowset from a SQL Server table and assigns it to a variable objRecs. I connect that to a foreach container with an ADO enumerator using objRecs variable and Rows in first table mode. I defined variables and mapped them to the columns.

I tested this by placing a Script task inside the foreach container and displaying the variables in a messagebox.

Now, for each row, I want to write a record to an MS Access table and then update a column back in the original SQL Server table where I retreived data in the Execute SQL task (i have the primary key). If I drop a Data Flow Task inside my foreach container, how do I pass the variables as input to an OLE DB Destination on the Data Flow?

Also, how would I update the original source table where source.id = objRects.id?

Thank you for your assistance. I have spent the day trying to figure this out (and thought it would be simple), but I am just not getting SSIS. Sorry if this has been covered.

Thanks,

Steve

smcneese wrote:

I have an Execute SQL Task that returns a Full Rowset from a SQL Server table and assigns it to a variable objRecs. I connect that to a foreach container with an ADO enumerator using objRecs variable and Rows in first table mode. I defined variables and mapped them to the columns.

I tested this by placing a Script task inside the foreach container and displaying the variables in a messagebox.

Now, for each row, I want to write a record to an MS Access table and then update a column back in the original SQL Server table where I retreived data in the Execute SQL task (i have the primary key). If I drop a Data Flow Task inside my foreach container, how do I pass the variables as input to an OLE DB Destination on the Data Flow?

Also, how would I update the original source table where source.id = objRects.id?

Thank you for your assistance. I have spent the day trying to figure this out (and thought it would be simple), but I am just not getting SSIS. Sorry if this has been covered.

Thanks,

Steve

You can use the Derived Column Component to put variable values into the pipeline.

-Jamie

|||Use a multicast and an OLE DB Command to perform the update on the original table.|||

I looked at this, but the Derived Column Component requires an input also. How do I configure that?

Thanks,

Steve

|||

smcneese wrote:

I looked at this, but the Derived Column Component requires an input also. How do I configure that?

Thanks,

Steve

You can't use Derived Column Component as a source adapter so in this case you'll have to use a script component.

I would question as to whether this is really what you want to do though. Executing a data-flow just to process one row of data with one column in it seems like the proverbial sledgehammer to crack a nut. What are you trying to achieve exactly?

-Jamie

|||

I question it myself. ;) I am trying to perform what I thought was a simple task, but I don't know DTS/SSIS well enough to know the correct approach. I spent all day trying to read articles to understand, but I am just not getting it.

I have a table is SQL Server 2005 that gets status records written to it for events that occur on wireless phones. When a record is written into this table, I need to write a record into a table of a legacy application running in Access. My original thought was to write a managed stored procedure in C# but someone suggested SSIS so I thought I would give it a try. I would think this to be a simple problem to solve and exactly what SSIS is for, but I cannot figure it out.

Can you or someone point me in the right direction? My current approach used an Execute SQL task to read all of the records that have not been processed. Then I used a Foreach container thinking I could take each row, write it to Access and then update that original source row to indicate it was processed. I would prefer not to do it row by row, but the source table is constantly being written to so that needs to be accounted for. Any help for your experts would be greatly appreciated.

Thanks,

Steve

|||

smcneese wrote:

I question it myself. ;) I am trying to perform what I thought was a simple task, but I don't know DTS/SSIS well enough to know the correct approach. I spent all day trying to read articles to understand, but I am just not getting it.

I have a table is SQL Server 2005 that gets status records written to it for events that occur on wireless phones. When a record is written into this table, I need to write a record into a table of a legacy application running in Access. My original thought was to write a managed stored procedure in C# but someone suggested SSIS so I thought I would give it a try. I would think this to be a simple problem to solve and exactly what SSIS is for, but I cannot figure it out.

Can you or someone point me in the right direction? My current approach used an Execute SQL task to read all of the records that have not been processed. Then I used a Foreach container thinking I could take each row, write it to Access and then update that original source row to indicate it was processed. I would prefer not to do it row by row, but the source table is constantly being written to so that needs to be accounted for. Any help for your experts would be greatly appreciated.

Thanks,

Steve

I don't really see a problem updating the table while it is being written to. Modern RDBMSs are supposed to be handle multiple concurrent connections to the same resource - that's kinda the point.

However, you say that when a record is written to the table in SQL Server 2005 you need to write it to the Access application. That is inherently a real-time operation and SSIS is a tool for batch operations. Given that 10000foot view of the problem I don't think SSIS is what you want. If you do NOT need to write to the access application at the same time as the record arrives then this becomes more of a batch operation and SSIS will be more suitable.

-Jamie

|||

I should have stated "near real time". Doing this batch every x minutes is fine. My point was about concurrent operation on the RDBMS. If I use and ADO .NET Input on the Data Flow with the appropriate SQL Statement to select my records I can then pass the results of that to the OLE ADO Ouput for Access. Now how can I use that same result set to got back and update my source table "processed" column so they don't get picked up again the next time the batch process runs? Can I split the output of the ADO.NET Input and use it as input to two other processes? Is that the way to do it?

Thanks for your help Jamie!

|||

smcneese wrote:

I should have stated "near real time". Doing this batch every x minutes is fine. My point was about concurrent operation on the RDBMS. If I use and ADO .NET Input on the Data Flow with the appropriate SQL Statement to select my records I can then pass the results of that to the OLE ADO Ouput for Access. Now how can I use that same result set to got back and update my source table "processed" column so they don't get picked up again the next time the batch process runs? Can I split the output of the ADO.NET Input and use it as input to two other processes? Is that the way to do it?

Thanks for your help Jamie!

Yes, that is the way to do it. And jwelch replied on this thread telling you exactly how.

-Jamie

|||

All,

Thank you for all of your help. Everything finally clicked on how this all works. Solution working fine, tested and in production.

Thanks,

Steve

|||

smcneese wrote:

All,

Thank you for all of your help. Everything finally clicked on how this all works. Solution working fine, tested and in production.

Thanks,

Steve

Good news. A happy customer for a change

Help: error when trying to connect to server using sql server 2005 express

Dear all,

I have installed sql server 2005 Express with SQLADV.exe. But when I open Management Studio Express it has error:

Can not connect to server

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error locating Server/Instance Specified).

I searched on google but did not find any solution. Anyone know about that, please help me.

check this link http://blogs.msdn.com/sql_protocols/archive/2006/09/30/SQL-Server-2005-Remote-Connectivity-Issue-TroubleShooting.aspx

there are few things to be done to access database engine

(a) Remote connection to be enabled

(b) Create exception if firewall is enabled on this srever

(c) start SQL Browser service

(d) check the protocols

Madhu

|||

Dear Madhu K Nair,

I just use my local computer to test, how can I check for protocol and should I do it. Now I just use my computer to create a website and database in my computer too.

|||

check this http://support.microsoft.com/kb/914277

Madhu

|||

Please check my blog for this:

http://blogs.msdn.com/sql_protocols/archive/2007/05/13/sql-network-interfaces-error-26-error-locating-server-instance-specified.aspx

HELP: ASP.NET won''t connect to SQLexpress after deploying to IIS, try a lot of things...

Hello,

I have finish building my ASP.NET site using VS 2005 and it compile just fine. Than I try hosting it to the web via IIS v5.1 and I am getting permission error from SQL express.

I have posted a detail question in experts-exchange.com and since you need a user account to even view the thread, I have taken the liberty to save the thread as .html file and host it to my ISP site. You can see the detail problem I am having here: http://users.accesscomm.ca/mm/EEdetail.html

I am going to list out some stuff I have done:

1. I have two database that need access, the ASPNETDB.mdf for user login and another database (PhotoDataBase.mdf) to store information relating to the photo I uploaded to my ASP.NET site.

2. I have already follow this How to site: http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx and setup:
- TCP/IP enable, as shown here:
- I have started SQL Browser service
- The firewall part I am not so sure about. I am currently using Zonealarm....

3. I have installed SQL Server Management Studio Express(SSMSE) and attach the two database to it.

4. I have set SSMSE server properties to accept both SQL and window authentication.

5. I have made sure that both database "read only" setting to false

6. I have setup SQL login with User ID = SQLLOGIN

Here is the original connection in web.config:
<add name="ConnectionString"
connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=|Da

taDirectory|\PhotoDataBase.mdf;Integrated Security=True;User Instance=True"
providerName="System.Data.SqlClient" />

and here is the new connection I just type in web.config that replace the original one:
<add name="ConnectionString"
connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\PhotoDataBase.mdf; Server=MINGDESKTOP; Integrated Security=False; uid=SQLLOGIN; Password=XXXXXX;"
providerName="System.Data.SqlClient" />

and the error i get are the follow:

Server Error in '/' Application.
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

7. I did haven't done much to ASPNETDB.mdf yet and the error i get right now are the following:

_

___
Server Error in '/' Application.
Cannot open user default database. Login failed.
Login failed for user 'MINGDESKTOP\ASPNET'.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: Cannot open user default database. Login failed.
Login failed for user 'MINGDESKTOP\ASPNET'.
__

Please help! I am really running out of ideas.... and I need to have this setup in a few days....

Thanks!

These two links will take you in the right direction but you still have the ASPNETDB as a User Instance database which is not supported in other editions of SQL Server so you need to correct that also. In Asp.net deployment takes careful planning or any part of the application can stop the deployment. Hope this helps.

http://geekswithblogs.net/ranganh/archive/2005/04/25/37613.aspx

http://weblogs.asp.net/scottgu/archive/2006/04/22/Always-set-the-_2200_applicationName_2200_-property-when-configuring-ASP.NET-2.0-Membership-and-other-Providers.aspx

|||

Caddre wrote:

These two links will take you in the right direction but you still have the ASPNETDB as a User Instance database which is not supported in other editions of SQL Server so you need to correct that also. In Asp.net deployment takes careful planning or any part of the application can stop the deployment. Hope this helps.

http://geekswithblogs.net/ranganh/archive/2005/04/25/37613.aspx

http://weblogs.asp.net/scottgu/archive/2006/04/22/Always-set-the-_2200_applicationName_2200_-property-when-configuring-ASP.NET-2.0-Membership-and-other-Providers.aspx

Thanks! This is the answer I needed!

|||

I am glad I could help.

Help..Error connecting to SQL Server

Hi,

I am writing my first aspx file to connect to a standalone SQL Server which is separated from the IIS webserver. The code is

<HTML>
<HEAD>
<TITLE>Store Locator</TITLE>
<script runat="server">
Sub Page_Load(ByVal Sender as Object, ByVal E as EventArgs)
if Not IsPostBack Then
Dim DBConn as OleDbConnection
Dim DBCommand As OleDbDataAdapter
Dim DSPageData as New DataSet
DBConn = New OleDbConnection("Provider=sqloledb;" _
& "server=dailyplanet;" _
& "Initial Catalog=JAVSTORE;" _
& "User Id=javtrader;" _
& "Password=rage123;")
DBCommand = New OleDbDataAdapter _
("Select * " _
& "From JAVInventory " _
& "Where ID > ((Select COUNT(ID) " _
& "From JAVInventory ) - 100)" _
& "Order By ID DESC", DBConn)
DBCommand.Fill(DSPageData, _
"RecentJAVs")
' ddlZipCode.DataSource = _
' DSPageData.Tables("RecentJAVs").DefaultView
' ddlZipCode.DataBind()
End If
End Sub

I used Visual .Net and Web Matrix and was able to connect to the sql server with the Data Connection to view the tables. However, when I use IIS or the Visual .Net debugger to run the aspx file, it get the following error.. please help..

Server Error in '/javtrade' Application.
------------------------

[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.OleDb.OleDbException: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

Source Error:

Line 21: & "From JAVInventory ) - 100)" _
Line 22: & "Order By ID DESC", DBConn)
Line 23: DBCommand.Fill(DSPageData, _
Line 24: "RecentJAVs")
Line 25: ' ddlZipCode.DataSource = _

Source File: c:\inetpub\wwwroot\javtrade\management.aspx Line: 23

Stack Trace:

[OleDbException (0x80004005): [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.]
System.Data.OleDb.OleDbConnection.ProcessResults(Int32 hr)
System.Data.OleDb.OleDbConnection.InitializeProvider()
System.Data.OleDb.OleDbConnection.Open()
System.Data.Common.DbDataAdapter.QuietOpen(IDbConnection connection, ConnectionState& originalState) +44
System.Data.Common.DbDataAdapter.FillFromCommand(Object data, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +304
System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +77
System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable) +36
ASP.management_aspx.Page_Load(Object Sender, EventArgs E) in c:\inetpub\wwwroot\javtrade\management.aspx:23
System.Web.UI.Control.OnLoad(EventArgs e) +67
System.Web.UI.Control.LoadRecursive() +35
System.Web.UI.Page.ProcessRequestMain() +731Two suggestions, one is to supply a 'server' name of localhost. The second is to make sure that the ASP.NET user has access to the SQL server.

Josh