September 15, 2009 at 10:11 am
Thanks Everybody for your valuable solutions.
It was an urgent requirement for me so we have decided to use the 32-bit server to create reports for Oracle datasource.
In 32-bit everything is working fine and we started our development init.
Coming to the 64-bit server, the TNSNAMES.org file is exactly correct but we are still getting the same error, so with the suggestions from the microsoft forum, we have decided to try to install Oracle 11g client and check if we can make it work.
We have even rebooted the server but we are still getting the same error.
Is there any other place I need to check for resolving the error message ?
Regards,
Sree
September 15, 2009 at 10:48 am
I did not tell you to use 11g for 10g Oracle connection property gets confused so remove the 11g client and yes an Oracle client is required for all development with oracle. Install the 10g client and then use these instructions to give the Oracle authenticated user permissions in NTFS files.
To fix the problem you have to give the Authenticated Users group privilege to the Oracle Home directory.
•Log on to Windows as a user with Administrator privileges.
•Start Window Explorer and navigate to the ORACLE_HOME folder.
•Choose properties on the ORACLE_HOME folder.
•Click the “Security” tab of the “Properties” window.
•Click on “Authenticated Users” item in the “Name” list.
•Uncheck the “Read and Execute” box in the “Permissions” list under the “Allow” column.
•Re-check the “Read and Execute” box under the “Allow” column
•Click the “Advanced” button and in the “Permission Entries” verify that “Authenticated Users” are listed with permission = “Read & Execute”, and Apply To = “This folder, subfolders and files”. If not, edit that line and make sure that “Apply To” drop-down box is set to “This folder, subfolders and files”. This should already be set properly but it is important that you verify it.
•Click the “Ok” button until you close out all of the security properties windows. The cursor may present the hour glass for a few seconds as it applies the permissions you just changed to all subfolders and files.
•Reboot, to assure that the changes have taken effect.
Goodluck.
Kind regards,
Gift Peddie
October 24, 2011 at 10:07 am
On 64-bit servers, you'll need to install the 32-bit and 64-bit Oracle client. The reason is that the Visual Studio components still run in the 32-bit runtime.
Steve
ah, i feared this might be true
is this still true in SSRS 2008 R2? I have seen it suggested that changing the IIS setting "Enable 32-Bit Application" helps, but it doesn't work for me?
October 24, 2011 at 12:33 pm
darth_vodka (10/24/2011)
On 64-bit servers, you'll need to install the 32-bit and 64-bit Oracle client. The reason is that the Visual Studio components still run in the 32-bit runtime.
Steve
ah, i feared this might be true
is this still true in SSRS 2008 R2? I have seen it suggested that changing the IIS setting "Enable 32-Bit Application" helps, but it doesn't work for me?
There might be other solutions but this is the easy one I know because I have helped someone using VS2010 back in 2010 with the same solution. In my day job now I do SSIS development not SSRS so my knowledge relevant to Oracle may not be current.
Kind regards,
Gift Peddie
October 25, 2011 at 3:47 am
There might be other solutions but this is the easy one I know because I have helped someone using VS2010 back in 2010 with the same solution. In my day job now I do SSIS development not SSRS so my knowledge relevant to Oracle may not be current.
thanks
in that case, I have a slightly different question...
when establishing an Oracle connection in SSIS (say with .Net/OracleClient Data Provider)
is that provider the 32 bit provider that looks for the 32 bit OracleClient? (I'm using the words provider and driver interchangeably...hope that's right!)
or
does it check the property Debugging>run64BitRuntime and then check for either the 32 or 64 OracleClient depending on that...? and the 32 or 64 tnsnames.ora
October 25, 2011 at 3:54 am
actually i think that's answered earlier in the thread
The call we had open with MS said that the BIDS runs with the 32-bit oracle client, and when scheduled ssis packages run, it runs through the DB engine which is 64-bit, in which case it looks for the 64-bit client. the x86 folder would be where the bids runtimes would be hosted.
so BIDS uses 32 bit OracleClient..but the Run64BitRunTime is defaulted to yes...
which seems counter intuitive and means there is no way to debug 64 bit Oracle connections...?
October 25, 2011 at 1:25 pm
darth_vodka (10/25/2011)
actually i think that's answered earlier in the threadThe call we had open with MS said that the BIDS runs with the 32-bit oracle client, and when scheduled ssis packages run, it runs through the DB engine which is 64-bit, in which case it looks for the 64-bit client. the x86 folder would be where the bids runtimes would be hosted.
so BIDS uses 32 bit OracleClient..but the Run64BitRunTime is defaulted to yes...
which seems counter intuitive and means there is no way to debug 64 bit Oracle connections...?
I think is it much easier to use x86 instead of x64.
Kind regards,
Gift Peddie
Viewing 7 posts - 16 through 21 (of 21 total)
You must be logged in to reply to this topic. Login to reply