I can't install MSDE release A in Windows XP SP2. I verified if Server
Service is started and it is ok. I also verified if File and Printer sharing
is checked on network properties and it is ok. The windows firewall also is
disabled but the instalation doesn't work. I run the follow comand setup.exe
sapwd="suportebsb." /L*v C:/MSDELog.log.
Anyone can help me?
Regards,
Cicero Galdino
******** This is the lastest lines in log instalation files
*******************
2005-06-01 16:49:35.64 spid4 Default collation successfully changed.
2005-06-01 16:49:35.67 spid4 Recovery complete.
2005-06-01 16:49:35.67 spid4 SQL global counter collection task is
created.
2005-06-01 16:49:35.69 spid4 Warning: override, autoexec procedures
skipped.
2005-06-01 16:49:43.36 spid4 SQL Server is terminating due to 'stop'
request from Service Control Manager.
=== Logging stopped: 01/06/2005 16:59:54 ===
MSI (c) (18:48) [16:59:54:724]: Note: 1: 1708
MSI (c) (18:48) [16:59:54:724]: Product: Microsoft SQL Server Desktop Engine
-- Installation operation failed.
MSI (c) (18:48) [16:59:54:724]: Grabbed execution mutex.
MSI (c) (18:48) [16:59:54:724]: Cleaning up uninstalled install packages, if
any exist
MSI (c) (18:48) [16:59:54:740]: MainEngineThread is returning 1603
=== Verbose logging stopped: 01/06/2005 16:59:54 ===
hi Cicero,
Cicero wrote:
> I can't install MSDE release A in Windows XP SP2. I verified if Server
> Service is started and it is ok. I also verified if File and Printer
> sharing is checked on network properties and it is ok. The windows
> firewall also is disabled but the instalation doesn't work. I run the
> follow comand setup.exe sapwd="suportebsb." /L*v C:/MSDELog.log.
please inspect your C:/MSDELog.log for
RETURN VALUE 3
entrie(s), that reports exeptions duting the install process...
about 10/15 lines before each entry some (sometime cryptic) descritpion of
the problem will be available
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
Showing posts with label verified. Show all posts
Showing posts with label verified. Show all posts
Monday, March 26, 2012
Wednesday, March 7, 2012
msdb.dbo.sysdbmaintplan_history table question
Hi,
I am trying to check that a backup integrity check has verified a log
backup because it is being done over a network drive.
There is an entry verify backup for each backup performed in the
msdb.dbo.sysdbmaintplan_history table. Is the verify backup entry the
correct one I should be looking at to see if RESTORE VERIFYONLY
succeeded ?
My question is how do I tell that a verification found an error?
Thanks
--SamMaint plan executed RESTORE VERIFYONLY. It will produce errors of such are f
ound. Make sure you
handle the job so your are notified if errors occurs.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<wildturtle@.gmail.com> wrote in message news:1147179633.997410.37830@.j73g2000cwa.googlegroup
s.com...
> Hi,
> I am trying to check that a backup integrity check has verified a log
> backup because it is being done over a network drive.
> There is an entry verify backup for each backup performed in the
> msdb.dbo.sysdbmaintplan_history table. Is the verify backup entry the
> correct one I should be looking at to see if RESTORE VERIFYONLY
> succeeded ?
> My question is how do I tell that a verification found an error?
> Thanks
> --Sam
>|||Thanks for your reply. My problem is the following:
the msdb.dbo.sysdbmaintplan_histor=ADy has two records: "Backup
transaction log" and "Verify Backup". They both have fields
called succeeded, error, and message. my question is, if a RESTORE
VERIFYONLY were to detect corruption, how would that be reflected
in the sysdbmaintplan_histor=ADy table ?
Many Thanks
--Sam|||I don't know, I'm afraid. I'd guess that Maint plans are smart enough to mar
k the execution as
failed and log the errors returned by RESTORE VERIFYONLY. I don't use maint
plans myself, as I
prefer more control over these things. Perhaps you can try, for instance doi
ng the backup to the
"nul" file name?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<wildturtle@.gmail.com> wrote in message
news:1147180762.992024.182010@.u72g2000cwu.googlegroups.com...
Thanks for your reply. My problem is the following:
the msdb.dbo.sysdbmaintplan_histor_y has two records: "Backup
transaction log" and "Verify Backup". They both have fields
called succeeded, error, and message. my question is, if a RESTORE
VERIFYONLY were to detect corruption, how would that be reflected
in the sysdbmaintplan_histor_y table ?
Many Thanks
--Sam
I am trying to check that a backup integrity check has verified a log
backup because it is being done over a network drive.
There is an entry verify backup for each backup performed in the
msdb.dbo.sysdbmaintplan_history table. Is the verify backup entry the
correct one I should be looking at to see if RESTORE VERIFYONLY
succeeded ?
My question is how do I tell that a verification found an error?
Thanks
--SamMaint plan executed RESTORE VERIFYONLY. It will produce errors of such are f
ound. Make sure you
handle the job so your are notified if errors occurs.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<wildturtle@.gmail.com> wrote in message news:1147179633.997410.37830@.j73g2000cwa.googlegroup
s.com...
> Hi,
> I am trying to check that a backup integrity check has verified a log
> backup because it is being done over a network drive.
> There is an entry verify backup for each backup performed in the
> msdb.dbo.sysdbmaintplan_history table. Is the verify backup entry the
> correct one I should be looking at to see if RESTORE VERIFYONLY
> succeeded ?
> My question is how do I tell that a verification found an error?
> Thanks
> --Sam
>|||Thanks for your reply. My problem is the following:
the msdb.dbo.sysdbmaintplan_histor=ADy has two records: "Backup
transaction log" and "Verify Backup". They both have fields
called succeeded, error, and message. my question is, if a RESTORE
VERIFYONLY were to detect corruption, how would that be reflected
in the sysdbmaintplan_histor=ADy table ?
Many Thanks
--Sam|||I don't know, I'm afraid. I'd guess that Maint plans are smart enough to mar
k the execution as
failed and log the errors returned by RESTORE VERIFYONLY. I don't use maint
plans myself, as I
prefer more control over these things. Perhaps you can try, for instance doi
ng the backup to the
"nul" file name?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<wildturtle@.gmail.com> wrote in message
news:1147180762.992024.182010@.u72g2000cwu.googlegroups.com...
Thanks for your reply. My problem is the following:
the msdb.dbo.sysdbmaintplan_histor_y has two records: "Backup
transaction log" and "Verify Backup". They both have fields
called succeeded, error, and message. my question is, if a RESTORE
VERIFYONLY were to detect corruption, how would that be reflected
in the sysdbmaintplan_histor_y table ?
Many Thanks
--Sam
msdb.dbo.sysdbmaintplan_history table question
Hi,
I am trying to check that a backup integrity check has verified a log
backup because it is being done over a network drive.
There is an entry verify backup for each backup performed in the
msdb.dbo.sysdbmaintplan_history table. Is the verify backup entry the
correct one I should be looking at to see if RESTORE VERIFYONLY
succeeded ?
My question is how do I tell that a verification found an error?
Thanks
--SamMaint plan executed RESTORE VERIFYONLY. It will produce errors of such are found. Make sure you
handle the job so your are notified if errors occurs.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<wildturtle@.gmail.com> wrote in message news:1147179633.997410.37830@.j73g2000cwa.googlegroups.com...
> Hi,
> I am trying to check that a backup integrity check has verified a log
> backup because it is being done over a network drive.
> There is an entry verify backup for each backup performed in the
> msdb.dbo.sysdbmaintplan_history table. Is the verify backup entry the
> correct one I should be looking at to see if RESTORE VERIFYONLY
> succeeded ?
> My question is how do I tell that a verification found an error?
> Thanks
> --Sam
>|||Thanks for your reply. My problem is the following:
the msdb.dbo.sysdbmaintplan_histor=ADy has two records: "Backup
transaction log" and "Verify Backup". They both have fields
called succeeded, error, and message. my question is, if a RESTORE
VERIFYONLY were to detect corruption, how would that be reflected
in the sysdbmaintplan_histor=ADy table ?
Many Thanks
--Sam|||I don't know, I'm afraid. I'd guess that Maint plans are smart enough to mark the execution as
failed and log the errors returned by RESTORE VERIFYONLY. I don't use maint plans myself, as I
prefer more control over these things. Perhaps you can try, for instance doing the backup to the
"nul" file name?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<wildturtle@.gmail.com> wrote in message
news:1147180762.992024.182010@.u72g2000cwu.googlegroups.com...
Thanks for your reply. My problem is the following:
the msdb.dbo.sysdbmaintplan_history has two records: "Backup
transaction log" and "Verify Backup". They both have fields
called succeeded, error, and message. my question is, if a RESTORE
VERIFYONLY were to detect corruption, how would that be reflected
in the sysdbmaintplan_history table ?
Many Thanks
--Sam
I am trying to check that a backup integrity check has verified a log
backup because it is being done over a network drive.
There is an entry verify backup for each backup performed in the
msdb.dbo.sysdbmaintplan_history table. Is the verify backup entry the
correct one I should be looking at to see if RESTORE VERIFYONLY
succeeded ?
My question is how do I tell that a verification found an error?
Thanks
--SamMaint plan executed RESTORE VERIFYONLY. It will produce errors of such are found. Make sure you
handle the job so your are notified if errors occurs.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<wildturtle@.gmail.com> wrote in message news:1147179633.997410.37830@.j73g2000cwa.googlegroups.com...
> Hi,
> I am trying to check that a backup integrity check has verified a log
> backup because it is being done over a network drive.
> There is an entry verify backup for each backup performed in the
> msdb.dbo.sysdbmaintplan_history table. Is the verify backup entry the
> correct one I should be looking at to see if RESTORE VERIFYONLY
> succeeded ?
> My question is how do I tell that a verification found an error?
> Thanks
> --Sam
>|||Thanks for your reply. My problem is the following:
the msdb.dbo.sysdbmaintplan_histor=ADy has two records: "Backup
transaction log" and "Verify Backup". They both have fields
called succeeded, error, and message. my question is, if a RESTORE
VERIFYONLY were to detect corruption, how would that be reflected
in the sysdbmaintplan_histor=ADy table ?
Many Thanks
--Sam|||I don't know, I'm afraid. I'd guess that Maint plans are smart enough to mark the execution as
failed and log the errors returned by RESTORE VERIFYONLY. I don't use maint plans myself, as I
prefer more control over these things. Perhaps you can try, for instance doing the backup to the
"nul" file name?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<wildturtle@.gmail.com> wrote in message
news:1147180762.992024.182010@.u72g2000cwu.googlegroups.com...
Thanks for your reply. My problem is the following:
the msdb.dbo.sysdbmaintplan_history has two records: "Backup
transaction log" and "Verify Backup". They both have fields
called succeeded, error, and message. my question is, if a RESTORE
VERIFYONLY were to detect corruption, how would that be reflected
in the sysdbmaintplan_history table ?
Many Thanks
--Sam
Subscribe to:
Posts (Atom)