Re: SQL state=08S01

Tech-Archive recommends: Speed Up your PC by fixing your registry

Sam (Sam@xxxxxxxxxxxxxxxxxxxxxxxxx) writes:
Need your advise, I have a user while trying to access remotely from
overseas to our ERP system always encounter the above mentioned subject
error.

Scenario one --> After user logon to the SSLVPN and logon to the ERP, it
will prompt 'Select error:SQLstate=08S01 Microsoft OLE DB Provider for SQL
Server Connection Failure' and straight away could not logon to the ERP.

Scenario two --> User will get this error --> 'Error while getting user
log-in details SQLSTATE=08S01 Microsoft OLE DB Provider for SQL
Server[DBNETLIB] connectionWrite(WrapperWrite()] General Network Error.
Check your network documentation.' when trying to logon to the ERP after
logon to SSLVPN.

Scenario three --> User will get this error after logon to SSLVPN and
ERP to use halfway --> 'Error while getting user log-in details
SQLSTATE=08S01 Microsoft OLE DB Provider for SQL Server[DBNETLIB]
connectionRead(WrapperRead()] General Network Error. Check your network
documentation.'

A very difficult issue to help with remotely. But in my experience these
types or problems are more related with networking and Active Directory
than SQL Server and OLE DB.

Do you use SQL authentication or Windows authentication? If you use
Windows authentication, try SQL authentication instead. If that works,
it's likely to be some AD issue. If the SQL authentication has the
same problem, I would guess that it's more of a network issue.

--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.

Relevant Pages

  • Mirror or Repl.: failsafe & disaster recovery vs. maintainability
    ... We are trying put together a disaster recovery plan for our production SQL ... production servers and a third server can be utilized for a backup/mirror ... Each production server will be housing an ERP SQL db for a different ...
    (microsoft.public.sqlserver.replication)
  • Re: Backup User cannot log in - backups fail immediately
    ... it is the "SBS Backup User" that the system now believes does not have the appropriate permissions to logon. ... I found an earlier entry in the newsgroup where one of the MVPs had posted the correct settings for all of the various logon rights in the group policy and they all match. ... I have since gotten all of that resolved, by uninstalling sharepoint, that instance of sql, and following the suggested MS document on how to clean out the registry, etc.. ...
    (microsoft.public.windows.server.sbs)
  • Cached Logon
    ... If IIS cached a logon just for one particular page, ... Authentication on SQL is set to SQL and Microsoft. ... It makes an ADO connection to SQL server using sa. ...
    (microsoft.public.sqlserver.connect)
  • Cached Logon
    ... If IIS cached a logon just for one particular page, ... Authentication on SQL is set to SQL and Microsoft. ... It makes an ADO connection to SQL server using sa. ...
    (microsoft.public.sqlserver.server)
  • Cached Logon
    ... If IIS cached a logon just for one particular page, ... Authentication on SQL is set to SQL and Microsoft. ... It makes an ADO connection to SQL server using sa. ...
    (microsoft.public.win2000.networking)