Thank you Alex!After intense research on the internet I discovered that I simply had to
re-register a problematic dll called msjtes40.dll. Once I registered this
dll, the problem disappeared, so perhaps you can use it as a possible
solution if someone else ever encounters this problem in the future.
http://support.microsoft.com/kb/317708