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 server 2005 setup on win2k sp4

error msg in summary.txt

Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows 2000 Server Service Pack 4 (Build 2195)
Time : Wed Feb 14 03:31:27 2007
LDINTSQL1 : There was an unexpected failure during the setup wizard. You may review the setup logs and/or click the help button for more information.

SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.

Time : Wed Feb 14 03:39:30 2007

List of log files:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0008_LDINTSQL1_Core.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0008_LDINTSQL1_Datastore.xml
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0008_LDINTSQL1_.NET Framework 2.0.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0008_LDINTSQL1_.NET Framework 2.0 LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0008_LDINTSQL1_.NET Framework Upgrade Advisor.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0008_LDINTSQL1_.NET Framework Upgrade Advisor LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0008_LDINTSQL1_.NET Framework Windows Installer.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0008_LDINTSQL1_.NET Framework Windows Installer LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0008_LDINTSQL1_SNAC.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0008_LDINTSQL1_Support.log

error msg in C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0008_LDINTSQL1_Core.log

Microsoft SQL Server 2005 Setup beginning at Wed Feb 14 03:31:27 2007
Process ID : 2176
\\ldnas1\msdn versions\Server Applications\SQL Server 2005 std\Servers\setup.exe Version: 2005.90.1399.0
Running: LoadResourcesAction at: 2007/1/14 3:31:27
Complete: LoadResourcesAction at: 2007/1/14 3:31:27, returned true
Running: ParseBootstrapOptionsAction at: 2007/1/14 3:31:27
Loaded DLL:\\ldnas1\msdn versions\Server Applications\SQL Server 2005 std\Servers\xmlrw.dll Version:2.0.3604.0
Complete: ParseBootstrapOptionsAction at: 2007/1/14 3:31:27, returned true
Running: ValidateWinNTAction at: 2007/1/14 3:31:27
Complete: ValidateWinNTAction at: 2007/1/14 3:31:27, returned true
Running: ValidateMinOSAction at: 2007/1/14 3:31:27
Complete: ValidateMinOSAction at: 2007/1/14 3:31:27, returned true
Running: PerformSCCAction at: 2007/1/14 3:31:27
Complete: PerformSCCAction at: 2007/1/14 3:31:27, returned true
Running: ActivateLoggingAction at: 2007/1/14 3:31:27
Complete: ActivateLoggingAction at: 2007/1/14 3:31:27, returned true
Delay load of action "DetectPatchedBootstrapAction" returned nothing. No action will occur as a result.
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__2176" returned false.
Running: PerformSCCAction2 at: 2007/1/14 3:31:27
Loaded DLL:C:\WINNT\system32\msi.dll Version:3.1.4000.2435
Loaded DLL:C:\WINNT\system32\msi.dll Version:3.1.4000.2435
Complete: PerformSCCAction2 at: 2007/1/14 3:31:27, returned true
Running: PerformDotNetCheck at: 2007/1/14 3:31:27
Complete: PerformDotNetCheck at: 2007/1/14 3:31:27, returned true
Running: ComponentUpdateAction at: 2007/1/14 3:31:27
Complete: ComponentUpdateAction at: 2007/1/14 3:31:54, returned true
Delay load of action "DetectLocalBootstrapAction" returned nothing. No action will occur as a result.
Action "LaunchLocalBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchLocalBootstrap__2176" returned false.
Running: PerformDotNetCheck2 at: 2007/1/14 3:31:54
Complete: PerformDotNetCheck2 at: 2007/1/14 3:31:54, returned true
Running: InvokeSqlSetupDllAction at: 2007/1/14 3:31:54
Error: Action "InvokeSqlSetupDllAction" threw an exception during execution.
Failed to determine path to bootstrap files : 2
Error Code: 0x80070002 (2)
Windows Error Text: The system cannot find the file specified.

Source File Name: setup\sqlsetupactions.cpp
Compiler Timestamp: Thu Sep 1 22:23:04 2005
Function Name: sqls::InvokeSqlSetupDllAction::perform
Source Line Number: 1663

any ideas?

thanks

Does your server have MDAC 2.8 SP1 installed (It is a pre-req for SQL Server 2005 setup)? To see the version of MDAC installed, you can do the following.

1. Start ->Run and type "regedit".

2. In the registry tree in the left panel, drill down to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DataAccess\Version. The version key should have "2.81.1117.0".

If MDAC version on the machine is less than 2.8 SP1, then you should go to download center and installing Mdac 2.8 sp1 redist from there.

If you have Mdac 2.8 sp1 installed, then can you provide the following info?

1. Are you an admin on the box?

2. What is the OS language although it shouldn't matter.

3. What is the language of SQL Server 2005 you are installing?

4. How are you installing it: Double-clicking setup.exe or through command line parameters passed to setup.exe?

5. Have you done previous installs of SQL Server 2005 on the machine?

6. Is the SQL Server 2005 you are installing an RTM release, if so which SKU?

