Showing posts with label installation. Show all posts
Showing posts with label installation. Show all posts
Thursday, March 8, 2012
Connection failure on standalone MSDE installtion when network is lost
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.Check local security policies on client machines that screw up. I had this
probelem recently.
<shridhargune@.hotmail.com> wrote in message
news:1122392145.762770.32950@.g49g2000cwa.googlegroups.com...
> 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.
>
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.Check local security policies on client machines that screw up. I had this
probelem recently.
<shridhargune@.hotmail.com> wrote in message
news:1122392145.762770.32950@.g49g2000cwa.googlegroups.com...
> 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.
>
Labels:
client,
connection,
database,
failure,
installation,
installtion,
microsoft,
msde,
mysql,
network,
oracle,
preparing,
samemachine,
scenario,
server,
sql,
standalone
Connection failure on standalone MSDE installtion when network is lost
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.
Check local security policies on client machines that screw up. I had this
probelem recently.
<shridhargune@.hotmail.com> wrote in message
news:1122392145.762770.32950@.g49g2000cwa.googlegro ups.com...
> 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.
>
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.
Check local security policies on client machines that screw up. I had this
probelem recently.
<shridhargune@.hotmail.com> wrote in message
news:1122392145.762770.32950@.g49g2000cwa.googlegro ups.com...
> 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.
>
Labels:
client,
connection,
database,
failure,
installation,
installtion,
microsoft,
msde,
mysql,
network,
oracle,
preparing,
samemachine,
scenario,
server,
sql,
standalone
Connection failure on MSDE 2000/XP installation
We have installed MSDE 2000 on XP For Tablet PC. All
applications that use ODBC to connect to the database work
well, however those applications that use either DBLIB or
E/SQL (embedded SQL built on top of DBLIB) return a "Failed
to get DBPROCESS" error. MSDE was installed with
SQL-Authentication and all apps are started locally on the
server running MSDE. All applications run succesfully under
SQL 2000. Using SQL Profiler to trace application-activity
results in NO events being logged/traced, suggesting that
no SQL commands ever reach the server. Any ideas ?
If they are connecting via tcp/ip, do you have an exception in the firewall
(presuming XP SP2 is installed)?
Is the protocol they are connecting on enabled? (see svrnetcn.exe).
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Fintan" <anonymous@.discussions.microsoft.com> wrote in message
news:074001c5356f$36253fe0$a401280a@.phx.gbl...
> We have installed MSDE 2000 on XP For Tablet PC. All
> applications that use ODBC to connect to the database work
> well, however those applications that use either DBLIB or
> E/SQL (embedded SQL built on top of DBLIB) return a "Failed
> to get DBPROCESS" error. MSDE was installed with
> SQL-Authentication and all apps are started locally on the
> server running MSDE. All applications run succesfully under
> SQL 2000. Using SQL Profiler to trace application-activity
> results in NO events being logged/traced, suggesting that
> no SQL commands ever reach the server. Any ideas ?
>
applications that use ODBC to connect to the database work
well, however those applications that use either DBLIB or
E/SQL (embedded SQL built on top of DBLIB) return a "Failed
to get DBPROCESS" error. MSDE was installed with
SQL-Authentication and all apps are started locally on the
server running MSDE. All applications run succesfully under
SQL 2000. Using SQL Profiler to trace application-activity
results in NO events being logged/traced, suggesting that
no SQL commands ever reach the server. Any ideas ?
If they are connecting via tcp/ip, do you have an exception in the firewall
(presuming XP SP2 is installed)?
Is the protocol they are connecting on enabled? (see svrnetcn.exe).
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Fintan" <anonymous@.discussions.microsoft.com> wrote in message
news:074001c5356f$36253fe0$a401280a@.phx.gbl...
> We have installed MSDE 2000 on XP For Tablet PC. All
> applications that use ODBC to connect to the database work
> well, however those applications that use either DBLIB or
> E/SQL (embedded SQL built on top of DBLIB) return a "Failed
> to get DBPROCESS" error. MSDE was installed with
> SQL-Authentication and all apps are started locally on the
> server running MSDE. All applications run succesfully under
> SQL 2000. Using SQL Profiler to trace application-activity
> results in NO events being logged/traced, suggesting that
> no SQL commands ever reach the server. Any ideas ?
>
Labels:
allapplications,
applications,
connect,
connection,
database,
failure,
installation,
installed,
microsoft,
msde,
mysql,
odbc,
oracle,
server,
sql,
tablet,
workwell
Sunday, February 12, 2012
Connecting to SQL server from Linux
Am trying to connect to SQL Server 2000 from a Debian Linux installation. What would be the best place to get documentation on this? Is using Open-TDS recommended (is there any other way)?
will greatly appreciate any assistance.
thanks
If Java is an option for you then you may want to consider the Microsoft SQL Server 2005 JDBC Driver v1.1, which was just released today and is available for download at http://msdn.microsoft.com/data/jdbc .
It supports both SQL Server 2000 and SQL Server 2005, and, because it is a Type 4 JDBC driver, it runs just fine on Linux. See the link above, for all the feature details and documentation.
Thank you,
--David Olix
JDBC Development
|||Would there be solution for connecting from perl?
thanks
Labels:
connect,
connecting,
database,
debian,
documentation,
installation,
linux,
microsoft,
mysql,
oracle,
server,
sql
Subscribe to:
Posts (Atom)