Creating MS SQL Server 2005 Analysis Services OLAP connection

Hello,
I am trying to add an OLAP data source in BI Publisher (which is part of the OBIEE 11.1.1.5.0 suite I have installed). However, the connection never seems to create - I don't get an error or a success message when I test the connection. However, if I cancel out of the create connection screen, I get this error: "Your request was denied as you have no permission to access the data.". This is odd since the credentials I am using have admin rights to the OLAP cube I am attempting to connect to.
SETUP
OBIEE 11.1.1.5.0 x86_64 bit Linux
MS SQL Server 2005 Analysis Services running on Windows Server Enterprise (32 bit) 2007 SP2
Windows users are able to connect to the Windows/SQL server via Excel 2007 and its built-in Analysis Services "Other Data Sources" option. Authentication is done via Windows Active Directory LDAP
QUESTIONS
1) In the BI Publisher connection screen, can I enter my AD username/password, or because I am connecting from a Linux Server, do I need to authenticate via a different method?
2) In the connection string, the initial catalog I am attempting to connect to has spaces in its name. Could this be an issue?
3) Given the "no permission to access data" message I am getting, is it possible I am reaching the SQL Server but need to set up a local database, non-AD account to access the OLAP catalog?
4) Are there any logs in the OBIEE server that I can check for more details?
Thanks!

Post Author: Sam Naghshineh
CA Forum: Olap
With the new productivity pack for Business Objects Enterprise XI R2 (Service Pack 2) you can access SSAS 2005 through the new OLAP tool called Voyager. The productivity pack is due out sometime in the next few weeks.
Hope this helps.

Similar Messages

BO XI R2 and SQL server 2005 Analysis services

Post Author: fasttrack
CA Forum: Olap
Hello,
I am new in BO, I am using XI R2 and I would like to know this:
I have to build some reports on Data Warehouse using SQL server 2005 Analysis Services.
My question is:
1) How I have to build this reports: directly to data warehouse or building an OLAP (CUBE) in analysis services 2005?
2) BO XI R2 supports SQL server 2005 and especially in this case Analysis services 2005 and provider (I have seen only provider for SQL Server 2000)?
Do you some good resources where to learn how to make reports on DW SQL server 2005?
Thank

Post Author: ShaunOberem
CA Forum: Olap
Hello,
I am new in BO, I am using XI R2 and I would like to know this:
I have to build some reports on Data Warehouse using SQL server 2005 Analysis Services.
My question is:
1) How I have to build this reports: directly to data warehouse or building an OLAP (CUBE) in analysis services 2005?
2) BO XI R2 supports SQL server 2005 and especially in this case Analysis services 2005 and provider (I have seen only provider for SQL Server 2000)?
Do you some good resources where to learn how to make reports on DW SQL server 2005?
Thank
Hi,
If you are trying to create a new OLAP Intelligence Report using SQL 05 I am afraid you are out of luck.
You will need to get a copy of the Productivity Pack (Available for Download in Subscribenet) .
Also, in your SQL Server Sufrace Configuraiton manager try setting Analysis Services to Allow Ananomous connections. This will make sure you get a little further initially. (Dont leave Anonymous on)

SQL Server 2005 Analysis Services across domains

Hi,
With SQL Server 2000, the Enterprise Edition was required to access
Analysis Services across domains.
Is this also the case in SQL Server 2005, that the Enterprise Edition
is needed?
Thanks, S

Silver,
Do you still need help with this?
Thank you!
Ed Price, Power BI & SQL Server Customer Program Manager (Blog,
Small Basic,
Wiki Ninjas,
Wiki)
Answer an interesting question?
Create a wiki article about it!

Microsoft OLE DB Provider for SQL Server 2012 Analysis Services Error Code = 0x80040E05

I've been running a package for 6 months without any issues that pulls data from a cube via MDX and moves it to a database.
We've recently moved to a new server x64 and the connections all succeed but at runtime (in 64 = T&F) I get the following error:
[SRC AdExchange [87]] Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E05.
An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server 2012 Analysis Services." Hresult: 0x00000001 Description: "Error Code = 0x80040E05, External Code = 0x00000000:.".
[SSIS.Pipeline] Error: SRC AdExchange failed the pre-execute phase and returned error code 0xC0202009.
I've installed SQL_AS_OLEDB, SQL_AS_ADOMD from Microsoft® SQL Server® 2012 SP1 Feature Pack
Why is my connection failing?

The server has a 10Gbps network connection.
I've installed CU6 for SQL Server 2012 SP1
http://support.microsoft.com/kb/2874879/en-us#hfi
I'm still getting the same error at runtime in BIDS:
[SRC AdExchange [87]] Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E05.
An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server 2012 Analysis Services." Hresult: 0x00000001 Description: "Error Code = 0x80040E05, External Code = 0x00000000:.".
[SSIS.Pipeline] Error: SRC AdExchange failed the pre-execute phase and returned error code 0xC0202009.
Looking at the errorlog, everything looks normal until:
Launched startup procedure 'sp_ssis_startup'.
Attempting to load library 'xpsqlbot.dll' into memory. This is an informational message only. No user action is required.
Using 'xpsqlbot.dll' version '2011.110.2100' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
Using 'xpstar.dll' version '2011.110.3000' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
Using 'xplog70.dll' version '2011.110.2100' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
AppDomain 2 (SSISDB.dbo[runtime].1) created.
Unsafe assembly 'microsoft.sqlserver.integrationservices.server, version=11.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil' loaded into appdomain 2 (SSISDB.dbo[runtime].1).
Unsafe assembly 'microsoft.sqlserver.integrationservices.server, version=11.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil' loaded into appdomain 2 (SSISDB.dbo[runtime].1).
AppDomain 3 (master.sys[runtime].2) created.
Software Usage Metrics is enabled.
SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.
Service Broker manager has shut down.
Error: 17054, Severity: 16, State: 1.
The current event was not reported to the Windows Events log. Operating system error = (null). You may need to clear the Windows Events log if it is full.
.NET Framework runtime has been stopped.
SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
The SQL Server Network Interface library could not deregister the Service Principal Name (SPN) [ MSSQLSvc/XXXXXXXXXX.com ] for the SQL Server service. Error: 0xffffffff, state: 63. Administrator should deregister this SPN manually to avoid client authentication
errors.
The SQL Server Network Interface library could not deregister the Service Principal Name (SPN) [ MSSQLSvc/XXXXXXXXXX.com:1433 ] for the SQL Server service. Error: 0xffffffff, state: 63. Administrator should deregister this SPN manually to avoid client authentication
errors.
Wondering about the unsafe assembly in SSIS and deregistering the SPN..
Anyone have any ideas on how to resolve this?
Thanks!

Is there a way to convert Crystal Reports to Microsoft SQL Server 2005 reporting services?

Post Author: Lourdes Hernandez
CA Forum: General
Our department has always worked with and we love Crystal Reports. Unfortunately, certain reports now need to be converted to Microsoft SQL Server 2005 reporting services which from what I read I think they are *.rdl reports. Does Crystal reports have any way around this? I would have to learn this other tool when I'm already so happy with Crystal. I was thinking If I could just code the report in crystal and export it in a specific format that would be compatible Microsoft, the problem would be solved.
Any ideas would be greatly appreciated.

Post Author: bettername
CA Forum: General
Ditto!
There are some software packages to convert from CR to RS, but none work 100% AFAIK, and will require manual tuning.
Seems like a big hassle and learning curve just to get reports published via another method - I know I'd put up huge resistance if they tried to take my CR away from me!

SQL Server 2008 Analysis Services and OBI EE

Hello,
How to use the Multidimensional import functionality of the BI EE Administration against a cube stored in a SQL Server 2008 Analysis Services?
Thanks,
Paul

Thanks Christian,
The article you mention takes for granted that a valid Analysis Services XMLA URL is present, which is not my case.
I have found a good article on how to configure specifically Analysis Services 2008 here:
http://bloggingabout.net/blogs/mglaser/archive/2008/08/15/configuring-http-access-to-sql-server-2008-analysis-services-on-microsoft-windows-server-2008.aspx
The article is the nearest I could find from my particular software platform (Vista).
What I'm currently dealing with is [nQSError: 64203] "XMLAnalysisError.0xc1010000", which is probably some security setting I have to get right. I will keep the thread updated if I move on.
Thanks,
Paul

SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server 2012 Analysis Services." Hresult: 0x80004005 Description: "Internal error: An une

SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server 2012 Analysis Services." Hresult: 0x80004005
Description: "Internal error: An unexpected error occurred (file 'pcxmlacommon.cpp', line 43, function 'PCFault::RaiseError').
I'm getting above error in the pre- execute phase of a DFT when I'm trying to fetch data from a SSAS cube using mdx query.
I'm using OLE DB provider for connecting to cube.
I got one resolution for Error Code 0X8004005, which asked me to add 'Format= Tabular' in cube's connection string. It does not seem to work either. Can any one help me out on this???

You are probably missing an update.
I saw a MS Connect post https://connect.microsoft.com/SQLServer/feedback/details/250920/error-using-oledb-or-datareader-to-get-analysis-services-data where that suggestion was proposed as a fix, but is for an older SQL Server version.
So do there is a question if you pull data from SQL Server 2012 SSAS using SSIS 2012 (so no other build is involved).
Arthur My Blog

How to present SAP R/3 data in SQL Server 2005 Reporting service?

Our company is using SharePoint Portal Server 2003 as our intranet. We are also using SAP R/3 4.6C to run their business. There are huge amount of important data in SAP database. There ere are business needs to present SAP data on SharePoint pages which are easier and more friendly to be accessed by users.
The top concern for IT people to meet this challenge is DO NOT CHANGE/UPGRADE THE EXISTING SAP SYSTEM which is so far run smoothly and stably. We cannot accept any risk to make big changes on SAP. and now we want to adopt the Microsoft SQLServer 2005 BI Solution. the most challenge is the ETL part.how to extract the data from SAP R/3 Data base to the SQL Server Data warehouse?
any suggestion or comments is welcome!

Hi
1.if you use web templates you can post the URL in share
point very easily.
any web developer will do that for you in 2 min.
2.this is a more chalanging issue.
the main issue is exacly as you defined it - the ETL.
the main advantage of BW over most BI tools is its
connectivity to SAP R3 and CRM.
But still there are many way's to extract data out
of any SAP sys and in R3 the data model makes it quite
easy.
In CRM its much more complicated because of the much
more complex Data Model.
Here are a few way's to extract data from SAP:
- olap bapi
http://help.sap.com/saphelp_bw33/helpdata/en/64/9b8f3c855f0454e10000000a11405a/frameset.htm
- odbo - vb/.net/c sharp
'connecting to sap bw using vb and ado md'
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ee19e9c7-0301-0010-8f84-97e3f6d7b5a6
'connecting to sap bw with excel and odbo'
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a06a51f3-0201-0010-8591-b742cfafd267
'odbo'
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/7f88b390-0201-0010-ae94-fdfd42b13407
'sap .net connector' (seems old version)
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/fb4dc990-0201-0010-429a-bf43852a6895
.net connector
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5a04426d-0601-0010-5e99-aeea1cd4aa81
'Access SAP BW ODS BAPI Using C-Sharp and SAP .NET Connector 2.0' doc can be download here
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/12f6d390-0201-0010-e18d-cdb4554a9e75
Reg's
Edan

Sql server 2005 reporting service access in java

Hello Friends,
I want to access Sql Server Reporting service in Java.If anybody knows than please help.
Thanking You

Hi
1.if you use web templates you can post the URL in share
point very easily.
any web developer will do that for you in 2 min.
2.this is a more chalanging issue.
the main issue is exacly as you defined it - the ETL.
the main advantage of BW over most BI tools is its
connectivity to SAP R3 and CRM.
But still there are many way's to extract data out
of any SAP sys and in R3 the data model makes it quite
easy.
In CRM its much more complicated because of the much
more complex Data Model.
Here are a few way's to extract data from SAP:
- olap bapi
http://help.sap.com/saphelp_bw33/helpdata/en/64/9b8f3c855f0454e10000000a11405a/frameset.htm
- odbo - vb/.net/c sharp
'connecting to sap bw using vb and ado md'
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ee19e9c7-0301-0010-8f84-97e3f6d7b5a6
'connecting to sap bw with excel and odbo'
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a06a51f3-0201-0010-8591-b742cfafd267
'odbo'
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/7f88b390-0201-0010-ae94-fdfd42b13407
'sap .net connector' (seems old version)
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/fb4dc990-0201-0010-429a-bf43852a6895
.net connector
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5a04426d-0601-0010-5e99-aeea1cd4aa81
'Access SAP BW ODS BAPI Using C-Sharp and SAP .NET Connector 2.0' doc can be download here
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/12f6d390-0201-0010-e18d-cdb4554a9e75
Reg's
Edan

SQL Server 2012 Analysis Services Deployment Wizard broken after SP1

I have installed SQL Server 2012 SP1, now I cannot edit Data Source Connection Strings anymore in the Deployment Wizard.
When clicking the button labeled "..." I get an error "Could not load file or assembly 'Microsoft.Data.ConnectionUI, Version=8.0.0.0' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference".
This happened on two different 2008 R2 servers and local windows 7 desktop, SP1 Cumulative Update 1 does not fix the error.
Please help!

I managed to fix it by modifying the Workaround from Microsoft a bit.
Microsoft Fix: https://support.microsoft.com/en-us/kb/2809127/
Summary of fix:
Open the following configuration file in a text editor, such as Notepad, as an administrator:
<var class="sbody-var" style="box-sizing:border-box;"><system drive>:</var>\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\Microsoft.AnalysisServices.Deployment.exe.config
2. Insert the runtime XML tags after the </startup> tag in the configuration section:<configuration>
<startup>
<requiredRuntime version="v4.0.30319" safemode="true" />
</startup>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="Microsoft.Data.ConnectionUI" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
<bindingRedirect oldVersion="8.0.0.0-9.0.0.0" newVersion="10.0.0.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="Microsoft.Data.ConnectionUI.Dialog" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
<bindingRedirect oldVersion="8.0.0.0-9.0.0.0" newVersion="10.0.0.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>
</configuration>
What i did to make it work:
<configuration>
<startup>
<requiredRuntime version="v4.0.30319" safemode="true" />
</startup>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="Microsoft.Data.ConnectionUI" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
<bindingRedirect oldVersion="10.0.0.0" newVersion="8.0.0.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="Microsoft.Data.ConnectionUI.Dialog" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
<bindingRedirect oldVersion="10.0.0.0" newVersion="8.0.0.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>
</configuration>
Instead of redirecting from version 8 and 9 to 10, i reverted it and made sure it uses version 8.

SQL Server 2005 Dev Integration Services Fail

I've got VS2005 v.8.0.50727.867 (vsvista.050727-8600) on my 64bit Windows 7 box. I am trying to install SQL Server 2005 Integration Services on this Win7 box so I can load and edit the Win XP SSIS projects that I had on my XP box. So far I've
not been able to successfully install the Integration Services with a failed permission on the SQL**DTD.msi file.....I've copied this file locally and tried to run it and it would start but then would give permission error.
Is there an inherent incompatibility running SSIS projects in SQL Server 2005 on a 64bit Win 7 box? Worked great on my XP box.
I've been "upgrading" the SSIS projects to VS2008 since I was able to get SSIS installed. Any ideas what I need to do to get this beast to work?
TIA
Harry

Thanks Alberto
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version      : Professional Service Pack 1 (Build 7601)
Time            : Mon Aug 25 09:31:30 2014
DT0315 : Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features. Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features,
install IIS from Add or Remove Programs in Control Panel or enable the IIS service through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL
Server in Books Online.
DT0315 : Failed to find the ASP.Net Version Registration with Microsoft Internet Information Services (IIS).
Machine         : DT0315
Product         : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLSupport_1.log
Machine         : DT0315
Product         : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_1.log
Machine         : DT0315
Product         : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_1.log
Machine         : DT0315
Product         : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLSupport_2.log
Machine         : DT0315
Product         : Microsoft SQL Server Native Client
Product Version : 9.00.5000.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLNCLI_1.log
Machine         : DT0315
Product         : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_2.log
Machine         : DT0315
Product         : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_2.log
Machine         : DT0315
Product         : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLSupport_3.log
Machine         : DT0315
Product         : Microsoft SQL Server Native Client
Product Version : 9.00.5000.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLNCLI_2.log
Machine         : DT0315
Product         : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_3.log
Machine         : DT0315
Product         : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_3.log
Machine         : DT0315
Product         : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLSupport_4.log
Machine         : DT0315
Product         : Microsoft SQL Server Native Client
Product Version : 9.00.5000.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLNCLI_3.log
Machine         : DT0315
Product         : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_4.log
Machine         : DT0315
Product         : Microsoft VSS Writer for SQL Server 2012
Product Version : 11.0.2100.60
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SqlWriter_1.log
Machine         : DT0315
Product         : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_4.log
Machine         : DT0315
Product         : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLSupport_5.log
Machine         : DT0315
Product         : Microsoft SQL Server Native Client
Product Version : 9.00.5000.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLNCLI_4.log
Machine         : DT0315
Product         : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_5.log
Machine         : DT0315
Product         : Microsoft SQL Server 2005 Books Online (English)
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BOL_1.log
Machine         : DT0315
Product         : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_5.log
Machine         : DT0315
Product         : Integration Services
Error           : Failed to install and configure assemblies C:\Program Files\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog. Error: -2146233087
Error message: Unknown error 0x80131501
Error description: One or more of the components being installed are already registered as 32 bit components in the target application. You must install the 64 bit versions of the components being installed in a different COM+ application, or delete the existing
32 bit versions of the components being installed from the target COM+ application prior to attempting install of the 64 bit versions. COM+ applications cannot contain bit neutral components.
Machine         : DT0315
Product         : Microsoft SQL Server 2005 Integration Services (64-bit)
Product Version : 9.00.1399.06
Install         : Failed
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_DTS.log
Last Action     : InstallFinalize
Error String    : Failed to install and configure assemblies C:\Program Files\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog. Error: -2146233087
Error message: Unknown error 0x80131501
Error description: One or more of the components being installed are already registered as 32 bit components in the target application. You must install the 64 bit versions of the components being installed in a different COM+ application, or delete the existing
32 bit versions of the components being installed from the target COM+ application prior to attempting install of the 64 bit versions. COM+ applications cannot contain bit neutral components.
Error Number    : 29549
Machine         : DT0315
Product         : SQLXML4
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLXML4_1.log
Machine         : DT0315
Product         : Microsoft SQL Server 2005 (64-bit)
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQL.log
Machine         : DT0315
Product         : SQLXML4
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLXML4_2.log
Machine         : DT0315
Product         : Microsoft SQL Server 2005 Analysis Services (64-bit)
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_AS.log
Machine         : DT0315
Product         : Microsoft SQL Server 2005 Notification Services (64-bit)
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_NS.log
Machine         : DT0315
Product         : Microsoft SQL Server 2005 Tools (64-bit)
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_Tools.log
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.

SQL Server 2005 SSAS connect to BI possible?

Hi there,
I have tested the new .Net Data Provider 1.0 for SAP Netweaver BI in SQL Server Reporting Service (SSRS). What I am wondering is that could SQL Server Analysis Service (SSAS) connect to SAP BI, too? How to do this?
Best Regardly

Dear Tom,
You can use Microsoft SQL Server 2005 Integration Services (SSIS) for this connection or through XML for Analysis (XML/A) (an XML standard for Online Analytical Processing - OLAP) it can be done. But I am not sure weather this service is available or not as SQL Server 2005 Reporting Services, which is now certified to run reports on SAP BW.
As I have never ventured in this, I would suggest you to use documentations of Microsoft SQL Server 2005 Integration Services (SSIS) and SSAS given by MS.
Also have a look at this doc:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/4ab89e84-0d01-0010-cda2-82ddc3548c65
Hope it helps.
Regards,
Ashish

PeopleTools 8.49 PeopleSoft Database Cannot Connect with MS SQL Server 2005

