Enumerate backup files

How do you enumerate database backup files? I see Server has an EnumDirectories but no EnumFiles. I'd like to show the user a list of database backups and have them choose the one they want to restore.SELECT DISTINCT physical_device_name FROM msdb.dbo.backupmediafamily returns the list.

Enumerate backup files

How do you enumerate database backup files? I see Server has an EnumDirectories but no EnumFiles. I'd like to show the user a list of database backups and have them choose the one they want to restore.SELECT DISTINCT physical_device_name FROM msdb.dbo.backupmediafamily returns the list.

Enterprise Manager Tape Backup issue

I have multiple failed backups jobs through the enterprise manager. I have an
event id 9 "\device\scis\aic78u21 did not respond within the timeout period"
and event id 15 "\device\tape0 is not ready for access yet." The aic78u21 is
the scsi controller and only appeared once. Since then, I have had multiple
event id 15. However I did boot up into the scsi utility and teh dlt tape
device is listed in the utility with scsi id 3, and the controler listed as
scsi id 7. I then ran a ntbackup job on a new media set and it ran fine.
However the scheduled jobs within enterprise manager still will not run. Our
SQL admin is no longer with us, and myself and another have been tasked with
the SQL admin, so we are both leery of making any changes that might have bad
reprecussions later. I thought about deleting and adding the tape device back
into the enterprise manager, but I'm wondering if it is a media set issue.
What do you think?
I forgot to mention that the device does show up in device manager with the
questions marks in the other devices category. Is this due to the device
running off of the scsi controller drivers?
"sigm" wrote:

> I have multiple failed backups jobs through the enterprise manager. I have an
> event id 9 "\device\scis\aic78u21 did not respond within the timeout period"
> and event id 15 "\device\tape0 is not ready for access yet." The aic78u21 is
> the scsi controller and only appeared once. Since then, I have had multiple
> event id 15. However I did boot up into the scsi utility and teh dlt tape
> device is listed in the utility with scsi id 3, and the controler listed as
> scsi id 7. I then ran a ntbackup job on a new media set and it ran fine.
> However the scheduled jobs within enterprise manager still will not run. Our
> SQL admin is no longer with us, and myself and another have been tasked with
> the SQL admin, so we are both leery of making any changes that might have bad
> reprecussions later. I thought about deleting and adding the tape device back
> into the enterprise manager, but I'm wondering if it is a media set issue.
> What do you think?
sql

Enterprise Manager Tape Backup issue

I have multiple failed backups jobs through the enterprise manager. I have a
n
event id 9 "\device\scis\aic78u21 did not respond within the timeout period"
and event id 15 "\device\tape0 is not ready for access yet." The aic78u21 is
the scsi controller and only appeared once. Since then, I have had multiple
event id 15. However I did boot up into the scsi utility and teh dlt tape
device is listed in the utility with scsi id 3, and the controler listed as
scsi id 7. I then ran a ntbackup job on a new media set and it ran fine.
However the scheduled jobs within enterprise manager still will not run. Our
SQL admin is no longer with us, and myself and another have been tasked with
the SQL admin, so we are both leery of making any changes that might have ba
d
reprecussions later. I thought about deleting and adding the tape device bac
k
into the enterprise manager, but I'm wondering if it is a media set issue.
What do you think?I forgot to mention that the device does show up in device manager with the
questions marks in the other devices category. Is this due to the device
running off of the scsi controller drivers?
"sigm" wrote:

> I have multiple failed backups jobs through the enterprise manager. I have
an
> event id 9 "\device\scis\aic78u21 did not respond within the timeout perio
d"
> and event id 15 "\device\tape0 is not ready for access yet." The aic78u21
is
> the scsi controller and only appeared once. Since then, I have had multipl
e
> event id 15. However I did boot up into the scsi utility and teh dlt tape
> device is listed in the utility with scsi id 3, and the controler listed a
s
> scsi id 7. I then ran a ntbackup job on a new media set and it ran fine.
> However the scheduled jobs within enterprise manager still will not run. O
ur
> SQL admin is no longer with us, and myself and another have been tasked wi
th
> the SQL admin, so we are both leery of making any changes that might have
bad
> reprecussions later. I thought about deleting and adding the tape device b
ack
> into the enterprise manager, but I'm wondering if it is a media set issue.
> What do you think?

Enterprise Manager Tape Backup issue

