1. What is the best way to obtain user requirements?
You have to understand each other. The user must have at least a minimal knowledge of IT, and you must have major knowledge of their business. 75% of requirements are not stated. In some cases it's because the user isn't conscious of them, in others it's because they assume since you live in the same country that they don't have to tell you how things work. In either case, they expect you to come to the meeting knowing most of what they need in advance.
Once you've got the requirements, they have to undergo inspection. Users will submit requirements that conflict with each other, don't make sense, or simply don't really specify what they want. Defects in requirements are the most expensive cause of software failure (they usually are discovered in production), the most difficult to catch during testing (after all, what do you test against?) and the most difficult to repair (they require starting over and rebuilding the software).
2. What are the most common reasons for the system not meeting the user requirements?
In my experience, this is covered in my previous answer. The developer doesn't really know what the users want, or the users didn't really ask for what they wanted.
3. How do you handle users who constantly change their mind about what they want?
If it's a serious problem, not just a gripe, you need a more formal project management methodology. The particular activity you lack is known as change control, configuration management, and various other names. It implies that you have a formal, approved project schedule and budget. Every time you receive a request to change the project requirements, you have to modify your project plan and budget to accommodate the extra time and work.
Your users need to understand that changing software once it's under development is almost as much work as changing it when it's in production. They wouldn't expect you to do that for free so they should understand that you can't respond to changes in requirements for free either.
If you don't have a formal software development methodology, this problem is a perfect example of why you should have one. This is the most common and most troublesome problem that project managers encounter. Failure to accommodate requirements changes realistically, by updating the schedule and budget, is one of the biggest causes of project overruns and failures.
If your users just can't help themselves because their requirements honestly do change frequently, then you need a methodology that can accommodate these changes, something more iterative than what you're now using. You may also need a more end-user oriented development environment, for example object-oriented, that allows the users to change their own processing rules without needing your help.