Dell PowerEdge 2850 crashes when backup starts



Hello!

After the server rebooted from the crash, Internet Explorer opened to the
Microsoft Online Crash Analysis page, which indicated Symantec is aware of a
problem with the symevent.sys file that causes crashes. Microsoft indicated
that Symantec has no known fix yet.

Here are the details.

We just did a fresh SBS 2003 Standard installation (created RAID 1 mirror,
booted from SBS CD, deleted C:\ partition but left roughly 32MB diag
partition, formatted and installed on new C: partition) on a new Dell
PowerEdge 2850, dual Xeon, 4GB RAM, two 73GB SCSI drives hardware mirrored,
Dell external PowerVault 110T SCSI tape backup, which is actually a Certance
Ultrium LTO 2 drive, Adaptec ASC-29320LP SCSI card for the tape unit.

We have all the patches, except SP1 is not installed for the OS or for SBS
2003. We have the updated storport.sys driver per KB article
http://support.microsoft.com/default.aspx?scid=kb;en-us;883646.

Software is:

Small Business Server 2003 Standard, not SP1
Veritas Backup Exec 9.4691.1 SP2
Veritas tape driver: latest file downloaded, driver "halfinch.sys" version
5.0.1.1, 11/1/2004 date (drive was not recognized with Dell driver)
Symantec Antivirus Corporate Edition 10.0.1.1000, scan engine 51.1.0.15
(latest downloaded version)
Symantec Mail Security 4.6.1.107 (latest downloaded version)

The crash has happened several times almost immediately after the backup
starts.

What is the issue with the symevent.sys file (version 11.6.2.4 that came
with SAVCE 10.0.1.1000) that Symantec knows about and what is the workaround
to keep our brand new server from crashing?

Is this a SAVCE problem or a Backup Exec problem?

Thank you!

Gregg Hill


.



Relevant Pages

  • Cancel IO problems on Server 2003
    ... I have an old monolithic driver that works OK on NT 4.0 and Win 2000 ... I have included a crash dump. ... An API library ... This all works OK on NT 4.0, Win2k and also 2003 Server. ...
    (microsoft.public.development.device.drivers)
  • Re: Going crazy over this one!
    ... You could use the firewall that is built-in to Windows Server 2003. ... tab place a check next to Remote Desktop adn verify you can still connect. ... As for the "NVIDIA Display Driver Service" service causing this problem with ... > I thought, "what the heck -- this must be Symantec, then"! ...
    (microsoft.public.windows.terminal_services)
  • Re: How to Troubleshoot Poor Terminal Server Performance and Reliablity
    ... >> we're up to date with all the drivers, firmware, BIOS updates, etc... ... >> crash dump file and see if I can at least tie the crashes to a specific ... >> driver or service. ... >>> Is there anything in the EventLog on the server? ...
    (microsoft.public.windows.terminal_services)
  • Re: HELP!!!!!! BSOD on customer ws2003sbs
    ... huge Symantec fan, so I'm always happy to have the blame fall on them; ... > wisdom updated the symevent.sys driver. ... All the previous server ... > tell Microsoft and as a result the updated driver you download when ...
    (microsoft.public.windows.server.sbs)
  • Re: HELP!!!!!! BSOD on customer ws2003sbs
    ... it turns out that Symantec in their ... wisdom updated the symevent.sys driver. ... All the previous server installations ...
    (microsoft.public.windows.server.sbs)

Quantcast