I've had similar problems to Ninon, on an IBM Server with IBM Raid, Windows 2003 and Veritas 9.1 with blue screens seemingly caused by ssrtln.sys which on searching the web has been linked to Veritas.
My problem seems to be fixed now, and am not entirely sure what caused it, but I updated all the RAID Bios and firmware to the latest version (as well as the 2003 Windows driver), updated the server BIOS, and then reinstalled Windows 2003. Then I reinstalled Veritas, just the server program itself first, followed by the OFO and then other agents, each with a reboot inbetween to check for blue screens. The only difference was that I did NOT install the Veritas tape drivers or Robotic library support, as advised http://seer.support.veritas.com/docs/261728.htm
I also had the Network Load Balancing problem and the solution provided by Veritas worked.
It may be a combination of all these things, but fingers crossed, no blue screens since.
Hope this helps.
Joanne
Quote:
Originally posted by Ninon Chassé
Hello Afzal,
For the Network Load Balancing, Veritas has a 'solution':
http://seer.support.veritas.com/docs/263037.htm
As for the BSOD, Veritas told me to follow their solution #26178 (see below)
however it didn't work for me as the Server gave me a BugCheck 0x50 followed
by a restart as soon as I tried to downgrade the IBM RAID 5i Controller card
divers to the 2000 version. The Server crashed again when I tried to
installed Veritas BackupExecTapeDeviceDriverInstall_268088.exe file. In the
end I gave up and uninstalled Backup Exec, the LTO tape drive and Adaptec
SCSI card to another Server. The Server that is now hosting Backup Exec is
behaving normally. The Server that has the IBM RAID controller has been
restarted only twice since I removed Backup Exec and it hasn't Blue
Screened. It's a bit early to confirm that removing Backup Exec from that
Server has solved the problem but I'm hoping. This Server is in production
hosting Exchange as well as the users' files so it is not restarted often
(once a month usually).
http://seer.support.veritas.com/docs/261728.htm
Did you, like me, installed the Microsoft hotfix from KB832336?
http://support.microsoft.com/default...uct=winsvr2003
Veritas has washed their hands on my issue saying that the crashes were
caused by a Microsoft file NTOSKRNL.EXE which is included in the KB832336
but I'm not so sure... My feeling is that the IBM RAID controller 2000
drivers are not fully compatible with Windows 2003 and Veritas Backup Exec
isn't compatible with IBM RAID controller 2003 drivers. So in my book,
Veritas isn't totally compatible with Windows 2003!
I don't know what type of business your running and what you have installed
on your Server but I would try the following:
1. Contact Veritas (if you haven't bought support use e-mail support it's
free and available on their website) to find out if they have a solution for
your Server as you may not have the same hardware as me. Plus, I'm running
Windows 2003 Standard while you're using SBS 2003. They are not exactly the
same.
2. If their solution doesn't work and do not have a space machine to do
your backup and host Backup Exec (you would also need a Remote Agent for
Windows Server license) switch to NTBackup. NTBackup comes with Windows
2003 and it's free. But you'll have to make sure it can do what you need in
term of backup. I used NTBackup for a few weeks and it did a great job
waiting for the Remote Agent license. If it hadn't been for the fact that I
want to backup individual mailboxes I would have stay with NTBackup.
I haven't uninstalled the Microsoft hotfix as I'm waiting to see how the
next reboot will go. If the Server Blue Screen again I'll try to remove it
and say how that goes. But this will have to wait for about 10 days as I'm
taking some time off.
Best of luck and keep me posted; I'll do the same
Ninon
"afzaldhanji" <afzaldhanji.1ahlin@mail.mcse.ms> wrote in message
news:afzaldhanji.1ahlin@mail.mcse.ms...
>
> Hi Ninon,
>
> I installed Veritas Backup Exec 9.1 on a Windows 2003 SBS server, I am
> getting the exact same blue screen when I reboot and the same NLB error
> at startup. How did you manage to resolve your problem?
>
> Thanks
> Afzal Dhanji
>
> Ninon Chassé wrote:
>
>
>
> --
> afzaldhanji
> ------------------------------------------------------------------------
> Posted via http://www.mcse.ms
> ------------------------------------------------------------------------
> View this thread: http://www.mcse.ms/message883720.html
>
|
Cell Phones reviews
07-21-04, 10:15 PM
MS Hotfix issues
Linear Mode
