OK, I have spent several days working on this. We are preparing to 
migrate to DPM 2010. This is what I understand:

We have Windows Server 2003 R2 x86 installed with DPM 2007. DPM 2010 is 
x64 only so the migration path is:

Migrate to DPM 2007 x64 and then upgrade DPM 2007 x64 to DPM 2010 - 
correct?

We prepared a test environment with Win 2003 R2 x86 + DPM 2007 and 
another server as Win 2008 R2 x64.

We managed to carry out all steps in test environment but had a problem 
when running the DPM management console GUI. This was crashing due to 
different SQL collations (we were not paying attention and the Win 2003 
R2 server was set as U.S locale while 2008 R2 was U.K locale).

Now in our production environment all locales are correct (U.K) and we 
checked that the collations are correct. Our problem is that dpmsync -
sync is failing in our production environment after restoring the DPM 
database using dpmsync -dbrestore. Logs show errors as follows:

Attempting to write error to the event log DataSourceInfo: bad column 
count in result 
set:Microsoft.Internal.EnterpriseStorage.Dls.DB.DBCorruptionException: 
DataSourceInfo: bad column count in result set
at Microsoft.Internal.EnterpriseStorage.Dls.DB.Catalog.IntegrityCheck
(Boolean condition, String message)
at 
Microsoft.Internal.EnterpriseStorage.Dls.PRMCatalog.DataSourceInfo.GetDa
taSourceInfo(SqlContext ctx, Guid datasourceIdLocal)
at 
Microsoft.Internal.EnterpriseStorage.Dls.PRMCatalog.Replica.Replica.GetA
llLogicalReplicaOnPhysicalReplica(DbContext ctx, Guid physicalReplicaId, 
Boolean readOnlyActiveReplica)
at 
Microsoft.Internal.EnterpriseStorage.Dls.PRMCatalog.PrmCatalog.GetAllLog
icalReplicaOnPhysicalReplica(Guid physicalReplicaId, Boolean 
readOnlyActiveReplica)
at 
Microsoft.Internal.EnterpriseStorage.Dls.PRMCatalog.PrmCatalog.RaiseRepl
icaStatusAlertsOnReplicaRefresh(Guid physicalReplicaIdPassed)
at 
Microsoft.Internal.EnterpriseStorage.Dls.Prm.Alerts.AlertsHelper.RaiseRe
plicaStatusAlertsOnReplicaRefresh(Guid physicalReplicaIdPassed)
at 
Microsoft.Internal.EnterpriseStorage.Dls.PRMCatalog.PrmCatalog.RefreshRe
plica(Guid replicaIdPassed, Boolean onStartup)
at 
Microsoft.Internal.EnterpriseStorage.Dls.Rhl.ReplicaAreaSetManagerHelper
..InternalRefresh(Boolean onStartup)
at 
Microsoft.Internal.EnterpriseStorage.Dls.Rhl.ReplicaAreaSetManagerHelper
..Refresh()
at 
Microsoft.Internal.EnterpriseStorage.Dls.Intent.IT.IntentTranslator.Inte
ntRestart()


A different error appears on the command line after dpmsync fails (note 
that the DPM service crashes every time this is attempted due to these 
errors):


C:\Users\administrator>dpmsync -sync
DpmSync 2.0 - DPM database synchronization command-line tool
Copyright (c) 2007 Microsoft Corporation. All rights reserved.


Unhandled Exception: System.Runtime.InteropServices.COMException 
(0x800706BE): The remote procedure call failed. (Exception from HRESULT: 
0x800706BE)
   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal
(Int32 errorCode, IntPtr errorInfo)
   at 
icrosoft.Internal.EnterpriseStorage.Dls.Engine.CProxyUtils.HandleErrors
(Int32 hr, tagSAFEARRAY* exceptionResult)
   at 
