This is underscoring the reason we need to know what environment a problem is occurring in. Without knowing what we are working with, we can't fix the problem. It's like calling a car repair and saying "my car doesn't run" Please, don't worry about flooding us with information. Something that may seem trivial may be the clue to busting some of these weird issues.
Posted at the top of this forum is
Having problems, READ THIS FIRST I know it's a pain to give us all the information, but believe me, it speeds the process up, and if need be, we'll build a server out with a similar configuration if we have to, just so we can figure out the bug. I recently (about 2 weeks ago) took two machines and that's all they are for, simulating server environments. While currently both are Unix based (sorry, I have no Windows server licenses, nor will I in the foreseeable future), it will enable us to work with the system in a safe and sane way.
Additionally, and I'm going to edit the sticky to include this, please DON'T send passwords to me, either by e-mail (other people monitor my e-mail when I'm out of town) or PM (this is ALWAYS a bad idea as I found out a couple of days ago.)
At this point I'm out of ideas, unless I can get a server to behave the same way, I probably won't be able to find the problem, which is too bad, since I'd like to get it fixed.
