Link to home
Start Free TrialLog in
Avatar of Casey Santos
Casey SantosFlag for United States of America

asked on

HTTP 12150 error when doing a post - possible registry issue?

Hi there,
Recently various members of our organization started getting a strange HTTP 12150 error when trying to open a third party application from their desktop.  We have done some troubleshooting and found that the error occurs whenever a "post" http transaction is run from this application, but not when a "get" function is used.  We have written sample programs that are generic and experience the same thing.

This has happened to a number of users in our group that at one point could use the software, leading us to think that it could have something to do with some sort of application/operating system update that is being pushed to our computers.  We cannot confirm, however.  

What we DO know is this:  if a user that is getting the error logs out and a different user logs in to the same machine and tries to operate the same functionality, it works.  We are not sure why this is occurs.  We thought it could be due to the registry settings, but I do not know where to begin to troubleshoot this one.

We are using Windows XP SP2

Can anyone help?

- Casey
Avatar of Walter Padrón
Walter Padrón
Flag of United States of America image

Hi csantos91,

You most likely have some kind of firewall that is blocking the program or antivirus security feature activated.

cheers
Avatar of Casey Santos

ASKER

wpadron,
What makes you think this?  Do you have any idea of a way to test this particular situation?  I need to have some concrete info. to give our IT infrastructure team.  Any help is much appreciated.

Casey
ASKER CERTIFIED SOLUTION
Avatar of Walter Padrón
Walter Padrón
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Hi there,

It did affect other users.  We narrowed it down to automatic updates being sent for Microsoft Windows.  

What we ended up doing was starting with a freshly re-imaged computer and adding updates one by one to isolate where it happened.  We narrowed it down to a security update from Microsoft then did a registry compare.  One by one we added the registry settings from the update to a freshly imaged computer and found the one that broke it.  It was an "Accept Language" registry setting - totally obscure.   But it caused the post command that our application was trying to do to fail.  Really frustrating.  It took us a lot of time and manpower to track that one down.  Now we are scared to accept these updates going forward, but since they are security updates we have little choice.

Thanks for your help.

Casey