Re: OT: MS SQL access
- From: Kent Wallace <kwallace@xxxxxxxxxxxxxxxxx>
- Date: Tue, 8 Aug 2006 12:50:38 -0600
I found the problem, conflicting port numbers used by MS SQL databases.
The error message was 19011 which tell you that the system was unable to
identify the error.
I feel Mr. Gates has enough money to hire someone to clean up his error
messages in the code.
Kent Wallace
-----Original Message-----
From: Captain Greb [mailto:grebs4hp@xxxxxxxxx]
Sent: Tuesday, August 08, 2006 10:29 AM
To: Kent Wallace
Subject: Re: OT: MS SQL access
What's the error message from your app, if any?
Does this only happen when you reboot, or do you lose connectivity
then reboot?
Are you on 2k or 2k5?
I've had issues with sql2k when the service packs weren't applied and
sometimes something would go wrong and connections would start
timing out and restarting the server.
After the reboot, make sure the server is fully up and running
before you test it. We've got a server with a flaky network card
and it doesn't reset unless we do a cold boot.
Make sure the SQL service is running on the server after the reboot.
Do you have some AV software running on the server?
Exclude MDB and LDB files.
Are you losing physical connectivity with the server?
Try pinging by IP address.
Try pinging by DNS name.
Try pinging by Windows name.
If that's all working, and you still can't connect,
try this (assumes windows xp):
telnet 1.2.3.4 ms-sql-s
That should connect to the sql server by ip address on the sql port.
hit return a few times.
to see if its accepting data.
control-] and quit to get out of telnet
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
.
- Prev by Date: Re: Limit a session to BA access only
- Next by Date: Re: OT: MS SQL access
- Previous by thread: Limit a session to BA access only
- Next by thread: Re: OT: MS SQL access
- Index(es):
Relevant Pages
|