Microsoft.Internal.EnterpriseStorage.Dls.Engine.RestoreDbSyncServicesPro
xy.RestoreDbSynchronize(Boolean reallocateReplica, Boolean* 
isExternalVolumeMissing)
   at 
Microsoft.Internal.EnterpriseStorage.Dls.Engine.CoreServicesProxy.Restor
eDbSynchronize(Boolean reallocateReplica, Boolean& 
isExternalVolumeMissing)
   at 
Microsoft.Internal.EnterpriseStorage.Dls.RestoreDbSync.RestoreDbSync.Syn
cFunction(Boolean reallocateReplica, Boolean& isExternalVolumeMissing)
   at 
Microsoft.Internal.EnterpriseStorage.Dls.RestoreDbSync.RestoreDbSync.Mai
n(String[] args)



Can anyone decipher these messages? DPM and SQL versions and service 
packs are the same. 


-- 
Regards,

R


--- news://freenews.netfront.net/ - complaints: news@netfront.net ---

In article <MPG.267a9156c17f22c6989683@freenews.netfront.net>, 
R@dontmailme.net says...
> 
> OK, I have spent several days working on this. We are preparing to 
> migrate to DPM 2010. This is what I understand:
> 
> We have Windows Server 2003 R2 x86 installed with DPM 2007. DPM 2010 is 
> x64 only so the migration path is:
> 
> Migrate to DPM 2007 x64 and then upgrade DPM 2007 x64 to DPM 2010 - 
> correct?
> 
> We prepared a test environment with Win 2003 R2 x86 + DPM 2007 and 
> another server as Win 2008 R2 x64.
> 
> We managed to carry out all steps in test environment but had a problem 
> when running the DPM management console GUI. This was crashing due to 
> different SQL collations (we were not paying attention and the Win 2003 
> R2 server was set as U.S locale while 2008 R2 was U.K locale).
> 
> Now in our production environment all locales are correct (U.K) and we 
> checked that the collations are correct. Our problem is that dpmsync -
> sync is failing in our production environment after restoring the DPM 
> database using dpmsync -dbrestore. Logs show errors as follows:
> 
> Attempting to write error to the event log DataSourceInfo: bad column 
> count in result 
> set:Microsoft.Internal.EnterpriseStorage.Dls.DB.DBCorruptionException: 
> DataSourceInfo: bad column count in result set
> at Microsoft.Internal.EnterpriseStorage.Dls.DB.Catalog.IntegrityCheck
> (Boolean condition, String message)
> at 
> Microsoft.Internal.EnterpriseStorage.Dls.PRMCatalog.DataSourceInfo.GetDa
> taSourceInfo(SqlContext ctx, Guid datasourceIdLocal)
> at 
> Microsoft.Internal.EnterpriseStorage.Dls.PRMCatalog.Replica.Replica.GetA
> llLogicalReplicaOnPhysicalReplica(DbContext ctx, Guid physicalReplicaId, 
> Boolean readOnlyActiveReplica)
> at 
> Microsoft.Internal.EnterpriseStorage.Dls.PRMCatalog.PrmCatalog.GetAllLog
> icalReplicaOnPhysicalReplica(Guid physicalReplicaId, Boolean 
> readOnlyActiveReplica)
> at 
> Microsoft.Internal.EnterpriseStorage.Dls.PRMCatalog.PrmCatalog.RaiseRepl
> icaStatusAlertsOnReplicaRefresh(Guid physicalReplicaIdPassed)
> at 
> Microsoft.Internal.EnterpriseStorage.Dls.Prm.Alerts.AlertsHelper.RaiseRe
> plicaStatusAlertsOnReplicaRefresh(Guid physicalReplicaIdPassed)
> at 
> Microsoft.Internal.EnterpriseStorage.Dls.PRMCatalog.PrmCatalog.RefreshRe
> plica(Guid replicaIdPassed, Boolean onStartup)
> at 


I will also post on DPM technet forum as requested!

Thanks!


-- 
Regards,

R

--- news://freenews.netfront.net/ - complaints: news@netfront.net ---

Reg. different collations of SQL have you installed SQL outside of DPM setup 
or the instance is installed by DPM.


-- 
Thanks
Venkata Praveen[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights.


"R" <R@dontmailme.net> wrote in message 
news:MPG.267a952ff1e9fe40989684@freenews.netfront.net...
> In article <MPG.267a9156c17f22c6989683@freenews.netfront.net>,
> R@dontmailme.net says...
>>
>> OK, I have spent several days working on this. We are preparing to
>> migrate to DPM 2010. This is what I understand:
>>
>> We have Windows Server 2003 R2 x86 installed with DPM 2007. DPM 2010 is
>> x64 only so the migration path is:
>>
>> Migrate to DPM 2007 x64 and then upgrade DPM 2007 x64 to DPM 2010 -
>> correct?
>>
>> We prepared a test environment with Win 2003 R2 x86 + DPM 2007 and
>> another server as Win 2008 R2 x64.
>>
>> We managed to carry out all steps in test environment but had a problem
>> when running the DPM management console GUI. This was crashing due to
>> different SQL collations (we were not paying attention and the Win 2003
>> R2 server was set as U.S locale while 2008 R2 was U.K locale).
>>
>> Now in our production environment all locales are correct (U.K) and we
>> checked that the collations are correct. Our problem is that dpmsync -
>> sync is failing in our production environment after restoring the DPM
>> database using dpmsync -dbrestore. Logs show errors as follows:
>>
>> Attempting to write error to the event log DataSourceInfo: bad column
>> count in result
>> set:Microsoft.Internal.EnterpriseStorage.Dls.DB.DBCorruptionException:
>> DataSourceInfo: bad column count in result set
>> at Microsoft.Internal.EnterpriseStorage.Dls.DB.Catalog.IntegrityCheck
>> (Boolean condition, String message)
>> at
>> Microsoft.Internal.EnterpriseStorage.Dls.PRMCatalog.DataSourceInfo.GetDa
>> taSourceInfo(SqlContext ctx, Guid datasourceIdLocal)
>> at
>> Microsoft.Internal.EnterpriseStorage.Dls.PRMCatalog.Replica.Replica.GetA
>> llLogicalReplicaOnPhysicalReplica(DbContext ctx, Guid physicalReplicaId,
>> Boolean readOnlyActiveReplica)
>> at
>> Microsoft.Internal.EnterpriseStorage.Dls.PRMCatalog.PrmCatalog.GetAllLog
>> icalReplicaOnPhysicalReplica(Guid physicalReplicaId, Boolean
>> readOnlyActiveReplica)
>> at
>> Microsoft.Internal.EnterpriseStorage.Dls.PRMCatalog.PrmCatalog.RaiseRepl
>> icaStatusAlertsOnReplicaRefresh(Guid physicalReplicaIdPassed)
>> at
>> Microsoft.Internal.EnterpriseStorage.Dls.Prm.Alerts.AlertsHelper.RaiseRe
>> plicaStatusAlertsOnReplicaRefresh(Guid physicalReplicaIdPassed)
>> at
>> Microsoft.Internal.EnterpriseStorage.Dls.PRMCatalog.PrmCatalog.RefreshRe
>> plica(Guid replicaIdPassed, Boolean onStartup)
>> at
>
>
> I will also post on DPM technet forum as requested!
>
> Thanks!
>
>
> -- 
> Regards,
>
> R
>
> --- news://freenews.netfront.net/ - complaints: news@netfront.net --- 

In article <BDD9AF21-FC0F-43BC-906D-AC155FE84AAB@microsoft.com>, 
vborra@microsoft.com says...
> 
> Reg. different collations of SQL have you installed SQL outside of DPM setup 
> or the instance is installed by DPM.

SQL is installed by DPM

-- 
Regards,

R

--- news://freenews.netfront.net/ - complaints: news@netfront.net ---