[THIN] Re: Xenapp 6, Office 2010 and Oracle ODBC

Wow…good feedback. I’ve never seen or come across that one before. Why don’t you just use the latest 10g version, as per my other response? It saves all the messing about with Office, etc.

 

Cheers,

Jeremy.

 

From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of David
Sent: Thursday, 9 June 2011 8:52 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Xenapp 6, Office 2010 and Oracle ODBC

 

Great, despite I have tried these options many times.
Installing 11g, Installing Office into another folder instead of (x86)....
Finally I could connect doing the following.

Symply copying folder c:\program files (x86)\microsof office\
to c:\program files\'new folder'\

and executing excel.exe from the new folder.

That's it, works fine.

Now, I have the doubt of office behaviour into production servers.
In a test environment, now works, but in the farm. How can I do?
If I change office shortcuts, will work, but all the registry entries point to (x86) instead of.
Therefore the assoc .xls will point to (x86) folder.

Here you go from June 5, 2009 (Fun with Oracle thread):

 

Btrieve.

 

 

on a more serious note:

 

 

Subject: ORA-12154 or ORA-6413 Running 32-bit Oracle Software on 64-bit Windows OS
Doc ID: Note:334528.1

Symptoms: You are attempting to connect to the Oracle database from a Windows platform using one of the following programmatic interfaces

ODBC
OLEDB
OO4O
ODP.NET

after installing 32-bit Oracle client software on a 64-bit Windows operating system (OS) you receive one of the following errors:

ORA-12154: TNS:could not resolve the connect identifier specified

or

ORA-6413: Connection not open. Cause64-bit Microsoft OS's install 32-bit applications into the following location

"C:\Program Files (x86)\..."
rather than the typical location of

"C:\Program Files\..."
This causes an existing networking bug to occur where the networking layer is unable to parse program locations that contain parenthesis in the path to the executable which is attempting to connect to Oracle.

The following bug has been filed to correct this behavior:

Bug 3807408 - CANNOT EXTERNALLY AUTHENTICATE USER WITH QUOTE IN USERNAME

Additional Information

The reason you receive an ORA-12154 vs. an ORA-6413 is generally due to which programmatic interface you have chosen to use to connect to Oracle.

The ORA-12154 is the typical error seen when connecting with up-to-date interfaces using the latest version of the Oracle Call Interface (OCI):

Oracle ODBC Driver
Oracle Provider for OLE DB
Oracle Objects for OLE
Oracle Data Provider for .NET (ODP.NET)
Microsoft's .NET Managed Provider for Oracle
The ORA-6413 is typical of using older interfaces which make legacy API calls such as Oracle's OCI Version 7 API:

Microsoft ODBC Driver for Oracle
Microsoft OLE DB Provider for Oracle

SolutionTo resolve this problem try either of the following solutions:

SOLUTION 1:

Use a version of the Oracle software that contains the fix for Bug 3807408.

NOTE: Currently the following patches have been released on Windows:

Windows 32-bit
9.2.0.7.0 Patch 6: Apply Patch 4928723 or later
10.2.0.1.0 Patch 4: Apply Patch 4923768 or later
10.2.0.2.0 Patch 5: Apply Patch 5383042 or later
10.2.0.3.0: Apply Patch 5337014 or later

Windows 64-bit AMD64 and INTEL EM64T

10.2.0.1.0 Patch 4: Apply Patch 4923787 or later
10.2.0.2.0 Patch 5: Apply Patch 5388871 or later
10.2.0.3.0: Apply Patch 5337014 or later

For all other versions on Windows please use SOLUTION 2 for now.

SOLUTION 2:

Find the location of the application that is generating the error. Check the path to this location and see if it contains any parenthesis. If so, you must relocate the application to a directory without any parenthesis in the path.

----

On Fri, Jun 5, 2009 at 2:50 PM, Greg Reese <gareese@xxxxxxxxx> wrote:

i just roll with what's already deployed.   I was really hoping for a MySQL data store one of these days but I guess that will never happen now.

 

On Thu, Jun 4, 2009 at 9:20 PM, Steve Snyder <kwajalein@xxxxxxxxx> wrote:

something about the connection information not being escaped properly which the parenthesis are a part of, or some mess like that

 

Mike would be so proud that you're dropping sql for oracle... :¬D

On Fri, Jun 5, 2009 at 1:15 PM, Greg Reese <gareese@xxxxxxxxx> wrote:

maybe they can figure it out with somoe of their new Sun brains.

I woudl be good just to find the hook that tells chfarm how to populate the list.

I did run filemon on it with no luck

 

On Thu, Jun 4, 2009 at 8:06 PM, Steve Snyder <kwajalein@xxxxxxxxx> wrote:

Oracle *really* hates parenthesis in the pathnames, I ran into for apps that were installed into the (X86) folder - didn't try it for xenapp though.

 

On Fri, Jun 5, 2009 at 10:13 AM, Greg Reese <gareese@xxxxxxxxx> wrote:

So i have two Windows 2003 x64 servers with XA 5 installed pointing to Access. 

I am trying to move them to Oracle.   Both of them have a working Oracle client.  I can tnsping the db, and connect with SQL plus using the proper credentials.

I am running chfarm and choosing the new farm option.

On one of the servers, Oracle isn't even an option.  Not sure why but it's not in the drop down list.

so I tried the other server, Oracle is an option, but I get a "Database connection canceled or failed" message.

I saw an article about Oracle not being able to handle the install location of XA on 64 bit servers.  It chokes on the "Program Files (x86)" path.  Seriously?  that seems pretty out there.  Even for oracle.  It seems odd that I will have to reinstall XenApp just to use Oracle.

Anyone else run into this or have any idea on it?

Thanks

Greg

 

 

Webster

 

From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of David
Subject: [THIN] Xenapp 6, Office 2010 and Oracle ODBC

 

Hi List,

recently we have migrated to Xenapp6 into Hyper-v environment.

We have installed Office 2010 32 bits edition because Microsoft recommends 32 rather than 64b.
Anyway, we also have ODBC oracle 10g release to access Oracle server, we use others programs to access and works fine.

But, the problem is to access from Office (normally excel) to Oracle using ODBC.
I have tried many many thinks but I cannot fix the problem.
ODBC administrator can only be configured from c:\windows\syswow64\odbcad32.exe
Using this I can configure and test connection, and connection is succesfull.

Moving to Excel and trying to access data from ODBC connection is not posible.


Has anybody faced this problem?

Thanks