Showing posts with label enterprise. Show all posts
Showing posts with label enterprise. Show all posts

Tuesday, March 27, 2012

Cannot register server

I am working on a LAN with 3 servers, VED, PM, JF
In Enterprise manager, from server PM, I registered server VED but
cannot register server JF. I see it in the list of proposed server, but
when I enter the SQL user code and password, an error message tells me
that server cannot be registered because of time out. But I tried that
last week and everything worked properly. I have been told that nothing
had been changed.
Looking forward to receiving some feedback on the above.
Regards
Patrick
A few things to try :-
Can you ping server JF
Is it listening on the default port 1433, use telnet to establish
Is SQL Server running on server JF or has the service been stopped
HTH. Ryan
"Patrick" <pmenage@.intnet.mu> wrote in message
news:1137472586.261082.252830@.o13g2000cwo.googlegr oups.com...
>I am working on a LAN with 3 servers, VED, PM, JF
> In Enterprise manager, from server PM, I registered server VED but
> cannot register server JF. I see it in the list of proposed server, but
> when I enter the SQL user code and password, an error message tells me
> that server cannot be registered because of time out. But I tried that
> last week and everything worked properly. I have been told that nothing
> had been changed.
> Looking forward to receiving some feedback on the above.
> Regards
> Patrick
>
|||Is latest version of MDAC installed on youre client machine?
Check for it also.
Regards
Amish
|||The MDAC has not been chenged
amish wrote:
> Is latest version of MDAC installed on youre client machine?
> Check for it also.
>
> Regards
> Amish
|||I can Ping the machine, I even see it in the list of proposed servers
to register. it seems that it is not a network problem.
|||I have the same problem on my client machine and I update MDAC to MDAC
2.8 and it was solved.
http://www.microsoft.com/downloads/d...displaylang=en
- To download MDAC Version
http://support.microsoft.com/default.aspx?kbid=301202 - To Check MDAC
Version
Check also for TCP IP port using telnet <server ip> <port> or check
if you have any other entry for this server name in client server
utility.
Regards
Amish

Cannot register server

I am working on a LAN with 3 servers, VED, PM, JF
In Enterprise manager, from server PM, I registered server VED but
cannot register server JF. I see it in the list of proposed server, but
when I enter the SQL user code and password, an error message tells me
that server cannot be registered because of time out. But I tried that
last week and everything worked properly. I have been told that nothing
had been changed.
Looking forward to receiving some feedback on the above.
Regards
PatrickA few things to try :-
Can you ping server JF
Is it listening on the default port 1433, use telnet to establish
Is SQL Server running on server JF or has the service been stopped
HTH. Ryan
"Patrick" <pmenage@.intnet.mu> wrote in message
news:1137472586.261082.252830@.o13g2000cwo.googlegroups.com...
>I am working on a LAN with 3 servers, VED, PM, JF
> In Enterprise manager, from server PM, I registered server VED but
> cannot register server JF. I see it in the list of proposed server, but
> when I enter the SQL user code and password, an error message tells me
> that server cannot be registered because of time out. But I tried that
> last week and everything worked properly. I have been told that nothing
> had been changed.
> Looking forward to receiving some feedback on the above.
> Regards
> Patrick
>|||Is latest version of MDAC installed on youre client machine?
Check for it also.
Regards
Amish|||The MDAC has not been chenged
amish wrote:
> Is latest version of MDAC installed on youre client machine?
> Check for it also.
>
> Regards
> Amish|||I can Ping the machine, I even see it in the list of proposed servers
to register. it seems that it is not a network problem.|||I have the same problem on my client machine and I update MDAC to MDAC
2.8 and it was solved.
http://www.microsoft.com/downloads/...&displaylang=en
- To download MDAC Version
http://support.microsoft.com/default.aspx?kbid=301202 - To Check MDAC
Version
Check also for TCP IP port using telnet <server ip> <port> or check
if you have any other entry for this server name in client server
utility.
Regards
Amishsql

Cannot register server

I am working on a LAN with 3 servers, VED, PM, JF
In Enterprise manager, from server PM, I registered server VED but
cannot register server JF. I see it in the list of proposed server, but
when I enter the SQL user code and password, an error message tells me
that server cannot be registered because of time out. But I tried that
last week and everything worked properly. I have been told that nothing
had been changed.
Looking forward to receiving some feedback on the above.
Regards
PatrickA few things to try :-
Can you ping server JF
Is it listening on the default port 1433, use telnet to establish
Is SQL Server running on server JF or has the service been stopped
--
HTH. Ryan
"Patrick" <pmenage@.intnet.mu> wrote in message
news:1137472586.261082.252830@.o13g2000cwo.googlegroups.com...
>I am working on a LAN with 3 servers, VED, PM, JF
> In Enterprise manager, from server PM, I registered server VED but
> cannot register server JF. I see it in the list of proposed server, but
> when I enter the SQL user code and password, an error message tells me
> that server cannot be registered because of time out. But I tried that
> last week and everything worked properly. I have been told that nothing
> had been changed.
> Looking forward to receiving some feedback on the above.
> Regards
> Patrick
>|||Is latest version of MDAC installed on youre client machine?
Check for it also.
Regards
Amish|||The MDAC has not been chenged
amish wrote:
> Is latest version of MDAC installed on youre client machine?
> Check for it also.
>
> Regards
> Amish|||I can Ping the machine, I even see it in the list of proposed servers
to register. it seems that it is not a network problem.|||I have the same problem on my client machine and I update MDAC to MDAC
2.8 and it was solved.
http://www.microsoft.com/downloads/details.aspx?FamilyID=6C050FE3-C795-4B7D-B037-185D0506396C&displaylang=en
- To download MDAC Version
http://support.microsoft.com/default.aspx?kbid=301202 - To Check MDAC
Version
Check also for TCP IP port using telnet <server ip> <port> or check
if you have any other entry for this server name in client server
utility.
--
Regards
Amish

Cannot Register Instance of SQL Server 2000

Information:

Server A: SQL Server 2000 Enterprise Edition. OS is Windows 2003 Server
Enterprise Edition. SQL Service pack is 3a. Member of domain
ABCDomain. Server A is going to function as a Distributor.
Location: New York.

Server B: SQL Server 2000 Enterprise Edition. OS is Windows 2003 Server
Standard Edition. SQL Service pack is 3a. Member of domain
ABCDomain. Server B is going to function as a Subscriber.
Location: London.

Server C: SQL Server 2000 Enterprise Edition. OS is Windows 2000 Advanced
Server. SQL Service pack 3a. Member of domain ABCDomain. Server C
is going to function as a Publisher. Location New York.

Problem: I am setting up a test replication environment prior to going live
with a replication from New York to London. When I try to register
Server A on Server B, I get the error: SQL Server does not exist or
access denied'. I get the same error when I try to register Server
B on Server A. Both boxes can ping the other. I am able to
register Server C (Publisher) on both Server A and B as well as
register both Server A and B on Server C.

I would appreciate your input as to what could be causing this
problem as well as a possible solution.

Thank you in advance."Robert M." <rmizzaro@.integratedbsi.com> wrote in message
news:9ff47a28.0407270533.280efcbd@.posting.google.c om...
> Information:
> Server A: SQL Server 2000 Enterprise Edition. OS is Windows 2003 Server
> Enterprise Edition. SQL Service pack is 3a. Member of domain
> ABCDomain. Server A is going to function as a Distributor.
> Location: New York.
> Server B: SQL Server 2000 Enterprise Edition. OS is Windows 2003 Server
> Standard Edition. SQL Service pack is 3a. Member of domain
> ABCDomain. Server B is going to function as a Subscriber.
> Location: London.
> Server C: SQL Server 2000 Enterprise Edition. OS is Windows 2000 Advanced
> Server. SQL Service pack 3a. Member of domain ABCDomain.
Server C
> is going to function as a Publisher. Location New York.
> Problem: I am setting up a test replication environment prior to going
live
> with a replication from New York to London. When I try to
register
> Server A on Server B, I get the error: 'SQL Server does not
exist or
> access denied'. I get the same error when I try to register
Server
> B on Server A. Both boxes can ping the other. I am able to
> register Server C (Publisher) on both Server A and B as well as
> register both Server A and B on Server C.
> I would appreciate your input as to what could be causing this
> problem as well as a possible solution.
> Thank you in advance.

I'm not really sure what you mean by "register" an instance - do you mean
you're using Enterprise Manager locally on Server B, and trying to register
Server A? Or do you mean you're doing something specific with the
replication tools? Either way, one key thing to check would be the service
account used for MSSQL and whether it has access to all the servers. This KB
article discusses many other possibilities:

http://support.microsoft.com/defaul...306&Product=sql

Simon|||I am trying to register the instance via Enterprise Manager locally on
each SQL Server. Also, for a test, I setup MSSQLSERVER and
SQLSERVERAGENT services using a domain administrator. Still I cannot
register Server A (through EM) on Server B or Server B (through EM) on
Server A.

"Simon Hayes" <sql@.hayes.ch> wrote in message news:<41068db6$1_2@.news.bluewin.ch>...
> "Robert M." <rmizzaro@.integratedbsi.com> wrote in message
> news:9ff47a28.0407270533.280efcbd@.posting.google.c om...
> > Information:
> > Server A: SQL Server 2000 Enterprise Edition. OS is Windows 2003 Server
> > Enterprise Edition. SQL Service pack is 3a. Member of domain
> > ABCDomain. Server A is going to function as a Distributor.
> > Location: New York.
> > Server B: SQL Server 2000 Enterprise Edition. OS is Windows 2003 Server
> > Standard Edition. SQL Service pack is 3a. Member of domain
> > ABCDomain. Server B is going to function as a Subscriber.
> > Location: London.
> > Server C: SQL Server 2000 Enterprise Edition. OS is Windows 2000 Advanced
> > Server. SQL Service pack 3a. Member of domain ABCDomain.
> Server C
> > is going to function as a Publisher. Location New York.
> > Problem: I am setting up a test replication environment prior to going
> live
> > with a replication from New York to London. When I try to
> register
> > Server A on Server B, I get the error: 'SQL Server does not
> exist or
> > access denied'. I get the same error when I try to register
> Server
> > B on Server A. Both boxes can ping the other. I am able to
> > register Server C (Publisher) on both Server A and B as well as
> > register both Server A and B on Server C.
> > I would appreciate your input as to what could be causing this
> > problem as well as a possible solution.
> > Thank you in advance.
> I'm not really sure what you mean by "register" an instance - do you mean
> you're using Enterprise Manager locally on Server B, and trying to register
> Server A? Or do you mean you're doing something specific with the
> replication tools? Either way, one key thing to check would be the service
> account used for MSSQL and whether it has access to all the servers. This KB
> article discusses many other possibilities:
> http://support.microsoft.com/defaul...306&Product=sql
> Simon

Cannot Register Any Instance of SQL Server 2000 to AD

