MSDE SQL Server marked as SUSPECT

Hello all! I have an instance of MSDE that is marked as SUSPECT. In
the error log I get:
I/O error on backup or restore restart-checkpoint file 'C:\Program
Files\Microsoft SQL Server\MSSQL$SBSMONITORING\backup\model4IDR.ckp'.
Operating system error 3(The system cannot find the path specified.).
The statement is proceeding but is non-restartable.
We don't have Enteprise Manager to look any closer at the DB. Do any of
you have a suggestion as to how to get this DB operational?
Jason
Restore it from a known good backup.
Jim
"Jason Hunsberger" <systems182@.nospam_andersontech.com> wrote in message
news:u1ZDFhWDFHA.3020@.TK2MSFTNGP09.phx.gbl...
> Hello all! I have an instance of MSDE that is marked as SUSPECT. In the
> error log I get:
> I/O error on backup or restore restart-checkpoint file 'C:\Program
> Files\Microsoft SQL Server\MSSQL$SBSMONITORING\backup\model4IDR.ckp'.
> Operating system error 3(The system cannot find the path specified.). The
> statement is proceeding but is non-restartable.
> We don't have Enteprise Manager to look any closer at the DB. Do any of
> you have a suggestion as to how to get this DB operational?
> Jason
sql

MSDE SQL Database Marked SUSPECT

Hello all! I have an instance of MSDE that is marked as SUSPECT. In
the error log I get:
I/O error on backup or restore restart-checkpoint file 'C:\Program
Files\Microsoft SQL Server\MSSQL$SBSMONITORING\backup\model4IDR.ckp'.
Operating system error 3(The system cannot find the path specified.).
The statement is proceeding but is non-restartable.
We don't have Enteprise Manager to look any closer at the DB. Do any of
you have a suggestion as to how to get this DB operational?
Jason
Jason,
You might check with Veritas regarding the Backup Exec.. The 4IDR part of
the filenames may have to do with their Intelligent Disaster Recovery..
Hope that helps,
David Copeland
Microsoft Small Business Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
SBS Newsgroups:
SBS v4.x: microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs
"Jason Hunsberger" <systems182@.nospam_andersontech.com> wrote in message
news:umOi6EWDFHA.208@.TK2MSFTNGP12.phx.gbl...
> Hello all! I have an instance of MSDE that is marked as SUSPECT. In
> the error log I get:
> I/O error on backup or restore restart-checkpoint file 'C:\Program
> Files\Microsoft SQL Server\MSSQL$SBSMONITORING\backup\model4IDR.ckp'.
> Operating system error 3(The system cannot find the path specified.).
> The statement is proceeding but is non-restartable.
> We don't have Enteprise Manager to look any closer at the DB. Do any of
> you have a suggestion as to how to get this DB operational?
> Jason

MSDE SP4 install problem

I attempted to install MSDE SP4 (file SQL2000.MSDE-KB884525-SP4-x86-ENU) on a WinXP Pro SP2 machine.

Command used:

setup SAPWD="ourpw" SECURITYMODE=SQL /L*v c:\MSDELog.log

Install log shows successful install.

MSDE appears to function properly, service starts automatically after reboot, etc.

I can open and work with DB's with a freebie 3rd party GUI called DbaMGR2K, through which I have added the necessary DB user for our locally running ASP application to use the db.

However, when I try to use the DB with our locally running ASP application - connecting with ADO from a dll we wrote, I get the following:

"[DNETLIB]{ConnectionOpen (Connect()).]SQL Server does not exist or access denied"

Any help appreciated.

day10

Hi,

make sure that you connect to the same database and you are using a valid login for connecting. Perhaps you have chosen another authentication mode within the ADO code ? That could explain either the one or the other error message you are getting.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

I think we have solved the issue. We used the SQL Server Network Utility to enable TCP/IP (apparently not enabled by default) and now all appears well.

I wonder if there is a way to enable TCP/IP during the install process. Is there an install flag/option?

|||

>> Is there an install flag/option?

Most likely. The flag for this when installing SP3 was "DISABLENETWORKPROTOCOLS=0". I wouldn't think that they would have removed it for SP4.

sql

MSDE SetUp Hell: Newbie Help

