Feeds:
Posts
Comments

Posts Tagged ‘x64’

We often get Excel files with content to import into SharePoint. Most of the time I fire up Visual Studio and write a small console application to import the Excel data. However with SharePoint 2010 I got the error “The ‘Microsoft.Jet.OLEDB.4.0′ provider is not registered on the local machine”.

The idea

When I need to import content into SharePoint using the oledb data is far the easiest way to read Excel files without having to install office on your SharePoint server.

You simply add an OleDbConnection , an OleDbCommand, an OleDbDataAdapter and a correctly formulated select statement.

            string ConnectionString = @"Provider=Microsoft.Jet.OLEDB.4.0; Data Source=c:\Import\Sample.xslx; Extended Properties=""Excel 8.0;HDR=Yes"";";
            string CommandText = "SELECT * FROM [Services$]";

            OleDbConnection connection = new OleDbConnection(ConnectionString);
            OleDbCommand command = new OleDbCommand(CommandText, connection);
            connection.Open();

            OleDbDataAdapter adapter = new OleDbDataAdapter(command);

            DataSet dataset = new DataSet();
            adapter.Fill(dataset, "Excel");

The cause

SharePoint 2010 is 64 bit so you need to compile your custom SharePoint code as a 64-bit applications. However the default Jet Library does not support 64-bit applications and thus results in the following error:

The ‘Microsoft.Jet.OLEDB.4.0′ provider is not registered on the local machine.

Solution

Luckily Micosoft has released a solution in the form of the Microsoft Access Database Engine 2010 Redistributable

  1. Download the Microsoft Access Database Engine 2010 Redistributable
  2. Install the package on your development machine
  3. Modify your OleDb Connection string from:
    Provider=Microsoft.Jet.OLEDB.4.0; ….
    to
    Provider=Microsoft.ACE.OLEDB.12.0;….
  4. rebuild your application
    note
    : make sure your application is set to compile as a 64 bit application

Don’t forget to install this redistibutable on your SharePoint server as well.

Read Full Post »

Lately I had some questions from a friend that also bought a Macbook pro but (accidently) bought the 64bit version of Vista.

Vista 64bit is not supported by Apple’s bootcamp. Vista will install properly but the drivers provided by Apple are not 64bit ‘capable’. The good news is. If you have some technical (Windows) background you can download the needed drivers from the hardware manufacture website.

Main problems occur with WIFI, bluetooth and the key mapper (eject button etc..) drivers.

I found a nice list at http://forum.notebookreview.com/showthread.php?t=149395 and decided to recompile the list with my own experiences and put it here for future reference ;-)

Apple bootcamp drivers overview for Vista 64bit (x64).Video
Video is currently supported. You can download the lastest 64 bit drivers from the nvidia site.

 

Audio
Audio is currently supported. Download the latest RealTek drivers from the realTek driver download site

Keyboard
You can support a variety of Keyboard functions by installing Input Remapper. Make certain you install this after connecting to the network and downloading windows updates, or it will break while attempting to uninstall nonexistant drivers. Also, be certain to disable Driver Signing beforehand.

Bluetooth
Is not supported. But this post on the apple forum tells you how enable bluetooth support in Vista x64 on your Macbook. Apple Forum. I did not test this. Looks more like a hack to me. So you might run into aother problems.

TrackPad
Though the trackpad works, it has none of the useful functionality that OS/X provides (such as double tap right click)

iSight
Not supported. Some claim that using the default Vista USB cam driver does the trick.

ExpressCard
Untested.

Fans
Supported with Input Remapper

Suspend and Hibernate
Not currently supported.

Wireless
Use default Vista drivers.
Or Mac has the Atheros AR5008 Wireless Network Adapter. The Atheros v7.3.1.127 Vista x86/x64 should work. Install the driver through the Device Manager.
If that doesn’t work try replacing the INF with the Atheros x64 modded INF. Or try some of the other Atheros drivers. Please provide feedback.

Read Full Post »

Follow

Get every new post delivered to your Inbox.