I have multiple failed backups jobs through the enterprise manager. I have an
event id 9 "\device\scis\aic78u21 did not respond within the timeout period"
and event id 15 "\device\tape0 is not ready for access yet." The aic78u21 is
the scsi controller and only appeared once. Since then, I have had multiple
event id 15. However I did boot up into the scsi utility and teh dlt tape
device is listed in the utility with scsi id 3, and the controler listed as
scsi id 7. I then ran a ntbackup job on a new media set and it ran fine.
However the scheduled jobs within enterprise manager still will not run. Our
SQL admin is no longer with us, and myself and another have been tasked with
the SQL admin, so we are both leery of making any changes that might have bad
reprecussions later. I thought about deleting and adding the tape device back
into the enterprise manager, but I'm wondering if it is a media set issue.
What do you think?I forgot to mention that the device does show up in device manager with the
questions marks in the other devices category. Is this due to the device
running off of the scsi controller drivers?
"sigm" wrote:
> I have multiple failed backups jobs through the enterprise manager. I have an
> event id 9 "\device\scis\aic78u21 did not respond within the timeout period"
> and event id 15 "\device\tape0 is not ready for access yet." The aic78u21 is
> the scsi controller and only appeared once. Since then, I have had multiple
> event id 15. However I did boot up into the scsi utility and teh dlt tape
> device is listed in the utility with scsi id 3, and the controler listed as
> scsi id 7. I then ran a ntbackup job on a new media set and it ran fine.
> However the scheduled jobs within enterprise manager still will not run. Our
> SQL admin is no longer with us, and myself and another have been tasked with
> the SQL admin, so we are both leery of making any changes that might have bad
> reprecussions later. I thought about deleting and adding the tape device back
> into the enterprise manager, but I'm wondering if it is a media set issue.
> What do you think?

Enterprise Manager hangs

Hi,
I have a production server which has about six user databases. Recently,
when I try to do a restore ( I wanted to see the available backup sets) on
any of the databases using Enterprise Manager (All Tasks -> Restore) it
hangs. However, it promptly brings a pop up window when I do the All Tasks ->
Backup. What might be causing it to behave this way?
Thanks in advance.
Hi
Perhaps you need to delete a backup history
http://weblogs.sqlteam.com/geoffh/archive/2008/01/21/MSDB-Performance-Tuning.aspx
"ronnie" <ronnie@.discussions.microsoft.com> wrote in message
news:B67B18F5-2ACD-49E5-A7EA-AA5A65487B68@.microsoft.com...
> Hi,
> I have a production server which has about six user databases. Recently,
> when I try to do a restore ( I wanted to see the available backup sets) on
> any of the databases using Enterprise Manager (All Tasks -> Restore) it
> hangs. However, it promptly brings a pop up window when I do the All
> Tasks ->
> Backup. What might be causing it to behave this way?
> Thanks in advance.
|||We are seeing this too. The only change we have done recently is applying
SLQ Server Cum 6 for SP2. Management Studio hangs when we attempt to restore
from a device. Specifically, it hangs when we click "Add" on the Specify
Backup dialog. We have no problems using the "From Database" option, so I do
not believe it has anything to do with MSDB indexes.
"ronnie" wrote:

> Hi,
> I have a production server which has about six user databases. Recently,
> when I try to do a restore ( I wanted to see the available backup sets) on
> any of the databases using Enterprise Manager (All Tasks -> Restore) it
> hangs. However, it promptly brings a pop up window when I do the All Tasks ->
> Backup. What might be causing it to behave this way?
> Thanks in advance.
|||I have narrowed this down to the command "insert #avmed exec
master.dbo.xp_availablemedia", which is what is hanging. I ran "exec
master.dbo.xp_availablemedia" stand alone, and it hangs. This is calling DLL
xpStar90.dll. Has anyone ever seen what might cause this?
"Brent" wrote:
[vbcol=seagreen]
> We are seeing this too. The only change we have done recently is applying
> SLQ Server Cum 6 for SP2. Management Studio hangs when we attempt to restore
> from a device. Specifically, it hangs when we click "Add" on the Specify
> Backup dialog. We have no problems using the "From Database" option, so I do
> not believe it has anything to do with MSDB indexes.
> "ronnie" wrote:
|||Restarting the server resolved this.
"Brent" wrote:
[vbcol=seagreen]
> I have narrowed this down to the command "insert #avmed exec
> master.dbo.xp_availablemedia", which is what is hanging. I ran "exec
> master.dbo.xp_availablemedia" stand alone, and it hangs. This is calling DLL
> xpStar90.dll. Has anyone ever seen what might cause this?
> "Brent" wrote:
|||I tried deleting the backuphistory but it didn't work. Maybe I need to
restart the server.
"Brent" wrote:
[vbcol=seagreen]
> Restarting the server resolved this.
> "Brent" wrote:
|||Our SQL Instance is clustered, so we failed over to the other node and
everything is fine. As soon as we restarted the node where things were
hanging, we started getting alerts on that the C drive is going bad. I think
this is why it was having trouble calling the dll. You may have a similar
issue. Are you using any monitoring tools like Sitescope to monitor the
hardware? You may have a drive that is going bad.
"ronnie" wrote:
[vbcol=seagreen]
> I tried deleting the backuphistory but it didn't work. Maybe I need to
> restart the server.
> "Brent" wrote:

Enterprise Manager hangs

Hi,
I have a production server which has about six user databases. Recently,
when I try to do a restore ( I wanted to see the available backup sets) on
any of the databases using Enterprise Manager (All Tasks -> Restore) it
hangs. However, it promptly brings a pop up window when I do the All Tasks ->
Backup. What might be causing it to behave this way?
Thanks in advance.Hi
Perhaps you need to delete a backup history
http://weblogs.sqlteam.com/geoffh/archive/2008/01/21/MSDB-Performance-Tuning.aspx
"ronnie" <ronnie@.discussions.microsoft.com> wrote in message
news:B67B18F5-2ACD-49E5-A7EA-AA5A65487B68@.microsoft.com...
> Hi,
> I have a production server which has about six user databases. Recently,
> when I try to do a restore ( I wanted to see the available backup sets) on
> any of the databases using Enterprise Manager (All Tasks -> Restore) it
> hangs. However, it promptly brings a pop up window when I do the All
> Tasks ->
> Backup. What might be causing it to behave this way?
> Thanks in advance.|||We are seeing this too. The only change we have done recently is applying
SLQ Server Cum 6 for SP2. Management Studio hangs when we attempt to restore
from a device. Specifically, it hangs when we click "Add" on the Specify
Backup dialog. We have no problems using the "From Database" option, so I do
not believe it has anything to do with MSDB indexes.
"ronnie" wrote:
> Hi,
> I have a production server which has about six user databases. Recently,
> when I try to do a restore ( I wanted to see the available backup sets) on
> any of the databases using Enterprise Manager (All Tasks -> Restore) it
> hangs. However, it promptly brings a pop up window when I do the All Tasks ->
> Backup. What might be causing it to behave this way?
> Thanks in advance.|||I have narrowed this down to the command "insert #avmed exec
master.dbo.xp_availablemedia", which is what is hanging. I ran "exec
master.dbo.xp_availablemedia" stand alone, and it hangs. This is calling DLL
xpStar90.dll. Has anyone ever seen what might cause this?
"Brent" wrote:
> We are seeing this too. The only change we have done recently is applying
> SLQ Server Cum 6 for SP2. Management Studio hangs when we attempt to restore
> from a device. Specifically, it hangs when we click "Add" on the Specify
> Backup dialog. We have no problems using the "From Database" option, so I do
> not believe it has anything to do with MSDB indexes.
> "ronnie" wrote:
> > Hi,
> >
> > I have a production server which has about six user databases. Recently,
> > when I try to do a restore ( I wanted to see the available backup sets) on
> > any of the databases using Enterprise Manager (All Tasks -> Restore) it
> > hangs. However, it promptly brings a pop up window when I do the All Tasks ->
> > Backup. What might be causing it to behave this way?
> >
> > Thanks in advance.|||Restarting the server resolved this.
"Brent" wrote:
> I have narrowed this down to the command "insert #avmed exec
> master.dbo.xp_availablemedia", which is what is hanging. I ran "exec
> master.dbo.xp_availablemedia" stand alone, and it hangs. This is calling DLL
> xpStar90.dll. Has anyone ever seen what might cause this?
> "Brent" wrote:
> > We are seeing this too. The only change we have done recently is applying
> > SLQ Server Cum 6 for SP2. Management Studio hangs when we attempt to restore
> > from a device. Specifically, it hangs when we click "Add" on the Specify
> > Backup dialog. We have no problems using the "From Database" option, so I do
> > not believe it has anything to do with MSDB indexes.
> >
> > "ronnie" wrote:
> >
> > > Hi,
> > >
> > > I have a production server which has about six user databases. Recently,
> > > when I try to do a restore ( I wanted to see the available backup sets) on
> > > any of the databases using Enterprise Manager (All Tasks -> Restore) it
> > > hangs. However, it promptly brings a pop up window when I do the All Tasks ->
> > > Backup. What might be causing it to behave this way?
> > >
> > > Thanks in advance.|||I tried deleting the backuphistory but it didn't work. Maybe I need to
restart the server.
"Brent" wrote:
> Restarting the server resolved this.
> "Brent" wrote:
> > I have narrowed this down to the command "insert #avmed exec
> > master.dbo.xp_availablemedia", which is what is hanging. I ran "exec
> > master.dbo.xp_availablemedia" stand alone, and it hangs. This is calling DLL
> > xpStar90.dll. Has anyone ever seen what might cause this?
> >
> > "Brent" wrote:
> >
> > > We are seeing this too. The only change we have done recently is applying
> > > SLQ Server Cum 6 for SP2. Management Studio hangs when we attempt to restore
> > > from a device. Specifically, it hangs when we click "Add" on the Specify
> > > Backup dialog. We have no problems using the "From Database" option, so I do
> > > not believe it has anything to do with MSDB indexes.
> > >
> > > "ronnie" wrote:
> > >
> > > > Hi,
> > > >
> > > > I have a production server which has about six user databases. Recently,
> > > > when I try to do a restore ( I wanted to see the available backup sets) on
> > > > any of the databases using Enterprise Manager (All Tasks -> Restore) it
> > > > hangs. However, it promptly brings a pop up window when I do the All Tasks ->
> > > > Backup. What might be causing it to behave this way?
> > > >
> > > > Thanks in advance.|||Our SQL Instance is clustered, so we failed over to the other node and
everything is fine. As soon as we restarted the node where things were
hanging, we started getting alerts on that the C drive is going bad. I think
this is why it was having trouble calling the dll. You may have a similar
issue. Are you using any monitoring tools like Sitescope to monitor the
hardware? You may have a drive that is going bad.
"ronnie" wrote:
> I tried deleting the backuphistory but it didn't work. Maybe I need to
> restart the server.
> "Brent" wrote:
> > Restarting the server resolved this.
> >
> > "Brent" wrote:
> >
> > > I have narrowed this down to the command "insert #avmed exec
> > > master.dbo.xp_availablemedia", which is what is hanging. I ran "exec
> > > master.dbo.xp_availablemedia" stand alone, and it hangs. This is calling DLL
> > > xpStar90.dll. Has anyone ever seen what might cause this?
> > >
> > > "Brent" wrote:
> > >
> > > > We are seeing this too. The only change we have done recently is applying
> > > > SLQ Server Cum 6 for SP2. Management Studio hangs when we attempt to restore
> > > > from a device. Specifically, it hangs when we click "Add" on the Specify
> > > > Backup dialog. We have no problems using the "From Database" option, so I do
> > > > not believe it has anything to do with MSDB indexes.
> > > >
> > > > "ronnie" wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I have a production server which has about six user databases. Recently,
> > > > > when I try to do a restore ( I wanted to see the available backup sets) on
> > > > > any of the databases using Enterprise Manager (All Tasks -> Restore) it
> > > > > hangs. However, it promptly brings a pop up window when I do the All Tasks ->
> > > > > Backup. What might be causing it to behave this way?
> > > > >
> > > > > Thanks in advance.

