Error: 66030

Hi,
On one of our SQL 2000 cluster servers we have been
getting a lot of error messages in our SQL Server log ile.
Error: 66030, Severity: 15, State: 1
Occasionally it also reports
Error: 66040, Severity: 15, State: 1.
I have been unable to find any information on these error
messages. I would be grateful if someone could shed some
light on what these messages actually mean. Thanks.The fact that the error number is > 50000 suggests that this actually an
application specific error message rather than a generic SQL message. Have a
look in master..sysmessages to see the text of the message, it might give
you a clue
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"PaulaC" <anonymous@.discussions.microsoft.com> wrote in message
news:bdac01c4380c$671e2b90$a501280a@.phx.gbl...
> Hi,
> On one of our SQL 2000 cluster servers we have been
> getting a lot of error messages in our SQL Server log ile.
> Error: 66030, Severity: 15, State: 1
> Occasionally it also reports
> Error: 66040, Severity: 15, State: 1.
> I have been unable to find any information on these error
> messages. I would be grateful if someone could shed some
> light on what these messages actually mean. Thanks.
>|||Thanks for the suggestion. Unfortunately, I cannot find
anything like my error messages in sysmessages.
Paula.
>--Original Message--
>The fact that the error number is > 50000 suggests that
this actually an
>application specific error message rather than a generic
SQL message. Have a
>look in master..sysmessages to see the text of the
message, it might give
>you a clue
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>
>"PaulaC" <anonymous@.discussions.microsoft.com> wrote in
message
>news:bdac01c4380c$671e2b90$a501280a@.phx.gbl...
>> Hi,
>> On one of our SQL 2000 cluster servers we have been
>> getting a lot of error messages in our SQL Server log
ile.
>> Error: 66030, Severity: 15, State: 1
>> Occasionally it also reports
>> Error: 66040, Severity: 15, State: 1.
>> I have been unable to find any information on these
error
>> messages. I would be grateful if someone could shed
some
>> light on what these messages actually mean. Thanks.
>
>.
>sql

Error: 66030

Hi,
On one of our SQL 2000 cluster servers we have been
getting a lot of error messages in our SQL Server log ile.
Error: 66030, Severity: 15, State: 1
Occasionally it also reports
Error: 66040, Severity: 15, State: 1.
I have been unable to find any information on these error
messages. I would be grateful if someone could shed some
light on what these messages actually mean. Thanks.The fact that the error number is > 50000 suggests that this actually an
application specific error message rather than a generic SQL message. Have a
look in master..sysmessages to see the text of the message, it might give
you a clue
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"PaulaC" <anonymous@.discussions.microsoft.com> wrote in message
news:bdac01c4380c$671e2b90$a501280a@.phx.gbl...
> Hi,
> On one of our SQL 2000 cluster servers we have been
> getting a lot of error messages in our SQL Server log ile.
> Error: 66030, Severity: 15, State: 1
> Occasionally it also reports
> Error: 66040, Severity: 15, State: 1.
> I have been unable to find any information on these error
> messages. I would be grateful if someone could shed some
> light on what these messages actually mean. Thanks.
>|||Thanks for the suggestion. Unfortunately, I cannot find
anything like my error messages in sysmessages.
Paula.

>--Original Message--
>The fact that the error number is > 50000 suggests that
this actually an
>application specific error message rather than a generic
SQL message. Have a
>look in master..sysmessages to see the text of the
message, it might give
>you a clue
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>
>"PaulaC" <anonymous@.discussions.microsoft.com> wrote in
message
>news:bdac01c4380c$671e2b90$a501280a@.phx.gbl...
ile.[vbcol=seagreen]
error[vbcol=seagreen]
some[vbcol=seagreen]
>
>.
>

Error: 66030

Hi,
On one of our SQL 2000 cluster servers we have been
getting a lot of error messages in our SQL Server log ile.
Error: 66030, Severity: 15, State: 1
Occasionally it also reports
Error: 66040, Severity: 15, State: 1.
I have been unable to find any information on these error
messages. I would be grateful if someone could shed some
light on what these messages actually mean. Thanks.
The fact that the error number is > 50000 suggests that this actually an
application specific error message rather than a generic SQL message. Have a
look in master..sysmessages to see the text of the message, it might give
you a clue
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"PaulaC" <anonymous@.discussions.microsoft.com> wrote in message
news:bdac01c4380c$671e2b90$a501280a@.phx.gbl...
> Hi,
> On one of our SQL 2000 cluster servers we have been
> getting a lot of error messages in our SQL Server log ile.
> Error: 66030, Severity: 15, State: 1
> Occasionally it also reports
> Error: 66040, Severity: 15, State: 1.
> I have been unable to find any information on these error
> messages. I would be grateful if someone could shed some
> light on what these messages actually mean. Thanks.
>
|||Thanks for the suggestion. Unfortunately, I cannot find
anything like my error messages in sysmessages.
Paula.

