Tuesday, March 27, 2012
Cannot register server (LOCAL)
However, I get the following message. I still can register other servers
using ip addresses though.
================================================== ===
Cannot connect to (LOCAL).
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: TCP Provider, error: 0 - No connection could be made because the
target machine actively refused it.) (Microsoft SQL Server, Error: 10061)
================================================== ===
Hi,
To let me better understand your issue, could you please let me know the
following questions:
1. Did you mean registering server named (local) or a database?
2. How did you perform the registration?
3. Why would you like to register a (local) server (database?) ?
From the error message, it seemed that you were trying to register a
(local) server remotely. "(local)" is preserved keyword for the default
instance of local SQL Server. You can only use it to locally connect to
your default instance of your SQL Server not remotely. Generally it is no
need to register a (local) server, if you want to rename a SQL server
instance, you can use sp_dropserver/sp_addserver stored procedures. You may
refer to:
How to: Rename a Computer that Hosts a Stand-Alone Instance of SQL Server
2005
http://technet.microsoft.com/en-us/library/ms143799.aspx
Anyway I think that I have not totally understood your scenario. If there
is any misunderstanding, I appreciate your pointing and kindly making some
further explanation.
Thanks and have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ===
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.
================================================== ====
|||Yes, But no luck on that too.
test
"Tibor Karaszi" wrote:
> did you try localhost?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "rkbnair" <rkbnair@.community.nospam> wrote in message
> news:5439BC07-3618-4DC5-99BB-7957915C6894@.microsoft.com...
>
>
|||Under the registered servers I see the following:
3tsd3b1
3tsd3b1\sqlexpress (which I can connect to successfully)
Under the Server Group I see the following items:
(LOCAL)
10.100.1.67 (which I can connect to successfully))
3TSSD3B1\SQLEXPRESS (which I can connect to successfully)
What should I do to create a database on my local machine.
In other words, what is the equivalent of registering (LOCAL) server in SQL
Server 2000?
"Charles Wang[MSFT]" wrote:
> Hi,
> To let me better understand your issue, could you please let me know the
> following questions:
> 1. Did you mean registering server named (local) or a database?
> 2. How did you perform the registration?
> 3. Why would you like to register a (local) server (database?) ?
> From the error message, it seemed that you were trying to register a
> (local) server remotely. "(local)" is preserved keyword for the default
> instance of local SQL Server. You can only use it to locally connect to
> your default instance of your SQL Server not remotely. Generally it is no
> need to register a (local) server, if you want to rename a SQL server
> instance, you can use sp_dropserver/sp_addserver stored procedures. You may
> refer to:
> How to: Rename a Computer that Hosts a Stand-Alone Instance of SQL Server
> 2005
> http://technet.microsoft.com/en-us/library/ms143799.aspx
> Anyway I think that I have not totally understood your scenario. If there
> is any misunderstanding, I appreciate your pointing and kindly making some
> further explanation.
> Thanks and have a nice day!
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ================================================== ===
> 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.
> ================================================== ====
>
>
>
|||The following services are started:
Server Status (green)
Report Server Virtual Directory (Red)
Report Manager Virtual Directory (red)
Windows Service Identity (Green)
Database Setup (Red)
Encryption Keys (Grey)
Initialization (Grey)
Email settings (Yellow)
Execution Account (Yellow)
test
"Tibor Karaszi" wrote:
> I suggest you first check what SQL Server related services you have installed. From that we can see
> how many instances of SQL Server you installed.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "rkbnair" <rkbnair@.community.nospam> wrote in message
> news:D5D736D2-EFB4-4E02-A37A-7CDE47D5C019@.microsoft.com...
>
|||Hi,
Thanks for your response.
I recommend that you post some screenshots here or or mail them to me
(changliw_at_microsoft_dot_com) so that we can better understand your
issue. Also as Tibor said, please run services.msc from command line and
check what the SQL Server services are listed. The SQL Server service name
is like "SQL Server (<instance name>)" or "MSSQLServer".
Additionally I need to confirm with you several questions for further
research:
a. What is the version of your (local) SQL Server instance, SQL Server 2000
or SQL Server 2005?
b. What is the client tool you use, SQL Server Enterprise Manager or SQL
Server Management Studio?
c. Was "3tsd3b1" the name of your local computer and was "10.100.1.67" the
IP address of your local computer?
Creating a database on your local machine does not mean registering (LOCAL)
server in SQL Server 2000. If you would like to register (LOCAL) server in
SQL Server 2000 (Enterprise Manager ?) , you need to ensure that there is a
SQL Server 2000 default instance (the service name is MSSQLServer in
Services panel) has been installed. Also SQL Server 2000 Enterprise Manager
(EM) cannot manage SQL Server 2005 instance, so if you would like to use
SQL Server 2000 EM to register a SQL Server 2005 instance, it is not
possible to do it. In this case, you have to use SQL Server 2005 Management
Studio (SSMS) to do it.
If there is a SQL Server 2000 default instance installed, you can locally
use either SQL Server 2000 EM or SSMS to connect to it via your computer
name, IP or "(local)" to connect to it. Appreciate your understanding if we
could not cleary understand your issue, it is hard for us to go further.
Thanks for your cooperation and look forward to your response.
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ===
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.
================================================== ====
|||SQL Server (SQLEXPRESS)
SQL Server Active Directory Helper
SQL Server Analysis Services (MSSQLSERVER)
SQL Server Browser
SQL Server Integration Services
SQL Server Reporting Services (MSSQLSERVER)
SQL Server VSS Writer
test
"Tibor Karaszi" wrote:
> What tool did you use to get that list? None of those looks like the name of a SQL Server 2005
> service to me. I suggest you do Run and in there type : services.msc
> This starts the "Services" windows applet. In there you look for services where the name starts with
> SQL Server, such as :
> SQL Server (MSSQLServer)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "rkbnair" <rkbnair@.community.nospam> wrote in message
> news:145F3211-E6D3-4D4F-877B-7F47AE7C7759@.microsoft.com...
>
Cannot register server (LOCAL)
However, I get the following message. I still can register other servers
using ip addresses though.
===================================================== Cannot connect to (LOCAL).
--
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: TCP Provider, error: 0 - No connection could be made because the
target machine actively refused it.) (Microsoft SQL Server, Error: 10061)
=====================================================did you try localhost?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"rkbnair" <rkbnair@.community.nospam> wrote in message
news:5439BC07-3618-4DC5-99BB-7957915C6894@.microsoft.com...
> I'm trying to register the (LOCAL) database using SQL Server authentication.
> However, I get the following message. I still can register other servers
> using ip addresses though.
> =====================================================> Cannot connect to (LOCAL).
> --
> ADDITIONAL INFORMATION:
> An error has occurred while establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by the fact that
> under the default settings SQL Server does not allow remote connections.
> (provider: TCP Provider, error: 0 - No connection could be made because the
> target machine actively refused it.) (Microsoft SQL Server, Error: 10061)
> =====================================================>|||Hi,
To let me better understand your issue, could you please let me know the
following questions:
1. Did you mean registering server named (local) or a database?
2. How did you perform the registration?
3. Why would you like to register a (local) server (database?) ?
From the error message, it seemed that you were trying to register a
(local) server remotely. "(local)" is preserved keyword for the default
instance of local SQL Server. You can only use it to locally connect to
your default instance of your SQL Server not remotely. Generally it is no
need to register a (local) server, if you want to rename a SQL server
instance, you can use sp_dropserver/sp_addserver stored procedures. You may
refer to:
How to: Rename a Computer that Hosts a Stand-Alone Instance of SQL Server
2005
http://technet.microsoft.com/en-us/library/ms143799.aspx
Anyway I think that I have not totally understood your scenario. If there
is any misunderstanding, I appreciate your pointing and kindly making some
further explanation.
Thanks and have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================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.
======================================================|||Yes, But no luck on that too.
--
test
"Tibor Karaszi" wrote:
> did you try localhost?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "rkbnair" <rkbnair@.community.nospam> wrote in message
> news:5439BC07-3618-4DC5-99BB-7957915C6894@.microsoft.com...
> > I'm trying to register the (LOCAL) database using SQL Server authentication.
> > However, I get the following message. I still can register other servers
> > using ip addresses though.
> >
> > =====================================================> > Cannot connect to (LOCAL).
> >
> > --
> > ADDITIONAL INFORMATION:
> >
> > An error has occurred while establishing a connection to the server. When
> > connecting to SQL Server 2005, this failure may be caused by the fact that
> > under the default settings SQL Server does not allow remote connections.
> > (provider: TCP Provider, error: 0 - No connection could be made because the
> > target machine actively refused it.) (Microsoft SQL Server, Error: 10061)
> > =====================================================> >
>
>|||Under the registered servers I see the following:
3tsd3b1
3tsd3b1\sqlexpress (which I can connect to successfully)
Under the Server Group I see the following items:
(LOCAL)
10.100.1.67 (which I can connect to successfully))
3TSSD3B1\SQLEXPRESS (which I can connect to successfully)
What should I do to create a database on my local machine.
In other words, what is the equivalent of registering (LOCAL) server in SQL
Server 2000?
"Charles Wang[MSFT]" wrote:
> Hi,
> To let me better understand your issue, could you please let me know the
> following questions:
> 1. Did you mean registering server named (local) or a database?
> 2. How did you perform the registration?
> 3. Why would you like to register a (local) server (database?) ?
> From the error message, it seemed that you were trying to register a
> (local) server remotely. "(local)" is preserved keyword for the default
> instance of local SQL Server. You can only use it to locally connect to
> your default instance of your SQL Server not remotely. Generally it is no
> need to register a (local) server, if you want to rename a SQL server
> instance, you can use sp_dropserver/sp_addserver stored procedures. You may
> refer to:
> How to: Rename a Computer that Hosts a Stand-Alone Instance of SQL Server
> 2005
> http://technet.microsoft.com/en-us/library/ms143799.aspx
> Anyway I think that I have not totally understood your scenario. If there
> is any misunderstanding, I appreciate your pointing and kindly making some
> further explanation.
> Thanks and have a nice day!
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> =====================================================> 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.
> ======================================================>
>
>|||I suggest you first check what SQL Server related services you have installed. From that we can see
how many instances of SQL Server you installed.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"rkbnair" <rkbnair@.community.nospam> wrote in message
news:D5D736D2-EFB4-4E02-A37A-7CDE47D5C019@.microsoft.com...
> Under the registered servers I see the following:
> 3tsd3b1
> 3tsd3b1\sqlexpress (which I can connect to successfully)
> Under the Server Group I see the following items:
> (LOCAL)
> 10.100.1.67 (which I can connect to successfully))
> 3TSSD3B1\SQLEXPRESS (which I can connect to successfully)
> What should I do to create a database on my local machine.
> In other words, what is the equivalent of registering (LOCAL) server in SQL
> Server 2000?
>
>
> "Charles Wang[MSFT]" wrote:
>> Hi,
>> To let me better understand your issue, could you please let me know the
>> following questions:
>> 1. Did you mean registering server named (local) or a database?
>> 2. How did you perform the registration?
>> 3. Why would you like to register a (local) server (database?) ?
>> From the error message, it seemed that you were trying to register a
>> (local) server remotely. "(local)" is preserved keyword for the default
>> instance of local SQL Server. You can only use it to locally connect to
>> your default instance of your SQL Server not remotely. Generally it is no
>> need to register a (local) server, if you want to rename a SQL server
>> instance, you can use sp_dropserver/sp_addserver stored procedures. You may
>> refer to:
>> How to: Rename a Computer that Hosts a Stand-Alone Instance of SQL Server
>> 2005
>> http://technet.microsoft.com/en-us/library/ms143799.aspx
>> Anyway I think that I have not totally understood your scenario. If there
>> is any misunderstanding, I appreciate your pointing and kindly making some
>> further explanation.
>> Thanks and have a nice day!
>> Best regards,
>> Charles Wang
>> Microsoft Online Community Support
>> =====================================================>> 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.
>> ======================================================>>
>>|||The following services are started:
Server Status (green)
Report Server Virtual Directory (Red)
Report Manager Virtual Directory (red)
Windows Service Identity (Green)
Database Setup (Red)
Encryption Keys (Grey)
Initialization (Grey)
Email settings (Yellow)
Execution Account (Yellow)
--
test
"Tibor Karaszi" wrote:
> I suggest you first check what SQL Server related services you have installed. From that we can see
> how many instances of SQL Server you installed.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "rkbnair" <rkbnair@.community.nospam> wrote in message
> news:D5D736D2-EFB4-4E02-A37A-7CDE47D5C019@.microsoft.com...
> > Under the registered servers I see the following:
> > 3tsd3b1
> > 3tsd3b1\sqlexpress (which I can connect to successfully)
> >
> > Under the Server Group I see the following items:
> > (LOCAL)
> > 10.100.1.67 (which I can connect to successfully))
> > 3TSSD3B1\SQLEXPRESS (which I can connect to successfully)
> >
> > What should I do to create a database on my local machine.
> > In other words, what is the equivalent of registering (LOCAL) server in SQL
> > Server 2000?
> >
> >
> >
> >
> > "Charles Wang[MSFT]" wrote:
> >
> >> Hi,
> >> To let me better understand your issue, could you please let me know the
> >> following questions:
> >> 1. Did you mean registering server named (local) or a database?
> >> 2. How did you perform the registration?
> >> 3. Why would you like to register a (local) server (database?) ?
> >>
> >> From the error message, it seemed that you were trying to register a
> >> (local) server remotely. "(local)" is preserved keyword for the default
> >> instance of local SQL Server. You can only use it to locally connect to
> >> your default instance of your SQL Server not remotely. Generally it is no
> >> need to register a (local) server, if you want to rename a SQL server
> >> instance, you can use sp_dropserver/sp_addserver stored procedures. You may
> >> refer to:
> >> How to: Rename a Computer that Hosts a Stand-Alone Instance of SQL Server
> >> 2005
> >> http://technet.microsoft.com/en-us/library/ms143799.aspx
> >>
> >> Anyway I think that I have not totally understood your scenario. If there
> >> is any misunderstanding, I appreciate your pointing and kindly making some
> >> further explanation.
> >>
> >> Thanks and have a nice day!
> >>
> >> Best regards,
> >> Charles Wang
> >> Microsoft Online Community Support
> >> =====================================================> >> 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.
> >> ======================================================> >>
> >>
> >>
> >>
> >>
>|||What tool did you use to get that list? None of those looks like the name of a SQL Server 2005
service to me. I suggest you do Run and in there type : services.msc
This starts the "Services" windows applet. In there you look for services where the name starts with
SQL Server, such as :
SQL Server (MSSQLServer)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"rkbnair" <rkbnair@.community.nospam> wrote in message
news:145F3211-E6D3-4D4F-877B-7F47AE7C7759@.microsoft.com...
> The following services are started:
> Server Status (green)
> Report Server Virtual Directory (Red)
> Report Manager Virtual Directory (red)
> Windows Service Identity (Green)
> Database Setup (Red)
> Encryption Keys (Grey)
> Initialization (Grey)
> Email settings (Yellow)
> Execution Account (Yellow)
> --
> test
>
> "Tibor Karaszi" wrote:
>> I suggest you first check what SQL Server related services you have installed. From that we can
>> see
>> how many instances of SQL Server you installed.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "rkbnair" <rkbnair@.community.nospam> wrote in message
>> news:D5D736D2-EFB4-4E02-A37A-7CDE47D5C019@.microsoft.com...
>> > Under the registered servers I see the following:
>> > 3tsd3b1
>> > 3tsd3b1\sqlexpress (which I can connect to successfully)
>> >
>> > Under the Server Group I see the following items:
>> > (LOCAL)
>> > 10.100.1.67 (which I can connect to successfully))
>> > 3TSSD3B1\SQLEXPRESS (which I can connect to successfully)
>> >
>> > What should I do to create a database on my local machine.
>> > In other words, what is the equivalent of registering (LOCAL) server in SQL
>> > Server 2000?
>> >
>> >
>> >
>> >
>> > "Charles Wang[MSFT]" wrote:
>> >
>> >> Hi,
>> >> To let me better understand your issue, could you please let me know the
>> >> following questions:
>> >> 1. Did you mean registering server named (local) or a database?
>> >> 2. How did you perform the registration?
>> >> 3. Why would you like to register a (local) server (database?) ?
>> >>
>> >> From the error message, it seemed that you were trying to register a
>> >> (local) server remotely. "(local)" is preserved keyword for the default
>> >> instance of local SQL Server. You can only use it to locally connect to
>> >> your default instance of your SQL Server not remotely. Generally it is no
>> >> need to register a (local) server, if you want to rename a SQL server
>> >> instance, you can use sp_dropserver/sp_addserver stored procedures. You may
>> >> refer to:
>> >> How to: Rename a Computer that Hosts a Stand-Alone Instance of SQL Server
>> >> 2005
>> >> http://technet.microsoft.com/en-us/library/ms143799.aspx
>> >>
>> >> Anyway I think that I have not totally understood your scenario. If there
>> >> is any misunderstanding, I appreciate your pointing and kindly making some
>> >> further explanation.
>> >>
>> >> Thanks and have a nice day!
>> >>
>> >> Best regards,
>> >> Charles Wang
>> >> Microsoft Online Community Support
>> >> =====================================================>> >> 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.
>> >> ======================================================>> >>
>> >>
>> >>
>> >>
>> >>|||Hi,
Thanks for your response.
I recommend that you post some screenshots here or or mail them to me
(changliw_at_microsoft_dot_com) so that we can better understand your
issue. Also as Tibor said, please run services.msc from command line and
check what the SQL Server services are listed. The SQL Server service name
is like "SQL Server (<instance name>)" or "MSSQLServer".
Additionally I need to confirm with you several questions for further
research:
a. What is the version of your (local) SQL Server instance, SQL Server 2000
or SQL Server 2005?
b. What is the client tool you use, SQL Server Enterprise Manager or SQL
Server Management Studio?
c. Was "3tsd3b1" the name of your local computer and was "10.100.1.67" the
IP address of your local computer?
Creating a database on your local machine does not mean registering (LOCAL)
server in SQL Server 2000. If you would like to register (LOCAL) server in
SQL Server 2000 (Enterprise Manager ?) , you need to ensure that there is a
SQL Server 2000 default instance (the service name is MSSQLServer in
Services panel) has been installed. Also SQL Server 2000 Enterprise Manager
(EM) cannot manage SQL Server 2005 instance, so if you would like to use
SQL Server 2000 EM to register a SQL Server 2005 instance, it is not
possible to do it. In this case, you have to use SQL Server 2005 Management
Studio (SSMS) to do it.
If there is a SQL Server 2000 default instance installed, you can locally
use either SQL Server 2000 EM or SSMS to connect to it via your computer
name, IP or "(local)" to connect to it. Appreciate your understanding if we
could not cleary understand your issue, it is hard for us to go further.
Thanks for your cooperation and look forward to your response.
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================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.
======================================================|||SQL Server (SQLEXPRESS)
SQL Server Active Directory Helper
SQL Server Analysis Services (MSSQLSERVER)
SQL Server Browser
SQL Server Integration Services
SQL Server Reporting Services (MSSQLSERVER)
SQL Server VSS Writer
--
test
"Tibor Karaszi" wrote:
> What tool did you use to get that list? None of those looks like the name of a SQL Server 2005
> service to me. I suggest you do Run and in there type : services.msc
> This starts the "Services" windows applet. In there you look for services where the name starts with
> SQL Server, such as :
> SQL Server (MSSQLServer)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "rkbnair" <rkbnair@.community.nospam> wrote in message
> news:145F3211-E6D3-4D4F-877B-7F47AE7C7759@.microsoft.com...
> > The following services are started:
> >
> > Server Status (green)
> > Report Server Virtual Directory (Red)
> > Report Manager Virtual Directory (red)
> > Windows Service Identity (Green)
> > Database Setup (Red)
> > Encryption Keys (Grey)
> > Initialization (Grey)
> > Email settings (Yellow)
> > Execution Account (Yellow)
> >
> > --
> > test
> >
> >
> > "Tibor Karaszi" wrote:
> >
> >> I suggest you first check what SQL Server related services you have installed. From that we can
> >> see
> >> how many instances of SQL Server you installed.
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://sqlblog.com/blogs/tibor_karaszi
> >>
> >>
> >> "rkbnair" <rkbnair@.community.nospam> wrote in message
> >> news:D5D736D2-EFB4-4E02-A37A-7CDE47D5C019@.microsoft.com...
> >> > Under the registered servers I see the following:
> >> > 3tsd3b1
> >> > 3tsd3b1\sqlexpress (which I can connect to successfully)
> >> >
> >> > Under the Server Group I see the following items:
> >> > (LOCAL)
> >> > 10.100.1.67 (which I can connect to successfully))
> >> > 3TSSD3B1\SQLEXPRESS (which I can connect to successfully)
> >> >
> >> > What should I do to create a database on my local machine.
> >> > In other words, what is the equivalent of registering (LOCAL) server in SQL
> >> > Server 2000?
> >> >
> >> >
> >> >
> >> >
> >> > "Charles Wang[MSFT]" wrote:
> >> >
> >> >> Hi,
> >> >> To let me better understand your issue, could you please let me know the
> >> >> following questions:
> >> >> 1. Did you mean registering server named (local) or a database?
> >> >> 2. How did you perform the registration?
> >> >> 3. Why would you like to register a (local) server (database?) ?
> >> >>
> >> >> From the error message, it seemed that you were trying to register a
> >> >> (local) server remotely. "(local)" is preserved keyword for the default
> >> >> instance of local SQL Server. You can only use it to locally connect to
> >> >> your default instance of your SQL Server not remotely. Generally it is no
> >> >> need to register a (local) server, if you want to rename a SQL server
> >> >> instance, you can use sp_dropserver/sp_addserver stored procedures. You may
> >> >> refer to:
> >> >> How to: Rename a Computer that Hosts a Stand-Alone Instance of SQL Server
> >> >> 2005
> >> >> http://technet.microsoft.com/en-us/library/ms143799.aspx
> >> >>
> >> >> Anyway I think that I have not totally understood your scenario. If there
> >> >> is any misunderstanding, I appreciate your pointing and kindly making some
> >> >> further explanation.
> >> >>
> >> >> Thanks and have a nice day!
> >> >>
> >> >> Best regards,
> >> >> Charles Wang
> >> >> Microsoft Online Community Support
> >> >> =====================================================> >> >> 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.
> >> >> ======================================================> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >>
>|||OK. It seems you have installed a named instance of SQL Server express database engine with the
instance name "SQLEXPRESS".
Also, you installed Analysis services and Reporting services as default instances.
So, I assume you want to connect to your express named instance (since that is the only database
engine instance). If you are local on the machine try:
localhost\SQLExpress
Or:
machinename\SQLEXPRESS
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"rkbnair" <rkbnair@.community.nospam> wrote in message
news:83688470-F1FB-4618-B743-D1F9B0B267E2@.microsoft.com...
> SQL Server (SQLEXPRESS)
> SQL Server Active Directory Helper
> SQL Server Analysis Services (MSSQLSERVER)
> SQL Server Browser
> SQL Server Integration Services
> SQL Server Reporting Services (MSSQLSERVER)
> SQL Server VSS Writer
> --
> test
>
> "Tibor Karaszi" wrote:
>> What tool did you use to get that list? None of those looks like the name of a SQL Server 2005
>> service to me. I suggest you do Run and in there type : services.msc
>> This starts the "Services" windows applet. In there you look for services where the name starts
>> with
>> SQL Server, such as :
>> SQL Server (MSSQLServer)
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "rkbnair" <rkbnair@.community.nospam> wrote in message
>> news:145F3211-E6D3-4D4F-877B-7F47AE7C7759@.microsoft.com...
>> > The following services are started:
>> >
>> > Server Status (green)
>> > Report Server Virtual Directory (Red)
>> > Report Manager Virtual Directory (red)
>> > Windows Service Identity (Green)
>> > Database Setup (Red)
>> > Encryption Keys (Grey)
>> > Initialization (Grey)
>> > Email settings (Yellow)
>> > Execution Account (Yellow)
>> >
>> > --
>> > test
>> >
>> >
>> > "Tibor Karaszi" wrote:
>> >
>> >> I suggest you first check what SQL Server related services you have installed. From that we
>> >> can
>> >> see
>> >> how many instances of SQL Server you installed.
>> >>
>> >> --
>> >> Tibor Karaszi, SQL Server MVP
>> >> http://www.karaszi.com/sqlserver/default.asp
>> >> http://sqlblog.com/blogs/tibor_karaszi
>> >>
>> >>
>> >> "rkbnair" <rkbnair@.community.nospam> wrote in message
>> >> news:D5D736D2-EFB4-4E02-A37A-7CDE47D5C019@.microsoft.com...
>> >> > Under the registered servers I see the following:
>> >> > 3tsd3b1
>> >> > 3tsd3b1\sqlexpress (which I can connect to successfully)
>> >> >
>> >> > Under the Server Group I see the following items:
>> >> > (LOCAL)
>> >> > 10.100.1.67 (which I can connect to successfully))
>> >> > 3TSSD3B1\SQLEXPRESS (which I can connect to successfully)
>> >> >
>> >> > What should I do to create a database on my local machine.
>> >> > In other words, what is the equivalent of registering (LOCAL) server in SQL
>> >> > Server 2000?
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > "Charles Wang[MSFT]" wrote:
>> >> >
>> >> >> Hi,
>> >> >> To let me better understand your issue, could you please let me know the
>> >> >> following questions:
>> >> >> 1. Did you mean registering server named (local) or a database?
>> >> >> 2. How did you perform the registration?
>> >> >> 3. Why would you like to register a (local) server (database?) ?
>> >> >>
>> >> >> From the error message, it seemed that you were trying to register a
>> >> >> (local) server remotely. "(local)" is preserved keyword for the default
>> >> >> instance of local SQL Server. You can only use it to locally connect to
>> >> >> your default instance of your SQL Server not remotely. Generally it is no
>> >> >> need to register a (local) server, if you want to rename a SQL server
>> >> >> instance, you can use sp_dropserver/sp_addserver stored procedures. You may
>> >> >> refer to:
>> >> >> How to: Rename a Computer that Hosts a Stand-Alone Instance of SQL Server
>> >> >> 2005
>> >> >> http://technet.microsoft.com/en-us/library/ms143799.aspx
>> >> >>
>> >> >> Anyway I think that I have not totally understood your scenario. If there
>> >> >> is any misunderstanding, I appreciate your pointing and kindly making some
>> >> >> further explanation.
>> >> >>
>> >> >> Thanks and have a nice day!
>> >> >>
>> >> >> Best regards,
>> >> >> Charles Wang
>> >> >> Microsoft Online Community Support
>> >> >> =====================================================>> >> >> 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 register server (LOCAL)
.
However, I get the following message. I still can register other servers
using ip addresses though.
========================================
=============
Cannot connect to (LOCAL).
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: TCP Provider, error: 0 - No connection could be made because the
target machine actively refused it.) (Microsoft SQL Server, Error: 10061)
========================================
=============did you try localhost?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"rkbnair" <rkbnair@.community.nospam> wrote in message
news:5439BC07-3618-4DC5-99BB-7957915C6894@.microsoft.com...
> I'm trying to register the (LOCAL) database using SQL Server authenticati
on.
> However, I get the following message. I still can register other servers
> using ip addresses though.
> ========================================
=============
> Cannot connect to (LOCAL).
> --
> ADDITIONAL INFORMATION:
> An error has occurred while establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by the fact that
> under the default settings SQL Server does not allow remote connections.
> (provider: TCP Provider, error: 0 - No connection could be made because th
e
> target machine actively refused it.) (Microsoft SQL Server, Error: 10061)
> ========================================
=============
>|||Hi,
To let me better understand your issue, could you please let me know the
following questions:
1. Did you mean registering server named (local) or a database?
2. How did you perform the registration?
3. Why would you like to register a (local) server (database?) ?
From the error message, it seemed that you were trying to register a
(local) server remotely. "(local)" is preserved keyword for the default
instance of local SQL Server. You can only use it to locally connect to
your default instance of your SQL Server not remotely. Generally it is no
need to register a (local) server, if you want to rename a SQL server
instance, you can use sp_dropserver/sp_addserver stored procedures. You may
refer to:
How to: Rename a Computer that Hosts a Stand-Alone Instance of SQL Server
2005
http://technet.microsoft.com/en-us/...y/ms143799.aspx
Anyway I think that I have not totally understood your scenario. If there
is any misunderstanding, I appreciate your pointing and kindly making some
further explanation.
Thanks and have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
========================================
=============
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.
========================================
==============|||Yes, But no luck on that too.
test
"Tibor Karaszi" wrote:
> did you try localhost?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "rkbnair" <rkbnair@.community.nospam> wrote in message
> news:5439BC07-3618-4DC5-99BB-7957915C6894@.microsoft.com...
>
>|||Under the registered servers I see the following:
3tsd3b1
3tsd3b1\sqlexpress (which I can connect to successfully)
Under the Server Group I see the following items:
(LOCAL)
10.100.1.67 (which I can connect to successfully))
3TSSD3B1\SQLEXPRESS (which I can connect to successfully)
What should I do to create a database on my local machine.
In other words, what is the equivalent of registering (LOCAL) server in SQL
Server 2000?
"Charles Wang[MSFT]" wrote:
> Hi,
> To let me better understand your issue, could you please let me know the
> following questions:
> 1. Did you mean registering server named (local) or a database?
> 2. How did you perform the registration?
> 3. Why would you like to register a (local) server (database?) ?
> From the error message, it seemed that you were trying to register a
> (local) server remotely. "(local)" is preserved keyword for the default
> instance of local SQL Server. You can only use it to locally connect to
> your default instance of your SQL Server not remotely. Generally it is no
> need to register a (local) server, if you want to rename a SQL server
> instance, you can use sp_dropserver/sp_addserver stored procedures. You ma
y
> refer to:
> How to: Rename a Computer that Hosts a Stand-Alone Instance of SQL Server
> 2005
> http://technet.microsoft.com/en-us/...y/ms143799.aspx
> Anyway I think that I have not totally understood your scenario. If there
> is any misunderstanding, I appreciate your pointing and kindly making some
> further explanation.
> Thanks and have a nice day!
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ========================================
=============
> 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
.
> ========================================
==============
>
>
>|||I suggest you first check what SQL Server related services you have installe
d. From that we can see
how many instances of SQL Server you installed.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"rkbnair" <rkbnair@.community.nospam> wrote in message
news:D5D736D2-EFB4-4E02-A37A-7CDE47D5C019@.microsoft.com...[vbcol=seagreen]
> Under the registered servers I see the following:
> 3tsd3b1
> 3tsd3b1\sqlexpress (which I can connect to successfully)
> Under the Server Group I see the following items:
> (LOCAL)
> 10.100.1.67 (which I can connect to successfully))
> 3TSSD3B1\SQLEXPRESS (which I can connect to successfully)
> What should I do to create a database on my local machine.
> In other words, what is the equivalent of registering (LOCAL) server in SQ
L
> Server 2000?
>
>
> "Charles Wang[MSFT]" wrote:
>|||The following services are started:
Server Status (green)
Report Server Virtual Directory (Red)
Report Manager Virtual Directory (red)
Windows Service Identity (Green)
Database Setup (Red)
Encryption Keys (Grey)
Initialization (Grey)
Email settings (Yellow)
Execution Account (Yellow)
test
"Tibor Karaszi" wrote:
> I suggest you first check what SQL Server related services you have instal
led. From that we can see
> how many instances of SQL Server you installed.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "rkbnair" <rkbnair@.community.nospam> wrote in message
> news:D5D736D2-EFB4-4E02-A37A-7CDE47D5C019@.microsoft.com...
>|||What tool did you use to get that list? None of those looks like the name of
a SQL Server 2005
service to me. I suggest you do Run and in there type : services.msc
This starts the "Services" windows applet. In there you look for services wh
ere the name starts with
SQL Server, such as :
SQL Server (MSSQLServer)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"rkbnair" <rkbnair@.community.nospam> wrote in message
news:145F3211-E6D3-4D4F-877B-7F47AE7C7759@.microsoft.com...[vbcol=seagreen]
> The following services are started:
> Server Status (green)
> Report Server Virtual Directory (Red)
> Report Manager Virtual Directory (red)
> Windows Service Identity (Green)
> Database Setup (Red)
> Encryption Keys (Grey)
> Initialization (Grey)
> Email settings (Yellow)
> Execution Account (Yellow)
> --
> test
>
> "Tibor Karaszi" wrote:
>|||Hi,
Thanks for your response.
I recommend that you post some screenshots here or or mail them to me
(changliw_at_microsoft_dot_com) so that we can better understand your
issue. Also as Tibor said, please run services.msc from command line and
check what the SQL Server services are listed. The SQL Server service name
is like "SQL Server (<instance name> )" or "MSSQLServer".
Additionally I need to confirm with you several questions for further
research:
a. What is the version of your (local) SQL Server instance, SQL Server 2000
or SQL Server 2005?
b. What is the client tool you use, SQL Server Enterprise Manager or SQL
Server Management Studio?
c. Was "3tsd3b1" the name of your local computer and was "10.100.1.67" the
IP address of your local computer?
Creating a database on your local machine does not mean registering (LOCAL)
server in SQL Server 2000. If you would like to register (LOCAL) server in
SQL Server 2000 (Enterprise Manager ?) , you need to ensure that there is a
SQL Server 2000 default instance (the service name is MSSQLServer in
Services panel) has been installed. Also SQL Server 2000 Enterprise Manager
(EM) cannot manage SQL Server 2005 instance, so if you would like to use
SQL Server 2000 EM to register a SQL Server 2005 instance, it is not
possible to do it. In this case, you have to use SQL Server 2005 Management
Studio (SSMS) to do it.
If there is a SQL Server 2000 default instance installed, you can locally
use either SQL Server 2000 EM or SSMS to connect to it via your computer
name, IP or "(local)" to connect to it. Appreciate your understanding if we
could not cleary understand your issue, it is hard for us to go further.
Thanks for your cooperation and look forward to your response.
Best regards,
Charles Wang
Microsoft Online Community Support
========================================
=============
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.
========================================
==============|||SQL Server (SQLEXPRESS)
SQL Server Active Directory Helper
SQL Server Analysis Services (MSSQLSERVER)
SQL Server Browser
SQL Server Integration Services
SQL Server Reporting Services (MSSQLSERVER)
SQL Server VSS Writer
test
"Tibor Karaszi" wrote:
> What tool did you use to get that list? None of those looks like the name
of a SQL Server 2005
> service to me. I suggest you do Run and in there type : services.msc
> This starts the "Services" windows applet. In there you look for services
where the name starts with
> SQL Server, such as :
> SQL Server (MSSQLServer)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "rkbnair" <rkbnair@.community.nospam> wrote in message
> news:145F3211-E6D3-4D4F-877B-7F47AE7C7759@.microsoft.com...
>
Thursday, March 22, 2012
Cannot perform an aggregate function on an expression containing an aggregate or a subquer
"Cannot perform an aggregate function on an expression containing an aggregate or a subquery." The problem is clear to me. The aggregate function Max() is being performed on the results of another aggregate function sum(). If I take out the MAX() function it works fine, but with incorrect results. The solution is not so clear to me
Do you have any thoughts about how to accomplish this using MS SQL Server?
thank
-Craig
Planned_Qty = MAX(isnull((select sum(t_Table_b.Planned_Qty
FROM t_Mfg_BOM t_Table_
WHER
t_Table_a.My_Location_Code = t_Table_b.My_Location_Code AN
t_Table_a.Mfg_Order_Nbr = t_Table_b.Mfg_Order_Nbr AN
t_Table_a.Mfg_Order_Operation_Nbr = t_Table_b.Mfg_Order_Operation_Nbr AN
t_Table_a.Item_Nbr = t_Table_b.Item_Nbr AN
((t_Table_a.BOM_Nbr = t_Table_b.BOM_Nbr) o
(t_Table_a.BOM_Nbr = t_Table_b.Alt_BOM_Nbr) o
(t_Table_a.Alt_For_BOM_Nbr = t_Table_b.BOM_Nbr) O
(t_Table_b.Alt_For_BOM_Nbr = t_Table_a.Alt_For_BOM_Nbr))),1))Put the SELECT with the subquery in a derived table and then GROUP it:
SELECT planned_qty = MAX(qty), ...
FROM
(SELECT ISNULL(
(SELECT SUM(t_Table_b.Planned_Qty)
FROM t_Mfg_BOM, t_Table_b
WHERE...)
,1)
FROM ...) AS X(qty, ...)
--
David Portas
SQL Server MVP
--sql
Cannot perform an aggregate function on an expression containing an aggregate or a sub
following error in MS SQL Server:
"Cannot perform an aggregate function on an expression containing an aggrega
te or a subquery." The problem is clear to me. The aggregate function Max(
) is being performed on the results of another aggregate function sum(). If
I take out the MAX() funct
ion it works fine, but with incorrect results. The solution is not so clear
to me.
Do you have any thoughts about how to accomplish this using MS SQL Server?
thanks
-Craig-
Planned_Qty = MAX(isnull((select sum(t_Table_b.Planned_Qty)
FROM t_Mfg_BOM t_Table_b
WHERE
t_Table_a.My_Location_Code = t_Table_b.My_Location_Code AND
t_Table_a.Mfg_Order_Nbr = t_Table_b.Mfg_Order_Nbr AND
t_Table_a.Mfg_Order_Operation_Nbr = t_Table_b.Mfg_Order_Operation_Nbr AND
t_Table_a.Item_Nbr = t_Table_b.Item_Nbr AND
((t_Table_a.BOM_Nbr = t_Table_b.BOM_Nbr) or
(t_Table_a.BOM_Nbr = t_Table_b.Alt_BOM_Nbr) or
(t_Table_a.Alt_For_BOM_Nbr = t_Table_b.BOM_Nbr) OR
(t_Table_b.Alt_For_BOM_Nbr = t_Table_a.Alt_For_BOM_Nbr))),1))Put the SELECT with the subquery in a derived table and then GROUP it:
SELECT planned_qty = MAX(qty), ...
FROM
(SELECT ISNULL(
(SELECT SUM(t_Table_b.Planned_Qty)
FROM t_Mfg_BOM, t_Table_b
WHERE...)
,1)
FROM ...) AS X(qty, ...)
David Portas
SQL Server MVP
--
Tuesday, March 20, 2012
Cannot Open Query analyser from SQL Enterprise Manager
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 offline cube
Hi,
I created an offline cube file (.cub) using SSAS 2005 sp1. I tried to open the cube file by following these steps:
1. Open excel 2003. On the toolbar, click on Data and select PivotTable and PivotChart report.
2. Select External data source as the data you want to analyze then click on next.
3. Click on the Get Data button on the next step.
4. Choose the OLAP Cubes tab on the pop-up window, select <New Data Source> and Click OK.
5. Type "Sales" as the name of the data source.
6.Choose Microsoft OLE DB Provider for Analysis Services 9.0 as the OLAP provider. Click on Connect button
7. Select the cube file option and browse for the location of the cube file. Click Finish.
8. On the fourth step (here comes the problem),on the Select the Cube that contains the data you want list, nothing is available in the dropdown list. And since I cannot finish this step, the OK button remains disabled and I was not able to open the cube file.
Can any one help me on this?
Thanks in advance,
Destry
I have exactly the same problem, as a matter of fact I was about to ask that question.
Should you find a workaround on your own, I would appreciate it if you could post it here as well too. Tia.
|||There are several things can be going wrong. Here are several ideas for you to try.
1. Try and use Microsoft OLE DB Provider for Analysis Services 8.0 to connect to your local cube.
2. Try and use MDXSample application. In the connection dialog, as server name specify a path to your local cube file. Something like c:\my cubes\cube1.cub. If you can connect and but cant see cube name there, most likely something wrong with your local cube file.
Edward Melomed.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Cannot open database"..."requested by the login...??
Hello,
I am using Visual Web Developer 2005 Express Edition and I am following the book:"Beginning ASP.NET 2.0 E-commerce in C# . I am encountering a problem and I haven't got the slightest idea how to solve the problem.
(If you have the book I got to p98)
If I debug then I get the next error: cannot open database"..." requested by the login...
In the book I had to make a GenericDataAccess.cs. What follows are snippets where the error occurs.
public static DataTable ExecuteSelectCommand(DbCommand command)
{
DataTable table
try
{
command.Connection.Open();
DbDataReader reader = command.ExecuteReader();
table = new DataTable();
table.Load(reader);
reader.Close();
}
catch (Exception ex)
{
Utilities.LogError(ex);
throw ex; //this is where my error occurs when I debug it
}
finally
{
commandConnection.close();
}
return table;
}
Ideas and sollutions are more than welcome :-)
YES!!!I'm currently using the same book and having the same problem too!
May i ask if how did you bypass the SQL Express part? Which programs did you use to substitute SQL Express Manager? I'm having problems with my database connection.
Would appreciate if you can share.
Thanks!
Monday, March 19, 2012
Cannot Open Database "XXXX" requested by login. The login failed. Login failed for user xx
hi,
so i have a new box and I'm trying to get my websites and SQL Server 2005 Standard Edition working on it, but the pages give me the following error when I try to load them:
"Cannot Open Database "XXXX" requested by login. The login failed. Login failed for user 'xxx'"
Everything seems exactly the same settings and user-wise from my old box to my new one, but nevertheless everything I've tried gives me the same error.
I've tried creating new users in SQL Server and giving them appropriate permissions to my database. I've even tried just using the built in 'sa' account. Nothing seems to change the error, except when I give it the incorrect password then it just says 'login failed'
This leads me to believe that i'm successfully logging into the SQL Server, but it doesn't want to give me access to the database I'm requesting access too. But "apparently" the account i'm using should have access to the database. If nothing else the 'sa' account should, but that didn't work either.
I'm stumped. Any ideas?
Check the database settings for user you are trying to login with and make sure they have permission and deny data reader is not checked.|||yep, the user currently has SELECT, UPDATE, INSERT, DELETE, and CONNECT permission selected.|||Look in the database properties under users and make sure the user has permissions there|||yep, the user is even marked as the dbowner.|||
here is my connection string just in case it's something funny there, but this connection string works on my old box with apparently the exact same settings
<
addname="ConnectionString"connectionString="Server=ServerName;Database=MyDatabase;User ID=MyID;Password=MyPassword;Trusted_Connection=False"providerName="System.Data.SqlClient" />|||ha!
the problem was that when I restored my database (from the old box to the new box), SQL Server replaced a certain character in the name with a different character. Namely replaced "\" with "_".
So it wasn't finding the database... I didn't need those five hours of my life anyways ;-)
Cannot Open Database
Msg 946, Level 14, State 1, Line 1
Cannot open database 'ESPune' version 539. Upgrade the database to the
latest version.
Kindly guide us how to upgrade the db to the latest version.
Except this db ESPune , all other dbs have version 611 when I see the
query select * from sysdatabases.
Regards
RajagopalHello Rajagopal!
Try to detach / attach your database.
Ekrem Önsoy
<rajagopal.ns@.gmail.com> wrote in message
news:1190980646.422354.287350@.50g2000hsm.googlegroups.com...
> We are getting the following error while opening a database.
> Msg 946, Level 14, State 1, Line 1
> Cannot open database 'ESPune' version 539. Upgrade the database to the
> latest version.
> Kindly guide us how to upgrade the db to the latest version.
> Except this db ESPune , all other dbs have version 611 when I see the
> query select * from sysdatabases.
> Regards
> Rajagopal
>|||What version of SQL Server are you using? when did you start seeing this
problem?
Was the database recently upgraded from an older version?
Could you please provide more info on this?
Thank you,
Saleem Hakani
WWW.SQLCOMMUNITY.COM
SQL Server Tips, SQL Server Scripts, SQL Server Forums, SQL Server Blogs,
SQL Server Radio, SQL Server Events..
"rajagopal.ns@.gmail.com" wrote:
> We are getting the following error while opening a database.
> Msg 946, Level 14, State 1, Line 1
> Cannot open database 'ESPune' version 539. Upgrade the database to the
> latest version.
> Kindly guide us how to upgrade the db to the latest version.
> Except this db ESPune , all other dbs have version 611 when I see the
> query select * from sysdatabases.
> Regards
> Rajagopal
>
Cannot open connection Dialog when starting SQL Server Management Studio
I start SQL Server Management Studio on my workstation and get the following message.
TITLE: Microsoft SQL Server Management Studio
Failed to open connection dialog.
ADDITIONAL INFORMATION:
Could not load file or assembly 'SqlMgmt, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) (mscorlib)
BUTTONS:
OK
I had SQl Express version installed previously and everything worked. I could connect to one server running SQL Express and a different server running full up SQL 2005 enterprise version.
I uninstalled All SQL express programs and installed tools from SQL 2005 developer.
I have rebooted, started the program directly (not using a link of any kind) and all attempts fail. After dismissing the error msg the tool opens and I can run queries agains the DB but the database engines and related tables do not show.
My work station is Windows XP with SP2 installed.
I have googled the problem extensively and tried solutions found but none have solved the problem.
Any help greatly appreciated.
I uninstalled all SQL Server components, deleted all directories (there were no files) in the installation directory. Then reinstalled SQL Server 2005 developer edition. All management tools appear to work correctly.Cannot open a connection
application, the reporting section show me the following error: "The report
server cannot open a connection to the report server database. A connection
to the database is required for all requests and processing.
(rsReportServerDatabaseUnavailable) SQL Server does not exist or access
denied". Then it show me the following warning: "An unhandled exception of
type
'Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseUnavailableException' occurred in microsoft.reportingservices.diagnostics.dll
Additional information: The report server cannot open a connection to the
report server database. A connection to the database is required for all
requests and processing."
Any ideas?
Thanks in advance.First thing is to make sure the report works outside of your application.
Have you tried the report from Report Manager, does it work from there?
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"mlugoc" <mlugoc@.discussions.microsoft.com> wrote in message
news:A33D1D4C-7E66-4A8F-93F3-06293284BFD6@.microsoft.com...
>I am using reporing services in my c# web application. When I debug my web
> application, the reporting section show me the following error: "The
> report
> server cannot open a connection to the report server database. A
> connection
> to the database is required for all requests and processing.
> (rsReportServerDatabaseUnavailable) SQL Server does not exist or access
> denied". Then it show me the following warning: "An unhandled exception
> of
> type
> 'Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseUnavailableException'
> occurred in microsoft.reportingservices.diagnostics.dll
> Additional information: The report server cannot open a connection to the
> report server database. A connection to the database is required for all
> requests and processing."
> Any ideas?
> Thanks in advance.
>|||Yes, I used Report Manager to test my report and it works great.
"Bruce L-C [MVP]" wrote:
> First thing is to make sure the report works outside of your application.
> Have you tried the report from Report Manager, does it work from there?
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "mlugoc" <mlugoc@.discussions.microsoft.com> wrote in message
> news:A33D1D4C-7E66-4A8F-93F3-06293284BFD6@.microsoft.com...
> >I am using reporing services in my c# web application. When I debug my web
> > application, the reporting section show me the following error: "The
> > report
> > server cannot open a connection to the report server database. A
> > connection
> > to the database is required for all requests and processing.
> > (rsReportServerDatabaseUnavailable) SQL Server does not exist or access
> > denied". Then it show me the following warning: "An unhandled exception
> > of
> > type
> > 'Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseUnavailableException'
> > occurred in microsoft.reportingservices.diagnostics.dll
> >
> > Additional information: The report server cannot open a connection to the
> > report server database. A connection to the database is required for all
> > requests and processing."
> >
> > Any ideas?
> > Thanks in advance.
> >
> >
>
>
Sunday, March 11, 2012
Cannot login using 'sa' user name and password
--
Mike
"Mike9900" wrote:
> Hello,
> When I try to connect it give the following message I copied from the log:
> Source Logon
> Message
> Login failed for user 'sa'. The user is not associated with a trusted SQL
> Server connection. [CLIENT: <local machine>]
>
> I am using Win 2003 Ent. and is domain controller. I use administrator
> login in win 2003. I recently installed a new win2003, but I had Win2003
> before and was fine.
> In SQL Server, it is a mixed mode and everything seems to be fine.
> What could be the other problems?
> Thanks
> --
> MikeHello,
When I try to connect it give the following message I copied from the log:
Source Logon
Message
Login failed for user 'sa'. The user is not associated with a trusted SQL
Server connection. [CLIENT: <local machine>]
I am using Win 2003 Ent. and is domain controller. I use administrator
login in win 2003. I recently installed a new win2003, but I had Win2003
before and was fine.
In SQL Server, it is a mixed mode and everything seems to be fine.
What could be the other problems?
Thanks
Mike|||Used configuration and enabled IP and is fiexed. Thanks.
--
Mike
"Mike9900" wrote:
> Hello,
> When I try to connect it give the following message I copied from the log:
> Source Logon
> Message
> Login failed for user 'sa'. The user is not associated with a trusted SQL
> Server connection. [CLIENT: <local machine>]
>
> I am using Win 2003 Ent. and is domain controller. I use administrator
> login in win 2003. I recently installed a new win2003, but I had Win2003
> before and was fine.
> In SQL Server, it is a mixed mode and everything seems to be fine.
> What could be the other problems?
> Thanks
> --
> Mike
Cannot load the DLL replincrementlsn extended procedure?
trying to setup a new push subscription and got the following error!
'Error 14053: Cannot load the DLL replincrementlsn extended procedure, or one of the DLLs it references. Reason: 126(The specified module could not be found.).
The subscription could not be updated at this time.
The subscription could not be created.'
Anyone have any ideas - I think it has some .dll missing or a sp missing but I couldn't find any such file on the CD.
Any help much appreciated...
Regards
DavejWhat is the level of service pack on both the machines?|||Hi Satya,
SP3...|||Try installing SP3a.
Thursday, March 8, 2012
Cannot link measure group from cube in different AS database
I am trying to link a measure group from a cube in a different AS database (but on the same server), and get the following error: Errors in the OLAP storage engine: The metadata for the statically linked measure group, with the name of 'AD043', cannot be verified against the source object.
Note that I can successfully link a dimension from a cube in a different AS database, and can also link a measure group from a different cube in the same AS database.
I found the following information at MSDN, but am not sure if this is the proper solution (nor do I entirely understand it--I'm not the security guy in our organization): In order to define or use a linked measure group, the Windows service account for the Analysis Services instance must belong to an Analysis Services database role that has ReadDefinition and Read access rights on the source Analysis Services instance to the source cube and measure group, or must belong to the Analysis Services Administrators role for the source Analysis Services instance.
At: http://msdn2.microsoft.com/en-us/library/ms174899(SQL.90).aspx
Can someone help me, please ?
When you create a linked MeasureGroup on a AS2005 server A, you specify its Source as a MeasureGroupBinding with these important properties:
- the DataSourceID pointing to the DataSource whose connection string points to the AS2005 server B on which the source MeasureGroup is
- the Persistance: an enum value, NotPersisted or Metadata; NonPersisted is the default and it means that the linked MeasureGroup content from server A will be pulled from the source server B at the time of creation. So a connection from server A is opened to server B. That's why the account for the AS2005 service on machine A needs to have permissions to AS2005 on machine B to read the source MeasureGroup. If the Persistance however is specified as Metadata, it means that you are sending manually the content of the linked MeasureGroup (so you specified the linked Measures one by one). In this case, a connection from A to B is still opened to verify the consistency between the linked MeasureGroup and its source. This verification adds more rules (that would generate the same error you are getting): the linked Measures need to be defined in same order as in the source MeasureGroup and they need to have the same DataTypes and AggregationFunctions as their source Measures.
Adrian Dumitrascu.
|||Thanks, Adrian. I read your response carefully, and also passed it on to our database admin. As you stated, "a connection from A to B is still opened to verify the consistency between the linked MeasureGroup and its source. This verification adds more rules (that would generate the same error you are getting): the linked Measures need to be defined in same order as in the source MeasureGroup and they need to have the same DataTypes and AggregationFunctions as their source Measures."
I found thru experimentation last night that these "rules" you mention prevent me from deleting any of the measures in a linked measure group--and this appears to cause of the problem. This seems like bizarre behavior, but I can live with it merely by setting the visible properties for those linked measures I do not want displayed to false.
Thanks again.
|||Yes, the linked MeasureGroup needs to define the same list of Measures as the source (in the same order) and the Visible property is the way to hide them fro user.
Adrian Dumitrascu.
Cannot Install Toolkit.
Trying to install SQL Everywhere Beta Toolkit. And am getting following error message:
"The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program.
The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade path."
On difference is I'm installing on top of the "recently released" verision of VS2005 SP1, not the beta.
But, other than that, all the prereqs are installed.
Any insight on suggestions would be greatly appreciated.
Thanks
Rob Vettor
It only works on the beta. I have been having trouble with this as well. According to what I have read and been told the new Service pack and the SQL Ce package you download seperate should be enough to allow you to connect to the .sdf files. I have not found this to be true but that is what it says online.good luck
Ben
Wednesday, March 7, 2012
Cannot install SQLExpress after uninstalling June CTP
I try to install SQL Server Express after uninstalling its beta and get the following error in the log file. Can anyone help me? Thanks.
Microsoft SQL Server 2005 Setup beginning at Thu Dec 15 20:28:39 2005
Process ID : 110612
c:\e7b4645908c60721e3107fa330d0184a\setup.exe Version: 2005.90.1399.0
Running: LoadResourcesAction at: 2005/11/15 20:28:38
Complete: LoadResourcesAction at: 2005/11/15 20:28:38, returned true
Running: ParseBootstrapOptionsAction at: 2005/11/15 20:28:38
Loaded DLL:c:\e7b4645908c60721e3107fa330d0184a\xmlrw.dll Version:2.0.3604.0
Complete: ParseBootstrapOptionsAction at: 2005/11/15 20:28:39, returned true
Running: ValidateWinNTAction at: 2005/11/15 20:28:39
Complete: ValidateWinNTAction at: 2005/11/15 20:28:39, returned true
Running: ValidateMinOSAction at: 2005/11/15 20:28:39
Complete: ValidateMinOSAction at: 2005/11/15 20:28:39, returned true
Running: PerformSCCAction at: 2005/11/15 20:28:39
Complete: PerformSCCAction at: 2005/11/15 20:28:39, returned true
Running: ActivateLoggingAction at: 2005/11/15 20:28:39
Complete: ActivateLoggingAction at: 2005/11/15 20:28:39, returned true
Delay load of action "DetectPatchedBootstrapAction" returned nothing. No action will occur as a result.
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__110612" returned false.
Running: PerformSCCAction2 at: 2005/11/15 20:28:39
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1116 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.06
The Product Name is "Microsoft SQL Server 2005 Express Edition CTP"
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Error: Action "PerformSCCAction2" threw an exception during execution.
Return Code: 70032
Message displayed to user
SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and then run SQL Server 2005 Setup again. For detailed instructions on uninstalling SQL Server 2005, see the SQL Server 2005 Readme.
Class not registered.
Delay load of action "UploadDrWatsonLogAction" returned nothing. No action will occur as a result.
Message pump returning: 70032
Here's the problem:
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1116 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.06
You can uninstall this from the command line using the following command:
msiexec /x {2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}
jeff.
|||I get the following error when I execute the command msiexec /x {2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}
Thanks,
Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 10005
Date: 12/15/2005
Time: 11:59:17 PM
User: TWSERVER3\Administrator
Computer: TWSERVER3
Description:
Product: Microsoft SQL Server 2005 Express Edition CTP -- Error 29628. The setup has encountered an unexpected error in datastore. The action is RestoreSetupParams. The error is :Failed to read property "InstallIds" {"MachineConfiguration", "", "TWSERVER3"} from cache
Unable to write property into cache: IsClustered
Unable to write property into cache: "IsClustered"
XmlRW Error: Failure loading xmlrw.dll
CheckAllProcedures() returned: 2
I am not sure if the following will work in your case, but that work in my case finally:
1. Delete all directories related to the previous version of SQL Server.
2. Search and deleted all keys(or parent key) of 2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F(in my case).
After that, I successfully install SQL Server Express.
|||
That seems to have worked for me too.
Many thanks for your help.
Cannot install SQL Server 2005 Express on Virtual PC 7.0
Microsoft SQL Server 2005 Setup was unable to install on your computer.
In the 'Microsoft SQL Server 2005 Setup', I received the following information:
EventType : sql90setup P1 : do_sqlscript P2: 0x733f
P3 : sqls__service__start P4 : 0x42b P5 : sqlsetuplib_service.cpp@.301
P6 : sqlca.dll@.2005.90.1399.0 P7 : sqlrun_sql.msi@.9/00.1399.06
Lastly, it said that it would send the following file as part of the report:
c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0007.cab
The host machine for Virtual PC 7.0.2 is Mac OS X 10.4.6. If you have any ideas as to how to resolve this issue, it would be GREATLY appreciated.
Peace,
-Conrad
I'm not sure what our supprt level is for VPC, I'm going to move this to the SQL Setup forum.
- Mike
|||I can tell you that Virtual PC for MAC is NOT supported. See the VPC Mac Forum posthttp://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.mac.virtualpc&tid=90715b2e-77ba-4f8a-a189-daee29467ff0&cat=en_US_595a5881-be4a-4db4-97b0-5f3a78602e23&lang=en&cr=US&sloc=en-us&m=1&p=1
As discussed in the above post, the issue is that VPC for Mac emulates a Pentium II and SQL Server 2005 requires a Pentium III. The cache prefetching instructions seem to be the real problem. At this stage the only possible way of running SQL Server 2005 on Mac hardware is to buy one of the new Intel based Macs and create a Dual boot for Windows XP on it, either that or pray to whatever diety you believe in that Microsoft will eventually bring out a version ov VPC for Mac that will emulate a Pentium III.
Cheers.
cannot install SQL Server 2005 Express Edition with Advanced Services SP2
I get the following error message each time I try to install SQL Server 2005 Express Edition with Advanced Services SP2:
Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features. Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features, install IIS from Add or Remove Programs in Control Panel or enable the IIS service through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL Server in Books Online.
This problem is described in:
http://support.microsoft.com/kb/920201
and each of the IIS 7 components specified in this article have been installed.
When I continue with:
http://support.microsoft.com/kb/934162,
the script 'adsutil.vbs' cannot be executed because it does not exist anywhere on my drive.
My question is, what is the 'adsutil.vbs' script and how do I get a hold of it? Are these contortions really necessary to get SQL server working or has MS provided a patch for this nasty problem?
My system:
VISTA Home Premium, x64
Intel Quad CPU, 2.4GHz
4Gig RAM
500Gig hard disk
Thanks,
Ian
I've removed MS Office, VS2005 + documentation and everthing related to SQL. I then re-installed the 64 bit version of the .NET framework 2.0 and followed this up by SQL Server 2005 Express Edition with Advanced Services SP2. The same problems occur as reported below.
I've been at this for 5 days. Can anyone give me an idea of where to begin debugging this problem or should I simply give up and report it as a bug to Microsoft. I would appreciate any comments or suggestions.
Thanks,
Ian
Reported warnings:
- IIS Feature Requirement (Warning)
Messages
IIS Feature Requirement
Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features. Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features, install IIS from Add or Remove Programs in Control Panel or enable the IIS service through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL Server in Books Online.
ASP.Net Version Registration Requirement (Warning)
Messages
ASP.Net Version Registration Requirement
64-bit ASP.Net is Registered. Required 32-bit ASP.Net to install Microsoft Reporting Services 2005(32-bit).
|||1. I've now enabled all IIS features.
2. For the SSEAS setup, I make no selections and simply keep the default feature selection (i.e. data base services). At the `Existing components` window, the option `SQL Server Database services 9.2.30042.00` is disabled and clicking on `next` displays a message that "None of the selected features can be installed or upgraded. Setup cannot proceed...".
Any ideas as to what this causing the bug and how to get past it?
Ian
|||I reformatted the hard driver, reinstalled Vista Premium, SQL Server Express and all is well now.|||Make shure you didnt mask reportng services resources on instalation, because, IIS is a pre-requisit to install it.cannot install SQL Server 2005 Express Edition with Advanced Services SP2
I get the following error message each time I try to install SQL Server 2005 Express Edition with Advanced Services SP2:
Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features. Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features, install IIS from Add or Remove Programs in Control Panel or enable the IIS service through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL Server in Books Online.
This problem is described in:
http://support.microsoft.com/kb/920201
and each of the IIS 7 components specified in this article have been installed.
When I continue with:
http://support.microsoft.com/kb/934162,
the script 'adsutil.vbs' cannot be executed because it does not exist anywhere on my drive.
My question is, what is the 'adsutil.vbs' script and how do I get a hold of it? Are these contortions really necessary to get SQL server working or has MS provided a patch for this nasty problem?
My system:
VISTA Home Premium, x64
Intel Quad CPU, 2.4GHz
4Gig RAM
500Gig hard disk
Thanks,
Ian
I've removed MS Office, VS2005 + documentation and everthing related to SQL. I then re-installed the 64 bit version of the .NET framework 2.0 and followed this up by SQL Server 2005 Express Edition with Advanced Services SP2. The same problems occur as reported below.
I've been at this for 5 days. Can anyone give me an idea of where to begin debugging this problem or should I simply give up and report it as a bug to Microsoft. I would appreciate any comments or suggestions.
Thanks,
Ian
Reported warnings:
- IIS Feature Requirement (Warning)
Messages
IIS Feature Requirement
Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features. Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features, install IIS from Add or Remove Programs in Control Panel or enable the IIS service through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL Server in Books Online.
ASP.Net Version Registration Requirement (Warning)
Messages
ASP.Net Version Registration Requirement
64-bit ASP.Net is Registered. Required 32-bit ASP.Net to install Microsoft Reporting Services 2005(32-bit).
|||1. I've now enabled all IIS features.
2. For the SSEAS setup, I make no selections and simply keep the default feature selection (i.e. data base services). At the `Existing components` window, the option `SQL Server Database services 9.2.30042.00` is disabled and clicking on `next` displays a message that "None of the selected features can be installed or upgraded. Setup cannot proceed...".
Any ideas as to what this causing the bug and how to get past it?
Ian
|||I reformatted the hard driver, reinstalled Vista Premium, SQL Server Express and all is well now.|||Make shure you didnt mask reportng services resources on instalation, because, IIS is a pre-requisit to install it.