Hi
I'm having trouble connecting to an instance of SQL Server 2005 (Express)
from 2 individual Windows Server 2003 machines running IIS (asp.net 2.0)
I have an IIS on each 2k3 machine, both with identical sites. The idea is
simply that we have a third sql server which is accessed by these 2 websites.
One server gives me a Server login error (user not found:
MYDomain\ServerName), which the second server gives me the usual error 26 -
Cannot connect to Server/Instance specified.
Both IIS apps use the same query string (server=MYSQLSERVER\DARTS;
database=dartsV2;trustedconnection=yes;)
but as I say, one connects, one doesn't! very odd. Anyone got any
suggestions? I've enabled named pipes and tcp/ip on the sql server, along
with "allowing remote and local connections" using surface area config. I've
even setup SQL Browser, which seemed to cure one of the servers (both were
giving me the cannot find instance specified error).
Any suggestions guys?! I'm getting kinda desperate on this one... :o)
Cheers
Dan
Hi,
To narrow down this issue, I have serveral questions which need your
confirmation:
1. Could you ping the SQL Server successfully from the two clients?
2. What will happen if you explicitly add the two domain accounts to the
users group of your third server ?
Also, I recommend you try configuring the client settings as following:
Click the Start menu;
Type cliconfg.exe;
Check if TCP/IP and Named Pipes protocols are enabled;
Select the Alias tab;
Check if the server instance exists in the list;
If it's not existed, click the Add button;
Input the alias name (<servername>\SQLEXPRESS) for Named Pipes protocol and
click OK.
Apply the settings, and then try again.
If you want to use TCP/IP protocol, please first check the listening TCP
port on your server via SQL Server Configuration Manager.
Then add an alias for TCP/IP protocol at the clients. Note that you need to
cancel the selection of "Dynamically determin the port" and input your TCP
port number.
An alias can be different with your SQL Server instance name, but the
server name should be same as your server name.
Please ensure that you can use telnet to access your SQL Server TCP port
before configuring the alias for TCP/IP:
telnet <your server name> <port number>
If you have any other concerns, please feel free to let me know. It's my
pleasure to be of assistance.
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 Charles,
Thanks for the reply. I've actually fixed this particular issue, I simply
copied the code with the "user" error onto the other IIS server, so now I
have that error on both. However, I'll post somewhere else for that...
For clarification...
1) yes. I could also use osql (or sqlcmd) to connect to the sql server from
both domain servers, cos they both had sqle installed but no instance
running).
2) I tried that, but it couldn't find the computer accounts when I tried
adding roles etc - presumbly because they were computer accounts and not
users, I'm not sure though?
I have named pipes enabled but this is considered a security risk is it not?
However, I'm not sure how to setup a connection string with an ip address? I
tried server=xxx.xxx.xxx.xxx but it that couldn't connect from either server?
(I have both named pipes and tcp/ip enabled).
Could you point me to an article on how to do that, because if named pipes
are risky, we shouldn't be using them!
Thanks for your reply and help.
Cheers
Dan
"Charles Wang[MSFT]" wrote:
> Hi,
> To narrow down this issue, I have serveral questions which need your
> confirmation:
> 1. Could you ping the SQL Server successfully from the two clients?
> 2. What will happen if you explicitly add the two domain accounts to the
> users group of your third server ?
> Also, I recommend you try configuring the client settings as following:
> Click the Start menu;
> Type cliconfg.exe;
> Check if TCP/IP and Named Pipes protocols are enabled;
> Select the Alias tab;
> Check if the server instance exists in the list;
> If it's not existed, click the Add button;
> Input the alias name (<servername>\SQLEXPRESS) for Named Pipes protocol and
> click OK.
> Apply the settings, and then try again.
> If you want to use TCP/IP protocol, please first check the listening TCP
> port on your server via SQL Server Configuration Manager.
> Then add an alias for TCP/IP protocol at the clients. Note that you need to
> cancel the selection of "Dynamically determin the port" and input your TCP
> port number.
> An alias can be different with your SQL Server instance name, but the
> server name should be same as your server name.
> Please ensure that you can use telnet to access your SQL Server TCP port
> before configuring the alias for TCP/IP:
> telnet <your server name> <port number>
> If you have any other concerns, please feel free to let me know. It's my
> pleasure to be of assistance.
> 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 Dan,
Thanks for your updating and response.
The user error should be caused by the windows logon account at your client
computer not matching the Windows authentication on the server.
Please check if the Windows login account is a member of the Users or
Administrators group under your SQL Server machine. You can maunually add
it to the Users group and then add it to the logins of your SQL Server 2005
Express and assign it permissions in SQL Server 2005 Express.
If you did not install the SQL Server 2005 Management Studio Express, you
can download it from:
http://www.microsoft.com/downloads/details.aspx?FamilyId=C243A5AE-4BD1-4E3D-
94B8-5A0F62BF7796&DisplayLang=en
This tool provides you an UI to manage your SQL Server 2005 Express like
SQL Server 2000 Enterprise Manager.
If this issue persists, it seems that it is related to the settings of your
web application. You can try using impersonation in your web.config file:
<system.web>
...
<authentication mode = "windows" />
...
<identity impersonate="true" />
...
</system.web>
For more information, you can refer to:
Using sql trusted Connections with asp.net
http://idunno.org/dotNet/trustedConnections.aspx
If you use impersonation, please ensure that the two Windows logon accounts
of your two web application servers must be as a member of the
Users/Administrators group on your SQL Server 2005 machine and be assigned
permissions in your SQL Server 2005 Express instance.
For the second error "Cannot connect to Server/Instance specified", it is
most likely a communication level error. If you are worried about the
security of Named Pipes, you can maually configure the TCP/IP protocol by
following my first reply. Also, you can configure a static TCP port at the
server side. By using SQL Server Configuration Manager, you can specify a
static TCP port under the IP All, and leave other fields under IP1 and IP2
blank:
1. Open SQL Server Configuration Manager;
2. Select Protocols for <instance name>;
3. Double click TCP/IP, switch to the IP Address tab;
4. Specify the TCP Port under the IPAll, leave all TCP Dynamics Ports under
IP1,IP2 and IPAll blank, and leave TCP Port under IP1 and IP2 blank.
5. Click OK and restart your SQL Server service.
On the client machines, ensure that you can use telnet to connect to the
server at the TCP port. Then try adding an alias for TCP/IP by using
cliconfg.exe at the client and try again.
Please feel free to let me know if you have any other questions or
concerns.
Sincerely yours,
Charles Wang
Microsoft Online Community Support
|||Hi Dan,
I am interested in this issue. Would you mind letting me know the result of
the suggestions? If you need further assistance, feel free to let me know.
I will be more than happy to be of assistance.
Have a great day!
Charles Wang
Microsoft Online Community Support
sql
Showing posts with label instance. Show all posts
Showing posts with label instance. Show all posts
Tuesday, March 20, 2012
3 server scenario problem
Hi
I'm having trouble connecting to an instance of SQL Server 2005 (Express)
from 2 individual Windows Server 2003 machines running IIS (asp.net 2.0)
I have an IIS on each 2k3 machine, both with identical sites. The idea is
simply that we have a third sql server which is accessed by these 2 websites
.
One server gives me a Server login error (user not found:
MYDomain\ServerName), which the second server gives me the usual error 26 -
Cannot connect to Server/Instance specified.
Both IIS apps use the same query string (server=MYSQLSERVER\DARTS;
database=dartsV2;trustedconnection=yes;)
but as I say, one connects, one doesn't! very odd. Anyone got any
suggestions? I've enabled named pipes and tcp/ip on the sql server, along
with "allowing remote and local connections" using surface area config. I've
even setup SQL Browser, which seemed to cure one of the servers (both were
giving me the cannot find instance specified error).
Any suggestions guys?! I'm getting kinda desperate on this one... :o)
Cheers
DanHi,
To narrow down this issue, I have serveral questions which need your
confirmation:
1. Could you ping the SQL Server successfully from the two clients?
2. What will happen if you explicitly add the two domain accounts to the
users group of your third server ?
Also, I recommend you try configuring the client settings as following:
Click the Start menu;
Type cliconfg.exe;
Check if TCP/IP and Named Pipes protocols are enabled;
Select the Alias tab;
Check if the server instance exists in the list;
If it's not existed, click the Add button;
Input the alias name (<servername>\SQLEXPRESS) for Named Pipes protocol and
click OK.
Apply the settings, and then try again.
If you want to use TCP/IP protocol, please first check the listening TCP
port on your server via SQL Server Configuration Manager.
Then add an alias for TCP/IP protocol at the clients. Note that you need to
cancel the selection of "Dynamically determin the port" and input your TCP
port number.
An alias can be different with your SQL Server instance name, but the
server name should be same as your server name.
Please ensure that you can use telnet to access your SQL Server TCP port
before configuring the alias for TCP/IP:
telnet <your server name> <port number>
If you have any other concerns, please feel free to let me know. It's my
pleasure to be of assistance.
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 Charles,
Thanks for the reply. I've actually fixed this particular issue, I simply
copied the code with the "user" error onto the other IIS server, so now I
have that error on both. However, I'll post somewhere else for that...
For clarification...
1) yes. I could also use osql (or sqlcmd) to connect to the sql server from
both domain servers, cos they both had sqle installed but no instance
running).
2) I tried that, but it couldn't find the computer accounts when I tried
adding roles etc - presumbly because they were computer accounts and not
users, I'm not sure though?
I have named pipes enabled but this is considered a security risk is it not?
However, I'm not sure how to setup a connection string with an ip address? I
tried server=xxx.xxx.xxx.xxx but it that couldn't connect from either server
?
(I have both named pipes and tcp/ip enabled).
Could you point me to an article on how to do that, because if named pipes
are risky, we shouldn't be using them!
Thanks for your reply and help.
Cheers
Dan
"Charles Wang[MSFT]" wrote:
> Hi,
> To narrow down this issue, I have serveral questions which need your
> confirmation:
> 1. Could you ping the SQL Server successfully from the two clients?
> 2. What will happen if you explicitly add the two domain accounts to the
> users group of your third server ?
> Also, I recommend you try configuring the client settings as following:
> Click the Start menu;
> Type cliconfg.exe;
> Check if TCP/IP and Named Pipes protocols are enabled;
> Select the Alias tab;
> Check if the server instance exists in the list;
> If it's not existed, click the Add button;
> Input the alias name (<servername>\SQLEXPRESS) for Named Pipes protocol an
d
> click OK.
> Apply the settings, and then try again.
> If you want to use TCP/IP protocol, please first check the listening TCP
> port on your server via SQL Server Configuration Manager.
> Then add an alias for TCP/IP protocol at the clients. Note that you need t
o
> cancel the selection of "Dynamically determin the port" and input your TCP
> port number.
> An alias can be different with your SQL Server instance name, but the
> server name should be same as your server name.
> Please ensure that you can use telnet to access your SQL Server TCP port
> before configuring the alias for TCP/IP:
> telnet <your server name> <port number>
> If you have any other concerns, please feel free to let me know. It's my
> pleasure to be of assistance.
> 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 Dan,
Thanks for your updating and response.
The user error should be caused by the windows logon account at your client
computer not matching the Windows authentication on the server.
Please check if the Windows login account is a member of the Users or
Administrators group under your SQL Server machine. You can maunually add
it to the Users group and then add it to the logins of your SQL Server 2005
Express and assign it permissions in SQL Server 2005 Express.
If you did not install the SQL Server 2005 Management Studio Express, you
can download it from:
http://www.microsoft.com/downloads/...A5AE-4BD1-4E3D-
94B8-5A0F62BF7796&DisplayLang=en
This tool provides you an UI to manage your SQL Server 2005 Express like
SQL Server 2000 Enterprise Manager.
If this issue persists, it seems that it is related to the settings of your
web application. You can try using impersonation in your web.config file:
<system.web>
..
<authentication mode = "windows" />
..
<identity impersonate="true" />
..
</system.web>
For more information, you can refer to:
Using sql trusted Connections with asp.net
http://idunno.org/dotNet/trustedConnections.aspx
If you use impersonation, please ensure that the two Windows logon accounts
of your two web application servers must be as a member of the
Users/Administrators group on your SQL Server 2005 machine and be assigned
permissions in your SQL Server 2005 Express instance.
For the second error "Cannot connect to Server/Instance specified", it is
most likely a communication level error. If you are worried about the
security of Named Pipes, you can maually configure the TCP/IP protocol by
following my first reply. Also, you can configure a static TCP port at the
server side. By using SQL Server Configuration Manager, you can specify a
static TCP port under the IP All, and leave other fields under IP1 and IP2
blank:
1. Open SQL Server Configuration Manager;
2. Select Protocols for <instance name>;
3. Double click TCP/IP, switch to the IP Address tab;
4. Specify the TCP Port under the IPAll, leave all TCP Dynamics Ports under
IP1,IP2 and IPAll blank, and leave TCP Port under IP1 and IP2 blank.
5. Click OK and restart your SQL Server service.
On the client machines, ensure that you can use telnet to connect to the
server at the TCP port. Then try adding an alias for TCP/IP by using
cliconfg.exe at the client and try again.
Please feel free to let me know if you have any other questions or
concerns.
Sincerely yours,
Charles Wang
Microsoft Online Community Support|||Hi Dan,
I am interested in this issue. Would you mind letting me know the result of
the suggestions? If you need further assistance, feel free to let me know.
I will be more than happy to be of assistance.
Have a great day!
Charles Wang
Microsoft Online Community Support
I'm having trouble connecting to an instance of SQL Server 2005 (Express)
from 2 individual Windows Server 2003 machines running IIS (asp.net 2.0)
I have an IIS on each 2k3 machine, both with identical sites. The idea is
simply that we have a third sql server which is accessed by these 2 websites
.
One server gives me a Server login error (user not found:
MYDomain\ServerName), which the second server gives me the usual error 26 -
Cannot connect to Server/Instance specified.
Both IIS apps use the same query string (server=MYSQLSERVER\DARTS;
database=dartsV2;trustedconnection=yes;)
but as I say, one connects, one doesn't! very odd. Anyone got any
suggestions? I've enabled named pipes and tcp/ip on the sql server, along
with "allowing remote and local connections" using surface area config. I've
even setup SQL Browser, which seemed to cure one of the servers (both were
giving me the cannot find instance specified error).
Any suggestions guys?! I'm getting kinda desperate on this one... :o)
Cheers
DanHi,
To narrow down this issue, I have serveral questions which need your
confirmation:
1. Could you ping the SQL Server successfully from the two clients?
2. What will happen if you explicitly add the two domain accounts to the
users group of your third server ?
Also, I recommend you try configuring the client settings as following:
Click the Start menu;
Type cliconfg.exe;
Check if TCP/IP and Named Pipes protocols are enabled;
Select the Alias tab;
Check if the server instance exists in the list;
If it's not existed, click the Add button;
Input the alias name (<servername>\SQLEXPRESS) for Named Pipes protocol and
click OK.
Apply the settings, and then try again.
If you want to use TCP/IP protocol, please first check the listening TCP
port on your server via SQL Server Configuration Manager.
Then add an alias for TCP/IP protocol at the clients. Note that you need to
cancel the selection of "Dynamically determin the port" and input your TCP
port number.
An alias can be different with your SQL Server instance name, but the
server name should be same as your server name.
Please ensure that you can use telnet to access your SQL Server TCP port
before configuring the alias for TCP/IP:
telnet <your server name> <port number>
If you have any other concerns, please feel free to let me know. It's my
pleasure to be of assistance.
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 Charles,
Thanks for the reply. I've actually fixed this particular issue, I simply
copied the code with the "user" error onto the other IIS server, so now I
have that error on both. However, I'll post somewhere else for that...
For clarification...
1) yes. I could also use osql (or sqlcmd) to connect to the sql server from
both domain servers, cos they both had sqle installed but no instance
running).
2) I tried that, but it couldn't find the computer accounts when I tried
adding roles etc - presumbly because they were computer accounts and not
users, I'm not sure though?
I have named pipes enabled but this is considered a security risk is it not?
However, I'm not sure how to setup a connection string with an ip address? I
tried server=xxx.xxx.xxx.xxx but it that couldn't connect from either server
?
(I have both named pipes and tcp/ip enabled).
Could you point me to an article on how to do that, because if named pipes
are risky, we shouldn't be using them!
Thanks for your reply and help.
Cheers
Dan
"Charles Wang[MSFT]" wrote:
> Hi,
> To narrow down this issue, I have serveral questions which need your
> confirmation:
> 1. Could you ping the SQL Server successfully from the two clients?
> 2. What will happen if you explicitly add the two domain accounts to the
> users group of your third server ?
> Also, I recommend you try configuring the client settings as following:
> Click the Start menu;
> Type cliconfg.exe;
> Check if TCP/IP and Named Pipes protocols are enabled;
> Select the Alias tab;
> Check if the server instance exists in the list;
> If it's not existed, click the Add button;
> Input the alias name (<servername>\SQLEXPRESS) for Named Pipes protocol an
d
> click OK.
> Apply the settings, and then try again.
> If you want to use TCP/IP protocol, please first check the listening TCP
> port on your server via SQL Server Configuration Manager.
> Then add an alias for TCP/IP protocol at the clients. Note that you need t
o
> cancel the selection of "Dynamically determin the port" and input your TCP
> port number.
> An alias can be different with your SQL Server instance name, but the
> server name should be same as your server name.
> Please ensure that you can use telnet to access your SQL Server TCP port
> before configuring the alias for TCP/IP:
> telnet <your server name> <port number>
> If you have any other concerns, please feel free to let me know. It's my
> pleasure to be of assistance.
> 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 Dan,
Thanks for your updating and response.
The user error should be caused by the windows logon account at your client
computer not matching the Windows authentication on the server.
Please check if the Windows login account is a member of the Users or
Administrators group under your SQL Server machine. You can maunually add
it to the Users group and then add it to the logins of your SQL Server 2005
Express and assign it permissions in SQL Server 2005 Express.
If you did not install the SQL Server 2005 Management Studio Express, you
can download it from:
http://www.microsoft.com/downloads/...A5AE-4BD1-4E3D-
94B8-5A0F62BF7796&DisplayLang=en
This tool provides you an UI to manage your SQL Server 2005 Express like
SQL Server 2000 Enterprise Manager.
If this issue persists, it seems that it is related to the settings of your
web application. You can try using impersonation in your web.config file:
<system.web>
..
<authentication mode = "windows" />
..
<identity impersonate="true" />
..
</system.web>
For more information, you can refer to:
Using sql trusted Connections with asp.net
http://idunno.org/dotNet/trustedConnections.aspx
If you use impersonation, please ensure that the two Windows logon accounts
of your two web application servers must be as a member of the
Users/Administrators group on your SQL Server 2005 machine and be assigned
permissions in your SQL Server 2005 Express instance.
For the second error "Cannot connect to Server/Instance specified", it is
most likely a communication level error. If you are worried about the
security of Named Pipes, you can maually configure the TCP/IP protocol by
following my first reply. Also, you can configure a static TCP port at the
server side. By using SQL Server Configuration Manager, you can specify a
static TCP port under the IP All, and leave other fields under IP1 and IP2
blank:
1. Open SQL Server Configuration Manager;
2. Select Protocols for <instance name>;
3. Double click TCP/IP, switch to the IP Address tab;
4. Specify the TCP Port under the IPAll, leave all TCP Dynamics Ports under
IP1,IP2 and IPAll blank, and leave TCP Port under IP1 and IP2 blank.
5. Click OK and restart your SQL Server service.
On the client machines, ensure that you can use telnet to connect to the
server at the TCP port. Then try adding an alias for TCP/IP by using
cliconfg.exe at the client and try again.
Please feel free to let me know if you have any other questions or
concerns.
Sincerely yours,
Charles Wang
Microsoft Online Community Support|||Hi Dan,
I am interested in this issue. Would you mind letting me know the result of
the suggestions? If you need further assistance, feel free to let me know.
I will be more than happy to be of assistance.
Have a great day!
Charles Wang
Microsoft Online Community Support
Monday, March 19, 2012
2-way replication through an outbound only firewall. Is this possible?
We have a client that would like to have their (Remote) web server
SQL2K instance set-up for 2-way replication against their internal
private SQL2K instance (Local). The problem is their network security
department won't allow *any* TCP/IP socket connections to be
initiated from the Remote SQL2K server through the firewall to their
internal Local server. However outbound connections, initiated from the
Local server (i.e. Local -> Firewall -> Remote), are allowed.
Can SQL Server support 2-way replication under this sort of firewall
restriction?
I imagine the Remote web server SQL2K instance would need to be
configured as the Publisher (listening on port 1433) and the Local
SQL2K instance a Subscriber. The Local Subscriber would then be
configured to connect periodically to the Publisher for updates. When
the Subscriber is connected all queued data deltas (on either server)
would be replicated between them to insure both instances are
synchronized. The Subscriber would then disconnect. (or not?)
Would the distributor process need to run on the Remote or Local
server? Would we need to run merge or transactional based replication?
More info:
- The network connection between servers should hardly
ever be down.
- Not all tables in the database schema need to be
replicated, just a subset.
- To begin with the tables will be empty on both servers,
so we don't need to worry about an initial snapshot.
- We hope to use SQL2K's Auto Identity Range Management
to ensure unique keys do not collide.
Thanks for any feedback you can offer.
Good to hear that it can work Markus,
Do you see any problems in running a very short period between data
merge pushes? Say every minute or even less?
Will SQL2K prevent a new merge from running if one is already in
progress?
-Paul
SQL2K instance set-up for 2-way replication against their internal
private SQL2K instance (Local). The problem is their network security
department won't allow *any* TCP/IP socket connections to be
initiated from the Remote SQL2K server through the firewall to their
internal Local server. However outbound connections, initiated from the
Local server (i.e. Local -> Firewall -> Remote), are allowed.
Can SQL Server support 2-way replication under this sort of firewall
restriction?
I imagine the Remote web server SQL2K instance would need to be
configured as the Publisher (listening on port 1433) and the Local
SQL2K instance a Subscriber. The Local Subscriber would then be
configured to connect periodically to the Publisher for updates. When
the Subscriber is connected all queued data deltas (on either server)
would be replicated between them to insure both instances are
synchronized. The Subscriber would then disconnect. (or not?)
Would the distributor process need to run on the Remote or Local
server? Would we need to run merge or transactional based replication?
More info:
- The network connection between servers should hardly
ever be down.
- Not all tables in the database schema need to be
replicated, just a subset.
- To begin with the tables will be empty on both servers,
so we don't need to worry about an initial snapshot.
- We hope to use SQL2K's Auto Identity Range Management
to ensure unique keys do not collide.
Thanks for any feedback you can offer.
Good to hear that it can work Markus,
Do you see any problems in running a very short period between data
merge pushes? Say every minute or even less?
Will SQL2K prevent a new merge from running if one is already in
progress?
-Paul
2nd Node does not come online
I have an "Active/Active" SQL 2000 cluster on Windows 2003 SP1. The first
node is the default instance and the second is a named instance. They are
both listenting on port 1433. When I fail the default instance over to the
2nd node, everything failsover and comes on line and I am able to connect and
query the data from both instances. I fail the node back over, again
everthing works.
When I fail the second node (named instance) over to the first node,
everthing fails over; however, the SQL Agent, Fulltext searching and the SQL
Server do not come on line. Any ideas on why this is happening? Thanks.
You can't have them both listening on port 1433. You can have one, say the
default, and the other DYNAMIC, which means SQL will randomly select a port.
When failed over it will attempt to acquire the same port as before, but not
always. The client rely on the Dynamic Discovery, UDP 1434, to detect which
port to use.
If you have these hard-coded, the named instance will fail whenever it fails
over to the node where the default instance has already acquired that port.
Consider it portetiquett, but no two TCP services can listen on the same
port on the same server. Sorry.
Sincerely,
Anthony Thomas
"MAGrimsley" <MAGrimsley@.discussions.microsoft.com> wrote in message
news:EC957BA9-76A8-42E4-AD8D-5F47354C149B@.microsoft.com...
> I have an "Active/Active" SQL 2000 cluster on Windows 2003 SP1. The first
> node is the default instance and the second is a named instance. They are
> both listenting on port 1433. When I fail the default instance over to the
> 2nd node, everything failsover and comes on line and I am able to connect
and
> query the data from both instances. I fail the node back over, again
> everthing works.
> When I fail the second node (named instance) over to the first node,
> everthing fails over; however, the SQL Agent, Fulltext searching and the
SQL
> Server do not come on line. Any ideas on why this is happening? Thanks.
node is the default instance and the second is a named instance. They are
both listenting on port 1433. When I fail the default instance over to the
2nd node, everything failsover and comes on line and I am able to connect and
query the data from both instances. I fail the node back over, again
everthing works.
When I fail the second node (named instance) over to the first node,
everthing fails over; however, the SQL Agent, Fulltext searching and the SQL
Server do not come on line. Any ideas on why this is happening? Thanks.
You can't have them both listening on port 1433. You can have one, say the
default, and the other DYNAMIC, which means SQL will randomly select a port.
When failed over it will attempt to acquire the same port as before, but not
always. The client rely on the Dynamic Discovery, UDP 1434, to detect which
port to use.
If you have these hard-coded, the named instance will fail whenever it fails
over to the node where the default instance has already acquired that port.
Consider it portetiquett, but no two TCP services can listen on the same
port on the same server. Sorry.
Sincerely,
Anthony Thomas
"MAGrimsley" <MAGrimsley@.discussions.microsoft.com> wrote in message
news:EC957BA9-76A8-42E4-AD8D-5F47354C149B@.microsoft.com...
> I have an "Active/Active" SQL 2000 cluster on Windows 2003 SP1. The first
> node is the default instance and the second is a named instance. They are
> both listenting on port 1433. When I fail the default instance over to the
> 2nd node, everything failsover and comes on line and I am able to connect
and
> query the data from both instances. I fail the node back over, again
> everthing works.
> When I fail the second node (named instance) over to the first node,
> everthing fails over; however, the SQL Agent, Fulltext searching and the
SQL
> Server do not come on line. Any ideas on why this is happening? Thanks.
Sunday, March 11, 2012
2nd Instance of SQL Server 7
How do I install a 'second instance' of MS SQL Server 7
along side my existing production database. I'm told it
is need to publish a second alias (seperate database)
from the same server.
Thanks,
Johnsql7 does not support named instances. hence, you only have 1 default
instance per server.
--
-oj
RAC v2.2 & QALite!
http://www.rac4sql.net
"John" <anonymous@.discussions.microsoft.com> wrote in message
news:03cc01c3ae2e$95ab0e50$a101280a@.phx.gbl...
> How do I install a 'second instance' of MS SQL Server 7
> along side my existing production database. I'm told it
> is need to publish a second alias (seperate database)
> from the same server.
> Thanks,
> John|||Is it at all possible to have 2 databases on a single sql
7 server system?
Thanks,
John
>--Original Message--
>sql7 does not support named instances. hence, you only
have 1 default
>instance per server.
>--
>-oj
>RAC v2.2 & QALite!
>http://www.rac4sql.net
>
>"John" <anonymous@.discussions.microsoft.com> wrote in
message
>news:03cc01c3ae2e$95ab0e50$a101280a@.phx.gbl...
>> How do I install a 'second instance' of MS SQL Server 7
>> along side my existing production database. I'm told it
>> is need to publish a second alias (seperate database)
>> from the same server.
>> Thanks,
>> John
>
>.
>|||John,
Yes. You can have upto 32767 databases per instance of sql7/2k.
--
-oj
RAC v2.2 & QALite!
http://www.rac4sql.net
<anonymous@.discussions.microsoft.com> wrote in message
news:0e9d01c3ae34$31a2a160$a601280a@.phx.gbl...
> Is it at all possible to have 2 databases on a single sql
> 7 server system?
> Thanks,
> John
> >--Original Message--
> >sql7 does not support named instances. hence, you only
> have 1 default
> >instance per server.
> >
> >--
> >-oj
> >RAC v2.2 & QALite!
> >http://www.rac4sql.net
> >
> >
> >"John" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:03cc01c3ae2e$95ab0e50$a101280a@.phx.gbl...
> >> How do I install a 'second instance' of MS SQL Server 7
> >> along side my existing production database. I'm told it
> >> is need to publish a second alias (seperate database)
> >> from the same server.
> >>
> >> Thanks,
> >> John
> >
> >
> >.
> >|||yes, you can have maximum of 32,767 database per SQL Server 7 instance.
--
- Vishal|||I've inherited an app system that requires 1 database per
sql server installation. a huge waste in my thinking...
but I need to get the equivilent of multiple sql
instances (as in sql2k) with sql 7. any ideas?
Thanks,
John
>--Original Message--
>How do I install a 'second instance' of MS SQL Server 7
>along side my existing production database. I'm told it
>is need to publish a second alias (seperate database)
>from the same server.
>Thanks,
>John
>.
>|||I assume your application has a hard-coded database name. In this case,
your only supported option is to upgrade to SQL Server 2000 so that you
can have multiple instances.
--
Hope this helps.
Dan Guzman
SQL Server MVP
--
SQL FAQ links (courtesy Neil Pike):
http://www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
http://www.sqlserverfaq.com
http://www.mssqlserver.com/faq
--
<anonymous@.discussions.microsoft.com> wrote in message
news:04bb01c3ae3d$4de18810$a501280a@.phx.gbl...
> I've inherited an app system that requires 1 database per
> sql server installation. a huge waste in my thinking...
> but I need to get the equivilent of multiple sql
> instances (as in sql2k) with sql 7. any ideas?
> Thanks,
> John
> >--Original Message--
> >How do I install a 'second instance' of MS SQL Server 7
> >along side my existing production database. I'm told it
> >is need to publish a second alias (seperate database)
> >from the same server.
> >
> >Thanks,
> >John
> >.
> >
along side my existing production database. I'm told it
is need to publish a second alias (seperate database)
from the same server.
Thanks,
Johnsql7 does not support named instances. hence, you only have 1 default
instance per server.
--
-oj
RAC v2.2 & QALite!
http://www.rac4sql.net
"John" <anonymous@.discussions.microsoft.com> wrote in message
news:03cc01c3ae2e$95ab0e50$a101280a@.phx.gbl...
> How do I install a 'second instance' of MS SQL Server 7
> along side my existing production database. I'm told it
> is need to publish a second alias (seperate database)
> from the same server.
> Thanks,
> John|||Is it at all possible to have 2 databases on a single sql
7 server system?
Thanks,
John
>--Original Message--
>sql7 does not support named instances. hence, you only
have 1 default
>instance per server.
>--
>-oj
>RAC v2.2 & QALite!
>http://www.rac4sql.net
>
>"John" <anonymous@.discussions.microsoft.com> wrote in
message
>news:03cc01c3ae2e$95ab0e50$a101280a@.phx.gbl...
>> How do I install a 'second instance' of MS SQL Server 7
>> along side my existing production database. I'm told it
>> is need to publish a second alias (seperate database)
>> from the same server.
>> Thanks,
>> John
>
>.
>|||John,
Yes. You can have upto 32767 databases per instance of sql7/2k.
--
-oj
RAC v2.2 & QALite!
http://www.rac4sql.net
<anonymous@.discussions.microsoft.com> wrote in message
news:0e9d01c3ae34$31a2a160$a601280a@.phx.gbl...
> Is it at all possible to have 2 databases on a single sql
> 7 server system?
> Thanks,
> John
> >--Original Message--
> >sql7 does not support named instances. hence, you only
> have 1 default
> >instance per server.
> >
> >--
> >-oj
> >RAC v2.2 & QALite!
> >http://www.rac4sql.net
> >
> >
> >"John" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:03cc01c3ae2e$95ab0e50$a101280a@.phx.gbl...
> >> How do I install a 'second instance' of MS SQL Server 7
> >> along side my existing production database. I'm told it
> >> is need to publish a second alias (seperate database)
> >> from the same server.
> >>
> >> Thanks,
> >> John
> >
> >
> >.
> >|||yes, you can have maximum of 32,767 database per SQL Server 7 instance.
--
- Vishal|||I've inherited an app system that requires 1 database per
sql server installation. a huge waste in my thinking...
but I need to get the equivilent of multiple sql
instances (as in sql2k) with sql 7. any ideas?
Thanks,
John
>--Original Message--
>How do I install a 'second instance' of MS SQL Server 7
>along side my existing production database. I'm told it
>is need to publish a second alias (seperate database)
>from the same server.
>Thanks,
>John
>.
>|||I assume your application has a hard-coded database name. In this case,
your only supported option is to upgrade to SQL Server 2000 so that you
can have multiple instances.
--
Hope this helps.
Dan Guzman
SQL Server MVP
--
SQL FAQ links (courtesy Neil Pike):
http://www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
http://www.sqlserverfaq.com
http://www.mssqlserver.com/faq
--
<anonymous@.discussions.microsoft.com> wrote in message
news:04bb01c3ae3d$4de18810$a501280a@.phx.gbl...
> I've inherited an app system that requires 1 database per
> sql server installation. a huge waste in my thinking...
> but I need to get the equivilent of multiple sql
> instances (as in sql2k) with sql 7. any ideas?
> Thanks,
> John
> >--Original Message--
> >How do I install a 'second instance' of MS SQL Server 7
> >along side my existing production database. I'm told it
> >is need to publish a second alias (seperate database)
> >from the same server.
> >
> >Thanks,
> >John
> >.
> >
26 - Error Locating Server/Instance Specified
Hi,
Have installed the club site starter kit on my pc and all it works well locally. I've used visual studio to publish my site to my third party webhost. Ive created the DB on their server and altered the connection string to:-
<
connectionStrings><!--<add name="ClubSiteDB" connectionString="Server=xx.xx.xx.xx;Database=somedatabasename;User ID=user;Password=Password;Trusted_Connection=False" providerName="System.Data.SqlClient"/>--></
connectionStrings>Now its on the webhosts server i get a System.Data.SqlClient.SqlException: 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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified).
This occurs when im trying to login in or register.
Can any one help.
Hi Ballantyne
This one usally means that your connection string is wrong - what to do is create a txt file on the web server and then rename it test.udl - now double click it and put in the details to the server and make sure you can connect to the database using the details your storing in your connection string.
Cheers
Gregor
First make sure your connection string is correct.
CheckSQL Server Troubleshooting to set everything properly.
If problem still exists make sure no firewall blocks your connection.
Hope it helps.
Saturday, February 25, 2012
2005 SP2 Install Would complete
Hi,
I have a problem with my SQL Server 2005 instance after trying to install SP2.
My machine has a default instance of SQL server 2005, and 2 instances of SQL 2005 express.
I installed Express SP2 and this installed without a hitch.
Then I installed SP2 for SQL Server 2005. After the install, all the components had installed correctly except the Database Engine, which had a status of failed. I did not investigate why, I simply re-ran the install.
It failed again, so I investigated further and I found out it failed because it had not been able to start the service VSS Writer. I looked at the service, and found I had changed the user which gives the service rights to start. I changed this back to Local System so the service could start correctly.
I then re-ran the SP2 install. This time it failed in a different place. The reason this time was my user was not a valid user for my server. This is a first, because I logged onto the database using this user name minutes before running the install. The install must have deleted my user. Then I tried to login using the sa account only for my server telling me that the sa account has been disabled.
I now cannot log into my database at all, and am stuck. If I try to rerun the install it tells me it cannot connect to the server to perform the update because there is no user.
Please Help!
Are you able to proceed past the Authentication screen in the SP2 installation Wizard? If not what error are you seeing? Can you post your summary.txt file, which will be in %programFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
Thanks,
Peter Saddow
|||There was a failure during installation search up in this log file for this message:
SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user 'TSI\Sean'. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
<EndFunc Name='ComponentUpgrade' Return='18456' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Mon Feb 26 14:11:18 2007
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='18456' GetLastError='0'>
MSI (s) (84:64) [14:11:19:083]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:083]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:099]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:099]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:099]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 14:11:19: CommitSqlUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 3.
Action ended 14:11:19: INSTALL. Return value 3.
--
Microsoft SQL Server 2005 Service Pack 2 Setup
--
Feature Selection
This setup program detected the following SQL Server 2005 features. Select the program
features that you would like to update. To see the details of a feature, click on the feature.
O Setup Support Files
X MSSQLSERVER
X Database Services
X Analysis Services Language ENU
X Reporting Services Platform x86
O SQLEXPRESS Edition DEVELOPER
O Database Services Status Upgraded
O Notification Services
O Integration Services
O SQL Server Native Client
O Client Components
O MSXML 6.0 Parser
O SQLXML4
O Backward Compatibility
O Microsoft SQL Server VSS Writer
|||After the previous screen I select next, then make sure Windows Authentication is selected then click next again.
-
Your account information could not be verified.
Press Ok to return to Authentication Mode screen to determine the reason for failure.
For setup to verify your credentials the services must be startable, connectable, and you must be a SQL Server administrator.
After I click Ok & Back the Feature Selection screen shows details of:
Login Failed: HResult 0xE9, Level 16, State 1 Shared Memory Provider: No process is on the other end of the pipe. Sqlcmd: Error: Microsoft SQL Native Client : Communication link failure.
And it shows a status of:
Not Valid
|||I am getting the same issue.. can you help? When i am trying to install SP2
Your account information could not be verified.
Press Ok to return to Authentication Mode screen to determine the reason for failure.
For setup to verify your credentials the services must be startable, connectable, and you must be a SQL Server administrator.
2005 SP2 Install Failed, and Now SQL Server is Unusable. - (SQL9_Hotfix_KB921896_sqlrun_sql.msp.
Hi,
I have a problem with my SQL Server 2005 instance after trying to install SP2.
My machine has a default instance of SQL server 2005, and 2 instances of SQL 2005 express.
I installed Express SP2 and this installed without a hitch.
Then I installed SP2 for SQL Server 2005. After the install, all the components had installed correctly except the Database Engine, which had a status of failed. I did not investigate why, I simply re-ran the install.
It failed again, so I investigated further and I found out it failed because it had not been able to start the service VSS Writer. I looked at the service, and found I had changed the user which gives the service rights to start. I changed this back to Local System so the service could start correctly.
I then re-ran the SP2 install. This time it failed in a different place. The reason this time was my user was not a valid user for my server. This is a first, because I logged onto the database using this user name minutes before running the install. The install must have deleted my user. Then I tried to login using the sa account only for my server telling me that the sa account has been disabled.
I now cannot log into my database at all, and am stuck. If I try to rerun the install it tells me it cannot connect to the server to perform the update because there is no user.
Please Help!
Are you able to proceed past the Authentication screen in the SP2 installation Wizard? If not what error are you seeing? Can you post your summary.txt file, which will be in %programFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
Thanks,
Peter Saddow
|||There was a failure during installation search up in this log file for this message:
SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user 'TSI\Sean'. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
<EndFunc Name='ComponentUpgrade' Return='18456' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Mon Feb 26 14:11:18 2007
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='18456' GetLastError='0'>
MSI (s) (84:64) [14:11:19:083]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:083]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:099]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:099]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:099]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 14:11:19: CommitSqlUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 3.
Action ended 14:11:19: INSTALL. Return value 3.
--
Microsoft SQL Server 2005 Service Pack 2 Setup
--
Feature Selection
This setup program detected the following SQL Server 2005 features. Select the program
features that you would like to update. To see the details of a feature, click on the feature.
O Setup Support Files
X MSSQLSERVER
X Database Services
X Analysis Services Language ENU
X Reporting Services Platform x86
O SQLEXPRESS Edition DEVELOPER
O Database Services Status Upgraded
O Notification Services
O Integration Services
O SQL Server Native Client
O Client Components
O MSXML 6.0 Parser
O SQLXML4
O Backward Compatibility
O Microsoft SQL Server VSS Writer
|||After the previous screen I select next, then make sure Windows Authentication is selected then click next again.
-
Your account information could not be verified.
Press Ok to return to Authentication Mode screen to determine the reason for failure.
For setup to verify your credentials the services must be startable, connectable, and you must be a SQL Server administrator.
After I click Ok & Back the Feature Selection screen shows details of:
Login Failed: HResult 0xE9, Level 16, State 1 Shared Memory Provider: No process is on the other end of the pipe. Sqlcmd: Error: Microsoft SQL Native Client : Communication link failure.
And it shows a status of:
Not Valid
|||I am getting the same issue.. can you help? When i am trying to install SP2
Your account information could not be verified.
Press Ok to return to Authentication Mode screen to determine the reason for failure.
For setup to verify your credentials the services must be startable, connectable, and you must be a SQL Server administrator.
2005 SP2 Install Failed, and Now SQL Server is Unusable. - (SP2 Install Screen Shot)
Hi,
I have a problem with my SQL Server 2005 instance after trying to install SP2.
My machine has a default instance of SQL server 2005, and 2 instances of SQL 2005 express.
I installed Express SP2 and this installed without a hitch.
Then I installed SP2 for SQL Server 2005. After the install, all the components had installed correctly except the Database Engine, which had a status of failed. I did not investigate why, I simply re-ran the install.
It failed again, so I investigated further and I found out it failed because it had not been able to start the service VSS Writer. I looked at the service, and found I had changed the user which gives the service rights to start. I changed this back to Local System so the service could start correctly.
I then re-ran the SP2 install. This time it failed in a different place. The reason this time was my user was not a valid user for my server. This is a first, because I logged onto the database using this user name minutes before running the install. The install must have deleted my user. Then I tried to login using the sa account only for my server telling me that the sa account has been disabled.
I now cannot log into my database at all, and am stuck. If I try to rerun the install it tells me it cannot connect to the server to perform the update because there is no user.
Please Help!
Are you able to proceed past the Authentication screen in the SP2 installation Wizard? If not what error are you seeing? Can you post your summary.txt file, which will be in %programFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
Thanks,
Peter Saddow
|||There was a failure during installation search up in this log file for this message:
SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user 'TSI\Sean'. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
<EndFunc Name='ComponentUpgrade' Return='18456' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Mon Feb 26 14:11:18 2007
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='18456' GetLastError='0'>
MSI (s) (84:64) [14:11:19:083]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:083]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:099]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:099]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:099]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 14:11:19: CommitSqlUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 3.
Action ended 14:11:19: INSTALL. Return value 3.
--
Microsoft SQL Server 2005 Service Pack 2 Setup
--
Feature Selection
This setup program detected the following SQL Server 2005 features. Select the program
features that you would like to update. To see the details of a feature, click on the feature.
O Setup Support Files
X MSSQLSERVER
X Database Services
X Analysis Services Language ENU
X Reporting Services Platform x86
O SQLEXPRESS Edition DEVELOPER
O Database Services Status Upgraded
O Notification Services
O Integration Services
O SQL Server Native Client
O Client Components
O MSXML 6.0 Parser
O SQLXML4
O Backward Compatibility
O Microsoft SQL Server VSS Writer
|||After the previous screen I select next, then make sure Windows Authentication is selected then click next again.
-
Your account information could not be verified.
Press Ok to return to Authentication Mode screen to determine the reason for failure.
For setup to verify your credentials the services must be startable, connectable, and you must be a SQL Server administrator.
After I click Ok & Back the Feature Selection screen shows details of:
Login Failed: HResult 0xE9, Level 16, State 1 Shared Memory Provider: No process is on the other end of the pipe. Sqlcmd: Error: Microsoft SQL Native Client : Communication link failure.
And it shows a status of:
Not Valid
|||I am getting the same issue.. can you help? When i am trying to install SP2
Your account information could not be verified.
Press Ok to return to Authentication Mode screen to determine the reason for failure.
For setup to verify your credentials the services must be startable, connectable, and you must be a SQL Server administrator.
2005 SP2 Install Failed, and Now SQL Server is Unusable.
Hi,
I have a problem with my SQL Server 2005 instance after trying to install SP2.
My machine has a default instance of SQL server 2005, and 2 instances of SQL 2005 express.
I installed Express SP2 and this installed without a hitch.
Then I installed SP2 for SQL Server 2005. After the install, all the components had installed correctly except the Database Engine, which had a status of failed. I did not investigate why, I simply re-ran the install.
It failed again, so I investigated further and I found out it failed because it had not been able to start the service VSS Writer. I looked at the service, and found I had changed the user which gives the service rights to start. I changed this back to Local System so the service could start correctly.
I then re-ran the SP2 install. This time it failed in a different place. The reason this time was my user was not a valid user for my server. This is a first, because I logged onto the database using this user name minutes before running the install. The install must have deleted my user. Then I tried to login using the sa account only for my server telling me that the sa account has been disabled.
I now cannot log into my database at all, and am stuck. If I try to rerun the install it tells me it cannot connect to the server to perform the update because there is no user.
Please Help!
Are you able to proceed past the Authentication screen in the SP2 installation Wizard? If not what error are you seeing? Can you post your summary.txt file, which will be in %programFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
Thanks,
Peter Saddow
|||There was a failure during installation search up in this log file for this message:
SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user 'TSI\Sean'. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
<EndFunc Name='ComponentUpgrade' Return='18456' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Mon Feb 26 14:11:18 2007
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='18456' GetLastError='0'>
MSI (s) (84:64) [14:11:19:083]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:083]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:099]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:099]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:099]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 14:11:19: CommitSqlUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 3.
Action ended 14:11:19: INSTALL. Return value 3.
--
Microsoft SQL Server 2005 Service Pack 2 Setup
--
Feature Selection
This setup program detected the following SQL Server 2005 features. Select the program
features that you would like to update. To see the details of a feature, click on the feature.
O Setup Support Files
X MSSQLSERVER
X Database Services
X Analysis Services Language ENU
X Reporting Services Platform x86
O SQLEXPRESS Edition DEVELOPER
O Database Services Status Upgraded
O Notification Services
O Integration Services
O SQL Server Native Client
O Client Components
O MSXML 6.0 Parser
O SQLXML4
O Backward Compatibility
O Microsoft SQL Server VSS Writer
|||After the previous screen I select next, then make sure Windows Authentication is selected then click next again.
-
Your account information could not be verified.
Press Ok to return to Authentication Mode screen to determine the reason for failure.
For setup to verify your credentials the services must be startable, connectable, and you must be a SQL Server administrator.
After I click Ok & Back the Feature Selection screen shows details of:
Login Failed: HResult 0xE9, Level 16, State 1 Shared Memory Provider: No process is on the other end of the pipe. Sqlcmd: Error: Microsoft SQL Native Client : Communication link failure.
And it shows a status of:
Not Valid
|||I am getting the same issue.. can you help? When i am trying to install SP2
Your account information could not be verified.
Press Ok to return to Authentication Mode screen to determine the reason for failure.
For setup to verify your credentials the services must be startable, connectable, and you must be a SQL Server administrator.
Sunday, February 19, 2012
2005 mgmt studio -> 2000 clustered instance
Is there any way to connect to a SQL Server 2000 clustered instance uinsg 2005 Management Studio? I have not been able to get this to work. Is this a known inability of 2005 mgmt studio?
Hi,
got no problem. Which error are you getting ? Didi you connect to the virtual adress or a node adress. In some cases the direct node adresses aren′′t accessible due to network restrictions.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
|||Connecting to the virtual sql server address. The error message is "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 default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)|||Found it...problem was in getting around the firewall using tcp/ip. After changing the protocol order on the client side and using Named Pipes before tcp/ip, the problem was resolved. Interestingly enough, this was not an issue with SQL Server 2000 EM.Saturday, February 11, 2012
2005 CTP Connection error
When I try to connect to the 2005 CTP SQL server in any of the VBexpress software packages I get the gfollowing error
user instance login flag not supported in this version of SQL
I am not sure what to check or what I may have missed in the SQL server setupThe User Instance flag is only supported in the express SKU, are you connected to Express or another version of SQL Server? You can check by running select @.@.version
user instance login flag not supported in this version of SQL
I am not sure what to check or what I may have missed in the SQL server setupThe User Instance flag is only supported in the express SKU, are you connected to Express or another version of SQL Server? You can check by running select @.@.version
-Euan|||I am trying to connect to the sql 2005 version CTP [not the express version]|||All versions(SKUs) are part of CTP.
But if you are convinced that you are not connecting to express then this is the problem you need to remove the User Instance from the connection string.
-Euan|||Yes I am sure I am using the non-express version. However, to connect I am using the wizards that come with the Visual Studio Express products...I hate be sound ignorant but this is not my area of expertise...how do I remove that user instance from the wizard?
and from the the SQL server management studio It tell me SQL Server 9.0.1187|||Actually I saw in the advanced area where to change that. But if I do I get this message
"Unable to open Phycical file...The process cannot access the file because is it in use by another process..."|||SQL Server 9.0.1187|||Ah ok there is another setting that is used by express that you need to remove and thats the AttachDBFilename.
I suspect you you selected in the Wizard to connect to database file, try connecting the database instead.
-Euan|||I would lvoe to but the only connection options I have are
Microsoft Access Databse File
Microsoft SQL server Database File|||
I had the same problem and it was solved choosing the appropriate MDF file to the field "AttachDBFileNAme" and inserting the logical name of DB (the name that appears on SQL Server Man. Studio) in the field "InitialCatalog".
No other configurations were needed on SQL Server
2005 CTP Connection error
When I try to connect to the 2005 CTP SQL server in any of the VBexpress software packages I get the gfollowing error
user instance login flag not supported in this version of SQL
I am not sure what to check or what I may have missed in the SQL server setupThe User Instance flag is only supported in the express SKU, are you connected to Express or another version of SQL Server? You can check by running select @.@.version
user instance login flag not supported in this version of SQL
I am not sure what to check or what I may have missed in the SQL server setupThe User Instance flag is only supported in the express SKU, are you connected to Express or another version of SQL Server? You can check by running select @.@.version
-Euan|||I am trying to connect to the sql 2005 version CTP [not the express version]|||All versions(SKUs) are part of CTP.
But if you are convinced that you are not connecting to express then this is the problem you need to remove the User Instance from the connection string.
-Euan|||Yes I am sure I am using the non-express version. However, to connect I am using the wizards that come with the Visual Studio Express products...I hate be sound ignorant but this is not my area of expertise...how do I remove that user instance from the wizard?
and from the the SQL server management studio It tell me SQL Server 9.0.1187|||Actually I saw in the advanced area where to change that. But if I do I get this message
"Unable to open Phycical file...The process cannot access the file because is it in use by another process..."|||SQL Server 9.0.1187|||Ah ok there is another setting that is used by express that you need to remove and thats the AttachDBFilename.
I suspect you you selected in the Wizard to connect to database file, try connecting the database instead.
-Euan|||I would lvoe to but the only connection options I have are
Microsoft Access Databse File
Microsoft SQL server Database File|||
I had the same problem and it was solved choosing the appropriate MDF file to the field "AttachDBFileNAme" and inserting the logical name of DB (the name that appears on SQL Server Man. Studio) in the field "InitialCatalog".
No other configurations were needed on SQL Server
2005 Create new instance, replace sqlexpress
I had installed Sql Express on my machine, now i have Visual Studio Pro
2005 which came with Sql Server 2005 Developer edition. I carefully
uninstalled anything I could find that was related to the express
edition before installing Developer. But still when I try to connect in
Management studio, it gives me only my Sql 2000 instance or a 2005
instance name SqlExpress. It fails trying to connect to the 2005
instance because apparently Express can't be connected to with this
tool.
Do I need to add a new instance? How do I get rid of the old one and
install a new one?
Any guidance appreciated, coming up with nothing in Books online and
this ng.
Bob(rvgrahamsevatenein@.sbcglobal.net) writes:
> I had installed Sql Express on my machine, now i have Visual Studio Pro
> 2005 which came with Sql Server 2005 Developer edition. I carefully
> uninstalled anything I could find that was related to the express
> edition before installing Developer. But still when I try to connect in
> Management studio, it gives me only my Sql 2000 instance or a 2005
> instance name SqlExpress. It fails trying to connect to the 2005
> instance because apparently Express can't be connected to with this
> tool.
> Do I need to add a new instance? How do I get rid of the old one and
> install a new one?
> Any guidance appreciated, coming up with nothing in Books online and
> this ng.
How did you run the install of Developer edition? Did you require a
named instance, or did you select a default instance? If you selected
the default instance, and you had SQL 2000 installed as a default instance,
then that install would have been upgraded to SQL 2005. Have you connected
to the instance check what @.@.version says?
Note that for an upgrage of SQL 2000 to succed you need at least SP3 of
SQL 2000.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Hi
Uninstall SQL Server Express Edition with all related installation (See in
ADD\REMOVE Program)
Moreover if you have a network (I have encountered some problems when it got
to set security File Stat )
, I'd suggest to unplug a cable and run SETUP
<rvgrahamsevatenein@.sbcglobal.net> wrote in message
news:1138996401.832192.216900@.z14g2000cwz.googlegroups.com...
>I had installed Sql Express on my machine, now i have Visual Studio Pro
> 2005 which came with Sql Server 2005 Developer edition. I carefully
> uninstalled anything I could find that was related to the express
> edition before installing Developer. But still when I try to connect in
> Management studio, it gives me only my Sql 2000 instance or a 2005
> instance name SqlExpress. It fails trying to connect to the 2005
> instance because apparently Express can't be connected to with this
> tool.
> Do I need to add a new instance? How do I get rid of the old one and
> install a new one?
> Any guidance appreciated, coming up with nothing in Books online and
> this ng.
> Bob
>|||Thank you for your replies,
I discovered when I did this same install on my home development
machine that what I had done wrong was to not specify for the Developer
Edition install to create a new named instance.
I was also unaware that VS2005 setup also installs SqlExpress, and that
it's apparently intentional that you end up with both running on your
machine. I'm assuming this is so you have Express available for testing
and deploying client apps containing stand-alone SqlExpress instances?
Bob Graham
2005 which came with Sql Server 2005 Developer edition. I carefully
uninstalled anything I could find that was related to the express
edition before installing Developer. But still when I try to connect in
Management studio, it gives me only my Sql 2000 instance or a 2005
instance name SqlExpress. It fails trying to connect to the 2005
instance because apparently Express can't be connected to with this
tool.
Do I need to add a new instance? How do I get rid of the old one and
install a new one?
Any guidance appreciated, coming up with nothing in Books online and
this ng.
Bob(rvgrahamsevatenein@.sbcglobal.net) writes:
> I had installed Sql Express on my machine, now i have Visual Studio Pro
> 2005 which came with Sql Server 2005 Developer edition. I carefully
> uninstalled anything I could find that was related to the express
> edition before installing Developer. But still when I try to connect in
> Management studio, it gives me only my Sql 2000 instance or a 2005
> instance name SqlExpress. It fails trying to connect to the 2005
> instance because apparently Express can't be connected to with this
> tool.
> Do I need to add a new instance? How do I get rid of the old one and
> install a new one?
> Any guidance appreciated, coming up with nothing in Books online and
> this ng.
How did you run the install of Developer edition? Did you require a
named instance, or did you select a default instance? If you selected
the default instance, and you had SQL 2000 installed as a default instance,
then that install would have been upgraded to SQL 2005. Have you connected
to the instance check what @.@.version says?
Note that for an upgrage of SQL 2000 to succed you need at least SP3 of
SQL 2000.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Hi
Uninstall SQL Server Express Edition with all related installation (See in
ADD\REMOVE Program)
Moreover if you have a network (I have encountered some problems when it got
to set security File Stat )
, I'd suggest to unplug a cable and run SETUP
<rvgrahamsevatenein@.sbcglobal.net> wrote in message
news:1138996401.832192.216900@.z14g2000cwz.googlegroups.com...
>I had installed Sql Express on my machine, now i have Visual Studio Pro
> 2005 which came with Sql Server 2005 Developer edition. I carefully
> uninstalled anything I could find that was related to the express
> edition before installing Developer. But still when I try to connect in
> Management studio, it gives me only my Sql 2000 instance or a 2005
> instance name SqlExpress. It fails trying to connect to the 2005
> instance because apparently Express can't be connected to with this
> tool.
> Do I need to add a new instance? How do I get rid of the old one and
> install a new one?
> Any guidance appreciated, coming up with nothing in Books online and
> this ng.
> Bob
>|||Thank you for your replies,
I discovered when I did this same install on my home development
machine that what I had done wrong was to not specify for the Developer
Edition install to create a new named instance.
I was also unaware that VS2005 setup also installs SqlExpress, and that
it's apparently intentional that you end up with both running on your
machine. I'm assuming this is so you have Express available for testing
and deploying client apps containing stand-alone SqlExpress instances?
Bob Graham
2005 Cluster install issue
Hello
I am having a problem installing the first instance in our two node cluster. We're running 64-bit 2003. I'm trying to install the database engine and client tools only, so of course I get the IIS warning for both nodes. This is expected because I don't want Reporting Services. So the install should still work. However, I'm also getting the ASP.net registration message on only one node.
"Failed to find the ASP.Net Version Registration with Microsoft Internet Information Services (IIS)."
I suspect that I should be getting the error on both nodes because I don't have IIS installed on either node. But again, I only get a warning for one node. This is probably the cause of my failure because it sees the nodes as being out of sync. I'm not sure how to correct this though when it appears that the nodes are exactly the same. Does anybody have any ideas? Thanks in advance!
:eek:Have you checked the SQL installation log?
I am having a problem installing the first instance in our two node cluster. We're running 64-bit 2003. I'm trying to install the database engine and client tools only, so of course I get the IIS warning for both nodes. This is expected because I don't want Reporting Services. So the install should still work. However, I'm also getting the ASP.net registration message on only one node.
"Failed to find the ASP.Net Version Registration with Microsoft Internet Information Services (IIS)."
I suspect that I should be getting the error on both nodes because I don't have IIS installed on either node. But again, I only get a warning for one node. This is probably the cause of my failure because it sees the nodes as being out of sync. I'm not sure how to correct this though when it appears that the nodes are exactly the same. Does anybody have any ideas? Thanks in advance!
:eek:Have you checked the SQL installation log?
2005 Cluster Install Error
I'm having problems installing 2005 Ent on my Win 2003 SP1 2 node cluster.
Please note this cluster has a SQL 2000 (SP4) virtual server/instance already
installed. I would like to run them side by side.
installing using the setup wizard I get error about the schedule task
failing to start on the 2nd node. Looking through the log files the setup
program on the 2nd node has thrown an exception error, core.log shows this:
Complete: ParseBootstrapOptionsAction at: 2005/10/7 13:25:6, returned false
Error: Action "ParseBootstrapOptionsAction" failed during execution. Error
information reported during run:
Could not decrypt command line due to WinException.
Error Code: -2146893822
Windows Error Text: Bad Hash.
Source File Name: cryptohelper\cryptpassword.cpp
Compiler Timestamp: Mon Jul 18 01:10:20 2005
Function Name: sqls::CryptPassword::UnprotectString
Source Line Number: 311
Running: ValidateWinNTAction at: 2005/10/7 13:25:6
Complete: ValidateWinNTAction at: 2005/10/7 13:25:6, returned true
Running: ValidateMinOSAction at: 2005/10/7 13:25:6
Complete: ValidateMinOSAction at: 2005/10/7 13:25:6, returned true
Running: PerformSCCAction at: 2005/10/7 13:25:6
Complete: PerformSCCAction at: 2005/10/7 13:25:6, returned true
Running: ActivateLoggingAction at: 2005/10/7 13:25:6
Error: Action "ActivateLoggingAction" threw an exception during execution.
Error information reported during run:
00D7CFC8Unable to proceed with setup, there was a command line parsing
error. : -2146893822
Error Code: -2146893822
Windows Error Text: Bad Hash.
Source File Name: cryptohelper\cryptpassword.cpp
Compiler Timestamp: Mon Jul 18 01:10:20 2005
Function Name: sqls::CryptPassword::UnprotectString
Source Line Number: 311
Delay load of action "UploadDrWatsonLogAction" returned nothing. No action
will occur as a result.
Message pump returning: 2148073474
-- END OF OUTPUT --
I've trying to work around it I have tried installing from the command line.
This gets much further with setup starting correctly on both nodes. I get as
far as installing the actual SQL Server Service instance then I'm thrown an
error. Summary.log shows:
Machine : SERVERA
Product : SQL Server Database Services
Error : A domain group is missing for one or more services. To
install SQL Server 2005 as a failover cluster, domain groups must be
specified for all the clustered services being installed .To proceed, enter
the missing domain group information.
The domain group cannot be validated for the service SQL Server.
Machine : SERVERA
Product : SQL Server Database Services
Error : A domain group is missing for one or more services. To
install SQL Server 2005 as a failover cluster, domain groups must be
specified for all the clustered services being installed .To proceed, enter
the missing domain group information.
The domain group cannot be validated for the service SQL Server.
Machine : SERVERA
Product : Microsoft SQL Server 2005
Product Version : 9.00.1399.06
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0014_LON-IMS01A_SQL.log
Last Action : Validate_ServiceAccounts
Error String : A domain group is missing for one or more services. To
install SQL Server 2005 as a failover cluster, domain groups must be
specified for all the clustered services being installed .To proceed, enter
the missing domain group information.
The domain group cannot be validated for the service SQL Server.
Error Number : 28130
-- END OF OUTPUT
In the GUI you get asked for Domain Groups for each service, the
documentation for the command line installer doesn't tell me what the
parameters are for this. Do I need them, is the documentation missing
something? Also I'm not too sure what the ADMINPASSWORD= paramater is for -
I'm putting in my domain password currently - again teh documentation isn't
too hot for this.
I'm running out of ideas. If anyone has any suggestions please let me know!
Thanks
I figured out the problem to the command line - why the GUI crashed I do not
know.
BOL does not document any of these parameters for the command line which are
REQUIRED for a cluster install:
SQLBROWSERACCOUNT="DOMAIN\USER"
SQLBROWSERPASSWORD="PASSWORD"
SQLCLUSTERGROUP="DOMAIN\GROUP"
AGTCLUSTERGROUP="DOMAIN\GROUP"
FTSCLUSTERGROUP="DOMAIN\GROUP"
However if you look in the template.ini file on your install cd you will
find details of how and when to use them.
A very dissapointed customer.
"Simon" wrote:
> I'm having problems installing 2005 Ent on my Win 2003 SP1 2 node cluster.
> Please note this cluster has a SQL 2000 (SP4) virtual server/instance already
> installed. I would like to run them side by side.
> installing using the setup wizard I get error about the schedule task
> failing to start on the 2nd node. Looking through the log files the setup
> program on the 2nd node has thrown an exception error, core.log shows this:
> Complete: ParseBootstrapOptionsAction at: 2005/10/7 13:25:6, returned false
> Error: Action "ParseBootstrapOptionsAction" failed during execution. Error
> information reported during run:
> Could not decrypt command line due to WinException.
> Error Code: -2146893822
> Windows Error Text: Bad Hash.
> Source File Name: cryptohelper\cryptpassword.cpp
> Compiler Timestamp: Mon Jul 18 01:10:20 2005
> Function Name: sqls::CryptPassword::UnprotectString
> Source Line Number: 311
> Running: ValidateWinNTAction at: 2005/10/7 13:25:6
> Complete: ValidateWinNTAction at: 2005/10/7 13:25:6, returned true
> Running: ValidateMinOSAction at: 2005/10/7 13:25:6
> Complete: ValidateMinOSAction at: 2005/10/7 13:25:6, returned true
> Running: PerformSCCAction at: 2005/10/7 13:25:6
> Complete: PerformSCCAction at: 2005/10/7 13:25:6, returned true
> Running: ActivateLoggingAction at: 2005/10/7 13:25:6
> Error: Action "ActivateLoggingAction" threw an exception during execution.
> Error information reported during run:
> 00D7CFC8Unable to proceed with setup, there was a command line parsing
> error. : -2146893822
> Error Code: -2146893822
> Windows Error Text: Bad Hash.
> Source File Name: cryptohelper\cryptpassword.cpp
> Compiler Timestamp: Mon Jul 18 01:10:20 2005
> Function Name: sqls::CryptPassword::UnprotectString
> Source Line Number: 311
> Delay load of action "UploadDrWatsonLogAction" returned nothing. No action
> will occur as a result.
> Message pump returning: 2148073474
>
> -- END OF OUTPUT --
>
> I've trying to work around it I have tried installing from the command line.
> This gets much further with setup starting correctly on both nodes. I get as
> far as installing the actual SQL Server Service instance then I'm thrown an
> error. Summary.log shows:
>
> Machine : SERVERA
> Product : SQL Server Database Services
> Error : A domain group is missing for one or more services. To
> install SQL Server 2005 as a failover cluster, domain groups must be
> specified for all the clustered services being installed .To proceed, enter
> the missing domain group information.
> The domain group cannot be validated for the service SQL Server.
> ----
> Machine : SERVERA
> Product : SQL Server Database Services
> Error : A domain group is missing for one or more services. To
> install SQL Server 2005 as a failover cluster, domain groups must be
> specified for all the clustered services being installed .To proceed, enter
> the missing domain group information.
> The domain group cannot be validated for the service SQL Server.
> ----
> Machine : SERVERA
> Product : Microsoft SQL Server 2005
> Product Version : 9.00.1399.06
> Install : Failed
> Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0014_LON-IMS01A_SQL.log
> Last Action : Validate_ServiceAccounts
> Error String : A domain group is missing for one or more services. To
> install SQL Server 2005 as a failover cluster, domain groups must be
> specified for all the clustered services being installed .To proceed, enter
> the missing domain group information.
> The domain group cannot be validated for the service SQL Server.
> Error Number : 28130
>
> -- END OF OUTPUT
>
> In the GUI you get asked for Domain Groups for each service, the
> documentation for the command line installer doesn't tell me what the
> parameters are for this. Do I need them, is the documentation missing
> something? Also I'm not too sure what the ADMINPASSWORD= paramater is for -
> I'm putting in my domain password currently - again teh documentation isn't
> too hot for this.
> I'm running out of ideas. If anyone has any suggestions please let me know!
> Thanks
>
|||Simon,
yep I noticed that too. Just an omission in BOL. I sent feedback via the BOL
entry for installing a Cluster from template/unattend, suggest you do the
same.
Andy.
"Simon" <Simon@.discussions.microsoft.com> wrote in message
news:ECC70F54-2E3D-43BE-AE8B-5B91EFC74E60@.microsoft.com...[vbcol=seagreen]
>I figured out the problem to the command line - why the GUI crashed I do
>not
> know.
> BOL does not document any of these parameters for the command line which
> are
> REQUIRED for a cluster install:
> SQLBROWSERACCOUNT="DOMAIN\USER"
> SQLBROWSERPASSWORD="PASSWORD"
> SQLCLUSTERGROUP="DOMAIN\GROUP"
> AGTCLUSTERGROUP="DOMAIN\GROUP"
> FTSCLUSTERGROUP="DOMAIN\GROUP"
> However if you look in the template.ini file on your install cd you will
> find details of how and when to use them.
> A very dissapointed customer.
>
>
> "Simon" wrote:
|||That information is in the Readme notes as well as the Readme errata posted
online.
ALWAYS READ THE README.
Anthony Thomas
"Andy Ball" <ng@.spamno77greenfell.com> wrote in message
news:u%23k3gf05FHA.3976@.TK2MSFTNGP15.phx.gbl...
> Simon,
> yep I noticed that too. Just an omission in BOL. I sent feedback via the
BOL[vbcol=seagreen]
> entry for installing a Cluster from template/unattend, suggest you do the
> same.
> Andy.
> "Simon" <Simon@.discussions.microsoft.com> wrote in message
> news:ECC70F54-2E3D-43BE-AE8B-5B91EFC74E60@.microsoft.com...
setup[vbcol=seagreen]
get[vbcol=seagreen]
thrown[vbcol=seagreen]
To[vbcol=seagreen]
--[vbcol=seagreen]
To[vbcol=seagreen]
--[vbcol=seagreen]
To
>
|||must be going blind - i'm looking @. ReadmeSQL2005.htm from the Dev \ MSDN
edition and Q907284 I can't see it
Andy.
"Anthony Thomas" <ALThomas@.kc.rr.com> wrote in message
news:OaT56MI6FHA.1184@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> That information is in the Readme notes as well as the Readme errata
> posted
> online.
> ALWAYS READ THE README.
>
> Anthony Thomas
>
> --
> "Andy Ball" <ng@.spamno77greenfell.com> wrote in message
> news:u%23k3gf05FHA.3976@.TK2MSFTNGP15.phx.gbl...
> BOL
> setup
> get
> thrown
> To
> --
> To
> --
> To
>
|||At the time, this seemed clearer, but it appears you are speaking of
something else. There is also the Setupsql9.chm file that is seperate from
the BOL. You are right; it is unclear.
Microsoft SQL Server September 2005 Community Technology Preview
http://download.microsoft.com/downlo...ntat ion_cuy1
3.5.15 Corrections to the Names of Security Groups Created During Setup
During setup, SQL Server 2005 adds the following security groups to Windows:
SQLServer2005DTSUser$ComputerName
SQLServer2005MSFTEUser$ComputerName$InstanceName
SQLServer2005MSOLAPUser$ComputerName$InstanceName
SQLServer2005MSSQLServerADHelperUser$ComputerName
SQLServer2005MSSQLUser$ComputerName$InstanceName
SQLServer2005NotificationServicesUser$ComputerName
SQLServer2005ReportingServicesWebServiceUser$Compu terName$InstanceName
SQLServer2005ReportServerUser$ComputerName$Instanc eName
SQLServer2005SQLAgentUser$ComputerName$InstanceNam e
SQLServer2005SQLBrowserUser$ComputerName
These groups simplify granting permissions required to run SQL Server
Windows services and other executables. They also help secure SQL Server
files.
In SQL Server Books Online, $ComputerName was omitted from the names. The
computer name has since been added to the group names to uniquely identify
each group. Unique group names are necessary if SQL Server 2005 is installed
on domain controllers. For all references to security groups that start with
"SQLServer2005," substitute the appropriate group name listed above.
3.5.17 Restrictions for Service Accounts on a Failover Cluster
SQL Server service, SQL Server Agent service, Analysis Services service, and
Full-Text Search service must run as domain accounts that are members of the
built-in Administrators group on each node of the cluster.
Sincerely,
Anthony Thomas
"Andy Ball" <ng@.spamno77greenfell.com> wrote in message
news:uEuMBdV6FHA.1000@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> must be going blind - i'm looking @. ReadmeSQL2005.htm from the Dev \ MSDN
> edition and Q907284 I can't see it
> Andy.
> "Anthony Thomas" <ALThomas@.kc.rr.com> wrote in message
> news:OaT56MI6FHA.1184@.TK2MSFTNGP12.phx.gbl...
>
the[vbcol=seagreen]
the[vbcol=seagreen]
do[vbcol=seagreen]
server/instance[vbcol=seagreen]
task[vbcol=seagreen]
shows[vbcol=seagreen]
returned[vbcol=seagreen]
parsing[vbcol=seagreen]
command[vbcol=seagreen]
I[vbcol=seagreen]
services.[vbcol=seagreen]
proceed,[vbcol=seagreen]
-[vbcol=seagreen]
services.[vbcol=seagreen]
proceed,[vbcol=seagreen]
-[vbcol=seagreen]
services.[vbcol=seagreen]
proceed,[vbcol=seagreen]
the[vbcol=seagreen]
missing[vbcol=seagreen]
documentation[vbcol=seagreen]
me
>
|||From the Setupsql9.chm, regarding your original issue:
How to: Install SQL Server 2005 from the Command Prompt
For failover cluster installations, you must be a local administrator with
permissions to logon as a service, and to act as part of the operating
system on all nodes of the virtual server.
start /wait setup.exe /qn VS=<VSName> INSTALLVS=Analysis_Server
INSTANCENAME=<InstanceName> ADDLOCAL=Analysis_Server ADDNODE=n
GROUP=<NotSQLDiskGroup> IP=<IP,Networkname> ADMINPASSWORD=<StrongPassword>
SAPWD=<StrongPassword> INSTALLSQLDIR=<InstallationPath>
INSTALLSQLDATADIR=<ShareDrivePath> ASACCOUNT=<domain\user>
ASPASSWORD=<DomainUserPassword> SQLBROWSERACCOUNT=<domain\user>
SQLBROWSERPASSWORD=<DomainUserPassword> SQLREPORTING=1
Start /wait <DVD Drive>\setup.exe /qn VS=<VSName> INSTALLVS=SQL_Engine
INSTANCENAME=<InstanceName> ADDLOCAL=SQL_Engine,Client_Components
ADDNODE=<NodeName1,NodeName2> GROUP=<Diskgroup> IP=<IP,Networkname>
ADMINPASSWORD=<StrongPassword> SAPWD=<StrongPassord>
INSTALLSQLDIR=<InstallationPath> INSTALLSQLDATADIR=<ShareDrivePath>
SQLACCOUNT=<domain\user> SQLPASSWORD=<DomainUserPassword>
AGTACCOUNT=<domain\user> AGTPASSWORD=<DomainUserPassword>
The same holds true for the other components.
Sincerely,
Anthony Thomas
"Anthony Thomas" <ALThomas@.kc.rr.com> wrote in message
news:eETZ86g6FHA.1000@.tk2msftngp13.phx.gbl...
> At the time, this seemed clearer, but it appears you are speaking of
> something else. There is also the Setupsql9.chm file that is seperate
from
> the BOL. You are right; it is unclear.
> Microsoft SQL Server September 2005 Community Technology Preview
>
http://download.microsoft.com/downlo...ntat ion_cuy1
> 3.5.15 Corrections to the Names of Security Groups Created During Setup
> During setup, SQL Server 2005 adds the following security groups to
Windows:
> SQLServer2005DTSUser$ComputerName
> SQLServer2005MSFTEUser$ComputerName$InstanceName
> SQLServer2005MSOLAPUser$ComputerName$InstanceName
> SQLServer2005MSSQLServerADHelperUser$ComputerName
> SQLServer2005MSSQLUser$ComputerName$InstanceName
> SQLServer2005NotificationServicesUser$ComputerName
> SQLServer2005ReportingServicesWebServiceUser$Compu terName$InstanceName
> SQLServer2005ReportServerUser$ComputerName$Instanc eName
> SQLServer2005SQLAgentUser$ComputerName$InstanceNam e
> SQLServer2005SQLBrowserUser$ComputerName
> These groups simplify granting permissions required to run SQL Server
> Windows services and other executables. They also help secure SQL Server
> files.
> In SQL Server Books Online, $ComputerName was omitted from the names. The
> computer name has since been added to the group names to uniquely identify
> each group. Unique group names are necessary if SQL Server 2005 is
installed
> on domain controllers. For all references to security groups that start
with
> "SQLServer2005," substitute the appropriate group name listed above.
> 3.5.17 Restrictions for Service Accounts on a Failover Cluster
> SQL Server service, SQL Server Agent service, Analysis Services service,
and
> Full-Text Search service must run as domain accounts that are members of
the[vbcol=seagreen]
> built-in Administrators group on each node of the cluster.
>
> Sincerely,
>
> Anthony Thomas
> --
> "Andy Ball" <ng@.spamno77greenfell.com> wrote in message
> news:uEuMBdV6FHA.1000@.tk2msftngp13.phx.gbl...
MSDN[vbcol=seagreen]
> the
> the
I[vbcol=seagreen]
> do
> server/instance
> task
the[vbcol=seagreen]
> shows
> returned
execution.[vbcol=seagreen]
> parsing
No[vbcol=seagreen]
> command
nodes.[vbcol=seagreen]
> I
> services.
be[vbcol=seagreen]
> proceed,
> -
> services.
be[vbcol=seagreen]
> proceed,
> -
> services.
be[vbcol=seagreen]
> proceed,
> the
> missing
paramater
> documentation
> me
>
|||and the portion I presume is talking about the Local Groups that created on
the Server where SQL is installed. Simon's original post is about the DOMAIN
local groups that are required for Clustering.
cheers,
Andy.
"Anthony Thomas" <ALThomas@.kc.rr.com> wrote in message
news:eETZ86g6FHA.1000@.tk2msftngp13.phx.gbl...
> At the time, this seemed clearer, but it appears you are speaking of
> something else. There is also the Setupsql9.chm file that is seperate
> from
> the BOL. You are right; it is unclear.
> Microsoft SQL Server September 2005 Community Technology Preview
> http://download.microsoft.com/downlo...ntat ion_cuy1
> 3.5.15 Corrections to the Names of Security Groups Created During Setup
> During setup, SQL Server 2005 adds the following security groups to
> Windows:
> SQLServer2005DTSUser$ComputerName
> SQLServer2005MSFTEUser$ComputerName$InstanceName
> SQLServer2005MSOLAPUser$ComputerName$InstanceName
> SQLServer2005MSSQLServerADHelperUser$ComputerName
> SQLServer2005MSSQLUser$ComputerName$InstanceName
> SQLServer2005NotificationServicesUser$ComputerName
> SQLServer2005ReportingServicesWebServiceUser$Compu terName$InstanceName
> SQLServer2005ReportServerUser$ComputerName$Instanc eName
> SQLServer2005SQLAgentUser$ComputerName$InstanceNam e
> SQLServer2005SQLBrowserUser$ComputerName
> These groups simplify granting permissions required to run SQL Server
> Windows services and other executables. They also help secure SQL Server
> files.
> In SQL Server Books Online, $ComputerName was omitted from the names. The
> computer name has since been added to the group names to uniquely identify
> each group. Unique group names are necessary if SQL Server 2005 is
> installed
> on domain controllers. For all references to security groups that start
> with
> "SQLServer2005," substitute the appropriate group name listed above.
> 3.5.17 Restrictions for Service Accounts on a Failover Cluster
> SQL Server service, SQL Server Agent service, Analysis Services service,
> and
> Full-Text Search service must run as domain accounts that are members of
> the
> built-in Administrators group on each node of the cluster.
>
> Sincerely,
>
> Anthony Thomas
> --
> "Andy Ball" <ng@.spamno77greenfell.com> wrote in message
> news:uEuMBdV6FHA.1000@.tk2msftngp13.phx.gbl...
> the
> the
> do
> server/instance
> task
> shows
> returned
> parsing
> command
> I
> services.
> proceed,
> -
> services.
> proceed,
> -
> services.
> proceed,
> the
> missing
> documentation
> me
>
|||Yea, I saw that and it didn't make sense. There is no such thing as "DOMAIN
local groups." There are DOMAIN Global groups, LOCAL groups, Cluster
Resource groups, and, apparently, SQL Server 2005 security groups.
However, there is a new requirement that not only does the Installation
Administrator need Local Administrators group membership but also the ACT AS
PART OF THE OPERATING SYSTEM User Security rights assignment for clustered
installations that probably caused the initial issue to begin with.
Sincerely,
Anthony Thomas
"Andy Ball" <ng@.spamno77greenfell.com> wrote in message
news:O$aRRzw6FHA.808@.TK2MSFTNGP09.phx.gbl...
> and the portion I presume is talking about the Local Groups that created
on
> the Server where SQL is installed. Simon's original post is about the
DOMAIN[vbcol=seagreen]
> local groups that are required for Clustering.
> cheers,
> Andy.
> "Anthony Thomas" <ALThomas@.kc.rr.com> wrote in message
> news:eETZ86g6FHA.1000@.tk2msftngp13.phx.gbl...
http://download.microsoft.com/downlo...ntat ion_cuy1[vbcol=seagreen]
The[vbcol=seagreen]
identify[vbcol=seagreen]
MSDN[vbcol=seagreen]
do[vbcol=seagreen]
I[vbcol=seagreen]
you[vbcol=seagreen]
the[vbcol=seagreen]
true[vbcol=seagreen]
true[vbcol=seagreen]
No[vbcol=seagreen]
nodes.[vbcol=seagreen]
-[vbcol=seagreen]
-[vbcol=seagreen]
let
>
|||Domain Local Groups were introduced in Windows 2000 Active Directory
cheers
Andy.
"Anthony Thomas" <ALThomas@.kc.rr.com> wrote in message
news:exXVCFx6FHA.3276@.TK2MSFTNGP10.phx.gbl...
> Yea, I saw that and it didn't make sense. There is no such thing as
> "DOMAIN
> local groups." There are DOMAIN Global groups, LOCAL groups, Cluster
> Resource groups, and, apparently, SQL Server 2005 security groups.
> However, there is a new requirement that not only does the Installation
> Administrator need Local Administrators group membership but also the ACT
> AS
> PART OF THE OPERATING SYSTEM User Security rights assignment for clustered
> installations that probably caused the initial issue to begin with.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Andy Ball" <ng@.spamno77greenfell.com> wrote in message
> news:O$aRRzw6FHA.808@.TK2MSFTNGP09.phx.gbl...
> on
> DOMAIN
> http://download.microsoft.com/downlo...ntat ion_cuy1
> The
> identify
> MSDN
> do
> I
> you
> the
> true
> true
> No
> nodes.
> -
> -
> let
>
Please note this cluster has a SQL 2000 (SP4) virtual server/instance already
installed. I would like to run them side by side.
installing using the setup wizard I get error about the schedule task
failing to start on the 2nd node. Looking through the log files the setup
program on the 2nd node has thrown an exception error, core.log shows this:
Complete: ParseBootstrapOptionsAction at: 2005/10/7 13:25:6, returned false
Error: Action "ParseBootstrapOptionsAction" failed during execution. Error
information reported during run:
Could not decrypt command line due to WinException.
Error Code: -2146893822
Windows Error Text: Bad Hash.
Source File Name: cryptohelper\cryptpassword.cpp
Compiler Timestamp: Mon Jul 18 01:10:20 2005
Function Name: sqls::CryptPassword::UnprotectString
Source Line Number: 311
Running: ValidateWinNTAction at: 2005/10/7 13:25:6
Complete: ValidateWinNTAction at: 2005/10/7 13:25:6, returned true
Running: ValidateMinOSAction at: 2005/10/7 13:25:6
Complete: ValidateMinOSAction at: 2005/10/7 13:25:6, returned true
Running: PerformSCCAction at: 2005/10/7 13:25:6
Complete: PerformSCCAction at: 2005/10/7 13:25:6, returned true
Running: ActivateLoggingAction at: 2005/10/7 13:25:6
Error: Action "ActivateLoggingAction" threw an exception during execution.
Error information reported during run:
00D7CFC8Unable to proceed with setup, there was a command line parsing
error. : -2146893822
Error Code: -2146893822
Windows Error Text: Bad Hash.
Source File Name: cryptohelper\cryptpassword.cpp
Compiler Timestamp: Mon Jul 18 01:10:20 2005
Function Name: sqls::CryptPassword::UnprotectString
Source Line Number: 311
Delay load of action "UploadDrWatsonLogAction" returned nothing. No action
will occur as a result.
Message pump returning: 2148073474
-- END OF OUTPUT --
I've trying to work around it I have tried installing from the command line.
This gets much further with setup starting correctly on both nodes. I get as
far as installing the actual SQL Server Service instance then I'm thrown an
error. Summary.log shows:
Machine : SERVERA
Product : SQL Server Database Services
Error : A domain group is missing for one or more services. To
install SQL Server 2005 as a failover cluster, domain groups must be
specified for all the clustered services being installed .To proceed, enter
the missing domain group information.
The domain group cannot be validated for the service SQL Server.
Machine : SERVERA
Product : SQL Server Database Services
Error : A domain group is missing for one or more services. To
install SQL Server 2005 as a failover cluster, domain groups must be
specified for all the clustered services being installed .To proceed, enter
the missing domain group information.
The domain group cannot be validated for the service SQL Server.
Machine : SERVERA
Product : Microsoft SQL Server 2005
Product Version : 9.00.1399.06
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0014_LON-IMS01A_SQL.log
Last Action : Validate_ServiceAccounts
Error String : A domain group is missing for one or more services. To
install SQL Server 2005 as a failover cluster, domain groups must be
specified for all the clustered services being installed .To proceed, enter
the missing domain group information.
The domain group cannot be validated for the service SQL Server.
Error Number : 28130
-- END OF OUTPUT
In the GUI you get asked for Domain Groups for each service, the
documentation for the command line installer doesn't tell me what the
parameters are for this. Do I need them, is the documentation missing
something? Also I'm not too sure what the ADMINPASSWORD= paramater is for -
I'm putting in my domain password currently - again teh documentation isn't
too hot for this.
I'm running out of ideas. If anyone has any suggestions please let me know!
Thanks
I figured out the problem to the command line - why the GUI crashed I do not
know.
BOL does not document any of these parameters for the command line which are
REQUIRED for a cluster install:
SQLBROWSERACCOUNT="DOMAIN\USER"
SQLBROWSERPASSWORD="PASSWORD"
SQLCLUSTERGROUP="DOMAIN\GROUP"
AGTCLUSTERGROUP="DOMAIN\GROUP"
FTSCLUSTERGROUP="DOMAIN\GROUP"
However if you look in the template.ini file on your install cd you will
find details of how and when to use them.
A very dissapointed customer.
"Simon" wrote:
> I'm having problems installing 2005 Ent on my Win 2003 SP1 2 node cluster.
> Please note this cluster has a SQL 2000 (SP4) virtual server/instance already
> installed. I would like to run them side by side.
> installing using the setup wizard I get error about the schedule task
> failing to start on the 2nd node. Looking through the log files the setup
> program on the 2nd node has thrown an exception error, core.log shows this:
> Complete: ParseBootstrapOptionsAction at: 2005/10/7 13:25:6, returned false
> Error: Action "ParseBootstrapOptionsAction" failed during execution. Error
> information reported during run:
> Could not decrypt command line due to WinException.
> Error Code: -2146893822
> Windows Error Text: Bad Hash.
> Source File Name: cryptohelper\cryptpassword.cpp
> Compiler Timestamp: Mon Jul 18 01:10:20 2005
> Function Name: sqls::CryptPassword::UnprotectString
> Source Line Number: 311
> Running: ValidateWinNTAction at: 2005/10/7 13:25:6
> Complete: ValidateWinNTAction at: 2005/10/7 13:25:6, returned true
> Running: ValidateMinOSAction at: 2005/10/7 13:25:6
> Complete: ValidateMinOSAction at: 2005/10/7 13:25:6, returned true
> Running: PerformSCCAction at: 2005/10/7 13:25:6
> Complete: PerformSCCAction at: 2005/10/7 13:25:6, returned true
> Running: ActivateLoggingAction at: 2005/10/7 13:25:6
> Error: Action "ActivateLoggingAction" threw an exception during execution.
> Error information reported during run:
> 00D7CFC8Unable to proceed with setup, there was a command line parsing
> error. : -2146893822
> Error Code: -2146893822
> Windows Error Text: Bad Hash.
> Source File Name: cryptohelper\cryptpassword.cpp
> Compiler Timestamp: Mon Jul 18 01:10:20 2005
> Function Name: sqls::CryptPassword::UnprotectString
> Source Line Number: 311
> Delay load of action "UploadDrWatsonLogAction" returned nothing. No action
> will occur as a result.
> Message pump returning: 2148073474
>
> -- END OF OUTPUT --
>
> I've trying to work around it I have tried installing from the command line.
> This gets much further with setup starting correctly on both nodes. I get as
> far as installing the actual SQL Server Service instance then I'm thrown an
> error. Summary.log shows:
>
> Machine : SERVERA
> Product : SQL Server Database Services
> Error : A domain group is missing for one or more services. To
> install SQL Server 2005 as a failover cluster, domain groups must be
> specified for all the clustered services being installed .To proceed, enter
> the missing domain group information.
> The domain group cannot be validated for the service SQL Server.
> ----
> Machine : SERVERA
> Product : SQL Server Database Services
> Error : A domain group is missing for one or more services. To
> install SQL Server 2005 as a failover cluster, domain groups must be
> specified for all the clustered services being installed .To proceed, enter
> the missing domain group information.
> The domain group cannot be validated for the service SQL Server.
> ----
> Machine : SERVERA
> Product : Microsoft SQL Server 2005
> Product Version : 9.00.1399.06
> Install : Failed
> Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0014_LON-IMS01A_SQL.log
> Last Action : Validate_ServiceAccounts
> Error String : A domain group is missing for one or more services. To
> install SQL Server 2005 as a failover cluster, domain groups must be
> specified for all the clustered services being installed .To proceed, enter
> the missing domain group information.
> The domain group cannot be validated for the service SQL Server.
> Error Number : 28130
>
> -- END OF OUTPUT
>
> In the GUI you get asked for Domain Groups for each service, the
> documentation for the command line installer doesn't tell me what the
> parameters are for this. Do I need them, is the documentation missing
> something? Also I'm not too sure what the ADMINPASSWORD= paramater is for -
> I'm putting in my domain password currently - again teh documentation isn't
> too hot for this.
> I'm running out of ideas. If anyone has any suggestions please let me know!
> Thanks
>
|||Simon,
yep I noticed that too. Just an omission in BOL. I sent feedback via the BOL
entry for installing a Cluster from template/unattend, suggest you do the
same.
Andy.
"Simon" <Simon@.discussions.microsoft.com> wrote in message
news:ECC70F54-2E3D-43BE-AE8B-5B91EFC74E60@.microsoft.com...[vbcol=seagreen]
>I figured out the problem to the command line - why the GUI crashed I do
>not
> know.
> BOL does not document any of these parameters for the command line which
> are
> REQUIRED for a cluster install:
> SQLBROWSERACCOUNT="DOMAIN\USER"
> SQLBROWSERPASSWORD="PASSWORD"
> SQLCLUSTERGROUP="DOMAIN\GROUP"
> AGTCLUSTERGROUP="DOMAIN\GROUP"
> FTSCLUSTERGROUP="DOMAIN\GROUP"
> However if you look in the template.ini file on your install cd you will
> find details of how and when to use them.
> A very dissapointed customer.
>
>
> "Simon" wrote:
|||That information is in the Readme notes as well as the Readme errata posted
online.
ALWAYS READ THE README.
Anthony Thomas
"Andy Ball" <ng@.spamno77greenfell.com> wrote in message
news:u%23k3gf05FHA.3976@.TK2MSFTNGP15.phx.gbl...
> Simon,
> yep I noticed that too. Just an omission in BOL. I sent feedback via the
BOL[vbcol=seagreen]
> entry for installing a Cluster from template/unattend, suggest you do the
> same.
> Andy.
> "Simon" <Simon@.discussions.microsoft.com> wrote in message
> news:ECC70F54-2E3D-43BE-AE8B-5B91EFC74E60@.microsoft.com...
setup[vbcol=seagreen]
get[vbcol=seagreen]
thrown[vbcol=seagreen]
To[vbcol=seagreen]
--[vbcol=seagreen]
To[vbcol=seagreen]
--[vbcol=seagreen]
To
>
|||must be going blind - i'm looking @. ReadmeSQL2005.htm from the Dev \ MSDN
edition and Q907284 I can't see it
Andy.
"Anthony Thomas" <ALThomas@.kc.rr.com> wrote in message
news:OaT56MI6FHA.1184@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> That information is in the Readme notes as well as the Readme errata
> posted
> online.
> ALWAYS READ THE README.
>
> Anthony Thomas
>
> --
> "Andy Ball" <ng@.spamno77greenfell.com> wrote in message
> news:u%23k3gf05FHA.3976@.TK2MSFTNGP15.phx.gbl...
> BOL
> setup
> get
> thrown
> To
> --
> To
> --
> To
>
|||At the time, this seemed clearer, but it appears you are speaking of
something else. There is also the Setupsql9.chm file that is seperate from
the BOL. You are right; it is unclear.
Microsoft SQL Server September 2005 Community Technology Preview
http://download.microsoft.com/downlo...ntat ion_cuy1
3.5.15 Corrections to the Names of Security Groups Created During Setup
During setup, SQL Server 2005 adds the following security groups to Windows:
SQLServer2005DTSUser$ComputerName
SQLServer2005MSFTEUser$ComputerName$InstanceName
SQLServer2005MSOLAPUser$ComputerName$InstanceName
SQLServer2005MSSQLServerADHelperUser$ComputerName
SQLServer2005MSSQLUser$ComputerName$InstanceName
SQLServer2005NotificationServicesUser$ComputerName
SQLServer2005ReportingServicesWebServiceUser$Compu terName$InstanceName
SQLServer2005ReportServerUser$ComputerName$Instanc eName
SQLServer2005SQLAgentUser$ComputerName$InstanceNam e
SQLServer2005SQLBrowserUser$ComputerName
These groups simplify granting permissions required to run SQL Server
Windows services and other executables. They also help secure SQL Server
files.
In SQL Server Books Online, $ComputerName was omitted from the names. The
computer name has since been added to the group names to uniquely identify
each group. Unique group names are necessary if SQL Server 2005 is installed
on domain controllers. For all references to security groups that start with
"SQLServer2005," substitute the appropriate group name listed above.
3.5.17 Restrictions for Service Accounts on a Failover Cluster
SQL Server service, SQL Server Agent service, Analysis Services service, and
Full-Text Search service must run as domain accounts that are members of the
built-in Administrators group on each node of the cluster.
Sincerely,
Anthony Thomas
"Andy Ball" <ng@.spamno77greenfell.com> wrote in message
news:uEuMBdV6FHA.1000@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> must be going blind - i'm looking @. ReadmeSQL2005.htm from the Dev \ MSDN
> edition and Q907284 I can't see it
> Andy.
> "Anthony Thomas" <ALThomas@.kc.rr.com> wrote in message
> news:OaT56MI6FHA.1184@.TK2MSFTNGP12.phx.gbl...
>
the[vbcol=seagreen]
the[vbcol=seagreen]
do[vbcol=seagreen]
server/instance[vbcol=seagreen]
task[vbcol=seagreen]
shows[vbcol=seagreen]
returned[vbcol=seagreen]
parsing[vbcol=seagreen]
command[vbcol=seagreen]
I[vbcol=seagreen]
services.[vbcol=seagreen]
proceed,[vbcol=seagreen]
-[vbcol=seagreen]
services.[vbcol=seagreen]
proceed,[vbcol=seagreen]
-[vbcol=seagreen]
services.[vbcol=seagreen]
proceed,[vbcol=seagreen]
the[vbcol=seagreen]
missing[vbcol=seagreen]
documentation[vbcol=seagreen]
me
>
|||From the Setupsql9.chm, regarding your original issue:
How to: Install SQL Server 2005 from the Command Prompt
For failover cluster installations, you must be a local administrator with
permissions to logon as a service, and to act as part of the operating
system on all nodes of the virtual server.
start /wait setup.exe /qn VS=<VSName> INSTALLVS=Analysis_Server
INSTANCENAME=<InstanceName> ADDLOCAL=Analysis_Server ADDNODE=n
GROUP=<NotSQLDiskGroup> IP=<IP,Networkname> ADMINPASSWORD=<StrongPassword>
SAPWD=<StrongPassword> INSTALLSQLDIR=<InstallationPath>
INSTALLSQLDATADIR=<ShareDrivePath> ASACCOUNT=<domain\user>
ASPASSWORD=<DomainUserPassword> SQLBROWSERACCOUNT=<domain\user>
SQLBROWSERPASSWORD=<DomainUserPassword> SQLREPORTING=1
Start /wait <DVD Drive>\setup.exe /qn VS=<VSName> INSTALLVS=SQL_Engine
INSTANCENAME=<InstanceName> ADDLOCAL=SQL_Engine,Client_Components
ADDNODE=<NodeName1,NodeName2> GROUP=<Diskgroup> IP=<IP,Networkname>
ADMINPASSWORD=<StrongPassword> SAPWD=<StrongPassord>
INSTALLSQLDIR=<InstallationPath> INSTALLSQLDATADIR=<ShareDrivePath>
SQLACCOUNT=<domain\user> SQLPASSWORD=<DomainUserPassword>
AGTACCOUNT=<domain\user> AGTPASSWORD=<DomainUserPassword>
The same holds true for the other components.
Sincerely,
Anthony Thomas
"Anthony Thomas" <ALThomas@.kc.rr.com> wrote in message
news:eETZ86g6FHA.1000@.tk2msftngp13.phx.gbl...
> At the time, this seemed clearer, but it appears you are speaking of
> something else. There is also the Setupsql9.chm file that is seperate
from
> the BOL. You are right; it is unclear.
> Microsoft SQL Server September 2005 Community Technology Preview
>
http://download.microsoft.com/downlo...ntat ion_cuy1
> 3.5.15 Corrections to the Names of Security Groups Created During Setup
> During setup, SQL Server 2005 adds the following security groups to
Windows:
> SQLServer2005DTSUser$ComputerName
> SQLServer2005MSFTEUser$ComputerName$InstanceName
> SQLServer2005MSOLAPUser$ComputerName$InstanceName
> SQLServer2005MSSQLServerADHelperUser$ComputerName
> SQLServer2005MSSQLUser$ComputerName$InstanceName
> SQLServer2005NotificationServicesUser$ComputerName
> SQLServer2005ReportingServicesWebServiceUser$Compu terName$InstanceName
> SQLServer2005ReportServerUser$ComputerName$Instanc eName
> SQLServer2005SQLAgentUser$ComputerName$InstanceNam e
> SQLServer2005SQLBrowserUser$ComputerName
> These groups simplify granting permissions required to run SQL Server
> Windows services and other executables. They also help secure SQL Server
> files.
> In SQL Server Books Online, $ComputerName was omitted from the names. The
> computer name has since been added to the group names to uniquely identify
> each group. Unique group names are necessary if SQL Server 2005 is
installed
> on domain controllers. For all references to security groups that start
with
> "SQLServer2005," substitute the appropriate group name listed above.
> 3.5.17 Restrictions for Service Accounts on a Failover Cluster
> SQL Server service, SQL Server Agent service, Analysis Services service,
and
> Full-Text Search service must run as domain accounts that are members of
the[vbcol=seagreen]
> built-in Administrators group on each node of the cluster.
>
> Sincerely,
>
> Anthony Thomas
> --
> "Andy Ball" <ng@.spamno77greenfell.com> wrote in message
> news:uEuMBdV6FHA.1000@.tk2msftngp13.phx.gbl...
MSDN[vbcol=seagreen]
> the
> the
I[vbcol=seagreen]
> do
> server/instance
> task
the[vbcol=seagreen]
> shows
> returned
execution.[vbcol=seagreen]
> parsing
No[vbcol=seagreen]
> command
nodes.[vbcol=seagreen]
> I
> services.
be[vbcol=seagreen]
> proceed,
> -
> services.
be[vbcol=seagreen]
> proceed,
> -
> services.
be[vbcol=seagreen]
> proceed,
> the
> missing
paramater
> documentation
> me
>
|||and the portion I presume is talking about the Local Groups that created on
the Server where SQL is installed. Simon's original post is about the DOMAIN
local groups that are required for Clustering.
cheers,
Andy.
"Anthony Thomas" <ALThomas@.kc.rr.com> wrote in message
news:eETZ86g6FHA.1000@.tk2msftngp13.phx.gbl...
> At the time, this seemed clearer, but it appears you are speaking of
> something else. There is also the Setupsql9.chm file that is seperate
> from
> the BOL. You are right; it is unclear.
> Microsoft SQL Server September 2005 Community Technology Preview
> http://download.microsoft.com/downlo...ntat ion_cuy1
> 3.5.15 Corrections to the Names of Security Groups Created During Setup
> During setup, SQL Server 2005 adds the following security groups to
> Windows:
> SQLServer2005DTSUser$ComputerName
> SQLServer2005MSFTEUser$ComputerName$InstanceName
> SQLServer2005MSOLAPUser$ComputerName$InstanceName
> SQLServer2005MSSQLServerADHelperUser$ComputerName
> SQLServer2005MSSQLUser$ComputerName$InstanceName
> SQLServer2005NotificationServicesUser$ComputerName
> SQLServer2005ReportingServicesWebServiceUser$Compu terName$InstanceName
> SQLServer2005ReportServerUser$ComputerName$Instanc eName
> SQLServer2005SQLAgentUser$ComputerName$InstanceNam e
> SQLServer2005SQLBrowserUser$ComputerName
> These groups simplify granting permissions required to run SQL Server
> Windows services and other executables. They also help secure SQL Server
> files.
> In SQL Server Books Online, $ComputerName was omitted from the names. The
> computer name has since been added to the group names to uniquely identify
> each group. Unique group names are necessary if SQL Server 2005 is
> installed
> on domain controllers. For all references to security groups that start
> with
> "SQLServer2005," substitute the appropriate group name listed above.
> 3.5.17 Restrictions for Service Accounts on a Failover Cluster
> SQL Server service, SQL Server Agent service, Analysis Services service,
> and
> Full-Text Search service must run as domain accounts that are members of
> the
> built-in Administrators group on each node of the cluster.
>
> Sincerely,
>
> Anthony Thomas
> --
> "Andy Ball" <ng@.spamno77greenfell.com> wrote in message
> news:uEuMBdV6FHA.1000@.tk2msftngp13.phx.gbl...
> the
> the
> do
> server/instance
> task
> shows
> returned
> parsing
> command
> I
> services.
> proceed,
> -
> services.
> proceed,
> -
> services.
> proceed,
> the
> missing
> documentation
> me
>
|||Yea, I saw that and it didn't make sense. There is no such thing as "DOMAIN
local groups." There are DOMAIN Global groups, LOCAL groups, Cluster
Resource groups, and, apparently, SQL Server 2005 security groups.
However, there is a new requirement that not only does the Installation
Administrator need Local Administrators group membership but also the ACT AS
PART OF THE OPERATING SYSTEM User Security rights assignment for clustered
installations that probably caused the initial issue to begin with.
Sincerely,
Anthony Thomas
"Andy Ball" <ng@.spamno77greenfell.com> wrote in message
news:O$aRRzw6FHA.808@.TK2MSFTNGP09.phx.gbl...
> and the portion I presume is talking about the Local Groups that created
on
> the Server where SQL is installed. Simon's original post is about the
DOMAIN[vbcol=seagreen]
> local groups that are required for Clustering.
> cheers,
> Andy.
> "Anthony Thomas" <ALThomas@.kc.rr.com> wrote in message
> news:eETZ86g6FHA.1000@.tk2msftngp13.phx.gbl...
http://download.microsoft.com/downlo...ntat ion_cuy1[vbcol=seagreen]
The[vbcol=seagreen]
identify[vbcol=seagreen]
MSDN[vbcol=seagreen]
do[vbcol=seagreen]
I[vbcol=seagreen]
you[vbcol=seagreen]
the[vbcol=seagreen]
true[vbcol=seagreen]
true[vbcol=seagreen]
No[vbcol=seagreen]
nodes.[vbcol=seagreen]
-[vbcol=seagreen]
-[vbcol=seagreen]
let
>
|||Domain Local Groups were introduced in Windows 2000 Active Directory
cheers
Andy.
"Anthony Thomas" <ALThomas@.kc.rr.com> wrote in message
news:exXVCFx6FHA.3276@.TK2MSFTNGP10.phx.gbl...
> Yea, I saw that and it didn't make sense. There is no such thing as
> "DOMAIN
> local groups." There are DOMAIN Global groups, LOCAL groups, Cluster
> Resource groups, and, apparently, SQL Server 2005 security groups.
> However, there is a new requirement that not only does the Installation
> Administrator need Local Administrators group membership but also the ACT
> AS
> PART OF THE OPERATING SYSTEM User Security rights assignment for clustered
> installations that probably caused the initial issue to begin with.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Andy Ball" <ng@.spamno77greenfell.com> wrote in message
> news:O$aRRzw6FHA.808@.TK2MSFTNGP09.phx.gbl...
> on
> DOMAIN
> http://download.microsoft.com/downlo...ntat ion_cuy1
> The
> identify
> MSDN
> do
> I
> you
> the
> true
> true
> No
> nodes.
> -
> -
> let
>
2005 beta Backup problems
Hi there,
I've created a maintenance plan in SQL2005 bet 2 (not default instance)
scheduled to run everyday but it never runs, I've all the services running.
When I choose to execute in the moment it says it had success after 5 seconds
but nothing happens really.
Is this a limitation of the beta release? Or am I doing something wrong?
I've another instance instaled in the same server (but with sql2000
version-default instance) and the maintenance plans work fine.
thanks in advance.
Nelson
Please re-post this on the beta newsgroups.
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Nelson Andr" <NelsonAndr@.discussions.microsoft.com> wrote in message
news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
> Hi there,
> I've created a maintenance plan in SQL2005 bet 2 (not default instance)
> scheduled to run everyday but it never runs, I've all the services
> running.
> When I choose to execute in the moment it says it had success after 5
> seconds
> but nothing happens really.
> Is this a limitation of the beta release? Or am I doing something wrong?
> I've another instance instaled in the same server (but with sql2000
> version-default instance) and the maintenance plans work fine.
> thanks in advance.
> Nelson
>
|||Where can I find it? I've searched the whole microsoft site and couldn't find
any reference to a sql2005 beta newsgroup
"Wayne Snyder" wrote:
> Please re-post this on the beta newsgroups.
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "Nelson André" <NelsonAndr@.discussions.microsoft.com> wrote in message
> news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
>
>
|||http://communities.microsoft.com/new...=sqlserver2005
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Nelson André" wrote:
[vbcol=seagreen]
> Where can I find it? I've searched the whole microsoft site and couldn't find
> any reference to a sql2005 beta newsgroup
> "Wayne Snyder" wrote:
I've created a maintenance plan in SQL2005 bet 2 (not default instance)
scheduled to run everyday but it never runs, I've all the services running.
When I choose to execute in the moment it says it had success after 5 seconds
but nothing happens really.
Is this a limitation of the beta release? Or am I doing something wrong?
I've another instance instaled in the same server (but with sql2000
version-default instance) and the maintenance plans work fine.
thanks in advance.
Nelson
Please re-post this on the beta newsgroups.
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Nelson Andr" <NelsonAndr@.discussions.microsoft.com> wrote in message
news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
> Hi there,
> I've created a maintenance plan in SQL2005 bet 2 (not default instance)
> scheduled to run everyday but it never runs, I've all the services
> running.
> When I choose to execute in the moment it says it had success after 5
> seconds
> but nothing happens really.
> Is this a limitation of the beta release? Or am I doing something wrong?
> I've another instance instaled in the same server (but with sql2000
> version-default instance) and the maintenance plans work fine.
> thanks in advance.
> Nelson
>
|||Where can I find it? I've searched the whole microsoft site and couldn't find
any reference to a sql2005 beta newsgroup
"Wayne Snyder" wrote:
> Please re-post this on the beta newsgroups.
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "Nelson André" <NelsonAndr@.discussions.microsoft.com> wrote in message
> news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
>
>
|||http://communities.microsoft.com/new...=sqlserver2005
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Nelson André" wrote:
[vbcol=seagreen]
> Where can I find it? I've searched the whole microsoft site and couldn't find
> any reference to a sql2005 beta newsgroup
> "Wayne Snyder" wrote:
2005 beta Backup problems
Hi there,
I've created a maintenance plan in SQL2005 bet 2 (not default instance)
scheduled to run everyday but it never runs, I've all the services running.
When I choose to execute in the moment it says it had success after 5 seconds
but nothing happens really.
Is this a limitation of the beta release? Or am I doing something wrong?
I've another instance instaled in the same server (but with sql2000
version-default instance) and the maintenance plans work fine.
thanks in advance.
NelsonPlease re-post this on the beta newsgroups.
--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Nelson André" <NelsonAndr@.discussions.microsoft.com> wrote in message
news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
> Hi there,
> I've created a maintenance plan in SQL2005 bet 2 (not default instance)
> scheduled to run everyday but it never runs, I've all the services
> running.
> When I choose to execute in the moment it says it had success after 5
> seconds
> but nothing happens really.
> Is this a limitation of the beta release? Or am I doing something wrong?
> I've another instance instaled in the same server (but with sql2000
> version-default instance) and the maintenance plans work fine.
> thanks in advance.
> Nelson
>|||Where can I find it? I've searched the whole microsoft site and couldn't find
any reference to a sql2005 beta newsgroup
"Wayne Snyder" wrote:
> Please re-post this on the beta newsgroups.
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "Nelson André" <NelsonAndr@.discussions.microsoft.com> wrote in message
> news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
> > Hi there,
> > I've created a maintenance plan in SQL2005 bet 2 (not default instance)
> > scheduled to run everyday but it never runs, I've all the services
> > running.
> > When I choose to execute in the moment it says it had success after 5
> > seconds
> > but nothing happens really.
> > Is this a limitation of the beta release? Or am I doing something wrong?
> > I've another instance instaled in the same server (but with sql2000
> > version-default instance) and the maintenance plans work fine.
> > thanks in advance.
> > Nelson
> >
>
>|||http://communities.microsoft.com/newsgroups/default.asp?icp=sqlserver2005
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Nelson André" wrote:
> Where can I find it? I've searched the whole microsoft site and couldn't find
> any reference to a sql2005 beta newsgroup
> "Wayne Snyder" wrote:
> > Please re-post this on the beta newsgroups.
> >
> > --
> > Wayne Snyder MCDBA, SQL Server MVP
> > Mariner, Charlotte, NC
> > (Please respond only to the newsgroup.)
> >
> > I support the Professional Association for SQL Server ( PASS) and it's
> > community of SQL Professionals.
> > "Nelson André" <NelsonAndr@.discussions.microsoft.com> wrote in message
> > news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
> > > Hi there,
> > > I've created a maintenance plan in SQL2005 bet 2 (not default instance)
> > > scheduled to run everyday but it never runs, I've all the services
> > > running.
> > > When I choose to execute in the moment it says it had success after 5
> > > seconds
> > > but nothing happens really.
> > > Is this a limitation of the beta release? Or am I doing something wrong?
> > > I've another instance instaled in the same server (but with sql2000
> > > version-default instance) and the maintenance plans work fine.
> > > thanks in advance.
> > > Nelson
> > >
> >
> >
> >
I've created a maintenance plan in SQL2005 bet 2 (not default instance)
scheduled to run everyday but it never runs, I've all the services running.
When I choose to execute in the moment it says it had success after 5 seconds
but nothing happens really.
Is this a limitation of the beta release? Or am I doing something wrong?
I've another instance instaled in the same server (but with sql2000
version-default instance) and the maintenance plans work fine.
thanks in advance.
NelsonPlease re-post this on the beta newsgroups.
--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Nelson André" <NelsonAndr@.discussions.microsoft.com> wrote in message
news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
> Hi there,
> I've created a maintenance plan in SQL2005 bet 2 (not default instance)
> scheduled to run everyday but it never runs, I've all the services
> running.
> When I choose to execute in the moment it says it had success after 5
> seconds
> but nothing happens really.
> Is this a limitation of the beta release? Or am I doing something wrong?
> I've another instance instaled in the same server (but with sql2000
> version-default instance) and the maintenance plans work fine.
> thanks in advance.
> Nelson
>|||Where can I find it? I've searched the whole microsoft site and couldn't find
any reference to a sql2005 beta newsgroup
"Wayne Snyder" wrote:
> Please re-post this on the beta newsgroups.
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "Nelson André" <NelsonAndr@.discussions.microsoft.com> wrote in message
> news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
> > Hi there,
> > I've created a maintenance plan in SQL2005 bet 2 (not default instance)
> > scheduled to run everyday but it never runs, I've all the services
> > running.
> > When I choose to execute in the moment it says it had success after 5
> > seconds
> > but nothing happens really.
> > Is this a limitation of the beta release? Or am I doing something wrong?
> > I've another instance instaled in the same server (but with sql2000
> > version-default instance) and the maintenance plans work fine.
> > thanks in advance.
> > Nelson
> >
>
>|||http://communities.microsoft.com/newsgroups/default.asp?icp=sqlserver2005
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Nelson André" wrote:
> Where can I find it? I've searched the whole microsoft site and couldn't find
> any reference to a sql2005 beta newsgroup
> "Wayne Snyder" wrote:
> > Please re-post this on the beta newsgroups.
> >
> > --
> > Wayne Snyder MCDBA, SQL Server MVP
> > Mariner, Charlotte, NC
> > (Please respond only to the newsgroup.)
> >
> > I support the Professional Association for SQL Server ( PASS) and it's
> > community of SQL Professionals.
> > "Nelson André" <NelsonAndr@.discussions.microsoft.com> wrote in message
> > news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
> > > Hi there,
> > > I've created a maintenance plan in SQL2005 bet 2 (not default instance)
> > > scheduled to run everyday but it never runs, I've all the services
> > > running.
> > > When I choose to execute in the moment it says it had success after 5
> > > seconds
> > > but nothing happens really.
> > > Is this a limitation of the beta release? Or am I doing something wrong?
> > > I've another instance instaled in the same server (but with sql2000
> > > version-default instance) and the maintenance plans work fine.
> > > thanks in advance.
> > > Nelson
> > >
> >
> >
> >
2005 beta Backup problems
Hi there,
I've created a maintenance plan in SQL2005 bet 2 (not default instance)
scheduled to run everyday but it never runs, I've all the services running.
When I choose to execute in the moment it says it had success after 5 second
s
but nothing happens really.
Is this a limitation of the beta release? Or am I doing something wrong?
I've another instance instaled in the same server (but with sql2000
version-default instance) and the maintenance plans work fine.
thanks in advance.
NelsonPlease re-post this on the beta newsgroups.
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Nelson Andr" <NelsonAndr@.discussions.microsoft.com> wrote in message
news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
> Hi there,
> I've created a maintenance plan in SQL2005 bet 2 (not default instance)
> scheduled to run everyday but it never runs, I've all the services
> running.
> When I choose to execute in the moment it says it had success after 5
> seconds
> but nothing happens really.
> Is this a limitation of the beta release? Or am I doing something wrong?
> I've another instance instaled in the same server (but with sql2000
> version-default instance) and the maintenance plans work fine.
> thanks in advance.
> Nelson
>|||Where can I find it? I've searched the whole microsoft site and couldn't fin
d
any reference to a sql2005 beta newsgroup
"Wayne Snyder" wrote:
> Please re-post this on the beta newsgroups.
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "Nelson André" <NelsonAndr@.discussions.microsoft.com> wrote in message
> news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
>
>|||http://communities.microsoft.com/ne...p=sqlserver2005
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Nelson André" wrote:
[vbcol=seagreen]
> Where can I find it? I've searched the whole microsoft site and couldn't f
ind
> any reference to a sql2005 beta newsgroup
> "Wayne Snyder" wrote:
>
I've created a maintenance plan in SQL2005 bet 2 (not default instance)
scheduled to run everyday but it never runs, I've all the services running.
When I choose to execute in the moment it says it had success after 5 second
s
but nothing happens really.
Is this a limitation of the beta release? Or am I doing something wrong?
I've another instance instaled in the same server (but with sql2000
version-default instance) and the maintenance plans work fine.
thanks in advance.
NelsonPlease re-post this on the beta newsgroups.
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Nelson Andr" <NelsonAndr@.discussions.microsoft.com> wrote in message
news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
> Hi there,
> I've created a maintenance plan in SQL2005 bet 2 (not default instance)
> scheduled to run everyday but it never runs, I've all the services
> running.
> When I choose to execute in the moment it says it had success after 5
> seconds
> but nothing happens really.
> Is this a limitation of the beta release? Or am I doing something wrong?
> I've another instance instaled in the same server (but with sql2000
> version-default instance) and the maintenance plans work fine.
> thanks in advance.
> Nelson
>|||Where can I find it? I've searched the whole microsoft site and couldn't fin
d
any reference to a sql2005 beta newsgroup
"Wayne Snyder" wrote:
> Please re-post this on the beta newsgroups.
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "Nelson André" <NelsonAndr@.discussions.microsoft.com> wrote in message
> news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
>
>|||http://communities.microsoft.com/ne...p=sqlserver2005
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Nelson André" wrote:
[vbcol=seagreen]
> Where can I find it? I've searched the whole microsoft site and couldn't f
ind
> any reference to a sql2005 beta newsgroup
> "Wayne Snyder" wrote:
>
Subscribe to:
Posts (Atom)