Skip to main content
Y
Yanta0205
Participating Frequently
October 17, 2011
Question

Installing coldfusion 9 kills WSUS; ODBC connectors on CF9 64bit

  • October 17, 2011
  • 2 replies
  • 1913 views

Two questions.

I have a server set up at home. I have 8 PCs conencted to it. It is used to run file services, WSUS to keep PCs up to date, and a home web server with some CF apps I've written over the years. This is a home environment, not a corporate environment so SQL / Exchange etc are out of the question.

The server used to run XP x86 with CF7. Everything just worked. All of the time.

But I wanted to make use of more memory, which means x64. I also updated the hardware and expanded my storage to 13TB. So I installed Windows 2008 R2 x64.

Got everything working perfectly, without Coldfusion. As soon as I installed Coldfusion my woes started. It installed properly first shot, which is a rare occurence if what I read here and around the net are any indication (I count my blessings that it worked first shot).

I installed CF 9.0.1 x64. WSUS ceased to function. All clients started getting download errors 0x80244018 etc. From googling the problem it seems that the problem was the handlers that CF9 added (But I could be wrong about that). WSUS runs on the same IIS7.5 server as my home website, but on port 8530.

And of course, there appear to be no 64 bit ODBC drivers. I just use MS Access and excel for all my needs. I have about half a dozen apps I have written, most of which I have become dependent on for many reasons. I have no need, desire, or justification to invest in expensive technologies. Upgrading my CF7 to CF9 is going to cost an arm and a leg.

So, rather than learning a new language like PHP..

Q1: How do I install CF9 without breaking WSUS?

Q2: How do I continue to use MS Access to access my mdb files when I have x64 O/S, X64 CF9?

    This topic has been closed for replies.

    2 replies

    Y
    Yanta0205Author
    Participating Frequently
    December 8, 2011

    Well, it seems I spoke too soon.

    As I only get one shot aat installing, due to the fact the the intial Coldfusion administrator will only work once per install of windows, I had to reinstall Windows a few more times. A pain really, because I have to set up shares, security and all roles and features all over every time.

    But, I've managed to get CF 9.0.1 x64 working on my Windows 2008 R2 x64 server with IIS and WSUS working together. I've set up my home and WSUS websites as seperate IIS sites, and I've even got MS Access connectivity working.

    Access required that I copy some registry keys from the x64 location to the 32 bit WOW64 location and add a system DSN manually using ODBCad32.exe. I still get the driverpath variable and architechture mismatch errors, and I haven't tested writes and updates to the datasources yet, but I can read the datasources from my PCs.

    I spent probably well over 150 hours working on this over the last 5 months to get this working. Partly due to a change in OS direction (XP - WIndows 7, then 7 - 2008 R2), mid way through.

    At this point though it seems to be working close to what I have with XP/CF 7

    Y
    Yanta0205Author
    Participating Frequently
    November 13, 2011

    Surely someone has Coldfusion running on Windows 2008 R2 with WSUS?

    A
    Adam Cameron.
    Inspiring
    November 13, 2011

    Surely someone has Coldfusion running on Windows 2008 R2 with WSUS?

    On the same box?  I doubt it would be that common.  I don't think it would be very common to be running WSUS from an application server box.  Obviously I can see why you're doing it, and it's a reasonable use case, but I don't imagine it's that common.

    Now... I am a CF developer, not a CFAdministrator, and haven't been a system's dude for about ten years now, so my knowledge on administering Windows and CF and all that sort of thing is very rusty, but the troubleshooting techniques should be similar.

    You mention WSUS talks to IIS on port 8350 (when it's working).  Have you checked what's listening on port 8350 once CF is installed?  I'm unaware of CF listening to any port in the 8xxx range other than the one you tell it to for the inbuilt webserver (which will be installed and listening even if you configured your CF install to use IIS).  However it usually listens on 8500.

    I'd also do a search through the CF / JRun dir for references to 8350.

    Secondly... I believe (but this is said with only about 50% confidence) one can export an IIS config to a text file these days?  Export the config before and after CF interferes with things, and do a diff.  What's different?

    That said, I presume they're both not working from the same website, so I think it's probably more likely to be at a network level than at application level.

    And when you have CF installed, the CF side of things runs fine (other than lack of ODBC drivers)?  Either way, scour the logs for both systems at start-up, to see if there's anything interesting.  You don't mention having looked at log files.

    As for ODBC drivers... forget it.  Port your data to a Derby DB (it should be able to do anything Access can do, I should think?), or MySQL or something and be done with it.

    --

    Adam

    D
    Community Expert
    Dave WattsCommunity Expert
    Community Expert
    November 13, 2011

    Secondly... I believe (but this is said with only about 50% confidence) one can export an IIS config to a text file these days?

    Actually, the IIS configuration IS a text file in IIS 7.x. There are a series of *.config XML files.

    Dave Watts, CTO, Fig Leaf Software

    Dave Watts, Eidolon LLC
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices