sql 2000 standard and sql 2005 express on same box and cannot authenti

[brettums]

I have BOTH sql 2000 standard and sql 2005 express on same box and cannot authenticate to the sql 2000 database. I know my sa account password etc... but it's just not accepting it.....

Just so you know here is the reason for the setup.


sql 2000 std will be used for a production database for medical files (which currently is NOT even setup) a good thing.... As for sql 2005 express I have Backup exec 11D using this as a backend engine..... The engine works fine for this....backups work great! I just don't know what to do w/ reference to the authentication protion of sql 2000 std. (notw doing this in enterprise manager). I'm a novice when it comes to sql administration, but I'm pretty good at figuring this out.

-brett

 

[gmmastros]

>> I know my sa account password etc...

Sometimes, that's not enough. If you installed SQL 2000 to use Windows Authentication ONLY, then you cannot log in with a user name and password.

I assume you are trying to connect with Enterprise Manager... Try using Windows Authentication instead.

-George

Strong and bitter words indicate a weak cause. - Fortune cookie wisdom

 

[SQLBill]

Did this happen right after you installed 2005? Or have they been working together and all of sudden 2000 stopped authenticating?

-SQLBill

Posting advice: FAQ481-4875

 

[brettums]

Gammastros.... yes. Enterprise manager.... and yes, I did that already....




SQLBill, Originally I have the backend db for BUE runnnig on sql2000, I uninstalled BUE (per symantec support) reinstalled it and when it came time to "connect the program to the backend (sql 2000 engine) itwas not liking the authentication, so that was when I said, ok, put 2005 express on (have both enginee's run parallel) 2005 express works fine.... I try to go into enterprise manager (connect to local and I constantly am asked for authentication...... I could have sworn I did windows authentication..... I even setup an account specific to run and connect to the engine..... but it's not working...... I mean this is a no brainer (a monkey can figure this out) LOL

I'm atthe point where I'm ready to start from scratch again...... is this a good idea (ie uninstall 2005 exp and sql 2000)

 

[gmmastros]

Are you sure the service is started?

Click Start -> Run
Type services.msc
click OK

for sql 2000, there should be a service named MSSQLSERVER.

Make sure it's started and set to automatic.

-George

Strong and bitter words indicate a weak cause. - Fortune cookie wisdom

 

[SQLBill]

Are you sure you installed 2005 and did not UPGRADE the 2000 install?

With 2005:

If the default installation on a server is 2000, then the default for 2005 is to UPGRADE. You must SPECIFICALLY tell 2005 during the install to use a named instance. If you did not do that, you upgraded the default instance from 2000 to 2005.

-SQLBill

Posting advice: FAQ481-4875

 

[brettums]

Gmmastros - yes.... all fine

SQLBill - I'll put money on it that is what I did... so saying that I'll assume I have to reinstall BOTH engine's to fix this?
-Brett

 

[SQLBill]

Yes and make sure that you pay attention when installing 2005. It is easy to miss the screen where it asks you if you are UPDGRADING or INSTALLING a new instance. Make sure that wherever it asks, that you give an instance name.

-SQLBill

Posting advice: FAQ481-4875