Kind of an obscure question, but here goes.
SQL2000 SP4
I have a E: drive on my SQL server that is ~400gb. On it you'll find
a ~100gb live DB file and last night's 100gb .bak file (maintenance
plan is set for one day retention). The vendor is telling me that I
am going to run out of space doing the SQL backups because 100gb is
used by the live DB, 100gb is used by last nights .bak file, 100gb
will be used to write today's .bak file, and the last 100gb will be
used in the deletion process of removing the old .bak file.
I can't say I know how SQL handles the removal of the old .bak file
but is this a true statement that SQL will need equal free space to
delete the old .bak file?SQL deletes old backups AFTER creating new ones, so you will need space for
at least two backups.
Look at it this way, what happens if your database blows up during a backup.
If you have an older backup, you are fine. If you are overwriting your only
backup, it is time to polish up the resume.
Personally, I would go out and buy a couple of USB drives and back up to
there. Last week my mother purchased a 500GB model for $99. If that is not
an option, you could look into one of the commercially available backup
compression tools. The three major ones are SQLSafe (www.idera.com),
LiteSpeed for SQL (www.quest.com), and SQL Backup (www.red-gate.com).
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
<rockemhard@.gmail.com> wrote in message
news:04b97215-0ec7-4545-a43b-f072fb3c47a2@.e6g2000prf.googlegroups.com...
> Kind of an obscure question, but here goes.
> SQL2000 SP4
> I have a E: drive on my SQL server that is ~400gb. On it you'll find
> a ~100gb live DB file and last night's 100gb .bak file (maintenance
> plan is set for one day retention). The vendor is telling me that I
> am going to run out of space doing the SQL backups because 100gb is
> used by the live DB, 100gb is used by last nights .bak file, 100gb
> will be used to write today's .bak file, and the last 100gb will be
> used in the deletion process of removing the old .bak file.
> I can't say I know how SQL handles the removal of the old .bak file
> but is this a true statement that SQL will need equal free space to
> delete the old .bak file?|||Right, I aggree. In your scenario I need 300gb, not 400gb as the
vendor claims.
100gb - live DB
100gb - last nights backup
100gb - to create tonights backup
--
300gb Total to perform the whole operation
Vendor is saying:
100gb - live DB
100gb - last nights backup
100gb - to create tonights backup
100gb - extra needed to delete last nights backup after a successful
backup
--
400gb Total to perform the whole operation
I just don't understand why that extra 100gb is needed.
On Nov 28, 10:46 am, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
> SQL deletes old backups AFTER creating new ones, so you will need space fo
r
> at least two backups.
> Look at it this way, what happens if your database blows up during a backu
p.
> If you have an older backup, you are fine. If you are overwriting your on
ly
> backup, it is time to polish up the resume.|||Also, a backup on the same disk as the primary is pretty useless when you
think about it.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
<rockemhard@.gmail.com> wrote in message
news:b1987afa-2fde-4bcc-9e25-4d2632f7c009@.j44g2000hsj.googlegroups.com...[vbcol=seagreen]
> Right, I aggree. In your scenario I need 300gb, not 400gb as the
> vendor claims.
> 100gb - live DB
> 100gb - last nights backup
> 100gb - to create tonights backup
> --
> 300gb Total to perform the whole operation
>
> Vendor is saying:
> 100gb - live DB
> 100gb - last nights backup
> 100gb - to create tonights backup
> 100gb - extra needed to delete last nights backup after a successful
> backup
> --
> 400gb Total to perform the whole operation
> I just don't understand why that extra 100gb is needed.
> On Nov 28, 10:46 am, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:|||Only if it's not getting written to tape ;)
On Nov 28, 11:28 am, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
> Also, a backup on the same disk as the primary is pretty useless when you
> think about it.|||I've never seen Windows needing temp storage in order to delete a file. Perh
aps your vendor somehow
confuses the windows Recycle Bin functionality somehow...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<rockemhard@.gmail.com> wrote in message
news:b1987afa-2fde-4bcc-9e25-4d2632f7c009@.j44g2000hsj.googlegroups.com...[vbcol=seagreen]
> Right, I aggree. In your scenario I need 300gb, not 400gb as the
> vendor claims.
> 100gb - live DB
> 100gb - last nights backup
> 100gb - to create tonights backup
> --
> 300gb Total to perform the whole operation
>
> Vendor is saying:
> 100gb - live DB
> 100gb - last nights backup
> 100gb - to create tonights backup
> 100gb - extra needed to delete last nights backup after a successful
> backup
> --
> 400gb Total to perform the whole operation
> I just don't understand why that extra 100gb is needed.
> On Nov 28, 10:46 am, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
Showing posts with label file. Show all posts
Showing posts with label file. Show all posts
Thursday, March 29, 2012
Equal disk space needed to delete .bak file?
Kind of an obscure question, but here goes.
SQL2000 SP4
I have a E: drive on my SQL server that is ~400gb. On it you'll find
a ~100gb live DB file and last night's 100gb .bak file (maintenance
plan is set for one day retention). The vendor is telling me that I
am going to run out of space doing the SQL backups because 100gb is
used by the live DB, 100gb is used by last nights .bak file, 100gb
will be used to write today's .bak file, and the last 100gb will be
used in the deletion process of removing the old .bak file.
I can't say I know how SQL handles the removal of the old .bak file
but is this a true statement that SQL will need equal free space to
delete the old .bak file?SQL deletes old backups AFTER creating new ones, so you will need space for
at least two backups.
Look at it this way, what happens if your database blows up during a backup.
If you have an older backup, you are fine. If you are overwriting your only
backup, it is time to polish up the resume.
Personally, I would go out and buy a couple of USB drives and back up to
there. Last week my mother purchased a 500GB model for $99. If that is not
an option, you could look into one of the commercially available backup
compression tools. The three major ones are SQLSafe (www.idera.com),
LiteSpeed for SQL (www.quest.com), and SQL Backup (www.red-gate.com).
--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
<rockemhard@.gmail.com> wrote in message
news:04b97215-0ec7-4545-a43b-f072fb3c47a2@.e6g2000prf.googlegroups.com...
> Kind of an obscure question, but here goes.
> SQL2000 SP4
> I have a E: drive on my SQL server that is ~400gb. On it you'll find
> a ~100gb live DB file and last night's 100gb .bak file (maintenance
> plan is set for one day retention). The vendor is telling me that I
> am going to run out of space doing the SQL backups because 100gb is
> used by the live DB, 100gb is used by last nights .bak file, 100gb
> will be used to write today's .bak file, and the last 100gb will be
> used in the deletion process of removing the old .bak file.
> I can't say I know how SQL handles the removal of the old .bak file
> but is this a true statement that SQL will need equal free space to
> delete the old .bak file?|||Right, I aggree. In your scenario I need 300gb, not 400gb as the
vendor claims.
100gb - live DB
100gb - last nights backup
100gb - to create tonights backup
--
300gb Total to perform the whole operation
Vendor is saying:
100gb - live DB
100gb - last nights backup
100gb - to create tonights backup
100gb - extra needed to delete last nights backup after a successful
backup
--
400gb Total to perform the whole operation
I just don't understand why that extra 100gb is needed.
On Nov 28, 10:46 am, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
> SQL deletes old backups AFTER creating new ones, so you will need space for
> at least two backups.
> Look at it this way, what happens if your database blows up during a backup.
> If you have an older backup, you are fine. If you are overwriting your only
> backup, it is time to polish up the resume.|||Also, a backup on the same disk as the primary is pretty useless when you
think about it.
--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
<rockemhard@.gmail.com> wrote in message
news:b1987afa-2fde-4bcc-9e25-4d2632f7c009@.j44g2000hsj.googlegroups.com...
> Right, I aggree. In your scenario I need 300gb, not 400gb as the
> vendor claims.
> 100gb - live DB
> 100gb - last nights backup
> 100gb - to create tonights backup
> --
> 300gb Total to perform the whole operation
>
> Vendor is saying:
> 100gb - live DB
> 100gb - last nights backup
> 100gb - to create tonights backup
> 100gb - extra needed to delete last nights backup after a successful
> backup
> --
> 400gb Total to perform the whole operation
> I just don't understand why that extra 100gb is needed.
> On Nov 28, 10:46 am, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
>> SQL deletes old backups AFTER creating new ones, so you will need space
>> for
>> at least two backups.
>> Look at it this way, what happens if your database blows up during a
>> backup.
>> If you have an older backup, you are fine. If you are overwriting your
>> only
>> backup, it is time to polish up the resume.|||Only if it's not getting written to tape ;)
On Nov 28, 11:28 am, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
> Also, a backup on the same disk as the primary is pretty useless when you
> think about it.|||I've never seen Windows needing temp storage in order to delete a file. Perhaps your vendor somehow
confuses the windows Recycle Bin functionality somehow...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<rockemhard@.gmail.com> wrote in message
news:b1987afa-2fde-4bcc-9e25-4d2632f7c009@.j44g2000hsj.googlegroups.com...
> Right, I aggree. In your scenario I need 300gb, not 400gb as the
> vendor claims.
> 100gb - live DB
> 100gb - last nights backup
> 100gb - to create tonights backup
> --
> 300gb Total to perform the whole operation
>
> Vendor is saying:
> 100gb - live DB
> 100gb - last nights backup
> 100gb - to create tonights backup
> 100gb - extra needed to delete last nights backup after a successful
> backup
> --
> 400gb Total to perform the whole operation
> I just don't understand why that extra 100gb is needed.
> On Nov 28, 10:46 am, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
>> SQL deletes old backups AFTER creating new ones, so you will need space for
>> at least two backups.
>> Look at it this way, what happens if your database blows up during a backup.
>> If you have an older backup, you are fine. If you are overwriting your only
>> backup, it is time to polish up the resume.sql
SQL2000 SP4
I have a E: drive on my SQL server that is ~400gb. On it you'll find
a ~100gb live DB file and last night's 100gb .bak file (maintenance
plan is set for one day retention). The vendor is telling me that I
am going to run out of space doing the SQL backups because 100gb is
used by the live DB, 100gb is used by last nights .bak file, 100gb
will be used to write today's .bak file, and the last 100gb will be
used in the deletion process of removing the old .bak file.
I can't say I know how SQL handles the removal of the old .bak file
but is this a true statement that SQL will need equal free space to
delete the old .bak file?SQL deletes old backups AFTER creating new ones, so you will need space for
at least two backups.
Look at it this way, what happens if your database blows up during a backup.
If you have an older backup, you are fine. If you are overwriting your only
backup, it is time to polish up the resume.
Personally, I would go out and buy a couple of USB drives and back up to
there. Last week my mother purchased a 500GB model for $99. If that is not
an option, you could look into one of the commercially available backup
compression tools. The three major ones are SQLSafe (www.idera.com),
LiteSpeed for SQL (www.quest.com), and SQL Backup (www.red-gate.com).
--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
<rockemhard@.gmail.com> wrote in message
news:04b97215-0ec7-4545-a43b-f072fb3c47a2@.e6g2000prf.googlegroups.com...
> Kind of an obscure question, but here goes.
> SQL2000 SP4
> I have a E: drive on my SQL server that is ~400gb. On it you'll find
> a ~100gb live DB file and last night's 100gb .bak file (maintenance
> plan is set for one day retention). The vendor is telling me that I
> am going to run out of space doing the SQL backups because 100gb is
> used by the live DB, 100gb is used by last nights .bak file, 100gb
> will be used to write today's .bak file, and the last 100gb will be
> used in the deletion process of removing the old .bak file.
> I can't say I know how SQL handles the removal of the old .bak file
> but is this a true statement that SQL will need equal free space to
> delete the old .bak file?|||Right, I aggree. In your scenario I need 300gb, not 400gb as the
vendor claims.
100gb - live DB
100gb - last nights backup
100gb - to create tonights backup
--
300gb Total to perform the whole operation
Vendor is saying:
100gb - live DB
100gb - last nights backup
100gb - to create tonights backup
100gb - extra needed to delete last nights backup after a successful
backup
--
400gb Total to perform the whole operation
I just don't understand why that extra 100gb is needed.
On Nov 28, 10:46 am, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
> SQL deletes old backups AFTER creating new ones, so you will need space for
> at least two backups.
> Look at it this way, what happens if your database blows up during a backup.
> If you have an older backup, you are fine. If you are overwriting your only
> backup, it is time to polish up the resume.|||Also, a backup on the same disk as the primary is pretty useless when you
think about it.
--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
<rockemhard@.gmail.com> wrote in message
news:b1987afa-2fde-4bcc-9e25-4d2632f7c009@.j44g2000hsj.googlegroups.com...
> Right, I aggree. In your scenario I need 300gb, not 400gb as the
> vendor claims.
> 100gb - live DB
> 100gb - last nights backup
> 100gb - to create tonights backup
> --
> 300gb Total to perform the whole operation
>
> Vendor is saying:
> 100gb - live DB
> 100gb - last nights backup
> 100gb - to create tonights backup
> 100gb - extra needed to delete last nights backup after a successful
> backup
> --
> 400gb Total to perform the whole operation
> I just don't understand why that extra 100gb is needed.
> On Nov 28, 10:46 am, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
>> SQL deletes old backups AFTER creating new ones, so you will need space
>> for
>> at least two backups.
>> Look at it this way, what happens if your database blows up during a
>> backup.
>> If you have an older backup, you are fine. If you are overwriting your
>> only
>> backup, it is time to polish up the resume.|||Only if it's not getting written to tape ;)
On Nov 28, 11:28 am, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
> Also, a backup on the same disk as the primary is pretty useless when you
> think about it.|||I've never seen Windows needing temp storage in order to delete a file. Perhaps your vendor somehow
confuses the windows Recycle Bin functionality somehow...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<rockemhard@.gmail.com> wrote in message
news:b1987afa-2fde-4bcc-9e25-4d2632f7c009@.j44g2000hsj.googlegroups.com...
> Right, I aggree. In your scenario I need 300gb, not 400gb as the
> vendor claims.
> 100gb - live DB
> 100gb - last nights backup
> 100gb - to create tonights backup
> --
> 300gb Total to perform the whole operation
>
> Vendor is saying:
> 100gb - live DB
> 100gb - last nights backup
> 100gb - to create tonights backup
> 100gb - extra needed to delete last nights backup after a successful
> backup
> --
> 400gb Total to perform the whole operation
> I just don't understand why that extra 100gb is needed.
> On Nov 28, 10:46 am, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
>> SQL deletes old backups AFTER creating new ones, so you will need space for
>> at least two backups.
>> Look at it this way, what happens if your database blows up during a backup.
>> If you have an older backup, you are fine. If you are overwriting your only
>> backup, it is time to polish up the resume.sql
EOF (end of file)
Hi! Is there an equivalent EOF function in Crystal Reports 8.5.?
I want to use a Do While Loop, but dont know the number of records so
I want to use the EOF so it will terminate upon reaching the end of the
file.
Thanks.you can have RECORD COUNT so based on that number you can specify total number of loops you will require in report
I want to use a Do While Loop, but dont know the number of records so
I want to use the EOF so it will terminate upon reaching the end of the
file.
Thanks.you can have RECORD COUNT so based on that number you can specify total number of loops you will require in report
Thursday, March 22, 2012
Enterprise Manger Error
I am getting an error:
MMC cannot open the file C:\program files\Miscorosft SQL
Server\80\Tools\BINN\SQL Server Enterprise Manager.MSC.
This may be because the file does not exist, is not an MMC console, or was
creted by a later version of MMC. This may also by because you do not have
sufficient access rights to the file.
I've tried uninstalling/reinstalling reapplying SP3a etc. with no luck.
I did find that renaming the file to anything else will allow it to work.
Which makes for an easy enough work around but was wondering if anybody knew
what is going on?
TIA
Hi
Have you tried running MMC and opening the file from there?
Check the file permissions.
If you have EM on another machine you may want to try copying the file.
Alternatively may want to extract the MSC file from the original CD.
John
"Ken Rinaman" <go@.away.net> wrote in message
news:%23sPCyhiUEHA.2972@.TK2MSFTNGP12.phx.gbl...
> I am getting an error:
> MMC cannot open the file C:\program files\Miscorosft SQL
> Server\80\Tools\BINN\SQL Server Enterprise Manager.MSC.
> This may be because the file does not exist, is not an MMC console, or was
> creted by a later version of MMC. This may also by because you do not have
> sufficient access rights to the file.
> I've tried uninstalling/reinstalling reapplying SP3a etc. with no luck.
> I did find that renaming the file to anything else will allow it to work.
> Which makes for an easy enough work around but was wondering if anybody
knew
> what is going on?
> TIA
>
|||
> Have you tried running MMC and opening the file from there?
Yes, same error.
> Check the file permissions.
I have the ability to rename, delete, etc.
> If you have EM on another machine you may want to try copying the file.
> Alternatively may want to extract the MSC file from the original CD.
I did pull the file from the CD which is how I discovered changing the name
fixes the problem. On the CD the file is called SQLEM.msc if I copy that
file to my computer it runs fine. However if I rename it to SQL Server
Enterprise Manger.msc it no longer runs.
sql
MMC cannot open the file C:\program files\Miscorosft SQL
Server\80\Tools\BINN\SQL Server Enterprise Manager.MSC.
This may be because the file does not exist, is not an MMC console, or was
creted by a later version of MMC. This may also by because you do not have
sufficient access rights to the file.
I've tried uninstalling/reinstalling reapplying SP3a etc. with no luck.
I did find that renaming the file to anything else will allow it to work.
Which makes for an easy enough work around but was wondering if anybody knew
what is going on?
TIA
Hi
Have you tried running MMC and opening the file from there?
Check the file permissions.
If you have EM on another machine you may want to try copying the file.
Alternatively may want to extract the MSC file from the original CD.
John
"Ken Rinaman" <go@.away.net> wrote in message
news:%23sPCyhiUEHA.2972@.TK2MSFTNGP12.phx.gbl...
> I am getting an error:
> MMC cannot open the file C:\program files\Miscorosft SQL
> Server\80\Tools\BINN\SQL Server Enterprise Manager.MSC.
> This may be because the file does not exist, is not an MMC console, or was
> creted by a later version of MMC. This may also by because you do not have
> sufficient access rights to the file.
> I've tried uninstalling/reinstalling reapplying SP3a etc. with no luck.
> I did find that renaming the file to anything else will allow it to work.
> Which makes for an easy enough work around but was wondering if anybody
knew
> what is going on?
> TIA
>
|||
> Have you tried running MMC and opening the file from there?
Yes, same error.
> Check the file permissions.
I have the ability to rename, delete, etc.
> If you have EM on another machine you may want to try copying the file.
> Alternatively may want to extract the MSC file from the original CD.
I did pull the file from the CD which is how I discovered changing the name
fixes the problem. On the CD the file is called SQLEM.msc if I copy that
file to my computer it runs fine. However if I rename it to SQL Server
Enterprise Manger.msc it no longer runs.
sql
Wednesday, March 21, 2012
Enterprise Manager Won't Start
All of a sudden, whenever I try to start the SQL Server
Enterprise Manager, I get the following error:
MMC cannot open the file C:\Program File\...\SQL Server
Enterprise Manager.MSC.
This may be because the file does not exist, is not an
MMC console, or was created by a later version of MMC.
This may also be because you do not have sufficient
access rights to the file.
I've uninstalled and re-installed SQL Server at least
four times now. I still get the same error. What is
going on? The file exists. I can see it. Please, I
need some insight on this. Help!
Glenn,
Try reapplying the latest SQL Server 2000 service pack. If that doesn't
work try copying SQLEM.MSC from the SQL Server CD (remember to rename it
to Enterprise Manager.msc on your machine).
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Glenn Cadoret wrote:
> All of a sudden, whenever I try to start the SQL Server
> Enterprise Manager, I get the following error:
> MMC cannot open the file C:\Program File\...\SQL Server
> Enterprise Manager.MSC.
> This may be because the file does not exist, is not an
> MMC console, or was created by a later version of MMC.
> This may also be because you do not have sufficient
> access rights to the file.
> I've uninstalled and re-installed SQL Server at least
> four times now. I still get the same error. What is
> going on? The file exists. I can see it. Please, I
> need some insight on this. Help!
|||Still no success. I have:
1. Verified all of the file permissions.
2. Installed SP3a.
3. Copied the SQLEM.MSC file, renamed it.
I still get the same error.
Any other possibilities?
Glenn Cadoret
>--Original Message--
>Glenn,
>Try reapplying the latest SQL Server 2000 service pack.
If that doesn't
>work try copying SQLEM.MSC from the SQL Server CD
(remember to rename it[vbcol=seagreen]
>to Enterprise Manager.msc on your machine).
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>Glenn Cadoret wrote:
Server[vbcol=seagreen]
Server[vbcol=seagreen]
MMC.
>.
>
|||Glenn,
Well, it sounds like a permissions issue to me. What did you change? ;-)
Can you log on as local administrator and open EM?
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Glenn Cadoret wrote:[vbcol=seagreen]
> Still no success. I have:
> 1. Verified all of the file permissions.
> 2. Installed SP3a.
> 3. Copied the SQLEM.MSC file, renamed it.
> I still get the same error.
> Any other possibilities?
> Glenn Cadoret
>
>
> If that doesn't
>
> (remember to rename it
>
> Server
>
> Server
>
> MMC.
|||I had the same problem. When I replaced SQLEM.msc from the CD I tried to
launch it before renaming it and it worked fine but after I renamed it it
would not open.
As long as I dont rename it to its original name it will launch fine? If
this is a permissions issue then it is easily worked around by just renaming
the file. Not a lot of security here on permissions if that is all it takes
to work around the permissons.
"Mark Allison" wrote:
> Glenn,
> Well, it sounds like a permissions issue to me. What did you change? ;-)
> Can you log on as local administrator and open EM?
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Glenn Cadoret wrote:
>
Enterprise Manager, I get the following error:
MMC cannot open the file C:\Program File\...\SQL Server
Enterprise Manager.MSC.
This may be because the file does not exist, is not an
MMC console, or was created by a later version of MMC.
This may also be because you do not have sufficient
access rights to the file.
I've uninstalled and re-installed SQL Server at least
four times now. I still get the same error. What is
going on? The file exists. I can see it. Please, I
need some insight on this. Help!
Glenn,
Try reapplying the latest SQL Server 2000 service pack. If that doesn't
work try copying SQLEM.MSC from the SQL Server CD (remember to rename it
to Enterprise Manager.msc on your machine).
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Glenn Cadoret wrote:
> All of a sudden, whenever I try to start the SQL Server
> Enterprise Manager, I get the following error:
> MMC cannot open the file C:\Program File\...\SQL Server
> Enterprise Manager.MSC.
> This may be because the file does not exist, is not an
> MMC console, or was created by a later version of MMC.
> This may also be because you do not have sufficient
> access rights to the file.
> I've uninstalled and re-installed SQL Server at least
> four times now. I still get the same error. What is
> going on? The file exists. I can see it. Please, I
> need some insight on this. Help!
|||Still no success. I have:
1. Verified all of the file permissions.
2. Installed SP3a.
3. Copied the SQLEM.MSC file, renamed it.
I still get the same error.
Any other possibilities?
Glenn Cadoret
>--Original Message--
>Glenn,
>Try reapplying the latest SQL Server 2000 service pack.
If that doesn't
>work try copying SQLEM.MSC from the SQL Server CD
(remember to rename it[vbcol=seagreen]
>to Enterprise Manager.msc on your machine).
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>Glenn Cadoret wrote:
Server[vbcol=seagreen]
Server[vbcol=seagreen]
MMC.
>.
>
|||Glenn,
Well, it sounds like a permissions issue to me. What did you change? ;-)
Can you log on as local administrator and open EM?
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Glenn Cadoret wrote:[vbcol=seagreen]
> Still no success. I have:
> 1. Verified all of the file permissions.
> 2. Installed SP3a.
> 3. Copied the SQLEM.MSC file, renamed it.
> I still get the same error.
> Any other possibilities?
> Glenn Cadoret
>
>
> If that doesn't
>
> (remember to rename it
>
> Server
>
> Server
>
> MMC.
|||I had the same problem. When I replaced SQLEM.msc from the CD I tried to
launch it before renaming it and it worked fine but after I renamed it it
would not open.
As long as I dont rename it to its original name it will launch fine? If
this is a permissions issue then it is easily worked around by just renaming
the file. Not a lot of security here on permissions if that is all it takes
to work around the permissons.
"Mark Allison" wrote:
> Glenn,
> Well, it sounds like a permissions issue to me. What did you change? ;-)
> Can you log on as local administrator and open EM?
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Glenn Cadoret wrote:
>
Enterprise Manager Won't Start
All of a sudden, whenever I try to start the SQL Server
Enterprise Manager, I get the following error:
MMC cannot open the file C:\Program File\...\SQL Server
Enterprise Manager.MSC.
This may be because the file does not exist, is not an
MMC console, or was created by a later version of MMC.
This may also be because you do not have sufficient
access rights to the file.
I've uninstalled and re-installed SQL Server at least
four times now. I still get the same error. What is
going on? The file exists. I can see it. Please, I
need some insight on this. Help!Does the account SQL Server is using have rights to the
directory? that would be my first guess
>--Original Message--
>All of a sudden, whenever I try to start the SQL Server
>Enterprise Manager, I get the following error:
>MMC cannot open the file C:\Program File\...\SQL Server
>Enterprise Manager.MSC.
>This may be because the file does not exist, is not an
>MMC console, or was created by a later version of MMC.
>This may also be because you do not have sufficient
>access rights to the file.
>I've uninstalled and re-installed SQL Server at least
>four times now. I still get the same error. What is
>going on? The file exists. I can see it. Please, I
>need some insight on this. Help!
>.
>|||Glenn,
Try reapplying the latest SQL Server 2000 service pack. If that doesn't
work try copying SQLEM.MSC from the SQL Server CD (remember to rename it
to Enterprise Manager.msc on your machine).
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Glenn Cadoret wrote:
> All of a sudden, whenever I try to start the SQL Server
> Enterprise Manager, I get the following error:
> MMC cannot open the file C:\Program File\...\SQL Server
> Enterprise Manager.MSC.
> This may be because the file does not exist, is not an
> MMC console, or was created by a later version of MMC.
> This may also be because you do not have sufficient
> access rights to the file.
> I've uninstalled and re-installed SQL Server at least
> four times now. I still get the same error. What is
> going on? The file exists. I can see it. Please, I
> need some insight on this. Help!|||Still no success. I have:
1. Verified all of the file permissions.
2. Installed SP3a.
3. Copied the SQLEM.MSC file, renamed it.
I still get the same error.
Any other possibilities?
Glenn Cadoret
>--Original Message--
>Glenn,
>Try reapplying the latest SQL Server 2000 service pack.
If that doesn't
>work try copying SQLEM.MSC from the SQL Server CD
(remember to rename it
>to Enterprise Manager.msc on your machine).
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>Glenn Cadoret wrote:
>> All of a sudden, whenever I try to start the SQL
Server
>> Enterprise Manager, I get the following error:
>> MMC cannot open the file C:\Program File\...\SQL
Server
>> Enterprise Manager.MSC.
>> This may be because the file does not exist, is not an
>> MMC console, or was created by a later version of
MMC.
>> This may also be because you do not have sufficient
>> access rights to the file.
>> I've uninstalled and re-installed SQL Server at least
>> four times now. I still get the same error. What is
>> going on? The file exists. I can see it. Please, I
>> need some insight on this. Help!
>.
>|||Glenn,
Well, it sounds like a permissions issue to me. What did you change? ;-)
Can you log on as local administrator and open EM?
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Glenn Cadoret wrote:
> Still no success. I have:
> 1. Verified all of the file permissions.
> 2. Installed SP3a.
> 3. Copied the SQLEM.MSC file, renamed it.
> I still get the same error.
> Any other possibilities?
> Glenn Cadoret
>
>>--Original Message--
>>Glenn,
>>Try reapplying the latest SQL Server 2000 service pack.
> If that doesn't
>>work try copying SQLEM.MSC from the SQL Server CD
> (remember to rename it
>>to Enterprise Manager.msc on your machine).
>>--
>>Mark Allison, SQL Server MVP
>>http://www.markallison.co.uk
>>Looking for a SQL Server replication book?
>>http://www.nwsu.com/0974973602.html
>>
>>Glenn Cadoret wrote:
>>All of a sudden, whenever I try to start the SQL
> Server
>>Enterprise Manager, I get the following error:
>>MMC cannot open the file C:\Program File\...\SQL
> Server
>>Enterprise Manager.MSC.
>>This may be because the file does not exist, is not an
>>MMC console, or was created by a later version of
> MMC.
>>This may also be because you do not have sufficient
>>access rights to the file.
>>I've uninstalled and re-installed SQL Server at least
>>four times now. I still get the same error. What is
>>going on? The file exists. I can see it. Please, I
>>need some insight on this. Help!
>>.sql
Enterprise Manager, I get the following error:
MMC cannot open the file C:\Program File\...\SQL Server
Enterprise Manager.MSC.
This may be because the file does not exist, is not an
MMC console, or was created by a later version of MMC.
This may also be because you do not have sufficient
access rights to the file.
I've uninstalled and re-installed SQL Server at least
four times now. I still get the same error. What is
going on? The file exists. I can see it. Please, I
need some insight on this. Help!Does the account SQL Server is using have rights to the
directory? that would be my first guess
>--Original Message--
>All of a sudden, whenever I try to start the SQL Server
>Enterprise Manager, I get the following error:
>MMC cannot open the file C:\Program File\...\SQL Server
>Enterprise Manager.MSC.
>This may be because the file does not exist, is not an
>MMC console, or was created by a later version of MMC.
>This may also be because you do not have sufficient
>access rights to the file.
>I've uninstalled and re-installed SQL Server at least
>four times now. I still get the same error. What is
>going on? The file exists. I can see it. Please, I
>need some insight on this. Help!
>.
>|||Glenn,
Try reapplying the latest SQL Server 2000 service pack. If that doesn't
work try copying SQLEM.MSC from the SQL Server CD (remember to rename it
to Enterprise Manager.msc on your machine).
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Glenn Cadoret wrote:
> All of a sudden, whenever I try to start the SQL Server
> Enterprise Manager, I get the following error:
> MMC cannot open the file C:\Program File\...\SQL Server
> Enterprise Manager.MSC.
> This may be because the file does not exist, is not an
> MMC console, or was created by a later version of MMC.
> This may also be because you do not have sufficient
> access rights to the file.
> I've uninstalled and re-installed SQL Server at least
> four times now. I still get the same error. What is
> going on? The file exists. I can see it. Please, I
> need some insight on this. Help!|||Still no success. I have:
1. Verified all of the file permissions.
2. Installed SP3a.
3. Copied the SQLEM.MSC file, renamed it.
I still get the same error.
Any other possibilities?
Glenn Cadoret
>--Original Message--
>Glenn,
>Try reapplying the latest SQL Server 2000 service pack.
If that doesn't
>work try copying SQLEM.MSC from the SQL Server CD
(remember to rename it
>to Enterprise Manager.msc on your machine).
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>Glenn Cadoret wrote:
>> All of a sudden, whenever I try to start the SQL
Server
>> Enterprise Manager, I get the following error:
>> MMC cannot open the file C:\Program File\...\SQL
Server
>> Enterprise Manager.MSC.
>> This may be because the file does not exist, is not an
>> MMC console, or was created by a later version of
MMC.
>> This may also be because you do not have sufficient
>> access rights to the file.
>> I've uninstalled and re-installed SQL Server at least
>> four times now. I still get the same error. What is
>> going on? The file exists. I can see it. Please, I
>> need some insight on this. Help!
>.
>|||Glenn,
Well, it sounds like a permissions issue to me. What did you change? ;-)
Can you log on as local administrator and open EM?
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Glenn Cadoret wrote:
> Still no success. I have:
> 1. Verified all of the file permissions.
> 2. Installed SP3a.
> 3. Copied the SQLEM.MSC file, renamed it.
> I still get the same error.
> Any other possibilities?
> Glenn Cadoret
>
>>--Original Message--
>>Glenn,
>>Try reapplying the latest SQL Server 2000 service pack.
> If that doesn't
>>work try copying SQLEM.MSC from the SQL Server CD
> (remember to rename it
>>to Enterprise Manager.msc on your machine).
>>--
>>Mark Allison, SQL Server MVP
>>http://www.markallison.co.uk
>>Looking for a SQL Server replication book?
>>http://www.nwsu.com/0974973602.html
>>
>>Glenn Cadoret wrote:
>>All of a sudden, whenever I try to start the SQL
> Server
>>Enterprise Manager, I get the following error:
>>MMC cannot open the file C:\Program File\...\SQL
> Server
>>Enterprise Manager.MSC.
>>This may be because the file does not exist, is not an
>>MMC console, or was created by a later version of
> MMC.
>>This may also be because you do not have sufficient
>>access rights to the file.
>>I've uninstalled and re-installed SQL Server at least
>>four times now. I still get the same error. What is
>>going on? The file exists. I can see it. Please, I
>>need some insight on this. Help!
>>.sql
Enterprise Manager Won't Start
All of a sudden, whenever I try to start the SQL Server
Enterprise Manager, I get the following error:
MMC cannot open the file C:\Program File\...\SQL Server
Enterprise Manager.MSC.
This may be because the file does not exist, is not an
MMC console, or was created by a later version of MMC.
This may also be because you do not have sufficient
access rights to the file.
I've uninstalled and re-installed SQL Server at least
four times now. I still get the same error. What is
going on? The file exists. I can see it. Please, I
need some insight on this. Help!Glenn,
Try reapplying the latest SQL Server 2000 service pack. If that doesn't
work try copying SQLEM.MSC from the SQL Server CD (remember to rename it
to Enterprise Manager.msc on your machine).
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Glenn Cadoret wrote:
> All of a sudden, whenever I try to start the SQL Server
> Enterprise Manager, I get the following error:
> MMC cannot open the file C:\Program File\...\SQL Server
> Enterprise Manager.MSC.
> This may be because the file does not exist, is not an
> MMC console, or was created by a later version of MMC.
> This may also be because you do not have sufficient
> access rights to the file.
> I've uninstalled and re-installed SQL Server at least
> four times now. I still get the same error. What is
> going on? The file exists. I can see it. Please, I
> need some insight on this. Help!|||Still no success. I have:
1. Verified all of the file permissions.
2. Installed SP3a.
3. Copied the SQLEM.MSC file, renamed it.
I still get the same error.
Any other possibilities?
Glenn Cadoret
>--Original Message--
>Glenn,
>Try reapplying the latest SQL Server 2000 service pack.
If that doesn't
>work try copying SQLEM.MSC from the SQL Server CD
(remember to rename it
>to Enterprise Manager.msc on your machine).
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>Glenn Cadoret wrote:
Server[vbcol=seagreen]
Server[vbcol=seagreen]
MMC.[vbcol=seagreen]
>.
>|||Glenn,
Well, it sounds like a permissions issue to me. What did you change? ;-)
Can you log on as local administrator and open EM?
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Glenn Cadoret wrote:[vbcol=seagreen]
> Still no success. I have:
> 1. Verified all of the file permissions.
> 2. Installed SP3a.
> 3. Copied the SQLEM.MSC file, renamed it.
> I still get the same error.
> Any other possibilities?
> Glenn Cadoret
>
>
> If that doesn't
>
> (remember to rename it
>
> Server
>
> Server
>
> MMC.
>|||I had the same problem. When I replaced SQLEM.msc from the CD I tried to
launch it before renaming it and it worked fine but after I renamed it it
would not open.
As long as I dont rename it to its original name it will launch fine? If
this is a permissions issue then it is easily worked around by just renaming
the file. Not a lot of security here on permissions if that is all it takes
to work around the permissons.
"Mark Allison" wrote:
> Glenn,
> Well, it sounds like a permissions issue to me. What did you change? ;-)
> Can you log on as local administrator and open EM?
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Glenn Cadoret wrote:
>
Enterprise Manager, I get the following error:
MMC cannot open the file C:\Program File\...\SQL Server
Enterprise Manager.MSC.
This may be because the file does not exist, is not an
MMC console, or was created by a later version of MMC.
This may also be because you do not have sufficient
access rights to the file.
I've uninstalled and re-installed SQL Server at least
four times now. I still get the same error. What is
going on? The file exists. I can see it. Please, I
need some insight on this. Help!Glenn,
Try reapplying the latest SQL Server 2000 service pack. If that doesn't
work try copying SQLEM.MSC from the SQL Server CD (remember to rename it
to Enterprise Manager.msc on your machine).
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Glenn Cadoret wrote:
> All of a sudden, whenever I try to start the SQL Server
> Enterprise Manager, I get the following error:
> MMC cannot open the file C:\Program File\...\SQL Server
> Enterprise Manager.MSC.
> This may be because the file does not exist, is not an
> MMC console, or was created by a later version of MMC.
> This may also be because you do not have sufficient
> access rights to the file.
> I've uninstalled and re-installed SQL Server at least
> four times now. I still get the same error. What is
> going on? The file exists. I can see it. Please, I
> need some insight on this. Help!|||Still no success. I have:
1. Verified all of the file permissions.
2. Installed SP3a.
3. Copied the SQLEM.MSC file, renamed it.
I still get the same error.
Any other possibilities?
Glenn Cadoret
>--Original Message--
>Glenn,
>Try reapplying the latest SQL Server 2000 service pack.
If that doesn't
>work try copying SQLEM.MSC from the SQL Server CD
(remember to rename it
>to Enterprise Manager.msc on your machine).
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>Glenn Cadoret wrote:
Server[vbcol=seagreen]
Server[vbcol=seagreen]
MMC.[vbcol=seagreen]
>.
>|||Glenn,
Well, it sounds like a permissions issue to me. What did you change? ;-)
Can you log on as local administrator and open EM?
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Glenn Cadoret wrote:[vbcol=seagreen]
> Still no success. I have:
> 1. Verified all of the file permissions.
> 2. Installed SP3a.
> 3. Copied the SQLEM.MSC file, renamed it.
> I still get the same error.
> Any other possibilities?
> Glenn Cadoret
>
>
> If that doesn't
>
> (remember to rename it
>
> Server
>
> Server
>
> MMC.
>|||I had the same problem. When I replaced SQLEM.msc from the CD I tried to
launch it before renaming it and it worked fine but after I renamed it it
would not open.
As long as I dont rename it to its original name it will launch fine? If
this is a permissions issue then it is easily worked around by just renaming
the file. Not a lot of security here on permissions if that is all it takes
to work around the permissons.
"Mark Allison" wrote:
> Glenn,
> Well, it sounds like a permissions issue to me. What did you change? ;-)
> Can you log on as local administrator and open EM?
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Glenn Cadoret wrote:
>
Monday, March 19, 2012
Enterprise manager running a BAT file
I wish to use Enterprise manager to run a batch file that the program
displays a window, but there is no user input for it. If I run the command
job it runs fine, If I use E.M to run it the job starts and looks like it
hangs and does nothing. Any ideas?
Jay
The GUI that is called runs in the context of a service. It will not be
visible on the screen. Re-write the application so that it is without a GUI
and things should work better.
Keith
"Jay" <Jay@.discussions.microsoft.com> wrote in message
news:47313383-F298-4B62-9597-CADE32CDCBE3@.microsoft.com...
>I wish to use Enterprise manager to run a batch file that the program
> displays a window, but there is no user input for it. If I run the
> command
> job it runs fine, If I use E.M to run it the job starts and looks like it
> hangs and does nothing. Any ideas?
> Jay
displays a window, but there is no user input for it. If I run the command
job it runs fine, If I use E.M to run it the job starts and looks like it
hangs and does nothing. Any ideas?
Jay
The GUI that is called runs in the context of a service. It will not be
visible on the screen. Re-write the application so that it is without a GUI
and things should work better.
Keith
"Jay" <Jay@.discussions.microsoft.com> wrote in message
news:47313383-F298-4B62-9597-CADE32CDCBE3@.microsoft.com...
>I wish to use Enterprise manager to run a batch file that the program
> displays a window, but there is no user input for it. If I run the
> command
> job it runs fine, If I use E.M to run it the job starts and looks like it
> hangs and does nothing. Any ideas?
> Jay
Friday, March 9, 2012
Enterprise Manager launch error
Not sure what has caused this to suddenly happen, but each time I attempt to launch Enterprise Manager I get the error:
"MMC cannot open the file C:\MSSQL\BINN\SQL Server Enterprises Manager.MSC
This may be because the file does not exist, is not an MMC console, or was created by a later version of MMC. This may also be because you do not have sufficient access rights to the file."
Now, I've already attempted to reinstall the client tools with no luck. The file does exist, and I have not changed my security settings -- at least that I'm aware of.
I use EM daily, so I'm perplexed as to why over night it stopped working. Is it possible a Windows Update could have caused this?
If you have any insight I'd appreciate it. Thanks.
PS. I'm using SQL 7.0 on a WinXP Pro laptop.
DavidI feel there could be some issue with h/w on the box and may refer to this KBA http://support.microsoft.com/default.aspx?scid=kb;en-us;315341 to fix it.
Ensure to obtain latest service pack for XP also, if nothing works reinstall from scratch.
"MMC cannot open the file C:\MSSQL\BINN\SQL Server Enterprises Manager.MSC
This may be because the file does not exist, is not an MMC console, or was created by a later version of MMC. This may also be because you do not have sufficient access rights to the file."
Now, I've already attempted to reinstall the client tools with no luck. The file does exist, and I have not changed my security settings -- at least that I'm aware of.
I use EM daily, so I'm perplexed as to why over night it stopped working. Is it possible a Windows Update could have caused this?
If you have any insight I'd appreciate it. Thanks.
PS. I'm using SQL 7.0 on a WinXP Pro laptop.
DavidI feel there could be some issue with h/w on the box and may refer to this KBA http://support.microsoft.com/default.aspx?scid=kb;en-us;315341 to fix it.
Ensure to obtain latest service pack for XP also, if nothing works reinstall from scratch.
Subscribe to:
Posts (Atom)