MSDE SQL Server 2000 Desktop Engine

Can someone advise me if this is basically SQL server 2000 and will work effectively to simulate sql server on a stand alone development machine ? Is this what its meant for?

I'm just not clear on this, here is the link:

http://www.microsoft.com/downloads/details.aspx?FamilyID=413744d1-a0bc-479f-bafa-e4b278eb9147&DisplayLang=en

Thanks in advance for any advice.MSDE is fine for a development machine.

There is a good FAQ here http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp

This explains the how they control MSDE performance http://www.microsoft.com/sql/msde/techinfo/workloadgov.asp

Simon|||yes

I found i had difficulty installing but these forums and its members have proved most helpful getting me up and running

many thanks

MSDE SP3a Upgrade problem

I just upgraded my desktop engine MSDE 1.0 to MSDE 2000 SP3a. Everything seemed to go well, MSSQLSERVER AND SQLSERVER Agent Services are running, problem is, I can no longer see the particular instance on the network from Enterprise Manager.

The installation instructions specified that if the Instance was to accept connections from applications on other computers not to specify the DISABLENETWORKPROTOCOLS parameter, so I didn't.

I'm a little green with this, can anyone suggest a place to start troubleshooting?Can you pull it up in Query Analyzer. Just type in (local) or whatever your instance name is for the connection server and see if it connects.

MSDE sharepoint databases how to import and export

Dear all,
I have a Intranet running the sharepoint version which
comes with Frontapage 2002 and MS desktop SQL 7.
My server have a problem and I have to upgrade it to MS
desktop SQL 2000A. Now my sharepoint databases don't work
anymore.
I was wondering if theere is a way to import them back
into the new MS DESKTOP SQL 2000A.
Thank you for any help
HI Renato,
ReadmeMSDE2000A.htm comes with your download of MS Desktop SQL 2000A. It
talks about the changes in this release. Your database doesn't work any
more probably due to the security change that requires strong password.
Empty sa passowrd is no longer accepted. If that is the case, you can
change your sa password by running this query: EXEC sp_password NULL,
'yourpassword', 'sa' and then replace in your code with the new password.
Hope this helps.
Amy
| Content-Class: urn:content-classes:message
| From: "Renato" <anonymous@.discussions.microsoft.com>
| Sender: "Renato" <anonymous@.discussions.microsoft.com>
| Subject: MSDE sharepoint databases how to import and export
| Date: Wed, 7 Apr 2004 07:34:13 -0700
| Lines: 13
| Message-ID: <19b6f01c41cad$65a1d0c0$a101280a@.phx.gbl>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Thread-Index: AcQcrWWh/rvselubSzuv0Twjq4q0CQ==
| Newsgroups: microsoft.public.sqlserver.msde
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.msde:13479
| NNTP-Posting-Host: tk2msftngxa09.phx.gbl 10.40.1.161
| X-Tomcat-NG: microsoft.public.sqlserver.msde
|
| Dear all,
|
| I have a Intranet running the sharepoint version which
| comes with Frontapage 2002 and MS desktop SQL 7.
|
| My server have a problem and I have to upgrade it to MS
| desktop SQL 2000A. Now my sharepoint databases don't work
| anymore.
|
| I was wondering if theere is a way to import them back
| into the new MS DESKTOP SQL 2000A.
|
| Thank you for any help
|

MSDE Setup and first database

I'm deploying MSDE with a desktop app (windows forms .net).
after installing MSDE, how do I create the database for the application?
I cannot provide a createdb.sql script to the user because there is no
queryanalyzer or similar tools.
How can I run the create query from the setup? or what is the recommended
method for doing this?
Thank You!
Hi,
Give a batch file to create the database. All you have to do is double click
the batch file. batch file should contain:-
OSQL -Usa -Ppassword -S servername -Q'Create database
dbname' -o'c:\createdb.log'
Save the command inside a .BAT file and send to client side to create the
database. Instad of giving the -Q parameter you
can also input a .SQL file which contans sequence of TSQL commands.
Thanks
Hari
SQL Server MVP
"Harley" <harleyobrienAThotmailDOTcom> wrote in message
news:E3273FC0-ADE4-47B1-9F3D-8DEC479E3341@.microsoft.com...
> I'm deploying MSDE with a desktop app (windows forms .net).
> after installing MSDE, how do I create the database for the application?
> I cannot provide a createdb.sql script to the user because there is no
> queryanalyzer or similar tools.
> How can I run the create query from the setup? or what is the recommended
> method for doing this?
> Thank You!

MSDE scalability

Hi all,
Im currently evaluating a change from Sybase ASA to MSDE
(sql server desktop engine) on all client sites.
We cannot afford to buy a bigger edition of MSDE, so it
is paramount to our decision that MSDE can handle the
expected workload.
We have estimated our maximum load to be 10 requests per.
second, and have run basic tests to ensure MSDE can
handle it. The results were good.
It would be very interesting to hear from anybody with
actual project experience with MSDE. Anybody with an
oppinion on MSDE in a production enviroment should also
let their voices be heard.
Best Regards
AlexHi
Your post is implying that MSDE is a different database engine to standard
SQL Server, which it isn't, therefore the throughput should be as good. You
are limited by database size and number of connections though.
John
"Alex" <alex_pedersen@.accenture_com> wrote in message
news:101b01c38bd9$dd00ff20$a301280a@.phx.gbl...
> Hi all,
> Im currently evaluating a change from Sybase ASA to MSDE
> (sql server desktop engine) on all client sites.
> We cannot afford to buy a bigger edition of MSDE, so it
> is paramount to our decision that MSDE can handle the
> expected workload.
> We have estimated our maximum load to be 10 requests per.
> second, and have run basic tests to ensure MSDE can
> handle it. The results were good.
> It would be very interesting to hear from anybody with
> actual project experience with MSDE. Anybody with an
> oppinion on MSDE in a production enviroment should also
> let their voices be heard.
> Best Regards
> Alex

MSDE RelA using all memory

Six months ago I rework our application to use MSDE as a desktop DB. It was
used to replace Paradox. I develop in Delphi with ADO.
I realized tremendous performance gains and the ability to use stored procs
and computed columns made many tasks far eaiser. But we seemed to have shot
outselves in the foot. Because to the significant performance gains, we
added additional features that involved complex queries.
Our application, which supports the automation of chicken processing, is
very DB intensive. We write a record to the database every 80 ms or so.
Lately some of our bigger clients have complained of application freeze-ups.
Upon further investigation, it turns out to be due to the consumption of
available memory by sqlsevr.exe. The executable goes consistantly and not at
a slow rate.
We have wittnessed it growing from 8 mb to over 700 mb in six hours. I
found some info via google and have tried setting the memory throttle but I
don't think it is working. The sqlsevr seems to blow right by the setting.
Presently we are advising out clients to install loads of ram and that does
help but we need a real resolution.
Our clients run on Win2000Pro
I am deparately looking for some advise to either limit the rate of the
executable or it's max size.
Thanks
Run sp_configure to check what's the value for "max server memory
(MB)". Probably it will be 2147483647 which means SQL server can use
all of the available memory. While this is good for the performance of
SQL server, it might cause problems for other apps on the server.
So if the machine is not a dedicated database server (and usually MSDE
instances are not), limit the max server memeory to a more convenient
number.
M
|||hi,
DelphiDeveloper wrote:
> Six months ago I rework our application to use MSDE as a desktop DB.
> It was used to replace Paradox. I develop in Delphi with ADO.
> I realized tremendous performance gains and the ability to use stored
> procs and computed columns made many tasks far eaiser. But we seemed
> to have shot outselves in the foot. Because to the significant
> performance gains, we added additional features that involved complex
> queries.
> Our application, which supports the automation of chicken processing,
> is very DB intensive. We write a record to the database every 80 ms
> or so.
> Lately some of our bigger clients have complained of application
> freeze-ups. Upon further investigation, it turns out to be due to the
> consumption of available memory by sqlsevr.exe. The executable goes
> consistantly and not at a slow rate.
> We have wittnessed it growing from 8 mb to over 700 mb in six hours.
> I found some info via google and have tried setting the memory
> throttle but I don't think it is working. The sqlsevr seems to blow
> right by the setting.
> Presently we are advising out clients to install loads of ram and
> that does help but we need a real resolution.
> Our clients run on Win2000Pro
> I am deparately looking for some advise to either limit the rate of
> the executable or it's max size.
> Thanks
in order to better understand memory management in SQL Server/MSDE you can
have a look at
http://www.windowsitpro.com/Article/...908/37908.html and
http://www.windowsitpro.com/Article/...908/37908.html by Notre Dame
SQL Server Kalen Delany or, at a lower level at
http://msdn.microsoft.com/library/de...v_03252004.asp
by Ken Henderson...
SQL Server/MSDE manages memory at it's best without human intervention, but
even if concerned about OS/other application pressures and really doing it's
best to as gentleman as possible and freing unused (and even used memory
discarding query plans and cache) it works best if there's not much
concurrency for resources on the pc it is istalled on..
limitg it's max memomory setting will decrease it's responseness (is this
english? :D) and fewer query plans, cached objects and so on will be
available, requiring mor I/O activities (among the other)... If I corectly
understand your scenario, you are working quiet real-time, and forcing MSDE
into lower memory barriers can causes troubles..
actually 700 mb for SQL Server are not that much, but you know your
customers...
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

MSDE over TCP/IP

