Can''t configure Features on Clustered Server

Hi, I am a relative newbie to SQL Server and I need some help trying to configure an existing clustered server. Using surface area configuration with "local" checked, I can see all of the components as pictured here. However, checking one (i.e. DatabaseMail) results in a pop-up message with "You cannot configure surface area of clustered services by connecting to a computer name. Connect to the virtual server to configure clustered services".

Ok. Fair enough. I then go back, check "remote" and enter the name of the cluster. After connecting, it only shows me a partial list of services as pictured here.

I first encounterd this while trying to enable Databasemail. However, I need to get an understanding of what I need to do be able to configure services or features on a clustered server using SAC.

Thanks for any help.

Just wondering if anyone else has had a similar problem and how they solved it.

I've inherited this problem and still have not found a resolution. Any response would be appreciated.

Can''t configure Features on Clustered Server

Hi, I am a relative newbie to SQL Server and I need some help trying to configure an existing clustered server. Using surface area configuration with "local" checked, I can see all of the components as pictured here. However, checking one (i.e. DatabaseMail) results in a pop-up message with "You cannot configure surface area of clustered services by connecting to a computer name. Connect to the virtual server to configure clustered services".

Ok. Fair enough. I then go back, check "remote" and enter the name of the cluster. After connecting, it only shows me a partial list of services as pictured here.

I first encounterd this while trying to enable Databasemail. However, I need to get an understanding of what I need to do be able to configure services or features on a clustered server using SAC.

Thanks for any help.

Just wondering if anyone else has had a similar problem and how they solved it.

I've inherited this problem and still have not found a resolution. Any response would be appreciated.

sql

Can't check "Check existing data on creation" in relationship

Hi
When I added relationship to table, checked "Check existing data on
creation" and clicked "Save" in Enterprise Management tool, it has no error.
However, when I check tables again, the "Check existing data on creation"
option was unchecked.
Help me!It's the expected behaviour: the first time you create the
relationship, the existing data is verified (if "Check existing data on
creation" is checked) and subsequently all the new data is verified (if
"Enforce relationship for INSERTs and UPDATEs" is checked).
If you modify something in the relationship (for example: the
relationship's name or the cascade updates/deletes checkboxes), the
existing data does not need be verified again (that's why this checkbox
is unchecked when you look at it later).
Only if you modify the relationship in more semnificative ways (for
example: different columns), you should make sure that you click on
"Check existing data on creation" so the existing data will be verified
according to the new relationship.
Razvan

Cant add fields to table in EM - Odd SP3a prob?

Ok, I think this is a SP3a issue but I wanted to know if anyone else had this same problem.

I am trying to add fields to an existing table but everytime I do, I get a message saying:

'Races' table
- Unable to create index 'IX_Races2'.
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid cursor state

I have narrowed it down to this. I can add the field if I add it to the bottom of the field list AND make it allow NULL. BUT...if I try to move the column up to another position (no, I don't need it in that position I know), it throws the error.

Also, if I add the field to the bottom of the field list, then try take off the NULL and fill in a default value, it still throws me this error. Someone tell me that this is just a SP3a issue. I have done this kind of thing before and never ran across this problem before.

Thanks,
GregHmm...ok. I have really narrowed it down now. The version that I am running on my server is 8.00.859. The version I have on my development machine is 8.00.760.

I detached the db from my server, attached it on my box, tried the same thing as above in my first post, and I was able to do it without a problem.

Anyone else experience this?

Greg

Cannot update ID because of no existing relationship

I have one table Phone and a table SmsMessage that are linked by the Cellnumber. Cellnumber is the primary key in Phone.

For some reason in the table Phone the Cellnumbers are stored with extra spaces like: '+27000000000 ', but in the SmsMessage table the same value is stored as '+27000000000'. However when I want perform an update to trim the Cellnumbers, I get the message 'Cannot modify values Cellnumber in Phone because there are dependent values in SmsMessage.

The fact is that there are no dependent values, but for MSSQL '+27000000000' and '+27000000000 ' is the same??! Note that the function Len(Cellnumber) gives me the length of the string WITHOUT the spaces as well.

Even if I remove all relationships from Phone, I still get the same error. Are there more places in MSSQL where relationships are stored besides the Diagrams?

Or is there a command that tells MSSQL to ignore all relationships for the next query?

Any ideas?I suspect that the data is stored in the column without the trailing spaces, although it may be presented with spaces added. This is common when retrieving data in columnar form. To test this, retrieve an expression rather than the raw column to see what you actually get, something like:SELECT myColumn, '[' + myColumn + ']'
FROM myTableThe real relationship information is stored in system tables in the form of constraints. The graphic representation is easier to understand, but the constraints are the "final answer" in terms of the relationships that MS-SQL enforces.

-PatP

cannot set name conflicts

For a snapshot replication.
I set the Name conflicts from the defualt-DROP the existing tables and
re-create it
to Delete All data in the existing table.
and set check in Include declared refertial integrity in Copy objects to
destination secton.
After I close these perperties window and reopen the publiction property
window to check the property on snapshop tab on article properties. I found
both the properties goes back to default values again
I am unable to repro your problem. Is this on SQL 2000 or SQL 7? Also which
sp?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Chen" <mxchen100@.hotmail.com> wrote in message
news:%231XSwgo2FHA.1572@.TK2MSFTNGP10.phx.gbl...
> For a snapshot replication.
> I set the Name conflicts from the defualt-DROP the existing tables and
> re-create it
> to Delete All data in the existing table.
> and set check in Include declared refertial integrity in Copy objects to
> destination secton.
> After I close these perperties window and reopen the publiction property
> window to check the property on snapshop tab on article properties. I
found
> both the properties goes back to default values again
>
>
|||on SQL 2000
Table
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%236uJRJu2FHA.476@.TK2MSFTNGP15.phx.gbl...
> I am unable to repro your problem. Is this on SQL 2000 or SQL 7? Also
which[vbcol=seagreen]
> sp?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Chen" <mxchen100@.hotmail.com> wrote in message
> news:%231XSwgo2FHA.1572@.TK2MSFTNGP10.phx.gbl...
property
> found
>
>
|||which sp? can you do a select @.@.version from QA?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Chen" <mxchen100@.hotmail.com> wrote in message
news:uUXNF7w2FHA.2292@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> on SQL 2000
> Table
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:%236uJRJu2FHA.476@.TK2MSFTNGP15.phx.gbl...
> which
to
> property
>
>

cannot see SQL Jobs on remote server

Hi,
I'm having troubles brining up details of existing SQL Jobs from remote
server. When I double-click existing job, it brings up "New Job" dialog box
instead of job details.
I needed to see and modify steps of a job on my collegue's machine. I can
connect to her SQL Server 2005 all right. But when I find the job I need,
right click it and select "Properties", I get "New Job" dialog box with all
tabs empty. What's interesting is I can still use "Script job as" menu item.
Another thing is that I see error messages like this in my error log:
DCOM was unable to communicate with the computer AAA using any of the
configured protocols.
I looked up this message and verified that I don't have UDP or IPX enabled,
only Connection-oriented TCP/IP and Connection-oriented SPX.
My other collegue can see the jobs fine, so I suppose the configuration
issue is with my machine. We all have WinXP Proferssional SP2 and both SQL
Server 2000 and 2005 on our machines. 2005's version is
Microsoft SQL Server 2005 - 9.00.2047.00 (Intel X86) Apr 14 2006 01:12:25
Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Windows
NT 5.1 (Build 2600: Service Pack 2)
I'd really appreciate if anyone has ideas on that.
thanks,
LucyI think the two errors are separate issues. I've seen the
issue with viewing jobs come up a few times. I suspect that
it's caused by problems with the smo dll - did you install
visual studio service packs to your PC? Try applying SQL
Server 2005 SP2 on your PC. That worked for me a couple of
times that I've run into this.
-Sue
On Fri, 30 Mar 2007 15:06:01 -0700, Lucy
<Lucy@.discussions.microsoft.com> wrote:

>Hi,
>I'm having troubles brining up details of existing SQL Jobs from remote
>server. When I double-click existing job, it brings up "New Job" dialog box
>instead of job details.
>I needed to see and modify steps of a job on my collegue's machine. I can
>connect to her SQL Server 2005 all right. But when I find the job I need,
>right click it and select "Properties", I get "New Job" dialog box with all
>tabs empty. What's interesting is I can still use "Script job as" menu item
.
>Another thing is that I see error messages like this in my error log:
>DCOM was unable to communicate with the computer AAA using any of the
>configured protocols.
>I looked up this message and verified that I don't have UDP or IPX enabled,
>only Connection-oriented TCP/IP and Connection-oriented SPX.
>My other collegue can see the jobs fine, so I suppose the configuration
>issue is with my machine. We all have WinXP Proferssional SP2 and both SQL
>Server 2000 and 2005 on our machines. 2005's version is
>Microsoft SQL Server 2005 - 9.00.2047.00 (Intel X86) Apr 14 2006 01:12:25
> Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Window
s
>NT 5.1 (Build 2600: Service Pack 2)
>I'd really appreciate if anyone has ideas on that.
>thanks,
>Lucy|||Hi Sue, thanks for answering.
I already have SP2, and SMO appears to be ok too.
The errors in the log appear at the time when I try to access the remote
jobs, so there has to be some connection between them...
"Sue Hoegemeier" wrote:

> I think the two errors are separate issues. I've seen the
> issue with viewing jobs come up a few times. I suspect that
> it's caused by problems with the smo dll - did you install
> visual studio service packs to your PC? Try applying SQL
> Server 2005 SP2 on your PC. That worked for me a couple of
> times that I've run into this.
> -Sue
> On Fri, 30 Mar 2007 15:06:01 -0700, Lucy
> <Lucy@.discussions.microsoft.com> wrote:
>
>|||Sorry, Sue, you were right. I looked at it once more and noticed that it was
my Windows that had SP2. Now I installed SP2 for SQL Server and the problem
went away.
Thanks a lot,
Lucy
"Lucy" wrote:
[vbcol=seagreen]
> Hi Sue, thanks for answering.
> I already have SP2, and SMO appears to be ok too.
> The errors in the log appear at the time when I try to access the remote
> jobs, so there has to be some connection between them...
> "Sue Hoegemeier" wrote:
>|||No problem...thanks for posting back.
-Sue
On Mon, 2 Apr 2007 12:32:06 -0700, Lucy
<Lucy@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Sorry, Sue, you were right. I looked at it once more and noticed that it wa
s
>my Windows that had SP2. Now I installed SP2 for SQL Server and the problem
>went away.
>Thanks a lot,
>Lucy
>"Lucy" wrote:
>

cannot see SQL Jobs on remote server

Hi,
I'm having troubles brining up details of existing SQL Jobs from remote
server. When I double-click existing job, it brings up "New Job" dialog box
instead of job details.
I needed to see and modify steps of a job on my collegue's machine. I can
connect to her SQL Server 2005 all right. But when I find the job I need,
right click it and select "Properties", I get "New Job" dialog box with all
tabs empty. What's interesting is I can still use "Script job as" menu item.
Another thing is that I see error messages like this in my error log:
DCOM was unable to communicate with the computer AAA using any of the
configured protocols.
I looked up this message and verified that I don't have UDP or IPX enabled,
only Connection-oriented TCP/IP and Connection-oriented SPX.
My other collegue can see the jobs fine, so I suppose the configuration
issue is with my machine. We all have WinXP Proferssional SP2 and both SQL
Server 2000 and 2005 on our machines. 2005's version is
Microsoft SQL Server 2005 - 9.00.2047.00 (Intel X86) Apr 14 2006 01:12:25
Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Windows
NT 5.1 (Build 2600: Service Pack 2)
I'd really appreciate if anyone has ideas on that.
thanks,
Lucy
I think the two errors are separate issues. I've seen the
issue with viewing jobs come up a few times. I suspect that
it's caused by problems with the smo dll - did you install
visual studio service packs to your PC? Try applying SQL
Server 2005 SP2 on your PC. That worked for me a couple of
times that I've run into this.
-Sue
On Fri, 30 Mar 2007 15:06:01 -0700, Lucy
<Lucy@.discussions.microsoft.com> wrote:

>Hi,
>I'm having troubles brining up details of existing SQL Jobs from remote
>server. When I double-click existing job, it brings up "New Job" dialog box
>instead of job details.
>I needed to see and modify steps of a job on my collegue's machine. I can
>connect to her SQL Server 2005 all right. But when I find the job I need,
>right click it and select "Properties", I get "New Job" dialog box with all
>tabs empty. What's interesting is I can still use "Script job as" menu item.
>Another thing is that I see error messages like this in my error log:
>DCOM was unable to communicate with the computer AAA using any of the
>configured protocols.
>I looked up this message and verified that I don't have UDP or IPX enabled,
>only Connection-oriented TCP/IP and Connection-oriented SPX.
>My other collegue can see the jobs fine, so I suppose the configuration
>issue is with my machine. We all have WinXP Proferssional SP2 and both SQL
>Server 2000 and 2005 on our machines. 2005's version is
>Microsoft SQL Server 2005 - 9.00.2047.00 (Intel X86) Apr 14 2006 01:12:25
> Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Windows
>NT 5.1 (Build 2600: Service Pack 2)
>I'd really appreciate if anyone has ideas on that.
>thanks,
>Lucy
|||Hi Sue, thanks for answering.
I already have SP2, and SMO appears to be ok too.
The errors in the log appear at the time when I try to access the remote
jobs, so there has to be some connection between them...
"Sue Hoegemeier" wrote:

> I think the two errors are separate issues. I've seen the
> issue with viewing jobs come up a few times. I suspect that
> it's caused by problems with the smo dll - did you install
> visual studio service packs to your PC? Try applying SQL
> Server 2005 SP2 on your PC. That worked for me a couple of
> times that I've run into this.
> -Sue
> On Fri, 30 Mar 2007 15:06:01 -0700, Lucy
> <Lucy@.discussions.microsoft.com> wrote:
>
>
|||Sorry, Sue, you were right. I looked at it once more and noticed that it was
my Windows that had SP2. Now I installed SP2 for SQL Server and the problem
went away.
Thanks a lot,
Lucy
"Lucy" wrote:
[vbcol=seagreen]
> Hi Sue, thanks for answering.
> I already have SP2, and SMO appears to be ok too.
> The errors in the log appear at the time when I try to access the remote
> jobs, so there has to be some connection between them...
> "Sue Hoegemeier" wrote:
|||No problem...thanks for posting back.
-Sue
On Mon, 2 Apr 2007 12:32:06 -0700, Lucy
<Lucy@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Sorry, Sue, you were right. I looked at it once more and noticed that it was
>my Windows that had SP2. Now I installed SP2 for SQL Server and the problem
>went away.
>Thanks a lot,
>Lucy
>"Lucy" wrote: