MSDE stopps with code 1603

Hi!
When I tried to install MDSE on W2003 Server it stopped with error code
1603. I want to Install NAI ProtectionPilot 1.1 an Veritas Backup Exec 9.1
whic use that as well.
KB article dont match to my problem...
Thanks for helping
Marcel
hi Marcel,
Marcel Ksling wrote:
> Hi!
> When I tried to install MDSE on W2003 Server it stopped with error
> code 1603. I want to Install NAI ProtectionPilot 1.1 an Veritas
> Backup Exec 9.1 whic use that as well.
> KB article dont match to my problem...
> Thanks for helping
> Marcel
please have a look at http://tinyurl.com/apb8e to see if helps...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hello,
I have seen the exact same problem on both Windows XP PRO and a Windows 2003
Server.
MSDE2000 Release A will not always install again after it has been
un-installed. I have never seen this problem on my own development machine,
only on customers machines installing our product!
So my guess is that on my machine where ex. Visual Studio .NET is installed
something is eliminating the problem... but NOT on a standard Windows XP PRO
or Windoes 2003 Server!
My question: Is there a solution to the problem or not ?
I can see a lot of people have had the same problem...
Best regards
Per Clausen
"Andrea Montanari" wrote:

> hi Marcel,
> Marcel K?sling wrote:
> please have a look at http://tinyurl.com/apb8e to see if helps...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||hi,
Per Clausen wrote:
> Hello,
> I have seen the exact same problem on both Windows XP PRO and a
> Windows 2003 Server.
which both now have MDAC 2.8 sp 2 ...

> MSDE2000 Release A will not always install again after it has been
> un-installed. I have never seen this problem on my own development
> machine, only on customers machines installing our product!
uninstalling MSDE (often) does non properly clear MSDE related file system
and registry entries, and this often confuses users... a proper (and manual)
clean up is required, as indicated in
http://support.microsoft.com/default...b;en-us;320873
http://support.microsoft.com/default...;EN-US;Q290991

> So my guess is that on my machine where ex. Visual Studio .NET is
> installed something is eliminating the problem... but NOT on a
> standard Windows XP PRO or Windoes 2003 Server!
> My question: Is there a solution to the problem or not ?
> I can see a lot of people have had the same problem...
none that I'm aware of... but, for what is worth, I never had this kind of
problems on Win2k, XP (rtm/sp1/sp2) and Win2003 (rtm/sp1)

Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.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,
Thank you for your reply. I guess we have to make a custom application to
fix the problem. It's just not easy when I can't reproduce the problem on my
own machine.
Best regards
Per Clausen
"Andrea Montanari" wrote:

> hi,
> Per Clausen wrote:
> which both now have MDAC 2.8 sp 2 ...
>
> uninstalling MSDE (often) does non properly clear MSDE related file system
> and registry entries, and this often confuses users... a proper (and manual)
> clean up is required, as indicated in
> http://support.microsoft.com/default...b;en-us;320873
> http://support.microsoft.com/default...;EN-US;Q290991
>
> none that I'm aware of... but, for what is worth, I never had this kind of
> problems on Win2k, XP (rtm/sp1/sp2) and Win2003 (rtm/sp1)
>
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||Hi,
For your information:
I have found a way to reproduce the MSDE re-installation problem.
If the value InstanceComponentSet.1 exist in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Component Set MSDE
will NOT install.
To make the MSDE install simply delete InstanceComponentSet.1 and everything
seems to work fine again.
Best regards
Per Clausen
CIM Electronics A/S
"Andrea Montanari" wrote:

> hi,
> Per Clausen wrote:
> which both now have MDAC 2.8 sp 2 ...
>
> uninstalling MSDE (often) does non properly clear MSDE related file system
> and registry entries, and this often confuses users... a proper (and manual)
> clean up is required, as indicated in
> http://support.microsoft.com/default...b;en-us;320873
> http://support.microsoft.com/default...;EN-US;Q290991
>
> none that I'm aware of... but, for what is worth, I never had this kind of
> problems on Win2k, XP (rtm/sp1/sp2) and Win2003 (rtm/sp1)
>
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||hi,
Per Clausen wrote:
> Hi,
> For your information:
> I have found a way to reproduce the MSDE re-installation problem.
> If the value InstanceComponentSet.1 exist in
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Component
> Set MSDE will NOT install.
> To make the MSDE install simply delete InstanceComponentSet.1 and
> everything seems to work fine again.
>
it's documented...
http://support.microsoft.com/default...b;en-us;320873
point 3..
3. If the following registry key points to the MSDE 2000 instance
ProductCode, remove the value InstanceComponentSet.x. For example,
InstanceComponentSet.1 has a value that matches the ProductCode of
Sqlrun01.msi:
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
sql

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 regualr maintenance - help

