Friday, March 30, 2012
Installing MSDE 2000 on a system with SQL Express 2005
has SQL Express 2005 installed) the MSDE setup will load and hang at "11
minutes" remaining. I can't cancel it, clicking Cancel switches the dialog
to say "Cancelling" but nothing ever happens.
Is it possible for MSDE 2000 to co-exist with SQL Express 2005 on a system?
If yes, how?
Thanks for your help!
hi Pyil,
Phil Palios wrote:
> I noticed that when I install an app that uses MSDE 2000 on my system
> (which has SQL Express 2005 installed) the MSDE setup will load and
> hang at "11 minutes" remaining. I can't cancel it, clicking Cancel
> switches the dialog to say "Cancelling" but nothing ever happens.
> Is it possible for MSDE 2000 to co-exist with SQL Express 2005 on a
> system? If yes, how?
yes it should be ... do not know if MSDE 2000 should be previously installed
than SQLExpress, but should be..
please provide the
/L*v "c:\MsdeLot.txt"
parameter to the setup.exe boostrap installer in order to allow verbose
logging of the installation process.. this will result in an about
2mb(succesfull installation) text file you can inspect for
RETURN VALUE 3
entries... about 10/15 lines before each entry, some (sometime cryptic)
description of the problem will be reported..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea,
I opened up the MSDE log and there are no lines that contain "value 3" my
guess for this is that since setup hung it never was able to log a value 3
and exit gracefully.
The last two lines in the log are:
Starting custom action InstallSqlRedis
Executing "C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlredis.exe
/q:a"
So it appears that sqlredis.exe may be what is hanging, and the MSDE install
is not hearing back so it hangs. Any ideas on what is going on and how it
may be fixed?
Thanks so much!
-Phil
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3t11onFprggaU1@.individual.net...
> hi Pyil,
> Phil Palios wrote:
> yes it should be ... do not know if MSDE 2000 should be previously
> installed than SQLExpress, but should be..
> please provide the
> /L*v "c:\MsdeLot.txt"
> parameter to the setup.exe boostrap installer in order to allow verbose
> logging of the installation process.. this will result in an about
> 2mb(succesfull installation) text file you can inspect for
> RETURN VALUE 3
> entries... about 10/15 lines before each entry, some (sometime cryptic)
> description of the problem will be reported..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Phil,
Phil Palios wrote:
> Hi Andrea,
> I opened up the MSDE log and there are no lines that contain "value
> 3" my guess for this is that since setup hung it never was able to
> log a value 3 and exit gracefully.
> The last two lines in the log are:
> Starting custom action InstallSqlRedis
> Executing "C:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\sqlredis.exe /q:a"
> So it appears that sqlredis.exe may be what is hanging, and the MSDE
> install is not hearing back so it hangs. Any ideas on what is going
> on and how it may be fixed?
>
you can not fix this, as this problem is raised by MDAC setup itself... but
you can hack it... it's not supported but you can do it...
first install the latest MDAC stack manually, then run MSDE setup.exe
boostrap installer...
when MSDE setup hangs, kill setupre.exe process via Task Manager, then the
setup will proceed and complete successfully...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Monday, March 26, 2012
Installing Client Tools
1. The 64 bit program only comes with 64 bit tools. (Should I just download the 32 bit evaluation copy? Will the tools expire in 180 days on all the client machines?)
2. What are the licensing rules? Surely I am allowed to load client tools (but not the server itself) onto client devices. Is that right?
Thanks!Evaulation edition expiration only applicable to server components whereby you cannot use the server services, but for client tools I haven't seen such problem you can use them to connect to other SQL server instances.|||That's very helpful - thank you.
It would also be nice to know what the licensing rules actually are & what the best practice is supposed to be.|||Refer to this http://support.microsoft.com/kb/257716 page that clears about licensing policy on client tools, though it is for SQL 2000 all the information is still applicable to SQL 2005 in this case. I would also ask you to refer to the local Microsoft support for more information on licensing, as x64 is bit new in recent times.