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 level and expressions

In a report, I have the expression :

=iif(Sum( Fields!X_A_1.Value)<>0,(Sum( Fields!X_A.Value)-Sum( Fields!X_A_1.Value))/Sum( Fields!X_A_1.Value),"NA")

This expression product the error

"The value expression for the textbox ‘textbox12’ contains an error: Attempted to divide by zero."

I think it's because reporting execute the expression
(Sum( Fields!X_A.Value)-Sum( Fields!X_A_1.Value))/Sum( Fields!X_A_1.Value)

even if X_A_1 is equal to 0.

I would like reporting to display NA and not "#Error" when X_A_1 = 0

Is there is a way to catch the error in reporting?

Is there is a way for reporting not to execute the expression

(Sum( Fields!X_A.Value)-Sum( Fields!X_A_1.Value))/Sum( Fields!X_A_1.Value)

when X_A_1 is equal to 0.

Sorry if my english is not very good

Note: IIF() is a function call and evaluates all arguments (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vblr7/html/vafctiif.asp)

Instead of the pattern =IIF(Y=0, A, X/Y), use =IIF(Y=0, A, X / IIF(Y=0, 1, Y)) to avoid the division by zero.

-- Robert

error ITransactionJoin::JoinTransaction

We have job that runs on sql server 2000 every mintute, the job logic is to retrieve data from remote sql 2000 server using link server config. 98% of the time the job run sucessfully, but once in while the job fails with the following error:
'SQLOLEDB' reported an error. [SQLSTATE 42000] (Error 7399)
[SQLSTATE 01000] (Error 7312) OLE DB error trace [OLE/DB Provider
'SQLOLEDB' ITransactionJoin::JoinTransaction returned 0x80004005: ].
[SQLSTATE 01000] (Error 7300). The step failed.
Does, anyone know why is this happening?
Thank You,
Jason
Jason,
What version of Windows are you using? If Windows 2000, make sure you
are on SP4. This might solve it. Also, check that there is not a
firewall between the servers, if there is, ensure that RPC traffic is
allowed through.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Jason wrote:
> We have job that runs on sql server 2000 every mintute, the job logic is to retrieve data from remote sql 2000 server using link server config. 98% of the time the job run sucessfully, but once in while the job fails with the following error:
> 'SQLOLEDB' reported an error. [SQLSTATE 42000] (Error 7399)
> [SQLSTATE 01000] (Error 7312) OLE DB error trace [OLE/DB Provider
> 'SQLOLEDB' ITransactionJoin::JoinTransaction returned 0x80004005: ].
> [SQLSTATE 01000] (Error 7300). The step failed.
> Does, anyone know why is this happening?
> Thank You,
> Jason
|||All the server that communiate with each other using link config do have sp4 for windows 2000 and there is no firewall between the servers.
|||Jason,
This looks like a case for Microsoft Support.
http://support.microsoft.com/default...d=fh;EN-US;sql
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
jason wrote:
> All the server that communiate with each other using link config do have sp4 for windows 2000 and there is no firewall between the servers.

error ITransactionJoin::JoinTransaction

We have job that runs on sql server 2000 every mintute, the job logic is to
retrieve data from remote sql 2000 server using link server config. 98% of t
he time the job run sucessfully, but once in while the job fails with the fo
llowing error:
'SQLOLEDB' reported an error. [SQLSTATE 42000] (Error 7399)
[SQLSTATE 01000] (Error 7312) OLE DB error trace [OLE/DB Provider
'SQLOLEDB' ITransactionJoin::JoinTransaction returned 0x80004005: ].
[SQLSTATE 01000] (Error 7300). The step failed.
Does, anyone know why is this happening?
Thank You,
JasonJason,
What version of Windows are you using? If Windows 2000, make sure you
are on SP4. This might solve it. Also, check that there is not a
firewall between the servers, if there is, ensure that RPC traffic is
allowed through.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Jason wrote:
> We have job that runs on sql server 2000 every mintute, the job logic is t
o retrieve data from remote sql 2000 server using link server config. 98% of
the time the job run sucessfully, but once in while the job fails with the
following error:
> 'SQLOLEDB' reported an error. [SQLSTATE 42000] (Error 7399)
> [SQLSTATE 01000] (Error 7312) OLE DB error trace [OLE/DB Provide
r
> 'SQLOLEDB' ITransactionJoin::JoinTransaction returned 0x80004005: ].
> [SQLSTATE 01000] (Error 7300). The step failed.
> Does, anyone know why is this happening?
> Thank You,
> Jason|||All the server that communiate with each other using link config do have sp4
for Windows 2000 and there is no firewall between the servers.|||Jason,
This looks like a case for Microsoft Support.
http://support.microsoft.com/defaul...id=fh;EN-US;sql
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
jason wrote:
> All the server that communiate with each other using link config do have sp4 for w
indows 2000 and there is no firewall between the servers.

Error is SQL block

I want to know the error in the following SQL block,

I want to know, what is the error in the below block,

BEGIN

Declare @.StoreIdasvarchar(20)

Declare @.DepartmentIdasvarchar(20)

Declare @.VendorNumberasvarchar(20)

Declare @.SortByasint

Declare @.AllVendorSelectedasint

Declare @.SQLasnvarchar(500)

Set @.StoreId='1'

Set @.DepartmentId='NONE'

Set @.VendorNumber='NONE'

Set @.SortBy= 0

Set @.AllVendorSelected= 0

SET @.SQL='SELECT

Inventory.ItemNum

,Inventory.ItemName

,Inventory.ItemName_Extra

,Inventory.Dept_ID

,Inventory.In_Stock

,Inventory.Cost

,Inventory.Price

,Inventory.NumBoxes

,Inventory.NumPerCase

,Inventory.Store_ID

,Departments.Description

FROM

Inventory

INNER JOIN Departments ON Inventory.Store_ID = Departments.Store_ID AND Inventory.Dept_ID = Departments.Dept_ID

LEFT OUTER JOIN Inventory_Vendors ON Inventory.ItemNum = Inventory_Vendors.ItemNum AND Inventory.Store_ID = Inventory_Vendors.Store_ID

WHERE

Inventory.Store_Id in (@.StoreId)

AND Inventory.Dept_ID in (@.DepartmentId)

AND (@.AllVendorSelected = 1 OR Inventory_Vendors.Vendor_Number in (@.VendorNumber))'

IF(@.SortBy= 0)

SET @.SQL= @.SQL+'ORDER BY Inventory.ItemNum'

ELSE

SET @.SQL= @.SQL+'ORDER BY Inventory.ItemName'

EXEC @.SQL

END

I see several errors, mostly to do with this.

WHERE

Inventory.Store_Id in (@.StoreId)

AND Inventory.Dept_ID in (@.DepartmentId)

AND (@.AllVendorSelected = 1 OR Inventory_Vendors.Vendor_Number in (@.VendorNumber))'

|||

I hate this editor.

Anyway, you can't stick @.StoreId in there like that if it may ever have multiples (I see a single here, but assume it's a test or you would not use IN). You need to use '+@.StoreId+' instead. Same goes for the other fields like that.

sql

error is installing msde

I am trying to install msde and everything went fine until the end i got the
error message "The instance name specified is invalid" that came up while
it was configuring Microsoft SQL Server Desktop Engine
hi,
dopey0331 wrote:
> I am trying to install msde and everything went fine until the end i
> got the error message "The instance name specified is invalid"
> that came up while it was configuring Microsoft SQL Server Desktop
> Engine
can you please post the command line used to install?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Error Installing Workstation Components SQL 2005 Enterprise

Hello. I am trying to install only the Workstation Components portion of SQL Server 2005 and I get about halfway through and the installation errors out. The error is:

EventType: sql90setup

P1: installtoolsaction

P2: 0xc0000006

P3: 0x78158a35

P4: 0xc0000006

P5: setup_sqlactionenginelistener.cpp@.198

P6: setup.exe@.2005.90.1399.0

P7: none

This happens after the second disk of the installation is about halfway through installing and then it throws an error stating that "The wrong volume is in the drive. Please insert volume SQLSRVRS into drive D. Cancel, Try Again, Continue" I replace the disc with the first disc and if I pick "Continue" it will display the error above. If I pick "Try again" the installation finishes, but there are components missing from Visual Studio.

Here is the log file:

=== Verbose logging started: 3/16/2006 14:03:49 Build type: SHIP UNICODE 3.01.4000.2435 Calling process: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe ===
MSI (c) (58:00) [14:03:49:483]: Resetting cached policy values
MSI (c) (58:00) [14:03:49:483]: Machine policy value 'Debug' is 0
MSI (c) (58:00) [14:03:49:483]: ******* RunEngine:
******* Product: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Setup\SqlRun_Tools.msi
******* Action:
******* CommandLine: **********
MSI (c) (58:00) [14:03:49:483]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (58:00) [14:03:49:483]: Grabbed execution mutex.
MSI (c) (58:00) [14:03:49:483]: Cloaking enabled.
MSI (c) (58:00) [14:03:49:483]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (58:00) [14:03:49:483]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (D4:80) [14:03:49:499]: Grabbed execution mutex.
MSI (s) (D4:BC) [14:03:49:499]: Resetting cached policy values
MSI (s) (D4:BC) [14:03:49:499]: Machine policy value 'Debug' is 0
MSI (s) (D4:BC) [14:03:49:499]: ******* RunEngine:
******* Product: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Setup\SqlRun_Tools.msi
******* Action:
******* CommandLine: **********
MSI (s) (D4:BC) [14:03:49:499]: Note: 1: 2203 2: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Setup\SqlRun_Tools.msi 3: -2147287037
MSI (s) (D4:BC) [14:03:49:499]: MainEngineThread is returning 3
MSI (c) (58:00) [14:03:49:499]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (58:00) [14:03:49:499]: MainEngineThread is returning 3
=== Verbose logging stopped: 3/16/2006 14:03:49 ===

Thank you very much,

BJ

Did you get this solved? I don't think this is a known issue. Possibly it's a bad disk. If you're still blocked by this please either file a bug or post a link to your complete setup logs.

Thanks,

Paul

|||If you want to install only client components, start setup from disc 2. That should fix the problem. I saw this error message commented somewhere, it is even worse when you use unattended setup from CD1 for client components only.|||

I think there is a problem with the disc because I was able to install the Workstation Components from the Developer disc that came with VS .NET 2005 on the same machines. I guess we will need to send them back for new discs.

Thanks!

BJ

|||We also ran into this problem with our Visual Studio 2005 CDs. The statement that you can run the set-up from the second CD only doesn't resolve the problem either. I will have to contact Microsoft regarding this problem though. I haven't been able to prevent this from occurring as of yet.|||

I also got this error. This is how I was able to complete the installation.

I just restarted installation using disk 1 and selected only workstation components to install. It asked for disk 2 and the it completed the installation. At the end of the installation again I got that error popped up but it's ok the SQL Server installation is fine and complete.

cool - Ashok Ojha

|||I also got this problem and solved installing the Client Components from the second cd