Hi folks
New to MSDE...
1. What is the best options to use when doing backups?
option 1. OSQL -U sa -P password -S server -Q "BACKUP DATABASE db1 TO DISK
= 'c:\Backups\backup1.bck'"
option 2. OSQL -U sa -P password -S server -Q "BACKUP DATABASE db1 TO DISK =
'C:\backups\backup1.bck' WITH FORMAT, STATS"
2. Should I also be doing a reindex? I would like to do a batch sql job (
like above backup)
USE DB1
GO
sp_msforeachtable @.command1 = 'DBCC DBREINDEX ([?])'
3. Should I do a Database check if yes, before or after backup...
dbcc checkdb ('database')
4. Would also like to get information DB size - just to mkae sure its stay's
under the 2GB limit.
Someone recommend the followinf - but not sure what they all do...
Save the following commands to a file named "WhatsUpMaint.bat":
osql -E -D WhatsUp -Q "DBCC SHRINKDATABASE (WhatsUp)"
osql -E -D WhatsUp -Q "EXEC sp_MsForEachTable 'DBCC DBREINDEX (''?'', '''',
0)'"
osql -E -D WhatsUp -Q "EXEC sp_createstats"
osql -E -D WhatsUp -Q "EXEC sp_updatestats"
osql -E -D WhatsUp -Q "EXEC sp_MsForEachTable 'sp_recompile ''?'''"
osql -E -D WhatsUp -Q "DBCC UPDATEUSAGE ('WhatsUp')"
osql -E -D WhatsUp -Q "EXEC sp_cycle_errorlog"
hi Danny,
Danny wrote:
> 1. What is the best options to use when doing backups?
> option 1. OSQL -U sa -P password -S server -Q "BACKUP DATABASE db1
> TO DISK = 'c:\Backups\backup1.bck'"
> option 2. OSQL -U sa -P password -S server -Q "BACKUP DATABASE db1 TO
> DISK = 'C:\backups\backup1.bck' WITH FORMAT, STATS"
the "bad thing" of this batch is that it includes sa's password in clear
text... please do not code a cmd/bat file this way :D
create a "backup" login with appropriate permissions and hardcode it's
credentials, not "sa" ones :D
WITH FORMAT specifies a new media set will be created.. so this depends on
your actual requirements.. if you want to "append" your current backup to
existing ones, do not specify it, else, do it..
STATS, on the other hand, specify to output backup percentage to the
standard output..
if not specified you usually have an output like
BACKUP DATABASE pubs TO DISK = 'c:\pus.bak';
--<--
Processed 248 pages for database 'pubs', file 'pubs' on file 4.
Processed 1 pages for database 'pubs', file 'pubs_log' on file 4.
BACKUP DATABASE successfully processed 249 pages in 0.073 seconds (27.942
MB/sec).
where
BACKUP DATABASE pubs TO DISK = 'c:\pus.bak'
WITH STATS;
--<--
12 percent processed.
22 percent processed.
32 percent processed.
41 percent processed.
51 percent processed.
61 percent processed.
70 percent processed.
80 percent processed.
93 percent processed.
Processed 248 pages for database 'pubs', file 'pubs' on file 5.
100 percent processed.
Processed 1 pages for database 'pubs', file 'pubs_log' on file 5.
BACKUP DATABASE successfully processed 249 pages in 0.069 seconds (29.562
MB/sec).
if you do not specify a percent value, SQL Server uses a default of 10%..

> 2. Should I also be doing a reindex? I would like to do a batch sql
> job ( like above backup)
> USE DB1
> GO
> sp_msforeachtable @.command1 = 'DBCC DBREINDEX ([?])'
this statement uses an undocumented stored procedure, sp_msforeachtable, to
rebuild all indexes of each table object.. this obviously imply
"rebuilding" the whole table with clustered index.. so this implies both
time and file related implications... have a look at
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx
for futher info, but, to our interest, reindexing is usually a "good thing"
to do :D

> 3. Should I do a Database check if yes, before or after backup...
> dbcc checkdb ('database')
you can go pre-backup

> 4. Would also like to get information DB size - just to mkae sure its
> stay's under the 2GB limit.
sorry, did not understand your requirement...

> Save the following commands to a file named "WhatsUpMaint.bat":
> osql -E -D WhatsUp -Q "DBCC SHRINKDATABASE (WhatsUp)"
about shrinking a database you can have a look at Tibor Karaszi's (SQL
Server MVP) article at http://www.karaszi.com/SQLServer/info_dont_shrink.asp
about the trusted connection you use here... -E indicates to connect as the
current logged in account.. and, as the statements you are executing require
high permissions in the instance context, this means the current interactive
Windows account is quite an admin... as this sounds to be a scheduled batch,
I'd opt for other credentials in order not to require to log in as such a
super man :D

> osql -E -D WhatsUp -Q "EXEC sp_MsForEachTable 'DBCC DBREINDEX (''?'',
> '''', 0)'"
> osql -E -D WhatsUp -Q "EXEC sp_createstats"
to my head this is not required as you usually set this at database level so
that statistics always are created and updated..

> osql -E -D WhatsUp -Q "EXEC sp_updatestats"
but this can be maintained as statistics are "rebuilt" when a certain
treshhold of changes is reached, so you can force it..

> osql -E -D WhatsUp -Q "EXEC sp_MsForEachTable 'sp_recompile ''?'''"
not correct.. this one is available for stored procedures only and not for
base tables...
causing the procedures to be recompiled at next execution time will
obviously imply penalties in their execution... I do usually not perform
that one..

