Re: Windows Server 2003 SP2 causes CEICW to fail?
- From: "kenkcj" <unknownmailbox@xxxxxxxxxxx>
- Date: Thu, 20 Sep 2007 13:25:20 -0500
Merv,
During my server reboot at lunch time today, I noticed that when windows
restarted it came up with an error message saying that CEICW was blocked
from opening due to errors caused by viruses or security threats, click to
change settings or close to exit. Or something along those lines. I changed
the settings so that CEICW would be able to open and then went on to run
through connect to the internet. I ran through the settings I wanted to
attempt to change and attached are the results within the ICWlog file. I
have not yet attempted to do what you have recommended but will tomorrow if
this icwlog doesn't help you out. Please let me know what you think.
-kenkcj
9/20/2007 12:51 PM
C:\Program Files\Microsoft Windows Small Business
Server\Networking\ICW\wizinet.dll, version 5.2.2651.0
calling CNetCommit::ValidatePropertyBag ().
Call to Querying for the property bag () returned ok.
Call to Reading hardware selection () returned ok.
Hardware selection: 2
Call to Validating hardware selection () returned ok.
9/20/2007 12:51 PM
C:\Program Files\Microsoft Windows Small Business
Server\Networking\ICW\wizrfire.dll, version 5.2.2651.0
calling CRFireCommit::ValidatePropertyBag (0x35178).
Call to Reading web publishing selection () returned ok.
Web publishing selections:
OWA publishing: 0
RUP publishing: 0
Monitoring publishing: 0
OMA publishing: 0
RPC publishing: 0
Companyweb publishing: 0
ROOT publishing: 0
Call to CRFireCommit::ValidatePropertyBag () returned ok.
9/20/2007 12:51 PM
C:\Program Files\Microsoft Windows Small Business
Server\Networking\ICW\wizcert.dll, version 5.2.2651.0
Calling CCertCommit::ValidatePropertyBag
Nothing is published, will not touch SSL Settings
*** CCertCommit::ValidatePropertyBag returned ERROR 1
9/20/2007 12:51 PM
C:\Program Files\Microsoft Windows Small Business
Server\Networking\ICW\wizemail.dll, version 5.2.2651.0
calling CEmailCommit::ValidatePropertyBag ().
calling pdispPPPBag->QueryInterface (IPropertyPagePropertyBag, 0x7f558).
Call to pdispPPPBag->QueryInterface () returned ok.
calling ReadInt4 (0x35178, DB5E5E45-3598-4F1D-8FF7-0ED35B9EB6A4).
Call to ReadInt4 () returned ok.
The out param of ReadInt4() is -1.
calling CValidatePropertyUtil.ValidatePropertyInteger ().
Call to CValidatePropertyUtil.ValidatePropertyInteger () returned ok.
Call to CEMailCommit::ValidatePropertyBag () returned ok.
calling CNetCommit::Commit (217464).
calling CNetCommit::ValidatePropertyBag ().
Call to Querying for the property bag () returned ok.
Property bag is not dirty, skipping validation
calling CNetCommit::Common ().
Call to CNetCommit::Common () returned ok.
Call to CNetCommit::Commit () returned ok.
calling CRFireCommit::CommitEx (0x35178).
calling CRFireCommit::ValidatePropertyBag (0x35178).
Call to Reading web publishing selection () returned ok.
Web publishing selections:
OWA publishing: 0
RUP publishing: 0
Monitoring publishing: 0
OMA publishing: 0
RPC publishing: 0
Companyweb publishing: 0
ROOT publishing: 0
Call to CRFireCommit::ValidatePropertyBag () returned ok.
calling Enable Basic Firewall (0x0).
calling Get Private NIC Info (0x0).
calling Set RRAS Inbound Filter (0x0).
calling Set RRAS Registry key (0x0).
Call to GetPrivateNICGuid () returned ok.
Call to GetIPAddress for private nic () returned ok.
Call to GetSubnetMask for private nic () returned ok.
RUP is not published
Error 0x80070003 returned from call to Fixing the inheritance for root
dir().
calling Set Web Publishing Rules (0x80070003).
Error 0x80070003 returned from call to CRFireCommit::Commit().
Calling CCertCommit::CommitEx
Calling CCertCommit::ValidatePropertyBag
Nothing is published, will not touch SSL Settings
*** CCertCommit::ValidatePropertyBag returned ERROR 1
CCertCommit::CommitEx returned OK
calling CEmailCommit::Commit (0x37fa8).
calling CEmailCommit::ValidatePropertyBag ().
calling pdispPPPBag->QueryInterface (IPropertyPagePropertyBag, 0x7f4d4).
Call to pdispPPPBag->QueryInterface () returned ok.
calling ReadInt4 (0x35178, DB5E5E45-3598-4F1D-8FF7-0ED35B9EB6A4).
Call to ReadInt4 () returned ok.
The out param of ReadInt4() is -1.
calling CValidatePropertyUtil.ValidatePropertyInteger ().
Call to CValidatePropertyUtil.ValidatePropertyInteger () returned ok.
Call to CEMailCommit::ValidatePropertyBag () returned ok.
calling pdispPPPBag->QueryInterface (IPropertyPagePropertyBag, 0x7f544).
Call to pdispPPPBag->QueryInterface () returned ok.
calling ReadInt4 (0x35178, DB5E5E45-3598-4F1D-8FF7-0ED35B9EB6A4).
Call to ReadInt4 () returned ok.
The out param of ReadInt4() is -1.
calling GetDomainAndControllerNames ().
Call to GetDomainAndControllerNames () returned ok.
calling GetOrganizationName (\\fmiserver.FMICNC.local, DC=FMICNC,DC=local).
Call to GetOrganizationName () returned ok.
calling GetFirstAdministrativeGroup (\\fmiserver.FMICNC.local,
DC=FMICNC,DC=local, FMICNC).
Call to GetFirstAdministrativeGroup () returned ok.
calling GetFirstRoutingGroup (\\fmiserver.FMICNC.local, DC=FMICNC,DC=local,
FMICNC, first administrative group).
Call to GetFirstRoutingGroup () returned ok.
Call to Getting NETBIOS domain name () returned ok.
NETBIOS domain name: FMICNC
Error 0x80070003 returned from call to Enabling NTLM on /public().
Error 0x80070003 returned from call to CEMailCommit::Commit().
calling GetBOConnector ().
Error 0x80072030 returned from call to GetBOConnector().
"Merv Porter [SBS-MVP]" <mwport@xxxxxxxxxxxxxxxxxxx> wrote in message
news:%23JUvQw5%23HHA.2268@xxxxxxxxxxxxxxxxxxxxxxx
SBS is a highly integrated set of components. When the default web site
was modified or removed, much of that intergration was broken. To restore
the functionality of the Wizards, I believe you will need to reinstall IIS
on the SBS server. This was detailed in KB 887305 but I see that has been
removed from the knowledgebase (hopefully temporarily). I don't believe
"swapping over" DLLs is going to fix the problem.
887305 How to re-install Internet Information Services (IIS) 6.0 in
Windows Small Business Server 2003
http://support.microsoft.com/?id=887305
(I've attached an .rtf file of that KB article, dated as of Feb 11, 2005).
You can create subsites beneath Companyweb if that is your goal:
How to create a sub site beneath Companyweb
http://www.smallbizserver.net/Articles/tabid/266/articleType/ArticleView/articleId/80/How-to-create-a-sub-site-beneath-Companyweb.aspx
--
Merv Porter [SBS-MVP]
============================
"kenkcj" <unknownmailbox@xxxxxxxxxxx> wrote in message
news:ua3bpZ5%23HHA.396@xxxxxxxxxxxxxxxxxxxxxxx
Merv,
Thank you for the links. We actually deleted the default website as we
don't
use anything within the default website. The website we have on there
doesn't have any virtual directories and as such no commas within them.
Before I try swapping over DLL files as Bill Vogel did, I was curious if
this would matter(would it cause problems?) from transferring these dlls
from a SBS 2003 R2 standard box to a SBS 2003 Premium box. Or if you had
any
other suggestions as to where to proceed from here. Thanks again for all
your assistance and I hope we can get this figured out.
-kenkcj
"Merv Porter [SBS-MVP]" <mwport@xxxxxxxxxxxxxxxxxxx> wrote in message
news:%23qP$7Xw%23HHA.3780@xxxxxxxxxxxxxxxxxxxxxxx
Or maybe...
ICW.EXE Error
http://www.winserverkb.com/Uwe/Forum.aspx/windows-server-sbs/17491/ICW-EXE-Error
--
Merv Porter [SBS-MVP]
============================
"kenkcj" <unknownmailbox@xxxxxxxxxxx> wrote in message
news:eAQXtPw%23HHA.3548@xxxxxxxxxxxxxxxxxxxxxxx
Merv,
I tried re-registering the wizards and CEICW is still doing the same
thing. I click connect to the interet, then hit the next button. The
hourglass mouse pointer comes up for about 5-10 seconds, then CEICW
closes out. I did however, find the event log for the failure. These
are
the 2 events that popped up after CEICW closed out, first one an error
and the second one just information message.
9/19/2007 Source: Application Error
Time: 4:19:34 PM
Category: (100)
Type: Error
Event ID: 1000
Description:
Faulting application icw.exe, version 5.2.2651.0, faulting module
unknown, version 0.0.0.0, fault address 0x000b1dc0.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
9/19/2007
Source: DrWatson
Time: 4:19:35 PM
Category: None
Type: Information
Event ID: 4097
Description:
The application, C:\Program Files\Microsoft Windows Small Business
Server\Networking\icw\icw.exe, generated an application error The error
occurred on 09/19/2007 @ 16:19:35.265 The exception generated was
c0000005 at address 000B1DC0 (<nosymbols>)
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Please help!!
Thanks for the assistance
-kenkcj
"Merv Porter [SBS-MVP]" <mwport@xxxxxxxxxxxxxxxxxxx> wrote in message
news:undtQ9j%23HHA.5328@xxxxxxxxxxxxxxxxxxxxxxx
Maybe try re-registering the wizards:
From a command prompt:
CD C:\Program files\Microsoft Windows Small Business
Server\Networking\ICW
Regsvr32 wizcert.dll
Regsvr32 wizemail.dll
Regsvr32 wizinet.dll
Regsvr32 wizproxy.dll
Regsvr32 wizrfire.dll
CD C:\Program files\Microsoft Windows Small Business
Server\Networking\RRASWiz
Regsvr32 wizrras.dll
Then try CEICW again.
--
Merv Porter [SBS-MVP]
============================
"kenkcj" <unknownmailbox@xxxxxxxxxxx> wrote in message
news:OxTTBZj%23HHA.5164@xxxxxxxxxxxxxxxxxxxxxxx
Hi everyone,
I recently reinstalled the company SBS 2003 Premium. The other day, I
was performing the needed updates to get it back to specification.
After the reboot following the installation of Windows Server 2003
Service Pack 2, I attempted to run CEICW because I realized there
were
a few ports that I had forgotten to open for access to the server.
CEICW opens up and I click on next to continue to options and it sits
there for 2 seconds and closes. No error message, warning or
anything.
I checked the event viewer and there were no error messages there
either. I'm stumped. If anyone knows that this is a problem and/or
how
to fix it, please advise. Thanks in advance.
-kenkcj
.
- Follow-Ups:
- Re: Windows Server 2003 SP2 causes CEICW to fail?
- From: Merv Porter [SBS-MVP]
- Re: Windows Server 2003 SP2 causes CEICW to fail?
- References:
- Windows Server 2003 SP2 causes CEICW to fail?
- From: kenkcj
- Re: Windows Server 2003 SP2 causes CEICW to fail?
- From: Merv Porter [SBS-MVP]
- Re: Windows Server 2003 SP2 causes CEICW to fail?
- From: kenkcj
- Re: Windows Server 2003 SP2 causes CEICW to fail?
- From: Merv Porter [SBS-MVP]
- Re: Windows Server 2003 SP2 causes CEICW to fail?
- From: kenkcj
- Re: Windows Server 2003 SP2 causes CEICW to fail?
- From: Merv Porter [SBS-MVP]
- Windows Server 2003 SP2 causes CEICW to fail?
- Prev by Date: Re: Introduce Terminal Server into a SBS2003 environment
- Next by Date: Re: vpn to server then remote desktop to client
- Previous by thread: Re: Windows Server 2003 SP2 causes CEICW to fail?
- Next by thread: Re: Windows Server 2003 SP2 causes CEICW to fail?
- Index(es):