On one node of a cluster I have I began getting this message today after a
failover. How do I resolve? I've tried copying SQLEM.msc and replacing it
an it in 80\tools\binn but it still doesn't work. This is the exact error
message:
Snap-in failed to initialize
Name: Microsoft SQL Enterprise Manager
Clsid: {0100100-1816-11D0-8EF5-00AA0062C8F}See this KB Article. it may helpful
http://support.microsoft.com/?kbid=297064
Petchikumar
"Cathy Soloway" wrote:
> On one node of a cluster I have I began getting this message today after a
> failover. How do I resolve? I've tried copying SQLEM.msc and replacing i
t
> an it in 80\tools\binn but it still doesn't work. This is the exact error
> message:
> Snap-in failed to initialize
> Name: Microsoft SQL Enterprise Manager
> Clsid: {0100100-1816-11D0-8EF5-00AA0062C8F}
>|||That didn't work either. I called support and they walked me through
checking out all the DLLs and functionality and finally suggested we do a
re-boot. Will try that over the weekend. Thanks for the response, though.
"Petchikumar" wrote:
[vbcol=seagreen]
> See this KB Article. it may helpful
> http://support.microsoft.com/?kbid=297064
>
> Petchikumar
>
> "Cathy Soloway" wrote:
>
Showing posts with label failed. Show all posts
Showing posts with label failed. Show all posts
Wednesday, March 21, 2012
Enterprise Manager won't work - "snap-in failed to initialize"
On one node of a cluster I have I began getting this message today after a
failover. How do I resolve? I've tried copying SQLEM.msc and replacing it
an it in 80\tools\binn but it still doesn't work. This is the exact error
message:
Snap-in failed to initialize
Name: Microsoft SQL Enterprise Manager
Clsid: {0100100-1816-11D0-8EF5-00AA0062C8F}See this KB Article. it may helpful
http://support.microsoft.com/?kbid=297064
Petchikumar
"Cathy Soloway" wrote:
> On one node of a cluster I have I began getting this message today after a
> failover. How do I resolve? I've tried copying SQLEM.msc and replacing it
> an it in 80\tools\binn but it still doesn't work. This is the exact error
> message:
> Snap-in failed to initialize
> Name: Microsoft SQL Enterprise Manager
> Clsid: {0100100-1816-11D0-8EF5-00AA0062C8F}
>|||That didn't work either. I called support and they walked me through
checking out all the DLLs and functionality and finally suggested we do a
re-boot. Will try that over the weekend. Thanks for the response, though.
"Petchikumar" wrote:
> See this KB Article. it may helpful
> http://support.microsoft.com/?kbid=297064
>
> Petchikumar
>
> "Cathy Soloway" wrote:
> > On one node of a cluster I have I began getting this message today after a
> > failover. How do I resolve? I've tried copying SQLEM.msc and replacing it
> > an it in 80\tools\binn but it still doesn't work. This is the exact error
> > message:
> >
> > Snap-in failed to initialize
> > Name: Microsoft SQL Enterprise Manager
> > Clsid: {0100100-1816-11D0-8EF5-00AA0062C8F}
> >
failover. How do I resolve? I've tried copying SQLEM.msc and replacing it
an it in 80\tools\binn but it still doesn't work. This is the exact error
message:
Snap-in failed to initialize
Name: Microsoft SQL Enterprise Manager
Clsid: {0100100-1816-11D0-8EF5-00AA0062C8F}See this KB Article. it may helpful
http://support.microsoft.com/?kbid=297064
Petchikumar
"Cathy Soloway" wrote:
> On one node of a cluster I have I began getting this message today after a
> failover. How do I resolve? I've tried copying SQLEM.msc and replacing it
> an it in 80\tools\binn but it still doesn't work. This is the exact error
> message:
> Snap-in failed to initialize
> Name: Microsoft SQL Enterprise Manager
> Clsid: {0100100-1816-11D0-8EF5-00AA0062C8F}
>|||That didn't work either. I called support and they walked me through
checking out all the DLLs and functionality and finally suggested we do a
re-boot. Will try that over the weekend. Thanks for the response, though.
"Petchikumar" wrote:
> See this KB Article. it may helpful
> http://support.microsoft.com/?kbid=297064
>
> Petchikumar
>
> "Cathy Soloway" wrote:
> > On one node of a cluster I have I began getting this message today after a
> > failover. How do I resolve? I've tried copying SQLEM.msc and replacing it
> > an it in 80\tools\binn but it still doesn't work. This is the exact error
> > message:
> >
> > Snap-in failed to initialize
> > Name: Microsoft SQL Enterprise Manager
> > Clsid: {0100100-1816-11D0-8EF5-00AA0062C8F}
> >
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
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?
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?
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?
Sunday, March 11, 2012
Enterprise Manager Problem
Snap-i failed to initialize.
Name:Microsoft SQL Enterprise Manager
CLSID:{00100100-1816-11D0-8EF5-00AA0062C58F}
I unintsalled and reinstalled EM with no luck.:confused:Try the latest version of mdac.
Name:Microsoft SQL Enterprise Manager
CLSID:{00100100-1816-11D0-8EF5-00AA0062C58F}
I unintsalled and reinstalled EM with no luck.:confused:Try the latest version of mdac.
Sunday, February 26, 2012
Enterprise Manager confusion
Ok i know that the main reason for the error that contains
System.Data.OleDb.OleDbException: Login failed for user 'BEDROOM\ASPNET'.
is because i do not have the ASPNET registered.
From what i have been told i need Enterprise Manager.
I HAVE NO CLUE WHERE TO GET IT OR HOW TO CONFIGURE IT OR ANYTHING OF IT
sorry for the caps.
I have search on here and google and nothing
any help
thanks
It is not a stand alone product, it is part of SQL Server 2000, try the link below to test drive the full version of SQL Server. Hope this helps.
http://www.microsoft.com/sql/evaluation/trial/default.mspx|||
Inthis previous threadyou said you already had Enterprise Manager. Sorry I didn'tfollow up with your question there, the open source part of yourresponse confused me and I forgot to respond.
You do notneed Enterprise Manager. You can perform the needed commands from the command line using the osql utility.
You might findHow To Manage the SQL Server Desktop Engine (MSDE 2000) by Using the Osql Utility to be helpful. In an osql session you will need to execute these commands:
|||BEAUTIFUL!!!!!
Thanks. Everything is up and operational
System.Data.OleDb.OleDbException: Login failed for user 'BEDROOM\ASPNET'.
is because i do not have the ASPNET registered.
From what i have been told i need Enterprise Manager.
I HAVE NO CLUE WHERE TO GET IT OR HOW TO CONFIGURE IT OR ANYTHING OF IT
sorry for the caps.
I have search on here and google and nothing
any help
thanks
It is not a stand alone product, it is part of SQL Server 2000, try the link below to test drive the full version of SQL Server. Hope this helps.
http://www.microsoft.com/sql/evaluation/trial/default.mspx|||
base836ball wrote:
Ok i know that the main reason for the error that contains
System.Data.OleDb.OleDbException: Login failed for user 'BEDROOM\ASPNET'.
is because i do not have the ASPNET registered.
From what i have been told i need Enterprise Manager.
I HAVE NO CLUE WHERE TO GET IT OR HOW TO CONFIGURE IT OR ANYTHING OF IT
sorry for the caps.
I have search on here and google and nothing
any help
thanks
Inthis previous threadyou said you already had Enterprise Manager. Sorry I didn'tfollow up with your question there, the open source part of yourresponse confused me and I forgot to respond.
You do notneed Enterprise Manager. You can perform the needed commands from the command line using the osql utility.
You might findHow To Manage the SQL Server Desktop Engine (MSDE 2000) by Using the Osql Utility to be helpful. In an osql session you will need to execute these commands:
EXEC sp_grantlogin 'BEDROOM\ASPNET'Seethis post andthis post for more step-by-step instructions that I've given in the past.
GO
USE yourDatabase
GO
EXEC sp_grantdbaccess 'BEDROOM\ASPNET', 'ASPNET'
GO
|||BEAUTIFUL!!!!!
Thanks. Everything is up and operational
Subscribe to:
Posts (Atom)