Error 33808 in Windows event log
Created: 25 Apr 2011 | 6 comments
I'm having a similar problem to the one mentioned in this posting: https://www-secure.symantec.com/connect/forums/event-id-33808-error-occurred-while-processing-b2d-command
I'm running Backup Exec on SBS 2008. Every day, I get this error in the event log:
|
Event Details: An error occurred while processing a B2D command. Changer: Sector size > 1KB, reverting to buffered I/O (Computer path). Error=2048 For more information, click the following link: http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml |
This path is to a removable hard drive (REV drive). I get no errors from Backup Exec. Any suggestions?
Discussion Filed Under:
Comments
Hi, Does your Backup Exec
Hi,
Does your Backup Exec service account have full access to this drive in terms of permissions...?
Thanks!
If you find this is a solution, please mark it as such.
Yes, the Veritas user that
Yes, the Veritas user that all the services run under have full permissions on the drive.
Oddly, I even get this error on days when no backup runs to this device.
It occurs during service restart. The reason I restart the services daily is because of this: https://www-secure.symantec.com/connect/forums/restart-services
...OK, let's go a couple of
...OK, let's go a couple of steps back:
1. Which version of BE is this? If not BE 2010 at least, consider upgrading to this as it has better management of B2D and removable devices.
2. Have you run LiveUpdate, or updated your media server manually to make sure you are running the latest patches?
Thanks!
If you find this is a solution, please mark it as such.
1. BE 12.5 for Windows
1. BE 12.5 for Windows Servers Small Business Suite. (An upgrade is unlikely for money reasons)
2. It is completely patched and updated.
Mmm...found a TN on the
Mmm...found a TN on the Symantec site you might want to check out...
http://www.symantec.com/business/support/index?page=content&id=TECH130540
If you find this is a solution, please mark it as such.
Results: C:\Users\**>net
Results:
C:\Users\**>net helpmsg 2048
2048 is not a valid Windows network message number.
More help is available by typing NET HELPMSG 3871.
C:\Users\**g>net helpmsg 3871
*** is not a valid Windows network message number.
Would you like to reply?
Login or Register to post your comment.