We had that problem before. I have no idea why it is happening but it seems to be related with the users which run the dll in COM+. When the user was a regular user (not in administrator group) we had that problem. I changed the user to be an administrator and we don't have this problem anymore.