I saw an amazing thing happen in Brussels airport


Let me begin by saying that I am impressed with the Brussels airport staff. The airport has a completely confusing layout but the TSA equivalents there are so much friendlier and eager to help passengers get on their way. The pinnacle of it all was , I saw a 5’5″ airline attendant run about 150 yards on 3 inch high heel shoes to tell a passenger that there has been a gate change.

Apparently, this passenger was directed to a different terminal by the same attendant. Shortly, she received a gate change announcement and she literally ran to inform the passenger about this gate change.

I learnt something about customer service in that moment! If this is not going above and beyond I don’t know what is

Bravo!

Advertisements

System.IO.FileNotFoundException when creating SPSite objects using the SharePoint object model


This is one of the interesting errors that we encountered recently. A console application was developed for content migration from a file share to SharePoint with an Excel file for mapping the files to specific content types. The application was run on our test environment and everything seemed to work fine. Of course we wanted to run this over the weekend. Time for easy deployment right since it is all tested and ready right? Wrong! When deploying to the server we came across this error

“Provider not registered in this environment” . After a bit of googling we realized the issue. Our test environment was running a 32 bit SharePoint installation, whereas the production version was 64 bit. Since we were using Jet drivers to connect to the Excel spreadsheet, we had to retool our application or target a specific architecture(since 32 bit drivers are available on the server). We chose the second option. We set the target platform to x86 and deployed it on production.

Update: Here is the forum post with the link to the solution. Scroll down to the 3rd comment with a link to the vbtips siteĀ  http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=125207&SiteID=1

Now we were seeing the dreaded System.IO.FileNotFoundException when creating SPSite objects in our code.

Apparently setting the target architecture to x86 and running the code on a x64 SharePoint installation, throws the FileNotFoundException. We changed the target architecture back to the default setting and had to retool the code to read the mappings using an Xml export.

%d bloggers like this: