The setup routines for the Lotus NotesSQL Driver(*.nsf) ODBC driver could not be loaded due to system error code 126.

I tried to create a system DSN for ODBC connection to the Lotus Notes Database and I got the following error:

"The setup routines for the Lotus NotesSQL Driver(*.nsf) ODBC driver could not be loaded due to system error code 126."

Solution
Just append the Lotus Installation Path to the Path environment variable and try setting up the DSN again and it will work.

Variable: not found in bash script

I was trying to assign a value to a variable using bash script and got this error.

Solution

You can't have space around the "=" sign. Remove the space around the equal to sign and run the script.

OLE DB provider "VFPOledb.1" has not been registered

I was trying to create a Linked Server on SQL SERVER 2008 R2 Server to connect to Foxpro database on a Windows 7 PC. I installed the Visual FoxPro 9.0 OLE DB provider and when I accessed the linked server, I got the above error.

Solution

Un-install the Visual FoxPro 9.0 OLE DB provider
Install the Provider for all users instead of current user and it will fix the problem.

Cannot convert lambda expression to type 'string' because it is not a delegate type

Got this odd error and but not so meaningful.

Solution

Just include the Linq namespace that will fix the error.

using System.Linq;

The service cannot be activated because it does not support ASP.NET compatibility. ASP.NET compatibility is enabled for this application. Turn off ASP.NET compatibility mode in the web.config or add the AspNetCompatibilityRequirements attribute to the service type with RequirementsMode setting as ‘Allowed’ or ‘Required’

If you get this error when you try to run a WCF Rest Service, then add the following line above the class declaration

[AspNetCompatibilityRequirements(RequirementsMode = AspNetCompatibilityRequirementsMode.Allowed)]
public class Class1 : IService1
{
}

This is because ASP.NET Compatibility Mode implies request processing semantics that are fundamentally different from the WCF default, individual service implementations have the ability to control whether they run inside of an application for which ASP.NET Compatibility Mode has been enabled. Services can use the AspNetCompatibilityRequirementsAttribute to indicate whether they support ASP.NET Compatibility Mode