Re: Connection failure on standalone MSDE installtion when network is lost

Check local security policies on client machines that screw up. I had this
probelem recently.


<shridhargune@xxxxxxxxxxx> wrote in message
news:1122392145.762770.32950@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Scenario -
> On a standalone installation i.e client and SQL server are on same
> machine, if network connection is lost while preparing SQL server
> connection through client application, then SQL connection could not be
> established. This was detected only on few machines. The configuration
> details are:
> OS : Windows 2000 SP 4 with MSDE
> Error : MSVC exception occurred. This is not consistent. Some times it
> throws error in sql server connectivity DLLs.
>


.

Relevant Pages

  • Re: Connection Error: ADO.Net and SQL Server 2005
    ... Hitchhiker's Guide to Visual Studio and SQL Server ... I can connect to the server through an ODBC connection ... It is very puzzling because this client doesn't seem to have anything ...
    (microsoft.public.sqlserver.connect)
  • RE: Error 17835 - When encryption and Shared Memory are enabled
    ... Did you encounter this error when you connected to your SQL Server ... Did your SQL Server instance use a certificate explicitly specified by ... you configure your client connection settings "Force Protocol Encryption" ...
    (microsoft.public.sqlserver.connect)
  • Re: RD from Win98 to server 2003
    ... but the window is greyed out and can't be changed. ... >>Done the internet connection wizard, ... one of the other machines has ... But I just tried to run a client on ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Losing connections with SQL 2005
    ... Hitchhiker's Guide to Visual Studio and SQL Server ... SQL Server automatically detects if the client falls into the sea or gets ... Does the Connection pooling mechanism do this on its ... Upgrading our app is a really big task, ...
    (microsoft.public.sqlserver.connect)
  • Re: netbios and named pipes sql replication.
    ... Once the client switched to named pipes, ... > connection with. ... > When we took named pipes support off the SQL server with the MS patch, ... > We had to manually walk thru the ODBC setup and configure the CLIENT ...
    (microsoft.public.sqlserver.replication)
Loading