I've got a SQL Server Desktop Engine (version 8.00.2039 - SP4) installation
running our SharePoint site. I now need to connect to this database remotely
via TCP/IP, but can't get it to enable the protocol.
The log file always just says:
2007-12-11 12:13:46.39 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2007-12-11 12:13:46.39 server SQL server listening on Shared Memory.
I've tried all the suggestions I've heard on the internet. What I've tried:
Install the latest MSDE Service Pack (SP4)
Use SVRNETCN.exe to enable the TCP/IP Protocol
Enable TCP/IP, Set to Port 0, Restart Service, Set to Port 1433, Restart
Service.
I've hard reset the machine, I've installed all the latest service packs on
this machine. I've disabled the firewall. I've tried ports other than 1433.
I've tried enabling Named Pipes & NWLink at various times as well. No matter
what I do, the log still shows it listening only on shared memory.
Any assistance would be greatly appreciated as I'm completely stumped.
Andrew Faust
http://www.andrewfaust.com
=?Utf-8?B?QW5kcmV3IEZhdXN0?= <andrew [at] andrewfaust.com> wrote in
news:23AE3B12-517E-4970-8F7D-3E094BE07541@.microsoft.com:

> I've got a SQL Server Desktop Engine (version 8.00.2039 - SP4)
> installation running our SharePoint site. I now need to connect to
> this database remotely via TCP/IP, but can't get it to enable the
> protocol.
> The log file always just says:
> 2007-12-11 12:13:46.39 server Using 'SSNETLIB.DLL' version
> '8.0.2039'. 2007-12-11 12:13:46.39 server SQL server listening on
> Shared Memory.
> I've tried all the suggestions I've heard on the internet. What I've
> tried:
> Install the latest MSDE Service Pack (SP4)
> Use SVRNETCN.exe to enable the TCP/IP Protocol
> Enable TCP/IP, Set to Port 0, Restart Service, Set to Port 1433,
> Restart Service.
> I've hard reset the machine, I've installed all the latest service
> packs on this machine. I've disabled the firewall. I've tried ports
> other than 1433. I've tried enabling Named Pipes & NWLink at various
> times as well. No matter what I do, the log still shows it listening
> only on shared memory.
> Any assistance would be greatly appreciated as I'm completely stumped.
If you see no effects at all from using svrnetcn.exe, perhaps you have got
multiple instances installed. Drop down the "Instances on this server"
combo at the top of the General tab of the svrnetcn.exe dialog (similarly
the Server combo at the top of the SQL Server Service Manager dialog).
|||Thanks for the response.
Unfortunately, that's not the problem. There is only 1 instance installed on
this server. I forgot to mention this before and don't know if it makes a
difference, but this is a named instance. It's called DOCMGR\SHAREPOINT. It's
also running on Windows Server 2003 with all the latest service packs
installed.
Andrew Faust
http://www.andrewfaust.com
"Chris.Cheney" wrote:

> =?Utf-8?B?QW5kcmV3IEZhdXN0?= <andrew [at] andrewfaust.com> wrote in
> news:23AE3B12-517E-4970-8F7D-3E094BE07541@.microsoft.com:
>
> If you see no effects at all from using svrnetcn.exe, perhaps you have got
> multiple instances installed. Drop down the "Instances on this server"
> combo at the top of the General tab of the svrnetcn.exe dialog (similarly
> the Server combo at the top of the SQL Server Service Manager dialog).
>
|||=?Utf-8?B?QW5kcmV3IEZhdXN0?= <andrew [at] andrewfaust.com> wrote in
news:B66EA507-0750-48F2-8E5F-F7B8FC60ED9F@.microsoft.com:

> Thanks for the response.
> Unfortunately, that's not the problem. There is only 1 instance
> installed on this server. I forgot to mention this before and don't
> know if it makes a difference, but this is a named instance. It's
> called DOCMGR\SHAREPOINT. It's also running on Windows Server 2003
> with all the latest service packs installed.
>
Well, it was something that was possible, given the symptoms you described.
Sorry, I'm out of further ideas. Good luck!
|||I appreciate the effort. I've finally given up on trying to make it work and
have moved my SharePoint to a full install of SQL Server 2000 and gotten the
functionality I needed.
Andrew Faust
http://www.andrewfaust.com
"Chris.Cheney" wrote:

> =?Utf-8?B?QW5kcmV3IEZhdXN0?= <andrew [at] andrewfaust.com> wrote in
> news:B66EA507-0750-48F2-8E5F-F7B8FC60ED9F@.microsoft.com:
>
> Well, it was something that was possible, given the symptoms you described.
> Sorry, I'm out of further ideas. Good luck!
>

MSDE ON WINDOWS XP - Unable to determine system default collation.

Please help Me,
I need Install MSDE2000 On Windows XP, but this message is show in the proces
Product: Microsoft SQL Server Desktop Engine -- Unable to determine system default collation.Are you running Windows XP Pro or Home?|||Please help Me,

I need Install MSDE2000 On Windows XP PRO, but this message is show in the proces

Product: Microsoft SQL Server Desktop Engine -- Unable to determine system default collation.|||Have you tried to logon with a user with administrator privileges?|||Originally posted by Dynatoz
Have you tried to logon with a user with administrator privileges?

Yes, I using the Administrator Acount

MSDE Memory Usage for Desktop Users

Hi all,
We are developing an application that uses MSDE as the database backend
running on the client's computer. As I understand it, SQL Server's memory
management model allows it to basically use as much memory as it possible
can when under heavy load. Then having allocated that much memory, SQL
Server will not release it unless another program needs it. Does MSDE work
in the same way? Would it be possible to signal SQL Server to release some
memory? If so, then we could signal MSDE to release some memory after we
have finished our major data crunching. This might at least give our
clients some relief as they have a tendency to become disconcerted by
whatever Task Manager tells them, no matter how much I tell them that SQL
Server will easily give up memory to allow other programs to run.
Thanks for any insight.
Jonathan
hi Jonathan,
"Jonathan Van Eenwyk" <jonathanve@.myrealbox.com> ha scritto nel messaggio
news:10hfeqaftls4778@.corp.supernews.com...
> Hi all,
> We are developing an application that uses MSDE as the database backend
> running on the client's computer. As I understand it, SQL Server's memory
> management model allows it to basically use as much memory as it possible
> can when under heavy load. Then having allocated that much memory, SQL
> Server will not release it unless another program needs it. Does MSDE
work
> in the same way? Would it be possible to signal SQL Server to release
some
> memory? If so, then we could signal MSDE to release some memory after we
> have finished our major data crunching. This might at least give our
> clients some relief as they have a tendency to become disconcerted by
> whatever Task Manager tells them, no matter how much I tell them that SQL
> Server will easily give up memory to allow other programs to run.
> Thanks for any insight.
> Jonathan
>
you can't... SQL Server (and MSDE so far) are totally disregarding
application signal... you can only limit it' memory footprint overriding the
dynamic memory configuration, setting a fixed upperbound limit...
please have a look at
http://msdn.microsoft.com/library/de...onfig_9zfy.asp
for further info about fixing memory...
another article, by Ken Henderson, available at
http://msdn.microsoft.com/library/de...v_03252004.asp
is worth reading too...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Andrea,
Alright. Thanks! Seems like that would be nice feature in a desktop
situation, but I guess that's not the real purpose of SQL Server.
Jonathan
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2nsbhvF46n5eU1@.uni-berlin.de...[vbcol=seagreen]
> hi Jonathan,
> "Jonathan Van Eenwyk" <jonathanve@.myrealbox.com> ha scritto nel messaggio
> news:10hfeqaftls4778@.corp.supernews.com...
memory[vbcol=seagreen]
possible[vbcol=seagreen]
> work
> some
we[vbcol=seagreen]
SQL
> you can't... SQL Server (and MSDE so far) are totally disregarding
> application signal... you can only limit it' memory footprint overriding
the
> dynamic memory configuration, setting a fixed upperbound limit...
> please have a look at
>
http://msdn.microsoft.com/library/de...onfig_9zfy.asp
> for further info about fixing memory...
> another article, by Ken Henderson, available at
>
http://msdn.microsoft.com/library/de...v_03252004.asp
> is worth reading too...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Jonathan,
"Jonathan Van Eenwyk" <jonathanve@.myrealbox.com> ha scritto nel messaggio
news:10hi63aggt5ja4b@.corp.supernews.com...
> Andrea,
> Alright. Thanks! Seems like that would be nice feature in a desktop
> situation, but I guess that's not the real purpose of SQL Server.
really not... =;-DD
SQL Server is suited to perform it's work the best it can and as quick it
can, with no regards (or little) to other boring users =;-DD
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE instance/SQL installed

I have an MSDE application and I'm wondering, if SQL Desktop already exists
on the machine its being installed on, what will happen if I try to install
a named instance of MSDE? Will it still install and then show an additional
service in the Services MMC?
Thanks.
STom
hi STom,
"TheNortonZ" <thenortonz@.hotmail.com> ha scritto nel messaggio
news:%235CpOEr5EHA.128@.TK2MSFTNGP15.phx.gbl
> I have an MSDE application and I'm wondering, if SQL Desktop already
> exists on the machine its being installed on, what will happen if I
> try to install a named instance of MSDE? Will it still install and
> then show an additional service in the Services MMC?
> Thanks.
> STom
you can install up to 16 instances (1 default instance and 15 named
instances) on the same pc...
all installed instances will have separate binaries (just the shared part of
them will be "shared" and updated at the highest service pack level),
registry keys, path and folders, and, of course, they will be separately
listed in SQL Server Service Manager and in the Services MMC applet..
the default instance will be listed there as MSSQLSERVER and SQLSERVERAGENT,
while each named instance as MSSQL$instanceName and SQLAgent$instanceName..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Andrea,
Thanks for the info.
Can I install MSDE2000A on a machine that is currently running SQL Server
2000 SP3a (Developer Edition)? I think you are saying I can.
STom
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:32ogv5F3phms8U1@.individual.net...
> hi STom,
> "TheNortonZ" <thenortonz@.hotmail.com> ha scritto nel messaggio
> news:%235CpOEr5EHA.128@.TK2MSFTNGP15.phx.gbl
> you can install up to 16 instances (1 default instance and 15 named
> instances) on the same pc...
> all installed instances will have separate binaries (just the shared part
> of
> them will be "shared" and updated at the highest service pack level),
> registry keys, path and folders, and, of course, they will be separately
> listed in SQL Server Service Manager and in the Services MMC applet..
> the default instance will be listed there as MSSQLSERVER and
> SQLSERVERAGENT,
> while each named instance as MSSQL$instanceName and
> SQLAgent$instanceName..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi,
"TheNortonZ" <thenortonz@.hotmail.com> ha scritto nel messaggio
news:%23luGIUu5EHA.3236@.TK2MSFTNGP15.phx.gbl
> Can I install MSDE2000A on a machine that is currently running SQL
> Server 2000 SP3a (Developer Edition)? I think you are saying I can.
yes, you can... and it must be a named instance if SQL Server Dev Edition is
the default instance..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE instance registration in Enterprise Manager

Hi All,
I'm trying to register an instance of MSDE on a remote machine using EM on my desktop. The remote machine has 2
named instances of MSDE running. I am able to register 1 instance with no problems. I had to register it using
"RemoteServer1\InstanceName" rather than just the remote machines name.
For the life of me I can not get the other instance to register. I get the "SQL Server does not exist or access
denied" error. I've tried just registering the 2nd instance without the first with the same results. I can see
no difference in the way either of the 2 instances were set up or in their properties. I am a machine admin on
the remote machine and am connecting using Windows Auth.
What am I missing and how can I register that 2nd instance?
Thank you.
gdr
Gary D. Rezek
University Networking Systems and Services
South Dakota State University
hi Gary,
Gary D. Rezek wrote:
> Hi All,
> I'm trying to register an instance of MSDE on a remote machine using
> EM on my desktop. The remote machine has 2 named instances of MSDE
> running. I am able to register 1 instance with no problems. I had to
> register it using "RemoteServer1\InstanceName" rather than just the
> remote machines name.
this is normal as a named instance full qualified name is
ComputerName\InstanceName...

> For the life of me I can not get the other instance to register. I
> get the "SQL Server does not exist or access denied" error. I've
> tried just registering the 2nd instance without the first with the
> same results. I can see no difference in the way either of the 2
> instances were set up or in their properties. I am a machine admin on
> the remote machine and am connecting using Windows Auth. What am I
> missing and how can I register that 2nd instance?
at least 1 difference must be present... the name... MSDE/SQL Server 2000
can be installed as a default instance or a named instance... but only a
default instance can be present, wit up to other 15 named instances per
computer...
as you already saw, a default instance is available as ComputerName, where a
named instance will be as ComputerName\InstanceName...
you can inspect your (remote) services for MSSQLSERVER and
MSSQL$InstanceName to see what is going on...
MSDE installs by default disabling network protocols, thus not allowing
remote connections... please verify using the Server Network Utiliy
(svrnetcn.exe) that the "failing" instance has enabled network protocols...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.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,
Thanks for your answer. It eventually led me to http://tinyurl.com/8q95s this post. In that post I found this
quote...
"You need to look for a line in the error log which states:
"SQL server listening on TCP, Shared Memory, Named Pipes.
"If you only have Shared Memory on this list, then only local connections are allowed."
In the instance I have been trying to connect, Shared Memory is the only thing listed in the errorlog, so no
TCP/IP or Named Pipes. I asked the individual who is responsible for the application which created this instance
of MSDE (and also the one who asked me WHY can't he connect through EM), I learned that this is the way it
should be. :^/ I've worked with MSDE very, very little, but I still should have looked at the ErrorLog to
begin with.
Thank you very much for your help
gdr
Gary D. Rezek
University Networking Systems and Services
South Dakota State University
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message news:3jg2rjFpnmhnU1@.individual.net...
> hi Gary,
> Gary D. Rezek wrote:
> this is normal as a named instance full qualified name is ComputerName\InstanceName...
>
> at least 1 difference must be present... the name... MSDE/SQL Server 2000 can be installed as a default
> instance or a named instance... but only a default instance can be present, wit up to other 15 named instances
> per computer...
> as you already saw, a default instance is available as ComputerName, where a named instance will be as
> ComputerName\InstanceName...
> you can inspect your (remote) services for MSSQLSERVER and MSSQL$InstanceName to see what is going on...
> MSDE installs by default disabling network protocols, thus not allowing remote connections... please verify
> using the Server Network Utiliy (svrnetcn.exe) that the "failing" instance has enabled network protocols...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual interface)
> -- remove DMO to reply
>
|||h Gary,
Gary D. Rezek wrote:
> Hi Andrea,
> Thanks for your answer. It eventually led me to
> http://tinyurl.com/8q95s this post. In that post I found this quote...
> "You need to look for a line in the error log which states:
> "SQL server listening on TCP, Shared Memory, Named Pipes.
> "If you only have Shared Memory on this list, then only local
> connections are allowed."
you always have to verify (on the server using Server Network Utility
[svrnetcn.exe] and on the client using Client Network Utility
[cliconfg.exe]) that a common network protocol is available for the client
and the server to dialog...

