SBS 2003 / Windows Server 2003 Stuck at Applying computer settings / Symantec Antivirus for Exchange

[Guest Pedro CR]

SBS 2003 / Windows Server 2003 Stuck at Applying computer settings / Symantec Antivirus for Exchange

 

Hi

 

I am posting this hoping that you won't have to go through the truble I've already had

 

I was running sbs2003 (windows server 2003 + exchange 2003) fully patched to date (31 oct 07).

Also running Symantec Antivirus 10.1.6.6010 and Symantec Information Foundation Mail Security For Exchange v.6

 

However in the last 2 weeks the server crashed and when rebooted it was stuck (hung) at Applying Computer Settings.

I could, however boot in safe mode.

 

If I set all exchange services to disabled and also the Av for exchange, the server would boot up normally.

I would then go to the services pane, and start each of the exchange services. This worked the first time. I set the excange services to startup type Automatic and it worked for another 2 weeks.

 

This last time, however, it would boot if I disabled the exchange services but, as soon as I attempted to start Exchange Information Store the server would crash.

 

My solution was to use ESEUTIL to repair/restore the exchange databases.

At first I got acces denied erros. I solved them by giving full permissions to the Amdinistrator group on the folders where the Exchange files where.

I could finally get exchange up again.

 

----

 

Now to the most important part: Why these crashes happened

After further investigation I found out that I had set a Full Scan on Symantec Information Foundation Mail Security For Exchange v.6 to run every two weeks. The symantec AV crashed the server while doing this. This was the reason.

 

I have removed Symantec Information Foundation Mail Security For Exchange v.6 and installed version 5. Did not set up any Full Scan now. Just real time scanning.

 

Also If you install any of these version of Symantec AV for exchange MAKE SURE you follow the steps described in the article bellow, EVEN IF YOU DON'T EXPERIENCE THE SIMPTOMS DESCRIBED:

http://service1.symantec.com/support/ent-gate.nsf/docid/2004060213183054?Open&src=ent_gold_nam - The Symantec Mail Security service is stuck in a starting state

 

On the occasions that I did not do this I've had all sorts fo random problems with the servers. The most common are Noetwork and Dial-Up Connections not showing up or inaccessible. The network icons not showing up in the system tray. Unable to access network card (nic) properties through a UI.

Also several services may get stuck in a "Starting" state.

Another simptom would be the Antivirus for Exchange logging events reporting unexpected shutdowns.

and so on...

 

Hope this can help someone.

Pedro.

[Guest vidguide2@gmail.com]

Re: SBS 2003 / Windows Server 2003 Stuck at Applying computer settings / Symantec Antivirus for Exchange

 

Re: SBS 2003 / Windows Server 2003 Stuck at Applying computer settings / Symantec Antivirus for Exchange

 

On Nov 1, 12:39 pm, "Pedro CR" <pram...@n0.spam.sapo.pt> wrote:

> Hi

>

> I am posting this hoping that you won't have to go through the truble I've already had

>

> I was running sbs2003 (windows server 2003 + exchange 2003) fully patched to date (31 oct 07).

> Also running Symantec Antivirus 10.1.6.6010 and Symantec Information Foundation Mail Security For Exchange v.6

>

> However in the last 2 weeks the server crashed and when rebooted it was stuck (hung) at Applying Computer Settings.

> I could, however boot in safe mode.

>

> If I set all exchange services to disabled and also the Av for exchange, the server would boot up normally.

> I would then go to the services pane, and start each of the exchange services. This worked the first time. I set the excange services to startup type Automatic and it worked for another 2 weeks.

>

> This last time, however, it would boot if I disabled the exchange services but, as soon as I attempted to start Exchange Information Store the server would crash.

>

> My solution was to use ESEUTIL to repair/restore the exchange databases.

> At first I got acces denied erros. I solved them by giving full permissions to the Amdinistrator group on the folders where the Exchange files where.

> I could finally get exchange up again.

>

> ----

>

> Now to the most important part: Why these crashes happened

> After further investigation I found out that I had set a Full Scan on Symantec Information Foundation Mail Security For Exchange v.6 to run every two weeks. The symantec AV crashed the server while doing this. This was the reason.

>

> I have removed Symantec Information Foundation Mail Security For Exchange v.6 and installed version 5. Did not set up any Full Scan now. Just real time scanning.

>

> Also If you install any of these version of Symantec AV for exchange MAKE SURE you follow the steps described in the article bellow, EVEN IF YOU DON'T EXPERIENCE THE SIMPTOMS DESCRIBED:http://service1.symantec.com/support/ent-gate.nsf/docid/2004060213183...- The Symantec Mail Security service is stuck in a starting state

>

> On the occasions that I did not do this I've had all sorts fo random problems with the servers. The most common are Noetwork and Dial-Up Connections not showing up or inaccessible. The network icons not showing up in the system tray. Unable to access network card (nic) properties through a UI.

> Also several services may get stuck in a "Starting" state.

> Another simptom would be the Antivirus for Exchange logging events reporting unexpected shutdowns.

> and so on...

>

> Hope this can help someone.

> Pedro.

 

Actaully, if you had to run a ese repair on your mail store, wouldn't

it suggest the database developed an error when you had a power event,

and it was only showing up when accessed? (ie, by the full scan)

 

Also curious, why did you go back to vers 5? Couldn't you stay with 6

and just disable the full scan?

 

Did you try to do a full scan after repairing the database?

[Guest Pedro CR]

Re: SBS 2003 / Windows Server 2003 Stuck at Applying computer settings / Symantec Antivirus for Exchange

 

Re: SBS 2003 / Windows Server 2003 Stuck at Applying computer settings / Symantec Antivirus for Exchange

 

 

<vidguide2@gmail.com> escreveu na mensagem

news:1193882925.902886.257080@t8g2000prg.googlegroups.com...

> On Nov 1, 12:39 pm, "Pedro CR" <pram...@n0.spam.sapo.pt> wrote:

>> Hi

>>

>> I am posting this hoping that you won't have to go through the truble

>> I've already had

>>

>> I was running sbs2003 (windows server 2003 + exchange 2003) fully patched

>> to date (31 oct 07).

>> Also running Symantec Antivirus 10.1.6.6010 and Symantec Information

>> Foundation Mail Security For Exchange v.6

>>

>> However in the last 2 weeks the server crashed and when rebooted it was

>> stuck (hung) at Applying Computer Settings.

>> I could, however boot in safe mode.

>>

>> If I set all exchange services to disabled and also the Av for exchange,

>> the server would boot up normally.

>> I would then go to the services pane, and start each of the exchange

>> services. This worked the first time. I set the excange services to

>> startup type Automatic and it worked for another 2 weeks.

>>

>> This last time, however, it would boot if I disabled the exchange

>> services but, as soon as I attempted to start Exchange Information Store

>> the server would crash.

>>

>> My solution was to use ESEUTIL to repair/restore the exchange databases.

>> At first I got acces denied erros. I solved them by giving full

>> permissions to the Amdinistrator group on the folders where the Exchange

>> files where.

>> I could finally get exchange up again.

>>

>> ----

>>

>> Now to the most important part: Why these crashes happened

>> After further investigation I found out that I had set a Full Scan on

>> Symantec Information Foundation Mail Security For Exchange v.6 to run

>> every two weeks. The symantec AV crashed the server while doing this.

>> This was the reason.

>>

>> I have removed Symantec Information Foundation Mail Security For Exchange

>> v.6 and installed version 5. Did not set up any Full Scan now. Just real

>> time scanning.

>>

>> Also If you install any of these version of Symantec AV for exchange MAKE

>> SURE you follow the steps described in the article bellow, EVEN IF YOU

>> DON'T EXPERIENCE THE SIMPTOMS

>> DESCRIBED:http://service1.symantec.com/support/ent-gate.nsf/docid/2004060213183...-

>> The Symantec Mail Security service is stuck in a starting state

>>

>> On the occasions that I did not do this I've had all sorts fo random

>> problems with the servers. The most common are Noetwork and Dial-Up

>> Connections not showing up or inaccessible. The network icons not showing

>> up in the system tray. Unable to access network card (nic) properties

>> through a UI.

>> Also several services may get stuck in a "Starting" state.

>> Another simptom would be the Antivirus for Exchange logging events

>> reporting unexpected shutdowns.

>> and so on...

>>

>> Hope this can help someone.

>> Pedro.

>

> Actaully, if you had to run a ese repair on your mail store, wouldn't

> it suggest the database developed an error when you had a power event,

> and it was only showing up when accessed? (ie, by the full scan)

>

> Also curious, why did you go back to vers 5? Couldn't you stay with 6

> and just disable the full scan?

>

> Did you try to do a full scan after repairing the database?

>

 

Well I can't really tell you if it's the scan or the power event that cause

the eschange corruption.

The thing is that after the scan, the box crashes. You can't shut it down

from the UI. If you just press the power button once to force a windows

shutdown on the server it won't respond either.

So the only option is to press and hold the power button to turn off the

box.

So it's impossible to determine which causes the problem: the anti virus

<before> crashing the server or the fact that the server has to be rebooted

the hard way.

 

I did not stick with v6 because these facts tell me that it cannot be

trusted. At this moment I don't feel safe to assume that if I disable

scheduled scans no other problem will pop up.

I am running v5. It works. I've used it before without any major problem.

And it also uses less resources.