Connectivity problem

Hi,
I have 3 SQL servers 7, and since yesterday, some of my
clients started receiving different error messages in the
middle of doing something like reporting, or editing.
(they run different applications).
However when i checked the event logs on all servers there
is no error message there. all different messages include
a "General network error" for example one of them is:
SQL Server Message 10054, Possible network error Write to
SQL Server Failed. General Network Error. Check your
documentation. Debugging info: sqlCompile...
Usually if I reboot their WS, thats temperary fixs their
problem.
Does anyone have any idea how to deal with this problem, I
am monitoring different switches but cannot see any
problem. Also checked ODBC settings all fine, and we have
these setting for a couple of years with no problem.
Thanks in advance for any help-RobAre the errors occurring on all 3 SQL Servers or just one SQL Server?
How is the health of the network? Are the switches in good working order?
How about the NIC's in the SQL Server machines? Is your DNS acting up?
What service packs have you applied recently to any equipment in the process
(Client, Server, routers/switches etc.).
What has changed in the last few weeks?
Rick Sawtell
MCT, MCSD, MCDBA
"Rob" <Rob@.nul.ca> wrote in message
news:d37d01c48ab6$39d66790$a601280a@.phx.gbl...
> Hi,
> I have 3 SQL servers 7, and since yesterday, some of my
> clients started receiving different error messages in the
> middle of doing something like reporting, or editing.
> (they run different applications).
> However when i checked the event logs on all servers there
> is no error message there. all different messages include
> a "General network error" for example one of them is:
> SQL Server Message 10054, Possible network error Write to
> SQL Server Failed. General Network Error. Check your
> documentation. Debugging info: sqlCompile...
> Usually if I reboot their WS, thats temperary fixs their
> problem.
> Does anyone have any idea how to deal with this problem, I
> am monitoring different switches but cannot see any
> problem. Also checked ODBC settings all fine, and we have
> these setting for a couple of years with no problem.
> Thanks in advance for any help-Rob
>|||On 2 of them. The network health is good and I can not see
any problem. As long as I am aware, we havent changed
anything recently and this problem startd since a couple
days ago.
Rob
>--Original Message--
>Are the errors occurring on all 3 SQL Servers or just one
SQL Server?
>How is the health of the network? Are the switches in
good working order?
>How about the NIC's in the SQL Server machines? Is your
DNS acting up?
>What service packs have you applied recently to any
equipment in the process
>(Client, Server, routers/switches etc.).
>What has changed in the last few weeks?
>
>Rick Sawtell
>MCT, MCSD, MCDBA
>
>
>"Rob" <Rob@.nul.ca> wrote in message
>news:d37d01c48ab6$39d66790$a601280a@.phx.gbl...
>> Hi,
>> I have 3 SQL servers 7, and since yesterday, some of my
>> clients started receiving different error messages in
the
>> middle of doing something like reporting, or editing.
>> (they run different applications).
>> However when i checked the event logs on all servers
there
>> is no error message there. all different messages
include
>> a "General network error" for example one of them is:
>> SQL Server Message 10054, Possible network error Write
to
>> SQL Server Failed. General Network Error. Check your
>> documentation. Debugging info: sqlCompile...
>> Usually if I reboot their WS, thats temperary fixs their
>> problem.
>> Does anyone have any idea how to deal with this
problem, I
>> am monitoring different switches but cannot see any
>> problem. Also checked ODBC settings all fine, and we
have
>> these setting for a couple of years with no problem.
>> Thanks in advance for any help-Rob
>>
>
>.
>|||Hi Bob,
Thanks for using MSDN Managed Newsgroup!
From your descriptions, I understood that your SQL7 received different
error and General Network Error. Have I understood you? If their is
anything I misunderstood, please feel free to let me know.
First of all, Would you please show me a detailed descriptions of what kind
of error message it will show? Is it possible for you to paste your latest
error log here?
Secondly, based on my scope, "General network error" doesn't mean a network
issue in most cases, it is a very common error that I am afraid we need
more time troubleshooting.
Thirdly, you said it will temperarily fix the problem by rebooting. How
long after rebooting will this kind of error occurs again?
Last but not the least, if it is an urgent one, you can contact Microsoft
Product Support directly to discuss additional support options you may have
available, by contacting us at 1-(800)936-5800 or by choosing one of the
options listed at
http://support.microsoft.com/default.aspx?scid=sz;en-us;top.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

Connectivity Issue

Hi Folks,

Im a bit stuck with this one.

Have a SQL 2000 Instance that we require a load of clients to connect to.

It seems that as soon as we get the MSSQL$Service to run under a domain account we can only authenticate to SQL Server if we set up a client alias.

Under a local system account it seems to authenticate without any issues.

This is a real pain as I don't want to have to set client ailas up on every one of my clients.

Anybody seen this sort of issue before.

Thanks in advanceAddtional Info :

The domain account that is running the mssql$service is in a differnet domain from the users that are connecting to SQL Server. There is a trust in place between the two domains.

The connection error is your usual null user not associated with a trusted connection.

The error log says SQL is listening on TCP, Shared Mem and Named Pipes|||Sorted

Bloody Group Policy on the service account.

Service Account had to get additional permissions.

Thanks|||This sounds cool .. any idea what permissions were required for the service accounts ?

Thanks,
-Ranjit

