new SSRS install, works great until I try to access Oracle datasource - System.Data.Oracle

re: new SSRS install, works great until I try to access Oracle
datasource - System.Data.OracleClient requires Oracle client software
>From my desktop the report accessing an Oracle 9i db with no problem.
I've deployed other reports accesing sql server with no problem.
Now I deploy the report and try to access my Oracle source and get:
System.Data.OracleClient requires Oracle client software version 8.1.7
or greater
On the server in question, I know they've installed the oracle client.
I can access the db from sql plus with no problem.
As the user that I access ssrs credentials, i remote login and am able
to write to oracle home.. C:\oracle\ora10g\NETWORK\ADMIN
i've confirmed my database is in tnsnames and it works from sqlplus.On Nov 5, 3:27 pm, jobs <j...@.webdos.com> wrote:
> re: new SSRS install, works great until I try to access Oracle
> datasource - System.Data.OracleClient requires Oracle client software
> >From my desktop the report accessing an Oracle 9i db with no problem.
> I've deployed other reports accesing sql server with no problem.
> Now I deploy the report and try to access my Oracle source and get:
> System.Data.OracleClient requires Oracle client software version 8.1.7
> or greater
> On the server in question, I know they've installed the oracle client.
> I can access the db from sql plus with no problem.
> As the user that I access ssrs credentials, i remote login and am abl
> to write to oracle home.. C:\oracle\ora10g\NETWORK\ADMIN
> i've confirmed my database is in tnsnames and it works from sqlplus.
This is just a guess; but, have you checked for all necessary assembly
references from the Oracle-side. I would start with maybe getting a
comparison tool (possibly 30-day trial version of Merge 2007:
http://www.araxis.com/ ) and compare the directory structure of your
machine versus the machine where the report is deployed (in reference
to Oracle 8.1.7). Also, you might want to check into the driver for
the SSRS connection to Oracle. Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||If you have the Oracle client installed on the server I think the issue is
that the directory it is installed in is not accessible to RS. I googled
this a little (oracle client reporting services permissions)
http://technet.microsoft.com/en-us/library/ms159689.aspx
a.. (Optional) Install Oracle client tools on the report server if your
reports use the Microsoft .NET Framework Data Provider for Oracle. After you
install the client tools, you must restart IIS. To support subscriptions to
reports that use Oracle data sources, you must grant permissions to the
NetworkService account. For more information, see
http://support.microsoft.com/kb/870668.
http://support.microsoft.com/kb/870668
To work around this problem, add permissions for the NETWORK SERVICE
security principal to the Oracle\Oracle version\bin directory and to the
Oracle\Oracle version\network\admin directory. To do this, follow these
steps. ...
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"jobs" <jobs@.webdos.com> wrote in message
news:1194298047.081192.142180@.o3g2000hsb.googlegroups.com...
> re: new SSRS install, works great until I try to access Oracle
> datasource - System.Data.OracleClient requires Oracle client software
>
>>From my desktop the report accessing an Oracle 9i db with no problem.
> I've deployed other reports accesing sql server with no problem.
> Now I deploy the report and try to access my Oracle source and get:
> System.Data.OracleClient requires Oracle client software version 8.1.7
> or greater
> On the server in question, I know they've installed the oracle client.
> I can access the db from sql plus with no problem.
> As the user that I access ssrs credentials, i remote login and am able
> to write to oracle home.. C:\oracle\ora10g\NETWORK\ADMIN
> i've confirmed my database is in tnsnames and it works from sqlplus.
>

New SP2 Client Install Failure

Hi,
I have successfully upgraded a server with both the new SP2 and the 3050
hotfix. I am now trying to do this to my client workstation. It selected the
following components on my SQL2005 SP1 client to upgrade.
Setup Support Files
SQL Server Native Client
Client Components
MSXML 6.0 Parser
SQLXML4
Backward Compatibility
The client component upgrade failed on
Microsoft.sqlserver.notificationservices.dll. I had an error code 1603 and
this in the hotfix.log
MSP Error: 29549 Failed to install and configure assemblies c:\Program
Files\Microsoft SQL
Server\90\NotificationServices\9.0.242\Bin\microso ft.sqlserver.notificationservices.dll
in the COM+ catalog. Error: -2146233087
Error message: Unknown error 0x80131501
Error description: The Transaction Manager is not available. (Exception from
HRESULT: 0x8004D01B)
Any ideas?
Thanks
Chris
I found the answer on Connect. You need to have DTC running for the update
to finish.
Chris
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:evoMCLaYHHA.2556@.TK2MSFTNGP02.phx.gbl...
> Hi,
> I have successfully upgraded a server with both the new SP2 and the 3050
> hotfix. I am now trying to do this to my client workstation. It selected
> the following components on my SQL2005 SP1 client to upgrade.
> Setup Support Files
> SQL Server Native Client
> Client Components
> MSXML 6.0 Parser
> SQLXML4
> Backward Compatibility
> The client component upgrade failed on
> Microsoft.sqlserver.notificationservices.dll. I had an error code 1603 and
> this in the hotfix.log
> MSP Error: 29549 Failed to install and configure assemblies c:\Program
> Files\Microsoft SQL
> Server\90\NotificationServices\9.0.242\Bin\microso ft.sqlserver.notificationservices.dll
> in the COM+ catalog. Error: -2146233087
> Error message: Unknown error 0x80131501
> Error description: The Transaction Manager is not available. (Exception
> from HRESULT: 0x8004D01B)
> Any ideas?
> Thanks
> Chris
>
|||Try starting MSDTC if it's not already started and double check your event
logs for any COM+ errors.
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:evoMCLaYHHA.2556@.TK2MSFTNGP02.phx.gbl...
> Hi,
> I have successfully upgraded a server with both the new SP2 and the 3050
> hotfix. I am now trying to do this to my client workstation. It selected
> the following components on my SQL2005 SP1 client to upgrade.
> Setup Support Files
> SQL Server Native Client
> Client Components
> MSXML 6.0 Parser
> SQLXML4
> Backward Compatibility
> The client component upgrade failed on
> Microsoft.sqlserver.notificationservices.dll. I had an error code 1603 and
> this in the hotfix.log
> MSP Error: 29549 Failed to install and configure assemblies c:\Program
> Files\Microsoft SQL
> Server\90\NotificationServices\9.0.242\Bin\microso ft.sqlserver.notificationservices.dll
> in the COM+ catalog. Error: -2146233087
> Error message: Unknown error 0x80131501
> Error description: The Transaction Manager is not available. (Exception
> from HRESULT: 0x8004D01B)
> Any ideas?
> Thanks
> Chris
>

New SP2 Client Install Failure

Hi,
I have successfully upgraded a server with both the new SP2 and the 3050
hotfix. I am now trying to do this to my client workstation. It selected the
following components on my SQL2005 SP1 client to upgrade.
Setup Support Files
SQL Server Native Client
Client Components
MSXML 6.0 Parser
SQLXML4
Backward Compatibility
The client component upgrade failed on
Microsoft.sqlserver.notificationservices.dll. I had an error code 1603 and
this in the hotfix.log
MSP Error: 29549 Failed to install and configure assemblies c:\Program
Files\Microsoft SQL
Server\90\NotificationServices\9.0.242\Bin\microsoft.sqlserver.notificationservices.dll
in the COM+ catalog. Error: -2146233087
Error message: Unknown error 0x80131501
Error description: The Transaction Manager is not available. (Exception from
HRESULT: 0x8004D01B)
Any ideas?
Thanks
ChrisI found the answer on Connect. You need to have DTC running for the update
to finish.
Chris
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:evoMCLaYHHA.2556@.TK2MSFTNGP02.phx.gbl...
> Hi,
> I have successfully upgraded a server with both the new SP2 and the 3050
> hotfix. I am now trying to do this to my client workstation. It selected
> the following components on my SQL2005 SP1 client to upgrade.
> Setup Support Files
> SQL Server Native Client
> Client Components
> MSXML 6.0 Parser
> SQLXML4
> Backward Compatibility
> The client component upgrade failed on
> Microsoft.sqlserver.notificationservices.dll. I had an error code 1603 and
> this in the hotfix.log
> MSP Error: 29549 Failed to install and configure assemblies c:\Program
> Files\Microsoft SQL
> Server\90\NotificationServices\9.0.242\Bin\microsoft.sqlserver.notificationservices.dll
> in the COM+ catalog. Error: -2146233087
> Error message: Unknown error 0x80131501
> Error description: The Transaction Manager is not available. (Exception
> from HRESULT: 0x8004D01B)
> Any ideas?
> Thanks
> Chris
>|||Try starting MSDTC if it's not already started and double check your event
logs for any COM+ errors.
--
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:evoMCLaYHHA.2556@.TK2MSFTNGP02.phx.gbl...
> Hi,
> I have successfully upgraded a server with both the new SP2 and the 3050
> hotfix. I am now trying to do this to my client workstation. It selected
> the following components on my SQL2005 SP1 client to upgrade.
> Setup Support Files
> SQL Server Native Client
> Client Components
> MSXML 6.0 Parser
> SQLXML4
> Backward Compatibility
> The client component upgrade failed on
> Microsoft.sqlserver.notificationservices.dll. I had an error code 1603 and
> this in the hotfix.log
> MSP Error: 29549 Failed to install and configure assemblies c:\Program
> Files\Microsoft SQL
> Server\90\NotificationServices\9.0.242\Bin\microsoft.sqlserver.notificationservices.dll
> in the COM+ catalog. Error: -2146233087
> Error message: Unknown error 0x80131501
> Error description: The Transaction Manager is not available. (Exception
> from HRESULT: 0x8004D01B)
> Any ideas?
> Thanks
> Chris
>

New SP2 Client Install Failure

Hi,
I have successfully upgraded a server with both the new SP2 and the 3050
hotfix. I am now trying to do this to my client workstation. It selected the
following components on my SQL2005 SP1 client to upgrade.
Setup Support Files
SQL Server Native Client
Client Components
MSXML 6.0 Parser
SQLXML4
Backward Compatibility
The client component upgrade failed on
Microsoft.sqlserver.notificationservices.dll. I had an error code 1603 and
this in the hotfix.log
MSP Error: 29549 Failed to install and configure assemblies c:\Program
Files\Microsoft SQL
Server\90\NotificationServices\9.0.242\Bin\microsoft.sqlserver.notifications
ervices.dll
in the COM+ catalog. Error: -2146233087
Error message: Unknown error 0x80131501
Error description: The Transaction Manager is not available. (Exception from
HRESULT: 0x8004D01B)
Any ideas?
Thanks
ChrisI found the answer on Connect. You need to have DTC running for the update
to finish.
Chris
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:evoMCLaYHHA.2556@.TK2MSFTNGP02.phx.gbl...
> Hi,
> I have successfully upgraded a server with both the new SP2 and the 3050
> hotfix. I am now trying to do this to my client workstation. It selected
> the following components on my SQL2005 SP1 client to upgrade.
> Setup Support Files
> SQL Server Native Client
> Client Components
> MSXML 6.0 Parser
> SQLXML4
> Backward Compatibility
> The client component upgrade failed on
> Microsoft.sqlserver.notificationservices.dll. I had an error code 1603 and
> this in the hotfix.log
> MSP Error: 29549 Failed to install and configure assemblies c:\Program
> Files\Microsoft SQL
> Server\90\NotificationServices\9.0.242\Bin\microsoft.sqlserver.notificatio
nservices.dll
> in the COM+ catalog. Error: -2146233087
> Error message: Unknown error 0x80131501
> Error description: The Transaction Manager is not available. (Exception
> from HRESULT: 0x8004D01B)
> Any ideas?
> Thanks
> Chris
>|||Try starting MSDTC if it's not already started and double check your event
logs for any COM+ errors.
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:evoMCLaYHHA.2556@.TK2MSFTNGP02.phx.gbl...
> Hi,
> I have successfully upgraded a server with both the new SP2 and the 3050
> hotfix. I am now trying to do this to my client workstation. It selected
> the following components on my SQL2005 SP1 client to upgrade.
> Setup Support Files
> SQL Server Native Client
> Client Components
> MSXML 6.0 Parser
> SQLXML4
> Backward Compatibility
> The client component upgrade failed on
> Microsoft.sqlserver.notificationservices.dll. I had an error code 1603 and
> this in the hotfix.log
> MSP Error: 29549 Failed to install and configure assemblies c:\Program
> Files\Microsoft SQL
> Server\90\NotificationServices\9.0.242\Bin\microsoft.sqlserver.notificatio
nservices.dll
> in the COM+ catalog. Error: -2146233087
> Error message: Unknown error 0x80131501
> Error description: The Transaction Manager is not available. (Exception
> from HRESULT: 0x8004D01B)
> Any ideas?
> Thanks
> Chris
>sql

New Setup Question

Hi there, a client asked me to make some recommendations as to the hardware setup for a new SQL 2000 setup. They will be importing a 9 gig sql 7 DB...

Specifically I'm looking for Optimal Raid configurations and Memory. Initially I was going to recommend a dual CPU machine with a raid 5 for the DAta, and rain 1 for the transaction logs. Is that still the recommended choice.

Also if they wanted to do a fail ever cluster I assume they are going to have to add an additional CPU license if the backup machine was a single CPU?Please provide more info about transactions nature. For high level of concurent transactions with high activity on writes RAID5 is not appropriate choise.

New Lynksys Router blocking access to SQL 2k

I have a new Wireless G router configured by a client for their VPN. They said to hook it up to my existing router. It works great if I try to connect to something on the VPN, Informix, SQL no problem.

I have my own SQL 2k on the same network locally. I can access the server with Maping tools but I can not get an ODBC connection to work either using Windows Authentication or SQL authentication. Tried my old router and it worked fine.

I figured it would not work while I was connected to the VPN, but thought I should be able to access SQL server when not on the VPN. Is this a port issue? Never had to deal with this.

Thanks

Mike D

make sure that you can access port 1433|||Take a look at all the rules implemented in your new Linksys router and check the port for SQL Server (1433 or 1434) if they are not being blocked.|||

Bass and Joey,

The client supplied Router is password protected. They gave me a laptop and router and asked that I plug their rounter into my existing router. I use their laptop to VPN to their site. I have only one cable to link the new router to the existing old router which is located in another office.

I got the WEP key so I could access the new router from my own laptop. Anyway I have to call their IT support team to get access. I have a feeling they won't want to open port 1433-34.

We will see.

Thanks for the info.

Mike

New Installation question

Do or should the client components be installed on the
Server?
If the client components are installed on the server
briefly describe what their purpose would be on the
server if they are also on the developers workstation.Jim,
This is completely up to you. If you're deploying a production box, then
you probably don't want client tools on it. If you're using it as a
development machine, you might.
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jim Abel" <jim.abel@.lmco.com> wrote in message
news:2b9b301c46921$d2c48bf0$a601280a@.phx.gbl...
> Do or should the client components be installed on the
> Server?
> If the client components are installed on the server
> briefly describe what their purpose would be on the
> server if they are also on the developers workstation.

New domain

I have a client that has been running 2 separate domains (same subnet). An
NT4 domain and a W2K3 domain. All clients have been added to the W2k3
domain. The NT domain now consists of a PDC, a BDC and 2 SQL 2000 servers
running W2k. My plan is to simply downlevel (remove from NT domain add to
workgroup) 2 SQL servers and then add them to to W2K3 domain. This would
render PDC and BDC with out use and we could do whatever with them. I am
wondering if this will cause any issues with SQL servers that I am not
forseeing. Insights very much appreciated.I cannot see any problems switching domain belonging as long as you dont
rename the SQL servers hostnames. You might also want to keep an eye on
which account is running the SQL services.
----
---
Johan Engdahl
CCSA, CCSE, CCA, MCP | johan AT firewall1 DOT nu | http://www.firewall1.nu
"Laurie" <Laurie@.discussions.microsoft.com> wrote in message
news:5E47BEEF-9BBD-43F6-B99F-BEAAEA4643A3@.microsoft.com...
>I have a client that has been running 2 separate domains (same subnet). An
> NT4 domain and a W2K3 domain. All clients have been added to the W2k3
> domain. The NT domain now consists of a PDC, a BDC and 2 SQL 2000 servers
> running W2k. My plan is to simply downlevel (remove from NT domain add to
> workgroup) 2 SQL servers and then add them to to W2K3 domain. This would
> render PDC and BDC with out use and we could do whatever with them. I am
> wondering if this will cause any issues with SQL servers that I am not
> forseeing. Insights very much appreciated.
>