>--Original Message--
>The fact that the error number is > 50000 suggests that
this actually an
>application specific error message rather than a generic
SQL message. Have a
>look in master..sysmessages to see the text of the
message, it might give
>you a clue
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>
>"PaulaC" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:bdac01c4380c$671e2b90$a501280a@.phx.gbl...
ile.[vbcol=seagreen]
error[vbcol=seagreen]
some
>
>.
>

error: 18452; very urgent

We have 2 failover servers and one client in our test environment. We
have all the three configured in mixed mode authentication(windows +
sql server authentication). But when we are failing over from 1st
server to 2nd one, we are getting the following error message,
'Unable to connected to server xxxx: Server : Msg 18452, Level 16,
State 1 [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user 'null'. Reason: Not associated with a trusted SQL server
connection.'
I got some clue.
For instance we have ser1 and ser2 as clusters. I registered both in
the client's EM. Now what I did was, I made ser1 to run and stopped sql
service in ser2 (active/passive) through failover. Now in the client's
EM I'm able to open ser1 and I cannot access ser2. Now what I did was,
I failed over to ser2 ( so sql service in ser1 is stopped). But now I
can still be able to access ser1 and also I can access ser2, even I'm
able to open query analyzer in ser1 through EM.But when I try to open
query analyzer directly, it is giving the same error message. ser1 is
the virtual name given to both ser1 and ser2. So I think when
connecting through EM, failover is occuring fine.I'm just wondering why
is this happening only with dsn. Can anybody help me?
Thanks,
Preethihttp://support.microsoft.com/default.aspx?scid=kb;en-us;555332
"sqldbapree" <mohanpreethi0125@.gmail.com> wrote in message
news:1129898680.495504.25600@.g44g2000cwa.googlegroups.com...
> We have 2 failover servers and one client in our test environment. We
> have all the three configured in mixed mode authentication(windows +
> sql server authentication). But when we are failing over from 1st
> server to 2nd one, we are getting the following error message,
> 'Unable to connected to server xxxx: Server : Msg 18452, Level 16,
> State 1 [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
> user 'null'. Reason: Not associated with a trusted SQL server
> connection.'
> I got some clue.
> For instance we have ser1 and ser2 as clusters. I registered both in
> the client's EM. Now what I did was, I made ser1 to run and stopped sql
> service in ser2 (active/passive) through failover. Now in the client's
> EM I'm able to open ser1 and I cannot access ser2. Now what I did was,
> I failed over to ser2 ( so sql service in ser1 is stopped). But now I
> can still be able to access ser1 and also I can access ser2, even I'm
> able to open query analyzer in ser1 through EM.But when I try to open
> query analyzer directly, it is giving the same error message. ser1 is
> the virtual name given to both ser1 and ser2. So I think when
> connecting through EM, failover is occuring fine.I'm just wondering why
> is this happening only with dsn. Can anybody help me?
> Thanks,
> Preethi
>

error: 18452; very urgent

We have 2 failover servers and one client in our test environment. We
have all the three configured in mixed mode authentication(windows +
sql server authentication). But when we are failing over from 1st
server to 2nd one, we are getting the following error message,
'Unable to connected to server xxxx: Server : Msg 18452, Level 16,
State 1 [Microsoft][ODBC SQL Server Driver][SQL Server]Login fai
led for
user 'null'. Reason: Not associated with a trusted SQL server
connection.'
I got some clue.
For instance we have ser1 and ser2 as clusters. I registered both in
the client's EM. Now what I did was, I made ser1 to run and stopped sql
service in ser2 (active/passive) through failover. Now in the client's
EM I'm able to open ser1 and I cannot access ser2. Now what I did was,
I failed over to ser2 ( so sql service in ser1 is stopped). But now I
can still be able to access ser1 and also I can access ser2, even I'm
able to open query analyzer in ser1 through EM.But when I try to open
query analyzer directly, it is giving the same error message. ser1 is
the virtual name given to both ser1 and ser2. So I think when
connecting through EM, failover is occuring fine.I'm just wondering why
is this happening only with dsn. Can anybody help me?
Thanks,
Preethihttp://support.microsoft.com/defaul...kb;en-us;555332
"sqldbapree" <mohanpreethi0125@.gmail.com> wrote in message
news:1129898680.495504.25600@.g44g2000cwa.googlegroups.com...
> We have 2 failover servers and one client in our test environment. We
> have all the three configured in mixed mode authentication(windows +
> sql server authentication). But when we are failing over from 1st
> server to 2nd one, we are getting the following error message,
> 'Unable to connected to server xxxx: Server : Msg 18452, Level 16,
> State 1 [Microsoft][ODBC SQL Server Driver][SQL Server]Login f
ailed for
> user 'null'. Reason: Not associated with a trusted SQL server
> connection.'
> I got some clue.
> For instance we have ser1 and ser2 as clusters. I registered both in
> the client's EM. Now what I did was, I made ser1 to run and stopped sql
> service in ser2 (active/passive) through failover. Now in the client's
> EM I'm able to open ser1 and I cannot access ser2. Now what I did was,
> I failed over to ser2 ( so sql service in ser1 is stopped). But now I
> can still be able to access ser1 and also I can access ser2, even I'm
> able to open query analyzer in ser1 through EM.But when I try to open
> query analyzer directly, it is giving the same error message. ser1 is
> the virtual name given to both ser1 and ser2. So I think when
> connecting through EM, failover is occuring fine.I'm just wondering why
> is this happening only with dsn. Can anybody help me?
> Thanks,
> Preethi
>

error: 18452; very urgent

We have 2 failover servers and one client in our test environment. We
have all the three configured in mixed mode authentication(windows +
sql server authentication). But when we are failing over from 1st
server to 2nd one, we are getting the following error message,
'Unable to connected to server xxxx: Server : Msg 18452, Level 16,
State 1 [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user 'null'. Reason: Not associated with a trusted SQL server
connection.'
I got some clue.
For instance we have ser1 and ser2 as clusters. I registered both in
the client's EM. Now what I did was, I made ser1 to run and stopped sql
service in ser2 (active/passive) through failover. Now in the client's
EM I'm able to open ser1 and I cannot access ser2. Now what I did was,
I failed over to ser2 ( so sql service in ser1 is stopped). But now I
can still be able to access ser1 and also I can access ser2, even I'm
able to open query analyzer in ser1 through EM.But when I try to open
query analyzer directly, it is giving the same error message. ser1 is
the virtual name given to both ser1 and ser2. So I think when
connecting through EM, failover is occuring fine.I'm just wondering why
is this happening only with dsn. Can anybody help me?
Thanks,
Preethi
http://support.microsoft.com/default...b;en-us;555332
"sqldbapree" <mohanpreethi0125@.gmail.com> wrote in message
news:1129898680.495504.25600@.g44g2000cwa.googlegro ups.com...
> We have 2 failover servers and one client in our test environment. We
> have all the three configured in mixed mode authentication(windows +
> sql server authentication). But when we are failing over from 1st
> server to 2nd one, we are getting the following error message,
> 'Unable to connected to server xxxx: Server : Msg 18452, Level 16,
> State 1 [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
> user 'null'. Reason: Not associated with a trusted SQL server
> connection.'
> I got some clue.
> For instance we have ser1 and ser2 as clusters. I registered both in
> the client's EM. Now what I did was, I made ser1 to run and stopped sql
> service in ser2 (active/passive) through failover. Now in the client's
> EM I'm able to open ser1 and I cannot access ser2. Now what I did was,
> I failed over to ser2 ( so sql service in ser1 is stopped). But now I
> can still be able to access ser1 and also I can access ser2, even I'm
> able to open query analyzer in ser1 through EM.But when I try to open
> query analyzer directly, it is giving the same error message. ser1 is
> the virtual name given to both ser1 and ser2. So I think when
> connecting through EM, failover is occuring fine.I'm just wondering why
> is this happening only with dsn. Can anybody help me?
> Thanks,
> Preethi
>

Error: "no report servers were found on the specified machine"

Error: "no report servers were found on the specified machine"

I get this error when launching the Reporting Services Configuration Manager...I've never seen this error, usually it can talk to my local servername but unfortunately it's not. This is a new test server and the first time I've come across this message after setting up Reporting services on 2 machines sucessfully in the past.

Are you using the config tool to manage a remote RS server?|||I'm getting this too but it's on the local box.|||

NoEgo wrote:

Error: "no report servers were found on the specified machine"

I get this error when launching the Reporting Services Configuration Manager...I've never seen this error, usually it can talk to my local servername but unfortunately it's not. This is a new test server and the first time I've come across this message after setting up Reporting services on 2 machines sucessfully in the past.

|||

Hello there, is got solved for me by running SQL Setup and selecting a new component (Reporting Services). See my post at http://blogs.msdn.com/dszabo/archive/2007/04/10/quot-no-report-servers-were-found-on-the-specified-machine-quot.aspx for more details.

David

Error: "no report servers were found on the specified machine"

Error: "no report servers were found on the specified machine"

I get this error when launching the Reporting Services Configuration Manager...I've never seen this error, usually it can talk to my local servername but unfortunately it's not. This is a new test server and the first time I've come across this message after setting up Reporting services on 2 machines sucessfully in the past.

Are you using the config tool to manage a remote RS server?|||I'm getting this too but it's on the local box.|||

NoEgo wrote:

Error: "no report servers were found on the specified machine"

I get this error when launching the Reporting Services Configuration Manager...I've never seen this error, usually it can talk to my local servername but unfortunately it's not. This is a new test server and the first time I've come across this message after setting up Reporting services on 2 machines sucessfully in the past.

|||

Hello there, is got solved for me by running SQL Setup and selecting a new component (Reporting Services). See my post at http://blogs.msdn.com/dszabo/archive/2007/04/10/quot-no-report-servers-were-found-on-the-specified-machine-quot.aspx for more details.

David

Error: "no report servers were found on the specified machine"

Error: "no report servers were found on the specified machine"

I get this error when launching the Reporting Services Configuration Manager...I've never seen this error, usually it can talk to my local servername but unfortunately it's not. This is a new test server and the first time I've come across this message after setting up Reporting services on 2 machines sucessfully in the past.

Are you using the config tool to manage a remote RS server?|||I'm getting this too but it's on the local box.|||

NoEgo wrote:

Error: "no report servers were found on the specified machine"

I get this error when launching the Reporting Services Configuration Manager...I've never seen this error, usually it can talk to my local servername but unfortunately it's not. This is a new test server and the first time I've come across this message after setting up Reporting services on 2 machines sucessfully in the past.

|||

Hello there, is got solved for me by running SQL Setup and selecting a new component (Reporting Services). See my post at http://blogs.msdn.com/dszabo/archive/2007/04/10/quot-no-report-servers-were-found-on-the-specified-machine-quot.aspx for more details.

David

Error with linked Servers

I am having an extremely difficult time getting a linked server to
work. I am attempting to link to using an ODBC driver to a proprietary
database. I can create the ODBC connection and see the tables from
with Access using this connection. I can set up the linked server but
as soon as I attempt to view the tables it either gives me an error
7399 or just sits there. Any help would be appreciative and if there
are any other questions I need to answer just let me know.
Thanks,
Matt
Can you elaborate on how are you connecting via Access and how are you using
to create the linked server?
"Matt" wrote:

> I am having an extremely difficult time getting a linked server to
> work. I am attempting to link to using an ODBC driver to a proprietary
> database. I can create the ODBC connection and see the tables from
> with Access using this connection. I can set up the linked server but
> as soon as I attempt to view the tables it either gives me an error
> 7399 or just sits there. Any help would be appreciative and if there
> are any other questions I need to answer just let me know.
> Thanks,
> Matt
>

Error with Linked Servers

From time to time the linked servers we have set up cannot be accessed. When
I click on the tables node under the linked server within enterprise manager
the session hangs and no error message is displayed. When querying the data
via an openquery no error is thrown, the query simply runs until manually
aborted.
I've created a linked server OK but immediately cannot open it. The only way
around this problem we have is a reboot of the server. Does anyone know how
to resolve this problem and also what would cause this.
Thanks
MikeMikeD
Do you have ping to linked server?
"MikeD" <MikeD@.discussions.microsoft.com> wrote in message
news:ACBEC816-1EE1-46E8-9535-8E52BB7C502A@.microsoft.com...
> From time to time the linked servers we have set up cannot be accessed.
> When
> I click on the tables node under the linked server within enterprise
> manager
> the session hangs and no error message is displayed. When querying the
> data
> via an openquery no error is thrown, the query simply runs until manually
> aborted.
> I've created a linked server OK but immediately cannot open it. The only
> way
> around this problem we have is a reboot of the server. Does anyone know
> how
> to resolve this problem and also what would cause this.
> Thanks
> Mike|||I can ping the server that sql is on if that's what you mean. I can see and
create linked servers but cannot query them - see below.
"Uri Dimant" wrote:

> MikeD
> Do you have ping to linked server?
> "MikeD" <MikeD@.discussions.microsoft.com> wrote in message
> news:ACBEC816-1EE1-46E8-9535-8E52BB7C502A@.microsoft.com...
>
>|||MikeD
Do you run the query in this way?
SELECT <> FROM Server.dbname.dbo.table
"MikeD" <MikeD@.discussions.microsoft.com> wrote in message
news:2C11B49F-D1BF-48C2-9ECC-2470666F9691@.microsoft.com...[vbcol=seagreen]
>I can ping the server that sql is on if that's what you mean. I can see and
> create linked servers but cannot query them - see below.
> "Uri Dimant" wrote:
>|||No - it's an openquery so it's :
SELECT * FROM OPENQUERY[linked_server_name], 'Select * from table_name'
But the problem isn't so much in the query it's the fact that when you
select the linked server the system hangs with no error message and the only
way we have of resolving the issue is a server reboot
"Uri Dimant" wrote:

> MikeD
> Do you run the query in this way?
> SELECT <> FROM Server.dbname.dbo.table
>
>
> "MikeD" <MikeD@.discussions.microsoft.com> wrote in message
> news:2C11B49F-D1BF-48C2-9ECC-2470666F9691@.microsoft.com...
>
>|||Well, is it large set data you want to return?
exec sp_serveroption 'servername','data access','true'
"MikeD" <MikeD@.discussions.microsoft.com> wrote in message
news:6EA13818-E61B-49E7-B6E0-35F581ADAF0F@.microsoft.com...[vbcol=seagreen]
> No - it's an openquery so it's :
> SELECT * FROM OPENQUERY[linked_server_name], 'Select * from table_name
'
> But the problem isn't so much in the query it's the fact that when you
> select the linked server the system hangs with no error message and the
> only
> way we have of resolving the issue is a server reboot
> "Uri Dimant" wrote:
>|||It's nothing to do with the query or the size of data. the problem is that
the linked server cannot be accessed until a reboot is done.
"Uri Dimant" wrote:

> Well, is it large set data you want to return?
> exec sp_serveroption 'servername','data access','true'
>
> "MikeD" <MikeD@.discussions.microsoft.com> wrote in message
> news:6EA13818-E61B-49E7-B6E0-35F581ADAF0F@.microsoft.com...
>
>

Error with linked Servers

I am having an extremely difficult time getting a linked server to
work. I am attempting to link to using an ODBC driver to a proprietary
database. I can create the ODBC connection and see the tables from
with Access using this connection. I can set up the linked server but
as soon as I attempt to view the tables it either gives me an error
7399 or just sits there. Any help would be appreciative and if there
are any other questions I need to answer just let me know.
Thanks,
MattCan you elaborate on how are you connecting via Access and how are you using
to create the linked server?
"Matt" wrote:

> I am having an extremely difficult time getting a linked server to
> work. I am attempting to link to using an ODBC driver to a proprietary
> database. I can create the ODBC connection and see the tables from
> with Access using this connection. I can set up the linked server but
> as soon as I attempt to view the tables it either gives me an error
> 7399 or just sits there. Any help would be appreciative and if there
> are any other questions I need to answer just let me know.
> Thanks,
> Matt
>

Error with linked Servers

I am having an extremely difficult time getting a linked server to
work. I am attempting to link to using an ODBC driver to a proprietary
database. I can create the ODBC connection and see the tables from
with Access using this connection. I can set up the linked server but
as soon as I attempt to view the tables it either gives me an error
7399 or just sits there. Any help would be appreciative and if there
are any other questions I need to answer just let me know.
Thanks,
MattCan you elaborate on how are you connecting via Access and how are you using
to create the linked server?
"Matt" wrote:
> I am having an extremely difficult time getting a linked server to
> work. I am attempting to link to using an ODBC driver to a proprietary
> database. I can create the ODBC connection and see the tables from
> with Access using this connection. I can set up the linked server but
> as soon as I attempt to view the tables it either gives me an error
> 7399 or just sits there. Any help would be appreciative and if there
> are any other questions I need to answer just let me know.
> Thanks,
> Matt
>

error with linked server

Hi
when i try to run a query using linked servers, i get the following
error.

Server: Msg 125, Level 15, State 1, Line 1
Case expressions may only be nested to level 10.

I do have more than 10 case statements, it works fine when it is less
than 10. can anyone tell me if there is a way to have more than 10
case statements. thanks alot.

Jay

my query
Select category, val, Sum(QTY) As QTY , yr
From
(
Select val, QTY2 As QTY,
KEEP = Case
When code = '004' And ((YR > 2003) Or (YR = 2003 And MON > 12))
Then 'N'
When CODE = '005' And ((YR > 2003) Or (YR = 2003 And MON > 12))
Then 'N'
When CODE = '003' And ((YR > 2003) Or (YR = 2003 And MON > 12))
Then 'N'
When CODE = '017' And ((YR > 2003) Or (YR = 2003 And MON > 12))
Then 'N'
When CODE = '007' And ((YR > 2003) Or (YR = 2003 And MON > 12))
Then 'N'
When CODE = '008' And ((YR > 2003) Or (YR = 2003 And MON > 12))
Then 'N'
When CODE = '009' And ((YR > 2003) Or (YR = 2003 And MON > 11))
Then 'N'
When CODE = '010' And ((YR > 2003) Or (YR = 2003 And MON > 12))
Then 'N'
When CODE = '038' And ((YR > 2003) Or (YR = 2003 And MON > 12))
Then 'N'
When CODE = '032' And ((YR > 2003) Or (YR = 2003 And MON > 12))
Then 'N'
When CODE = '030' And ((YR > 2003) Or (YR = 2003 And MON > 12))
Then 'N'
When CODE = '018' And ((YR > 2003) Or (YR = 2003 And MON > 12))
Then 'N'
Else 'Y' End
From
amf a Join linkedserver.source.dbo.table2 b On a.COM = b.COM
Where CATEGORY In ('1') And CODE In ('001','003','004','005')
And b.YR Between 2003 And 2004 And b.MON <= 1
) x
Where KEEP = 'Y'
Group By CATEGORY, YR"Jay" <webforum2000@.yahoo.com> wrote in message
news:9594a55e.0404230831.50bcabe0@.posting.google.c om...
> Hi
> when i try to run a query using linked servers, i get the following
> error.
> Server: Msg 125, Level 15, State 1, Line 1
> Case expressions may only be nested to level 10.
> I do have more than 10 case statements, it works fine when it is less
> than 10. can anyone tell me if there is a way to have more than 10
> case statements. thanks alot.
> Jay
> my query
> Select category, val, Sum(QTY) As QTY , yr
> From
> (
> Select val, QTY2 As QTY,
> KEEP = Case
> When code = '004' And ((YR > 2003) Or (YR = 2003 And MON > 12))
> Then 'N'
> When CODE = '005' And ((YR > 2003) Or (YR = 2003 And MON > 12))
> Then 'N'
> When CODE = '003' And ((YR > 2003) Or (YR = 2003 And MON > 12))
> Then 'N'
> When CODE = '017' And ((YR > 2003) Or (YR = 2003 And MON > 12))
> Then 'N'
> When CODE = '007' And ((YR > 2003) Or (YR = 2003 And MON > 12))
> Then 'N'
> When CODE = '008' And ((YR > 2003) Or (YR = 2003 And MON > 12))
> Then 'N'
> When CODE = '009' And ((YR > 2003) Or (YR = 2003 And MON > 11))
> Then 'N'
> When CODE = '010' And ((YR > 2003) Or (YR = 2003 And MON > 12))
> Then 'N'
> When CODE = '038' And ((YR > 2003) Or (YR = 2003 And MON > 12))
> Then 'N'
> When CODE = '032' And ((YR > 2003) Or (YR = 2003 And MON > 12))
> Then 'N'
> When CODE = '030' And ((YR > 2003) Or (YR = 2003 And MON > 12))
> Then 'N'
> When CODE = '018' And ((YR > 2003) Or (YR = 2003 And MON > 12))
> Then 'N'
> Else 'Y' End
> From
> amf a Join linkedserver.source.dbo.table2 b On a.COM = b.COM
> Where CATEGORY In ('1') And CODE In ('001','003','004','005')
> And b.YR Between 2003 And 2004 And b.MON <= 1
> ) x
> Where KEEP = 'Y'
> Group By CATEGORY, YR

Since most of your conditions are the same, have you tried something like
this?

Select category, val, Sum(QTY) As QTY , yr
From
(
Select val, QTY2 As QTY,
KEEP = Case
When code in ('004', '005, '003', '017', /* etc. */)
And ((YR > 2003) Or (YR = 2003 And MON > 12))
Else 'Y' End
From
amf a Join linkedserver.source.dbo.table2 b On a.COM = b.COM
Where CATEGORY In ('1') And CODE In ('001','003','004','005')
And b.YR Between 2003 And 2004 And b.MON <= 1
) x

Simon|||
hi
thanks for the suggestion. I have a problem, this is one of the query
where it is all the same, in a few others it varies a lot. i want to
know if the limitaion exists in sql using linked servers ( since it
works fine if i dont use linked servers and have them in the same
server). i want to get aroud this, so that i dont have to change all my
existing queries, and would hamper my using linked server. thanks.. any
suggestion?

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Error while synchronizing merge replication for first time

I am trying to run the replication merge agent for the first time for a
replication. Several servers already replicate to the same server without
problems. I have replicated all the previous Publishers to my subscriber
with the identical setup with the exception of the user login into the
server. The user login sees the appropriate tables in the subscriber yet the
first synchronization errors with the following:
rror messages:
The process could not connect to Subscriber 'hera'. (Source: MSSQL_REPL,
Error number: MSSQL_REPL20084) Get help: http://help/MSSQL_REPL20084 Named
Pipes Provider: Could not open a connection to SQL Server [53].
(Source: MSSQLServer, Error number: 53)
Get help: http://help/53
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. (Source: MSSQLServer, Error number: 53) Get help:
http://help/53 Login timeout expired (Source: MSSQLServer, Error number: 0)
Get help: http://help/0 The merge process failed to execute a query because
the query timed out.
If this failure continues, increase the query timeout for the process.
When troubleshooting, restart the synchronization with verbose history
logging and specify an output file to which to write. (Source:
MSSQLServer, Error number: 0)
Get help: http://help/0
The subscription to publication 'PUB_1' could not be verified. Ensure that
all Merge Agent command line parameters are specified correctly and that the
subscription is correctly configured. If the Publisher no longer has
information about this subscription, drop and recreate the subscription.
(Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201019) Get help:
http://help/MSSQL_REPL-2147201019
Have any of you seen this error before? Do you know of a possible solution?
Thank you,
Pete Ocasio
Senior Software Developer
It sounds like the publisher login or the distributor login does not have
sufficient rights to pull the subscription.
Verify the subscriber can connect to the publisher - try a ping and map a
drive to the publisher from the subscriber and then verify the distributor
login assigned on the subscriber is in the dbo_role on the publisher and the
publisher login defined on the subscriber is in the pal on the publisher.
http://www.zetainteractive.com - Shift Happens!
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
"Pete Ocasio" <pete.ocasio@.execupay.com> wrote in message
news:O5cWeJ9RIHA.4888@.TK2MSFTNGP02.phx.gbl...
>I am trying to run the replication merge agent for the first time for a
>replication. Several servers already replicate to the same server without
>problems. I have replicated all the previous Publishers to my subscriber
>with the identical setup with the exception of the user login into the
>server. The user login sees the appropriate tables in the subscriber yet
>the first synchronization errors with the following:
> rror messages:
> The process could not connect to Subscriber 'hera'. (Source: MSSQL_REPL,
> Error number: MSSQL_REPL20084) Get help: http://help/MSSQL_REPL20084 Named
> Pipes Provider: Could not open a connection to SQL Server [53].
> (Source: MSSQLServer, Error number: 53)
> Get help: http://help/53
> 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. (Source: MSSQLServer, Error number: 53) Get help:
> http://help/53 Login timeout expired (Source: MSSQLServer, Error number:
> 0) Get help: http://help/0 The merge process failed to execute a query
> because the query timed out.
> If this failure continues, increase the query timeout for the process.
> When troubleshooting, restart the synchronization with verbose history
> logging and specify an output file to which to write. (Source:
> MSSQLServer, Error number: 0)
> Get help: http://help/0
> The subscription to publication 'PUB_1' could not be verified. Ensure that
> all Merge Agent command line parameters are specified correctly and that
> the subscription is correctly configured. If the Publisher no longer has
> information about this subscription, drop and recreate the subscription.
> (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201019) Get help:
> http://help/MSSQL_REPL-2147201019
> Have any of you seen this error before? Do you know of a possible
> solution?
> Thank you,
> Pete Ocasio
> Senior Software Developer
>

Error while retrieving servers

I've tried to retrieve and fill a combobox with all my servers on my network, and the program tells me he doesn't found any servers, I've got three instances running (SRV-01,SRV-02,SRV-01\SQLEXPRESS), I really don't understand. So I use

SmoApplication.EnumAvailableSqlServers(true)

to test only on my local machine and no server found ?

Here is the code I used :

this.Cursor = Cursors.WaitCursor;

DataTable dtSqlServer = SmoApplication.EnumAvailableSqlServers(true);

foreach (DataRow drServer in dtSqlServer.Rows)

{

string sServer = drServer["Server"].ToString();

if (drServer["Instance"] != null && drServer["Instance"].ToString().Length > 0)

sServer += @."\" + drServer["Instance"].ToString();

if (listDataBases.Items.IndexOf(sServer) < 0)

listDataBases.Items.Add(sServer);

//Make the local server the default

Server local = new Server();

String serverName = local.Name;

if (local.InstanceName != null && local.InstanceName.Length > 0)

serverName += @."\" + local.InstanceName;

Int32 idx = listDataBases.FindStringExact(serverName);

if (idx >= 0)

listDataBases.SelectedIndex = idx;

this.Cursor = Cursors.Default;

}

Is someone can help me thanks, I use Win XP SP2, VS 2005 team suite, SQL Server 2005 std + SP1, SQL Server 2005 express + SP 1

PS : I've tried without EnumAvailableSqlServers using a simple textbox instead, and when I enter the name of my servers it works ?!!!

I've disabled SQL Server Browser now it see my local server but not my network instances and not my SQL Express instance ?|||Hi, I guess you are messing up with instance and server of the resultset of the enumaration of the server.

http://www.sqlserver2005.de/articles/1/

HTH, jens Suessmeyer.

http://www.sqlserver2005.de

Error while executing the Best Practice Group

Hi,
I've tried to install the BPA on two different SQL servers, but in every
case I get the following error executing it (bellow). I've reinstalled
several times and used different computers and SQL's. The .NET framework is
1.1. Any ideas?
"Error while executing the Best Practice Group. See the log file
Cmpl_javierx_0001_1.1.1.1_sqlbpa.log. Error message: Execution log not found
in the repository"
Thanks
Any ideas? Anyone?
"Javier" wrote:

> Hi,
> I've tried to install the BPA on two different SQL servers, but in every
> case I get the following error executing it (bellow). I've reinstalled
> several times and used different computers and SQL's. The .NET framework is
> 1.1. Any ideas?
> "Error while executing the Best Practice Group. See the log file
> Cmpl_javierx_0001_1.1.1.1_sqlbpa.log. Error message: Execution log not found
> in the repository"
> Thanks
>
>
|||Hi Javier,
If you didn't find your solution yet, I've got the same problem as you
but fix it by unchecking the no Count option on in the SQL Server Properties.
In the connection Tab, you will need to uncheck "no Count"... Try that, it
should fix the problem...
"Javier Limones" wrote:
[vbcol=seagreen]
> Any ideas? Anyone?
> "Javier" wrote:
|||Dennis,
Sorry for the late reply... The servers we use need the "No Count" option
checked for an application to work... Is there another way to fix this?
Javier
"Denis Daigle" wrote:
[vbcol=seagreen]
> Hi Javier,
> If you didn't find your solution yet, I've got the same problem as you
> but fix it by unchecking the no Count option on in the SQL Server Properties.
> In the connection Tab, you will need to uncheck "no Count"... Try that, it
> should fix the problem...
> "Javier Limones" wrote:

error while Configuring XML Support in IIS with IIS 6.0

Hi,

I've two servers on which there is the SQL 2000 Server and the IIS 6.0.

I installed the SQL Server Client Tools on web server.

And created the nwind as told in booksonline.

I declared the SQLXML extention and allowed it using IIS 6.

But there is a problem with the virtual directory I created using the tool "Configure XML Support in IIS". Web server doesn't realize it as a virtual directory. Even a jpg or a text file is not served by the IIS.

The web server shows the following error.

ERROR: 500 Internal Server Error
HResult: 0x800706f4
Source: Microsoft SQL isapi extension
Description: Invalid virtual root settings

Thanks for any suggestions.Ok,

Do not use Client Tools any more on web server.

Instead, yuo can use SQLXML 3.0.

This solved my problem.|||Cool. Glad it's solved. The good news is that Yukon integrates all these features, so there won't be this kind of confusion. That is, if you can wait a year or so for Yukon!

Don