RE: SQL server trouble

2002-05-30 Thread Dave Watts

> If you are able to figure out what service is grabbing 1433 
> ahead of sql server, I'd suggest changing the startup parameter 
> for that service to manual to allow sql to get it first. Of 
> course you then have to remember to manually start that other 
> service after every reboot.

Actually, you can configure your services to start in whatever order you'd
like. You have to edit the Registry and set the DependOnService key for the
second service so that it won't start until the first one has already
started.

Ray Camden pointed this out to me, I think; it came up with running
SiteMinder and SQL Server on the same server. SiteMinder had to start after
SQL Server, or no one would be able to log in!

Dave Watts, CTO, Fig Leaf Software 
http://www.figleaf.com/ 
phone: 202-797-5496 
fax: 202-797-5444
__
This list and all House of Fusion resources hosted by CFHosting.com. The place for 
dependable ColdFusion Hosting.
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists



Re: SQL server trouble

2002-05-30 Thread Mario Martinez

Thank you Rob again.
regards Mario

- Original Message -
From: "Rob Baxter" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Thursday, May 30, 2002 3:00 PM
Subject: RE: SQL server trouble


> If you are able to figure out what service is grabbing 1433 ahead of sql
> server, I'd suggest changing the startup parameter for that service to
> manual to allow sql to get it first. Of course you then have to remember
to
> manually start that other service after every reboot.
>
> 
>
> -Original Message-
> From: Mario Martinez [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 30, 2002 2:23 PM
> To: CF-Talk
> Subject: Re: SQL server trouble
>
>
> Tony:
> This file you are taking about  does not contain any info about port 1433.
> You can be sure I did a search in microsoft site before going to the list
,
> although  I did not find the right keyword combinations at the begining .
> After making a cousious search in the SQL Errorlog I found the right
keyword
> combination.
> thanks friend
> regards Mario
>
>
> - Original Message -
> From: <[EMAIL PROTECTED]>
> To: "CF-Talk" <[EMAIL PROTECTED]>
> Sent: Thursday, May 30, 2002 2:11 PM
> Subject: RE: SQL server trouble
>
>
> > just out curiosity. I wonder, if the next time this happens, if you
viewed
> > the services file, (c:\winnt\system32\drivers\etc\services) if it would
> tell
> > you what is hooked on that port. if it does, then you know what app is
the
> > culprit.
> >
> > Anthony Petruzzi
> > Webmaster
> > 954-321-4703
> > [EMAIL PROTECTED]
> > http://www.sheriff.org
> >
> >
> > -Original Message-
> > From: Mario Martinez [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, May 30, 2002 1:46 PM
> > To: CF-Talk
> > Subject: Re: SQL server trouble
> >
> >
> > Thank you for your responses friends.
> > I finally found the answer in www.microsoft.com  in the troubleshouting
> > section.
> > The problem was that somehow one winsock service(as the port asiggment
is
> > dinamically on it) was steeling the 1433 port and SQL server could not
> > listen in 1433 port. What I did was to stop all the services except the
> > defaults, restart the SQL service and restart the others services again,
> in
> > this way SQL server takes this port firts.
> > I have to work around it because it could happen again anytime
> > I restart the machine.
> >
> > Thanks for your concern
> >
> > regards Mario
> > - Original Message -
> > From: "Rob Baxter" <[EMAIL PROTECTED]>
> > To: "CF-Talk" <[EMAIL PROTECTED]>
> > Sent: Thursday, May 30, 2002 12:32 PM
> > Subject: RE: SQL server trouble
> >
> >
> > > check to make sure your SQL server is listening on tcp port 1433
(unless
> > you
> > > have changed the default port). You can either do a netstat -an from
the
> > sql
> > > box or from the client machine try
> > >
> > > telnet sql-server-ip 1433
> > >
> > > If you get a response your traffic is getting through. If not you've
> > either
> > > got something in the way (firewall) or a problem with your SQL network
> > > libraries. I actually just had this problem yesterday so if that is it
> > I'll
> > > tell you what worked for me. Have you made any configuration changes
to
> > SQL
> > > recently?
> > >
> > > 
> > >
> > > -Original Message-
> > > From: Mario Martinez [mailto:[EMAIL PROTECTED]]
> > > Sent: Thursday, May 30, 2002 12:10 PM
> > > To: CF-Talk
> > > Subject: SQL server trouble
> > >
> > >
> > > Hi all friends:
> > >
> > > I got a coldfusion system with an SQL server . Today I came in here
and
> I
> > > realize that I can't connect this SQL server from any other computer
> > through
> > > ODBC . I could do that before , now none of my remotly ODBC
connections
> > are
> > > working
> > > This is the error I receive when I try to connect remotly:
> > > Connection failed
> > > SQLState:'01000'
> > > SQL Server Error: 10061
> > > [Microsoft][ODBC SQL Server Driver ][TCP/IP
> > > Sockets]ConnectionOpen(connect()).
> > > Connection failed:
> > > SQLState: '08001'
> > > SQL Server Error: 11
> > > [Microsoft][ODBC SQL Server Driver]General network error. Check your
> > network
> > > documentation.
> > >
> > > Any ideas will be more than appreciate.
> > > regards
> > > Mario
> > >
> > >
> > >
> >
> >
>
> 
__
Structure your ColdFusion code with Fusebox. Get the official book at 
http://www.fusionauthority.com/bkinfo.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists



RE: SQL server trouble

2002-05-30 Thread Rob Baxter

If you are able to figure out what service is grabbing 1433 ahead of sql
server, I'd suggest changing the startup parameter for that service to
manual to allow sql to get it first. Of course you then have to remember to
manually start that other service after every reboot.



-Original Message-
From: Mario Martinez [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 30, 2002 2:23 PM
To: CF-Talk
Subject: Re: SQL server trouble


Tony:
This file you are taking about  does not contain any info about port 1433.
You can be sure I did a search in microsoft site before going to the list ,
although  I did not find the right keyword combinations at the begining .
After making a cousious search in the SQL Errorlog I found the right keyword
combination.
thanks friend
regards Mario


- Original Message -
From: <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Thursday, May 30, 2002 2:11 PM
Subject: RE: SQL server trouble


> just out curiosity. I wonder, if the next time this happens, if you viewed
> the services file, (c:\winnt\system32\drivers\etc\services) if it would
tell
> you what is hooked on that port. if it does, then you know what app is the
> culprit.
>
> Anthony Petruzzi
> Webmaster
> 954-321-4703
> [EMAIL PROTECTED]
> http://www.sheriff.org
>
>
> -Original Message-
> From: Mario Martinez [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 30, 2002 1:46 PM
> To: CF-Talk
> Subject: Re: SQL server trouble
>
>
> Thank you for your responses friends.
> I finally found the answer in www.microsoft.com  in the troubleshouting
> section.
> The problem was that somehow one winsock service(as the port asiggment is
> dinamically on it) was steeling the 1433 port and SQL server could not
> listen in 1433 port. What I did was to stop all the services except the
> defaults, restart the SQL service and restart the others services again,
in
> this way SQL server takes this port firts.
> I have to work around it because it could happen again anytime
> I restart the machine.
>
> Thanks for your concern
>
> regards Mario
> - Original Message -
> From: "Rob Baxter" <[EMAIL PROTECTED]>
> To: "CF-Talk" <[EMAIL PROTECTED]>
> Sent: Thursday, May 30, 2002 12:32 PM
> Subject: RE: SQL server trouble
>
>
> > check to make sure your SQL server is listening on tcp port 1433 (unless
> you
> > have changed the default port). You can either do a netstat -an from the
> sql
> > box or from the client machine try
> >
> > telnet sql-server-ip 1433
> >
> > If you get a response your traffic is getting through. If not you've
> either
> > got something in the way (firewall) or a problem with your SQL network
> > libraries. I actually just had this problem yesterday so if that is it
> I'll
> > tell you what worked for me. Have you made any configuration changes to
> SQL
> > recently?
> >
> > 
> >
> > -Original Message-
> > From: Mario Martinez [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, May 30, 2002 12:10 PM
> > To: CF-Talk
> > Subject: SQL server trouble
> >
> >
> > Hi all friends:
> >
> > I got a coldfusion system with an SQL server . Today I came in here and
I
> > realize that I can't connect this SQL server from any other computer
> through
> > ODBC . I could do that before , now none of my remotly ODBC connections
> are
> > working
> > This is the error I receive when I try to connect remotly:
> > Connection failed
> > SQLState:'01000'
> > SQL Server Error: 10061
> > [Microsoft][ODBC SQL Server Driver ][TCP/IP
> > Sockets]ConnectionOpen(connect()).
> > Connection failed:
> > SQLState: '08001'
> > SQL Server Error: 11
> > [Microsoft][ODBC SQL Server Driver]General network error. Check your
> network
> > documentation.
> >
> > Any ideas will be more than appreciate.
> > regards
> > Mario
> >
> >
> >
>
>

__
Get the mailserver that powers this list at http://www.coolfusion.com
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists



Re: SQL server trouble

2002-05-30 Thread Mario Martinez

Tony:
This file you are taking about  does not contain any info about port 1433.
You can be sure I did a search in microsoft site before going to the list ,
although  I did not find the right keyword combinations at the begining .
After making a cousious search in the SQL Errorlog I found the right keyword
combination.
thanks friend
regards Mario


- Original Message -
From: <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Thursday, May 30, 2002 2:11 PM
Subject: RE: SQL server trouble


> just out curiosity. I wonder, if the next time this happens, if you viewed
> the services file, (c:\winnt\system32\drivers\etc\services) if it would
tell
> you what is hooked on that port. if it does, then you know what app is the
> culprit.
>
> Anthony Petruzzi
> Webmaster
> 954-321-4703
> [EMAIL PROTECTED]
> http://www.sheriff.org
>
>
> -Original Message-
> From: Mario Martinez [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 30, 2002 1:46 PM
> To: CF-Talk
> Subject: Re: SQL server trouble
>
>
> Thank you for your responses friends.
> I finally found the answer in www.microsoft.com  in the troubleshouting
> section.
> The problem was that somehow one winsock service(as the port asiggment is
> dinamically on it) was steeling the 1433 port and SQL server could not
> listen in 1433 port. What I did was to stop all the services except the
> defaults, restart the SQL service and restart the others services again,
in
> this way SQL server takes this port firts.
> I have to work around it because it could happen again anytime
> I restart the machine.
>
> Thanks for your concern
>
> regards Mario
> - Original Message -
> From: "Rob Baxter" <[EMAIL PROTECTED]>
> To: "CF-Talk" <[EMAIL PROTECTED]>
> Sent: Thursday, May 30, 2002 12:32 PM
> Subject: RE: SQL server trouble
>
>
> > check to make sure your SQL server is listening on tcp port 1433 (unless
> you
> > have changed the default port). You can either do a netstat -an from the
> sql
> > box or from the client machine try
> >
> > telnet sql-server-ip 1433
> >
> > If you get a response your traffic is getting through. If not you've
> either
> > got something in the way (firewall) or a problem with your SQL network
> > libraries. I actually just had this problem yesterday so if that is it
> I'll
> > tell you what worked for me. Have you made any configuration changes to
> SQL
> > recently?
> >
> > 
> >
> > -Original Message-
> > From: Mario Martinez [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, May 30, 2002 12:10 PM
> > To: CF-Talk
> > Subject: SQL server trouble
> >
> >
> > Hi all friends:
> >
> > I got a coldfusion system with an SQL server . Today I came in here and
I
> > realize that I can't connect this SQL server from any other computer
> through
> > ODBC . I could do that before , now none of my remotly ODBC connections
> are
> > working
> > This is the error I receive when I try to connect remotly:
> > Connection failed
> > SQLState:'01000'
> > SQL Server Error: 10061
> > [Microsoft][ODBC SQL Server Driver ][TCP/IP
> > Sockets]ConnectionOpen(connect()).
> > Connection failed:
> > SQLState: '08001'
> > SQL Server Error: 11
> > [Microsoft][ODBC SQL Server Driver]General network error. Check your
> network
> > documentation.
> >
> > Any ideas will be more than appreciate.
> > regards
> > Mario
> >
> >
> >
>
> 
__
Signup for the Fusion Authority news alert and keep up with the latest news in 
ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists



RE: SQL server trouble

2002-05-30 Thread Dave Watts

> I wonder, if the next time this happens, if you viewed the 
> services file, (c:\winnt\system32\drivers\etc\services) if 
> it would tell you what is hooked on that port. if it does, 
> then you know what app is the culprit.

The services file doesn't reflect what's actually listening; it just lists
standard ports used by services.

There are apps which can determine what's listening at a specific port, and
netstat in XP does this, which is kind of neat.

Dave Watts, CTO, Fig Leaf Software 
http://www.figleaf.com/ 
phone: 202-797-5496 
fax: 202-797-5444
__
Your ad could be here. Monies from ads go to support these lists and provide more 
resources for the community. http://www.fusionauthority.com/ads.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists



RE: SQL server trouble

2002-05-30 Thread Tony_Petruzzi

just out curiosity. I wonder, if the next time this happens, if you viewed
the services file, (c:\winnt\system32\drivers\etc\services) if it would tell
you what is hooked on that port. if it does, then you know what app is the
culprit.

Anthony Petruzzi
Webmaster
954-321-4703
[EMAIL PROTECTED]
http://www.sheriff.org


-Original Message-
From: Mario Martinez [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 30, 2002 1:46 PM
To: CF-Talk
Subject: Re: SQL server trouble


Thank you for your responses friends.
I finally found the answer in www.microsoft.com  in the troubleshouting
section.
The problem was that somehow one winsock service(as the port asiggment is
dinamically on it) was steeling the 1433 port and SQL server could not
listen in 1433 port. What I did was to stop all the services except the
defaults, restart the SQL service and restart the others services again, in
this way SQL server takes this port firts.
I have to work around it because it could happen again anytime
I restart the machine.

Thanks for your concern

regards Mario
- Original Message -
From: "Rob Baxter" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Thursday, May 30, 2002 12:32 PM
Subject: RE: SQL server trouble


> check to make sure your SQL server is listening on tcp port 1433 (unless
you
> have changed the default port). You can either do a netstat -an from the
sql
> box or from the client machine try
>
> telnet sql-server-ip 1433
>
> If you get a response your traffic is getting through. If not you've
either
> got something in the way (firewall) or a problem with your SQL network
> libraries. I actually just had this problem yesterday so if that is it
I'll
> tell you what worked for me. Have you made any configuration changes to
SQL
> recently?
>
> 
>
> -Original Message-
> From: Mario Martinez [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 30, 2002 12:10 PM
> To: CF-Talk
> Subject: SQL server trouble
>
>
> Hi all friends:
>
> I got a coldfusion system with an SQL server . Today I came in here and I
> realize that I can't connect this SQL server from any other computer
through
> ODBC . I could do that before , now none of my remotly ODBC connections
are
> working
> This is the error I receive when I try to connect remotly:
> Connection failed
> SQLState:'01000'
> SQL Server Error: 10061
> [Microsoft][ODBC SQL Server Driver ][TCP/IP
> Sockets]ConnectionOpen(connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 11
> [Microsoft][ODBC SQL Server Driver]General network error. Check your
network
> documentation.
>
> Any ideas will be more than appreciate.
> regards
> Mario
>
>
> 

__
Signup for the Fusion Authority news alert and keep up with the latest news in 
ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists



RE: SQL server trouble

2002-05-30 Thread Tony_Petruzzi

that's the first place to go whenever you have problem with a Microsoft
product. Second is google groups. this list should be a last ditch effort.

Anthony Petruzzi
Webmaster
954-321-4703
[EMAIL PROTECTED]
http://www.sheriff.org


-Original Message-
From: Mario Martinez [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 30, 2002 1:45 PM
To: CF-Talk
Subject: Re: SQL server trouble


Thank you for your responses friends.
I finally found the answer in www.microsoft.com  in the troubleshouting
section.Down here  the article URL
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q293107
I have to work around it because it could happen again anytime
I restart the machine.

Thanks for your concern , thank you Rob and the others friends

regards Mario
- Original Message -
From: "Rob Baxter" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Thursday, May 30, 2002 12:32 PM
Subject: RE: SQL server trouble


> check to make sure your SQL server is listening on tcp port 1433 (unless
you
> have changed the default port). You can either do a netstat -an from the
sql
> box or from the client machine try
>
> telnet sql-server-ip 1433
>
> If you get a response your traffic is getting through. If not you've
either
> got something in the way (firewall) or a problem with your SQL network
> libraries. I actually just had this problem yesterday so if that is it
I'll
> tell you what worked for me. Have you made any configuration changes to
SQL
> recently?
>
> 
>
> -Original Message-
> From: Mario Martinez [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 30, 2002 12:10 PM
> To: CF-Talk
> Subject: SQL server trouble
>
>
> Hi all friends:
>
> I got a coldfusion system with an SQL server . Today I came in here and I
> realize that I can't connect this SQL server from any other computer
through
> ODBC . I could do that before , now none of my remotly ODBC connections
are
> working
> This is the error I receive when I try to connect remotly:
> Connection failed
> SQLState:'01000'
> SQL Server Error: 10061
> [Microsoft][ODBC SQL Server Driver ][TCP/IP
> Sockets]ConnectionOpen(connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 11
> [Microsoft][ODBC SQL Server Driver]General network error. Check your
network
> documentation.
>
> Any ideas will be more than appreciate.
> regards
> Mario
>
>
> 

__
Your ad could be here. Monies from ads go to support these lists and provide more 
resources for the community. http://www.fusionauthority.com/ads.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists



Re: SQL server trouble

2002-05-30 Thread Mario Martinez

Thank you for your responses friends.
I finally found the answer in www.microsoft.com  in the troubleshouting
section.
The problem was that somehow one winsock service(as the port asiggment is
dinamically on it) was steeling the 1433 port and SQL server could not
listen in 1433 port. What I did was to stop all the services except the
defaults, restart the SQL service and restart the others services again, in
this way SQL server takes this port firts.
I have to work around it because it could happen again anytime
I restart the machine.

Thanks for your concern

regards Mario
- Original Message -
From: "Rob Baxter" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Thursday, May 30, 2002 12:32 PM
Subject: RE: SQL server trouble


> check to make sure your SQL server is listening on tcp port 1433 (unless
you
> have changed the default port). You can either do a netstat -an from the
sql
> box or from the client machine try
>
> telnet sql-server-ip 1433
>
> If you get a response your traffic is getting through. If not you've
either
> got something in the way (firewall) or a problem with your SQL network
> libraries. I actually just had this problem yesterday so if that is it
I'll
> tell you what worked for me. Have you made any configuration changes to
SQL
> recently?
>
> 
>
> -Original Message-
> From: Mario Martinez [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 30, 2002 12:10 PM
> To: CF-Talk
> Subject: SQL server trouble
>
>
> Hi all friends:
>
> I got a coldfusion system with an SQL server . Today I came in here and I
> realize that I can't connect this SQL server from any other computer
through
> ODBC . I could do that before , now none of my remotly ODBC connections
are
> working
> This is the error I receive when I try to connect remotly:
> Connection failed
> SQLState:'01000'
> SQL Server Error: 10061
> [Microsoft][ODBC SQL Server Driver ][TCP/IP
> Sockets]ConnectionOpen(connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 11
> [Microsoft][ODBC SQL Server Driver]General network error. Check your
network
> documentation.
>
> Any ideas will be more than appreciate.
> regards
> Mario
>
>
> 
__
Structure your ColdFusion code with Fusebox. Get the official book at 
http://www.fusionauthority.com/bkinfo.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists



Re: SQL server trouble

2002-05-30 Thread Mario Martinez

Thank you for your responses friends.
I finally found the answer in www.microsoft.com  in the troubleshouting
section.Down here  the article URL
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q293107
I have to work around it because it could happen again anytime
I restart the machine.

Thanks for your concern , thank you Rob and the others friends

regards Mario
- Original Message -
From: "Rob Baxter" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Thursday, May 30, 2002 12:32 PM
Subject: RE: SQL server trouble


> check to make sure your SQL server is listening on tcp port 1433 (unless
you
> have changed the default port). You can either do a netstat -an from the
sql
> box or from the client machine try
>
> telnet sql-server-ip 1433
>
> If you get a response your traffic is getting through. If not you've
either
> got something in the way (firewall) or a problem with your SQL network
> libraries. I actually just had this problem yesterday so if that is it
I'll
> tell you what worked for me. Have you made any configuration changes to
SQL
> recently?
>
> 
>
> -Original Message-
> From: Mario Martinez [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 30, 2002 12:10 PM
> To: CF-Talk
> Subject: SQL server trouble
>
>
> Hi all friends:
>
> I got a coldfusion system with an SQL server . Today I came in here and I
> realize that I can't connect this SQL server from any other computer
through
> ODBC . I could do that before , now none of my remotly ODBC connections
are
> working
> This is the error I receive when I try to connect remotly:
> Connection failed
> SQLState:'01000'
> SQL Server Error: 10061
> [Microsoft][ODBC SQL Server Driver ][TCP/IP
> Sockets]ConnectionOpen(connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 11
> [Microsoft][ODBC SQL Server Driver]General network error. Check your
network
> documentation.
>
> Any ideas will be more than appreciate.
> regards
> Mario
>
>
> 
__
Your ad could be here. Monies from ads go to support these lists and provide more 
resources for the community. http://www.fusionauthority.com/ads.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists



Re: SQL server trouble

2002-05-30 Thread Alex

can you ping the database machine?

On Thu, 30 May 2002, Mario Martinez wrote:

> Hi all friends:
> 
> I got a coldfusion system with an SQL server . Today I came in here and I
> realize that I can't connect this SQL server from any other computer through
> ODBC . I could do that before , now none of my remotly ODBC connections are
> working
> This is the error I receive when I try to connect remotly:
> Connection failed
> SQLState:'01000'
> SQL Server Error: 10061
> [Microsoft][ODBC SQL Server Driver ][TCP/IP
> Sockets]ConnectionOpen(connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 11
> [Microsoft][ODBC SQL Server Driver]General network error. Check your network
> documentation.
> 
> Any ideas will be more than appreciate.
> regards
> Mario
> 
> 
__
Get the mailserver that powers this list at http://www.coolfusion.com
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists



RE: SQL server trouble

2002-05-30 Thread Rob Baxter

check to make sure your SQL server is listening on tcp port 1433 (unless you
have changed the default port). You can either do a netstat -an from the sql
box or from the client machine try

telnet sql-server-ip 1433

If you get a response your traffic is getting through. If not you've either
got something in the way (firewall) or a problem with your SQL network
libraries. I actually just had this problem yesterday so if that is it I'll
tell you what worked for me. Have you made any configuration changes to SQL
recently?



-Original Message-
From: Mario Martinez [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 30, 2002 12:10 PM
To: CF-Talk
Subject: SQL server trouble


Hi all friends:

I got a coldfusion system with an SQL server . Today I came in here and I
realize that I can't connect this SQL server from any other computer through
ODBC . I could do that before , now none of my remotly ODBC connections are
working
This is the error I receive when I try to connect remotly:
Connection failed
SQLState:'01000'
SQL Server Error: 10061
[Microsoft][ODBC SQL Server Driver ][TCP/IP
Sockets]ConnectionOpen(connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 11
[Microsoft][ODBC SQL Server Driver]General network error. Check your network
documentation.

Any ideas will be more than appreciate.
regards
Mario


__
Signup for the Fusion Authority news alert and keep up with the latest news in 
ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists



Re: SQL server trouble

2002-05-30 Thread Stephen Moretti

Mario,

Sounds like your SQL Server down or someone closed up the firewall between
your CF Server and your SQL Server.

Can you get access to your SQL Server by any other means? ie. Enterprise
Manager?

Regards

Stephen
- Original Message -
From: "Mario Martinez" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Thursday, May 30, 2002 5:09 PM
Subject: SQL server trouble


> Hi all friends:
>
> I got a coldfusion system with an SQL server . Today I came in here and I
> realize that I can't connect this SQL server from any other computer
through
> ODBC . I could do that before , now none of my remotly ODBC connections
are
> working
> This is the error I receive when I try to connect remotly:
> Connection failed
> SQLState:'01000'
> SQL Server Error: 10061
> [Microsoft][ODBC SQL Server Driver ][TCP/IP
> Sockets]ConnectionOpen(connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 11
> [Microsoft][ODBC SQL Server Driver]General network error. Check your
network
> documentation.
>
> Any ideas will be more than appreciate.
> regards
> Mario
>
> 
__
Signup for the Fusion Authority news alert and keep up with the latest news in 
ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists