Problem running MSDE 2000 with SQL Server 2000 and cannot uninstall MSDE

Hi, I really hope that someone can help me out!

I recently installed MSDE 2000 on my Windows XP Pro laptop to develop a standalone VB application with an embedded database.  My plan was to build the database in SQL Server 2000 and then migrate it over.  I created a test database and attached it MSDE and easily added data, ran sp’s, etc.

The problem came up when I powered up my laptop this morning.  I could no longer connect to my SQL Server database.  (The error was something to do with “corrupt” and possibly “invalid ID” - I wish that I had written it down).

Google searches suggested running SQL Server setup again, which I did, but didn’t have any luck fixing the installation.  They also mentioned that this can come up if the name of the machine is changed, which I didn’t do.

So I decided to uninstall SQL Server and reinstall it, hoping that would fix the problem.  After doing so and attempting to connect to the SQL Server, I got the error:

Login failed for user 'sa'. Reason Not associated with a trusted SQL Server connection

I tried several installs with different options (windows authentication, no sa password, etc.).  Nothing seemed to work.

At this point, my theory was that MSDE was causing the problem, since it was the only recent change to my machine.  I uninstalled SQL Server (again!) and attempted to uninstall MSDE (from control panels/add remove programs).  It ran through the normal uninstall process, then I got the error:

“Fatal Error during installation”

In a perfect world, I would love to have SQL Server 2000 and MSDE 2000 running flawlessly.  My second choice would be to just get SQL Server running again and to successfully remove MSDE.  At that point, I will most likely choose an alternate database solution for this product.

Thanks in advance!
MaxSterlingAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

mnyeCommented:
search for any *.ldf(log file) or *.mdf (data file).

if you have both or atleast the mdf then you should be alright. let me know what you have and ill tell you yer best options.

so at this point you dont have either SQL 2000 or MSDE?
0
MaxSterlingAuthor Commented:
Thanks for the response...  I checked and I cannot seem to run any queries against the MSDE:

[Shared Memory]SQL Server does not exist or access denied.
[Shared Memory]ConnectionOpen (Connect()).

I have multiple sets of mdf's and ldf's' for various SQL Server 2000 databases that I've created.  Here is a list of files in my SQL data directory:

03/31/2003  09:52 PM    <DIR>          .
03/31/2003  09:52 PM    <DIR>          ..
03/30/2003  04:06 PM         1,048,576 AdvancedCalc_Data.MDF
03/30/2003  04:06 PM         1,048,576 AdvancedCalc_Log.LDF
03/30/2003  04:06 PM        36,569,088 AmCatHDSQL.mdf
03/30/2003  04:06 PM       582,549,504 AmCatHDSQL_log.LDF
03/30/2003  04:06 PM        24,182,784 ContractsBilling.mdf
03/30/2003  04:06 PM        44,302,336 ContractsBilling_log.ldf
03/31/2003  12:58 PM        10,878,976 master.mdf
03/31/2003  12:58 PM           524,288 mastlog.ldf
03/31/2003  12:58 PM           655,360 model.mdf
03/31/2003  12:58 PM           524,288 modellog.ldf
08/06/2000  01:42 AM         3,145,728 msdbdata.mdf
08/06/2000  01:42 AM           524,288 msdblog.ldf
03/31/2003  12:58 PM         2,097,152 tempdb.mdf
03/31/2003  12:58 PM           524,288 templog.ldf

Let me know if there's any other info that I can give you.  I really appreciate the help
0
MaxSterlingAuthor Commented:
By the way, I DID try stopping the MSDE service and uninstalling, same result (Fatal Error during installation...)
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

spynettCommented:
When reinstall SQL Server by default sets Windows authentication.

In my case I just have 3 accounts created directly in SQL so I changed the authentication to mixed mode.

To do this: Search in the registry the word 'Login Mode' and set the value to 2.

Hope this helps,

SpyNett
0
mnyeCommented:
make sure you completely uninstall both MSDE and MS-SQL 2000.  Check your regsitry and see if the registry keys were unistalled as well. Once that is done, try reinstalling one or the other.  You can then attach the .mdf files.  Those are your database data files.  ldf's are your log files.