Hello; I keep getting this message, 'SQL Enterprise Manager could not add
server '(local)' to AD. Error: 14303: Stored procedure
'sp_ActiveDirectory_SCP' failed to access registry key. Now, what does this
mean? I am the SA of this instance; I am the dbo, if you will, also. So, I
have the sufficient permissions to register any instance to AD, right? I even
installed SP4, but that didn't work. I"m a student of sql server services and
I'm in a training class, so I'd appreciate "guru"-level assistance. Thanks.
DominickAre you a local administrator on the machine? The error is telling you
that EM can't access the system registry. You also need the rights on
AD to publish the instance, sorry - I don't recall off hand the exact
permission.
Dominick D. wrote:
> Hello; I keep getting this message, 'SQL Enterprise Manager could not add
> server '(local)' to AD. Error: 14303: Stored procedure
> 'sp_ActiveDirectory_SCP' failed to access registry key. Now, what does this
> mean? I am the SA of this instance; I am the dbo, if you will, also. So, I
> have the sufficient permissions to register any instance to AD, right? I even
> installed SP4, but that didn't work. I"m a student of sql server services and
> I'm in a training class, so I'd appreciate "guru"-level assistance. Thanks.
> Dominick|||Yes, I am a local administrator on the machine where AD is located; I have
enterprise/domain admin rights. I don't understand why EM is not accessing
the registry. Can you dig a little deeper? Get some assistance?
Unfortunately, your response has not helped me.
"PSPDBA" wrote:
> Are you a local administrator on the machine? The error is telling you
> that EM can't access the system registry. You also need the rights on
> AD to publish the instance, sorry - I don't recall off hand the exact
> permission.
>
> Dominick D. wrote:
> > Hello; I keep getting this message, 'SQL Enterprise Manager could not add
> > server '(local)' to AD. Error: 14303: Stored procedure
> > 'sp_ActiveDirectory_SCP' failed to access registry key. Now, what does this
> > mean? I am the SA of this instance; I am the dbo, if you will, also. So, I
> > have the sufficient permissions to register any instance to AD, right? I even
> > installed SP4, but that didn't work. I"m a student of sql server services and
> > I'm in a training class, so I'd appreciate "guru"-level assistance. Thanks.
> >
> > Dominick
>|||Based on some reading, try change the SQL Service account to your
domain admin account, and use your domain admin to run the stored proc.
I would guess that the SQL Service account doesn't have the privileges
to read/edit the registy on the server.
Dominick D. wrote:
> Yes, I am a local administrator on the machine where AD is located; I have
> enterprise/domain admin rights. I don't understand why EM is not accessing
> the registry. Can you dig a little deeper? Get some assistance?
> Unfortunately, your response has not helped me.
> "PSPDBA" wrote:
> > Are you a local administrator on the machine? The error is telling you
> > that EM can't access the system registry. You also need the rights on
> > AD to publish the instance, sorry - I don't recall off hand the exact
> > permission.
> >
> >
> > Dominick D. wrote:
> > > Hello; I keep getting this message, 'SQL Enterprise Manager could not add
> > > server '(local)' to AD. Error: 14303: Stored procedure
> > > 'sp_ActiveDirectory_SCP' failed to access registry key. Now, what does this
> > > mean? I am the SA of this instance; I am the dbo, if you will, also. So, I
> > > have the sufficient permissions to register any instance to AD, right? I even
> > > installed SP4, but that didn't work. I"m a student of sql server services and
> > > I'm in a training class, so I'd appreciate "guru"-level assistance. Thanks.
> > >
> > > Dominick
> >
> >|||OK, I placed the SQLService domain user account into the domain admins group
and I was able to register another instance to the AD, so your advice worked;
however, I was not able to register the default instance to the AD :(. I
don't get that. Any other clue for that reason? Thanks for your help.
"PSPDBA" wrote:
> Based on some reading, try change the SQL Service account to your
> domain admin account, and use your domain admin to run the stored proc.
> I would guess that the SQL Service account doesn't have the privileges
> to read/edit the registy on the server.
>
> Dominick D. wrote:
> > Yes, I am a local administrator on the machine where AD is located; I have
> > enterprise/domain admin rights. I don't understand why EM is not accessing
> > the registry. Can you dig a little deeper? Get some assistance?
> > Unfortunately, your response has not helped me.
> >
> > "PSPDBA" wrote:
> >
> > > Are you a local administrator on the machine? The error is telling you
> > > that EM can't access the system registry. You also need the rights on
> > > AD to publish the instance, sorry - I don't recall off hand the exact
> > > permission.
> > >
> > >
> > > Dominick D. wrote:
> > > > Hello; I keep getting this message, 'SQL Enterprise Manager could not add
> > > > server '(local)' to AD. Error: 14303: Stored procedure
> > > > 'sp_ActiveDirectory_SCP' failed to access registry key. Now, what does this
> > > > mean? I am the SA of this instance; I am the dbo, if you will, also. So, I
> > > > have the sufficient permissions to register any instance to AD, right? I even
> > > > installed SP4, but that didn't work. I"m a student of sql server services and
> > > > I'm in a training class, so I'd appreciate "guru"-level assistance. Thanks.
> > > >
> > > > Dominick
> > >
> > >
>|||Ok, we're getting further. I did a little more reading - check the
MSSQLServerADHelper service and set it to use the domain admin account
too.
Dominick D. wrote:
> OK, I placed the SQLService domain user account into the domain admins group
> and I was able to register another instance to the AD, so your advice worked;
> however, I was not able to register the default instance to the AD :(. I
> don't get that. Any other clue for that reason? Thanks for your help.
> "PSPDBA" wrote:
> > Based on some reading, try change the SQL Service account to your
> > domain admin account, and use your domain admin to run the stored proc.
> >
> > I would guess that the SQL Service account doesn't have the privileges
> > to read/edit the registy on the server.
> >
> >
> > Dominick D. wrote:
> > > Yes, I am a local administrator on the machine where AD is located; I have
> > > enterprise/domain admin rights. I don't understand why EM is not accessing
> > > the registry. Can you dig a little deeper? Get some assistance?
> > > Unfortunately, your response has not helped me.
> > >
> > > "PSPDBA" wrote:
> > >
> > > > Are you a local administrator on the machine? The error is telling you
> > > > that EM can't access the system registry. You also need the rights on
> > > > AD to publish the instance, sorry - I don't recall off hand the exact
> > > > permission.
> > > >
> > > >
> > > > Dominick D. wrote:
> > > > > Hello; I keep getting this message, 'SQL Enterprise Manager could not add
> > > > > server '(local)' to AD. Error: 14303: Stored procedure
> > > > > 'sp_ActiveDirectory_SCP' failed to access registry key. Now, what does this
> > > > > mean? I am the SA of this instance; I am the dbo, if you will, also. So, I
> > > > > have the sufficient permissions to register any instance to AD, right? I even
> > > > > installed SP4, but that didn't work. I"m a student of sql server services and
> > > > > I'm in a training class, so I'd appreciate "guru"-level assistance. Thanks.
> > > > >
> > > > > Dominick
> > > >
> > > >
> >
> >|||OK, I can do that, but, I noticed that there is no such user/group called
MSSQLServerADHelper. Do I have to create it or is it already created?
"PSPDBA" wrote:
> Ok, we're getting further. I did a little more reading - check the
> MSSQLServerADHelper service and set it to use the domain admin account
> too.
>
> Dominick D. wrote:
> > OK, I placed the SQLService domain user account into the domain admins group
> > and I was able to register another instance to the AD, so your advice worked;
> > however, I was not able to register the default instance to the AD :(. I
> > don't get that. Any other clue for that reason? Thanks for your help.
> >
> > "PSPDBA" wrote:
> >
> > > Based on some reading, try change the SQL Service account to your
> > > domain admin account, and use your domain admin to run the stored proc.
> > >
> > > I would guess that the SQL Service account doesn't have the privileges
> > > to read/edit the registy on the server.
> > >
> > >
> > > Dominick D. wrote:
> > > > Yes, I am a local administrator on the machine where AD is located; I have
> > > > enterprise/domain admin rights. I don't understand why EM is not accessing
> > > > the registry. Can you dig a little deeper? Get some assistance?
> > > > Unfortunately, your response has not helped me.
> > > >
> > > > "PSPDBA" wrote:
> > > >
> > > > > Are you a local administrator on the machine? The error is telling you
> > > > > that EM can't access the system registry. You also need the rights on
> > > > > AD to publish the instance, sorry - I don't recall off hand the exact
> > > > > permission.
> > > > >
> > > > >
> > > > > Dominick D. wrote:
> > > > > > Hello; I keep getting this message, 'SQL Enterprise Manager could not add
> > > > > > server '(local)' to AD. Error: 14303: Stored procedure
> > > > > > 'sp_ActiveDirectory_SCP' failed to access registry key. Now, what does this
> > > > > > mean? I am the SA of this instance; I am the dbo, if you will, also. So, I
> > > > > > have the sufficient permissions to register any instance to AD, right? I even
> > > > > > installed SP4, but that didn't work. I"m a student of sql server services and
> > > > > > I'm in a training class, so I'd appreciate "guru"-level assistance. Thanks.
> > > > > >
> > > > > > Dominick
> > > > >
> > > > >
> > >
> > >
>|||Thats a service on the server, not a group/user.
Dominick D. wrote:
> OK, I can do that, but, I noticed that there is no such user/group called
> MSSQLServerADHelper. Do I have to create it or is it already created?
> "PSPDBA" wrote:
> > Ok, we're getting further. I did a little more reading - check the
> > MSSQLServerADHelper service and set it to use the domain admin account
> > too.
> >
> >
> > Dominick D. wrote:
> > > OK, I placed the SQLService domain user account into the domain admins group
> > > and I was able to register another instance to the AD, so your advice worked;
> > > however, I was not able to register the default instance to the AD :(. I
> > > don't get that. Any other clue for that reason? Thanks for your help.
> > >
> > > "PSPDBA" wrote:
> > >
> > > > Based on some reading, try change the SQL Service account to your
> > > > domain admin account, and use your domain admin to run the stored proc.
> > > >
> > > > I would guess that the SQL Service account doesn't have the privileges
> > > > to read/edit the registy on the server.
> > > >
> > > >
> > > > Dominick D. wrote:
> > > > > Yes, I am a local administrator on the machine where AD is located; I have
> > > > > enterprise/domain admin rights. I don't understand why EM is not accessing
> > > > > the registry. Can you dig a little deeper? Get some assistance?
> > > > > Unfortunately, your response has not helped me.
> > > > >
> > > > > "PSPDBA" wrote:
> > > > >
> > > > > > Are you a local administrator on the machine? The error is telling you
> > > > > > that EM can't access the system registry. You also need the rights on
> > > > > > AD to publish the instance, sorry - I don't recall off hand the exact
> > > > > > permission.
> > > > > >
> > > > > >
> > > > > > Dominick D. wrote:
> > > > > > > Hello; I keep getting this message, 'SQL Enterprise Manager could not add
> > > > > > > server '(local)' to AD. Error: 14303: Stored procedure
> > > > > > > 'sp_ActiveDirectory_SCP' failed to access registry key. Now, what does this
> > > > > > > mean? I am the SA of this instance; I am the dbo, if you will, also. So, I
> > > > > > > have the sufficient permissions to register any instance to AD, right? I even
> > > > > > > installed SP4, but that didn't work. I"m a student of sql server services and
> > > > > > > I'm in a training class, so I'd appreciate "guru"-level assistance. Thanks.
> > > > > > >
> > > > > > > Dominick
> > > > > >
> > > > > >
> > > >
> > > >
> >
> >|||OK, how do I access it and by putting the sa into the domain admins group, I
was able to register both the default and named instance on the AD, so your
advice helped. Thanks.
"PSPDBA" wrote:
> Thats a service on the server, not a group/user.
>
> Dominick D. wrote:
> > OK, I can do that, but, I noticed that there is no such user/group called
> > MSSQLServerADHelper. Do I have to create it or is it already created?
> >
> > "PSPDBA" wrote:
> >
> > > Ok, we're getting further. I did a little more reading - check the
> > > MSSQLServerADHelper service and set it to use the domain admin account
> > > too.
> > >
> > >
> > > Dominick D. wrote:
> > > > OK, I placed the SQLService domain user account into the domain admins group
> > > > and I was able to register another instance to the AD, so your advice worked;
> > > > however, I was not able to register the default instance to the AD :(. I
> > > > don't get that. Any other clue for that reason? Thanks for your help.
> > > >
> > > > "PSPDBA" wrote:
> > > >
> > > > > Based on some reading, try change the SQL Service account to your
> > > > > domain admin account, and use your domain admin to run the stored proc.
> > > > >
> > > > > I would guess that the SQL Service account doesn't have the privileges
> > > > > to read/edit the registy on the server.
> > > > >
> > > > >
> > > > > Dominick D. wrote:
> > > > > > Yes, I am a local administrator on the machine where AD is located; I have
> > > > > > enterprise/domain admin rights. I don't understand why EM is not accessing
> > > > > > the registry. Can you dig a little deeper? Get some assistance?
> > > > > > Unfortunately, your response has not helped me.
> > > > > >
> > > > > > "PSPDBA" wrote:
> > > > > >
> > > > > > > Are you a local administrator on the machine? The error is telling you
> > > > > > > that EM can't access the system registry. You also need the rights on
> > > > > > > AD to publish the instance, sorry - I don't recall off hand the exact
> > > > > > > permission.
> > > > > > >
> > > > > > >
> > > > > > > Dominick D. wrote:
> > > > > > > > Hello; I keep getting this message, 'SQL Enterprise Manager could not add
> > > > > > > > server '(local)' to AD. Error: 14303: Stored procedure
> > > > > > > > 'sp_ActiveDirectory_SCP' failed to access registry key. Now, what does this
> > > > > > > > mean? I am the SA of this instance; I am the dbo, if you will, also. So, I
> > > > > > > > have the sufficient permissions to register any instance to AD, right? I even
> > > > > > > > installed SP4, but that didn't work. I"m a student of sql server services and
> > > > > > > > I'm in a training class, so I'd appreciate "guru"-level assistance. Thanks.
> > > > > > > >
> > > > > > > > Dominick
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> > >
> > >
>

Cannot Register Any Instance of SQL Server 2000 to AD

Hello; I keep getting this message, 'SQL Enterprise Manager could not add
server '(local)' to AD. Error: 14303: Stored procedure
'sp_ActiveDirectory_SCP' failed to access registry key. Now, what does this
mean? I am the SA of this instance; I am the dbo, if you will, also. So, I
have the sufficient permissions to register any instance to AD, right? I eve
n
installed SP4, but that didn't work. I"m a student of sql server services an
d
I'm in a training class, so I'd appreciate "guru"-level assistance. Thanks.
DominickAre you a local administrator on the machine? The error is telling you
that EM can't access the system registry. You also need the rights on
AD to publish the instance, sorry - I don't recall off hand the exact
permission.
Dominick D. wrote:
> Hello; I keep getting this message, 'SQL Enterprise Manager could not add
> server '(local)' to AD. Error: 14303: Stored procedure
> 'sp_ActiveDirectory_SCP' failed to access registry key. Now, what does th
is
> mean? I am the SA of this instance; I am the dbo, if you will, also. So, I
> have the sufficient permissions to register any instance to AD, right? I e
ven
> installed SP4, but that didn't work. I"m a student of sql server services
and
> I'm in a training class, so I'd appreciate "guru"-level assistance. Thanks
.
> Dominick|||Yes, I am a local administrator on the machine where AD is located; I have
enterprise/domain admin rights. I don't understand why EM is not accessing
the registry. Can you dig a little deeper? Get some assistance?
Unfortunately, your response has not helped me.
"PSPDBA" wrote:

> Are you a local administrator on the machine? The error is telling you
> that EM can't access the system registry. You also need the rights on
> AD to publish the instance, sorry - I don't recall off hand the exact
> permission.
>
> Dominick D. wrote:
>|||Based on some reading, try change the SQL Service account to your
domain admin account, and use your domain admin to run the stored proc.
I would guess that the SQL Service account doesn't have the privileges
to read/edit the registy on the server.
Dominick D. wrote:[vbcol=seagreen]
> Yes, I am a local administrator on the machine where AD is located; I have
> enterprise/domain admin rights. I don't understand why EM is not accessing
> the registry. Can you dig a little deeper? Get some assistance?
> Unfortunately, your response has not helped me.
> "PSPDBA" wrote:
>|||OK, I placed the SQLService domain user account into the domain admins group
and I was able to register another instance to the AD, so your advice worked
;
however, I was not able to register the default instance to the AD . I
don't get that. Any other clue for that reason? Thanks for your help.
"PSPDBA" wrote:

> Based on some reading, try change the SQL Service account to your
> domain admin account, and use your domain admin to run the stored proc.
> I would guess that the SQL Service account doesn't have the privileges
> to read/edit the registy on the server.
>
> Dominick D. wrote:
>|||Ok, we're getting further. I did a little more reading - check the
MSSQLServerADHelper service and set it to use the domain admin account
too.
Dominick D. wrote:[vbcol=seagreen]
> OK, I placed the SQLService domain user account into the domain admins gro
up
> and I was able to register another instance to the AD, so your advice work
ed;
> however, I was not able to register the default instance to the AD . I
> don't get that. Any other clue for that reason? Thanks for your help.
> "PSPDBA" wrote:
>|||OK, I can do that, but, I noticed that there is no such user/group called
MSSQLServerADHelper. Do I have to create it or is it already created?
"PSPDBA" wrote:

> Ok, we're getting further. I did a little more reading - check the
> MSSQLServerADHelper service and set it to use the domain admin account
> too.
>
> Dominick D. wrote:
>|||Thats a service on the server, not a group/user.
Dominick D. wrote:[vbcol=seagreen]
> OK, I can do that, but, I noticed that there is no such user/group called
> MSSQLServerADHelper. Do I have to create it or is it already created?
> "PSPDBA" wrote:
>|||OK, how do I access it and by putting the sa into the domain admins group, I
was able to register both the default and named instance on the AD, so your
advice helped. Thanks.
"PSPDBA" wrote:

> Thats a service on the server, not a group/user.
>
> Dominick D. wrote:
>sql

Thursday, March 22, 2012

cannot open table in Enterprise manager

Hi, each time I want to open a table (return all rows)
this message pop up:
The query cannot be executed because some files are
either missing or not registered.
I found, on microsoft.com, that I just have to reinstall
the product or use regsvr32.exe to register some dll's.
I tried both solutions and it's not working.
Any ideas?
thanks
A little more information might help - What application are you using to
perform the query?
Jim
"eric champagne" <anonymous@.discussions.microsoft.com> wrote in message
news:1417e01c41801$7a6a3070$a601280a@.phx.gbl...
> Hi, each time I want to open a table (return all rows)
> this message pop up:
> The query cannot be executed because some files are
> either missing or not registered.
> I found, on microsoft.com, that I just have to reinstall
> the product or use regsvr32.exe to register some dll's.
> I tried both solutions and it's not working.
> Any ideas?
> thanks
|||sql server enterprise manager 2000... on my other windows
xp workstation , it's working fine.

>--Original Message--
>A little more information might help - What application
are you using to
>perform the query?
>Jim
>"eric champagne" <anonymous@.discussions.microsoft.com>
wrote in message
>news:1417e01c41801$7a6a3070$a601280a@.phx.gbl...
reinstall
>
>.
>
|||Did you apply Service Pack 3a of SQL Server to the workstation? This needs
to be done to update EM also.
Jim
<anonymous@.discussions.microsoft.com> wrote in message
news:142be01c41813$7d1bddc0$a601280a@.phx.gbl...
> sql server enterprise manager 2000... on my other windows
> xp workstation , it's working fine.
> are you using to
> wrote in message
> reinstall
|||Yes I did that...
It's very strange because it's working on all my other
workstation with XP

>--Original Message--
>Did you apply Service Pack 3a of SQL Server to the
workstation? This needs
>to be done to update EM also.
>Jim
><anonymous@.discussions.microsoft.com> wrote in message
>news:142be01c41813$7d1bddc0$a601280a@.phx.gbl...
windows
application
rows)
dll's.
>
>.
>
|||Did you reinstall the client tools?
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"eric champagne" <anonymous@.discussions.microsoft.com> wrote in message
news:1417e01c41801$7a6a3070$a601280a@.phx.gbl...
> Hi, each time I want to open a table (return all rows)
> this message pop up:
> The query cannot be executed because some files are
> either missing or not registered.
> I found, on microsoft.com, that I just have to reinstall
> the product or use regsvr32.exe to register some dll's.
> I tried both solutions and it's not working.
> Any ideas?
> thanks
|||Are you trying to use Query Analyzer or the table data browser in EM?
Can you run queries using QA?
Jim
<anonymous@.discussions.microsoft.com> wrote in message
news:143b801c41821$c469c530$a601280a@.phx.gbl...
> Yes I did that...
> It's very strange because it's working on all my other
> workstation with XP
> workstation? This needs
> windows
> application
> rows)
> dll's.

Tuesday, March 20, 2012

cannot open query analyzer and profiler through EM

Hello Experts,
My problem is that I can't call QA and Profiler through Enterprise Manager
from the tools menu.
I made some MSDE installations and UnInstallations for debug reasons and
then this problem occurred.
Step 1) Installing an named instance "MYINSTANCE"
Step 2) UnInstalling "MYINSTANCE"
Step 3) ReInstalling "MYINSTANCE"
Step 4) UnInstalling "MYINSTANCE"
Can anyone please help me with this? I'm afraid that may be other functions
have crashed, but this is the first problem face up.
Regards!What happens when you go to Start|Run, type "isqlw" without the quotes, and
hit enter?
Or if you run Query Analyzer or Profiler from the Start Menu?
FWIW, I always call those tools directly.
"x-rays" <xrays@.discussions.microsoft.com> wrote in message
news:9F764D97-FE3F-4E80-90AE-7A7DD34DB2CB@.microsoft.com...
> Hello Experts,
> My problem is that I can't call QA and Profiler through Enterprise Manager
> from the tools menu.
> I made some MSDE installations and UnInstallations for debug reasons and
> then this problem occurred.
> Step 1) Installing an named instance "MYINSTANCE"
> Step 2) UnInstalling "MYINSTANCE"
> Step 3) ReInstalling "MYINSTANCE"
> Step 4) UnInstalling "MYINSTANCE"
> Can anyone please help me with this? I'm afraid that may be other
> functions
> have crashed, but this is the first problem face up.
> Regards!|||Hello Aaron, thank you for your reply,
No problem with that, qa and profiler work, I think that EM has lost the
right paths for the tools but I don't know where I have to go to correct the
m.
Do you have any Idea?
Regards!
Ο χρ?στη? "Aaron Bertrand [SQL Server MVP]" _γγραψε:

> What happens when you go to Start|Run, type "isqlw" without the quotes, an
d
> hit enter?
> Or if you run Query Analyzer or Profiler from the Start Menu?
> FWIW, I always call those tools directly.
>
>
> "x-rays" <xrays@.discussions.microsoft.com> wrote in message
> news:9F764D97-FE3F-4E80-90AE-7A7DD34DB2CB@.microsoft.com...
>
>|||Hello Aaron and thank you for your reply.
No problem with that, I think that EM have lost the paths of the tools and I
don't know where to go to correct them.
regards!
Ο χρ?στη? "Aaron Bertrand [SQL Server MVP]" _γγραψε:

> What happens when you go to Start|Run, type "isqlw" without the quotes, an
d
> hit enter?
> Or if you run Query Analyzer or Profiler from the Start Menu?
> FWIW, I always call those tools directly.
>
>
> "x-rays" <xrays@.discussions.microsoft.com> wrote in message
> news:9F764D97-FE3F-4E80-90AE-7A7DD34DB2CB@.microsoft.com...
>
>|||> No problem with that, qa and profiler work, I think that EM has lost the
> right paths for the tools but I don't know where I have to go to correct
> them.
> Do you have any Idea?
Reinstall client tools, or stop using EM to launch tools other than EM...|||Ok, thank you very much for your time Aaron.
Ο χρ?στη? "Aaron Bertrand [SQL Server MVP]" _γγραψε:

