[U2] [UV] UniOLEDB driver 64-bit windows and installers (take 50 or something)
Greetings all,
I've been parsing through the posts I've seen in the group and online,
and I'd love to get to a point where there's a conflict, but no such luck for
me I'm afraid. Our issue seems a little different and I'm hoping someone has
seen this recently. I have a single UniVerse server (10.1) it's running
Windows Server 2008, and had (as of this weekend) SQL Server 2008 on it as
well; both were setup as 32-bit. This weekend I tried to move all my SQL
Server to a new box which is still SQL Server 2008, but the Server itself is
64-bit and Windows Server 2008 R2. To make a medium story shorter I cannot get
IBM.UniOLE to show up as a Provider in SQL Server, I had it working pretty
darn well on my old box and was quite happy. Unfortunately no matter what I do
with installs (I have tried older, newer, 32-bit and 64-bit drivers) I just
cannot get it to work.
So during my debugging and disassembling of this poor process I've
made, I noticed that the Registry says the following:
Key:
HKEY_CLASSES_ROOT
Wow6432Node\CLSID\{DB14F292-CA54-11D1-BEB8-0060973B624E}\InprocServer32
ValueName: (Default)
Value: C:\Windows\SysWow64\UniOLEDB.dll
I have no such file, I've looked w/ /a etc, so it's not just hidden.
In fact, a quick search revealed no file w/ that name ANYWHERE on the HD. Now
I was able to determine that the .msi package has a nested structure and the
file _3C788511D64D4D17B7955EB0B3E14A56 really is the DLL in question, but...
I would rather do this the correct way and no brute force something into place.
Could there be something I'm missing or do not understand about the UniOLEDB
64-bit installer?
Thank you everyone,
---
John J. Wahl
Employee Owner
Programmer / Analyst
Tel: (888) 465-6737 Ext. 120
Fax: (330) 342-3896
Email: jw...@joseph.com -- farm me I dare you ;)
Web: http://www.Joseph.com/
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] [UV] UniOLEDB driver 64-bit windows and installers (take 50 or something)
John:
1. There are some third-party ODBC tools available.
2. I do something like this now with Adobe's ColdFusion... a free developer
version of CF is available for download from Adobe.
3. Rocket has some tech manuals that cover this area.
4. When I was troubleshooting this with CF, I wrote a little Java connection
string test program.
--Bill
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of John J. Wahl
Sent: Monday, April 23, 2012 5:44 PM
To: U2 Users List
Subject: [U2] [UV] UniOLEDB driver 64-bit windows and installers (take 50 or
something)
Greetings all,
I've been parsing through the posts I've seen in the group and online,
and I'd love to get to a point where there's a conflict, but no such luck for
me I'm afraid. Our issue seems a little different and I'm hoping someone has
seen this recently. I have a single UniVerse server (10.1) it's running
Windows Server 2008, and had (as of this weekend) SQL Server 2008 on it as
well; both were setup as 32-bit. This weekend I tried to move all my SQL
Server to a new box which is still SQL Server 2008, but the Server itself is
64-bit and Windows Server 2008 R2. To make a medium story shorter I cannot get
IBM.UniOLE to show up as a Provider in SQL Server, I had it working pretty
darn well on my old box and was quite happy. Unfortunately no matter what I do
with installs (I have tried older, newer, 32-bit and 64-bit drivers) I just
cannot get it to work.
So during my debugging and disassembling of this poor process I've
made, I noticed that the Registry says the following:
Key:
HKEY_CLASSES_ROOT
Wow6432Node\CLSID\{DB14F292-CA54-11D1-BEB8-0060973B624E}\InprocServer32
ValueName: (Default)
Value: C:\Windows\SysWow64\UniOLEDB.dll
I have no such file, I've looked w/ /a etc, so it's not just hidden.
In fact, a quick search revealed no file w/ that name ANYWHERE on the HD. Now
I was able to determine that the .msi package has a nested structure and the
file _3C788511D64D4D17B7955EB0B3E14A56 really is the DLL in question, but...
I would rather do this the correct way and no brute force something into place.
Could there be something I'm missing or do not understand about the UniOLEDB
64-bit installer?
Thank you everyone,
---
John J. Wahl
Employee Owner
Programmer / Analyst
Tel: (888) 465-6737 Ext. 120
Fax: (330) 342-3896
Email: jw...@joseph.com -- farm me I dare you ;)
Web: http://www.Joseph.com/
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] [UV] UniOLEDB driver 64-bit windows and installers (take 50 or something)
To use 32 bit UniVerse client software on a 64 bit Windows platform, you need
to set up the DSN with odbcad32.exe from syswow64 (not system32). If your
client software is 64 bit then you need UniVerse 11.1 whIch has 64 bit client
software, and updated SQL/ODBC as well.
Hope this helps.
Regards JayJay
Sent from my new toy.
On 23 Apr 2012, at 22:44, John J. Wahl jw...@joseph.com wrote:
Greetings all,
I've been parsing through the posts I've seen in the group and online, and
I'd love to get to a point where there's a conflict, but no such luck for me
I'm afraid. Our issue seems a little different and I'm hoping someone has
seen this recently. I have a single UniVerse server (10.1) it's running
Windows Server 2008, and had (as of this weekend) SQL Server 2008 on it as
well; both were setup as 32-bit. This weekend I tried to move all my SQL
Server to a new box which is still SQL Server 2008, but the Server itself is
64-bit and Windows Server 2008 R2. To make a medium story shorter I cannot
get IBM.UniOLE to show up as a Provider in SQL Server, I had it working
pretty darn well on my old box and was quite happy. Unfortunately no matter
what I do with installs (I have tried older, newer, 32-bit and 64-bit
drivers) I just cannot get it to work.
So during my debugging and disassembling of this poor process I've made, I
noticed that the Registry says the following:
Key:
HKEY_CLASSES_ROOT
Wow6432Node\CLSID\{DB14F292-CA54-11D1-BEB8-0060973B624E}\InprocServer32
ValueName: (Default)
Value: C:\Windows\SysWow64\UniOLEDB.dll
I have no such file, I've looked w/ /a etc, so it's not just hidden. In
fact, a quick search revealed no file w/ that name ANYWHERE on the HD. Now I
was able to determine that the .msi package has a nested structure and the
file _3C788511D64D4D17B7955EB0B3E14A56 really is the DLL in question,
but... I would rather do this the correct way and no brute force something
into place. Could there be something I'm missing or do not understand about
the UniOLEDB 64-bit installer?
Thank you everyone,
---
John J. Wahl
Employee Owner
Programmer / Analyst
Tel: (888) 465-6737 Ext. 120
Fax: (330) 342-3896
Email: jw...@joseph.com -- farm me I dare you ;)
Web: http://www.Joseph.com/
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] [UV] UniOLEDB driver 64-bit windows and installers (take 50 or something)
Thanks Bill,
Personally if it's windows, I normally just make a new Text document,
then rename the file Test {whatever}.udl and the GUI usually has that
associated to what is now called Microsoft Data Link file format, but I swear
it used to be something else... anyway, you can get your provider tabs, Data
Source Tabs, Advanced, etc and I'm assuming Microsoft bought it's been in there
since at least XP. Then pick your provider and test away. With this specific
issue I'm having though, I'm now able to get the uvODBC 64-bit driver to work
that way:
Provider=MSDASQL.1;Password=xx;Persist Security Info=True;User
ID=Server\user;Data Source=Data123
However that MsDASQL.1 provider, that's not working in SQL Server w/
that same set of variables, nor can I use OpenDataSource, or OpenRowSet, I'm
running out of things to try. I swear I did this two or three years ago w/ my
current server ;) Tried the old IBM.UniOLEDB driver I had before, I've tried a
few ways. I actually got a Linked Server to almost work using...
EXEC master.dbo.sp_addlinkedserver
@server = N'Linked_Server_Name'
,@srvproduct = N'UniVerse'
,@provider = N'MSDASQL'
,@datasrc=N'ODBC_DSN_Name1'
... but this lets me expand the catalog and see the VIEWS from the
account in question, but not query a darn thing. Any query gives me:
...[Table_or_View] contains no columns that can be selected or the current user
does not have permissions on that object.
I hate to write a CLR trigger/addon for SQL just to read and write
changes for some adhoc stuff that we've never written back in UniVerse. The
reads and writes really seemed to finally be getting faster too from my
UniVerse server too.
John J. Wahl
Employee Owner
Programmer / Analyst
Tel: (888) 465-6737 Ext. 120
Web: http://www.Joseph.com/
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Bill Brutzman
Sent: Monday, April 23, 2012 18:02
To: U2 Users List
Subject: Re: [U2] [UV] UniOLEDB driver 64-bit windows and installers (take 50
or something)
John:
1. There are some third-party ODBC tools available.
2. I do something like this now with Adobe's ColdFusion... a free developer
version of CF is available for download from Adobe.
3. Rocket has some tech manuals that cover this area.
4. When I was troubleshooting this with CF, I wrote a little Java connection
string test program.
--Bill
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of John J. Wahl
Sent: Monday, April 23, 2012 5:44 PM
To: U2 Users List
Subject: [U2] [UV] UniOLEDB driver 64-bit windows and installers (take 50 or
something)
Greetings all,
I've been parsing through the posts I've seen in the group and online,
and I'd love to get to a point where there's a conflict, but no such luck for
me I'm afraid. Our issue seems a little different and I'm hoping someone has
seen this recently. I have a single UniVerse server (10.1) it's running
Windows Server 2008, and had (as of this weekend) SQL Server 2008 on it as
well; both were setup as 32-bit. This weekend I tried to move all my SQL
Server to a new box which is still SQL Server 2008, but the Server itself is
64-bit and Windows Server 2008 R2. To make a medium story shorter I cannot get
IBM.UniOLE to show up as a Provider in SQL Server, I had it working pretty
darn well on my old box and was quite happy. Unfortunately no matter what I do
with installs (I have tried older, newer, 32-bit and 64-bit drivers) I just
cannot get it to work.
So during my debugging and disassembling of this poor process I've
made, I noticed that the Registry says the following:
Key:
HKEY_CLASSES_ROOT
Wow6432Node\CLSID\{DB14F292-CA54-11D1-BEB8-0060973B624E}\InprocServer32
ValueName: (Default)
Value: C:\Windows\SysWow64\UniOLEDB.dll
I have no such file, I've looked w/ /a etc, so it's not just hidden.
In fact, a quick search revealed no file w/ that name ANYWHERE on the HD. Now
I was able to determine that the .msi package has a nested structure and the
file _3C788511D64D4D17B7955EB0B3E14A56 really is the DLL in question, but...
I would rather do this the correct way and no brute force something into place.
Could there be something I'm missing or do not understand about the UniOLEDB
64-bit installer?
Thank you everyone,
---
John J. Wahl
Employee Owner
Programmer / Analyst
Tel: (888) 465-6737 Ext. 120
Fax: (330) 342-3896
Email: jw...@joseph.com -- farm me I dare you ;)
Web: http://www.Joseph.com/
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] [UV] UniOLEDB driver 64-bit windows and installers (take 50 or something)
Sorry John,
I dropped the ball on that one, I was indeed aware of that, and yes got
past this entire portion months ago w/ my vendor. I installed the 11.1.x
client that is 64-bit on the 64-bit server, the download was a Nov 2011
release, and as best as I know the newest thing I was back out a little bit ago
and didn't see anything newer I could try. As stated ODBC would be fine if
Microsoft SQL Server 2008 allowed that... when I tried the old Connection
string I was using in an OpenDataSource directly I was getting an error about a
single threaded apartment model not being valid. That led me to believe my
install was messed up and found the DLL was not even present in the correct
place, and more hours of fun ;)
The older string that the other machine uses returns an error like:
Msg 7308, Level 16, State 1, Line 1
OLE DB provider 'IBM.UniOLEDB' cannot be used for distributed queries because
the provider is configured to run in single-threaded apartment mode.
... and ... doesn't actually show up as a provider anyway, so I was
reaching.
Thank you for the feedback,
--
John J. Wahl
Employee Owner
Programmer / Analyst
Tel: (888) 465-6737 Ext. 120
Fax: (330) 342-3896
Email: jw...@joseph.com
Web: http://www.Joseph.com/
Add Me
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of John Jenkins
Sent: Monday, April 23, 2012 18:40
To: U2 Users List
Cc: U2 Users List
Subject: Re: [U2] [UV] UniOLEDB driver 64-bit windows and installers (take 50
or something)
To use 32 bit UniVerse client software on a 64 bit Windows platform, you need
to set up the DSN with odbcad32.exe from syswow64 (not system32). If your
client software is 64 bit then you need UniVerse 11.1 whIch has 64 bit client
software, and updated SQL/ODBC as well.
Hope this helps.
Regards JayJay
Sent from my new toy.
On 23 Apr 2012, at 22:44, John J. Wahl jw...@joseph.com wrote:
Greetings all,
I've been parsing through the posts I've seen in the group and online, and
I'd love to get to a point where there's a conflict, but no such luck for me
I'm afraid. Our issue seems a little different and I'm hoping someone has
seen this recently. I have a single UniVerse server (10.1) it's running
Windows Server 2008, and had (as of this weekend) SQL Server 2008 on it as
well; both were setup as 32-bit. This weekend I tried to move all my SQL
Server to a new box which is still SQL Server 2008, but the Server itself is
64-bit and Windows Server 2008 R2. To make a medium story shorter I cannot
get IBM.UniOLE to show up as a Provider in SQL Server, I had it working
pretty darn well on my old box and was quite happy. Unfortunately no matter
what I do with installs (I have tried older, newer, 32-bit and 64-bit
drivers) I just cannot get it to work.
So during my debugging and disassembling of this poor process I've made, I
noticed that the Registry says the following:
Key:
HKEY_CLASSES_ROOT
Wow6432Node\CLSID\{DB14F292-CA54-11D1-BEB8-0060973B624E}\InprocServer32
ValueName: (Default)
Value: C:\Windows\SysWow64\UniOLEDB.dll
I have no such file, I've looked w/ /a etc, so it's not just hidden. In
fact, a quick search revealed no file w/ that name ANYWHERE on the HD. Now I
was able to determine that the .msi package has a nested structure and the
file _3C788511D64D4D17B7955EB0B3E14A56 really is the DLL in question,
but... I would rather do this the correct way and no brute force something
into place. Could there be something I'm missing or do not understand about
the UniOLEDB 64-bit installer?
Thank you everyone,
---
John J. Wahl
Employee Owner
Programmer / Analyst
Tel: (888) 465-6737 Ext. 120
Fax: (330) 342-3896
Email: jw...@joseph.com -- farm me I dare you ;)
Web: http://www.Joseph.com/
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
