Error linked server query after installing SP4 on SQL 2000

Hello
SQL 2000 SP3a run fine with an linked server query like
select * from openquery( linkedOlapServer, .. here is the MDX ...')
After installing SP4 build 2039 this query fails with error:
Server: Msg 7302, Level 16, State 1, Line 1
Could not create an instance of OLE DB provider 'MSOLAP'.
OLE DB error trace [Non-interface error: CoCreate of DSO for MSOLAP
returned 0x80040154].
Appreciate hints from experience on which hot fix do I need to install?
Nic
Does changing the "AllowInProcess" to something non zero fix this problem?
http://msdn2.microsoft.com/en-us/library/ms190918.aspx
In Object Explorer, right-click the provider name and select Properties. The
following table describes the available provider options...
thanks,
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/
"Nic" <Nic@.discussions.microsoft.com> wrote in message
news:E4A1CCBC-331D-4C70-B83C-F1AFE5CFAA62@.microsoft.com...
> Hello
> SQL 2000 SP3a run fine with an linked server query like
> select * from openquery( linkedOlapServer, .. here is the MDX ...')
> After installing SP4 build 2039 this query fails with error:
> Server: Msg 7302, Level 16, State 1, Line 1
> Could not create an instance of OLE DB provider 'MSOLAP'.
> OLE DB error trace [Non-interface error: CoCreate of DSO for MSOLAP
> returned 0x80040154].
> Appreciate hints from experience on which hot fix do I need to install?
> Nic
>

Error in SQL Query Analyzer when running script in ISQL

I am using SQL 2000 Named Instance with SP3a on a Windows 2000 Server OS
When running this script below I get the following error:
declare @.answer as int
declare @.load_id as int
declare @.dos_command as varchar(500)
set @.load_id = 1
exec @.answer = cp_is_file_ready @.load_id
if (@.answer = 1)
begin
set @.dos_command =
'isql -Sserver -sa -Ppassword -database -Q"exec cp_import_data ' +
convert(varchar(10), @.load_id) + '"'
exec master..xp_cmdshell @.dos_command
end
ERROR MESSAGE:
Msg 18456, Level 14, State 1:
Login failed for user 'sa'.
DB-Library: Login incorrect.
NULL
I checked the sa password and it works for registering the SQL Instance via
the SQL Client and works when connecting to SQL Query Analyzer with it. But
for some reason it blows up when using ISQL.
I am baffled at this point.
Any help is greatly appreciated.Hi,
Replace -U (user) and -P (password) with -E option in ISQL .
I feel the password you enter for the instance is wrong.
Thanks
Hari
MCDBA
"GI" <glenn.illig@.healthtrio.com> wrote in message
news:ej6JV6s1DHA.1752@.tk2msftngp13.phx.gbl...

quote:

---

> I am using SQL 2000 Named Instance with SP3a on a Windows 2000 Server OS
> When running this script below I get the following error:
> declare @.answer as int
> declare @.load_id as int
> declare @.dos_command as varchar(500)
>
> set @.load_id = 1
>
> exec @.answer = cp_is_file_ready @.load_id
> if (@.answer = 1)
> begin
>
> set @.dos_command =
> 'isql -Sserver -sa -Ppassword -database -Q"exec cp_import_data ' +
> convert(varchar(10), @.load_id) + '"'
> exec master..xp_cmdshell @.dos_command
> end
>
> ERROR MESSAGE:
> Msg 18456, Level 14, State 1:
> Login failed for user 'sa'.
> DB-Library: Login incorrect.
> NULL
>
> I checked the sa password and it works for registering the SQL Instance

---

via

quote:

---

> the SQL Client and works when connecting to SQL Query Analyzer with it.

---

But

quote:

---

> for some reason it blows up when using ISQL.
> I am baffled at this point.
> Any help is greatly appreciated.
>
>
>

---

|||GI (glenn.illig@.healthtrio.com) writes:

quote:

---

> I am using SQL 2000 Named Instance with SP3a on a Windows 2000 Server OS
> When running this script below I get the following error:
> declare @.answer as int
> declare @.load_id as int
> declare @.dos_command as varchar(500)
> set @.load_id = 1
> exec @.answer = cp_is_file_ready @.load_id
> if (@.answer = 1)
> begin
> set @.dos_command =
> 'isql -Sserver -sa -Ppassword -database -Q"exec cp_import_data ' +
> convert(varchar(10), @.load_id) + '"'
> exec master..xp_cmdshell @.dos_command
> end

---

If the instance name is SERVER\INSTANCE, does your command line
actually say -S SERVER\INSTANCE? If you only say -S SERVER, you are
trying to connect to the default instance which may have a
different password.
Rather than hardcoding the server name, it may be better to use the
global variable @.@.servername.
Another possible cause is that the password includes non-ASCII characters.
The will be converted to the OEM charset - or a fallback if not available
in the OEM charset. In any case, using -E is much better, since you don't
have to hardcode the password.
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.aspsql

Error In Application Logs

hii...
I am using SQL 2000 With sp3a on win200server.
i am getting following error in application log.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 10/31/2003
Time: 3:52:54 PM
User: N/A
Computer: BNET8
Description:
Error: 17832, Severity: 20, State: 8
Connection opened but invalid login packet(s) sent. Connection closed. Data:
0000: a8 45 00 00 14 00 00 00 =A8E.....
0008: 06 00 00 00 42 00 4e 00 ...B.N.
0010: 45 00 54 00 38 00 00 00 E.T.8...
0018: 00 00 00 00 ...
Please explain? what is this and solution.
Thanks in advanceHi ,
The error (17832) do not indicate a problem with SQL Server, but rather a
network failure, or client application problem.
17832 can happen if a client starts to connect, but never successfully
completes the attempt.
Normally this error is caused by the network failing between the time a
connection attempt is initiated, and when it completes.
You can just ignore this error incase the occurance of this error is
limited. Incase if the occurance is higher please check with your network
services.
Thanks
Hari
MCDBA
"sandi" <anonymous@.discussions.microsoft.com> wrote in message
news:057a01c3a026$9171c6a0$a301280a@.phx.gbl...
hii...
I am using SQL 2000 With sp3a on win200server.
i am getting following error in application log.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 10/31/2003
Time: 3:52:54 PM
User: N/A
Computer: BNET8
Description:
Error: 17832, Severity: 20, State: 8
Connection opened but invalid login packet(s) sent.
Connection closed.
Data:
0000: a8 45 00 00 14 00 00 00 ¨E.....
0008: 06 00 00 00 42 00 4e 00 ...B.N.
0010: 45 00 54 00 38 00 00 00 E.T.8...
0018: 00 00 00 00 ...
Please explain? what is this and solution.
Thanks in advance|||Dear Hari,
Thanks for your help.
sandi
>--Original Message--
>Hi ,
>The error (17832) do not indicate a problem with SQL Server, but rather a
>network failure, or client application problem.
>17832 can happen if a client starts to connect, but never successfully
>completes the attempt.
>Normally this error is caused by the network failing between the time a
>connection attempt is initiated, and when it completes.
>You can just ignore this error incase the occurance of this error is
>limited. Incase if the occurance is higher please check with your network
>services.
>Thanks
>Hari
>MCDBA
>"sandi" <anonymous@.discussions.microsoft.com> wrote in message
>news:057a01c3a026$9171c6a0$a301280a@.phx.gbl...
>hii...
>I am using SQL 2000 With sp3a on win200server.
>i am getting following error in application log.
>Event Type: Error
>Event Source: MSSQLSERVER
>Event Category: (2)
>Event ID: 17052
>Date: 10/31/2003
>Time: 3:52:54 PM
>User: N/A
>Computer: BNET8
>Description:
>Error: 17832, Severity: 20, State: 8
>Connection opened but invalid login packet(s) sent.
>Connection closed.
>Data:
>0000: a8 45 00 00 14 00 00 00 =A8E.....
>0008: 06 00 00 00 42 00 4e 00 ...B.N.
>0010: 45 00 54 00 38 00 00 00 E.T.8...
>0018: 00 00 00 00 ...
>Please explain? what is this and solution.
>Thanks in advance
>
>.
>