Folks,
Hello. I am working on PeopleSoft PIA. My system is Windows Server 2003, MS SQL Server Express 2005 Standard, PeopleTools 8.49. I am setting up PeopleSoft Database \PsMpDbInstall\setup.exe and got the errors as follows:
Error: Setup fails to connect to SQL Server. The default settings SQL Server does not allow remote connection.
Then I type in "sqlcmd" in Command Prompt and got the same error as follows:
Name Pipe Provider: Could not open a connection to SQL Server. MS SQL Native Client: the default settings SQL Server does not allow remote connection.
In order to fix SQL Server 2005 remote connection problem, I have done the 3 steps as follows:
Step 1: In SQL Server Surface Area Connection, enable local and remote connection, TCP/IP and Name Pipes, SQL Server browser Startup type "automatic" and status "running".
Step 2: Create exception for SQL Server 2005 and SQL Server browser Service in Windows Firewall.
Step 3: Add the default SQL Server Port 1433 into Windows Firewall.
But the above 3 steps cannot resolve SQL Server Express 2005 remote connection problem. Can any folks help to resolve this problem ?
Thanks.

Folks,
Management Studio can connect with SQL Server 2005 successfully.
I have turned off Windows Server 2003 firewall completely. But "sqlcmd" in Command Prompt still connect with SQL Server 2005 because its remote connection is not allowed.
Is the "not allow remote connection" problem caused by Windows Firewall or SQL Server 2005 itself ?
Thanks.

OraOledb, Linked Servers and SQL Server 2005 issues

Some issues I've come across when using SQL Server 2005 (and SQL Server Express 2005), the OraOLEDB provider (10.2.0.1) and a linked Oracle database (8.1.7.4.0 64-bit)
1) You must set the OraOledb.Oracle\AllowInProcess value to 1 to allow the OraOledb provider to run in SQL Server's process. Without doing this I receive an 'unspecified error' from the OLE DB provider when attempting to run a query
2) When running a ' select * ' query across a linked server using the provider, I receive the following error: Msg 9803, Level 16, State 1, Line 1
Invalid data for type "numeric". I can, however, select all of the columns by name and the query completes (no error). Sometimes the 'select *' query returns a few rows before the error, sometimes it doesn't. The Microsoft Provider for Oracle does not have this problem

Okay... I've got a Win2K3 Std Ed server (x64) running 64-bit SQL Server 2005 Enterprise Edition. I've installed the Oracle 10g 10.2.1 full client and admin tools, added two named services via the NetConfig assistant, and successfully set up (and tested) a connection via the ODBC Administrator to an Oracle database.
Now... when I try to create a new connection manager in SQL Server 2005 Integration Services, the OLEDB provider for Oracle can't be found, and when I try to manually add an underlying OLEDB connection to the database, SQL Server reports:
Test connection failed because of an error in initializing provider. The 'OraOLEDB.Oracle.1' provider is not registered on the local machine.
Does anyone know what I need to do to see my ODBC Server data connections in SQL Server 2005 (64 bit)? I don't have this issue on my 32-bit SQL Server 2005 servers.

Installation of ODI with SQL Server 2005

Hi
I am trying to install ODI with MS Sql Server 2005.
I created a database in Sql Server & created a user with db_owner rights for logging into the database.
While trying to install Master Repository, i selected Sql Server with following details
Driver: com.microsoft.jdbc.sqlserver.SQLServerDriver
URL: jdbc:microsoft:sqlserver://<myhostname>:1433;SelectMethod=cursor
The repository does not get created giving error:
*com.sunopsis.core.q: java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter 1 (""): Data type 0x38 is unknown*
Now if i change the URL to jdbc:microsoft:sqlserver://<myhostname>:1433, the repository gets created successfully. But at the time of login into the topology manager using the same Master repository, it again prompts me the same error.
Has anyone faced the same issue?

Hi,
You are using SQL server 2005 but trying to connect using the SQL server 2000 connection details you should be using
com.microsoft.sqlserver.jdbc.SQLServerDriver
jdbc:sqlserver://ServerName:1433;databaseName=DBNAME;SelectMethod=cursor
You will also need to make sure you are using the correct SQL server 2005 driver, if you are using a version of Java before 1.5 for ODI then you will need the SQL Server 2005 1.2 JDBC driver.
Cheers
John
http://john-goodwin.blogspot.com/

Creating MS SQL Server 2005 Analysis Services OLAP connection

Similar Messages

Maybe you are looking for