Skip to main content


Showing posts from December, 2008

Google Search

Custom Search

Live Search

Yahoo Search

Search the web Search this site

Exception from HRESULT: 0x80040E14

Recently in SharePoint server I got an error when trying to do almost any action.
The error was Exception from HRESULT: 0x80040E14.
After sometime I did find out, that my C drive has gone out of disk space, and that caused SQL transaction log creation failure which resulted this error.
So freeing up more space on C drive solved my problem.
You will be able to get more details of the error by checking SharePoint log files.

Planning to Buy a Vehicle?

Thought to share some expensive and valuable information that might help you if you are planning to buy a vehicle. Lookout for two main things.
1. Quality of the Vehicle
2. Legal Side of the Vehicle

Although most of the things I mention in this are specific to Sri Lanka I definitely know there are similar things to check in other countries as well.

1. Quality of the Car
If you are buying a brand new vehicle this is not required because the company will give you the details technical overview and will also give you a warranty.
But if you are going for a used vehicle then you have to check for its quality. Anyway I am not that good in the technical side so you have to rely on the knowledge that you have or someone who knows better.

2. Legal Side of the Vehicle
This is one area most people are not paying that much interest. But this is the most important side, imagine a vehicle that you buy having problems with its documents, If that happens you wont be able to transfer it to your name with ease…

Visual Studio not Showing Errors

Is your Visual Studio showing error line numbers and respective pages while you develop?
If not read on, recently I came up to a machine which was having Visual Studio error. Visual Studio was showing errors when a project is compiled but the error details (error code line number, error file) which we can use to identify the error are not displayed.
After trying out several things found the cause of it and thought to share it.
The problem was not with the project but with the path the project was kept.
In the machine the failing project was stored under a folder which was having parenthesis or brackets "(".
For example the solution path was like C:\ProjectsA(V1)\MyProj\.
The (V1) part was confusing Visual Studio making it stop displaying the error details.
If you also have the same problem simply remove the brackets by renaming the folder and reload your project to Visual Studio from the new path. The error details will be shown correctly.