hth
late
matt
0
MaxSterlingAuthor Commented:
Hey spynett, I couldn't find "Login Mode" anywhere.  I thought it might be b/c I uninstalled sql server so I reinstalled it using windows authentication.  After that, I searched the entire registry for "Login Mode" and couldn't find it.  This is SQL Server 2K, does that help?  Thanks for the suggestion
0
MaxSterlingAuthor Commented:
Hello mnye, I cannot uninstall MSDE.  It gives a "Fatal Error during installation" error.
0
mnyeCommented:
what does the event log say? back up those mdf and ldf files to a disk.  if you have to can you install MSSQL 2000 on another computer?
0
MaxSterlingAuthor Commented:
Hello mnye,

I will paste the messages below.  I do have another machine but unfortunately this is my laptop and I need to get it working b/c I work onsite at the client a lot.  Thanks, I hope this helps

Event log messages:

17126 :
SQL Server is ready for client connections


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


19013 :
SQL server listening on 192.168.1.5:1433, 127.0.0.1:1433.


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Product: Microsoft SQL Server Desktop Engine -- Removal failed.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
(the link didn't tell anything)

19013 :
SQL server listening on TCP, Shared Memory, Named Pipes.


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

SuperSocket info: (SpnRegister) : Error 1355.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
(also no info online)

17052 :
Recovery complete.


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

17834 :
Using 'SSNETLIB.DLL' version '8.0.194'.


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

17125 :
Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

17124 :
SQL Server configured for thread mode processing.


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

17162 :
SQL Server is starting at priority class 'normal'(1 CPU detected).


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

17104 :
Server Process ID is 3884.


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

17052 :
Microsoft SQL Server  2000 - 8.00.194 (Intel X86)
     Aug  6 2000 00:57:48
     Copyright (c) 1988-2000 Microsoft Corporation
     Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 1)



For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

17148 :
SQL Server is terminating due to 'stop' request from Service Control Manager.


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

17126 :
SQL Server is ready for client connections


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.



Should I list more events?  Are these at all helpful?  Thanks!


0
MaxSterlingAuthor Commented:
Oh, I backed up the mdf and ldf files as you suggested.
0
MaxSterlingAuthor Commented:
I am bumping the points to 1000 because of the critical nature of this problem.  Please help!  I realized that I also installed MSDE on my other machine so neither of my SQL Server installations are working now.  Thanks
0
MaxSterlingAuthor Commented:
It would only let me do 500 points I guess...
0
mnyeCommented:


the first thing that sticks out would be:

SuperSocket info: (SpnRegister) : Error 1355.

this is an error saying that the socket is already in use.
via cmd run 'netstat -a' and look for a local address listening on port 1433 or TCP MS-SQL.  this is assuming you have TCP installed on your box.


Next:

got to SystemRoot\Windows\ and open log file Dasetup.log to determine what version of MDAC you have.  you may need to update to a newer version of MDAC. you may need to upgrade to 2.6, especially if you are using XP Pro.

