Sure, but to be clear, I didn’t mean to convey any offence. I really am just proposing that it would seem penny-wise and pound-foolish on the part of your mgt if they told you to proceed with the major code rewrite you fear may be needed, when in fact the fix from Adobe should have sufficed, and a little configuration effort/tweaking might well get things working as they should.
The point (if it was not clear) is that many times people will say “but I did everything Adobe told me to do, so there’s nothing more you can do”, and they may well have done all they should. They might not have missed a single step (though many often do).
I’m saying that despite that (their following every step), things may still be amiss—not because Adobe’s steps were wrong, nor did the admin fail to follow them to the letter—but because something else (perhaps from some previous iterations of problem-solving or configuraiton of IIS or the connector) has left things not working, even though all is configured as it should be (in IIS and in the CF connector).
And in such situations, I have helped people redo some things, and then magically all “worked” as expected.
Again, that may take no more than an hour of investigation and trial/error. That’s why I can’t possibly propose here what all it may be. It varies per situation. But since I know what SHOULD work, and how things SHOULD be configured, and I know also what things MAY “look right” but still NOT be working, I also know what to propose that MIGHT be changed to resolve the problem. Image may be NSFW.
Clik here to view.
So again, there is nothing behind my words here but a sincere desire to help if I might. Image may be NSFW.
Clik here to view. And also to convey that I totally get how mgt is often not willing to envision that such outside help is needed or can help. I’m saying, more than anything, that they have nothing to lose (but an hour or so of your time) if it turns out we do not resolve it.
If interested, please drop me a line directly at charlie (at) carehart.org.
/charlie
