Announcement

Collapse
No announcement yet.

event id 2038

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • event id 2038

    Hi all,

    I encountered this problem every night after my scheduled backup ( we are using wbadmin.exe ) has completed. It appeared 7 times in the application log, which coincide with the number of storage group I have. Naturally, the logs are not truncated and hence filling up my drive.

    It all began after we have rebuilt our passive node Exchange 2007 server. We are running on W2008 Ent 64-bit with sp2 and the Exchange 2007 is also on sp2. The same configuration also applies to the active node of the CCR configuration.


    Any advice how to get rid of this error?

    Thanks

  • #2
    Re: event id 2038

    You need to post the full text of the error. Code on its own is useless.

    Also Exchange 2007 Sp2 is very old. Strongly suggest upgrading to SP3 with rollup 10.

    Simon.
    --
    Simon Butler
    Exchange MVP

    Blog: http://blog.sembee.co.uk/
    More Exchange Content: http://exchange.sembee.info/
    Exchange Resources List: http://exbpa.com/
    In the UK? Hire me: http://www.sembee.co.uk/

    Sembee is a registered trademark, used here with permission.

    Comment


    • #3
      Re: event id 2038

      Originally posted by Sembee View Post
      You need to post the full text of the error. Code on its own is useless.

      Also Exchange 2007 Sp2 is very old. Strongly suggest upgrading to SP3 with rollup 10.

      Simon.
      Oops...sorry.

      The following is the error I draw from the application log of my passive node.

      "...Log Name: Application
      Source: MSExchangeRepl
      Date: 7/24/2013 7:00:47 PM
      Event ID: 2038
      Task Category: Exchange VSS Writer
      Level: Warning
      Keywords: Classic
      User: N/A
      Computer: mailbx1.teleport.com
      Description:
      The Microsoft Exchange VSS Writer (instance 8930efcf-7269-4345-abe0-70a6c4d19a41) backup failed for storage group 'eb5da43c-0340-40b8-bf56-77cf33606c44'. No log files were truncated.
      ....."

      It appear 4 times. I suspect it has to do with storage groups but I cannot lay a finger on it what is causing this.

      I am kinda of wary of upgrading up to sp3 as we have not fully tested the patch yet in our test environment.

      Any advice how to overcome this is deeply appreciated.

      Thanks

      Comment


      • #4
        Re: event id 2038

        I would have to say that you need to upgrade to Exchange 2007 SP3 first, as you are using the native VSS writers and are not on the latest version.

        Simon.
        --
        Simon Butler
        Exchange MVP

        Blog: http://blog.sembee.co.uk/
        More Exchange Content: http://exchange.sembee.info/
        Exchange Resources List: http://exbpa.com/
        In the UK? Hire me: http://www.sembee.co.uk/

        Sembee is a registered trademark, used here with permission.

        Comment


        • #5
          Re: event id 2038

          Originally posted by ericwi View Post

          I am kinda of wary of upgrading up to sp3 as we have not fully tested the patch yet in our test environment.

          Any advice how to overcome this is deeply appreciated.

          Thanks
          in concert with what simon said - test your backup and ensure it works in your test environment and that it's truncating logs and abcking up exchange successfully

          then apply SP3 - you'll know you have a rollback point if you need to because your backups work.
          Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

          Comment

          Working...
          X