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:
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
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
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
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
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
]
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
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
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
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
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
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
12 matches
Mail list logo