Re: Error code 0x50d when preparing for backup.

Tech-Archive recommends: Fix windows errors by optimizing your registry



Hi M.T.



I remember someone else recently posting a similar problem but with Veritas,
they said the error was resolved after a reboot. I think they might be
related because both cases are using the MS VSS provider.



Are there any errors in the Event log?


Regards
Ben Hoffman
MCP (Win2000 Pro/Server & Exchange 2003 Admin)
http://www.ExchangeIS.com

"M. T." <MT@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E5FC0770-48E1-48A5-97F3-56A2B17337C0@xxxxxxxxxxxxxxxx
> We are running Exchange 2003 on Windoes 2003 server. We are receiving
> error
>
> "Error code 0x50d when preparing for backup." in our event log.
>
> The error is coming after information "Exchange VSS Snapshot metadata
> document has been collected. "
>
> What can we do to fix this error.
>
> Thanking you in anticipations.
>
> Regards
> M.T.


.



Relevant Pages

  • Re: Wont remote re-boot
    ... Regards ... Anything recorded in the system event log? ... site and it came up with a blue screen Bugcheck. ... shutdown if you can't get a normal, ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: Error : the certificate cannot be installed because of problem with the cryptographic hardware
    ... Please paste the full event log for that error here. ... >> Hi Michel, ... >> Regards, ... >> Jeff Qiu ...
    (microsoft.public.win2000.security)
  • Re: Disks take long time to bring online if failover
    ... No chkDsk_...log found, no logs in the event log, could not find out any ... Regards ... George ... >> Here are the files in the Cluster directory, ...
    (microsoft.public.windows.server.clustering)
  • RE: Event 9539 - Exchange 2003 Enterprise
    ... > the NOS partition and 75GB Free on the Exchange partition. ... > I checked the Event log and received several Event IDs at the time we lose ... > The second makes sense since the database store has stopped. ... > regards to 9539...there are no other codes that would indicate the database ...
    (microsoft.public.exchange.connectivity)