Re: ADO.NET 2.0 & MSDE & Win98



Does SQL Server Express run just fine on Windows 98?

"William (Bill) Vaughn" <billvaRemoveThis@xxxxxxxxxx> wrote in message
news:#646XKwNGHA.1716@xxxxxxxxxxxxxxxxxxxxxxx
SQL Server Express and MSDE are shipped with the network protocols
disabled.
This prevents them from being attacked by those who know the default port
assignments. At this point in time you should be using SQL Server Express,
not MSDE. It's also free and has a far richer toolset and functionality.
And
no, if you're using ADO.NET 2.0, you don't need the MDAC stack.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no
rights.
__________________________________

"Mircea Pleteriu" <mpleteriu@xxxxxxxxxxxxxxxx> wrote in message
news:%23CtbarvNGHA.3728@xxxxxxxxxxxxxxxxxxxxxxx
I'm back.

The problem was fixed by reinstalling the MSDE with
DISABLENETWORKPROTOCOLS
= 0.
Don't know why.

"Mircea Pleteriu" <mpleteriu@xxxxxxxxxxxxxxxx> wrote in message
news:#HX8z0fNGHA.3360@xxxxxxxxxxxxxxxxxxxxxxx
Hi all,

I've implemented a .NET Windows Forms application with VS 2005 and .NET
Framework 2.0 which must be deployed on Windows 98 platform. The MSDE
will
be installed on Win98 as the SQL Server to which the app will connect.

On the Win98 platform I've installed .NET Framework redistributable
package
and the MSDE and then I've set up the database (which my app will use)
by
running a script with the OSQL tool.

All fina by now.

But surprize... even if the db can be access and browsed with the osql
tool... the .net app cannot connect to the database. It throws the
following
exception message:

System.Data.SqlClient.SqlException: An error has occurred while
establishing
a connection to the server. When connection to SQL Server 2005, this
failure
may be caused by the fact that under the default settings SQL Server
does
not allow remote connections. (provider: Named Pipes Provider, error:
4- -
Could not open a connection to SQL Server).

Do you have any idea where the problem could be?

I mention that my app runs successfuly on Windows XP/2000 with MSDE
installed.

Mircea,








.



Relevant Pages

  • Getting to the bottom of MSDE network connection problems ...
    ... but other than that it is MSDE 2000 with sp3a already applied. ... I've finally figured out the connection problems associated with this, ... and it seems the problems are due to Windows XP and not MSDE. ... the enterprise/standard versions of SQL server won't install ...
    (microsoft.public.sqlserver.msde)
  • RE: Getting to the bottom of MSDE network connection problems ...
    ... the way using the same installation scenario on Win2K works with no problem. ... > various versions of MSDE and Windows XP ... > and it seems the problems are due to Windows XP and not MSDE. ... > on a desktop OS like XP (meaning that, you can not compare SQL Server ...
    (microsoft.public.sqlserver.msde)
  • Re: Need help & support regarding MBSA 2.1 beta 2
    ... Issue: Local Account Password Test ... Check is skipped on Windows XP Home Edition computers. ... SQL Server and/or MSDE authentication mode is set to Windows ...
    (microsoft.public.security)
  • Need help & support regarding MBSA 2.1 beta 2
    ... Issue: Local Account Password Test ... Check is skipped on Windows XP Home Edition computers. ... SQL Server and/or MSDE authentication mode is set to Windows Only. ...
    (microsoft.public.security)
  • Re: Slow booting xp home.
    ... Changing the boot order to boot first from your hard disk might save you a half second, but you won't be able to boot from a CD until you change it back - and the time spent to do that will erase any previous time saved. ... 2- Consider what software you really want to start with Windows and also how you've configured your applications at startup ... Installing and Registering Visual Studio Express Editions Smart Device ...
    (microsoft.public.windowsxp.perform_maintain)