> Reinstall client tools, or stop using EM to launch tools other than EM...
>
>

Cannot Open Query analyser from SQL Enterprise Manager

I intalled SQL200SP4 on my Windows 2003 server and now, I cannot open Query
analyser from SQL Enterprise Manager.
I get the following message: "The specified file was not found"
I can go to Query Analyser directly from the Start Menu and it works fine.
Can you please suggest, what I should do to fix this?
Thanks
Hello!
I thought this was a managed Newsgroup.
Anyone from Microsoft with a clue, why this is happening and how can I fix
this?
Thanks
"gurusinghj" wrote:

> I intalled SQL200SP4 on my Windows 2003 server and now, I cannot open Query
> analyser from SQL Enterprise Manager.
> I get the following message: "The specified file was not found"
> I can go to Query Analyser directly from the Start Menu and it works fine.
> Can you please suggest, what I should do to fix this?
> Thanks
|||gurusinghj wrote:
> I intalled SQL200SP4 on my Windows 2003 server and now, I cannot open
> Query analyser from SQL Enterprise Manager.
> I get the following message: "The specified file was not found"
> I can go to Query Analyser directly from the Start Menu and it works
> fine.
> Can you please suggest, what I should do to fix this?
> Thanks
Make sure the SQL tools are in your path. The default might look
something like the following in the path environment variable:
"C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;"
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||Thanks David,
But i do have this in path, but I still get this issue.
Thinking back, I did once install SQL Server 2000 Desktop Engine (MSDE)
after SQl server was already installed. (Another application that I
installed, did the insalltion, without me knowing.)
I did subsequently uninstall it. Do you think, that might have messed up
some registry settings.
Any help on how to restore these back, will be really appreciated.
Thanks
"David Gugick" wrote:

> gurusinghj wrote:
> Make sure the SQL tools are in your path. The default might look
> something like the following in the path environment variable:
> "C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;"
>
>
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>
|||gurusinghj wrote:
> Thanks David,
> But i do have this in path, but I still get this issue.
> Thinking back, I did once install SQL Server 2000 Desktop Engine
> (MSDE) after SQl server was already installed. (Another application
> that I installed, did the insalltion, without me knowing.)
> I did subsequently uninstall it. Do you think, that might have messed
> up some registry settings.
> Any help on how to restore these back, will be really appreciated.
I doubt it. MSDE does not have any client tools and I doubt it would
add/change the PATH variable. If you open a command window and type
ISQL.EXE from the C:\ root folder, does QA come up? Also make sure the
"Start In" folder is the same as the "Target" folder in the shortcut for
SQL EM. The Target should look something like:
C:\WINDOWS\system32\mmc.exe /s "C:\Program Files\Microsoft SQL
Server\80\Tools\BINN\SQL Server Enterprise Manager.MSC"
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||I get the same problem right after installing MSDE also
"David Gugick" wrote:

> gurusinghj wrote:
> I doubt it. MSDE does not have any client tools and I doubt it would
> add/change the PATH variable. If you open a command window and type
> ISQL.EXE from the C:\ root folder, does QA come up? Also make sure the
> "Start In" folder is the same as the "Target" folder in the shortcut for
> SQL EM. The Target should look something like:
> C:\WINDOWS\system32\mmc.exe /s "C:\Program Files\Microsoft SQL
> Server\80\Tools\BINN\SQL Server Enterprise Manager.MSC"
>
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>
|||In SQL Enterprise Manager (SEM), go to Tools->External Tools; add the path
to isqlw with the parameters
-S[SRV] -d[DBN]
A new menu item should be created under Tools that will launch QA with the
right database and server context based on SEM.
If the "file not found" messge box appears, you might need the full path for
isqlw.exe OR ensure the "isqlw.exe" string appears in the "command field".
If the path contains spaces, you need to wrap the path with double quotes.
The -S and -d parameters are optional but allow you to bypass the connection
dialog each and every launch.
Regards,
Keith
This posting is provided "as is" without inferring rights or warranties.
"jdehne" <jdehne@.discussions.microsoft.com> wrote in message
news:66BE5CD0-0CE9-46E3-A258-A033FD06E75A@.microsoft.com...[vbcol=seagreen]
>I get the same problem right after installing MSDE also
> "David Gugick" wrote:

Cannot open Enterprise Mgr

All of a sudden I am getting a "Microsoft Management Console has encountered
a problem..." error when opening EM. It has been working fine up til now, and
I've made no changes to system, etc....
I replaced the SQL Server Enterprise Manager.MSC file with one from my
laptop, which is identical, but this did not help. I can open other mmc
files, just not this one.
Any help would be greatly appreciated, as this is preventing me from doing
many tasks.
Thanks in advance,
Tom
Hi Tom,
From your descriptions, I understood that you are not able to open SQL
Server Enterprise Manager with the error message "Microsoft Management
Console has encountered a problem...". Have I understood you? Correct me if
I was wrong.
Based on my knowledge, please delete file "SQL Server Enterprise Manager"
under
C:\Documents and Settings\<login ID>\Application Data\Microsoft\MMC
and then try again.
If you have any questions or concerns, don't hesitate to let me know. We
are always here to be of assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Thanks Michael, that did the trick.
I appreciate your quick response and assistance.
Tom
"Michael Cheng [MSFT]" wrote:

> Hi Tom,
> From your descriptions, I understood that you are not able to open SQL
> Server Enterprise Manager with the error message "Microsoft Management
> Console has encountered a problem...". Have I understood you? Correct me if
> I was wrong.
> Based on my knowledge, please delete file "SQL Server Enterprise Manager"
> under
> C:\Documents and Settings\<login ID>\Application Data\Microsoft\MMC
> and then try again.
> If you have any questions or concerns, don't hesitate to let me know. We
> are always here to be of assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
|||Hi Tom,
It's great to hear that it works
If you have any questions or concerns on SQL Server next time, don't
hesitate to let me know. We are always here to be of assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/tec...rview/40010469
Others: https://partner.microsoft.com/US/tec...pportoverview/
If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

cannot open Enterprise Manager

Hi All,
Several months ago, I installed SQL Server 2000
Development edition on my Windows XP laptop.
Today, for the first time, for some unknown reason I
cannot open the Enterprise Manager. I have been able to
open it, practically everyday, for the past few months.
I am getting the following Microsoft Management Console
error message:
"MMC cannot open the file C:\Program Files\Microsoft SQL
Server\80\Tools\BINN\SQL Server Enterprise Manager.MSC.
This may be because the file does not exist, is not an
MMCconsole, or was created by a later version of MMC.
This may also be because you do not have sufficient
access rights to the file."
SQL Server Enterprise Manager.MSC file does exist in
I have all access rights to my laptop!
Any idea what have caused this problem and how could I
fix it.
Thank you,
Mitra
Try uninstalling / reinstalling the client tools, and/or reapplying SP3a.
http://www.aspfaq.com/
(Reverse address to reply.)
"mitra fatholahi" <mitra928@.hotmail.com> wrote in message
news:1b2d201c44f45$da666d60$a001280a@.phx.gbl...
> Hi All,
> Several months ago, I installed SQL Server 2000
> Development edition on my Windows XP laptop.
> Today, for the first time, for some unknown reason I
> cannot open the Enterprise Manager. I have been able to
> open it, practically everyday, for the past few months.
> I am getting the following Microsoft Management Console
> error message:
> "MMC cannot open the file C:\Program Files\Microsoft SQL
> Server\80\Tools\BINN\SQL Server Enterprise Manager.MSC.
> This may be because the file does not exist, is not an
> MMCconsole, or was created by a later version of MMC.
> This may also be because you do not have sufficient
> access rights to the file."
> SQL Server Enterprise Manager.MSC file does exist in
> I have all access rights to my laptop!
> Any idea what have caused this problem and how could I
> fix it.
> Thank you,
> Mitra
>
>
>
|||The file that becomes the SQL Server Enterprise Manager.MSC is named
SQLEM.MSC on the SQL Server 2000 CD. You can try copying the one form the
CD, renaming it and replcacing the one on disk.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Cannot open Enterprise Manager

I have performed a windows update on the server and now i am presented with
an error when trying to open enterprise manager. The MMC cannot find the
file C:\Program Files\Microsoft SQL Server\80\Tools\Bin\SQL Server Enterprise
Manager.msc
My sql server resides on D: and I have never had a problem opening SQL
Enterprise Manager. I can access the enterprise manager by adding the
snapin. Any ideas.
If you are launching it from a program icon those are all
shortcuts. Right click on the icon and select properties and
check the path to your SQL Server Enterprise Manager.msc
file.
-Sue
On Mon, 7 Nov 2005 06:30:09 -0800, KMD
<KMD@.discussions.microsoft.com> wrote:

>I have performed a windows update on the server and now i am presented with
>an error when trying to open enterprise manager. The MMC cannot find the
>file C:\Program Files\Microsoft SQL Server\80\Tools\Bin\SQL Server Enterprise
>Manager.msc
>My sql server resides on D: and I have never had a problem opening SQL
>Enterprise Manager. I can access the enterprise manager by adding the
>snapin. Any ideas.

cannot open Enterprise Manager

Hi All,
Several months ago, I installed SQL Server 2000
Development edition on my Windows XP laptop.
Today, for the first time, for some unknown reason I
cannot open the Enterprise Manager. I have been able to
open it, practically everyday, for the past few months.
I am getting the following Microsoft Management Console
error message:
"MMC cannot open the file C:\Program Files\Microsoft SQL
Server\80\Tools\BINN\SQL Server Enterprise Manager.MSC.
This may be because the file does not exist, is not an
MMCconsole, or was created by a later version of MMC.
This may also be because you do not have sufficient
access rights to the file."
SQL Server Enterprise Manager.MSC file does exist in
I have all access rights to my laptop!
Any idea what have caused this problem and how could I
fix it.
Thank you,
MitraTry uninstalling / reinstalling the client tools, and/or reapplying SP3a.
--
http://www.aspfaq.com/
(Reverse address to reply.)
"mitra fatholahi" <mitra928@.hotmail.com> wrote in message
news:1b2d201c44f45$da666d60$a001280a@.phx.gbl...
> Hi All,
> Several months ago, I installed SQL Server 2000
> Development edition on my Windows XP laptop.
> Today, for the first time, for some unknown reason I
> cannot open the Enterprise Manager. I have been able to
> open it, practically everyday, for the past few months.
> I am getting the following Microsoft Management Console
> error message:
> "MMC cannot open the file C:\Program Files\Microsoft SQL
> Server\80\Tools\BINN\SQL Server Enterprise Manager.MSC.
> This may be because the file does not exist, is not an
> MMCconsole, or was created by a later version of MMC.
> This may also be because you do not have sufficient
> access rights to the file."
> SQL Server Enterprise Manager.MSC file does exist in
> I have all access rights to my laptop!
> Any idea what have caused this problem and how could I
> fix it.
> Thank you,
> Mitra
>
>
>|||The file that becomes the SQL Server Enterprise Manager.MSC is named
SQLEM.MSC on the SQL Server 2000 CD. You can try copying the one form the
CD, renaming it and replcacing the one on disk.
Rand
This posting is provided "as is" with no warranties and confers no rights.sql

Cannot open Enterprise Manager

I have performed a windows update on the server and now i am presented with
an error when trying to open enterprise manager. The MMC cannot find the
file C:\Program Files\Microsoft SQL Server\80\Tools\Bin\SQL Server Enterprise
Manager.msc
My sql server resides on D: and I have never had a problem opening SQL
Enterprise Manager. I can access the enterprise manager by adding the
snapin. Any ideas.If you are launching it from a program icon those are all
shortcuts. Right click on the icon and select properties and
check the path to your SQL Server Enterprise Manager.msc
file.
-Sue
On Mon, 7 Nov 2005 06:30:09 -0800, KMD
<KMD@.discussions.microsoft.com> wrote:
>I have performed a windows update on the server and now i am presented with
>an error when trying to open enterprise manager. The MMC cannot find the
>file C:\Program Files\Microsoft SQL Server\80\Tools\Bin\SQL Server Enterprise
>Manager.msc
>My sql server resides on D: and I have never had a problem opening SQL
>Enterprise Manager. I can access the enterprise manager by adding the
>snapin. Any ideas.

Cannot open Enterprise Manager

I have performed a windows update on the server and now i am presented with
an error when trying to open enterprise manager. The MMC cannot find the
file C:\Program Files\Microsoft SQL Server\80\Tools\Bin\SQL Server Enterpris
e
Manager.msc
My sql server resides on D: and I have never had a problem opening SQL
Enterprise Manager. I can access the enterprise manager by adding the
snapin. Any ideas.If you are launching it from a program icon those are all
shortcuts. Right click on the icon and select properties and
check the path to your SQL Server Enterprise Manager.msc
file.
-Sue
On Mon, 7 Nov 2005 06:30:09 -0800, KMD
<KMD@.discussions.microsoft.com> wrote:

>I have performed a windows update on the server and now i am presented with
>an error when trying to open enterprise manager. The MMC cannot find the
>file C:\Program Files\Microsoft SQL Server\80\Tools\Bin\SQL Server Enterpri
se
>Manager.msc
>My sql server resides on D: and I have never had a problem opening SQL
>Enterprise Manager. I can access the enterprise manager by adding the
>snapin. Any ideas.

cannot open Enterprise Manager

Hi All,
Several months ago, I installed SQL Server 2000
Development edition on my Windows XP laptop.
Today, for the first time, for some unknown reason I
cannot open the Enterprise Manager. I have been able to
open it, practically everyday, for the past few months.
I am getting the following Microsoft Management Console
error message:
"MMC cannot open the file C:\Program Files\Microsoft SQL
Server\80\Tools\BINN\SQL Server Enterprise Manager.MSC.
This may be because the file does not exist, is not an
MMCconsole, or was created by a later version of MMC.
This may also be because you do not have sufficient
access rights to the file."
SQL Server Enterprise Manager.MSC file does exist in
I have all access rights to my laptop!
Any idea what have caused this problem and how could I
fix it.
Thank you,
MitraTry uninstalling / reinstalling the client tools, and/or reapplying SP3a.
http://www.aspfaq.com/
(Reverse address to reply.)
"mitra fatholahi" <mitra928@.hotmail.com> wrote in message
news:1b2d201c44f45$da666d60$a001280a@.phx
.gbl...
> Hi All,
> Several months ago, I installed SQL Server 2000
> Development edition on my Windows XP laptop.
> Today, for the first time, for some unknown reason I
> cannot open the Enterprise Manager. I have been able to
> open it, practically everyday, for the past few months.
> I am getting the following Microsoft Management Console
> error message:
> "MMC cannot open the file C:\Program Files\Microsoft SQL
> Server\80\Tools\BINN\SQL Server Enterprise Manager.MSC.
> This may be because the file does not exist, is not an
> MMCconsole, or was created by a later version of MMC.
> This may also be because you do not have sufficient
> access rights to the file."
> SQL Server Enterprise Manager.MSC file does exist in
> I have all access rights to my laptop!
> Any idea what have caused this problem and how could I
> fix it.
> Thank you,
> Mitra
>
>
>|||The file that becomes the SQL Server Enterprise Manager.MSC is named
SQLEM.MSC on the SQL Server 2000 CD. You can try copying the one form the
CD, renaming it and replcacing the one on disk.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Sunday, March 11, 2012

Cannot modify data

Hi,
Sometimes when I try to modify data in enterprise manager, I get this error:
Key column information is insufficient or incorrect.
Too many rows were affected by
How can I solve this problem?
Many thanks in advance.
Leila
Hi
There are a few issue with modifying data in EM, this seems to be that the
row you are changing can not be distinguished i.e it does not have a Primary
Key. Query analyser is usually a better tool to do larger or more complex
updates.
John
"Leila" <lelas@.hotpop.com> wrote in message
news:uhjs7s6oEHA.1816@.TK2MSFTNGP09.phx.gbl...
> Hi,
> Sometimes when I try to modify data in enterprise manager, I get this
error:
> Key column information is insufficient or incorrect.
> Too many rows were affected by
> How can I solve this problem?
> Many thanks in advance.
> Leila
>
|||I can image that if your PK has multiple columns, you might get this. So as
the previous poster suggests, change it using an update statement.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Leila" <lelas@.hotpop.com> wrote in message
news:uhjs7s6oEHA.1816@.TK2MSFTNGP09.phx.gbl...
> Hi,
> Sometimes when I try to modify data in enterprise manager, I get this
error:
> Key column information is insufficient or incorrect.
> Too many rows were affected by
> How can I solve this problem?
> Many thanks in advance.
> Leila
>

