MSDE and Enterprise Manager?

I am a complete sql newbie! For the life of me I can't figure out how to get Enterprise Manager to connect with MSDE. Something about mixed mode or tcp/ip settings? But no one's ever really clear on how to do these things. I've uninstalled MSDE until I can get more info.

I just need a quick walk-through on how to install msde to work with EM. This is what I used when MSDE requested a strong password:

setup INSTANCENAME="InstanceName" SECURITYMODE=SQL SAPWD="AStrongSAPwd"

Is this correct? Any help would be appreciated.

Thanks.

You access it by address or servername + \ + Instance name:

Server\MSDEInstanceName

|||

What part are you having a problem with?

Tell EM to connect to the server\instancename using sql authentication login sa, password AStrongPWD.

|||If you have the full SQL Server installed then you install the MSDE as a named instance and right click at the top of the Enterprise manager of the full version to register the MSDE and you can manage it directly. If you have the MSDE installed then you install the full version as a named instance and repeat the above. I have registered 68 SQL Server 7/2000 in one XP box so if you have more questions post again. Hope this helps.|||

Thanks to everyone for their help.

I had the eval version of 2000 installed but it's expired. I would now like to use EM with MSDE to connect to the database on my website. I re-installed MSDE but it's only showing the local database.

When I try to register my online domain (ip address) it fails. Says sql may not be running. But it is running. I know it's something basic and silly I'm not doing, but I'm still very new to sql. Is there any other very basic step I may be missing?

Again, thanks for everyone's help...sorry for all the newbie questions.

|||

Which is probably correct because your SQL Server service maybe off, the developer edition is $40 in the link below but you could get it for less because when you are using hosting company you need Enterprise manager. Hope this helps.

http://www.provantage.com/buy-22053391-microsoft-backoffice-sql-server-2000-developer-edition-shopping.htm

MSDE 2000 SP3a Won't install on 2003 server

I hope someone has seen this... I have a 2003 server that refuses to install MSDE 2000 SP3a. The install goes to 99% complete, then rolls back and automatically uninstalls. I have seen this in the past when file and printer sharing is not installed or
insufficient permissions, but this time it has me stumped. Event viewer is useless, it just reports that the install failed and doesn't give any reason. No error logs get created, no errors come up, the install just won't take. I have sucessfully insta
lled MSDE 2000 on other 2003 servers and have never had this much trouble. I have a verbose install log available from the install if anyone wants to look at it. Any ideas?
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
hi,
<dnoble@.-NOSPAM-raymorgan.com> ha scritto nel messaggio
news:%23fZGykYpEHA.648@.tk2msftngp13.phx.gbl
> I hope someone has seen this... I have a 2003 server that refuses to
> install MSDE 2000 SP3a. The install goes to 99% complete, then rolls
> back and automatically uninstalls. I have seen this in the past when
> file and printer sharing is not installed or insufficient
> permissions, but this time it has me stumped. Event viewer is
> useless, it just reports that the install failed and doesn't give any
> reason. No error logs get created, no errors come up, the install
> just won't take. I have sucessfully installed MSDE 2000 on other
> 2003 servers and have never had this much trouble. I have a verbose
> install log available from the install if anyone wants to look at it.
> Any ideas?
search for
RETURN VALUE 3
in your install log... it usually reports where the problem is
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
|||Thanks for the reply... I did locate a spot with Return Value 3. From the
log file:
Starting custom action InstallSQLAgentSecurity
InstallSQLAgentSecurity failed (FOX,LocalSystem,87).
Action ended 10:04:07: InstallFinalize. Return value 3.
Any thoughts on this?
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2rtpgpF1f5farU1@.uni-berlin.de...
> hi,
> <dnoble@.-NOSPAM-raymorgan.com> ha scritto nel messaggio
> news:%23fZGykYpEHA.648@.tk2msftngp13.phx.gbl
> search for
> RETURN VALUE 3
> in your install log... it usually reports where the problem is
> --
> 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
>
|||"News" <david-noble@.sbcglobal.net> ha scritto nel messaggio
news:TDk6d.3964$nj.741@.newssvr13.news.prodigy.com
> Thanks for the reply... I did locate a spot with Return Value 3.
> From the log file:
> Starting custom action InstallSQLAgentSecurity
> InstallSQLAgentSecurity failed (FOX,LocalSystem,87).
> Action ended 10:04:07: InstallFinalize. Return value 3.
> Any thoughts on this?
please have a look at http://tinyurl.com/69vo6 if can help solving your
problem
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
|||If you setup is failing, specify a command line parameter DISABLEROLLBACK =
1, this would stop MSDE Installer from rolling back in case of failure.
Also specify /L*v <log file patch with name>. This would enable setup to
write logs into the specified file. Try to search "return value 3" and
check where did it fail.
Once we know where it is failing we can help better. Also add the logfile
when you reply .
|||Thanks for all the replys, but so far all are off base a bit... The server
service is already running and file sharing is installed. A log file was
created and return value 3 came up with the following:
Starting custom action InstallSQLAgentSecurity
InstallSQLAgentSecurity failed (FOX,LocalSystem,87).
Action ended 10:04:07: InstallFinalize. Return value 3.
All responses to this so far have referred me to articles that talk about
making sure the server service is running, which is already the case.
<dnoble@.-NOSPAM-raymorgan.com> wrote in message
news:%23fZGykYpEHA.648@.tk2msftngp13.phx.gbl...
> I hope someone has seen this... I have a 2003 server that refuses to
install MSDE 2000 SP3a. The install goes to 99% complete, then rolls back
and automatically uninstalls. I have seen this in the past when file and
printer sharing is not installed or insufficient permissions, but this time
it has me stumped. Event viewer is useless, it just reports that the
install failed and doesn't give any reason. No error logs get created, no
errors come up, the install just won't take. I have sucessfully installed
MSDE 2000 on other 2003 servers and have never had this much trouble. I
have a verbose install log available from the install if anyone wants to
look at it. Any ideas?
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine
supports Post Alerts, Ratings, and Searching.