> In the instance I have been trying to connect, Shared Memory is the
> only thing listed in the errorlog, so no TCP/IP or Named Pipes. I
> asked the individual who is responsible for the application which
> created this instance of MSDE (and also the one who asked me WHY
> can't he connect through EM), I learned that this is the way it
> should be. :^/
if Shared Memory is the only protocol that "must" be enabled, then no remote
connections will be available... but it can be ok in local scenarios ..
MSDE will then actually be used as a local desktop database..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

msde installation invalid instance name

while installing msde desktop sp3 it gives error invalid instance name what should i do to resolve it
Do you already have an instance (of SQL Server or MSDE) installed?
If so, you'll need to identify a new instance name for your new
installation:
"..\setup.exe INSTANCENAME=whatever ..."
You need to issues this command via the command window or you can setup a
shortcu for this.
Also, if you have installed and instance and can't access it from clients,
run SVRNETCN.exe and make sure that you have at least one protocol enabled
(e.g. TCP/IP or Multi Protocol). If no protocols are enabled, clients won't
be able to access it.
Hope this helps,
Joe Geretz
"pink" <anonymous@.discussions.microsoft.com> wrote in message
news:E2E88A6D-5E7C-467E-9764-B6DA962F7C7A@.microsoft.com...
> while installing msde desktop sp3 it gives error invalid instance name
what should i do to resolve it

MSDE install problems...log attached

I am trying to install MSDE desktop engine and I having the most
difficult time.
I installed it once and then tried uninstalling it while it was still
running. Half of it uninstalled the other half still being there. I
then could not reinstall or uninstall cause a the DLL kept running. I
booted in safe mode and uninstalled the rest of the engine folder.
I tried to reinstall and it kept rolling back. I then installed and
turned off rollback. It said my version of SQL server is corrupt and I
have to reinstall it. I deleleted the folder and tried to reinstall. It
now kicks out at the gathering information portion of the install.
Below is a copy of my log. can someone decifer it for me please...
=3D=3D=3D Verbose logging started: 10/31/2005 17:11:35 Build type: SHIP
UNICODE 2.00.2600.1106 Calling process:
C:\WINDOWS\System32\msiexec.exe =3D=3D=3D
MSI (c) (24:F0): Resetting cached policy values
MSI (c) (24:F0): Machine policy value 'Debug' is 0
MSI (c) (24:F0): ******* RunEngine:
******* Product: C:\sql2ksp3\MSDE\Setup\SqlRun01.msi
******* Action:
******* CommandLine: **********
MSI (c) (24:F0): Machine policy value 'DisableUserInstalls' is 0
MSI (c) (24:F0): SOFTWARE RESTRICTION POLICY: Verifying package -->
'C:\sql2ksp3\MSDE\Setup\SqlRun01.msi' against software restriction
policy
MSI (c) (24:F0): Note: 1: 2262 2: DigitalSignature 3: -2147287038
MSI (c) (24:F0): SOFTWARE RESTRICTION POLICY:
C:\sql2ksp3\MSDE\Setup\SqlRun01.msi is not digitally signed
MSI (c) (24:F0): SOFTWARE RESTRICTION POLICY:
C:\sql2ksp3\MSDE\Setup\SqlRun01.msi is permitted to run at the
'unrestricted' authorization level.
MSI (c) (24:F0): Cloaking enabled.
MSI (c) (24:F0): End dialog not enabled
MSI (c) (24:F0): Original package =3D=3D>
C:\sql2ksp3\MSDE\Setup\SqlRun01.msi
MSI (c) (24:F0): Package we're running from =3D=3D>
C:\DOCUME~1\518494\LOCALS~1\Temp\2bf23d.msi
MSI (c) (24:F0): APPCOMPAT: looking for appcompat database entry with
ProductCode '{E09B48B5-E141-427A-AB0C-D3605127224A}'.
MSI (c) (24:F0): APPCOMPAT: no matching ProductCode found in database.
MSI (c) (24:F0): Machine policy value 'TransformsSecure' is 0
MSI (c) (24:F0): User policy value 'TransformsAtSource' is 0
MSI (c) (24:F0): APPCOMPAT: looking for appcompat database entry with
ProductCode '{E09B48B5-E141-427A-AB0C-D3605127224A}'.
MSI (c) (24:F0): APPCOMPAT: no matching ProductCode found in database.
MSI (c) (24:F0): Transforms are not secure.
MSI (c) (24:F0): Note: 1: 2262 2: Control 3: -2147287038
MSI (c) (24:F0): Command Line: sa...
MSI (c) (24:F0): Product Code passed to Engine.Initialize: ''
MSI (c) (24:F0): Product Code from property table before transforms:
'{E09B48B5-E141-427A-AB0C-D3605127224A}'
MSI (c) (24:F0): Product Code from property table after transforms:
'{E09B48B5-E141-427A-AB0C-D3605127224A}'
MSI (c) (24:F0): Product not registered: beginning first-time install
MSI (c) (24:F0): Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (c) (24:F0): User policy value 'SearchOrder' is 'nmu'
MSI (c) (24:F0): Adding new sources is allowed.
MSI (c) (24:F0): Package name extracted from package path:
'SqlRun01.msi'
MSI (c) (24:F0): Package to be registered: 'SqlRun01.msi'
MSI (c) (24:F0): Note: 1: 2262 2: AdminProperties 3: -2147287038
MSI (c) (24:F0): Machine policy value 'DisableMsi' is 0
MSI (c) (24:F0): Machine policy value 'AlwaysInstallElevated' is 0
MSI (c) (24:F0): User policy value 'AlwaysInstallElevated' is 0
MSI (c) (24:F0): Product installation will be elevated because user is
admin and product is being installed per-machine.
MSI (c) (24:F0): Running product
'{E09B48B5-E141-427A-AB0C-D3605127224A}' with elevated privileges:
Product is assigned.
MSI (c) (24:F0): TRANSFORMS property is now:
MSI (c) (24:F0): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\518494\Application Data
MSI (c) (24:F0): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\518494\Favorites
MSI (c) (24:F0): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\518494\NetHood
MSI (c) (24:F0): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\518494\My Documents
MSI (c) (24:F0): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\518494\PrintHood
MSI (c) (24:F0): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\518494\Recent
MSI (c) (24:F0): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\518494\SendTo
MSI (c) (24:F0): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\518494\Templates
MSI (c) (24:F0): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\All Users\Application Data
MSI (c) (24:F0): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\518494\Local Settings\Application Data
MSI (c) (24:F0): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\518494\My Documents\My Pictures
MSI (c) (24:F0): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\All Users\Start Menu\Programs\Administrative Tools
MSI (c) (24:F0): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\All Users\Start Menu\Programs\Startup
MSI (c) (24:F0): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\All Users\Start Menu\Programs
MSI (c) (24:F0): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\All Users\Start Menu
MSI (c) (24:F0): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\All Users\Desktop
MSI (c) (24:F0): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\518494\Start Menu\Programs\Administrative Tools
MSI (c) (24:F0): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\518494\Start Menu\Programs\Startup
MSI (c) (24:F0): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\518494\Start Menu\Programs
MSI (c) (24:F0): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\518494\Start Menu
MSI (c) (24:F0): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\518494\Desktop
MSI (c) (24:F0): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\All Users\Templates
MSI (c) (24:F0): SHELL32::SHGetFolderPath returned: C:\WINDOWS\Fonts
MSI (c) (24:F0): Note: 1: 2898 2: MS Sans Serif 3: MS Sans Serif 4: 0
5: 16
MSI (c) (24:F0): MSCOREE not loaded loading copy from system32
MSI (c) (24:F0): Note: 1: 1402 2:
HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
MSI (c) (24:F0): Note: 1: 1402 2:
HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
=3D=3D=3D Logging started: 10/31/2005 17:11:35 =3D=3D=3D
MSI (c) (24:F0): Machine policy value 'DisableRollback' is 0
MSI (c) (24:F0): User policy value 'DisableRollback' is 0
MSI (c) (24:F0): Doing action: INSTALL
Action start 17:11:35: INSTALL.
MSI (c) (24:F0): UI Sequence table 'InstallUISequence' is present and
populated.
MSI (c) (24:F0): In client but switching to server to run
ExecuteSequence
MSI (c) (24:F0): Grabbed execution mutex.
MSI (c) (24:F0): Incrementing counter to disable shutdown. Counter
after increment: 0
MSI (c) (24:F0): Note: 1: 2262 2: Control 3: -2147287038
MSI (c) (24:F0): Switching to server: SA...
MSI (s) (70:B8): Resetting cached policy values
MSI (s) (70:B8): Machine policy value 'Debug' is 0
MSI (s) (70:B8): ******* RunEngine:
******* Product: C:\sql2ksp3\MSDE\Setup\SqlRun01.msi
******* Action: INSTALL
******* CommandLine: **********
MSI (s) (70:B8): Machine policy value 'DisableUserInstalls' is 0
MSI (s) (70:B8): Setting cached product context: User non-assigned for
product: 06C7E36CBE523D11E8AD000A9C118E5E
MSI (s) (70:B8): Using cached product context: User non-assigned for
product: 06C7E36CBE523D11E8AD000A9C118E5E
MSI (s) (70:B8): Setting cached product context: User non-assigned for
product: 1A934039E94B45A44A9913DB1C9AD15E
MSI (s) (70:B8): Using cached product context: User non-assigned for
product: 1A934039E94B45A44A9913DB1C9AD15E
MSI (s) (70:B8): Setting cached product context: User non-assigned for
product: 95C59463C9801D94DB51E9B58DD69C1A
MSI (s) (70:B8): Using cached product context: User non-assigned for
product: 95C59463C9801D94DB51E9B58DD69C1A
MSI (s) (70:B8): Setting cached product context: User non-assigned for
product: c3b9757207456944ebc6c07862471ff9
MSI (s) (70:B8): Using cached product context: User non-assigned for
product: c3b9757207456944ebc6c07862471ff9
MSI (s) (70:B8): Setting cached product context: machine assigned for
product: 069DB0F15256EEF45B7742377FF72177
MSI (s) (70:B8): Using cached product context: machine assigned for
product: 069DB0F15256EEF45B7742377FF72177
MSI (s) (70:B8): Setting cached product context: machine assigned for
product: 0B79C053C7D38EE4AB9A00CB3B5D2472
MSI (s) (70:B8): Using cached product context: machine assigned for
product: 0B79C053C7D38EE4AB9A00CB3B5D2472
MSI (s) (70:B8): Setting cached product context: machine assigned for
product: 0DEF1459F7230FD4B869FE75FE26F291
MSI (s) (70:B8): Using cached product context: machine assigned for
product: 0DEF1459F7230FD4B869FE75FE26F291
MSI (s) (70:B8): Setting cached product context: machine assigned for
product: 2C22E5E46831EA74E8ED23DDDCDC6635
MSI (s) (70:B8): Using cached product context: machine assigned for
product: 2C22E5E46831EA74E8ED23DDDCDC6635
MSI (s) (70:B8): Setting cached product context: machine assigned for
product: 47CB7D76FD8E1184B91406328A9CBBF3
MSI (s) (70:B8): Using cached product context: machine assigned for
product: 47CB7D76FD8E1184B91406328A9CBBF3
MSI (s) (70:B8): Setting cached product context: machine assigned for
product: 497CA84818B8A04418EA464733D75B72
MSI (s) (70:B8): Using cached product context: machine assigned for
product: 497CA84818B8A04418EA464733D75B72
MSI (s) (70:B8): Setting cached product context: machine assigned for
product: 68AB67CA000000000000068247A7ED10
MSI (s) (70:B8): Using cached product context: machine assigned for
product: 68AB67CA000000000000068247A7ED10
MSI (s) (70:B8): Setting cached product context: machine assigned for
product: 68AB67CA7DA73301B7440A0000000010
MSI (s) (70:B8): Using cached product context: machine assigned for
product: 68AB67CA7DA73301B7440A0000000010
MSI (s) (70:B8): Setting cached product context: machine assigned for
product: 8A0F841731866D117AB7000B0D410204
MSI (s) (70:B8): Using cached product context: machine assigned for
product: 8A0F841731866D117AB7000B0D410204
MSI (s) (70:B8): Setting cached product context: machine assigned for
product: 9040110900063D11C8EF10054038389C
MSI (s) (70:B8): Using cached product context: machine assigned for
product: 9040110900063D11C8EF10054038389C
MSI (s) (70:B8): Setting cached product context: machine assigned for
product: 9040150900063D11C8EF10054038389C
MSI (s) (70:B8): Using cached product context: machine assigned for
product: 9040150900063D11C8EF10054038389C
MSI (s) (70:B8): Setting cached product context: machine assigned for
product: 9040250900063D11C8EF10054038389C
MSI (s) (70:B8): Using cached product context: machine assigned for
product: 9040250900063D11C8EF10054038389C
MSI (s) (70:B8): Setting cached product context: machine assigned for
product: 9040EA0900063D11C8EF10054038389C
MSI (s) (70:B8): Using cached product context: machine assigned for
product: 9040EA0900063D11C8EF10054038389C
MSI (s) (70:B8): Setting cached product context: machine assigned for
product: AB4CD6A618FCA8641B528D4408C96335
MSI (s) (70:B8): Using cached product context: machine assigned for
product: AB4CD6A618FCA8641B528D4408C96335
MSI (s) (70:B8): Setting cached product context: machine assigned for
product: AC97FE678A6A4C14EA944EB90A57AF15
MSI (s) (70:B8): Using cached product context: machine assigned for
product: AC97FE678A6A4C14EA944EB90A57AF15
MSI (s) (70:B8): Setting cached product context: machine assigned for
product: B2129F0245AAA384387D83CBBBFCBAFC
MSI (s) (70:B8): Using cached product context: machine assigned for
product: B2129F0245AAA384387D83CBBBFCBAFC
MSI (s) (70:B8): Setting cached product context: machine assigned for
product: B2D1BCADB2B1DA944937DB84F3FA9333
MSI (s) (70:B8): Using cached product context: machine assigned for
product: B2D1BCADB2B1DA944937DB84F3FA9333
MSI (s) (70:B8): Setting cached product context: machine assigned for
product: BEFEE19DF569579409494108C80C6D15
MSI (s) (70:B8): Using cached product context: machine assigned for
product: BEFEE19DF569579409494108C80C6D15
MSI (s) (70:B8): Setting cached product context: machine assigned for
product: D1D05B87C24698B4CB7C53E2EA63417D
MSI (s) (70:B8): Using cached product context: machine assigned for
product: D1D05B87C24698B4CB7C53E2EA63417D
MSI (s) (70:B8): Setting cached product context: machine assigned for
product: DDE7F2BCF1D91C3409CFF425AE1E271A
MSI (s) (70:B8): Using cached product context: machine assigned for
product: DDE7F2BCF1D91C3409CFF425AE1E271A
MSI (s) (70:B8): Setting cached product context: machine assigned for
product: ECFD4F8763317204CB2BA1002CA46835
MSI (s) (70:B8): Using cached product context: machine assigned for
product: ECFD4F8763317204CB2BA1002CA46835
MSI (s) (70:B8): File will have security applied from OpCode.
MSI (s) (70:B8): SOFTWARE RESTRICTION POLICY: Verifying package -->
'C:\sql2ksp3\MSDE\Setup\SqlRun01.msi' against software restriction
policy
MSI (s) (70:B8): Note: 1: 2262 2: DigitalSignature 3: -2147287038
MSI (s) (70:B8): SOFTWARE RESTRICTION POLICY:
C:\sql2ksp3\MSDE\Setup\SqlRun01.msi is not digitally signed
MSI (s) (70:B8): SOFTWARE RESTRICTION POLICY:
C:\sql2ksp3\MSDE\Setup\SqlRun01.msi is permitted to run at the
'unrestricted' authorization level.
MSI (s) (70:B8): End dialog not enabled
MSI (s) (70:B8): Original package =3D=3D>
C:\sql2ksp3\MSDE\Setup\SqlRun01.msi
MSI (s) (70:B8): Package we're running from =3D=3D>
C:\WINDOWS\Installer\2ae4a3.msi
MSI (s) (70:B8): APPCOMPAT: looking for appcompat database entry with
ProductCode '{E09B48B5-E141-427A-AB0C-D3605127224A}'.
MSI (s) (70:B8): APPCOMPAT: no matching ProductCode found in database.
MSI (s) (70:B8): Machine policy value 'TransformsSecure' is 0
MSI (s) (70:B8): User policy value 'TransformsAtSource' is 0
MSI (s) (70:B8): APPCOMPAT: looking for appcompat database entry with
ProductCode '{E09B48B5-E141-427A-AB0C-D3605127224A}'.
MSI (s) (70:B8): APPCOMPAT: no matching ProductCode found in database.
MSI (s) (70:B8): Transforms are not secure.
MSI (s) (70:B8): Note: 1: 2262 2: Control 3: -2147287038
MSI (s) (70:B8): Command Line: SA...
MSI (s) (70:B8): Product Code passed to Engine.Initialize: ''
MSI (s) (70:B8): Product Code from property table before transforms:
'{E09B48B5-E141-427A-AB0C-D3605127224A}'
MSI (s) (70:B8): Product Code from property table after transforms:
'{E09B48B5-E141-427A-AB0C-D3605127224A}'
MSI (s) (70:B8): Product not registered: beginning first-time install
MSI (s) (70:B8): Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (s) (70:B8): User policy value 'SearchOrder' is 'nmu'
MSI (s) (70:B8): Adding new sources is allowed.
MSI (s) (70:B8): Package name extracted from package path:
'SqlRun01.msi'
MSI (s) (70:B8): Package to be registered: 'SqlRun01.msi'
MSI (s) (70:B8): Note: 1: 2262 2: AdminProperties 3: -2147287038
MSI (s) (70:B8): Machine policy value 'DisableMsi' is 0
MSI (s) (70:B8): Machine policy value 'AlwaysInstallElevated' is 0
MSI (s) (70:B8): User policy value 'AlwaysInstallElevated' is 0
MSI (s) (70:B8): Product installation will be elevated because user is
admin and product is being installed per-machine.
MSI (s) (70:B8): Running product
'{E09B48B5-E141-427A-AB0C-D3605127224A}' with elevated privileges:
Product is assigned.
MSI (s) (70:B8): TRANSFORMS property is now:
MSI (s) (70:B8): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\518494\Application Data
MSI (s) (70:B8): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\518494\Favorites
MSI (s) (70:B8): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\518494\NetHood
MSI (s) (70:B8): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\518494\My Documents
MSI (s) (70:B8): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\518494\PrintHood
MSI (s) (70:B8): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\518494\Recent
MSI (s) (70:B8): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\518494\SendTo
MSI (s) (70:B8): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\518494\Templates
MSI (s) (70:B8): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\All Users\Application Data
MSI (s) (70:B8): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\518494\Local Settings\Application Data
MSI (s) (70:B8): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\518494\My Documents\My Pictures
MSI (s) (70:B8): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\All Users\Start Menu\Programs\Administrative Tools
MSI (s) (70:B8): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\All Users\Start Menu\Programs\Startup
MSI (s) (70:B8): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\All Users\Start Menu\Programs
MSI (s) (70:B8): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\All Users\Start Menu
MSI (s) (70:B8): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\All Users\Desktop
MSI (s) (70:B8): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\518494\Start Menu\Programs\Administrative Tools
MSI (s) (70:B8): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\518494\Start Menu\Programs\Startup
MSI (s) (70:B8): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\518494\Start Menu\Programs
MSI (s) (70:B8): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\518494\Start Menu
MSI (s) (70:B8): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\518494\Desktop
MSI (s) (70:B8): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\All Users\Templates
MSI (s) (70:B8): SHELL32::SHGetFolderPath returned: C:\WINDOWS\Fonts
MSI (s) (70:B8): Note: 1: 2898 2: MS Sans Serif 3: MS Sans Serif 4: 0
5: 16
MSI (s) (70:B8): MSCOREE not loaded loading copy from system32
=3D=3D=3D Logging started: 10/31/2005 17:11:35 =3D=3D=3D
MSI (s) (70:B8): Machine policy value 'DisableRollback' is 0
MSI (s) (70:B8): User policy value 'DisableRollback' is 0
MSI (s) (70:B8): Doing action: INSTALL
Action start 17:11:35: INSTALL.
MSI (s) (70:B8): Running ExecuteSequence
MSI (s) (70:B8): Doing action:
ProgramFilesFolder.66CDF039_0EDE_453E_A1E5_1931046 C4056
Action start 17:11:35:
ProgramFilesFolder.66CDF039_0EDE_453E_A1E5_1931046 C4056.
Action ended 17:11:35:
ProgramFilesFolder.66CDF039_0EDE_453E_A1E5_1931046 C4056. Return value
1=2E
MSI (s) (70:B8): Doing action:
ProgramFilesFolder.ACD7EC22_4989_4067_B267_6DB5716 695BC
Action start 17:11:35:
ProgramFilesFolder.ACD7EC22_4989_4067_B267_6DB5716 695BC.
Action ended 17:11:35:
ProgramFilesFolder.ACD7EC22_4989_4067_B267_6DB5716 695BC. Return value
1=2E
MSI (s) (70:B8): Doing action:
ProgramFilesFolder.0C7570D6_6225_4960_B951_4D16DD9 06838
Action start 17:11:35:
ProgramFilesFolder.0C7570D6_6225_4960_B951_4D16DD9 06838.
Action ended 17:11:35:
ProgramFilesFolder.0C7570D6_6225_4960_B951_4D16DD9 06838. Return value
1=2E
MSI (s) (70:B8): Doing action:
ProgramFilesFolder.88C26F26_166C_4CD7_8175_38297C2 276D7
Action start 17:11:35:
ProgramFilesFolder.88C26F26_166C_4CD7_8175_38297C2 276D7.
Action ended 17:11:35:
ProgramFilesFolder.88C26F26_166C_4CD7_8175_38297C2 276D7. Return value
1=2E
MSI (s) (70:B8): Doing action:
ProgramFilesFolder.CC1A8C58_27D1_4D38_BF1B_C0A5CBB 90616
Action start 17:11:35:
ProgramFilesFolder.CC1A8C58_27D1_4D38_BF1B_C0A5CBB 90616.
Action ended 17:11:36:
ProgramFilesFolder.CC1A8C58_27D1_4D38_BF1B_C0A5CBB 90616. Return value
1=2E
MSI (s) (70:B8): Doing action:
StartupFolder.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616
Action start 17:11:36:
StartupFolder.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616 .
Action ended 17:11:36:
StartupFolder.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616 . Return value 1.
MSI (s) (70:B8): Doing action:
SystemFolder.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616
Action start 17:11:36:
SystemFolder.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616.
Action ended 17:11:36:
SystemFolder.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616. Return value 1.
MSI (s) (70:B8): Doing action:
ProgramFilesFolder.BF65A835_E76E_4CA5_8B97_E8FD33E 7C475
Action start 17:11:36:
ProgramFilesFolder.BF65A835_E76E_4CA5_8B97_E8FD33E 7C475.
Action ended 17:11:36:
ProgramFilesFolder.BF65A835_E76E_4CA5_8B97_E8FD33E 7C475. Return value
1=2E
MSI (s) (70:B8): Doing action:
ProgramFilesFolder.C4D32C83_C28D_4329_A829_31C4C60 34F59
Action start 17:11:36:
ProgramFilesFolder.C4D32C83_C28D_4329_A829_31C4C60 34F59.
Action ended 17:11:36:
ProgramFilesFolder.C4D32C83_C28D_4329_A829_31C4C60 34F59. Return value
1=2E
MSI (s) (70:B8): Doing action:
ProgramFilesFolder.EF490CFB_7BC2_4102_8395_426CE58 70B18
Action start 17:11:36:
ProgramFilesFolder.EF490CFB_7BC2_4102_8395_426CE58 70B18.
Action ended 17:11:36:
ProgramFilesFolder.EF490CFB_7BC2_4102_8395_426CE58 70B18. Return value
1=2E
MSI (s) (70:B8): Doing action:
ProgramFilesFolder.DCDF3AA8_FCF8_49F6_9877_752F754 DD676
Action start 17:11:36:
ProgramFilesFolder.DCDF3AA8_FCF8_49F6_9877_752F754 DD676.
Action ended 17:11:36:
ProgramFilesFolder.DCDF3AA8_FCF8_49F6_9877_752F754 DD676. Return value
1=2E
MSI (s) (70:B8): Doing action:
ProgramFilesFolder.D9BC9C10_2DCD_44D3_AACC_9C58CAF 76128
Action start 17:11:36:
ProgramFilesFolder.D9BC9C10_2DCD_44D3_AACC_9C58CAF 76128.
Action ended 17:11:36:
ProgramFilesFolder.D9BC9C10_2DCD_44D3_AACC_9C58CAF 76128. Return value
1=2E
MSI (s) (70:B8): Doing action:
ProgramFilesFolder.185C1D8F_1545_4277_BB64_857D262 2DB57
Action start 17:11:36:
ProgramFilesFolder.185C1D8F_1545_4277_BB64_857D262 2DB57.
Action ended 17:11:36:
ProgramFilesFolder.185C1D8F_1545_4277_BB64_857D262 2DB57. Return value
1=2E
MSI (s) (70:B8): Doing action:
ProgramFilesFolder.9240E1C0_49D2_40A2_93CE_E62CD8B 48DDC
Action start 17:11:36:
ProgramFilesFolder.9240E1C0_49D2_40A2_93CE_E62CD8B 48DDC.
Action ended 17:11:36:
ProgramFilesFolder.9240E1C0_49D2_40A2_93CE_E62CD8B 48DDC. Return value
1=2E
MSI (s) (70:B8): Doing action:
ProgramFilesFolder.55BCEE28_CDBF_4D7F_97C4_082D6B5 8B9FF
Action start 17:11:36:
ProgramFilesFolder.55BCEE28_CDBF_4D7F_97C4_082D6B5 8B9FF.
Action ended 17:11:36:
ProgramFilesFolder.55BCEE28_CDBF_4D7F_97C4_082D6B5 8B9FF. Return value
1=2E
MSI (s) (70:B8): Doing action:
ProgramFilesFolder.6496AA57_4ABB_4A5B_A0A9_E712ECF A8092
Action start 17:11:36:
ProgramFilesFolder.6496AA57_4ABB_4A5B_A0A9_E712ECF A8092.
Action ended 17:11:36:
ProgramFilesFolder.6496AA57_4ABB_4A5B_A0A9_E712ECF A8092. Return value
1=2E
MSI (s) (70:B8): Doing action:
ProgramFilesFolder.9B023A3C_3C86_4E4B_90D5_DE42FB9 019F7
Action start 17:11:36:
ProgramFilesFolder.9B023A3C_3C86_4E4B_90D5_DE42FB9 019F7.
Action ended 17:11:36:
ProgramFilesFolder.9B023A3C_3C86_4E4B_90D5_DE42FB9 019F7. Return value
1=2E
MSI (s) (70:B8): Doing action:
ProgramFilesFolder.AC2DB678_071D_4330_A52D_9286D61 8F650
Action start 17:11:36:
ProgramFilesFolder.AC2DB678_071D_4330_A52D_9286D61 8F650.
Action ended 17:11:36:
ProgramFilesFolder.AC2DB678_071D_4330_A52D_9286D61 8F650. Return value
1=2E
MSI (s) (70:B8): Doing action:
ProgramFilesFolder.F5ABDAB8_DDBD_4D92_BEAD_A0511D9 C85DB
Action start 17:11:36:
ProgramFilesFolder.F5ABDAB8_DDBD_4D92_BEAD_A0511D9 C85DB.
Action ended 17:11:36:
ProgramFilesFolder.F5ABDAB8_DDBD_4D92_BEAD_A0511D9 C85DB. Return value
1=2E
MSI (s) (70:B8): Doing action:
SystemFolder.F26FFD4A_05B4_4969_A552_30C7F9BAB1F4
Action start 17:11:36:
SystemFolder.F26FFD4A_05B4_4969_A552_30C7F9BAB1F4.
Action ended 17:11:36:
SystemFolder.F26FFD4A_05B4_4969_A552_30C7F9BAB1F4. Return value 1.
MSI (s) (70:B8): Doing action:
ProgramFilesFolder.F26FFD4A_05B4_4969_A552_30C7F9B AB1F4
Action start 17:11:36:
ProgramFilesFolder.F26FFD4A_05B4_4969_A552_30C7F9B AB1F4.
Action ended 17:11:36:
ProgramFilesFolder.F26FFD4A_05B4_4969_A552_30C7F9B AB1F4. Return value
1=2E
MSI (s) (70:B8): Doing action:
TempFolder.F26FFD4A_05B4_4969_A552_30C7F9BAB1F4
Action start 17:11:36: TempFolder.F26FFD4A_05B4_4969_A552_30C7F9BAB1F4.
Action ended 17:11:36: TempFolder.F26FFD4A_05B4_4969_A552_30C7F9BAB1F4.
Return value 1.
MSI (s) (70:B8): Doing action:
ProgramFilesFolder.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B
Action start 17:11:36:
ProgramFilesFolder.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B.
Action ended 17:11:36:
ProgramFilesFolder.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B. Return value
1=2E
MSI (s) (70:B8): Doing action:
StartupFolder.2D02443E_7002_4C0B_ABC9_EAB2C064397B
Action start 17:11:36:
StartupFolder.2D02443E_7002_4C0B_ABC9_EAB2C064397B .
Action ended 17:11:36:
StartupFolder.2D02443E_7002_4C0B_ABC9_EAB2C064397B . Return value 1.
MSI (s) (70:B8): Doing action:
SystemFolder.2D02443E_7002_4C0B_ABC9_EAB2C064397B
Action start 17:11:36:
SystemFolder.2D02443E_7002_4C0B_ABC9_EAB2C064397B.
Action ended 17:11:36:
SystemFolder.2D02443E_7002_4C0B_ABC9_EAB2C064397B. Return value 1.
MSI (s) (70:B8): Doing action: SetInstallDir
Action start 17:11:36: SetInstallDir.
Action ended 17:11:36: SetInstallDir. Return value 1.
MSI (s) (70:B8): Doing action: SetDataDir
Action start 17:11:36: SetDataDir.
Action ended 17:11:36: SetDataDir. Return value 1.
MSI (s) (70:B8): Doing action: SetInstanceName
Action start 17:11:36: SetInstanceName.
Action ended 17:11:36: SetInstanceName. Return value 1.
MSI (s) (70:B8): Doing action: SetCollation
Action start 17:11:36: SetCollation.
Action ended 17:11:36: SetCollation. Return value 1.
MSI (s) (70:B8): Doing action: SetCallback
Action start 17:11:36: SetCallback.
Action ended 17:11:36: SetCallback. Return value 1.
MSI (s) (70:B8): Doing action: SetSecurityMode
Action start 17:11:36: SetSecurityMode.
Action ended 17:11:36: SetSecurityMode. Return value 1.
MSI (s) (70:B8): Doing action: SetUpgrade
Action start 17:11:36: SetUpgrade.
Action ended 17:11:36: SetUpgrade. Return value 1.
MSI (s) (70:B8): Doing action: SetUpgradeUser
Action start 17:11:36: SetUpgradeUser.
Action ended 17:11:36: SetUpgradeUser. Return value 1.
MSI (s) (70:B8): Skipping action: SetUpgradeUserWin9x (condition is
false)
MSI (s) (70:B8): Skipping action: SetSecurityMode9x (condition is
false)
MSI (s) (70:B8): Doing action: SetSaPword
Action start 17:11:36: SetSaPword.
Action ended 17:11:36: SetSaPword. Return value 1.
MSI (s) (70:B8): Doing action: SetUpgradeUserPword
Action start 17:11:36: SetUpgradeUserPword.
Action ended 17:11:36: SetUpgradeUserPword. Return value 1.
MSI (s) (70:B8): Doing action: SetAllowBlankSaPword
Action start 17:11:36: SetAllowBlankSaPword.
Action ended 17:11:36: SetAllowBlankSaPword. Return value 1.
MSI (s) (70:B8): Skipping action: SetSqlDoUpgrade (condition is false)
MSI (s) (70:B8): Doing action: SetDisableAgentStartup
Action start 17:11:36: SetDisableAgentStartup.
Action ended 17:11:36: SetDisableAgentStartup. Return value 1.
MSI (s) (70:B8): Doing action: SetAllowXDBChaining
Action start 17:11:36: SetAllowXDBChaining.
Action ended 17:11:36: SetAllowXDBChaining. Return value 1.
MSI (s) (70:B8): Doing action:
DefaultProgramDir.2D02443E_7002_4C0B_ABC9_EAB2C064 397B
Action start 17:11:36:
DefaultProgramDir.2D02443E_7002_4C0B_ABC9_EAB2C064 397B.
Action ended 17:11:36:
DefaultProgramDir.2D02443E_7002_4C0B_ABC9_EAB2C064 397B. Return value 1.
MSI (s) (70:B8): Doing action:
DefaultDataDir.2D02443E_7002_4C0B_ABC9_EAB2C064397 B
Action start 17:11:36:
DefaultDataDir.2D02443E_7002_4C0B_ABC9_EAB2C064397 B.
Action ended 17:11:36:
DefaultDataDir.2D02443E_7002_4C0B_ABC9_EAB2C064397 B. Return value 1.
MSI (s) (70:B8): Doing action:
SQLVersion.2D02443E_7002_4C0B_ABC9_EAB2C064397B
Action start 17:11:36: SQLVersion.2D02443E_7002_4C0B_ABC9_EAB2C064397B.
Action ended 17:11:36: SQLVersion.2D02443E_7002_4C0B_ABC9_EAB2C064397B.
Return value 1.
MSI (s) (70:B8): Doing action:
StreamSupportFiles.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B
Action start 17:11:36:
StreamSupportFiles.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B.
MSI (s) (70:B8): Creating MSIHANDLE (65) of type 790542 for thread 3512
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Creating CA Temp Directory :
C:\DOCUME~1\518494\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Streamed setupex.2D02443E_7002_4C0B_ABC9_EAB2C064397B to
C:\DOCUME~1\518494\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\set=
upex.dll
Streamed sqdedev.2D02443E_7002_4C0B_ABC9_EAB2C064397B to
C:\DOCUME~1\518494\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqd=
edev.dll
Streamed sqlsut.2D02443E_7002_4C0B_ABC9_EAB2C064397B to
C:\DOCUME~1\518494\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sql=
sut.dll
Streamed sqlunirl.2D02443E_7002_4C0B_ABC9_EAB2C064397B to
C:\DOCUME~1\518494\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sql=
unirl.dll
Streamed sqlresld.2D02443E_7002_4C0B_ABC9_EAB2C064397B to
C:\DOCUME~1\518494\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sql=
resld.dll
Streamed sqlcaxrll.2D02443E_7002_4C0B_ABC9_EAB2C064397B to
C:\DOCUME~1\518494\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sql=
cax.rll
Streamed sqlstp.2D02443E_7002_4C0B_ABC9_EAB2C064397B to
C:\DOCUME~1\518494\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sql=
stp.dll
Streamed sqlstprll.2D02443E_7002_4C0B_ABC9_EAB2C064397B to
C:\DOCUME~1\518494\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sql=
stp.rll
Streamed sqlcax.2D02443E_7002_4C0B_ABC9_EAB2C064397B to
C:\DOCUME~1\518494\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sql=
cax.dll
Action ended 17:11:36:
StreamSupportFiles.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B. Return value
1=2E
MSI (s) (70:B8): Doing action:
SetPropSQLMSDEInstalled.2D02443E_7002_4C0B_ABC9_EA B2C064397B
Action start 17:11:36:
SetPropSQLMSDEInstalled.2D02443E_7002_4C0B_ABC9_EA B2C064397B.
MSI (s) (70:B8): Creating MSIHANDLE (113) of type 790542 for thread
3512
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\518494\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\518494\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sql=
cax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action SetPropSQLMSDEInstalled
FindSet for ProductCode <{E09B48B5-E141-427A-AB0C-D3605127224A}>
returned 1
Setting SQLMSDEInstalled by MsiSetProperty returned 0
Setting SQLMSDESelected by MsiSetProperty returned 0
End SetPropSQLMSDEInstalled
Action ended 17:11:37:
SetPropSQLMSDEInstalled.2D02443E_7002_4C0B_ABC9_EA B2C064397B. Return
value 1.
MSI (s) (70:B8): Doing action:
RestoreSetupParams.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B
Action start 17:11:37:
RestoreSetupParams.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B.
MSI (s) (70:B8): Creating MSIHANDLE (123) of type 790542 for thread
3512
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Entering Function MyMsiEvaluateCondition
MsiEvaluateCondition for SQLMSDEInstalled returned TRUE
End Function MyMsiEvaluateCondition
Error reading setup parameters
Action ended 17:11:37:
RestoreSetupParams.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B. Return value
3=2E
Action ended 17:11:37: INSTALL. Return value 3.
MSI (s) (70:B8): Note: 1: 2262 2: Control 3: -2147287038
Property(S): UpgradeCode =3D {421A321C-2214-4713-B3EB-253F2FBCCE49}
Property(S): SqlDataDir =3D C:\Program Files\Microsoft SQL Server\
Property(S): SqlProgramDir =3D C:\Program Files\Microsoft SQL Server\
Property(S): SqlSecurityMode =3D sql
Property(S): SqlSa...
Property(S): VersionNT =3D 501
Property(S): ALLUSERS =3D 1
Property(S): ARPNOMODIFY =3D 1
Property(S): DefaultUIFont =3D Tahoma8
Property(S): INSTALLLEVEL =3D 3
Property(S): LIMITUI =3D 1
Property(S): Manufacturer =3D Microsoft Corporation
Property(S): ProductCode =3D {E09B48B5-E141-427A-AB0C-D3605127224A}
Property(S): ProductLanguage =3D 1033
Property(S): ProductName =3D Microsoft SQL Server Desktop Engine
Property(S): ProductVersion =3D 8.00.761
Property(S): MsiHiddenProperties =3D SqlSa...
Property(S): ProgramFilesFolder.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B =3D
C:\Program Files\
Property(S): StartupFolder.2D02443E_7002_4C0B_ABC9_EAB2C064397B =3D
C:\Documents and Settings\All Users\Start Menu\Programs\Startup\
Property(S): SystemFolder.2D02443E_7002_4C0B_ABC9_EAB2C064397B =3D
C:\WINDOWS\System32\
Property(S): SQLVersion.2D02443E_7002_4C0B_ABC9_EAB2C064397B =3D 8.00.194
Property(S): SQLMSDEInstalled =3D 1
Property(S): SQLExitCode.2D02443E_7002_4C0B_ABC9_EAB2C064397B =3D 1603
Property(S): APPS_TEST =3D 1
Property(S): SQLMSDESelected =3D 1
Property(S): CSDVersionNumber =3D 768
Property(S): CSDVersion =3D 8.00.761
Property(S): SQLVersion =3D 8.00.194
Property(S): SystemFolder.F26FFD4A_05B4_4969_A552_30C7F9BAB1F4 =3D
C:\WINDOWS\System32\
Property(S): ProgramFilesFolder.F26FFD4A_05B4_4969_A552_30C7F9B AB1F4 =3D
C:\Program Files\
Property(S): TempFolder.F26FFD4A_05B4_4969_A552_30C7F9BAB1F4 =3D
C:\DOCUME~1\518494\LOCALS~1\Temp\
Property(S): ProgramFilesFolder.F5ABDAB8_DDBD_4D92_BEAD_A0511D9 C85DB =3D
C:\Program Files\
Property(S): ProgramFilesFolder.AC2DB678_071D_4330_A52D_9286D61 8F650 =3D
C:\Program Files\
Property(S): ProgramFilesFolder.9B023A3C_3C86_4E4B_90D5_DE42FB9 019F7 =3D
C:\Program Files\
Property(S): ProgramFilesFolder.6496AA57_4ABB_4A5B_A0A9_E712ECF A8092 =3D
C:\Program Files\
Property(S): ProgramFilesFolder.55BCEE28_CDBF_4D7F_97C4_082D6B5 8B9FF =3D
C:\Program Files\
Property(S): ProgramFilesFolder.9240E1C0_49D2_40A2_93CE_E62CD8B 48DDC =3D
C:\Program Files\
Property(S): ProgramFilesFolder.185C1D8F_1545_4277_BB64_857D262 2DB57 =3D
C:\Program Files\
Property(S): ProgramFilesFolder.D9BC9C10_2DCD_44D3_AACC_9C58CAF 76128 =3D
C:\Program Files\
Property(S): ProgramFilesFolder.DCDF3AA8_FCF8_49F6_9877_752F754 DD676 =3D
C:\Program Files\
Property(S): ProgramFilesFolder.EF490CFB_7BC2_4102_8395_426CE58 70B18 =3D
C:\Program Files\
Property(S): ProgramFilesFolder.C4D32C83_C28D_4329_A829_31C4C60 34F59 =3D
C:\Program Files\
Property(S): ProgramFilesFolder.BF65A835_E76E_4CA5_8B97_E8FD33E 7C475 =3D
C:\Program Files\
Property(S): ProgramFilesFolder.CC1A8C58_27D1_4D38_BF1B_C0A5CBB 90616 =3D
C:\Program Files\
Property(S): StartupFolder.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616 =3D
C:\Documents and Settings\All Users\Start Menu\Programs\Startup\
Property(S): SystemFolder.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616 =3D
C:\WINDOWS\System32\
Property(S): ProgramFilesFolder.88C26F26_166C_4CD7_8175_38297C2 276D7 =3D
C:\Program Files\
Property(S): ProgramFilesFolder.0C7570D6_6225_4960_B951_4D16DD9 06838 =3D
C:\Program Files\
Property(S): ProgramFilesFolder.ACD7EC22_4989_4067_B267_6DB5716 695BC =3D
C:\Program Files\
Property(S): ProgramFilesFolder.66CDF039_0EDE_453E_A1E5_1931046 C4056 =3D
C:\Program Files\
Property(S): SystemFolder =3D C:\WINDOWS\System32\
Property(S): PackageCode =3D {D29DCF7A-8199-4373-BA0D-2F3635EC940C}
Property(S): ProductState =3D -1
Property(S): PackagecodeChanging =3D 1
Property(S): SA...
Property(S): SECURITYMODE =3D sql
Property(S): CURRENTDIRECTORY =3D C:\sql2ksp3\MSDE
Property(S): CLIENTUILEVEL =3D 0
Property(S): CLIENTPROCESSID =3D 3876
Property(S): USERNAME =3D Booz Allen Hamilton
Property(S): COMPANYNAME =3D Booz Allen Hamilton
Property(S): ACTION =3D INSTALL
Property(S): VersionDatabase =3D 110
Property(S): VersionMsi =3D 2.00
Property(S): WindowsBuild =3D 2600
Property(S): ServicePackLevel =3D 1
Property(S): ServicePackLevelMinor =3D 0
Property(S): MsiNTProductType =3D 1
Property(S): WindowsFolder =3D C:\WINDOWS\
Property(S): WindowsVolume =3D C:\
Property(S): System16Folder =3D C:\WINDOWS\System\
Property(S): RemoteAdminTS =3D 1
Property(S): TempFolder =3D C:\DOCUME~1\518494\LOCALS~1\Temp\
Property(S): ProgramFilesFolder =3D C:\Program Files\
Property(S): CommonFilesFolder =3D C:\Program Files\Common Files\
Property(S): AppDataFolder =3D C:\Documents and
Settings\518494\Application Data\
Property(S): FavoritesFolder =3D C:\Documents and
Settings\518494\Favorites\
Property(S): NetHoodFolder =3D C:\Documents and Settings\518494\NetHood\
Property(S): PersonalFolder =3D C:\Documents and Settings\518494\My
Documents\
Property(S): PrintHoodFolder =3D C:\Documents and
Settings\518494\PrintHood\
Property(S): RecentFolder =3D C:\Documents and Settings\518494\Recent\
Property(S): SendToFolder =3D C:\Documents and Settings\518494\SendTo\
Property(S): TemplateFolder =3D C:\Documents and Settings\All
Users\Templates\
Property(S): CommonAppDataFolder =3D C:\Documents and Settings\All
Users\Application Data\
Property(S): LocalAppDataFolder =3D C:\Documents and
Settings\518494\Local Settings\Application Data\
Property(S): MyPicturesFolder =3D C:\Documents and Settings\518494\My
Documents\My Pictures\
Property(S): AdminToolsFolder =3D C:\Documents and Settings\All
Users\Start Menu\Programs\Administrative Tools\
Property(S): StartupFolder =3D C:\Documents and Settings\All Users\Start
Menu\Programs\Startup\
Property(S): ProgramMenuFolder =3D C:\Documents and Settings\All
Users\Start Menu\Programs\
Property(S): StartMenuFolder =3D C:\Documents and Settings\All
Users\Start Menu\
Property(S): DesktopFolder =3D C:\Documents and Settings\All
Users\Desktop\
Property(S): FontsFolder =3D C:\WINDOWS\Fonts\
Property(S): GPTSupport =3D 1
Property(S): OLEAdvtSupport =3D 1
Property(S): ShellAdvtSupport =3D 1
Property(S): Intel =3D 6
Property(S): PhysicalMemory =3D 1023
Property(S): VirtualMemory =3D 2173
Property(S): AdminUser =3D 1
Property(S): LogonUser =3D 518494
Property(S): UserSID =3D S-1-5-21-1079118523-3685698554-67682326-1008
Property(S): UserLanguageID =3D 1033
Property(S): ComputerName =3D BAH518494ABTAHI
Property(S): SystemLanguageID =3D 1033
Property(S): ScreenX =3D 1024
Property(S): ScreenY =3D 768
Property(S): CaptionHeight =3D 19
Property(S): BorderTop =3D 1
Property(S): BorderSide =3D 1
Property(S): TextHeight =3D 16
Property(S): ColorBits =3D 32
Property(S): TTCSupport =3D 1
Property(S): MsiNetAssemblySupport =3D 1.1.4322.2032
Property(S): MsiWin32AssemblySupport =3D 5.1.2600.1579
Property(S): RedirectedDllSupport =3D 2
Property(S): Time =3D 17:11:37
Property(S): Date =3D 10/31/2005
Property(S): Privileged =3D 1
Property(S): DATABASE =3D C:\WINDOWS\Installer\2ae4a3.msi
Property(S): OriginalDatabase =3D C:\sql2ksp3\MSDE\Setup\SqlRun01.msi
Property(S): UILevel =3D 3
MSI (s) (70:B8): MainEngineThread is returning 1603
MSI (c) (24:F0): Back from server. Return value: 1603
MSI (c) (24:F0): Decrementing counter to disable shutdown. If counter
>=3D 0, shutdown will be denied. Counter after decrement: -1
Action ended 17:11:37: INSTALL. Return value 3.
MSI (c) (24:F0): Note: 1: 2262 2: Control 3: -2147287038
Property(C): UpgradeCode =3D {421A321C-2214-4713-B3EB-253F2FBCCE49}
Property(C): VersionNT =3D 501
Property(C): ALLUSERS =3D 1
Property(C): ARPNOMODIFY =3D 1
Property(C): DefaultUIFont =3D Tahoma8
Property(C): INSTALLLEVEL =3D 3
Property(C): LIMITUI =3D 1
Property(C): Manufacturer =3D Microsoft Corporation
Property(C): ProductCode =3D {E09B48B5-E141-427A-AB0C-D3605127224A}
Property(C): ProductLanguage =3D 1033
Property(C): ProductName =3D Microsoft SQL Server Desktop Engine
Property(C): ProductVersion =3D 8.00.761
Property(C): MsiHiddenProperties =3D SqlSa...
Property(C): SQLVersion.2D02443E_7002_4C0B_ABC9_EAB2C064397B =3D 8.00.194
Property(C): SQLExitCode.2D02443E_7002_4C0B_ABC9_EAB2C064397B =3D 1603
Property(C): APPS_TEST =3D 1
Property(C): SQLMSDESelected =3D 1
Property(C): CSDVersionNumber =3D 768
Property(C): CSDVersion =3D 8.00.761
Property(C): SystemFolder =3D C:\WINDOWS\System32\
Property(C): PackageCode =3D {D29DCF7A-8199-4373-BA0D-2F3635EC940C}
Property(C): ProductState =3D -1
Property(C): PackagecodeChanging =3D 1
Property(C): SA...
Property(C): SECURITYMODE =3D sql
Property(C): CURRENTDIRECTORY =3D C:\sql2ksp3\MSDE
Property(C): CLIENTUILEVEL =3D 0
Property(C): CLIENTPROCESSID =3D 3876
Property(C): VersionDatabase =3D 110
Property(C): VersionMsi =3D 2.00
Property(C): WindowsBuild =3D 2600
Property(C): ServicePackLevel =3D 1
Property(C): ServicePackLevelMinor =3D 0
Property(C): MsiNTProductType =3D 1
Property(C): WindowsFolder =3D C:\WINDOWS\
Property(C): WindowsVolume =3D C:\
Property(C): System16Folder =3D C:\WINDOWS\System\
Property(C): RemoteAdminTS =3D 1
Property(C): TempFolder =3D C:\DOCUME~1\518494\LOCALS~1\Temp\
Property(C): ProgramFilesFolder =3D C:\Program Files\
Property(C): CommonFilesFolder =3D C:\Program Files\Common Files\
Property(C): AppDataFolder =3D C:\Documents and
Settings\518494\Application Data\
Property(C): FavoritesFolder =3D C:\Documents and
Settings\518494\Favorites\
Property(C): NetHoodFolder =3D C:\Documents and Settings\518494\NetHood\
Property(C): PersonalFolder =3D C:\Documents and Settings\518494\My
Documents\
Property(C): PrintHoodFolder =3D C:\Documents and
Settings\518494\PrintHood\
Property(C): RecentFolder =3D C:\Documents and Settings\518494\Recent\
Property(C): SendToFolder =3D C:\Documents and Settings\518494\SendTo\
Property(C): TemplateFolder =3D C:\Documents and Settings\All
Users\Templates\
Property(C): CommonAppDataFolder =3D C:\Documents and Settings\All
Users\Application Data\
Property(C): LocalAppDataFolder =3D C:\Documents and
Settings\518494\Local Settings\Application Data\
Property(C): MyPicturesFolder =3D C:\Documents and Settings\518494\My
Documents\My Pictures\
Property(C): AdminToolsFolder =3D C:\Documents and Settings\All
Users\Start Menu\Programs\Administrative Tools\
Property(C): StartupFolder =3D C:\Documents and Settings\All Users\Start
Menu\Programs\Startup\
Property(C): ProgramMenuFolder =3D C:\Documents and Settings\All
Users\Start Menu\Programs\
Property(C): StartMenuFolder =3D C:\Documents and Settings\All
Users\Start Menu\
Property(C): DesktopFolder =3D C:\Documents and Settings\All
Users\Desktop\
Property(C): FontsFolder =3D C:\WINDOWS\Fonts\
Property(C): GPTSupport =3D 1
Property(C): OLEAdvtSupport =3D 1
Property(C): ShellAdvtSupport =3D 1
Property(C): Intel =3D 6
Property(C): PhysicalMemory =3D 1023
Property(C): VirtualMemory =3D 2175
Property(C): AdminUser =3D 1
Property(C): LogonUser =3D 518494
Property(C): UserSID =3D S-1-5-21-1079118523-3685698554-67682326-1008
Property(C): UserLanguageID =3D 1033
Property(C): ComputerName =3D BAH518494ABTAHI
Property(C): SystemLanguageID =3D 1033
Property(C): ScreenX =3D 1024
Property(C): ScreenY =3D 768
Property(C): CaptionHeight =3D 19
Property(C): BorderTop =3D 1
Property(C): BorderSide =3D 1
Property(C): TextHeight =3D 16
Property(C): ColorBits =3D 32
Property(C): TTCSupport =3D 1
Property(C): MsiNetAssemblySupport =3D 1.1.4322.2032
Property(C): MsiWin32AssemblySupport =3D 5.1.2600.1579
Property(C): RedirectedDllSupport =3D 2
Property(C): Time =3D 17:11:38
Property(C): Date =3D 10/31/2005
Property(C): Privileged =3D 1
Property(C): USERNAME =3D Booz Allen Hamilton
Property(C): COMPANYNAME =3D Booz Allen Hamilton
Property(C): DATABASE =3D C:\DOCUME~1\518494\LOCALS~1\Temp\2bf23d.msi
Property(C): OriginalDatabase =3D C:\sql2ksp3\MSDE\Setup\SqlRun01.msi
Property(C): UILevel =3D 3
Property(C): ACTION =3D INSTALL
=3D=3D=3D Logging stopped: 10/31/2005 17:11:38 =3D=3D=3D
MSI (c) (24:F0): Note: 1: 1708
MSI (c) (24:F0): Product: Microsoft SQL Server Desktop Engine --
Installation operation failed.
MSI (c) (24:F0): Grabbed execution mutex.
MSI (c) (24:F0): Cleaning up uninstalled install packages, if any exist
MSI (c) (24:F0): MainEngineThread is returning 1603
=3D=3D=3D Verbose logging stopped: 10/31/2005 17:11:38 =3D=3D=3D
hi,
youngveh wrote:
> I am trying to install MSDE desktop engine and I having the most
> difficult time.
try having a look at http://tinyurl.com/7j4mt
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
|||that worked but now it installs and rollsback.