none
Cannot Open Management Tab - DPM Exception RRS feed

  • Question

  • Hi Folks

    I am getting the following error coming up when I try and view the Management tab in DPM Admin Console.

    Problem signature:
    Problem Event Name: DPMException
    Problem Signature 01: DPM
    Problem Signature 02: 2.0.8868.0
    Problem Signature 03: mmc.exe
    Problem Signature 04: 6.1.7600.16385
    Problem Signature 05: System.Data.SqlClient.SqlException
    Problem Signature 06: System.Data.SqlClient.SqlConnection.OnError
    Problem Signature 07: D32419BB
    OS Version: 6.1.7600.2.0.0.272.7
    Locale ID: 2057

    Does anyone know what is causing this issue and have a suggested fix?

    This all started after a restore of a DPM DB that was on old 32bit hardware. It's now on 64bit hardware with new storage pool disks and everything appears to work apart from the inability to open the management tab, which is quite important if you want to do anything useful.

    I am running DPM 2007 SP1 with latest updates.

    If anyone could help I would be very grateful, I want to upgrade to DPM 2010 but i'm worried that the upgrade will fail unless I fix this issue first.

    TIA

    Adam

    Friday, April 1, 2011 5:04 PM

Answers

  • OK so I ignored this and just backed up the DB and went for the upgrade. Worked fine and all is ok now!

    Wow what an epic journey

    Thanks to Mike J (MSFT) who assisted with the upgrade steps!

    TIA

    Adam

     

    Friday, April 1, 2011 7:33 PM

All replies

  • Ok so it looks as though I am nearer to finding the root cause, but why it happened and how to fix easily I am not sure of.

    I found this in one of the DPM error logs:

    Server: xxxxxx\MS$DPM2007$
    0DF0 0FD4 04/01 17:13:37.172 12 Catalog.cs(954)   Message: Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the is operation.
    0DF0 0FD4 04/01 17:13:37.172 12 Catalog.cs(954)   Procedure: prc_Mon_Jobs_Get_ALL
    0DF0 0FD4 04/01 17:13:37.172 12 Catalog.cs(954)   Line: 96 FileName:; Method:ExecuteReader(); lineNo:0; ilOffset:7.
    0DF0 0FD4 04/01 17:13:37.172 12 Catalog.cs(954)   FileName:; Method:ExecuteJobsReader(); lineNo:0; ilOffset:293.
    0DF0 0FD4 04/01 17:13:37.172 12 Catalog.cs(954)   FileName:; Method:GetLibraryJobs(); lineNo:0; ilOffset:181.
    0DF0 0FD4 04/01 17:13:37.172 12 Catalog.cs(954)   FileName:; Method:Run(); lineNo:0; ilOffset:95.
    0DF0 0FD4 04/01 17:13:37.172 12 Catalog.cs(954)   FileName:; Method:ThreadStart(); lineNo:0; ilOffset:25.

    It looks as though the SQL Server setup has been installed as Latin1_General and the DPMBD is SQL_Latin1. I believe this is the problem, does anyone have a suggested fix for this?

    TIA

    Adam

    Friday, April 1, 2011 5:49 PM
  • OK so I ignored this and just backed up the DB and went for the upgrade. Worked fine and all is ok now!

    Wow what an epic journey

    Thanks to Mike J (MSFT) who assisted with the upgrade steps!

    TIA

    Adam

     

    Friday, April 1, 2011 7:33 PM