cannot rename instance of analysis server.missing reg key

when i use the rename instance tool i get this error saying it cannot find the regestry key

hkey_local_Machine\wow6432Node\Microsoft\Microsoft Sql Server\90

When i look for this key, it doesnt exist. My installation went perfectly. what is going wrong

There are 2 versions of ASInstanceRename utility. Make sure you use one that is installed with 64bit version of Analysis Server.

Edward Melomed.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||but i am using the 32 bit version of sql server 2005, and its on a 32 bit pc. theres no way i can install the 64 bit version as my machine wont even run the setup file|||

You should use 64 bit version of asinstancerename utility on 64 bit machine to rename 32bit instances. It is intended to be able to handle 32bit instances.

To get 64bit version of asinstancerename, uninstall 32bit version SQL Tools from your machine and install them back using 64ibt CD.

That should get you going.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Cannot remotely login to SQL Express since last windows update

Since today (after installing the latest Windows Updates !on my local machine!) I cannot login to a SQLExpress instance remotely; stating that it cannot find the server/instance.

The weird thing is: it only happens when I want to login to the non-default instance (sqlexpress 2005) (<IP>\<instance>).

When i'm using the default instance (msde 2000 or sqlexpress 2005 on another machine) (<IP>) it seems to work fine.

Does this have something to do with the windows updates, or is it just a coincedence?

Thanks in advance,

Remco RosThis is probably due to the update changed your setting. Just check your firewall on the server and put sqlbrowser.exe or UDP port 1434 to exception. Also make sure your sqlbrowser is running.|||we didn't install the updates on the server (yet) only on the client, so it must be a client thing.

Server:
Win 2003 / SQL Express 2005
Tcp/ip / named pipes: yes
sqlbrowser running
firewall exception on 1434udp 1433tcp.

tested on these client(s):
Local (without latest updates): CAN connect
XP Home with SQL Server Management studio (with lates windows updates): CANNOT connect
XP Pro with SQL Server Management studio Express (with lates windows updates): CANNOT connect
Win 2003 with SQL Server Management studio Express

(WITHOUT lates windows updates): CAN connect.

I see a pattern here...|||Are you sure your SQL Express listens on TCP port 1433 since your put 1433 in exception? What's the result if you run "telnet yourserver sql_tcp_port"? Can it connect? Could it be possible that IPSEC blocked the traffic between the problem machine if the IPSEC is on?

Cannot remotely connect on SQL Server Instances by name.

Hi all,

On my computer I have installed two instances of SQL Server 2000. The first one is the default instance of SQL Server Personal Edition and the second one is an MSDE instance.

From other PCs on the company LAN I can connect, by name, only to the first one and not to the MSDE instance.

I have tried the combination IP Address, TCP Port and it work fine.

Anyone any ideas?

Thanks in advance,

Stavros Makridis.

did you get this fixed ever?|||

Hi,

the named instance is accessible with MachineName\InstanceName,PortNumber in SQL Server 2000.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||

Jens K. Suessmeyer wrote:

Hi,

the named instance is accessible with MachineName\InstanceName,PortNumber in SQL Server 2000.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

If tcp port is specified in the connection string, the instance name value is ignored.|||UDP port 1434 must be blocked somehow. SQL Browser needs this port to resolve srv\instance to a valid server:tcp_port.|||He is using SQL 2000, so no SQL Browser.|||

Yes there is. Browser is handled by the first instance of sqlserver internally.

|||

I wasn′t aware of that, do you have some links about this topic and this internal feature ?

|||You can find it in bol and on technet.

Here is an excerpt from bol (ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/3cc00d3a-487c-4cd9-a155-655f02485fa0.htm):
"Background

Prior to Microsoft SQL Server 2000, only one instance of SQL Server could be installed on a computer. SQL Server listened for incoming requests on port 1433, assigned to SQL Server by the official Internet Assigned Numbers Authority (IANA). Only one instance of SQL Server can use a port, so when SQL Server 2000 introduced support for multiple instances of SQL Server, SQL Server Resolution Protocol (SSRP) was developed to listen on UDP port 1434. This listener service responded to client requests with the names of the installed instances, and the ports or named pipes used by the instance. To resolve limitations of the SSRP system, SQL Server 2005 introduces the SQL Server Browser service as a replacement for SSRP."

Cannot remotely connect on SQL Server Instances by name.

Hi all,

On my computer I have installed two instances of SQL Server 2000. The first one is the default instance of SQL Server Personal Edition and the second one is an MSDE instance.

From other PCs on the company LAN I can connect, by name, only to the first one and not to the MSDE instance.

I have tried the combination IP Address, TCP Port and it work fine.

Anyone any ideas?

Thanks in advance,

Stavros Makridis.

did you get this fixed ever?|||

Hi,

the named instance is accessible with MachineName\InstanceName,PortNumber in SQL Server 2000.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

Jens K. Suessmeyer wrote:

Hi,

the named instance is accessible with MachineName\InstanceName,PortNumber in SQL Server 2000.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

If tcp port is specified in the connection string, the instance name value is ignored.|||UDP port 1434 must be blocked somehow. SQL Browser needs this port to resolve srv\instance to a valid server:tcp_port.|||He is using SQL 2000, so no SQL Browser.|||

Yes there is. Browser is handled by the first instance of sqlserver internally.

|||

I wasn′t aware of that, do you have some links about this topic and this internal feature ?

|||You can find it in bol and on technet.

Here is an excerpt from bol (ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/3cc00d3a-487c-4cd9-a155-655f02485fa0.htm):
"Background

Prior to Microsoft SQL Server 2000, only one instance of SQL Server

could be installed on a computer. SQL Server listened for incoming requests on

port 1433, assigned to SQL Server by the official Internet Assigned Numbers

Authority (IANA). Only one instance of SQL Server can use a port, so when SQL

Server 2000 introduced support for multiple instances of SQL Server, SQL Server

Resolution Protocol (SSRP) was developed to listen on UDP port 1434. This

listener service responded to client requests with the names of the installed

instances, and the ports or named pipes used by the instance. To resolve

limitations of the SSRP system, SQL Server 2005 introduces the SQL Server

Browser service as a replacement for SSRP."

Cannot Remotely Access SQL Server Standard Named Instance

Good Day,

I am creating a SQL Named instance as a testing environment. This instance is on the same physical box as my Development environment, both are SQL 2005 standard edition. From the server in Management Studio, I can load, and interact with both instances. From a remote connection (e.g., my pc) I cannot access the named instance. I am getting the following:

Connect to Server

X Cannot connect to <server>\<named instance>

Additional Information

An error has occured while establishing a connection to the server. When connecting to SQL Sever 2006, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)(Microsoft SQL Server)

I have checked, and rechecked the server settings for this named instance, and remote connections are set to "allow" I have enabled TCPIP and Named Pipes prototocals, and have ensured that my firewall is allowing the "listenting port" for the named instance, and have even tried turning off my XP firewall during testing.

I am sure that I have probably missed something, and have searched the community but only have been able to find resolutions that I have already tried. Is there more?

Thanks in advance for any help and guidance you can provide.

hi mt,

please be guided by this article

http://forums.microsoft.com/MSDN/AddPost.aspx?PostID=807492&SiteID=1

regards,

joey

|||" error: 26 - Error

Locating Server/Instance Specified", it means that it's trying to

locate the SQL Server using SSRP but could not get contact with SQL

Browser. So, please make sure your SQL Browser is running.

|||Yes, that is absolutely it. I did not set up the Browser Severvice to run. Thank you.

Cannot Register the server

