• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 672
  • Last Modified:

CEICW. Fails to run.

SBS2003 Release 1. SBS SP1 Windows Server SP2. I have upgraded the motherboard in my server, successfully, except for the CEICW which fails to run. When selecting it from either Server Management or directly from the icw.exe, the web page opens, for the initial page, however when clicking NEXT, the ICW.EXE executable vanishes from Task Manager and nothing else happens. The ICWLOG.TXT does not get updated. Nothing happens.
It worked on the old motherboard right up to the change over. The new motherboard is a quad based xeon with Hyperthreading switched off to allow for ISA to run. ISA2000, Exchange including OWA and RWW are all working, it appears only the CEICW will not run. I will/may require this to fix problems in the future so any help or advice would be appreciated.
0
jwjjwj
Asked:
jwjjwj
  • 2
  • 2
1 Solution
 
Keith AlabasterEnterprise ArchitectCommented:
Strange configuration you have.

If you have SBS 2003 SP1 then you would have had access to the ISA2004 product rather than the non-supported (anymore) ISA 2000 product.
ISA 2004 SP3 plus OS updates - as I recall - supports hyperthreading. The issue as you likely know was simply the way the check on processors reported its results. i.e. it read cores as processors.

What sort of mobo is it - compared to the previous?
0
 
jwjjwjAuthor Commented:
Not really strange, rather as it came out of the box from Microsoft some 6-8 years ago with a sp added. The first issues of SBS2003 as this one is, had only ISA2000, not 2004. Later issues just prior to Release2 had 2004. As we have non-upgradable applications on this box, we are stuck with the configuration.  Just need to get CEICW running again for possible future requirements.
0
 
davorinCommented:
It's an old post but you can try the solution in author's post - disable DEP, reregister a number of dlls.
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/SBS_Small_Business_Server/Q_22668134.html
0
 
jwjjwjAuthor Commented:
Thank you davorin for both listening and providing the answer. Adding icw.exe to the DEP exceptions worked immediately.
0
 
davorinCommented:
I'm glad it helped.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now