Showing posts with label drivers. Show all posts
Showing posts with label drivers. Show all posts

Saturday, February 25, 2012

64-bit JET drivers or alternative?

Hi all -
I'm enountering the same problem many have previously reported.
Running SQL Server 2005 x64 on Windows Server 2003, and I can't use a
Data Flow Task in SSIS where the destination in an Excel spreadsheet
because there is no 64-bit JET driver for Excel.
Is anyone aware of a 64-bit driver now available or any 3rd party
options? Running the entire package in 32-bit mode is not a
possibility, so I can't use the DTExec workaround.
Any assistance would be appreciated --
Jamie > Running SQL Server 2005 x64 on Windows Server 2003, and I can't use a
> Data Flow Task in SSIS where the destination in an Excel spreadsheet
> because there is no 64-bit JET driver for Excel.
> Is anyone aware of a 64-bit driver now available or any 3rd party
> options? Running the entire package in 32-bit mode is not a
> possibility, so I can't use the DTExec workaround.
You can vote here:
Microsoft Connect > SQL Server: x64 Jet provider
http://connect.microsoft.com/SQLSer...=12511
7

64-bit JET drivers or alternative?

Hi all -
I'm enountering the same problem many have previously reported.
Running SQL Server 2005 x64 on Windows Server 2003, and I can't use a
Data Flow Task in SSIS where the destination in an Excel spreadsheet
because there is no 64-bit JET driver for Excel.
Is anyone aware of a 64-bit driver now available or any 3rd party
options? Running the entire package in 32-bit mode is not a
possibility, so I can't use the DTExec workaround.
Any assistance would be appreciated --
Jamie :)> Running SQL Server 2005 x64 on Windows Server 2003, and I can't use a
> Data Flow Task in SSIS where the destination in an Excel spreadsheet
> because there is no 64-bit JET driver for Excel.
> Is anyone aware of a 64-bit driver now available or any 3rd party
> options? Running the entire package in 32-bit mode is not a
> possibility, so I can't use the DTExec workaround.
You can vote here:
Microsoft Connect > SQL Server: x64 Jet provider
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=125117

Friday, February 24, 2012

64 bit ODBC Datasource

Hello together
I'm running Reporting Services on a 64 bit Windows 2003 R2 machine. I've
installed the MyOdbc 3.51 Drivers for MySql which I would like to use as the
Datasource for my reports. I configured and tested the ODBC connection
successfully using the odbcad32.exe in the windows\syswow64 folder.
But when I deploy a report which I designed on my 32 bit development machine
where all is running correctly, and I run the report on the server, it
cannot find the datasource.
I think it has the same reason why I cannot see the MyODBC driver in the
normal ODBC Configuration Manager in the Administrative Tools.
Is there a possiblity to do that anyway'
Thank you and greetings from Switzerland
ThomasHi Thomas,
Did you get a response to this question? I'm not using MySQL, but
I've spent most of today chasing this exact problem. I can tell you
that hacking the registry doesn't work, but I'd really like to know if
you heard from someone that had solved it, or if you found the answer
yourself.
Thanks in advance.
Dan
Thomas Bolt wrote:
> Hello together
> I'm running Reporting Services on a 64 bit Windows 2003 R2 machine. I've
> installed the MyOdbc 3.51 Drivers for MySql which I would like to use as the
> Datasource for my reports. I configured and tested the ODBC connection
> successfully using the odbcad32.exe in the windows\syswow64 folder.
> But when I deploy a report which I designed on my 32 bit development machine
> where all is running correctly, and I run the report on the server, it
> cannot find the datasource.
> I think it has the same reason why I cannot see the MyODBC driver in the
> normal ODBC Configuration Manager in the Administrative Tools.
> Is there a possiblity to do that anyway'
> Thank you and greetings from Switzerland
> Thomas|||Hi Dan,
Did you get anywhere with this? I'm in exactly the same position that you
were in August!
Any help would be very much appreciated.
Rob
"barnetted@.michigan.gov" wrote:
> Hi Thomas,
> Did you get a response to this question? I'm not using MySQL, but
> I've spent most of today chasing this exact problem. I can tell you
> that hacking the registry doesn't work, but I'd really like to know if
> you heard from someone that had solved it, or if you found the answer
> yourself.
> Thanks in advance.
> Dan
> Thomas Bolt wrote:
> > Hello together
> >
> > I'm running Reporting Services on a 64 bit Windows 2003 R2 machine. I've
> > installed the MyOdbc 3.51 Drivers for MySql which I would like to use as the
> > Datasource for my reports. I configured and tested the ODBC connection
> > successfully using the odbcad32.exe in the windows\syswow64 folder.
> > But when I deploy a report which I designed on my 32 bit development machine
> > where all is running correctly, and I run the report on the server, it
> > cannot find the datasource.
> >
> > I think it has the same reason why I cannot see the MyODBC driver in the
> > normal ODBC Configuration Manager in the Administrative Tools.
> > Is there a possiblity to do that anyway'
> >
> > Thank you and greetings from Switzerland
> > Thomas
>

64 Bit drivers IBM Db2

Hey guys .. I am trying to run SSIS on the WIn2k3 .. The server is a 64 bit machine. I could not find Db2 drivers for a 64 bit one .. any clues as to how , I can find it. By the way .. I have been running the package in 32 bit mode for now .. which I dont think is a very good idea.

Any suggestions are most welcome ..

Have you tried the Microsoft one (http://www.microsoft.com/downloads/details.aspx?familyid=D09C1D60-A13C-4479-9B91-9E8B9D835CDC&displaylang=en)

The standalone Microsoft OLE DB Provider 2005, which ships in the Feature Pack for SQL Server 2005, offers a single download package and setup program. The setup will detect the processor and install (1) X86 only on Windows X86, (2) x86 side-by-side X64 on Windows X64, or (3) x86 only on Windows IA64. The other Microsoft OLE DB Provider for DB2 that ships in HIS 2006, offers x86 only. The end result of running "either" setup program is an X86 only DB2OLEDB provider.

If you don't want the WOW64 "work-around" for SSIS, you must get the 64 bit provider for DB2 from IBM. Its part of their standard client install kit.