I've installed an Instance of MSDE on a Win2k Machine and and WinXP Machine.
I'm able to register the Instances locally through EM (v.8.0), but when I
try to register them from a different PC with EM on it, I get the following
error.
SQL Server does not exist or access is denied. ConnectionOpen (Connect()
Is MSDE limited to local Enterprise Management?
Wack
This message will self destruct.
hi Ray,
Ray Lewis wrote:
> I've installed an Instance of MSDE on a Win2k Machine and and WinXP
> Machine. I'm able to register the Instances locally through EM
> (v.8.0), but when I try to register them from a different PC with EM
> on it, I get the following error.
> SQL Server does not exist or access is denied. ConnectionOpen
> (Connect()
> Is MSDE limited to local Enterprise Management?
please verify the network protocols are enabled via Server Network Utility
(svrnetcn.exe)...
MSDE installs by default disabling network protocols in order to prevent
external connections/attacks... you have to provide the
DISABLENETWORKPROTOCOLS=0
parameter at install time in order to force network protocols to be enable,
or, later afte install, use svrnetcn.exe to enable and configure the desired
protocol
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks. I finally discovered that. Also, on XP SP2, you need to allow port
1433 through the firewall.
Wack
This message will self destruct.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:38p2mrF5riea7U1@.individual.net...
> hi Ray,
> Ray Lewis wrote:
> please verify the network protocols are enabled via Server Network Utility
> (svrnetcn.exe)...
> MSDE installs by default disabling network protocols in order to prevent
> external connections/attacks... you have to provide the
> DISABLENETWORKPROTOCOLS=0
> parameter at install time in order to force network protocols to be
enable,
> or, later afte install, use svrnetcn.exe to enable and configure the
desired
> protocol
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>

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

Cannot register a local instance

I have SQL Server 2000 installed, client tools only. I can
access the SQL Server on my network and various remote SQL
boxes but I cannot register a local instance.
I keep getting the "SQL Server does not exist or access
denied error message".
Any advice?If you have only the client tools installed locally, you won't be able to
connect to a local instance because there's no local instance. You need to
install the actual engine to be able to connect locally. However, if you
have sql installed locally and you can't connect, make sure the service is
running. You can check this out in the services applet in administrative
tools.
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 programming by Example
"Rich" <anonymous@.discussions.microsoft.com> wrote in message
news:67db01c3e422$2409f840$7d02280a@.phx.gbl...

quote:

---

> I have SQL Server 2000 installed, client tools only. I can
> access the SQL Server on my network and various remote SQL
> boxes but I cannot register a local instance.
> I keep getting the "SQL Server does not exist or access
> denied error message".
> Any advice?

---

|||Thanks for that.
I have run a local instance of SQL server on a stand alone
machine in the past, SQL 7 was also installed though.
I need to be able to use SQL server offline at home on my
laptop. Any suggestions?
No SQL services apparently running locally.

quote:

---

>--Original Message--
>If you have only the client tools installed locally, you

---

won't be able to

quote:

---

>connect to a local instance because there's no local

---

instance. You need to

quote:

---

>install the actual engine to be able to connect locally.

---

However, if you

quote:

---

>have sql installed locally and you can't connect, make

---

sure the service is

quote:

---

>running. You can check this out in the services applet in

---

administrative

quote:

---

>tools.
>--
>Carlos E. Rojas
>SQL Server MVP
>Co-Author SQL Server 2000 programming by Example
>
>"Rich" <anonymous@.discussions.microsoft.com> wrote in

---

message

quote:

---

>news:67db01c3e422$2409f840$7d02280a@.phx.gbl...
can[QUOTE]
SQL[QUOTE]
>
>.
>

---

|||What version of windows are you running? You could try sql 2000 desktop
edition or developer edition. You can find more info on
www.microsoft.com/sql
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 programming by Example
<anonymous@.discussions.microsoft.com> wrote in message
news:490501c3e42a$7e056cf0$a501280a@.phx.gbl...[QUOTE]
> Thanks for that.
> I have run a local instance of SQL server on a stand alone
> machine in the past, SQL 7 was also installed though.
> I need to be able to use SQL server offline at home on my
> laptop. Any suggestions?
> No SQL services apparently running locally.
> won't be able to
> instance. You need to
> However, if you
> sure the service is
> administrative
> message
> can
> SQL|||Windows 2000 Professional SP3, that is why I could only
install client tools. Desktop edition still cannot find a
local instance to install from.
SQL server 7 would allow a local instance even when not
installed on a server. There must be a way to run an
offline/stand alone version of SQL Server 2000?

quote:

---

>--Original Message--
>What version of windows are you running? You could try

---

sql 2000 desktop

quote:

---

>edition or developer edition. You can find more info on
>www.microsoft.com/sql
>--
>Carlos E. Rojas
>SQL Server MVP
>Co-Author SQL Server 2000 programming by Example
>
><anonymous@.discussions.microsoft.com> wrote in message
>news:490501c3e42a$7e056cf0$a501280a@.phx.gbl...
alone[QUOTE]
my[QUOTE]
you[QUOTE]
locally.[QUOTE]
in[QUOTE]
I[QUOTE]
remote[QUOTE]
access[QUOTE]
>
>.
>

---

|||MSDE (desktop edition), personal edition, or developer edition should
install on a non-server edition of Windows. If you're getting an error
installing SQL Server you can post the exact error and sqlstp.log to the
setup newsgroup. If you're installing MSDE there is a slipstreamed version
that includes SP3, otherwise install the RTM version then immediately apply
SP3. Then apply the latest security rollup for SQL Server.
122352 INF: Supported Windows Versions for SQL Server
http://support.microsoft.com/?id=122352
SQL Server 2000 Evaluation Edition and Developer Edition can run on the
following operating systems:
Operating systems listed above for Enterprise and Standard Editions
Windows XP Professional
Windows XP Home Edition
Windows 2000 Professional
Windows NT Workstation 4.0 with SP5 or later
SQL Server 2000 Personal Edition and SQL Server 2000 Desktop Engine (MSDE)
can run on the following operating systems:
Operating systems listed above for Enterprise, Standard, Evaluation, and
Developer Editions
Windows Server 2003, Web Edition1 (MSDE only)
Windows 98
Windows Millennium Edition (Windows Me)
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

Cannot install Sql 2005 SP2, Error: Your Account information Could not be verified

Hi all,

I am running a named instance of SQL Server 2005 Enterprise Edition, side by side with named instance of SQL Server 2000 in Windows Server 2003. When I start the installation. I am unable to proceed from authentication stage.

The error description for Database Services and Reporting Services under both sa and windows authentication mode is: Encryption not supported on client Sqlcmd error: Microsoft SQL Native client: Client Unable to establish connection

In Service Manager, all SQL Server 2005 services are running with Logon as Administrator, and I am also able to connect to SSAS, SSRS, SSIS via Management studio both via Windows authentication and sa account information.

Would you please inform if I have to change any security settings before SP2 installation here.

How to add myself a Sql Server Administrator. The link in Surface Area Configuration to Add new Administrator doesn't work.

Hi,

I tried repairing the Sql Server Native Client via Add/ Remove Programs. After successfully repairing, SP2 installation went fine.

Thanks

Subhash Subramanyam

|||

Hi,

I 'm having the same trouble. I've just tired to repair instalation of SQL NativeClient, but the resupl is still the same.

In part of instalation in verifing of accounts , there is status "Login failed".

I'm not able to solve this issue. Please , encounter somebody this trouble?

|||

Hi Barlo,

Are you using a local account (Windows authentication), If so then make sure you have NT Administrator privileges while installing. In my case I run all the services under local account. If you are doing the same, verify the type of account installed. Run Services.msc -> For all the Sql 2005 Services running -> properties -> log on with local account. Make sure that you are able to connect to all the services.

Still if you face error during authentication mode, Please look at the error instructions on the third column in the table on authentication modes for list of services, after it prompts the error. e.g: Table might show that Reporting Services and Database cannot connect, since native client failed..

Cannot install Sql 2005 SP2, Error: Your Account information Could not be verified

Hi all,

I am running a named instance of SQL Server 2005 Enterprise Edition, side by side with named instance of SQL Server 2000 in Windows Server 2003. When I start the installation. I am unable to proceed from authentication stage.

The error description for Database Services and Reporting Services under both sa and windows authentication mode is: Encryption not supported on client Sqlcmd error: Microsoft SQL Native client: Client Unable to establish connection

In Service Manager, all SQL Server 2005 services are running with Logon as Administrator, and I am also able to connect to SSAS, SSRS, SSIS via Management studio both via Windows authentication and sa account information.

Would you please inform if I have to change any security settings before SP2 installation here.

How to add myself a Sql Server Administrator. The link in Surface Area Configuration to Add new Administrator doesn't work.

Hi,

I tried repairing the Sql Server Native Client via Add/ Remove Programs. After successfully repairing, SP2 installation went fine.

Thanks

Subhash Subramanyam

|||

Hi,

I 'm having the same trouble. I've just tired to repair instalation of SQL NativeClient, but the resupl is still the same.

In part of instalation in verifing of accounts , there is status "Login failed".

I'm not able to solve this issue. Please , encounter somebody this trouble?

|||

Hi Barlo,

Are you using a local account (Windows authentication), If so then make sure you have NT Administrator privileges while installing. In my case I run all the services under local account. If you are doing the same, verify the type of account installed. Run Services.msc -> For all the Sql 2005 Services running -> properties -> log on with local account. Make sure that you are able to connect to all the services.

Still if you face error during authentication mode, Please look at the error instructions on the third column in the table on authentication modes for list of services, after it prompts the error. e.g: Table might show that Reporting Services and Database cannot connect, since native client failed..

Cannot install or uninstall

We have a 2003 server with SQL Server 2005.
Our instance in SRS was playing up basically so I uninstalled it.
When I now try to reinstall via the original CD it still thinks the product
is installed. If I try to uninstall it tells me no features have changed
and exits.
When I try to reinstall or uninstall via control panel and changing the
items installed and that gives me an error of "Could not find a package to
install on the installation media".
Any help would be appreciated.
ChubblyI have now completely removed the instance of SQL Server, run a registry
cleaner to remove any erroneous entries and then tried to reinstall SQL
Server. It still thinks however that Reporting Services are already there.
I continued with the installation which threw up numerous other errors,
installed the SQL 2005 patch from Microsoft update and then tried to change
the installed components of SQL Server. To no avail. I still receive
"Could not find a package to install on the installation media".
If I try to manually run the SqlRun_RS.msi file I get the following error:
"An instance with the same name is already installed on this computer. To
proceed with SQL Server Setup, provide a unique instance name."
I'm stumped and don't particularly want to have to rebuild the whole server.
Chubbly
"Chubbly Geezer" <chubbly_geezer@.newsgroup.nospam> wrote in message
news:eyJQY9wPHHA.4484@.TK2MSFTNGP02.phx.gbl...
> We have a 2003 server with SQL Server 2005.
> Our instance in SRS was playing up basically so I uninstalled it.
> When I now try to reinstall via the original CD it still thinks the
> product is installed. If I try to uninstall it tells me no features have
> changed and exits.
> When I try to reinstall or uninstall via control panel and changing the
> items installed and that gives me an error of "Could not find a package to
> install on the installation media".
> Any help would be appreciated.
> Chubbly
>
>

Cannot Initialize RS

Hi All
I'm having some problem to initialize a RS Instance, backup, restore, change
or delete Encryption Keys. The RS reports the following error message:
"ReportServicesConfigUI.WMIProvider.WMIProviderException: Cannot decrypt the
Configuration Encrypteds Value for "LogonCred".
(rsFailedToDecryptConfigInformation)
in
ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.ThrowOnError(ManagementBaseObject
mo)
en
ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.RestoreEncryptionKey(Byte[]
encryptedBytes, String password)"
This issue avoid me to implement some reports I made by Business
Intelligence Development Studio.
Thanks in advance.Hello Tiempo,
Based on my research, you should respecify a domain user as the excution
account in the reporting services configuration.
If this still could not resolved the problem, please check the report
services error log file to see are there any detailed error logs.
By default, the log file is located at \Microsoft SQL Server\<SQL Server
Instance>\Reporting Services\LogFiles.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||Thank you very much, Wei Lu.
I'll test it next week due to technical reasons.
Arturo Carrión
.Net & Sql Server Developer at
Tiempo Soluciones Informáticas
"Wei Lu [MSFT]" <weilu@.online.microsoft.com> escribió en el mensaje
news:MEt$kSfOHHA.2300@.TK2MSFTNGHUB02.phx.gbl...
> Hello Tiempo,
> Based on my research, you should respecify a domain user as the excution
> account in the reporting services configuration.
> If this still could not resolved the problem, please check the report
> services error log file to see are there any detailed error logs.
> By default, the log file is located at \Microsoft SQL Server\<SQL Server
> Instance>\Reporting Services\LogFiles.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications.
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> http://msdn.microsoft.com/subscriptions/support/default.aspx.
> ==================================================> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>|||Hi Wei, I solve the problem but by another way. I navigated through the MSDN
and I found the rsconfig utility that I had been run by a comman line, whit
this utility I regenerated the private keys and I could initialize my RS.
Thanks, in any case..
<tiempotecnologia@.newsgroup.nospam> escribió en el mensaje
news:eNRbXZwOHHA.320@.TK2MSFTNGP06.phx.gbl...
> Thank you very much, Wei Lu.
> I'll test it next week due to technical reasons.
> Arturo Carrión
> .Net & Sql Server Developer at
> Tiempo Soluciones Informáticas
> "Wei Lu [MSFT]" <weilu@.online.microsoft.com> escribió en el mensaje
> news:MEt$kSfOHHA.2300@.TK2MSFTNGHUB02.phx.gbl...
>> Hello Tiempo,
>> Based on my research, you should respecify a domain user as the excution
>> account in the reporting services configuration.
>> If this still could not resolved the problem, please check the report
>> services error log file to see are there any detailed error logs.
>> By default, the log file is located at \Microsoft SQL Server\<SQL Server
>> Instance>\Reporting Services\LogFiles.
>> Sincerely,
>> Wei Lu
>> Microsoft Online Community Support
>> ==================================================>> Get notification to my posts through email? Please refer to
>> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
>> ications.
>> Note: The MSDN Managed Newsgroup support offering is for non-urgent
>> issues
>> where an initial response from the community or a Microsoft Support
>> Engineer within 1 business day is acceptable. Please note that each
>> follow
>> up response may take approximately 2 business days as the support
>> professional working with you may need further investigation to reach the
>> most efficient resolution. The offering is not appropriate for situations
>> that require urgent, real-time or phone-based interactions or complex
>> project analysis and dump analysis issues. Issues of this nature are best
>> handled working with a dedicated Microsoft Support Engineer by contacting
>> Microsoft Customer Support Services (CSS) at
>> http://msdn.microsoft.com/subscriptions/support/default.aspx.
>> ==================================================>> (This posting is provided "AS IS", with no warranties, and confers no
>> rights.)
>|||Hello Tiempo,
Glad to hear that you resolved this issue bu regenerated the private key.
If you have any questions, please feel free to let me know.
Sincerely yours,
Wei Lu
Microsoft Online Partner Support
=====================================================
PLEASE NOTE: The partner managed newsgroups are provided to assist with
break/fix
issues and simple how to questions.
We also love to hear your product feedback!
Let us know what you think by posting
- from the web interface: Partner Feedback
- from your newsreader: microsoft.private.directaccess.partnerfeedback.
We look forward to hearing from you!
======================================================When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================

Cannot Initialize Report Server

Hi,
Trying to initialize a new instance of Reporting Services on SQL Server
2005. I've setup every part of it up to the Initialization. When I
click on initialization I get the below error. I've checked the
services on the machine and the RPC service is certainly running as is
the Report Server service. Any thoughts?
Thanks,
Bill
--
Reporting Services Configuration Manager
--
There was an error while switching panels. The most likely cause is an
error retrieving WMI properties. The exception details are:
An error occurred when attempting to connect to the report server
remote procedure call (RPC) end point. Verify that the Report Server
Windows service is running, and then retry the operation.
Details:
The RPC server is not listening. (Exception from HRESULT: 0x800706B3)
--
OK
--One other note. Both database and website are on the same server.
zinck74 wrote:
> Hi,
> Trying to initialize a new instance of Reporting Services on SQL Server
> 2005. I've setup every part of it up to the Initialization. When I
> click on initialization I get the below error. I've checked the
> services on the machine and the RPC service is certainly running as is
> the Report Server service. Any thoughts?
> Thanks,
> Bill
>
> --
> Reporting Services Configuration Manager
> --
> There was an error while switching panels. The most likely cause is an
> error retrieving WMI properties. The exception details are:
> An error occurred when attempting to connect to the report server
> remote procedure call (RPC) end point. Verify that the Report Server
> Windows service is running, and then retry the operation.
> Details:
> The RPC server is not listening. (Exception from HRESULT: 0x800706B3)
> --
> OK
> --

Cannot generate SSPI context

Hi,
Im having trouble connecting to the SQL2005 default instance installed on
one of my sql servers within my domain. I have a second SQL2005 server that
I
can connect to just fine. Both are in the same OU.
This particular server, I can connect to AS2005, but not to SQL2005. I keep
getting the 'Cannot generate SSPI context. (.Net SqlClient Data Provider)'
error. I've not changed anything in terms of settings on my PC, nor have any
settings been changed on the SQL server, though I was able to connect to
SQL2005 for this server last week. Something obviously has changed, but I
have no idea where to look. One of the other SysAdmins has no problems
connecting to the database.
I'm hoping this is just something simple to fix.
regards,
AnatoliAll the below is happening while I'm attempting to connect remotely from my
XP SP2 pc using SSMS.
Further to this, I've found that I can connect to the server in question
remotely using the SA account. I can also, connect to SQL2005 locally with m
y
network account from within an RDP session.
"Anatoli" wrote:

> Hi,
> Im having trouble connecting to the SQL2005 default instance installed on
> one of my sql servers within my domain. I have a second SQL2005 server tha
t I
> can connect to just fine. Both are in the same OU.
> This particular server, I can connect to AS2005, but not to SQL2005. I kee
p
> getting the 'Cannot generate SSPI context. (.Net SqlClient Data Provider)'
> error. I've not changed anything in terms of settings on my PC, nor have a
ny
> settings been changed on the SQL server, though I was able to connect to
> SQL2005 for this server last week. Something obviously has changed, but I
> have no idea where to look. One of the other SysAdmins has no problems
> connecting to the database.
> I'm hoping this is just something simple to fix.
> regards,
> Anatoli|||Anatoli,
check these links.
http://support.microsoft.com/kb/811889/
http://msdn2.microsoft.com/en-us/library/ms191153.aspx
http://msdn2.microsoft.com/en-us/library/ms189585.aspx
Hope this helps
Markus|||Markus,
Thanks for your reply. From what I can tell, this problem is specific to my
domain account. That is that I can connect remotely to the SQL server using
the SA account, but I can't connect using my domain account. I tried using
another PC from which one of other admins was able to easily connect to
SQL2005. I don't use a roaming profile, and this was the first time I logged
onto that PC and still I got the same error. Again, when I logged in locally
to the SQL server I didn't have any problems SSMS connecting.
So from what I can tell, there aren't any setting issues on the SQL server
side nor are there any issues from my PC side as I'm able to connect to othe
r
instances of SQL 2005 with my domain account.
Are there any settings associated with the login to cause such an error?
"MarkusB" wrote:

> Anatoli,
> check these links.
> http://support.microsoft.com/kb/811889/
> http://msdn2.microsoft.com/en-us/library/ms191153.aspx
> http://msdn2.microsoft.com/en-us/library/ms189585.aspx
> Hope this helps
> Markus
>|||Turned out to be how the system guys upgraded the server to W2K3, SQL and AS
2005. They blew away the old sql server and installed W2K3, SQL/AS 2005, but
never removed the computer object out of AD. Used the SETSPN.exe utility
determine that there was more than one SPN for that particular server.
regards,
"Anatoli" wrote:
[vbcol=seagreen]
> Markus,
> Thanks for your reply. From what I can tell, this problem is specific to m
y
> domain account. That is that I can connect remotely to the SQL server usin
g
> the SA account, but I can't connect using my domain account. I tried using
> another PC from which one of other admins was able to easily connect to
> SQL2005. I don't use a roaming profile, and this was the first time I logg
ed
> onto that PC and still I got the same error. Again, when I logged in local
ly
> to the SQL server I didn't have any problems SSMS connecting.
> So from what I can tell, there aren't any setting issues on the SQL server
> side nor are there any issues from my PC side as I'm able to connect to ot
her
> instances of SQL 2005 with my domain account.
> Are there any settings associated with the login to cause such an error?
> "MarkusB" wrote:
>

Cannot generate SSPI context

Hi,
Im having trouble connecting to the SQL2005 default instance installed on
one of my sql servers within my domain. I have a second SQL2005 server that I
can connect to just fine. Both are in the same OU.
This particular server, I can connect to AS2005, but not to SQL2005. I keep
getting the 'Cannot generate SSPI context. (.Net SqlClient Data Provider)'
error. I've not changed anything in terms of settings on my PC, nor have any
settings been changed on the SQL server, though I was able to connect to
SQL2005 for this server last week. Something obviously has changed, but I
have no idea where to look. One of the other SysAdmins has no problems
connecting to the database.
I'm hoping this is just something simple to fix.
regards,
AnatoliAll the below is happening while I'm attempting to connect remotely from my
XP SP2 pc using SSMS.
Further to this, I've found that I can connect to the server in question
remotely using the SA account. I can also, connect to SQL2005 locally with my
network account from within an RDP session.
"Anatoli" wrote:
> Hi,
> Im having trouble connecting to the SQL2005 default instance installed on
> one of my sql servers within my domain. I have a second SQL2005 server that I
> can connect to just fine. Both are in the same OU.
> This particular server, I can connect to AS2005, but not to SQL2005. I keep
> getting the 'Cannot generate SSPI context. (.Net SqlClient Data Provider)'
> error. I've not changed anything in terms of settings on my PC, nor have any
> settings been changed on the SQL server, though I was able to connect to
> SQL2005 for this server last week. Something obviously has changed, but I
> have no idea where to look. One of the other SysAdmins has no problems
> connecting to the database.
> I'm hoping this is just something simple to fix.
> regards,
> Anatoli|||Anatoli,
check these links.
http://support.microsoft.com/kb/811889/
http://msdn2.microsoft.com/en-us/library/ms191153.aspx
http://msdn2.microsoft.com/en-us/library/ms189585.aspx
Hope this helps
Markus|||Markus,
Thanks for your reply. From what I can tell, this problem is specific to my
domain account. That is that I can connect remotely to the SQL server using
the SA account, but I can't connect using my domain account. I tried using
another PC from which one of other admins was able to easily connect to
SQL2005. I don't use a roaming profile, and this was the first time I logged
onto that PC and still I got the same error. Again, when I logged in locally
to the SQL server I didn't have any problems SSMS connecting.
So from what I can tell, there aren't any setting issues on the SQL server
side nor are there any issues from my PC side as I'm able to connect to other
instances of SQL 2005 with my domain account.
Are there any settings associated with the login to cause such an error?
"MarkusB" wrote:
> Anatoli,
> check these links.
> http://support.microsoft.com/kb/811889/
> http://msdn2.microsoft.com/en-us/library/ms191153.aspx
> http://msdn2.microsoft.com/en-us/library/ms189585.aspx
> Hope this helps
> Markus
>|||Turned out to be how the system guys upgraded the server to W2K3, SQL and AS
2005. They blew away the old sql server and installed W2K3, SQL/AS 2005, but
never removed the computer object out of AD. Used the SETSPN.exe utility
determine that there was more than one SPN for that particular server.
regards,
"Anatoli" wrote:
> Markus,
> Thanks for your reply. From what I can tell, this problem is specific to my
> domain account. That is that I can connect remotely to the SQL server using
> the SA account, but I can't connect using my domain account. I tried using
> another PC from which one of other admins was able to easily connect to
> SQL2005. I don't use a roaming profile, and this was the first time I logged
> onto that PC and still I got the same error. Again, when I logged in locally
> to the SQL server I didn't have any problems SSMS connecting.
> So from what I can tell, there aren't any setting issues on the SQL server
> side nor are there any issues from my PC side as I'm able to connect to other
> instances of SQL 2005 with my domain account.
> Are there any settings associated with the login to cause such an error?
> "MarkusB" wrote:
> > Anatoli,
> >
> > check these links.
> > http://support.microsoft.com/kb/811889/
> >
> > http://msdn2.microsoft.com/en-us/library/ms191153.aspx
> > http://msdn2.microsoft.com/en-us/library/ms189585.aspx
> >
> > Hope this helps
> >
> > Markus
> >
> >

Cannot find SQLResourceLoader.dll

We have a server with the default instance and 2 addtional named instances running SQL 2000 SP4. I attempted to install another instance for SQL 2005 and promptly ran into the above error when running DTS packages on the default SQL 2000 instance.

The legacy components had been installed and the server had been re-started. I also tried re-registering the dll as suggested on another forum post.

Any ideas on what I could do to get around this problem? We need to keep our existing SQL 2000 installs as is until we have a SQL 2005 server setup ready to take over the workload with absolute minimal downtime.

Thanks
Phill
mailto:philcart@.gmail.com
http://www.philcart.net/blog
http://www.sqlserver.org.au/user/bio/ViewBio.aspx?bioId=46
http://www.sqlservercentral.com/forums/userinfo.aspx?id=5534

Phil, did you hit any issues installing the legacy components from the SQL 2005 tools package? This typically is the fix for this issue.

Thanks,
Sam Lester (MSFT)

|||

No errors were reported during the install.

Over the weekend I had a chance to perform a couple of install/uninstalls. I actually did it 4 times and it failed on the 1st and 3rd times.

Guess there is something shaky there.

Cannot find my default instance

Hi,

I'm using SQL server 200 Personal Edition. I had a named instance created at the time of installation and a default instance later. Now my default instance crashed and I want to rebuild my master db. But neither can I find my default instance in the drop down in the rebuildm dialog box (Only the named instance is present) nor is it allowing me to edit the server name in the drop down. What should I do?

Thanks in advance.

Each instance has its own set of services. Look for the name following the $ in the service name, or the value in () depending on your installation and OS.

Cannot find folder "\Maintenance Plans".

I've been looking for treads with a possible similar problem but thus far nothing.

I recently upgraded SQL 2000 (STD ed.) instance to SQL 2005 (STD ed.).

This includes the db's. All their compatibility levels were changed to level 90 (SQL 2005).

Everything seems to be working fine but when trying to migrate a legacy maintenance plan I keep getting the message, "Cannot find folder "\Maintenance Plans"." even though the folder is clearly listed.

Not sure where to start. I have created two virtual images and both have the same problem.

Any help would be greatly appreciated.

RoviWil

I still can't find anyone who had this problem and yet I got it in multiple tests.

I did however manage to use a workaround by means of system sp's.

I used SQL Profiler.

Verify that the folder is missing:
exec sp_executesql N'exec [msdb].[dbo].[sp_dts_getfolder] @.P1, @.P2',N'@.P1 nvarchar(17),@.P2 uniqueidentifier',N'Maintenance Plans','00000000-0000-0000-0000-000000000000'

Add the folder if missing:
exec sp_dts_addfolder '00000000-0000-0000-0000-000000000000','Maintenance Plans','08AA12D5-8F98-4DAB-A4FC-980B150A5DC8'

|||You for got to mention that you must do these commands from the using the msdb database. Took me 45 minutes to figure it out. I thought thier was a problem with the upgrade of my database so I compared all of the objects in a known good 2005 database to the converted one.

But thanks for the info anyway I would never ever have figured it out without it.|||

Hi,

I'm having the same problem, and I've found your post on several sites, that all lead back to your post as the only fix right now. I saw on connections were it's accepted as a bug, but no resolution yet.

What I need help with, and I know this sound really stupid, but I don't understand how to use Profiler to run a SP. I know how to create one, and how to execute it either from Studio or a query or VB, but I don't understand how to execute one from Profier and apparently you have to do it from there because I've tried creating that as a stored procedure from the MSDB Database, and it throws an error and I still have the same problem.

I can get the lookup to run, and it comes back blank, but the create throws another expection error, now it comes back that I have a duplicate key.

Msg 2627, Level 14, State 1, Procedure sp_dts_addfolder, Line 14

Violation of UNIQUE KEY constraint 'U_sysdtspackagefolders90uniquepath'. Cannot insert duplicate key in object 'dbo.sysdtspackagefolders90'.

The statement has been terminated.

(1 row(s) affected)

Any help would be appreciated.

|||

Hi tropics43!

I just had exactly the same problem as you describe.... obviously the folder with the id '08AA12D5-8F98-4DAB-A4FC-980B150A5DC8' was already in the according msdb table.... check it out:

SELECT * FROM msdb.dbo.sysdtspackagefolders90

you will see that the folderid exists but has (for whatever reason...) the wrong name, not 'Maintenance Plans'. You can repair this by just using this statement:

UPDATE msdb.dbo.sysdtspackagefolders90
SET foldername = 'Maintenance Plans'
WHERE folderid='08AA12D5-8F98-4DAB-A4FC-980B150A5DC8'

It worked for me perfectly fine... after that maintenance plans can be created again....

Best regards,
Wolfgang