also, did you check your registry to see what it looks like? im not going to suggest it but sometime to completely remove a program you have to manually delete the keys.  but i would never do it.
0
MaxSterlingAuthor Commented:
Hey mnye, thanks for the input on the netstat.  To be honest, that is over my head.  Here is the output from it, does this tell you anything?  I will now do "Next"


Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    Steve2:epmap           Steve2:0               LISTENING
  TCP    Steve2:microsoft-ds    Steve2:0               LISTENING
  TCP    Steve2:1025            Steve2:0               LISTENING
  TCP    Steve2:1032            Steve2:0               LISTENING
  TCP    Steve2:2934            Steve2:0               LISTENING
  TCP    Steve2:2937            Steve2:0               LISTENING
  TCP    Steve2:2985            Steve2:0               LISTENING
  TCP    Steve2:2986            Steve2:0               LISTENING
  TCP    Steve2:2988            Steve2:0               LISTENING
  TCP    Steve2:3084            Steve2:0               LISTENING
  TCP    Steve2:3085            Steve2:0               LISTENING
  TCP    Steve2:5000            Steve2:0               LISTENING
  TCP    Steve2:ms-sql-s        Steve2:0               LISTENING
  TCP    Steve2:5180            Steve2:0               LISTENING
  TCP    Steve2:netbios-ssn     Steve2:0               LISTENING
  TCP    Steve2:ms-sql-s        Steve2:0               LISTENING
  TCP    Steve2:2008            Steve2:0               LISTENING
  TCP    Steve2:2801            Steve2:0               LISTENING
  TCP    Steve2:2820            Steve2:0               LISTENING
  TCP    Steve2:2849            Steve2:0               LISTENING
  TCP    Steve2:2860            Steve2:0               LISTENING
  TCP    Steve2:2934            205.188.11.76:5190     ESTABLISHED
  TCP    Steve2:2937            64.12.27.155:5190      ESTABLISHED
  TCP    Steve2:3029            Steve2:0               LISTENING
  TCP    Steve2:3029            192.168.1.102:netbios-ssn  ESTABLISHED
  TCP    Steve2:3111            adserv.internetfuel.com:http  TIME_WAIT
  TCP    Steve2:3121            nitrous4.internetfuel.com:http  TIME_WAIT
  UDP    Steve2:epmap           *:*                    
  UDP    Steve2:microsoft-ds    *:*                    
  UDP    Steve2:isakmp          *:*                    
  UDP    Steve2:1026            *:*                    
  UDP    Steve2:1027            *:*                    
  UDP    Steve2:1041            *:*                    
  UDP    Steve2:1072            *:*                    
  UDP    Steve2:ms-sql-m        *:*                    
  UDP    Steve2:1712            *:*                    
  UDP    Steve2:ntp             *:*                    
  UDP    Steve2:1040            *:*                    
  UDP    Steve2:1045            *:*                    
  UDP    Steve2:1900            *:*                    
  UDP    Steve2:3086            *:*                    
  UDP    Steve2:ntp             *:*                    
  UDP    Steve2:netbios-ns      *:*                    
  UDP    Steve2:netbios-dgm     *:*                    
  UDP    Steve2:1900            *:*                    
0
MaxSterlingAuthor Commented:
Hey mnye,

My MDAC:

ProductName = Microsoft Data Access Components 2.6
0
mnyeCommented:
max,

go ahead and delete any IP or url address out of that last post.
0
MaxSterlingAuthor Commented:
hello mnye, I don't understand what you want me to do
0
mnyeCommented:
go to this link
http://www.networkingfiles.com/SecurityApps/downloads/visiondownload.htm

it will download a utility called Vision which will give you the ability to view all open ports and thier number, what application they are associated to and the path of each process.

once its installed, run the program, find all processes that are running under SQL Server and kill them (right click, kill).  

Then go to Services in your Administrative Tool, make sure your SQLAGENT, MSSQLSERVER and Distributed Transaction Coordinator are stopped, then attempt to uninstall both programs.


before, i was suggesting that you take out all instances of IP address and URLs from that post of your netstat run.  just for safty.

hth
late
matt
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
MaxSterlingAuthor Commented:
Hey myne,

Well, I got it working!  I did the steps that you suggested (except for the last networking step) and had to take one more.  Quite honestly, I'm not sure what combination of things fixed it but you provided the most help and I'll be glad to give you the points.  

In case you're interested, I blew away the registry keys for sql server, reinstalled and still could not connect.  i took a closer look at the running services and noticed that "Log On As" for the SQL one was STEVE or something, rather than "Local System" like most of the others.  I thought i might as well changing it and was shocked when I was able to connect to sql server.

Thanks again for the help, it is very much appreciated
0
mnyeCommented:
not too sure if i was of much help, glad you worked it out. if you need help attching the DBs let me know.
0
MaxSterlingAuthor Commented:
Thanks, I know how to attach them!  I appreciate all the help
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.