Hi All

I was trying to setup IIS, ASP and MSDE 2000 Rel A on a machine yesterday
and my usual SQL server OLEDB dsn-less connection string would not work on
this machine.

I know it's down to this, as I used a tool called QTADO to setup dummy data
in the db and I had to use an ODBC dsn-less connection to connect to the db.
I couldn't use the program's default OLE DB method.

The machine was WinXP Pro SP2 (might have been SP1), but I thought the OLE
DB thingy came as standard on this OS.

I didn't have chance to try the standard SQL ODBC connection string, will do
this on Wed, but I'm sure it will work. Any ideas why the OLE DB wouldn't?
Just kept getting General Network error on Connection (read).

Thanks

[quoted text, click to view]

My guess would be that either named pipes or tcp/ip is not enabled in your
SQL Server configuration. Do you have the SQL Server client tools to enable
you to set up the network libraries for your copy of MSDE? If not, see here:
http://www.aspfaq.com/show.asp?id=2442

--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

Hi Bob

Thanks for the reply. Hope you are well.

When I installed MSDE I used these params in the setup.ini:

sapwd=mypassword
securitymode=sql
networkprotocols=0 << think I tried 1 as well can never remember which way
this has to go round

Anyway I went into the installed Microsoft Server/80/Tools/Bin folder and
ran the network config util, found that tcp/ip wasn't selected, moved it
across (also put named pipes over for the fun of it!!), stopped and started
the MSSQLServer service and still no joy.

Just whilst I've got you, I believe there MSDE has been updated quite a bit
and comes in 2 versions now:

SQL Express - MSDE updated
and SQL Desktop - just a few single files

Am I right re the above?

Is SQL Express easier to install and allows more user connections?

The SQL Desktop (or whatever it was called) appeared to have a really small
footprint, about 1MB, but absolutely no documentation on how to create and
manipulate the bloody thing esp for VB6 users wanting to work with it - is
this still the case?

Thanks


[quoted text, click to view]

My guess would be that either named pipes or tcp/ip is not enabled in your
SQL Server configuration. Do you have the SQL Server client tools to enable
you to set up the network libraries for your copy of MSDE? If not, see here:
http://www.aspfaq.com/show.asp?id=2442

--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

[quoted text, click to view]

Hmm, unlikely as it seems given your OS, corrupted MDAC installation? Go to
msdn and search for the Component Checker; download it and .

Give the guys in this group a little more time to see your post and respond.
If you still have no joy, I suggest you post to a SQL Server group.

[quoted text, click to view]

Sort of. It's the SQL2005 lite. MSDE no longer exists in SQL 2005. You can
read about it at www.microsoft.com/sql

[quoted text, click to view]

If you cannot connect to MSDE, I don't imagine that it will be easier with
SQL Express. However, installing it may correct the problems you are having
with OLE DB ... it's worth a try.



--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"