----------------------
Its OK to be a fool for 5 minutes than for the rest of your life ( Old Japanese Proverb )|||To summarise the problem for future reference:

Situation
Windows Server 2003 in RBSRES01.Net domain
SQL Server 2000 + SP4 (and any other appropriate patches)
SQL Service running under domain account (either EUROPA or RBSRES01)

Connection From
Enterprise Manager or ODBC (DSN or Ms Access)
Any client machine (workstation or server) without a named pipe client alias setup

Error
Server: Msg 18452, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.

Root Cause
As per the below Microsoft KB article the account running SQL server must have certain windows rights. To grant these rights under the RBSRES01 group policy setup, the account needs to be a member of the following domain local security groups:
sSRV-AssignPrimaryToken-Privilege
sSRV-BatchLogon-Right
sSRV-ChangeNotify-Privilege
sSRV-EnableDelegation-Privilege
sSRV-Impersonate-Privilege
sSRV-LockMemory-Privilege
sSRV-ServiceLogon-Right

http://support.microsoft.com/kb/840219

Simply adding the account to the local Admins group will not suffice!

Connections Timing Out

I am running an application on MS SQL2000 SP4. I have 5 clients connecting to
the SQL server. Almost every night between 5pm and 6:30pm, I lose the
connection to the server from the clients and I get a message about my
database possibly being compromised. Everything locks up and I must reboot
the client.
Has any one experienced this?
Fini2549
Check to see if there are any scheduled jobs running at that time. Sounds
like someone is running a DBCC CHECKDB and placing the db in single user
mode.
Andrew J. Kelly SQL MVP
"Fini2549" <Fini2549@.discussions.microsoft.com> wrote in message
news:9990B03B-CE13-4CEB-9EF8-E4FFB68E0A10@.microsoft.com...
>I am running an application on MS SQL2000 SP4. I have 5 clients connecting
>to
> the SQL server. Almost every night between 5pm and 6:30pm, I lose the
> connection to the server from the clients and I get a message about my
> database possibly being compromised. Everything locks up and I must reboot
> the client.
> Has any one experienced this?
> Fini2549

Connection String for selling Web Applications?

If I'm wanting to sell my Web Applications to clients that run using SQL Server, is it best to use a UserID and Password in the connection string, or would using Windows Integrated Security (SSPI) do? The reason I'm wondering is because I wouldn't know my customer's UserID and Password when they purchased one of my web apps, I would have to recompile the app with the new connection string (I'm not storing it in the web.config file)..

What is the best way to handle this on a global level, so that it would work on any system?

for example, would having the following connection string be a good idea for a production site?

string strMyConnectionString = " Data Source = (local); Integrated Security = SSPI; Initital Catalog = MyDBSource; ";It would really be better to allow it to be specified in the Web.Config. What happens if the database is not located on the same machine?|||Why are you not storing it in the web.config file ?|||I didn't store it in the web.config file for security reasons. Would the web.config be the best way to go? Should I encrypt the string?|||Yes and Yes

Connection Problems SQL2000 on Local Machine

This may be a stupid newbie question, but being that I'm not a DBA I'm going to ask it anyway.

We discovered a problem with a clients server (Windows 2003 SBS) when we tried to install Veritas Backup Exec. Backup Exec requires an instance of either SQLMSDE or full SQL. This server has full SQL 2000 sp3a installed on it with a working account application. When backup exec trys to create it's instance it fails.

Investigating further...when I go into Enterprise Manager (logged in as Domain Admin) I get an error when I select the local server.

I.E.
"A connection could not be established to (LOCAL).
Reason: Data source name not found and no default driver specified.
Please verify SQL Server is running and check your SQL Server registration properties. blah blah blah.

Okay the server is running. The accounting application (client/server) is still working. I right click on the server and select "New Server Registration" for the field "server" I click the browse button and the "Active Servers" box is empty..:shocked:

I went to check the "Data Sources" under drivers, that field is blank. (no drivers installed). I downloaded MS's component checker and it says "MDAC 2.8 on Windows server 2003 sp1" is installed.

At this point I have exhausted my knowledge of MS-SQL server. My goal is to get BackupExec installed and NOT break the existing accounting application.

Any help is greatly appreciated.

Thanks
rogerbHi there,

i think the running instance on your server was not installed with the "Mixed Mode" authentication.
That's where the external application trying to connect on windows login account fials.

Hope this helps.

Regards.|||I think I've determined that there is a named instance of SQL running, but that the default instance is NOT running. How do I start the default instance and not mess up the named instance that is running? I tried "sqlservr.exe" at the command prompt but received a number of errors regard the log files being locked by another process?

Edit: Nope, my last statement is wrong there. There are two instances running. Which would explain the logfile errors. But...I still can't connect to the server with Enterprise Manger.

Edit 2: The authentication mode on the named instance was set to 2 (mixed), the default 1(windows), I set the default to 2 and restarted the service. I still can't connect with Enterprise Manager.|||Okay I fixed my own problem. Here's what I found. In the registry under HKLM\Software\ODBC there is an entry "odbcinst.ini". There are suppose to be a list of installed drivers here. In my case this key was empty. So I created the SQL Server key and the Text value"Driver" which equals, "c:\winnt\system32\sqlsrv32.dll.

And...I can get into the default instance now.