Unable to Install Embedded SP2 Database files

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

The other tools in the setup application for SP2 work fine.

The message I get back when installing the SP2 Database is:
"Setup cannot gain access to the existing component database. this maybe due
to other Windows Embedded applications currently using the database. You
should shutdown these applications before continuing to install this product.
Would you like to continue?" With Retry and Cancel buttons. This window
pops up almost immediately on pressing the Next key to start the install.

Retry just repeats the message, Cancel goes to Finish on the exit panel.

The computer I am trying to install this on is a Windows 2000 SQL server
running as a member server of the NT 4.0 domain, SQL Server 2000 service pack
3a, OS service Pack 4, hardware is an Athlon 2000+ with 512 MB.
Install order was Service Pack 4 about 3 months ago. Sql Server Pack 3a
three days ago.

The database was upgraded to SP1 over a year ago and has worked flawlessly
until now. I have kept up with all the QFE's in the meantime. In an effort to
eliminate the issue of authentication failing. I've tried logging on as an
administrator locally and as a delegated administrator by our NT 4.0 domain (
I have local admin privileges via domain authentication on the box). I can
log onto the computer locally or as a Domain autheniticated user. I can run
the SQL management tools without any error messages under either logon. I do
know that I have to be in Windows Authentication to run SQL Server with the
Embedded Database so that's not an issue. I've also set my local and domain
logons as database Admins on both the Master and Embedded Databases.

I've also lost the SQL connection from the XP Pro SP2 CPU I run Target
Designer on. I am not a SQL Server guru, and unfortunately nobody else here
is either. This SQL Server is the only standalone version we have running,
other workstations have the MSDE running as integrated modules in
applications. I would prefer not to run the MSDE since it creates such a
performance hit on Target Designer. I liked being able to compile OS images
in 5 minutes or less!

Anybody got an idea what I need to fix ? I've got a project due in 2 weeks
so this is pretty serious for me.
 
If I'm understanding you correctly, you have reported two issues. One is
that you can't upgrade the SP1 DB to SP2 and the other is that your XPe
tools (like Database Manager) can no longer connect to the remote DB.

On the surface, it basically sounds like an issue with the DB on the server
side is either corrupt, or detached or the SQL service is stopped.

I know you said no one there is a SQL expert but it would be helpful if you
could at least verify the sql service is running, if so open Enterprise
Manager (a sql management snapin available in the start menu with the other
SQL links) and try to browse the available DBs from this tool, check to see
if the MantisSQL DB is attached and you can browse the list of tables. This
would at least indicate that you're not in a completely hosed state at the
server.

You could try to remove and reinstall the SP1 DB from Add/Remove Programs,
but this would be a last resort since you'd lose any custom components in
the configuration, but re-importing them is a snap if you have access to
them all.

Also, while you troubleshoot the SQL Server, my personal recommendation is
to keep making forward progress on your project with MSDE on a local machine
temporarily.

Good luck. I'll write a short blog entry this weekend about this subject,
add a comment to the blog with the status of your checks.
http://blogs.msdn.com/embedded/
--
Andy

This posting is provided "AS IS" with no warranties, and confers no rights.

------------------
 
Back
Top