Connection Problem

[DroopyA]

I installed SQL Database Engine (MSDE) using the below ini file.

[Options]
INSTANCENAME=TagLinkMSDE
securitymode=sql
SAPWD=taglink
DISABLENETWORKPROTOCOLS=0

I then try to connect to the newly installed instance of MSDE using the below connection string.

m_cn.Open "Provider = SQLOLEDB.1; User ID = sa; Password = abcdefg; Initial Catalog = MyDatabaseCS; Data Source = ServerName\TAGLINKMSDE"

I get an error saying that the login for user 'sa' failed. Does anybody know why?

 

[SQLBill]

It looks like you set the SA password to taglink
SAPWD=taglink

but you are trying to use abcdefg
Password = abcdefg

-SQLBill

 

[DroopyA]

awww. nope. That was just an example error. They are both "taglink" in the real code but I just used abcdefg as an example when I posted it on this site. I guess I forgot to change the ini file code as well.

Any other ideas? I know nothing about MSDE and I had to convert our old program to SQL all by myself. This is the last thing I have to do and I would really like to start testing tomorrow.

I have an idea. How about somebody giving me an example of how you would connect to the "master" db through MSDE. If I try that and it doesn't work then I know the error is else where. If it does work then I'm sure that will be enough to help me figure out where my custom code is wrong.

 

[SQLBill]

I don't use MSDE, just SQL Server Enterprise Edition. But I saw that error and figured I should point it out to you.

-SQLBill

 

[DroopyA]

Thanks for the help, I wish it was that easy. Unfortunitly I know nothing of MSDE either and have had a hell of a year completely rewriting software to fit MSDEs requirements. And don't even get me started on the install... did you know Microsoft admits that their MSDE Merge Modules don't work? And they don't seem to care... talk about a pain in the ass.

Anyway, I got it all up and running, it installs, uninstalls, and does everything else except... run. And the program would run correctly if it could connect. So this one line of code is the only thing keeping me from ending a year long hell... and nobody can seem to help me.

Oh well, thanks for the help again, I really appreciate it and maybe somebody else on this site will know how it works.

 

[SQLBill]

The 'problem' is that MSDE is free-ware from Microsoft. It's just something they created for people/vendors to use instead of buying/licensing the 'real' product.

That's why they doen't do a wonderful job of supporting it - there's no money in it.

The above is only my opinion.

-SQLBill

 

[DroopyA]

I agree, and if it was up to me I wouldn't even convert to SQLServer. I don't see the need for such a large database program for the backend of what I do. But I don't really have a choice and since Microsoft gains nothing from helping me, they too couldn't care less. Of course I could always call them... but even that will cost $250. That seems a little much for such a small problem... but at this point in time it may be my only solution. How sad, and I know my problem is something really small too.

 

[psprague]

Did you try a blank password? Thats the default.

 

[DroopyA]

Oddly enough, that's exactly what needed to be done psprague. I have no idea why, but a blank pasword allowd me to connect even though I was required to give the sa a default password during the install. Thanks for your help.