---

This posting is provided "AS IS" with no warranties, and confers no rights.

Error in Sql Server 2000 sp4

I′ve got a problem with SQL server. The server stops responding and gives me
out an error below.
Anyone can help me. When it runs this select in the database the server
keeps with 80% 100% processor up and stops responding all client requests.
Memory
MemoryLoad = 94%
Total Physical = 2047 MB
Available Physical = 116 MB
Total Page File = 8041 MB
Available Page File = 6246 MB
Total Virtual = 2047 MB
Available Virtual = 281 MB
*Stack Dump being sent to E:\Microsoft SQL Server\MSSQL\log\SQLDump0009.txt
*
************************************************** ***************************
**
*
* BEGIN STACK DUMP:
* 02/23/07 10:17:59 spid 89
*
* Exception Address = 00402836
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred writing address 00000004
* Input Buffer 82 bytes -
* SELECT * from ProdutosParaSiteWeb_ANALISE
Luis,
Is ProdutosParaSiteWeb_ANALISE a view? If so, examine the code for the view
for complexity. Maybe you have uncovered a SQL Server bug, but recrafting
the code could work around the problem.
If ProdutosParaSiteWeb_ANALISE is a table, or the view is very simple, then
you might be concerned with database integrity. Run as DBCC CHECKDB and see
if it reveals any errors.
RLF
"Luis" <Luis@.discussions.microsoft.com> wrote in message
news:D1CA43FA-34B2-4A2A-8D83-529913BB66AB@.microsoft.com...
> Ive got a problem with SQL server. The server stops responding and gives
> me
> out an error below.
> Anyone can help me. When it runs this select in the database the server
> keeps with 80% 100% processor up and stops responding all client requests.
> Memory
> MemoryLoad = 94%
> Total Physical = 2047 MB
> Available Physical = 116 MB
> Total Page File = 8041 MB
> Available Page File = 6246 MB
> Total Virtual = 2047 MB
> Available Virtual = 281 MB
> *Stack Dump being sent to E:\Microsoft SQL
> Server\MSSQL\log\SQLDump0009.txt
> *
> ************************************************** ***************************
> **
> *
> * BEGIN STACK DUMP:
> * 02/23/07 10:17:59 spid 89
> *
> * Exception Address = 00402836
> * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> * Access Violation occurred writing address 00000004
> * Input Buffer 82 bytes -
> * SELECT * from ProdutosParaSiteWeb_ANALISE
>

Error in Sql Server 2000 sp4

I′ve got a problem with SQL server. The server stops responding and gives m
e
out an error below.
Anyone can help me. When it runs this select in the database the server
keeps with 80% 100% processor up and stops responding all client requests.
Memory
MemoryLoad = 94%
Total Physical = 2047 MB
Available Physical = 116 MB
Total Page File = 8041 MB
Available Page File = 6246 MB
Total Virtual = 2047 MB
Available Virtual = 281 MB
*Stack Dump being sent to E:\Microsoft SQL Server\MSSQL\log\SQLDump0009.txt
*
****************************************
************************************
*
**
*
* BEGIN STACK DUMP:
* 02/23/07 10:17:59 spid 89
*
* Exception Address = 00402836
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred writing address 00000004
* Input Buffer 82 bytes -
* SELECT * from ProdutosParaSiteWeb_ANALISELuis,
Is ProdutosParaSiteWeb_ANALISE a view? If so, examine the code for the view
for complexity. Maybe you have uncovered a SQL Server bug, but recrafting
the code could work around the problem.
If ProdutosParaSiteWeb_ANALISE is a table, or the view is very simple, then
you might be concerned with database integrity. Run as DBCC CHECKDB and see
if it reveals any errors.
RLF
"Luis" <Luis@.discussions.microsoft.com> wrote in message
news:D1CA43FA-34B2-4A2A-8D83-529913BB66AB@.microsoft.com...
> Ive got a problem with SQL server. The server stops responding and gives
> me
> out an error below.
> Anyone can help me. When it runs this select in the database the server
> keeps with 80% 100% processor up and stops responding all client requests.
> Memory
> MemoryLoad = 94%
> Total Physical = 2047 MB
> Available Physical = 116 MB
> Total Page File = 8041 MB
> Available Page File = 6246 MB
> Total Virtual = 2047 MB
> Available Virtual = 281 MB
> *Stack Dump being sent to E:\Microsoft SQL
> Server\MSSQL\log\SQLDump0009.txt
> *
> ****************************************
**********************************
***
> **
> *
> * BEGIN STACK DUMP:
> * 02/23/07 10:17:59 spid 89
> *
> * Exception Address = 00402836
> * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> * Access Violation occurred writing address 00000004
> * Input Buffer 82 bytes -
> * SELECT * from ProdutosParaSiteWeb_ANALISE
>

Error in Sql Server 2000 sp4

I´ve got a problem with SQL server. The server stops responding and gives me
out an error below.
Anyone can help me. When it runs this select in the database the server
keeps with 80% 100% processor up and stops responding all client requests.
Memory
MemoryLoad = 94%
Total Physical = 2047 MB
Available Physical = 116 MB
Total Page File = 8041 MB
Available Page File = 6246 MB
Total Virtual = 2047 MB
Available Virtual = 281 MB
*Stack Dump being sent to E:\Microsoft SQL Server\MSSQL\log\SQLDump0009.txt
*
*****************************************************************************
**
*
* BEGIN STACK DUMP:
* 02/23/07 10:17:59 spid 89
*
* Exception Address = 00402836
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred writing address 00000004
* Input Buffer 82 bytes -
* SELECT * from ProdutosParaSiteWeb_ANALISELuis,
Is ProdutosParaSiteWeb_ANALISE a view? If so, examine the code for the view
for complexity. Maybe you have uncovered a SQL Server bug, but recrafting
the code could work around the problem.
If ProdutosParaSiteWeb_ANALISE is a table, or the view is very simple, then
you might be concerned with database integrity. Run as DBCC CHECKDB and see
if it reveals any errors.
RLF
"Luis" <Luis@.discussions.microsoft.com> wrote in message
news:D1CA43FA-34B2-4A2A-8D83-529913BB66AB@.microsoft.com...
> I´ve got a problem with SQL server. The server stops responding and gives
> me
> out an error below.
> Anyone can help me. When it runs this select in the database the server
> keeps with 80% 100% processor up and stops responding all client requests.
> Memory
> MemoryLoad = 94%
> Total Physical = 2047 MB
> Available Physical = 116 MB
> Total Page File = 8041 MB
> Available Page File = 6246 MB
> Total Virtual = 2047 MB
> Available Virtual = 281 MB
> *Stack Dump being sent to E:\Microsoft SQL
> Server\MSSQL\log\SQLDump0009.txt
> *
> *****************************************************************************
> **
> *
> * BEGIN STACK DUMP:
> * 02/23/07 10:17:59 spid 89
> *
> * Exception Address = 00402836
> * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> * Access Violation occurred writing address 00000004
> * Input Buffer 82 bytes -
> * SELECT * from ProdutosParaSiteWeb_ANALISE
>

Error in Distribution Clean Up Agent

Server 1 SQL 2000 (SP4) Distributor, Publisher
Server 2 SQL 2000 (SP4) Subscriber
Transactional Replication set up between Server 1 and 2.
All the agents are running successfully (Log Reader, Snapshot, Other
Miscellenaous agent...except the Distribution Clean Up Agent
error
Executed as user: COOP\sqladmin. Could not remove directory
'\\ALXCONTGC\ReplData\unc\ALXCONTGC_sales_Pub_Alxo ffc_Anualtrans\20061119100406\'.
Check the security context of xp_cmdshell and close other processes
that may be accessing the directory. [SQLSTATE 42000] (Error 20015)
Replication-@.rowcount_only parameter must be the value 0,1, or 2. 0=7.0
compatible checksum. 1=only check rowcou: agent
distribution@.rowcount_only parameter must be the value 0,1, or 2. 0=7.0
compatible checksum. 1=only scheduled for retry. Could not clean up
the distribution transaction tables. [SQLSTATE 01000] (Message 14152).
The step failed.
?
can you make sure xp_cmdshell is enabled? Do this:
exec master.dbo.sp_configure 'xp_cmdshell'
If run value is 0, do this
exec master.dbo.sp_configure 'xp_cmdshell',1
reconfigure with override
Then start up your distribution clean up task.
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
"noda" <hend_g@.hotmail.com> wrote in message
news:1164102353.485024.276880@.j44g2000cwa.googlegr oups.com...
Server 1 SQL 2000 (SP4) Distributor, Publisher
Server 2 SQL 2000 (SP4) Subscriber
Transactional Replication set up between Server 1 and 2.
All the agents are running successfully (Log Reader, Snapshot, Other
Miscellenaous agent...except the Distribution Clean Up Agent
error
Executed as user: COOP\sqladmin. Could not remove directory
'\\ALXCONTGC\ReplData\unc\ALXCONTGC_sales_Pub_Alxo ffc_Anualtrans\20061119100406\'.
Check the security context of xp_cmdshell and close other processes
that may be accessing the directory. [SQLSTATE 42000] (Error 20015)
Replication-@.rowcount_only parameter must be the value 0,1, or 2. 0=7.0
compatible checksum. 1=only check rowcou: agent
distribution@.rowcount_only parameter must be the value 0,1, or 2. 0=7.0
compatible checksum. 1=only scheduled for retry. Could not clean up
the distribution transaction tables. [SQLSTATE 01000] (Message 14152).
The step failed.
?
|||Is your sql server agent running as an account that is in the sysadmin role?
If not it'll try to use the proxy account that might not have been
configured.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .