Re: Connection String/Network Library
From: Curt_C [MVP] (software_AT_darkfalz.com)
Date: 01/31/05
- Next message: Curt_C [MVP]: "Re: MoveFile problem"
- Previous message: n2K: "Re: Var Assignment."
- In reply to: James: "Connection String/Network Library"
- Next in thread: James: "Re: Connection String/Network Library"
- Reply: James: "Re: Connection String/Network Library"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 31 Jan 2005 08:51:46 -0600
Building your connection string
http://www.darkfalz.com/1059
Beyond that it's most likely NOT the connection string, its either the
network communications, unclosed connections, etc.
-- Curt Christianson Site & Scripts: http://www.Darkfalz.com Blog: http://blog.Darkfalz.com "James" <letyoudown@verizon.net> wrote in message news:%23SFtO65BFHA.2676@TK2MSFTNGP12.phx.gbl... > We've had a recurring problem where all of a sudden we get a DBMSSOCN > General Network Error on any page that connects to SQL Server. Then we > have > to reboot the server and everything works fine again, for a few more hours > and then we have the same problem. Someone suggested adding ";Network > Library=DBMSSOCN" to our connection strings. I've tried to figure out > exactly what this does and why not having it would be a problem. Any > ideas? > Thanks. > >
- Next message: Curt_C [MVP]: "Re: MoveFile problem"
- Previous message: n2K: "Re: Var Assignment."
- In reply to: James: "Connection String/Network Library"
- Next in thread: James: "Re: Connection String/Network Library"
- Reply: James: "Re: Connection String/Network Library"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|