Cannot modify data

Hi,
Sometimes when I try to modify data in enterprise manager, I get this error:
Key column information is insufficient or incorrect.
Too many rows were affected by
How can I solve this problem?
Many thanks in advance.
LeilaHi
There are a few issue with modifying data in EM, this seems to be that the
row you are changing can not be distinguished i.e it does not have a Primary
Key. Query analyser is usually a better tool to do larger or more complex
updates.
John
"Leila" <lelas@.hotpop.com> wrote in message
news:uhjs7s6oEHA.1816@.TK2MSFTNGP09.phx.gbl...
> Hi,
> Sometimes when I try to modify data in enterprise manager, I get this
error:
> Key column information is insufficient or incorrect.
> Too many rows were affected by
> How can I solve this problem?
> Many thanks in advance.
> Leila
>|||I can image that if your PK has multiple columns, you might get this. So as
the previous poster suggests, change it using an update statement.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Leila" <lelas@.hotpop.com> wrote in message
news:uhjs7s6oEHA.1816@.TK2MSFTNGP09.phx.gbl...
> Hi,
> Sometimes when I try to modify data in enterprise manager, I get this
error:
> Key column information is insufficient or incorrect.
> Too many rows were affected by
> How can I solve this problem?
> Many thanks in advance.
> Leila
>

Cannot make New role assignments

New role assignment does not work on my new installation of SQL Reporting Services Enterprise edition on a Windows 2003 server. From Report Manager I navigate to: Home->Properties and select 'New Role Assignment'. I fill in a local user and select the 'Browser' role and click 'OK'. Nothing happens - there is no post-back. I have the same problem for 'Site Settings'. It's as if the Report Manager is running in read-only mode. Do I need to change some configuration to facilitate changes?
Thanks,
--steveDo you see any script errors? They would show up in the lower left corner
of IE.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"stark" <stark@.discussions.microsoft.com> wrote in message
news:2AD202DE-EA7F-4AB2-B0D0-4B6B450C75DB@.microsoft.com...
> New role assignment does not work on my new installation of SQL Reporting
Services Enterprise edition on a Windows 2003 server. From Report Manager I
navigate to: Home->Properties and select 'New Role Assignment'. I fill in a
local user and select the 'Browser' role and click 'OK'. Nothing happens -
there is no post-back. I have the same problem for 'Site Settings'. It's as
if the Report Manager is running in read-only mode. Do I need to change some
configuration to facilitate changes?
> Thanks,
> --steve|||Dan,
I'm having the same problem on trying to create New Role on both spots as the previous poster. There is no script errors in lower left hand corner. The button "New Role" does not even post back to the browser as I always thought "submit" uses the method specified in form action? Any rate the button is not working and I'm using Windows 2003 as well with lastest Framework 1.1.
HTML Output from "EditGroup.aspx"
<input type="submit" name="ui_btnCreateNewRole" value="New Role" id="ui_btnCreateNewRole" class="msrs-button" />
"Daniel Reib [MSFT]" wrote:
> Do you see any script errors? They would show up in the lower left corner
> of IE.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "stark" <stark@.discussions.microsoft.com> wrote in message
> news:2AD202DE-EA7F-4AB2-B0D0-4B6B450C75DB@.microsoft.com...
> > New role assignment does not work on my new installation of SQL Reporting
> Services Enterprise edition on a Windows 2003 server. From Report Manager I
> navigate to: Home->Properties and select 'New Role Assignment'. I fill in a
> local user and select the 'Browser' role and click 'OK'. Nothing happens -
> there is no post-back. I have the same problem for 'Site Settings'. It's as
> if the Report Manager is running in read-only mode. Do I need to change some
> configuration to facilitate changes?
> > Thanks,
> > --steve
>
>|||I found the a partial work around to get access to exisitng parent roles.
When you create a report folder, and you click on the report folder, you will have a "security" link in left hand nav. This allowed me to assign to Browser role which I did not have access to under Parent site setting and properties. Also it will ask if youre sure you want to use specific security on that folder, you must say Yes. You can always revert back using the button provided.
"Daniel Reib [MSFT]" wrote:
> Do you see any script errors? They would show up in the lower left corner
> of IE.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "stark" <stark@.discussions.microsoft.com> wrote in message
> news:2AD202DE-EA7F-4AB2-B0D0-4B6B450C75DB@.microsoft.com...
> > New role assignment does not work on my new installation of SQL Reporting
> Services Enterprise edition on a Windows 2003 server. From Report Manager I
> navigate to: Home->Properties and select 'New Role Assignment'. I fill in a
> local user and select the 'Browser' role and click 'OK'. Nothing happens -
> there is no post-back. I have the same problem for 'Site Settings'. It's as
> if the Report Manager is running in read-only mode. Do I need to change some
> configuration to facilitate changes?
> > Thanks,
> > --steve
>
>|||We have the same problem on our reporting server as well (just after
we made the last SP installation), new rule and move report actions
are not working.
After clicking on the "OK" nothing happen, no script error or any
other error indication can be found.
Any ideas?|||Hi,
this should be it:
on the server run:
aspnet_regiis -c
from the .Net framwork dir.|||I have the same problem. This aspnet_regiis didn't solve it for me...
any other suggestions?
elad@.cydoor.com (Elad) wrote in message news:<2ba7f8ad.0408041410.38bd9598@.posting.google.com>...
> Hi,
> this should be it:
> on the server run:
> aspnet_regiis -c
> from the .Net framwork dir.|||I had the problem described above... and 'aspnet_regiis -c' worked out.
Win 2003 Server, SQL Srvr w/ sp3 and RS w/ sp1.
In case this helps anyone...
The installation had a problem (25619) with virtual directories and I had to
create them manually (setup parameter -rsdonotcreatevirtualdirectories=true)
which I found in a kb article. I followed the steps to create the vir dir's
after the install and everything functioned except for the problem described
in this thread.
Perhaps the following kb article should be updated with a step to execute
aspnet_regiis -c from the .net framework dir.
http://support.microsoft.com/?kbid=867872
"Scott Stonehouse" wrote:
> I have the same problem. This aspnet_regiis didn't solve it for me...
> any other suggestions?
> elad@.cydoor.com (Elad) wrote in message news:<2ba7f8ad.0408041410.38bd9598@.posting.google.com>...
> > Hi,
> >
> > this should be it:
> >
> > on the server run:
> > aspnet_regiis -c
> >
> > from the .Net framwork dir.
>

Thursday, March 8, 2012

Cannot load SQL Server Enterprise Manager

This morning when I tried to load SQL Server Enterprise Manager I got the
following error message dialog.
MMC cannot open the file C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\SQL Server Enterprise Manager.MCS.
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.
The file exists, I've made the assumption it is an MMC console, I've had the
same version installed since sp-3 was distributed and I'm logged in under a
system adminsitrators account. Further, I've had and run the same setup for
several months with no problems.

Quote:

Originally posted by Charles
This morning when I tried to load SQL Server Enterprise Manager I got the
following error message dialog.
MMC cannot open the file C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\SQL Server Enterprise Manager.MCS.
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.
The file exists, I've made the assumption it is an MMC console, I've had the
same version installed since sp-3 was distributed and I'm logged in under a
system adminsitrators account. Further, I've had and run the same setup for
several months with no problems.