msdb refuses to back up w/ plan

All,
I've created (and re-created) a Mx plan for the system databases.
Part of it is a complete backup. All the default options in the
wizard were chosen, including the option to verify.
Master and Model back up fine. MSDB, however, fails. According to
the Mx Plan log, the backup completes successfully, but the verify
fails as follows:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201:
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open backu
p
device 'd:\sql_data\MSSQL\BACKUP\msdb_db_200407
042207.BAK'. Device
error or device off-line. See the SQL Server error log for more
details.
[Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY DATABASE i
s
terminating abnormally.
1- It doesn't appear that the backup actually succeeded, as there is
no msdb_db_200407042207.bak file in the directory.
2- There is no additional information in the SQL Server error log
3- I can successfully back up msdb -manually- without a hiccup.
I've tried:
1- Recreating a new Mx Plan from scratch (no effect)
2- Can full index/optimizations on msdb (no errors found)
3- Tried shrinking the database (it's 215MBish) to make it faster
4- Tried a full backup/restore of msdb in case it had any mystery
corruption (no effect)
Oh yes, SQL Server standard 2000 sp3 on W2.3K standard. NTFS
partition. SQL Agent using a domain account, SQL Server running under
the same account.
Can anyone shed light on this? I can come up with no reason why the
Mx plan would fail for just this one database, when I can back it up
just fine manually.
GeofHere's some more info:
I did find some additional information in the app event log, giving the spec
ific T-SQL that was failing:
BACKUP DATABASE [msdb] TO DISK = N'd:\sql_data\MSSQL\BACKUP\msdb_db_200
407042238.BAK' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
After some pondering and re-reading my own post, I went ahead and logged int
o the server interactively using SQL Server's account. I attempted to execu
te the above SQL and lo and behond, it failed (General Network Error). When
executed under my normal U
serID, it executed fine.
Trial and error then produced the rather odd discovery that the problem part
of the statement is the seemingly innocuous "STATS=10" command. If the sam
e statement is run under the SQL Server account EXCEPT for removing the stat
s=10 command, it works fine|||Go the Maintenance Plan and right click and view maintenance history out
there ...Thats where most of the reasoning is for the failure..
"Geof" <Geof@.discussions.microsoft.com> wrote in message
news:C6436F94-BF81-41FD-9869-5595F7FBA6B4@.microsoft.com...
> Here's some more info:
> I did find some additional information in the app event log, giving the
specific T-SQL that was failing:
> BACKUP DATABASE [msdb] TO DISK =
N'd:\sql_data\MSSQL\BACKUP\msdb_db_20040
7042238.BAK' WITH INIT , NOUNLOAD
, NOSKIP , STATS = 10, NOFORMAT
> After some pondering and re-reading my own post, I went ahead and logged
into the server interactively using SQL Server's account. I attempted to
execute the above SQL and lo and behond, it failed (General Network Error).
When executed under my normal UserID, it executed fine.
> Trial and error then produced the rather odd discovery that the problem
part of the statement is the seemingly innocuous "STATS=10" command. If the
same statement is run under the SQL Server account EXCEPT for removing the
stats=10 command, it works fine.
> While I've gotten more information on exactly what is causing the problem,
I:
> 1- Have no idea why the problem is occurring, and
> 2- Don't know a way around it (other than backup w/o using a Mx Plan)
> My nearest stab would be that this particular T-SQL (and STATS option in
particular) is causing some sort of collision between SQL Server and SQL
Server Agent since they would both be running under the same account. (But
surely I'm not the only one in the history of SQL Server to have created a
sysdb mx plan w/ both SQL and SQL Agent running under an identical domain
account, huh')
> Ideas'|||In my first post I listed what was in the Mx Plan History. Does
anyone have any other ideas?
Geof
"Hassan" <fatima_ja@.hotmail.com> wrote in message news:<#GDGyveYEHA.996@.TK2MSFTNGP12.phx.gbl
>...
> Go the Maintenance Plan and right click and view maintenance history out
> there ...Thats where most of the reasoning is for the failure..

msdb refuses to back up w/ plan

All,
I've created (and re-created) a Mx plan for the system databases.
Part of it is a complete backup. All the default options in the
wizard were chosen, including the option to verify.
Master and Model back up fine. MSDB, however, fails. According to
the Mx Plan log, the backup completes successfully, but the verify
fails as follows:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201:
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open backup
device 'd:\sql_data\MSSQL\BACKUP\msdb_db_200407042207.BAK '. Device
error or device off-line. See the SQL Server error log for more
details.
[Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY DATABASE is
terminating abnormally.
1- It doesn't appear that the backup actually succeeded, as there is
no msdb_db_200407042207.bak file in the directory.
2- There is no additional information in the SQL Server error log
3- I can successfully back up msdb -manually- without a hiccup.
I've tried:
1- Recreating a new Mx Plan from scratch (no effect)
2- Can full index/optimizations on msdb (no errors found)
3- Tried shrinking the database (it's 215MBish) to make it faster
4- Tried a full backup/restore of msdb in case it had any mystery
corruption (no effect)
Oh yes, SQL Server standard 2000 sp3 on W2.3K standard. NTFS
partition. SQL Agent using a domain account, SQL Server running under
the same account.
Can anyone shed light on this? I can come up with no reason why the
Mx plan would fail for just this one database, when I can back it up
just fine manually.
Geof
Here's some more info:
I did find some additional information in the app event log, giving the specific T-SQL that was failing:
BACKUP DATABASE [msdb] TO DISK = N'd:\sql_data\MSSQL\BACKUP\msdb_db_200407042238.BA K' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
After some pondering and re-reading my own post, I went ahead and logged into the server interactively using SQL Server's account. I attempted to execute the above SQL and lo and behond, it failed (General Network Error). When executed under my normal U
serID, it executed fine.
Trial and error then produced the rather odd discovery that the problem part of the statement is the seemingly innocuous "STATS=10" command. If the same statement is run under the SQL Server account EXCEPT for removing the stats=10 command, it works fine
|||Go the Maintenance Plan and right click and view maintenance history out
there ...Thats where most of the reasoning is for the failure..
"Geof" <Geof@.discussions.microsoft.com> wrote in message
news:C6436F94-BF81-41FD-9869-5595F7FBA6B4@.microsoft.com...
> Here's some more info:
> I did find some additional information in the app event log, giving the
specific T-SQL that was failing:
> BACKUP DATABASE [msdb] TO DISK =
N'd:\sql_data\MSSQL\BACKUP\msdb_db_200407042238.BA K' WITH INIT , NOUNLOAD
, NOSKIP , STATS = 10, NOFORMAT
> After some pondering and re-reading my own post, I went ahead and logged
into the server interactively using SQL Server's account. I attempted to
execute the above SQL and lo and behond, it failed (General Network Error).
When executed under my normal UserID, it executed fine.
> Trial and error then produced the rather odd discovery that the problem
part of the statement is the seemingly innocuous "STATS=10" command. If the
same statement is run under the SQL Server account EXCEPT for removing the
stats=10 command, it works fine.
> While I've gotten more information on exactly what is causing the problem,
I:
> 1- Have no idea why the problem is occurring, and
> 2- Don't know a way around it (other than backup w/o using a Mx Plan)
> My nearest stab would be that this particular T-SQL (and STATS option in
particular) is causing some sort of collision between SQL Server and SQL
Server Agent since they would both be running under the same account. (But
surely I'm not the only one in the history of SQL Server to have created a
sysdb mx plan w/ both SQL and SQL Agent running under an identical domain
account, huh?)
> Ideas?
|||In my first post I listed what was in the Mx Plan History. Does
anyone have any other ideas?
Geof
"Hassan" <fatima_ja@.hotmail.com> wrote in message news:<#GDGyveYEHA.996@.TK2MSFTNGP12.phx.gbl>...
> Go the Maintenance Plan and right click and view maintenance history out
> there ...Thats where most of the reasoning is for the failure..

msdb refuses to back up w/ plan

All,
I've created (and re-created) a Mx plan for the system databases.
Part of it is a complete backup. All the default options in the
wizard were chosen, including the option to verify.
Master and Model back up fine. MSDB, however, fails. According to
the Mx Plan log, the backup completes successfully, but the verify
fails as follows:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201:
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open backup
device 'd:\sql_data\MSSQL\BACKUP\msdb_db_200407042207.BAK'. Device
error or device off-line. See the SQL Server error log for more
details.
[Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY DATABASE is
terminating abnormally.
1- It doesn't appear that the backup actually succeeded, as there is
no msdb_db_200407042207.bak file in the directory.
2- There is no additional information in the SQL Server error log
3- I can successfully back up msdb -manually- without a hiccup.
I've tried:
1- Recreating a new Mx Plan from scratch (no effect)
2- Can full index/optimizations on msdb (no errors found)
3- Tried shrinking the database (it's 215MBish) to make it faster
4- Tried a full backup/restore of msdb in case it had any mystery
corruption (no effect)
Oh yes, SQL Server standard 2000 sp3 on W2.3K standard. NTFS
partition. SQL Agent using a domain account, SQL Server running under
the same account.
Can anyone shed light on this? I can come up with no reason why the
Mx plan would fail for just this one database, when I can back it up
just fine manually.
GeofHere's some more info:
I did find some additional information in the app event log, giving the specific T-SQL that was failing:
BACKUP DATABASE [msdb] TO DISK = N'd:\sql_data\MSSQL\BACKUP\msdb_db_200407042238.BAK' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
After some pondering and re-reading my own post, I went ahead and logged into the server interactively using SQL Server's account. I attempted to execute the above SQL and lo and behond, it failed (General Network Error). When executed under my normal UserID, it executed fine.
Trial and error then produced the rather odd discovery that the problem part of the statement is the seemingly innocuous "STATS=10" command. If the same statement is run under the SQL Server account EXCEPT for removing the stats=10 command, it works fine.
While I've gotten more information on exactly what is causing the problem, I:
1- Have no idea why the problem is occurring, and
2- Don't know a way around it (other than backup w/o using a Mx Plan)
My nearest stab would be that this particular T-SQL (and STATS option in particular) is causing some sort of collision between SQL Server and SQL Server Agent since they would both be running under the same account. (But surely I'm not the only one in the history of SQL Server to have created a sysdb mx plan w/ both SQL and SQL Agent running under an identical domain account, huh')
Ideas'|||Go the Maintenance Plan and right click and view maintenance history out
there ...Thats where most of the reasoning is for the failure..
"Geof" <Geof@.discussions.microsoft.com> wrote in message
news:C6436F94-BF81-41FD-9869-5595F7FBA6B4@.microsoft.com...
> Here's some more info:
> I did find some additional information in the app event log, giving the
specific T-SQL that was failing:
> BACKUP DATABASE [msdb] TO DISK =N'd:\sql_data\MSSQL\BACKUP\msdb_db_200407042238.BAK' WITH INIT , NOUNLOAD
, NOSKIP , STATS = 10, NOFORMAT
> After some pondering and re-reading my own post, I went ahead and logged
into the server interactively using SQL Server's account. I attempted to
execute the above SQL and lo and behond, it failed (General Network Error).
When executed under my normal UserID, it executed fine.
> Trial and error then produced the rather odd discovery that the problem
part of the statement is the seemingly innocuous "STATS=10" command. If the
same statement is run under the SQL Server account EXCEPT for removing the
stats=10 command, it works fine.
> While I've gotten more information on exactly what is causing the problem,
I:
> 1- Have no idea why the problem is occurring, and
> 2- Don't know a way around it (other than backup w/o using a Mx Plan)
> My nearest stab would be that this particular T-SQL (and STATS option in
particular) is causing some sort of collision between SQL Server and SQL
Server Agent since they would both be running under the same account. (But
surely I'm not the only one in the history of SQL Server to have created a
sysdb mx plan w/ both SQL and SQL Agent running under an identical domain
account, huh')
> Ideas'|||In my first post I listed what was in the Mx Plan History. Does
anyone have any other ideas?
Geof
"Hassan" <fatima_ja@.hotmail.com> wrote in message news:<#GDGyveYEHA.996@.TK2MSFTNGP12.phx.gbl>...
> Go the Maintenance Plan and right click and view maintenance history out
> there ...Thats where most of the reasoning is for the failure..

msdb log backup failed

Hello guys,
I am sorry if I insist but I am still having this error about msdb log
file failed.
BACKUP failed to complete the command BACKUP LOG [msdb] TO [systemLo
g]
WITH NOINIT , NOUNLOAD , NAME = N'msdb backup', NOSKIP , STATS =
10, NOFORMAT
I do not understand why.
Could someone help me on solve this problem.
InaHi,
Can you verify the recovery model of MSDB database by executing below
command:-
select databasepropertyex('msdb','recovery')
If the result return SIMPLE then you can not perform a transaction log
backup. Incase if you need to do a log backup then change the recovery
model to FULL using below command
ALTER DATABASE MSDB SET RECOVERY FULL
After to regroup the backup chain; perform a FULL MSDB backup and then then
start the log backup.,
Thanks
Hari
"ina" <roberta.inalbon@.gmail.com> wrote in message
news:1159778124.630986.307670@.h48g2000cwc.googlegroups.com...
> Hello guys,
> I am sorry if I insist but I am still having this error about msdb log
> file failed.
> BACKUP failed to complete the command BACKUP LOG [msdb] TO [system
Log]
> WITH NOINIT , NOUNLOAD , NAME = N'msdb backup', NOSKIP , STATS =
> 10, NOFORMAT
>
> I do not understand why.
> Could someone help me on solve this problem.
> Ina
>|||Thanks Hari,
It was set to simple. I changed as you advice me. One question when I
schedule the schedule log backup do you thing i can do something
between 4 Am until 10 Pm (every hour) because the backup of MSDB is 23
PM ?
ina
Hari Prasad wrote:[vbcol=seagreen]
> Hi,
> Can you verify the recovery model of MSDB database by executing below
> command:-
> select databasepropertyex('msdb','recovery')
> If the result return SIMPLE then you can not perform a transaction log
> backup. Incase if you need to do a log backup then change the recovery
> model to FULL using below command
> ALTER DATABASE MSDB SET RECOVERY FULL
> After to regroup the backup chain; perform a FULL MSDB backup and then the
n
> start the log backup.,
> Thanks
> Hari
>
> "ina" <roberta.inalbon@.gmail.com> wrote in message
> news:1159778124.630986.307670@.h48g2000cwc.googlegroups.com...

msdb log backup failed

Hello guys,
I am sorry if I insist but I am still having this error about msdb log
file failed.
BACKUP failed to complete the command BACKUP LOG [msdb] TO [systemLog]
WITH NOINIT , NOUNLOAD , NAME = N'msdb backup', NOSKIP , STATS =
10, NOFORMAT
I do not understand why.
Could someone help me on solve this problem.
Ina
Hi,
Can you verify the recovery model of MSDB database by executing below
command:-
select databasepropertyex('msdb','recovery')
If the result return SIMPLE then you can not perform a transaction log
backup. Incase if you need to do a log backup then change the recovery
model to FULL using below command
ALTER DATABASE MSDB SET RECOVERY FULL
After to regroup the backup chain; perform a FULL MSDB backup and then then
start the log backup.,
Thanks
Hari
"ina" <roberta.inalbon@.gmail.com> wrote in message
news:1159778124.630986.307670@.h48g2000cwc.googlegr oups.com...
> Hello guys,
> I am sorry if I insist but I am still having this error about msdb log
> file failed.
> BACKUP failed to complete the command BACKUP LOG [msdb] TO [systemLog]
> WITH NOINIT , NOUNLOAD , NAME = N'msdb backup', NOSKIP , STATS =
> 10, NOFORMAT
>
> I do not understand why.
> Could someone help me on solve this problem.
> Ina
>
|||Thanks Hari,
It was set to simple. I changed as you advice me. One question when I
schedule the schedule log backup do you thing i can do something
between 4 Am until 10 Pm (every hour) because the backup of MSDB is 23
PM ?
ina
Hari Prasad wrote:[vbcol=seagreen]
> Hi,
> Can you verify the recovery model of MSDB database by executing below
> command:-
> select databasepropertyex('msdb','recovery')
> If the result return SIMPLE then you can not perform a transaction log
> backup. Incase if you need to do a log backup then change the recovery
> model to FULL using below command
> ALTER DATABASE MSDB SET RECOVERY FULL
> After to regroup the backup chain; perform a FULL MSDB backup and then then
> start the log backup.,
> Thanks
> Hari
>
> "ina" <roberta.inalbon@.gmail.com> wrote in message
> news:1159778124.630986.307670@.h48g2000cwc.googlegr oups.com...

msdb log backup failed

Hello guys,
I am sorry if I insist but I am still having this error about msdb log
file failed.
BACKUP failed to complete the command BACKUP LOG [msdb] TO [systemLog]
WITH NOINIT , NOUNLOAD , NAME = N'msdb backup', NOSKIP , STATS = 10, NOFORMAT
I do not understand why.
Could someone help me on solve this problem.
InaHi,
Can you verify the recovery model of MSDB database by executing below
command:-
select databasepropertyex('msdb','recovery')
If the result return SIMPLE then you can not perform a transaction log
backup. Incase if you need to do a log backup then change the recovery
model to FULL using below command
ALTER DATABASE MSDB SET RECOVERY FULL
After to regroup the backup chain; perform a FULL MSDB backup and then then
start the log backup.,
Thanks
Hari
"ina" <roberta.inalbon@.gmail.com> wrote in message
news:1159778124.630986.307670@.h48g2000cwc.googlegroups.com...
> Hello guys,
> I am sorry if I insist but I am still having this error about msdb log
> file failed.
> BACKUP failed to complete the command BACKUP LOG [msdb] TO [systemLog]
> WITH NOINIT , NOUNLOAD , NAME = N'msdb backup', NOSKIP , STATS => 10, NOFORMAT
>
> I do not understand why.
> Could someone help me on solve this problem.
> Ina
>|||Thanks Hari,
It was set to simple. I changed as you advice me. One question when I
schedule the schedule log backup do you thing i can do something
between 4 Am until 10 Pm (every hour) because the backup of MSDB is 23
PM ?
ina
Hari Prasad wrote:
> Hi,
> Can you verify the recovery model of MSDB database by executing below
> command:-
> select databasepropertyex('msdb','recovery')
> If the result return SIMPLE then you can not perform a transaction log
> backup. Incase if you need to do a log backup then change the recovery
> model to FULL using below command
> ALTER DATABASE MSDB SET RECOVERY FULL
> After to regroup the backup chain; perform a FULL MSDB backup and then then
> start the log backup.,
> Thanks
> Hari
>
> "ina" <roberta.inalbon@.gmail.com> wrote in message
> news:1159778124.630986.307670@.h48g2000cwc.googlegroups.com...
> > Hello guys,
> >
> > I am sorry if I insist but I am still having this error about msdb log
> > file failed.
> >
> > BACKUP failed to complete the command BACKUP LOG [msdb] TO [systemLog]
> > WITH NOINIT , NOUNLOAD , NAME = N'msdb backup', NOSKIP , STATS => > 10, NOFORMAT
> >
> >
> > I do not understand why.
> >
> > Could someone help me on solve this problem.
> >
> > Ina
> >