I am trying to setup MSDE for the very first time. So I am absolutely a
newbie. I downloaded sql2ksp3 from microsoft site. I unpacked the file to a
folder and then clicked on setup.
I get an error message about using the command line to supply a strong
password and the setup exits...
I use the command line to supply a password like
setup SAPWD="Pwd777b7" and then the setup seems to install or change some
files.
I click on the setup again and I get an error an invalid Instance name name
error. I have read and reread the (from a first user's point of view) the
very unhelpful help file I download with MSDE setup.
I have been going back and forth on this. Anyone know what's wrong... Anyone
know of a URL where I can find a step-by-step method of installing MSDE.
Thanks in advance
hi,
JP Bless wrote:
> I am trying to setup MSDE for the very first time. So I am absolutely
> a newbie. I downloaded sql2ksp3 from microsoft site. I unpacked the
> file to a folder and then clicked on setup.
> I get an error message about using the command line to supply a strong
> password and the setup exits...
> I use the command line to supply a password like
> setup SAPWD="Pwd777b7" and then the setup seems to install or change
> some files.
you should have a new default instace of MSDE installed, with no network
protocols enabled and allowing only Windows authenticated connections..
please verify using the Windows Services applet (control panel->management
tools->services) you have a MSSQLSERVER and SQLSERVERAGENT entry for the
related services...

> I click on the setup again and I get an error an invalid Instance
> name name error.
it failed as you tried that way to install a second default instance of MSDE
and ony 1 default instace is allowed... you can install other (up to 15, for
a max of 16 instances in total) named instances providing the additional
parameter
INSTANCENAME=whatever_name

>I have read and reread the (from a first user's
> point of view) the very unhelpful help file I download with MSDE
> setup.
> I have been going back and forth on this. Anyone know what's wrong...
> Anyone know of a URL where I can find a step-by-step method of
> installing MSDE.
>
if you can read/understand french,
http://perso.wanadoo.fr/jm.doudoux/m...msde/msde.htm, if you can
read/understand italian, http://www.visual-basic.it/articoli/scMsde01.htm,
but I do not know english sites
anyway, you should not just click on the setup.exe boostrap installer but
call it from a command window and provide all the required parameters,
usually (depending on your needs) in the form of
c:\...\>setupe.exe INSTANCENAME=whatever SAPWD=your_strong_pwd
SECURITYMODE=SQL DISABLENETWORKPROTOCOLS=0 /L*v "C:\MSDELOG.txt"
this typical command line will install a named instance named "whatever",
with "sa" login pwd = "your_strong_pwd", enabling SQL Server standard
connections (mixed mode authentication, allowing both integrated security a
standard SQL Server connections), enabling network protocols and thus
enabling remote connections and finally enabling verbose logging of the
installation process to a text file of about 2mb for a successfull
installation you can inspect in case of troubles for
RETURN VALUE 3
entries... this entries are localized in the particular MSDE localized
flavour, and 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
|||Thanks Andrea. It helped. Now I am done with with installation, I guess I
just cleared the first hurdle. My next task is to know how to add tables and
queries. I see there is no GUI (like Enterprise Manager) in the full/server
version, to administer/add table/Queries etc. Any tips where to begin?
Once again, thanks for the help, I really appreciate it.
Joe
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3rv3laFloeqnU1@.individual.net...
> hi,
> JP Bless wrote:
> you should have a new default instace of MSDE installed, with no network
> protocols enabled and allowing only Windows authenticated connections..
> please verify using the Windows Services applet (control panel->management
> tools->services) you have a MSSQLSERVER and SQLSERVERAGENT entry for the
> related services...
> it failed as you tried that way to install a second default instance of
MSDE
> and ony 1 default instace is allowed... you can install other (up to 15,
for
> a max of 16 instances in total) named instances providing the additional
> parameter
> INSTANCENAME=whatever_name
>
> if you can read/understand french,
> http://perso.wanadoo.fr/jm.doudoux/m...msde/msde.htm, if you can
> read/understand italian, http://www.visual-basic.it/articoli/scMsde01.htm,
> but I do not know english sites
> anyway, you should not just click on the setup.exe boostrap installer but
> call it from a command window and provide all the required parameters,
> usually (depending on your needs) in the form of
> c:\...\>setupe.exe INSTANCENAME=whatever SAPWD=your_strong_pwd
> SECURITYMODE=SQL DISABLENETWORKPROTOCOLS=0 /L*v "C:\MSDELOG.txt"
> this typical command line will install a named instance named "whatever",
> with "sa" login pwd = "your_strong_pwd", enabling SQL Server standard
> connections (mixed mode authentication, allowing both integrated security
a
> standard SQL Server connections), enabling network protocols and thus
> enabling remote connections and finally enabling verbose logging of the
> installation process to a text file of about 2mb for a successfull
> installation you can inspect in case of troubles for
> RETURN VALUE 3
> entries... this entries are localized in the particular MSDE localized
> flavour, and 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 Joe,
JP Bless wrote:
> Thanks Andrea. It helped. Now I am done with with installation, I
> guess I just cleared the first hurdle. My next task is to know how to
> add tables and queries. I see there is no GUI (like Enterprise
> Manager) in the full/server version, to administer/add table/Queries
> etc. Any tips where to begin?
>
my tip is to use the prj you can find at the link following my sign., which
provides free a user interface similar to Enterprise Manager written in vb6
on top of SQL-DMO object model as long as a lot of dynamic SQL :D, but I'm
deeply involved in that advice :D
you have further choices, both commercial and free at
http://www.microsoft.com/sql/msde/partners and
http://www.aspfaq.com/show.asp?id=2442
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
|||Thanks a million... I appreciate the help. I will look at the sites and
tools.
Once again thanks.
Joe
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3rvco3FkpmcvU1@.individual.net...
> hi Joe,
> JP Bless wrote:
> my tip is to use the prj you can find at the link following my sign.,
which
> provides free a user interface similar to Enterprise Manager written in
vb6
> on top of SQL-DMO object model as long as a lot of dynamic SQL :D, but I'm
> deeply involved in that advice :D
> you have further choices, both commercial and free at
> http://www.microsoft.com/sql/msde/partners and
> http://www.aspfaq.com/show.asp?id=2442
> --
> 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 Reinstall

Have reinstalled MSDE using Command Prompt Installation and received Errors.
Then I proceeded with a Batch.file installation and that seemed to work for the most part.

This is what I used for the Batch.file

setup.exe SAPWD=somename INSTANCENAME=somename SECURITYMODE=SQL

The Problem I ran into is - I can't seem to get the (SQL SERVER SERVICE MANAGER) to connect. I've entered the server name & instancename but so far no luck.

Ive checked - Control Panel/Administive Tools/Services - to make sure that it was installed & Yes it is there. So I Proceeded to start it up. Next I tried to Connect Via SERVER MANGER with no luck.
Then I did a c:\>osql -E check with the Command Line Prompt which returned the following message:

[Shared Memory]SQL Server does not exist or access denied.
[Shared Memory]ConnectionOpen <Connect<>>.

Tried again with c:\>osql -E -S
returned the same message.

[Shared Memory]SQL Server does not exist or access denied.
[Shared Memory]ConnectionOpen <Connect<>>.

Not sure what to do at this point any help/advice. Thx/TIA

(MSDE Version: sql2kdesksp3)
OS = XP ProUpdate:

Finally Managed to Connect to (SERVICE MANAGER) So now I have Connection with my server. I had to Specify ServerName\Instancename - and finally managed to connect.

But I can't seem to make a Database Connection In webMatrix. I entered The (USERName & Password Name) with no luck, even tried different combinations but still no luck!! USERNAME:Someusername**** (and) PASSWORD:SomePassword****

Is there a way I can create a New USERNAME & PASSWORD, with the command Line Prompt?
Anyone know how to do this? THX /TIS

Tristen|||view post 446484|||Thank you for Link/replying Bill,

Problem corrected. Reinstalled MSDE & Made a New SQL Authentication Password.|||Did "setup /upgradesp" help you?

MSDE Purge/shrink not allowed as it would take over 2048MB?

I have a database file which is close to the 2048MB limit, but not
there yet.
I am trying DELETE FROM TABLE many of the tables so that I can shrink
it and get under the 2048 limit.
When doing this, I get errors that ALTER (?) would put me over the
2048MB limit..?
I have many full blown SQL servers. This one just needs MSDE. I just
got a little behind in internal logging cleanup (not ldf.)
Can I move this file to a full blown SQL server, run my DELETE, then
move it back? What's the easiest way to do that? Remotely attach it
using UNC? Any better ways?
hi,
edavid3001@.gmail.com wrote:
> ...
> Can I move this file to a full blown SQL server, run my DELETE, then
> move it back?
yep...

> What's the easiest way to do that? Remotely attach it
> using UNC? Any better ways?
nope, I'd go detaching the database, moving corresponding physical files to
the full blown SQL Server machine, reattach it, delete/shrink, detach, move
and reattach, or, instead of detach/attach use backup/restore...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.16.0 - DbaMgr ver 0.61.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE or SQL on a DC?

I am running a small shop where we have a dual XEON (1) 2003 Standard Server
serving as our DC, File & Print and DNS server. We have the opportunity to
upgrade to an application we currently use but it will require us to install
SQL 2000 or MSDE on this server. My question is this, can SQL 2000 or MSDE
exist on the same box?
Thanks - Sean
Yes. However, consider the performance and security aspects of this. As for security, I'm particularly
referring to the service account. Is the machine is a DC, the account is now a domain account...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"HelpPls" <smd6169@.hotmail.com> wrote in message news:eNHg3u7NEHA.1312@.TK2MSFTNGP12.phx.gbl...
> I am running a small shop where we have a dual XEON (1) 2003 Standard Server
> serving as our DC, File & Print and DNS server. We have the opportunity to
> upgrade to an application we currently use but it will require us to install
> SQL 2000 or MSDE on this server. My question is this, can SQL 2000 or MSDE
> exist on the same box?
> Thanks - Sean
>

MSDE newbie quetsion: importing data from SQL Server

I've been given a file with no extension, and told that it's "a full
export from our SQL server tables".
What sort of file is this likely to be, and is there any way I can
import it into MSDE?
Simon Elliott http://www.ctsn.co.uk
hi Simon,
"Simon Elliott" <Simon at ctsn.co.uk> ha scritto nel messaggio
news:u5XG0NwQEHA.3728@.TK2MSFTNGP10.phx.gbl...
> I've been given a file with no extension, and told that it's "a full
> export from our SQL server tables".
> What sort of file is this likely to be, and is there any way I can
> import it into MSDE?
it really depend what kind of file it is...
it can be a full backup of a database, and you can test it executing from
any query tool
RESTORE HEADERONLY
FROM DISK = 'c:\....\filename'
which returns a result set indicating the content, if any and valid, of the
potential backup, or something like
Server: Msg 3242, Level 16, State 1, Line 1
The file on device 'd:\cursor.txt' is not a valid Microsoft Tape Format
backup set.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE HEADERONLY is terminating abnormally.
it can even be a DML sql file, containing a list of INSERT INTO statements
you have to execute to load an existing table... or a bulk copy export you
have to bulk insert..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||hi Simon,
"Simon Elliott" <Simon at ctsn.co.uk> ha scritto nel messaggio
news:%23ba4YhDREHA.3124@.TK2MSFTNGP12.phx.gbl...
> On 27/05/2004, Simon Elliott wrote:
> Is there a MSDE based on SQL Server 2000 available for free download?
>
yese, you can get the package at
http://www.microsoft.com/sql/msde/do...s/download.asp

> If so, how do I uninstall the current version? I've had no luck trying
> to uninstall it so far, as the uninstaller tells me that the service is
> still running, even if I have stopped it.
>
the uninstall applet shoul'd work as expected, but you can read
http://support.microsoft.com/default...oduct=sql&FR=1
for some hints on how to manually uninstall SQL Server 7.0 version...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||On 28/05/2004, Andrea Montanari wrote:
> yese, you can get the package at
> http://www.microsoft.com/sql/msde/do...s/download.asp
>
> the uninstall applet shoul'd work as expected, but you can read
> http://support.microsoft.com/default...276044&Product
> =sql&FR=1 for some hints on how to manually uninstall SQL Server 7.0
> version... --
OK, I'll give that a try. Thanks again for all your help.
Simon Elliott http://www.ctsn.co.uk

MSDE log file grown to 7 gig.

We have a software program that uses MSDE and the log file
is currently at 7 gigabytes in size which is abnormal.
When I do a backup using the softwares utility the backup
is only about 12 meg but when i restore to a fresh install
of windows the log file is right back at 7 gigabytes.
Whats wrong with the MSDE and how do it shrink/correct
this?
hi John,
"John P." <anonymous@.discussions.microsoft.com> ha scritto nel
messaggio news:02fb01c4ec23$aed1ebe0$3a01280a@.phx.gbl
> We have a software program that uses MSDE and the log file
> is currently at 7 gigabytes in size which is abnormal.
> When I do a backup using the softwares utility the backup
> is only about 12 meg but when i restore to a fresh install
> of windows the log file is right back at 7 gigabytes.
> Whats wrong with the MSDE and how do it shrink/correct
> this?
please have a look at MVP SQL Server Tibor Karaszi excellnt article on how
(and eventutally when) to shrink the transaction log at
http://www.karaszi.com/sqlserver/info_dont_shrink.asp ; the article also
contains links to Microsoft Knowledge Base to HOW TO articles to perform
correct backup/shrink operation
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
|||Also, make sure that the recovery mode is set to simple, for the database
the log is growing for, if you are not doing transaction log backups.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:33aucqF3pm2sjU1@.individual.net...
> hi John,
> "John P." <anonymous@.discussions.microsoft.com> ha scritto nel
> messaggio news:02fb01c4ec23$aed1ebe0$3a01280a@.phx.gbl
> please have a look at MVP SQL Server Tibor Karaszi excellnt article on how
> (and eventutally when) to shrink the transaction log at
> http://www.karaszi.com/sqlserver/info_dont_shrink.asp ; the article also
> contains links to Microsoft Knowledge Base to HOW TO articles to perform
> correct backup/shrink operation
> --
> 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 Derrick
"Derrick Leggett" <derrickleggett@.yahoo.com> ha scritto nel messaggio
news:%23x$S3rG7EHA.1292@.TK2MSFTNGP10.phx.gbl
> Also, make sure that the recovery mode is set to simple, for the
> database the log is growing for, if you are not doing transaction log
> backups.
about simple recovery model, I would not be that fast in changing it and I'd
consider my whole recovery strategy...
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
||| He obviously needs to do that. Until he does though, there is no reason
to have the database in simple recovery mode. He then has a constant
maintenance nightmare and something extra to worry about. He should set it
to simple, figure out what he's doing, then reapproach the situation.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:33dedaF3t60usU1@.individual.net...
> hi Derrick
> "Derrick Leggett" <derrickleggett@.yahoo.com> ha scritto nel messaggio
> news:%23x$S3rG7EHA.1292@.TK2MSFTNGP10.phx.gbl
> about simple recovery model, I would not be that fast in changing it and
I'd
> consider my whole recovery strategy...
> --
> 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 log file full

Getting error "msde log file is full, back up the transaction file for the database." I do not know how to clear out the log file for msde? Any help is greatly appreciated.
Thank you very much
If you need to keep your log backup sequence intact, you can
use something similar:
backup log msde
to disk = 'D:\PathToYourBackups\YourDB_Log.bak'
If you do not want to keep the log backup and can afford to
have the log sequence invalidated, you can use something
along the lines of:
backup log msde with truncate_only
For more information, refer to Backup in books online.
Additionally, if you aren't using the logs as part of your
recovery plan for the database, you can set it to simple
recovery.
-Sue
On Tue, 20 Apr 2004 17:36:04 -0700, Marion
<anonymous@.discussions.microsoft.com> wrote:

>Getting error "msde log file is full, back up the transaction file for the database." I do not know how to clear out the log file for msde? Any help is greatly appreciated.
>Thank you very much
|||Hi,
First check the recovery model for the database "MSDE". If it is FULL, you
need to backup the transaction log in frequent intervals. Otherwise
every time you will get this sort of error, even if you clear the log once.
I feel that you are using MSDE, You have to OSQL command line utility
OSQL -Usa -Ppassword -S Servername -Q"sp_helpdb MSDE"
If the recover model is FULL , then you have to Backup the transaction log
and shrink the transaction log file
From command prompt execute
OSQL -Usa -Ppassword -S Servername (Press enter, this will go to a prompt)
backup log MSDE to disk='d:\backup\dbname.trn'
go
dbcc shrinkfile('logical_log_file',truncateonly)
go
If the recovery model is SIMPLE then you do not want to schedule a
transaction log backup.
From command prompt execute
OSQL -Usa -Ppassword -S Servername (Press enter, this will go to a prompt)
backup log MSDE with truncate_only
go
dbcc shrinkfile('logical_log_file',truncateonly)
go
Note:
Logical Log file name can identified by executing:
OSQL -Usa -Ppassword -S Servername (Press enter, this will go to a prompt)
use MSDE
go
sp_helpfile
(The name column contains the logical file name)
Thanks
Hari
MCDBA
"Marion" <anonymous@.discussions.microsoft.com> wrote in message
news:7C1DFCCA-9BF5-478E-B7AB-21F027A638FE@.microsoft.com...
> Getting error "msde log file is full, back up the transaction file for the
database." I do not know how to clear out the log file for msde? Any help
is greatly appreciated.
> Thank you very much

msde log file full

Getting error "msde log file is full, back up the transaction file for the d
atabase." I do not know how to clear out the log file for msde? Any help i
s greatly appreciated.
Thank you very muchIf you need to keep your log backup sequence intact, you can
use something similar:
backup log msde
to disk = 'D:\PathToYourBackups\YourDB_Log.bak'
If you do not want to keep the log backup and can afford to
have the log sequence invalidated, you can use something
along the lines of:
backup log msde with truncate_only
For more information, refer to Backup in books online.
Additionally, if you aren't using the logs as part of your
recovery plan for the database, you can set it to simple
recovery.
-Sue
On Tue, 20 Apr 2004 17:36:04 -0700, Marion
<anonymous@.discussions.microsoft.com> wrote:

>Getting error "msde log file is full, back up the transaction file for the
database." I do not know how to clear out the log file for msde? Any help
is greatly appreciated.
>Thank you very much|||Hi,
First check the recovery model for the database "MSDE". If it is FULL, you
need to backup the transaction log in frequent intervals. Otherwise
every time you will get this sort of error, even if you clear the log once.
I feel that you are using MSDE, You have to OSQL command line utility
OSQL -Usa -Ppassword -S Servername -Q"sp_helpdb MSDE"
If the recover model is FULL , then you have to Backup the transaction log
and shrink the transaction log file
From command prompt execute
OSQL -Usa -Ppassword -S Servername (Press enter, this will go to a prompt)
backup log MSDE to disk='d:\backup\dbname.trn'
go
dbcc shrinkfile('logical_log_file',truncateon
ly)
go
If the recovery model is SIMPLE then you do not want to schedule a
transaction log backup.
From command prompt execute
OSQL -Usa -Ppassword -S Servername (Press enter, this will go to a prompt)
backup log MSDE with truncate_only
go
dbcc shrinkfile('logical_log_file',truncateon
ly)
go
Note:
Logical Log file name can identified by executing:
OSQL -Usa -Ppassword -S Servername (Press enter, this will go to a prompt)
use MSDE
go
sp_helpfile
(The name column contains the logical file name)
Thanks
Hari
MCDBA
"Marion" <anonymous@.discussions.microsoft.com> wrote in message
news:7C1DFCCA-9BF5-478E-B7AB-21F027A638FE@.microsoft.com...
> Getting error "msde log file is full, back up the transaction file for the
database." I do not know how to clear out the log file for msde? Any help
is greatly appreciated.
> Thank you very much

MSDE limitations lifted in Express?

8 connection limit, 2GB file size limit in MSDE? What are the limits in the
capabilities of SQL Express?
-billb
billb -
http://www.microsoft.com/technet/prodtechnol/sql/2005/msde2sqlexpress.mspx
No 8 connection limit, 4GB database size, and some other things are
different.
RLF
"William Bernat" <Wil86ianospammb86ernat@.cap86tanospamaris.com> wrote in
message news:urA1lqAaHHA.3268@.TK2MSFTNGP04.phx.gbl...
>8 connection limit, 2GB file size limit in MSDE? What are the limits in the
>capabilities of SQL Express?
> -billb
>
|||Although it was not really an '8 connection' limit. See Euan Garden's
Mythbuster BLOG. http://blogs.msdn.com/euanga/archive/2006/03/09/545576.aspx
RLF
|||Thanks Russell!!!
-billb
"Russell Fields" <russellfields@.nomail.com> wrote in message
news:ekDT08AaHHA.5056@.TK2MSFTNGP03.phx.gbl...
> Although it was not really an '8 connection' limit. See Euan Garden's
> Mythbuster BLOG.
> http://blogs.msdn.com/euanga/archive/2006/03/09/545576.aspx
>
> RLF
>
|||Indeed, there is not 8 concurrent queries limit, the 2GB database size
limit has been raised to 4GB, but the maximum RAM limit of 2GB has
been lowered to 1GB and SQL Server Agent is no longer included.
Razvan

MSDE limitations lifted in Express?

8 connection limit, 2GB file size limit in MSDE? What are the limits in the
capabilities of SQL Express?
-billbbillb -
http://www.microsoft.com/technet/pr...sqlexpress.mspx
No 8 connection limit, 4GB database size, and some other things are
different.
RLF
"William Bernat" < Wil86ianospammb86ernat@.cap86tanospamaris
.com> wrote in
message news:urA1lqAaHHA.3268@.TK2MSFTNGP04.phx.gbl...
>8 connection limit, 2GB file size limit in MSDE? What are the limits in the
>capabilities of SQL Express?
> -billb
>|||Although it was not really an '8 connection' limit. See Euan Garden's
Mythbuster BLOG. http://blogs.msdn.com/euanga/archiv.../09/545576.aspx
RLF|||Thanks Russell!!!
-billb
"Russell Fields" <russellfields@.nomail.com> wrote in message
news:ekDT08AaHHA.5056@.TK2MSFTNGP03.phx.gbl...
> Although it was not really an '8 connection' limit. See Euan Garden's
> Mythbuster BLOG.
> http://blogs.msdn.com/euanga/archiv.../09/545576.aspx
>
> RLF
>|||Indeed, there is not 8 concurrent queries limit, the 2GB database size
limit has been raised to 4GB, but the maximum RAM limit of 2GB has
been lowered to 1GB and SQL Server Agent is no longer included.
Razvan

MSDE limitations lifted in Express?

8 connection limit, 2GB file size limit in MSDE? What are the limits in the
capabilities of SQL Express?
-billbbillb -
http://www.microsoft.com/technet/prodtechnol/sql/2005/msde2sqlexpress.mspx
No 8 connection limit, 4GB database size, and some other things are
different.
RLF
"William Bernat" <Wil86ianospammb86ernat@.cap86tanospamaris.com> wrote in
message news:urA1lqAaHHA.3268@.TK2MSFTNGP04.phx.gbl...
>8 connection limit, 2GB file size limit in MSDE? What are the limits in the
>capabilities of SQL Express?
> -billb
>|||Although it was not really an '8 connection' limit. See Euan Garden's
Mythbuster BLOG. http://blogs.msdn.com/euanga/archive/2006/03/09/545576.aspx
RLF|||Thanks Russell!!!
-billb
"Russell Fields" <russellfields@.nomail.com> wrote in message
news:ekDT08AaHHA.5056@.TK2MSFTNGP03.phx.gbl...
> Although it was not really an '8 connection' limit. See Euan Garden's
> Mythbuster BLOG.
> http://blogs.msdn.com/euanga/archive/2006/03/09/545576.aspx
>
> RLF
>|||Indeed, there is not 8 concurrent queries limit, the 2GB database size
limit has been raised to 4GB, but the maximum RAM limit of 2GB has
been lowered to 1GB and SQL Server Agent is no longer included.
Razvan

MSDE installation without reboot

Hi all, I'm trying to install MSDE in silent mode and without using a .ini file (on a machine with windows 2000 server and SQL 2000 already insatalled).
At the end of the installation, the machine reboot automatically, but I need to stop this reboot to register some information and then reboot the machine.
Someone can help me?
Thanks all
Its something like 'REBOOT=REALLY_SUPPRESS'. Not sure about the spelling.
Its not documented in the SQL install but may be on MS site somewhere.
"A@.Rome" wrote:

> Hi all, I'm trying to install MSDE in silent mode and without using a .ini file (on a machine with windows 2000 server and SQL 2000 already insatalled).
> At the end of the installation, the machine reboot automatically, but I need to stop this reboot to register some information and then reboot the machine.
> Someone can help me?
> Thanks all
|||Thank you very much Jon, I'll try to look for that
"Jon Bishop" wrote:
[vbcol=seagreen]
> Its something like 'REBOOT=REALLY_SUPPRESS'. Not sure about the spelling.
> Its not documented in the SQL install but may be on MS site somewhere.
> "A@.Rome" wrote:
|||Jon, you're right. The exact spelling is 'reboot=reallysuppress' and it's the
option that REALLY suppress the reboot
Here it is the link to the research I've done restricted to the microsoft
support site:
http://www.google.com/search?hl=en&l...ally suppress
thank you so much, Andrew @. Rome
"Jon Bishop" wrote:
[vbcol=seagreen]
> Its something like 'REBOOT=REALLY_SUPPRESS'. Not sure about the spelling.
> Its not documented in the SQL install but may be on MS site somewhere.
> "A@.Rome" wrote:

MSDE Installation Fails

These are the last 3 lines the log file creates before
the installation stops. Does anyone know how to complete
the installation?
SOFTWARE\Microsoft\Microsoft SQL Server Setup.{E09B48B5-
E141-427A-AB0C-D3605127224A}
Starting custom action InstallSqlRedis
Executing "C:\Program Files\Microsoft SQL Server\80
\Tools\Binn\sqlredis.exe /q:a"
hi,
"Clete" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:19d401c4ad71$b5f839b0$a301280a@.phx.gbl
> These are the last 3 lines the log file creates before
> the installation stops. Does anyone know how to complete
> the installation?
> SOFTWARE\Microsoft\Microsoft SQL Server Setup.{E09B48B5-
> E141-427A-AB0C-D3605127224A}
> Starting custom action InstallSqlRedis
> Executing "C:\Program Files\Microsoft SQL Server\80
> \Tools\Binn\sqlredis.exe /q:a"
try manually installing MDAC 2.7.1 before MSDE ... get MDAC at
http://msdn.microsoft.com/data/Default.aspx
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 install worked 20 times now doesn't

Hi Group,
I've installed msde already about 20times and they all went ok, except one
but that had to do with file and printer sharing. Now I'm trying to install
it on win 2000 sp4 like all the others, but I can't get it to install, the
pc has got file and printer sharing enabled, it has got internet explorer 6
sp1, I checked HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\Component Set
Value name: InstanceComponentSet.x Value and it's emtpy, there's no value
name: InstanceComponentSet.x
I already searched on google and something that seems to be returning is
that I should post the lines from the log file where I find return value 3
so here they are with some lines that are in front and some lines that are
behind it, (btw you won't find return value 3 but you have to search for
retourwaarde 3, it logs some words in dutch)
Any help would be very welcome
thanks in advance Peter
WriteRegistryValues: Sleutel:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
D, Naam: CategoryCount, Waarde: #8
MSI (s) (7C:B0): Executing op:
RegAddValue(Name=CategoryMessageFile,Value=C:\Prof elExec\MSSQL$PFD\Binn\Reso
urces\1043\sqlevn70.rll,)
WriteRegistryValues: Sleutel:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
D, Naam: CategoryMessageFile, Waarde:
C:\PROFEL~2\MSSQL$~1\Binn\RESOUR~1\1043\sqlevn70.r ll
MSI (s) (7C:B0): Executing op:
RegAddValue(Name=EventMessageFile,Value=C:\ProfelE xec\MSSQL$PFD\Binn\Resourc
es\1043\sqlevn70.rll,)
WriteRegistryValues: Sleutel:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
D, Naam: EventMessageFile, Waarde:
C:\PROFEL~2\MSSQL$~1\Binn\RESOUR~1\1043\sqlevn70.r ll
MSI (s) (7C:B0): Executing op: RegAddValue(Name=TypesSupported,Value=#255,)
WriteRegistryValues: Sleutel:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
D, Naam: TypesSupported, Waarde: #255
MSI (s) (7C:B0): Executing op:
RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Microsoft SQL
Server\PFD\MSSQLServer\CurrentVersion,,BinaryType= 0)
MSI (s) (7C:B0): Executing op: RegAddValue(Name=Language,Value=#1043,)
WriteRegistryValues: Sleutel:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\PFD\MSSQLServer\CurrentVersion, Naam: Language, Waarde: #1043
MSI (s) (7C:B0): Executing op:
RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A
pplication\PFD,,BinaryType=0)
MSI (s) (7C:B0): Executing op: RegAddValue(Name=CategoryCount,Value=#8,)
WriteRegistryValues: Sleutel:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
D, Naam: CategoryCount, Waarde: #8
MSI (s) (7C:B0): Executing op:
RegAddValue(Name=CategoryMessageFile,Value=C:\Prof elExec\MSSQL$PFD\Binn\Reso
urces\1033\sqlevn70.rll,)
WriteRegistryValues: Sleutel:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
D, Naam: CategoryMessageFile, Waarde:
C:\PROFEL~2\MSSQL$~1\Binn\RESOUR~1\1033\sqlevn70.r ll
MSI (s) (7C:B0): Executing op:
RegAddValue(Name=EventMessageFile,Value=C:\ProfelE xec\MSSQL$PFD\Binn\Resourc
es\1033\sqlevn70.rll,)
WriteRegistryValues: Sleutel:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
D, Naam: EventMessageFile, Waarde:
C:\PROFEL~2\MSSQL$~1\Binn\RESOUR~1\1033\sqlevn70.r ll
MSI (s) (7C:B0): Executing op: RegAddValue(Name=TypesSupported,Value=#255,)
WriteRegistryValues: Sleutel:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
D, Naam: TypesSupported, Waarde: #255
MSI (s) (7C:B0): Executing op:
ActionStart(Name=WriteEnvironmentStrings,Descripti on=Bezig met het bijwerken
van omgevingsstrings,Template=Naam: , waarde: , actie )
Actie 11:48:29: WriteEnvironmentStrings. Bezig met het bijwerken van
omgevingsstrings
MSI (s) (7C:B0): Executing op:
ProgressTotal(Total=1,Type=1,ByteEquivalent=13200)
MSI (s) (7C:B0): Executing op:
UpdateEnvironmentStrings(Name=PATH,Value=C:\Progra m Files\Microsoft SQL
Server\80\Tools\Binn\,Delimiter=;,Action=161061273 8,)
WriteEnvironmentStrings: Naam: PATH, waarde: C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\, actie 1610612738
MSI (s) (7C:B0): Executing op:
ActionStart(Name=RegisterTypeLibraries,Description =Bezig met het registreren
van typebibliotheken,Template=Bibliotheek-id: )
Actie 11:48:29: RegisterTypeLibraries. Bezig met het registreren van
typebibliotheken
MSI (s) (7C:B0): Executing op: TypeLibraryRegister(,,FilePath=C:\Program
Files\Microsoft SQL
Server\80\Tools\Binn\SQLDMO.dll,LibID={10010001-E260-11CF-AE68-00AA004A34D5}
,Version=-2147483648,,Language=0,,BinaryType=0)
RegisterTypeLibraries: Bibliotheek-id:
{10010001-E260-11CF-AE68-00AA004A34D5}
MSI (s) (7C:B0): QueryPathOfRegTypeLib returned -2147319779 in local
context. Path is ''
MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
impersonated.
MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
MSI (s) (7C:B0): Executing op: TypeLibraryRegister(,,FilePath=C:\Program
Files\Microsoft SQL
Server\80\Tools\Binn\dtspkg.DLL,LibID={10010001-EB1C-11CF-AE6E-00AA004A34D5}
,Version=-2147483648,,Language=0,,BinaryType=0)
RegisterTypeLibraries: Bibliotheek-id:
{10010001-EB1C-11CF-AE6E-00AA004A34D5}
MSI (s) (7C:B0): QueryPathOfRegTypeLib returned -2147319779 in local
context. Path is ''
MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
impersonated.
MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
MSI (s) (7C:B0): Executing op: TypeLibraryRegister(,,FilePath=C:\Program
Files\Microsoft SQL
Server\80\Tools\Binn\dtspump.DLL,LibID={10010200-740B-11D0-AE7B-00AA004A34D5
},Version=-2147483648,,Language=0,,BinaryType=0)
RegisterTypeLibraries: Bibliotheek-id:
{10010200-740B-11D0-AE7B-00AA004A34D5}
MSI (s) (7C:B0): QueryPathOfRegTypeLib returned -2147319779 in local
context. Path is ''
MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
impersonated.
MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
MSI (s) (7C:B0): Executing op:
ActionStart(Name=InstallServices,Description=Bezig met het installeren van
nieuwe services,Template=Service: )
Actie 11:48:30: InstallServices. Bezig met het installeren van nieuwe
services
MSI (s) (7C:B0): Executing op:
ProgressTotal(Total=2,Type=1,ByteEquivalent=130000 0)
MSI (s) (7C:B0): Executing op:
ServiceInstall(Name=SQLAgent$PFD,DisplayName=SQLAg ent$PFD,ImagePath=C:\Profe
lExec\MSSQL$PFD\Binn\sqlagent.EXE -i
PFD,ServiceType=16,StartType=3,ErrorControl=1,,Dep endencies=MSSQL$PFD
MSI (s) (7C:B0): Executing op:
ServiceInstall(Name=MSSQL$PFD,DisplayName=MSSQL$PF D,ImagePath=C:\ProfelExec\
MSSQL$PFD\Binn\sqlservr.exe -sPFD,ServiceType=16,StartType=2,ErrorControl=1,
,,,,,)
MSI (s) (7C:B0): Executing op:
ActionStart(Name=InstallPerfMon.2D02443E_7002_4C0B _ABC9_EAB2C064397B,,)
Actie 11:48:32: InstallPerfMon.2D02443E_7002_4C0B_ABC9_EAB2C064397 B.
MSI (s) (7C:B0): Executing op:
CustomActionSchedule(Action=InstallPerfMon.2D02443 E_7002_4C0B_ABC9_EAB2C0643
97B,ActionType=1025,Source=BinaryData,Target=Insta llPerfMon,)
MSI (s) (7C:B0): Creating MSIHANDLE (496) of type 790536 for thread 688
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sq
lcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action InstallPerfMon
Registering performance counters from sqlctr.ini
PerfmonLoad routine returned error code 6
Actie beindigd 11:48:34: InstallFinalize. Retourwaarde 3.
MSI (s) (7C:B0): User policy value 'DisableRollback' is 0
MSI (s) (7C:B0): Machine policy value 'DisableRollback' is 0
MSI (s) (7C:B0): Executing op:
Header(Signature=1397708873,Version=200,Timestamp= 846618063,LangId=1043,Plat
form=0,ScriptType=2,ScriptMajorVersion=21,ScriptMi norVersion=4,ScriptAttribu
tes=1)
MSI (s) (7C:B0): Executing op: DialogInfo(Type=0,Argument=1043)
MSI (s) (7C:B0): Executing op: DialogInfo(Type=1,Argument=Microsoft SQL
Server Desktop Engine)
MSI (s) (7C:B0): Executing op:
RollbackInfo(,RollbackAction=Rollback,RollbackDesc ription=Terugdraai-actie:,
RollbackTemplate=,CleanupAction=RollbackCleanup,Cl eanupDescription=Bezig met
het verwijderen van reservekopiebestanden,CleanupTemplate=Bestand: [
1])
Actie 11:48:34: Rollback. Terugdraai-actie:
Rollback: InstallPerfMon.2D02443E_7002_4C0B_ABC9_EAB2C064397 B
MSI (s) (7C:B0): Executing op:
ActionStart(Name=InstallPerfMon.2D02443E_7002_4C0B _ABC9_EAB2C064397B,,)
MSI (s) (7C:B0): Executing op:
ProductInfo(ProductKey={E09B48B5-E141-427A-AB0C-D3605127224A},ProductName=Mi
crosoft SQL Server Desktop
Engine,PackageName=SqlRun01.msi,Language=1043,Vers ion=134218489,Assignment=1
,ObsoleteArg=0,,,PackageCode={D29DCF7A-8199-4
373-BA0D-2F3635EC940C},,,InstanceType=0)
Rollback: Bezig met het installeren van nieuwe services
MSI (s) (7C:B0): Executing op:
ActionStart(Name=InstallServices,Description=Bezig met het installeren van
nieuwe services,Template=Service: )
MSI (s) (7C:B0): Executing op: ServiceControl(,Name=MSSQL$PFD,Action=8,,)
MSI (s) (7C:B0): Executing op: ServiceControl(,Name=SQLAgent$PFD,Action=8,,)
Rollback: Bezig met het registreren van typebibliotheken
MSI (s) (7C:B0): Executing op:
ActionStart(Name=RegisterTypeLibraries,Description =Bezig met het registreren
van typebibliotheken,Template=Bibliotheek-id: )
MSI (s) (7C:B0): Executing op: TypeLibraryUnregister(,,FilePath=C:\Program
Files\Microsoft SQL
Server\80\Tools\Binn\dtspump.DLL,LibID={10010200-740B-11D0-AE7B-00AA004A34D5
},Version=-2147483648,,Language=0,,BinaryType=0)
MSI (s) (7C:B0): Note: 1: 1402 2:
UNKNOWN\TypeLib\{10010200-740B-11D0-AE7B-00AA004A34D5}\0.0\0\win32 3: 2
MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
impersonated.
MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
MSI (s) (7C:B0): Executing op: TypeLibraryUnregister(,,FilePath=C:\Program
Files\Microsoft SQL
Server\80\Tools\Binn\dtspkg.DLL,LibID={10010001-EB1C-11CF-AE6E-00AA004A34D5}
,Version=-2147483648,,Language=0,,BinaryType=0)
MSI (s) (7C:B0): Note: 1: 1402 2:
UNKNOWN\TypeLib\{10010001-EB1C-11CF-AE6E-00AA004A34D5}\0.0\0\win32 3: 2
MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
impersonated.
MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
MSI (s) (7C:B0): Executing op: TypeLibraryUnregister(,,FilePath=C:\Program
Files\Microsoft SQL
Server\80\Tools\Binn\SQLDMO.dll,LibID={10010001-E260-11CF-AE68-00AA004A34D5}
,Version=-2147483648,,Language=0,,BinaryType=0)
MSI (s) (7C:B0): Note: 1: 1402 2:
UNKNOWN\TypeLib\{10010001-E260-11CF-AE68-00AA004A34D5}\0.0\0\win32 3: 2
MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
impersonated.
MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
Rollback: Bezig met het bijwerken van omgevingsstrings
MSI (s) (7C:B0): Executing op:
ActionStart(Name=WriteEnvironmentStrings,Descripti on=Bezig met het bijwerken
van omgevingsstrings,Template=Naam: , waarde: , actie )
MSI (s) (7C:B0): Executing op:
RegOpenKey(Root=-2147483646,Key=System\CurrentControlSet\Control\Se ssion
Manager\Environment,,)
MSI (s) (7C:B0): Executing op:
RegAddValue(Name=PATH,Value=#%C:\PROGRA~1\MICROS~1 \OFFICE;%SYSTEMROOT%;%SYST
EMROOT%\COMMAND;"C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\";C:\PROGRA~1\MICROS~5\80\TOO LS\BINN;%SYSTEMROOT%\syste
m32;%SYSTEMROOT%\system3
2\WBEM,)
Rollback: Bezig met het schrijven van systeemregisterwaarden
MSI (s) (7C:B0): Executing op:
ActionStart(Name=WriteRegistryValues,Description=B ezig met het schrijven van
systeemregisterwaarden,Template=Sleutel: , Naam: , Waarde: )
MSI (s) (7C:B0): Executing op:
RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A
pplication\PFD,,BinaryType=0)
MSI (s) (7C:B0): Executing op:
RegRemoveValue(Name=TypesSupported,Value=#255,)
MSI (s) (7C:B0): Executing op: RegAddValue(Name=TypesSupported,Value=#255,)
MSI (s) (7C:B0): Executing op:
RegRemoveValue(Name=EventMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~
1\1033\sqlevn70.rll,)
MSI (s) (7C:B0): Executing op:
RegAddValue(Name=EventMessageFile,Value=C:\PROFEL~ 2\MSSQL$~1\Binn\RESOUR~1\1
043\sqlevn70.rll,)
MSI (s) (7C:B0): Executing op:
RegRemoveValue(Name=CategoryMessageFile,Value=C:\P ROFEL~2\MSSQL$~1\Binn\RESO
UR~1\1033\sqlevn70.rll,)
MSI (s) (7C:B0): Executing op:
RegAddValue(Name=CategoryMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~
1\1043\sqlevn70.rll,)
MSI (s) (7C:B0): Executing op: RegRemoveValue(Name=CategoryCount,Value=#8,)
MSI (s) (7C:B0): Executing op: RegAddValue(Name=CategoryCount,Value=#8,)
MSI (s) (7C:B0): Executing op:
RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Microsoft SQL
Server\PFD\MSSQLServer\CurrentVersion,,BinaryType= 0)
MSI (s) (7C:B0): Executing op: RegRemoveValue(Name=Language,Value=#1043,)
MSI (s) (7C:B0): Executing op: RegAddValue(Name=Language,Value=#1043,)
MSI (s) (7C:B0): Executing op:
RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A
pplication\PFD,,BinaryType=0)
MSI (s) (7C:B0): Executing op:
RegRemoveValue(Name=TypesSupported,Value=#255,)
MSI (s) (7C:B0): Executing op: RegCreateKey()
MSI (s) (7C:B0): Executing op:
RegRemoveValue(Name=EventMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~
1\1043\sqlevn70.rll,)
MSI (s) (7C:B0): Executing op: RegCreateKey()
MSI (s) (7C:B0): Executing op:
RegRemoveValue(Name=CategoryMessageFile,Value=C:\P ROFEL~2\MSSQL$~1\Binn\RESO
UR~1\1043\sqlevn70.rll,)
MSI (s) (7C:B0): Executing op: RegCreateKey()
MSI (s) (7C:B0): Executing op: RegRemoveValue(Name=CategoryCount,Value=#8,)
MSI (s) (7C:B0): Executing op: RegRemoveKey()
Peter,
I have exactly the same problem. I cannot install MSDE 2000 on a Windows XP
Pro SP2 machine. The install rolls back every time at exactly the same point
as yours. I posted here but did not get the answer. It may have something to
do with with manually deleting registry keys and Windows Installer parameters
to enable a "clean" install. I thought I did all the necessary steps but have
never been able to make it work. I will be watching your replies with
interest to see if you are able to get it installed.
Good luck!
"Peter Proost" wrote:

> Hi Group,
> I've installed msde already about 20times and they all went ok, except one
> but that had to do with file and printer sharing. Now I'm trying to install
> it on win 2000 sp4 like all the others, but I can't get it to install, the
> pc has got file and printer sharing enabled, it has got internet explorer 6
> sp1, I checked HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
> Server\Component Set
> Value name: InstanceComponentSet.x Value and it's emtpy, there's no value
> name: InstanceComponentSet.x
> I already searched on google and something that seems to be returning is
> that I should post the lines from the log file where I find return value 3
> so here they are with some lines that are in front and some lines that are
> behind it, (btw you won't find return value 3 but you have to search for
> retourwaarde 3, it logs some words in dutch)
> Any help would be very welcome
> thanks in advance Peter
> WriteRegistryValues: Sleutel:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> D, Naam: CategoryCount, Waarde: #8
> MSI (s) (7C:B0): Executing op:
> RegAddValue(Name=CategoryMessageFile,Value=C:\Prof elExec\MSSQL$PFD\Binn\Reso
> urces\1043\sqlevn70.rll,)
> WriteRegistryValues: Sleutel:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> D, Naam: CategoryMessageFile, Waarde:
> C:\PROFEL~2\MSSQL$~1\Binn\RESOUR~1\1043\sqlevn70.r ll
> MSI (s) (7C:B0): Executing op:
> RegAddValue(Name=EventMessageFile,Value=C:\ProfelE xec\MSSQL$PFD\Binn\Resourc
> es\1043\sqlevn70.rll,)
> WriteRegistryValues: Sleutel:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> D, Naam: EventMessageFile, Waarde:
> C:\PROFEL~2\MSSQL$~1\Binn\RESOUR~1\1043\sqlevn70.r ll
> MSI (s) (7C:B0): Executing op: RegAddValue(Name=TypesSupported,Value=#255,)
> WriteRegistryValues: Sleutel:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> D, Naam: TypesSupported, Waarde: #255
> MSI (s) (7C:B0): Executing op:
> RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Microsoft SQL
> Server\PFD\MSSQLServer\CurrentVersion,,BinaryType= 0)
> MSI (s) (7C:B0): Executing op: RegAddValue(Name=Language,Value=#1043,)
> WriteRegistryValues: Sleutel:
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
> Server\PFD\MSSQLServer\CurrentVersion, Naam: Language, Waarde: #1043
> MSI (s) (7C:B0): Executing op:
> RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A
> pplication\PFD,,BinaryType=0)
> MSI (s) (7C:B0): Executing op: RegAddValue(Name=CategoryCount,Value=#8,)
> WriteRegistryValues: Sleutel:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> D, Naam: CategoryCount, Waarde: #8
> MSI (s) (7C:B0): Executing op:
> RegAddValue(Name=CategoryMessageFile,Value=C:\Prof elExec\MSSQL$PFD\Binn\Reso
> urces\1033\sqlevn70.rll,)
> WriteRegistryValues: Sleutel:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> D, Naam: CategoryMessageFile, Waarde:
> C:\PROFEL~2\MSSQL$~1\Binn\RESOUR~1\1033\sqlevn70.r ll
> MSI (s) (7C:B0): Executing op:
> RegAddValue(Name=EventMessageFile,Value=C:\ProfelE xec\MSSQL$PFD\Binn\Resourc
> es\1033\sqlevn70.rll,)
> WriteRegistryValues: Sleutel:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> D, Naam: EventMessageFile, Waarde:
> C:\PROFEL~2\MSSQL$~1\Binn\RESOUR~1\1033\sqlevn70.r ll
> MSI (s) (7C:B0): Executing op: RegAddValue(Name=TypesSupported,Value=#255,)
> WriteRegistryValues: Sleutel:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> D, Naam: TypesSupported, Waarde: #255
> MSI (s) (7C:B0): Executing op:
> ActionStart(Name=WriteEnvironmentStrings,Descripti on=Bezig met het bijwerken
> van omgevingsstrings,Template=Naam: , waarde: , actie )
> Actie 11:48:29: WriteEnvironmentStrings. Bezig met het bijwerken van
> omgevingsstrings
> MSI (s) (7C:B0): Executing op:
> ProgressTotal(Total=1,Type=1,ByteEquivalent=13200)
> MSI (s) (7C:B0): Executing op:
> UpdateEnvironmentStrings(Name=PATH,Value=C:\Progra m Files\Microsoft SQL
> Server\80\Tools\Binn\,Delimiter=;,Action=161061273 8,)
> WriteEnvironmentStrings: Naam: PATH, waarde: C:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\, actie 1610612738
> MSI (s) (7C:B0): Executing op:
> ActionStart(Name=RegisterTypeLibraries,Description =Bezig met het registreren
> van typebibliotheken,Template=Bibliotheek-id: )
> Actie 11:48:29: RegisterTypeLibraries. Bezig met het registreren van
> typebibliotheken
> MSI (s) (7C:B0): Executing op: TypeLibraryRegister(,,FilePath=C:\Program
> Files\Microsoft SQL
> Server\80\Tools\Binn\SQLDMO.dll,LibID={10010001-E260-11CF-AE68-00AA004A34D5}
> ,Version=-2147483648,,Language=0,,BinaryType=0)
> RegisterTypeLibraries: Bibliotheek-id:
> {10010001-E260-11CF-AE68-00AA004A34D5}
> MSI (s) (7C:B0): QueryPathOfRegTypeLib returned -2147319779 in local
> context. Path is ''
> MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
> impersonated.
> MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
> MSI (s) (7C:B0): Executing op: TypeLibraryRegister(,,FilePath=C:\Program
> Files\Microsoft SQL
> Server\80\Tools\Binn\dtspkg.DLL,LibID={10010001-EB1C-11CF-AE6E-00AA004A34D5}
> ,Version=-2147483648,,Language=0,,BinaryType=0)
> RegisterTypeLibraries: Bibliotheek-id:
> {10010001-EB1C-11CF-AE6E-00AA004A34D5}
> MSI (s) (7C:B0): QueryPathOfRegTypeLib returned -2147319779 in local
> context. Path is ''
> MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
> impersonated.
> MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
> MSI (s) (7C:B0): Executing op: TypeLibraryRegister(,,FilePath=C:\Program
> Files\Microsoft SQL
> Server\80\Tools\Binn\dtspump.DLL,LibID={10010200-740B-11D0-AE7B-00AA004A34D5
> },Version=-2147483648,,Language=0,,BinaryType=0)
> RegisterTypeLibraries: Bibliotheek-id:
> {10010200-740B-11D0-AE7B-00AA004A34D5}
> MSI (s) (7C:B0): QueryPathOfRegTypeLib returned -2147319779 in local
> context. Path is ''
> MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
> impersonated.
> MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
> MSI (s) (7C:B0): Executing op:
> ActionStart(Name=InstallServices,Description=Bezig met het installeren van
> nieuwe services,Template=Service: )
> Actie 11:48:30: InstallServices. Bezig met het installeren van nieuwe
> services
> MSI (s) (7C:B0): Executing op:
> ProgressTotal(Total=2,Type=1,ByteEquivalent=130000 0)
> MSI (s) (7C:B0): Executing op:
> ServiceInstall(Name=SQLAgent$PFD,DisplayName=SQLAg ent$PFD,ImagePath=C:\Profe
> lExec\MSSQL$PFD\Binn\sqlagent.EXE -i
> PFD,ServiceType=16,StartType=3,ErrorControl=1,,Dep endencies=MSSQL$PFD
> MSI (s) (7C:B0): Executing op:
> ServiceInstall(Name=MSSQL$PFD,DisplayName=MSSQL$PF D,ImagePath=C:\ProfelExec\
> MSSQL$PFD\Binn\sqlservr.exe -sPFD,ServiceType=16,StartType=2,ErrorControl=1,
> ,,,,,)
> MSI (s) (7C:B0): Executing op:
> ActionStart(Name=InstallPerfMon.2D02443E_7002_4C0B _ABC9_EAB2C064397B,,)
> Actie 11:48:32: InstallPerfMon.2D02443E_7002_4C0B_ABC9_EAB2C064397 B.
> MSI (s) (7C:B0): Executing op:
> CustomActionSchedule(Action=InstallPerfMon.2D02443 E_7002_4C0B_ABC9_EAB2C0643
> 97B,ActionType=1025,Source=BinaryData,Target=Insta llPerfMon,)
> MSI (s) (7C:B0): Creating MSIHANDLE (496) of type 790536 for thread 688
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> TempFolder is
> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
> Loading extended custom action library
> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sq
> lcax.dll
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> Starting custom action InstallPerfMon
> Registering performance counters from sqlctr.ini
> PerfmonLoad routine returned error code 6
> Actie be?indigd 11:48:34: InstallFinalize. Retourwaarde 3.
> MSI (s) (7C:B0): User policy value 'DisableRollback' is 0
> MSI (s) (7C:B0): Machine policy value 'DisableRollback' is 0
> MSI (s) (7C:B0): Executing op:
> Header(Signature=1397708873,Version=200,Timestamp= 846618063,LangId=1043,Plat
> form=0,ScriptType=2,ScriptMajorVersion=21,ScriptMi norVersion=4,ScriptAttribu
> tes=1)
> MSI (s) (7C:B0): Executing op: DialogInfo(Type=0,Argument=1043)
> MSI (s) (7C:B0): Executing op: DialogInfo(Type=1,Argument=Microsoft SQL
> Server Desktop Engine)
> MSI (s) (7C:B0): Executing op:
> RollbackInfo(,RollbackAction=Rollback,RollbackDesc ription=Terugdraai-actie:,
> RollbackTemplate=,CleanupAction=RollbackCleanup,Cl eanupDescription=Bezig met
> het verwijderen van reservekopiebestanden,CleanupTemplate=Bestand: [
> 1])
> Actie 11:48:34: Rollback. Terugdraai-actie:
> Rollback: InstallPerfMon.2D02443E_7002_4C0B_ABC9_EAB2C064397 B
> MSI (s) (7C:B0): Executing op:
> ActionStart(Name=InstallPerfMon.2D02443E_7002_4C0B _ABC9_EAB2C064397B,,)
> MSI (s) (7C:B0): Executing op:
> ProductInfo(ProductKey={E09B48B5-E141-427A-AB0C-D3605127224A},ProductName=Mi
> crosoft SQL Server Desktop
> Engine,PackageName=SqlRun01.msi,Language=1043,Vers ion=134218489,Assignment=1
> ,ObsoleteArg=0,,,PackageCode={D29DCF7A-8199-4
> 373-BA0D-2F3635EC940C},,,InstanceType=0)
> Rollback: Bezig met het installeren van nieuwe services
> MSI (s) (7C:B0): Executing op:
> ActionStart(Name=InstallServices,Description=Bezig met het installeren van
> nieuwe services,Template=Service: )
> MSI (s) (7C:B0): Executing op: ServiceControl(,Name=MSSQL$PFD,Action=8,,)
> MSI (s) (7C:B0): Executing op: ServiceControl(,Name=SQLAgent$PFD,Action=8,,)
> Rollback: Bezig met het registreren van typebibliotheken
> MSI (s) (7C:B0): Executing op:
> ActionStart(Name=RegisterTypeLibraries,Description =Bezig met het registreren
> van typebibliotheken,Template=Bibliotheek-id: )
> MSI (s) (7C:B0): Executing op: TypeLibraryUnregister(,,FilePath=C:\Program
> Files\Microsoft SQL
> Server\80\Tools\Binn\dtspump.DLL,LibID={10010200-740B-11D0-AE7B-00AA004A34D5
> },Version=-2147483648,,Language=0,,BinaryType=0)
> MSI (s) (7C:B0): Note: 1: 1402 2:
> UNKNOWN\TypeLib\{10010200-740B-11D0-AE7B-00AA004A34D5}\0.0\0\win32 3: 2
> MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
> impersonated.
> MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
> MSI (s) (7C:B0): Executing op: TypeLibraryUnregister(,,FilePath=C:\Program
> Files\Microsoft SQL
> Server\80\Tools\Binn\dtspkg.DLL,LibID={10010001-EB1C-11CF-AE6E-00AA004A34D5}
> ,Version=-2147483648,,Language=0,,BinaryType=0)
> MSI (s) (7C:B0): Note: 1: 1402 2:
> UNKNOWN\TypeLib\{10010001-EB1C-11CF-AE6E-00AA004A34D5}\0.0\0\win32 3: 2
> MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
> impersonated.
> MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
> MSI (s) (7C:B0): Executing op: TypeLibraryUnregister(,,FilePath=C:\Program
> Files\Microsoft SQL
> Server\80\Tools\Binn\SQLDMO.dll,LibID={10010001-E260-11CF-AE68-00AA004A34D5}
> ,Version=-2147483648,,Language=0,,BinaryType=0)
> MSI (s) (7C:B0): Note: 1: 1402 2:
> UNKNOWN\TypeLib\{10010001-E260-11CF-AE68-00AA004A34D5}\0.0\0\win32 3: 2
> MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
> impersonated.
> MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
> Rollback: Bezig met het bijwerken van omgevingsstrings
> MSI (s) (7C:B0): Executing op:
> ActionStart(Name=WriteEnvironmentStrings,Descripti on=Bezig met het bijwerken
> van omgevingsstrings,Template=Naam: , waarde: , actie )
> MSI (s) (7C:B0): Executing op:
> RegOpenKey(Root=-2147483646,Key=System\CurrentControlSet\Control\Se ssion
> Manager\Environment,,)
> MSI (s) (7C:B0): Executing op:
> RegAddValue(Name=PATH,Value=#%C:\PROGRA~1\MICROS~1 \OFFICE;%SYSTEMROOT%;%SYST
> EMROOT%\COMMAND;"C:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\";C:\PROGRA~1\MICROS~5\80\TOO LS\BINN;%SYSTEMROOT%\syste
> m32;%SYSTEMROOT%\system3
> 2\WBEM,)
> Rollback: Bezig met het schrijven van systeemregisterwaarden
> MSI (s) (7C:B0): Executing op:
> ActionStart(Name=WriteRegistryValues,Description=B ezig met het schrijven van
> systeemregisterwaarden,Template=Sleutel: , Naam: , Waarde: )
> MSI (s) (7C:B0): Executing op:
> RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A
> pplication\PFD,,BinaryType=0)
> MSI (s) (7C:B0): Executing op:
> RegRemoveValue(Name=TypesSupported,Value=#255,)
> MSI (s) (7C:B0): Executing op: RegAddValue(Name=TypesSupported,Value=#255,)
> MSI (s) (7C:B0): Executing op:
> RegRemoveValue(Name=EventMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~
> 1\1033\sqlevn70.rll,)
> MSI (s) (7C:B0): Executing op:
> RegAddValue(Name=EventMessageFile,Value=C:\PROFEL~ 2\MSSQL$~1\Binn\RESOUR~1\1
> 043\sqlevn70.rll,)
> MSI (s) (7C:B0): Executing op:
> RegRemoveValue(Name=CategoryMessageFile,Value=C:\P ROFEL~2\MSSQL$~1\Binn\RESO
> UR~1\1033\sqlevn70.rll,)
> MSI (s) (7C:B0): Executing op:
> RegAddValue(Name=CategoryMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~
> 1\1043\sqlevn70.rll,)
> MSI (s) (7C:B0): Executing op: RegRemoveValue(Name=CategoryCount,Value=#8,)
> MSI (s) (7C:B0): Executing op: RegAddValue(Name=CategoryCount,Value=#8,)
> MSI (s) (7C:B0): Executing op:
> RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Microsoft SQL
> Server\PFD\MSSQLServer\CurrentVersion,,BinaryType= 0)
> MSI (s) (7C:B0): Executing op: RegRemoveValue(Name=Language,Value=#1043,)
> MSI (s) (7C:B0): Executing op: RegAddValue(Name=Language,Value=#1043,)
> MSI (s) (7C:B0): Executing op:
> RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A
> pplication\PFD,,BinaryType=0)
> MSI (s) (7C:B0): Executing op:
> RegRemoveValue(Name=TypesSupported,Value=#255,)
> MSI (s) (7C:B0): Executing op: RegCreateKey()
> MSI (s) (7C:B0): Executing op:
> RegRemoveValue(Name=EventMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~
> 1\1043\sqlevn70.rll,)
> MSI (s) (7C:B0): Executing op: RegCreateKey()
> MSI (s) (7C:B0): Executing op:
> RegRemoveValue(Name=CategoryMessageFile,Value=C:\P ROFEL~2\MSSQL$~1\Binn\RESO
> UR~1\1043\sqlevn70.rll,)
> MSI (s) (7C:B0): Executing op: RegCreateKey()
> MSI (s) (7C:B0): Executing op: RegRemoveValue(Name=CategoryCount,Value=#8,)
> MSI (s) (7C:B0): Executing op: RegRemoveKey()
>
>
|||Hi Stephen,
I got it to work, but hold your breath, only after reinstalling windows
because it had something to do with corrupted performance counters in the
registry. I tried evertyhting in this link
http://support.microsoft.com/default...microsoft.com:
80/support/kb/articles/q315/0/83.asp&NoWebContent=1
but I didn't get it to work, just for your info the pc was an upgraded one,
I upgraded it from me to 2000 I think there went something wrong there.
Maybe this link can help you
greetz Peter
"Stephen Bishop" <StephenBishop@.discussions.microsoft.com> schreef in
bericht news:9197FA53-F560-4CDC-847E-E81D354D1CE5@.microsoft.com...
> Peter,
> I have exactly the same problem. I cannot install MSDE 2000 on a Windows
XP
> Pro SP2 machine. The install rolls back every time at exactly the same
point
> as yours. I posted here but did not get the answer. It may have something
to
> do with with manually deleting registry keys and Windows Installer
parameters
> to enable a "clean" install. I thought I did all the necessary steps but
have[vbcol=seagreen]
> never been able to make it work. I will be watching your replies with
> interest to see if you are able to get it installed.
> Good luck!
> "Peter Proost" wrote:
one[vbcol=seagreen]
install[vbcol=seagreen]
the[vbcol=seagreen]
explorer 6[vbcol=seagreen]
value[vbcol=seagreen]
3[vbcol=seagreen]
are[vbcol=seagreen]
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF[vbcol=seagreen]
RegAddValue(Name=CategoryMessageFile,Value=C:\Prof elExec\MSSQL$PFD\Binn\Reso[vbcol=seagreen]
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF[vbcol=seagreen]
RegAddValue(Name=EventMessageFile,Value=C:\ProfelE xec\MSSQL$PFD\Binn\Resourc[vbcol=seagreen]
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF[vbcol=seagreen]
RegAddValue(Name=TypesSupported,Value=#255,)[vbcol=seagreen]
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF[vbcol=seagreen]
RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A[vbcol=seagreen]
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF[vbcol=seagreen]
RegAddValue(Name=CategoryMessageFile,Value=C:\Prof elExec\MSSQL$PFD\Binn\Reso[vbcol=seagreen]
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF[vbcol=seagreen]
RegAddValue(Name=EventMessageFile,Value=C:\ProfelE xec\MSSQL$PFD\Binn\Resourc[vbcol=seagreen]
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF[vbcol=seagreen]
RegAddValue(Name=TypesSupported,Value=#255,)[vbcol=seagreen]
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF[vbcol=seagreen]
bijwerken[vbcol=seagreen]
SQL[vbcol=seagreen]
registreren[vbcol=seagreen]
Server\80\Tools\Binn\SQLDMO.dll,LibID={10010001-E260-11CF-AE68-00AA004A34D5}[vbcol=seagreen]
not[vbcol=seagreen]
Server\80\Tools\Binn\dtspkg.DLL,LibID={10010001-EB1C-11CF-AE6E-00AA004A34D5}[vbcol=seagreen]
not[vbcol=seagreen]
Server\80\Tools\Binn\dtspump.DLL,LibID={10010200-740B-11D0-AE7B-00AA004A34D5[vbcol=seagreen]
not[vbcol=seagreen]
van[vbcol=seagreen]
ServiceInstall(Name=SQLAgent$PFD,DisplayName=SQLAg ent$PFD,ImagePath=C:\Profe[vbcol=seagreen]
ServiceInstall(Name=MSSQL$PFD,DisplayName=MSSQL$PF D,ImagePath=C:\ProfelExec\[vbcol=seagreen]
MSSQL$PFD\Binn\sqlservr.exe -sPFD,ServiceType=16,StartType=2,ErrorControl=1,[vbcol=seagreen]
CustomActionSchedule(Action=InstallPerfMon.2D02443 E_7002_4C0B_ABC9_EAB2C0643[vbcol=seagreen]
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\[vbcol=seagreen]
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sq[vbcol=seagreen]
Header(Signature=1397708873,Version=200,Timestamp= 846618063,LangId=1043,Plat[vbcol=seagreen]
form=0,ScriptType=2,ScriptMajorVersion=21,ScriptMi norVersion=4,ScriptAttribu[vbcol=seagreen]
RollbackInfo(,RollbackAction=Rollback,RollbackDesc ription=Terugdraai-actie:,[vbcol=seagreen]
met[vbcol=seagreen]
ProductInfo(ProductKey={E09B48B5-E141-427A-AB0C-D3605127224A},ProductName=Mi[vbcol=seagreen]
Engine,PackageName=SqlRun01.msi,Language=1043,Vers ion=134218489,Assignment=1[vbcol=seagreen]
van[vbcol=seagreen]
ServiceControl(,Name=MSSQL$PFD,Action=8,,)[vbcol=seagreen]
ServiceControl(,Name=SQLAgent$PFD,Action=8,,)[vbcol=seagreen]
registreren[vbcol=seagreen]
TypeLibraryUnregister(,,FilePath=C:\Program[vbcol=seagreen]
Server\80\Tools\Binn\dtspump.DLL,LibID={10010200-740B-11D0-AE7B-00AA004A34D5[vbcol=seagreen]
not[vbcol=seagreen]
TypeLibraryUnregister(,,FilePath=C:\Program[vbcol=seagreen]
Server\80\Tools\Binn\dtspkg.DLL,LibID={10010001-EB1C-11CF-AE6E-00AA004A34D5}[vbcol=seagreen]
not[vbcol=seagreen]
TypeLibraryUnregister(,,FilePath=C:\Program[vbcol=seagreen]
Server\80\Tools\Binn\SQLDMO.dll,LibID={10010001-E260-11CF-AE68-00AA004A34D5}[vbcol=seagreen]
not[vbcol=seagreen]
bijwerken[vbcol=seagreen]
RegAddValue(Name=PATH,Value=#%C:\PROGRA~1\MICROS~1 \OFFICE;%SYSTEMROOT%;%SYST[vbcol=seagreen]
Server\80\Tools\Binn\";C:\PROGRA~1\MICROS~5\80\TOO LS\BINN;%SYSTEMROOT%\syste[vbcol=seagreen]
van[vbcol=seagreen]
RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A[vbcol=seagreen]
RegAddValue(Name=TypesSupported,Value=#255,)[vbcol=seagreen]
RegRemoveValue(Name=EventMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~[vbcol=seagreen]
RegAddValue(Name=EventMessageFile,Value=C:\PROFEL~ 2\MSSQL$~1\Binn\RESOUR~1\1[vbcol=seagreen]
RegRemoveValue(Name=CategoryMessageFile,Value=C:\P ROFEL~2\MSSQL$~1\Binn\RESO[vbcol=seagreen]
RegAddValue(Name=CategoryMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~[vbcol=seagreen]
RegRemoveValue(Name=CategoryCount,Value=#8,)[vbcol=seagreen]
RegRemoveValue(Name=Language,Value=#1043,)[vbcol=seagreen]
RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A[vbcol=seagreen]
RegRemoveValue(Name=EventMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~[vbcol=seagreen]
RegRemoveValue(Name=CategoryMessageFile,Value=C:\P ROFEL~2\MSSQL$~1\Binn\RESO[vbcol=seagreen]
RegRemoveValue(Name=CategoryCount,Value=#8,)[vbcol=seagreen]
|||Hi Peter,
Thanks for the reply. We have identical scenarios! I upgraded from ME to XP
Home, then upgraded again to XP Pro, SP2. I will take a look at the link you
posted, but it appears that I am probably headed toward the same conclusion
you reached - a complete reinstall of XP!
Thanks again and good luck!
"Peter Proost" wrote:

> Hi Stephen,
> I got it to work, but hold your breath, only after reinstalling windows
> because it had something to do with corrupted performance counters in the
> registry. I tried evertyhting in this link
> http://support.microsoft.com/default...microsoft.com:
> 80/support/kb/articles/q315/0/83.asp&NoWebContent=1
> but I didn't get it to work, just for your info the pc was an upgraded one,
> I upgraded it from me to 2000 I think there went something wrong there.
> Maybe this link can help you
> greetz Peter
>
> "Stephen Bishop" <StephenBishop@.discussions.microsoft.com> schreef in
> bericht news:9197FA53-F560-4CDC-847E-E81D354D1CE5@.microsoft.com...
> XP
> point
> to
> parameters
> have
> one
> install
> the
> explorer 6
> value
> 3
> are
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> RegAddValue(Name=CategoryMessageFile,Value=C:\Prof elExec\MSSQL$PFD\Binn\Reso
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> RegAddValue(Name=EventMessageFile,Value=C:\ProfelE xec\MSSQL$PFD\Binn\Resourc
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> RegAddValue(Name=TypesSupported,Value=#255,)
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> RegAddValue(Name=CategoryMessageFile,Value=C:\Prof elExec\MSSQL$PFD\Binn\Reso
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> RegAddValue(Name=EventMessageFile,Value=C:\ProfelE xec\MSSQL$PFD\Binn\Resourc
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> RegAddValue(Name=TypesSupported,Value=#255,)
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> bijwerken
> SQL
> registreren
> Server\80\Tools\Binn\SQLDMO.dll,LibID={10010001-E260-11CF-AE68-00AA004A34D5}
> not
> Server\80\Tools\Binn\dtspkg.DLL,LibID={10010001-EB1C-11CF-AE6E-00AA004A34D5}
> not
> Server\80\Tools\Binn\dtspump.DLL,LibID={10010200-740B-11D0-AE7B-00AA004A34D5
> not
> van
> ServiceInstall(Name=SQLAgent$PFD,DisplayName=SQLAg ent$PFD,ImagePath=C:\Profe
> ServiceInstall(Name=MSSQL$PFD,DisplayName=MSSQL$PF D,ImagePath=C:\ProfelExec\
> MSSQL$PFD\Binn\sqlservr.exe -sPFD,ServiceType=16,StartType=2,ErrorControl=1,
> CustomActionSchedule(Action=InstallPerfMon.2D02443 E_7002_4C0B_ABC9_EAB2C0643
> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sq
> Header(Signature=1397708873,Version=200,Timestamp= 846618063,LangId=1043,Plat
> form=0,ScriptType=2,ScriptMajorVersion=21,ScriptMi norVersion=4,ScriptAttribu
> RollbackInfo(,RollbackAction=Rollback,RollbackDesc ription=Terugdraai-actie:,
> met
> ProductInfo(ProductKey={E09B48B5-E141-427A-AB0C-D3605127224A},ProductName=Mi
> Engine,PackageName=SqlRun01.msi,Language=1043,Vers ion=134218489,Assignment=1
> van
> ServiceControl(,Name=MSSQL$PFD,Action=8,,)
> ServiceControl(,Name=SQLAgent$PFD,Action=8,,)
> registreren
> TypeLibraryUnregister(,,FilePath=C:\Program
> Server\80\Tools\Binn\dtspump.DLL,LibID={10010200-740B-11D0-AE7B-00AA004A34D5
> not
> TypeLibraryUnregister(,,FilePath=C:\Program
> Server\80\Tools\Binn\dtspkg.DLL,LibID={10010001-EB1C-11CF-AE6E-00AA004A34D5}
> not
> TypeLibraryUnregister(,,FilePath=C:\Program
> Server\80\Tools\Binn\SQLDMO.dll,LibID={10010001-E260-11CF-AE68-00AA004A34D5}
> not
> bijwerken
> RegAddValue(Name=PATH,Value=#%C:\PROGRA~1\MICROS~1 \OFFICE;%SYSTEMROOT%;%SYST
> Server\80\Tools\Binn\";C:\PROGRA~1\MICROS~5\80\TOO LS\BINN;%SYSTEMROOT%\syste
> van
> RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A
> RegAddValue(Name=TypesSupported,Value=#255,)
> RegRemoveValue(Name=EventMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~
> RegAddValue(Name=EventMessageFile,Value=C:\PROFEL~ 2\MSSQL$~1\Binn\RESOUR~1\1
> RegRemoveValue(Name=CategoryMessageFile,Value=C:\P ROFEL~2\MSSQL$~1\Binn\RESO
> RegAddValue(Name=CategoryMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~
> RegRemoveValue(Name=CategoryCount,Value=#8,)
> RegRemoveValue(Name=Language,Value=#1043,)
> RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A
> RegRemoveValue(Name=EventMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~
> RegRemoveValue(Name=CategoryMessageFile,Value=C:\P ROFEL~2\MSSQL$~1\Binn\RESO
> RegRemoveValue(Name=CategoryCount,Value=#8,)
>
>

MSDE install problem

Hi,

My computer OS is win2000 +sp3, I download the MSDE setup file(sql2kdesksp3.exe), I followed the instruction of the microsoft web site to install the msde, but during the windows configure the SQL server desktop engine, it hangs up there. I checked the setup log file, it has no error, it goes to sqlredis.exe, and stop there.

Can any one help me for this?

I really appreciated!

zgWhat is the command line you are using to install msde?

-Kashif

MSDE install common sense issues?

MSDE installs via a batch file using Microsoft's setup.
Once installed does it really make sense to uninstall it?
What if Visio is already installed before my install, or some other product
that uses MSDE, what happens to that install when my install runs?
Would I need the sa password of the prior install?
If I install my database into the default instance? And then someone
uninstalls the original app (prior to my install) that installed MSDE. Does
the installation uninstall MSDE even though my app uses it too?
Is it safer always to make my database run in its own instance?
Regards...
j
hi Jeff,
"Jeff" <joedirt@.datahook.com> ha scritto nel messaggio
news:%23nD5tx8XEHA.3520@.TK2MSFTNGP10.phx.gbl...
> MSDE installs via a batch file using Microsoft's setup.
> Once installed does it really make sense to uninstall it?
I don't understand this question... if you install an application, does it
make sense uninstalling it?...
if you need that MSDE instance, don't uninstall it..

> What if Visio is already installed before my install, or some other
product
> that uses MSDE, what happens to that install when my install runs?
I don't know if Visio install a separate MSDE instance (my Visio
installation did not) .. but you can install up to 16 different instances of
MSDE.. ok that number is quite prohibitive as regard resources, as you never
will have or desire 16 running instances of MSDE on the same box..
but if you have a "particular" instance you don't want to share with other
applications, than you can install a private instance for that app and using
a "common" instance for all other databases...

> Would I need the sa password of the prior install?
as long as that instance is up, you need it...

> If I install my database into the default instance? And then someone
> uninstalls the original app (prior to my install) that installed MSDE.
Does
> the installation uninstall MSDE even though my app uses it too?
this must be asked to the ISV providing that MSDE instance... as per MSDE
original EULA it shoul'd be that way, but now MSDE is free, and each
instance can be a shared one, as long as the ISV providing it does not
specify it's reserved for his/her app(s)

> Is it safer always to make my database run in its own instance?
it really depends... personally I do not, I only have separate instances for
test under different service pack levels, but on production servers I always
ask the end user before installing if he/se needs a separate named instance
when an existing MSDE/SQL Server instance is detected..
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 hosting

Hi all!

One good thing about access databases is the ability to upload the .mdb file to a hosting server and not being charged for database space.

How about MSDE? Does it require SQLServer hosting or can it be done just by uploading the database file?

Thanks,
Ricardo

MSDE is smaller version of SQL server. It is good for development but when you want upload web files and database you will need SQL server. There is a lot of hosting companies offering hosting plan with SQL support for less than $10/m