Enterprise Manager Corrupted?

We create a simple maintenance plan with no error. When we go back to edit the settings, many have defaulted.
In particular, the backup definition loses the definition of where to backup files to on the disk is cleared, and the Device option is checked.
Further, in delete files older than, the selector will not populate (although we can manually enter a number), and the drop-down that should show "hours", "Days" etc, is completely empty, and we cannot enter anything.
Suggestions?
Have your client tools been updated with SP3?
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"jnorman" <anonymous@.discussions.microsoft.com> wrote in message
news:ADE1F886-6641-4741-ABD4-BFED23FD7AED@.microsoft.com...
> We create a simple maintenance plan with no error. When we go back to edit
> the settings, many have defaulted.
> In particular, the backup definition loses the definition of where to
> backup files to on the disk is cleared, and the Device option is checked.
> Further, in delete files older than, the selector will not populate
> (although we can manually enter a number), and the drop-down that should
> show "hours", "Days" etc, is completely empty, and we cannot enter
> anything.
> Suggestions?
>
|||Good idea. In fact it turns out that, despite assurances
to the contrary, our new client had NOT upgraded to sp3.
So we installed it.
Unfortunately, We still have the same problem. We can
still save an original maintenance plan, although the drop-
down list for the number of time units to delete after is
still blank (it apparently defaults to "weeks," though).
The original save is error-free, but to save any mods
generates this error:
error 8114: error converting data type int to tinyint
We still have no way to simply modify a maintenance plan.
More suggestions?
>--Original Message--
>Have your client tools been updated with SP3?
>--
>Aaron Bertrand
>SQL Server MVP
>http://www.aspfaq.com/
>
>"jnorman" <anonymous@.discussions.microsoft.com> wrote in
message
>news:ADE1F886-6641-4741-ABD4-BFED23FD7AED@.microsoft.com...
we go back to edit
definition of where to
option is checked.
not populate
down that should
cannot enter
>
>.
>
|||What is the database compatibility? What hotfixes have been applied? Have
you restored master or msdb from another place or another version?
I'm just trying to think of things which would make a system-used datatype
change, and usually these are restricted to service pack/version releases.
A
<anonymous@.discussions.microsoft.com> wrote in message
news:153c901c41a8d$122349f0$a601280a@.phx.gbl...
> Good idea. In fact it turns out that, despite assurances
> to the contrary, our new client had NOT upgraded to sp3.
> So we installed it.
> Unfortunately, We still have the same problem. We can
> still save an original maintenance plan, although the drop-
> down list for the number of time units to delete after is
> still blank (it apparently defaults to "weeks," though).
> The original save is error-free, but to save any mods
> generates this error:
> error 8114: error converting data type int to tinyint
> We still have no way to simply modify a maintenance plan.
> More suggestions?
> message
> we go back to edit
> definition of where to
> option is checked.
> not populate
> down that should
> cannot enter

Enterprise Manager Corrupted?

We create a simple maintenance plan with no error. When we go back to edit t
he settings, many have defaulted.
In particular, the backup definition loses the definition of where to backup
files to on the disk is cleared, and the Device option is checked.
Further, in delete files older than, the selector will not populate (althoug
h we can manually enter a number), and the drop-down that should show "hours
", "Days" etc, is completely empty, and we cannot enter anything.
Suggestions?Have your client tools been updated with SP3?
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"jnorman" <anonymous@.discussions.microsoft.com> wrote in message
news:ADE1F886-6641-4741-ABD4-BFED23FD7AED@.microsoft.com...
> We create a simple maintenance plan with no error. When we go back to edit
> the settings, many have defaulted.
> In particular, the backup definition loses the definition of where to
> backup files to on the disk is cleared, and the Device option is checked.
> Further, in delete files older than, the selector will not populate
> (although we can manually enter a number), and the drop-down that should
> show "hours", "Days" etc, is completely empty, and we cannot enter
> anything.
> Suggestions?
>|||Good idea. In fact it turns out that, despite assurances
to the contrary, our new client had NOT upgraded to sp3.
So we installed it.
Unfortunately, We still have the same problem. We can
still save an original maintenance plan, although the drop-
down list for the number of time units to delete after is
still blank (it apparently defaults to "weeks," though).
The original save is error-free, but to save any mods
generates this error:
error 8114: error converting data type int to tinyint
We still have no way to simply modify a maintenance plan.
More suggestions?
>--Original Message--
>Have your client tools been updated with SP3?
>--
>Aaron Bertrand
>SQL Server MVP
>http://www.aspfaq.com/
>
>"jnorman" <anonymous@.discussions.microsoft.com> wrote in
message
>news:ADE1F886-6641-4741-ABD4-BFED23FD7AED@.microsoft.com...
we go back to edit
definition of where to
option is checked.
not populate
down that should
cannot enter
>
>.
>|||What is the database compatibility? What hotfixes have been applied? Have
you restored master or msdb from another place or another version?
I'm just trying to think of things which would make a system-used datatype
change, and usually these are restricted to service pack/version releases.
A
<anonymous@.discussions.microsoft.com> wrote in message
news:153c901c41a8d$122349f0$a601280a@.phx
.gbl...
> Good idea. In fact it turns out that, despite assurances
> to the contrary, our new client had NOT upgraded to sp3.
> So we installed it.
> Unfortunately, We still have the same problem. We can
> still save an original maintenance plan, although the drop-
> down list for the number of time units to delete after is
> still blank (it apparently defaults to "weeks," though).
> The original save is error-free, but to save any mods
> generates this error:
> error 8114: error converting data type int to tinyint
> We still have no way to simply modify a maintenance plan.
> More suggestions?
> message
> we go back to edit
> definition of where to
> option is checked.
> not populate
> down that should
> cannot enter|||The SQL Server 2000 instance was originally installed (by another
consultant) last summer. I doubt that any hot fixes were applied before we
came onto the scene in December, since, as you saw, they never got around to
applying SP3.
The master/msdb were installed fresh, I'm sure (the other vendor wasn't
sophisticated enough to know how to do any of that.
Any other thoughts? I'm sort of getting the idea that we probably have no
choice but to rip it out and reinstall?
J
"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:OHyiE7oGEHA.2052@.TK2MSFTNGP11.phx.gbl...
> What is the database compatibility? What hotfixes have been applied?
Have
> you restored master or msdb from another place or another version?
> I'm just trying to think of things which would make a system-used datatype
> change, and usually these are restricted to service pack/version releases.
> A
>
> <anonymous@.discussions.microsoft.com> wrote in message
> news:153c901c41a8d$122349f0$a601280a@.phx
.gbl...
>

Enterprise Manager broken on SQL 2000, how to put back

I uninstalled Veritas Backup Exec 90 from my SQL 2000 server.
Now, none of my SQL "Snap Ins" (SQL Query, Enterprise Manager) work.
SQL appears to be running fine and my SQL applications are working fine too.
How can I put back my SQL Enterprise Manager and SQL Query Analyser?
If I reinstall SQL 2000 will that mess up my installed SQL applications?
Will SQL installer attempt to "repair" things with messing up my installed
databases?
My SQL applications/databases are a bear to reinstall and I don't want to if
I don't have to. Like I said, they are running fine.
Greatful for any help.
RonYou can try to reinstall the SQL Server service pack to start with...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:A7A214E5-B073-4988-8E18-8464F2407483@.microsoft.com...
> I uninstalled Veritas Backup Exec 90 from my SQL 2000 server.
> Now, none of my SQL "Snap Ins" (SQL Query, Enterprise Manager) work.
> SQL appears to be running fine and my SQL applications are working fine too.
> How can I put back my SQL Enterprise Manager and SQL Query Analyser?
> If I reinstall SQL 2000 will that mess up my installed SQL applications?
> Will SQL installer attempt to "repair" things with messing up my installed
> databases?
> My SQL applications/databases are a bear to reinstall and I don't want to if
> I don't have to. Like I said, they are running fine.
> Greatful for any help.
> Ron
>|||Thank you for your response. I tried first to restart the SQL server. Boy,
that was a mistake (of sorts). When the server came back up, none of the SQL
applications were working (although the SQL service had started).
Tried to reinstall SP3 as suggested (thank you) but niether windows
authentication nor the sa account would work.
So, out of desperation I reinstalled Veritas Backupexec 91 for servers. I
rebooted the machine and bingo, the SQL apps could access the SQL databases
again!
But SQL is still broken, in that Enterprise Manager and SQL query will not
run.
I am almost to the point where I am going to try reinstalling SQL.
Will it recognize my existing SQL databases or will I have to reinstall
everything?
The Win 2003 server itself is fine, it's just that SQL is "not all there" it
seems.
Ron
"Ron" wrote:
> I uninstalled Veritas Backup Exec 90 from my SQL 2000 server.
> Now, none of my SQL "Snap Ins" (SQL Query, Enterprise Manager) work.
> SQL appears to be running fine and my SQL applications are working fine too.
> How can I put back my SQL Enterprise Manager and SQL Query Analyser?
> If I reinstall SQL 2000 will that mess up my installed SQL applications?
> Will SQL installer attempt to "repair" things with messing up my installed
> databases?
> My SQL applications/databases are a bear to reinstall and I don't want to if
> I don't have to. Like I said, they are running fine.
> Greatful for any help.
> Ron
>

Enterprise Manager broken on SQL 2000, how to put back

I uninstalled Veritas Backup Exec 90 from my SQL 2000 server.
Now, none of my SQL "Snap Ins" (SQL Query, Enterprise Manager) work.
SQL appears to be running fine and my SQL applications are working fine too.
How can I put back my SQL Enterprise Manager and SQL Query Analyser?
If I reinstall SQL 2000 will that mess up my installed SQL applications?
Will SQL installer attempt to "repair" things with messing up my installed
databases?
My SQL applications/databases are a bear to reinstall and I don't want to if
I don't have to. Like I said, they are running fine.
Greatful for any help.
Ron
You can try to reinstall the SQL Server service pack to start with...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:A7A214E5-B073-4988-8E18-8464F2407483@.microsoft.com...
> I uninstalled Veritas Backup Exec 90 from my SQL 2000 server.
> Now, none of my SQL "Snap Ins" (SQL Query, Enterprise Manager) work.
> SQL appears to be running fine and my SQL applications are working fine too.
> How can I put back my SQL Enterprise Manager and SQL Query Analyser?
> If I reinstall SQL 2000 will that mess up my installed SQL applications?
> Will SQL installer attempt to "repair" things with messing up my installed
> databases?
> My SQL applications/databases are a bear to reinstall and I don't want to if
> I don't have to. Like I said, they are running fine.
> Greatful for any help.
> Ron
>
|||Thank you for your response. I tried first to restart the SQL server. Boy,
that was a mistake (of sorts). When the server came back up, none of the SQL
applications were working (although the SQL service had started).
Tried to reinstall SP3 as suggested (thank you) but niether windows
authentication nor the sa account would work.
So, out of desperation I reinstalled Veritas Backupexec 91 for servers. I
rebooted the machine and bingo, the SQL apps could access the SQL databases
again!
But SQL is still broken, in that Enterprise Manager and SQL query will not
run.
I am almost to the point where I am going to try reinstalling SQL.
Will it recognize my existing SQL databases or will I have to reinstall
everything?
The Win 2003 server itself is fine, it's just that SQL is "not all there" it
seems.
Ron
"Ron" wrote:

> I uninstalled Veritas Backup Exec 90 from my SQL 2000 server.
> Now, none of my SQL "Snap Ins" (SQL Query, Enterprise Manager) work.
> SQL appears to be running fine and my SQL applications are working fine too.
> How can I put back my SQL Enterprise Manager and SQL Query Analyser?
> If I reinstall SQL 2000 will that mess up my installed SQL applications?
> Will SQL installer attempt to "repair" things with messing up my installed
> databases?
> My SQL applications/databases are a bear to reinstall and I don't want to if
> I don't have to. Like I said, they are running fine.
> Greatful for any help.
> Ron
>

Enterprise Manager automatic backup

The "Schedule" checkbox on the backup page in Enterprise Manager
doesn't stay checked when I close it. All of the schedule options
revert to default values. What am I doing wrong? Otherwise, backup and
restore works fine. Running MSDE over network with Windows XP Home
Edition on all machines. Thanks.That only creates an Agent Job. For every time you open that dialog, select "schedule", a new job is
created for you.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Brian2401" <brian.nutsch@.gmail.com> wrote in message
news:1159249821.610783.70390@.m7g2000cwm.googlegroups.com...
> The "Schedule" checkbox on the backup page in Enterprise Manager
> doesn't stay checked when I close it. All of the schedule options
> revert to default values. What am I doing wrong? Otherwise, backup and
> restore works fine. Running MSDE over network with Windows XP Home
> Edition on all machines. Thanks.
>|||Thanks Tibor! -Brian
Tibor Karaszi wrote:
> That only creates an Agent Job. For every time you open that dialog, select "schedule", a new job is
> created for you.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Brian2401" <brian.nutsch@.gmail.com> wrote in message
> news:1159249821.610783.70390@.m7g2000cwm.googlegroups.com...
> > The "Schedule" checkbox on the backup page in Enterprise Manager
> > doesn't stay checked when I close it. All of the schedule options
> > revert to default values. What am I doing wrong? Otherwise, backup and
> > restore works fine. Running MSDE over network with Windows XP Home
> > Edition on all machines. Thanks.
> >

Enterprise Manager automatic backup

The "Schedule" checkbox on the backup page in Enterprise Manager
doesn't stay checked when I close it. All of the schedule options
revert to default values. What am I doing wrong? Otherwise, backup and
restore works fine. Running MSDE over network with Windows XP Home
Edition on all machines. Thanks.
That only creates an Agent Job. For every time you open that dialog, select "schedule", a new job is
created for you.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Brian2401" <brian.nutsch@.gmail.com> wrote in message
news:1159249821.610783.70390@.m7g2000cwm.googlegrou ps.com...
> The "Schedule" checkbox on the backup page in Enterprise Manager
> doesn't stay checked when I close it. All of the schedule options
> revert to default values. What am I doing wrong? Otherwise, backup and
> restore works fine. Running MSDE over network with Windows XP Home
> Edition on all machines. Thanks.
>
|||Thanks Tibor! -Brian
Tibor Karaszi wrote:[vbcol=seagreen]
> That only creates an Agent Job. For every time you open that dialog, select "schedule", a new job is
> created for you.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Brian2401" <brian.nutsch@.gmail.com> wrote in message
> news:1159249821.610783.70390@.m7g2000cwm.googlegrou ps.com...

Enterprise Manager automatic backup

The "Schedule" checkbox on the backup page in Enterprise Manager
doesn't stay checked when I close it. All of the schedule options
revert to default values. What am I doing wrong? Otherwise, backup and
restore works fine. Running MSDE over network with Windows XP Home
Edition on all machines. Thanks.That only creates an Agent Job. For every time you open that dialog, select
"schedule", a new job is
created for you.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Brian2401" <brian.nutsch@.gmail.com> wrote in message
news:1159249821.610783.70390@.m7g2000cwm.googlegroups.com...
> The "Schedule" checkbox on the backup page in Enterprise Manager
> doesn't stay checked when I close it. All of the schedule options
> revert to default values. What am I doing wrong? Otherwise, backup and
> restore works fine. Running MSDE over network with Windows XP Home
> Edition on all machines. Thanks.
>|||Thanks Tibor! -Brian
Tibor Karaszi wrote:[vbcol=seagreen]
> That only creates an Agent Job. For every time you open that dialog, selec
t "schedule", a new job is
> created for you.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Brian2401" <brian.nutsch@.gmail.com> wrote in message
> news:1159249821.610783.70390@.m7g2000cwm.googlegroups.com...

Enterprise manager

hi,
I used backup and restore moved a database from one server to another.
Everything works fine. But I got problem view the taskpad of the database. I
could view it from another server but not this server.
right after restore I could view it but after close EM and reopen , I got
this error when trying to view the taskpad of the database:
Internet Explorer script error:
An error has occurred in the script on this page:
Line: 307
Char: 2
Error: unspecified error
Code: 0
URL:
res://c:\Program%20Files\Microsoft%20SQL%20server\80\Tools\Binn\Resources\10
33\sqlmmc.rll/Tabs.html
Could you please help!!
Thanks
Kathy ChenHi Kathy.
Hopefully someone will give you a more precise answer to the actual problem
you're experiencing, but my 20c worth on this is that you probably shouldn't
become too dependant on the MMC SnapIn TaskPads. If you search the archive
of this newsgroup you'll find a trail of destruction from others trying to
use the TaskPad views - they simply don't work very reliably. There's lots
more on this in microsoft.public.management.mmc as well.
Another thing that often fails with Task Views is in the "Table Info" tab -
this view often won't let you scroll to the next page - often the next page
nav tools are missing. It's a really nice feature, but it just doesn't work
reliably, imho. My work around to that problem was simply to use profiler to
grab what the EM was sending to the server, saved it as a script & you get
the same information.. (c:
Regards,
Greg Linwood
SQL Server MVP
"Kathy" <kathy_chen@.hotmail.com> wrote in message
news:e8SWyCEyDHA.536@.tk2msftngp13.phx.gbl...
> hi,
> I used backup and restore moved a database from one server to another.
> Everything works fine. But I got problem view the taskpad of the database.
I
> could view it from another server but not this server.
> right after restore I could view it but after close EM and reopen , I got
> this error when trying to view the taskpad of the database:
>
> Internet Explorer script error:
> An error has occurred in the script on this page:
> Line: 307
> Char: 2
> Error: unspecified error
> Code: 0
> URL:
>
res://c:\Program%20Files\Microsoft%20SQL%20server\80\Tools\Binn\Resources\10
> 33\sqlmmc.rll/Tabs.html
> Could you please help!!
> Thanks
> Kathy Chen
>
>|||Hi Kathy,
There's a very simple workaround for the scripting error you'r
encountering in Enterprise Manager.
Just right-click on the DB, click view, then click list to display th
DB objects. Go back, right-click on the DB, click view, then clic
Taskpad. It will reset the web interface and it'll work again.
Yes, another stupid bug in MSSQL SQL Server.
Best Regards,
Chuck Lee
chucksql@.hotmail.co
-
chuckle
----
Posted via http://www.mcse.m
----
View this thread: http://www.mcse.ms/message205074.htm