> osql -E -D WhatsUp -Q "DBCC UPDATEUSAGE ('WhatsUp')"
this one re-syncs catalog's stats.. I do usually not do that if not
required.. but it does not hurt..

> osql -E -D WhatsUp -Q "EXEC sp_cycle_errorlog"
this one changes the current log to a new created one... I really do not do
that if not required in order to have a troubleshoot log to archive so some
reason.. but it does not imply penaltie/problems at all..
at the end of the game, I'd suggest to "log" the results of your
maintenances outputting them to a text file you can later inspect, send by
mail or whatever..
just add the
>filePathAndName.txt
parameter to your 1st oSql call to initilize your file and add[vbcol=seagreen]
parameter to the other ones, causing the results to be appended to that
file...
regards
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply

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 installation fails due to detection of previous installation

Please help,

I am trying to install MSDE 2000 so that Backup exec will run on this
server. I have gotten so far as to find an entry in my SQLSTP.TXT file
that says that c:\mssql7 was detected so the install fails.

Now, to start with there is no directory called C:\mssql7 on this
server. I have gone through all MS articles on manual removal of SQL
server and instances. I have searched the registry for mssql7 and
removed any keys that matched, as per MS article I have searched on
SQLBOOT.dll and it is not present anywhere on my system and I still get
the same results.

2:07:44 Begin Action: Detection
12:07:44 SQL Server version already installed: 7.00.623
12:07:44 Previous Install SQL Path: C:\MSSQL7
12:07:44 Previous Install SQL Data Path: C:\MSSQL7
12:07:44 End Action Detection
12:07:44 Begin Action: ODBCLocked
12:07:44 End Action ODBCLocked
12:07:44 GetDefinition returned: 1
12:07:44 Previous SQL Server ProductType: MSDE [0x4]
12:07:44 This combination of Package and Operating System allows a full
product install.

can anyone think of anything here..

what else could be causing the server to think there is a previous
version of SQL 7 on this box!!!?Hi

Have you looked at the services running using NET START?

You may want to try a registry cleaning tool.

I assume you have seen
http://support.microsoft.com/defaul...kb;en-us;276044
This may help http://support.microsoft.com/defaul...kb;en-us;320873

Have you tried specifying and instance name for the installation?

John

<jdisco@.gmail.com> wrote in message
news:1112988946.699106.224300@.o13g2000cwo.googlegr oups.com...
> Please help,
> I am trying to install MSDE 2000 so that Backup exec will run on this
> server. I have gotten so far as to find an entry in my SQLSTP.TXT file
> that says that c:\mssql7 was detected so the install fails.
> Now, to start with there is no directory called C:\mssql7 on this
> server. I have gone through all MS articles on manual removal of SQL
> server and instances. I have searched the registry for mssql7 and
> removed any keys that matched, as per MS article I have searched on
> SQLBOOT.dll and it is not present anywhere on my system and I still get
> the same results.
>
> 2:07:44 Begin Action: Detection
> 12:07:44 SQL Server version already installed: 7.00.623
> 12:07:44 Previous Install SQL Path: C:\MSSQL7
> 12:07:44 Previous Install SQL Data Path: C:\MSSQL7
> 12:07:44 End Action Detection
> 12:07:44 Begin Action: ODBCLocked
> 12:07:44 End Action ODBCLocked
> 12:07:44 GetDefinition returned: 1
> 12:07:44 Previous SQL Server ProductType: MSDE [0x4]
> 12:07:44 This combination of Package and Operating System allows a full
> product install.
>
> can anyone think of anything here..
> what else could be causing the server to think there is a previous
> version of SQL 7 on this box!!!?

MSDE Event ID 208/17055 (Newbie)

Hello,
We get these events logged every night, apparently when
the SQLAGENT tries to do it's backup. I'm afraid I
didn't configure MSDE on this particular server, and I
don't have any Enterprise Mgr functions on the desktop,
so I'm slightly at a loss as to how to go about resolving
this issue, being that I'm a noob when it comes to SQL.
Any advise, help or pointers would be great.
A pint goes to the first correct answer!
Andy Griggs.
Hello,
If you have another computer with Entreprise manager, you can donnect to the
msde by the network..
Marc Allard
"Andy Griggs" <andrew.griggs@.agile-it.net> a crit dans le message de
news:20dd701c459ec$940620c0$a101280a@.phx.gbl...
> Hello,
> We get these events logged every night, apparently when
> the SQLAGENT tries to do it's backup. I'm afraid I
> didn't configure MSDE on this particular server, and I
> don't have any Enterprise Mgr functions on the desktop,
> so I'm slightly at a loss as to how to go about resolving
> this issue, being that I'm a noob when it comes to SQL.
> Any advise, help or pointers would be great.
> A pint goes to the first correct answer!
> Andy Griggs.