Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 1 subscriber
  • Views 4937 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Enterprise Console 5 Server migration problems

corkdood
I have been attempting to migrate sophos enterprise console 5 from a 32bit server 2003 platform to a 64bit server 2008 platform.
 
I followed the steps in the server to server migration guide. The only issues encountered were during point 10.1
net start "sophos patch endpoint communicator"
net start "sophos management host"
net start "sophos patch endpoint orchestrator"
All 3 commands above produced an error message - 'Did not start due to a logon failure'
 
Furthermore when I got to point 12 (configure updating policy) and double clicked an updating policy the following message was displayed.
 
An unexpected error has occurred. Click the 'advanced' button for information which you can send to sophos tech support.
close the console and open it again.
 
Clicking advanced displayed the text below with a message to email it to sophos for assistance which I have done - no response yet. Please advise what I need to do to rectify the problem.
 
Sophos.Management.GeneralException: SQL error: 468 ---> System.Data.SqlClient.SqlException: Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
   at System.Data.SqlClient.SqlDataReader.get_MetaData()
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior)
   at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
   at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
   at System.Data.Common.DbDataAdapter.Fill(DataTable[] dataTables, Int32 startRecord, Int32 maxRecords, IDbCommand command, CommandBehavior behavior)
   at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)
   at Sophos.Management.Data.GeneralCommand.ExecuteAndReturnDataTableImpl()
   --- End of inner exception stack trace ---
   at Sophos.Management.Data.SPErrorHandler.AnalyseAndConvertException(Exception e)
   at Sophos.Management.Data.GeneralCommand.ExecuteAndReturnDataTableImpl()
   at Sophos.Management.Data.Utils.ExecuteAndHandleTransientErrors(ISqlConnectionContext scc, MethodThatMayThrowTransientError methodToCall)
   at Sophos.Management.Data.GeneralCommand.ExecuteAndReturnDataTable()
   at Sophos.Management.Data.GeneralCommand.ExecuteAndReturnDataRowImpl()
   at Sophos.Management.Data.Utils.ExecuteAndHandleTransientErrors(ISqlConnectionContext scc, MethodThatMayThrowTransientError methodToCall)
   at Sophos.Management.Data.GeneralCommand.ExecuteAndReturnDataRow()
   at Sophos.Management.Data.CrudPersister.ExecuteAndReturnDataRow(GeneralCommandMetadata commandMetadata)
   at Sophos.Management.Data.Sddma.SddmServerSql.GetSubscriptionData()
   at Sophos.Management.Data.Sddma.Dali.ServerDao.GetSubscriptionData()
   at Sophos.Management.Services.Sddma.SubscriptionDataProvider.FetchSubscriptionData()
   at Sophos.Management.Services.Sddma.SubscriptionDataProvider.GetSubscriptionData()
   at Sophos.Management.Services.Sddma.SubscriptionDataProvider.GetLocationsForSubscriptionPolicy(ISubscriptionPolicy subscriptionPolicyArg)
 
----- [outer exception] -----
   -- error: 0x80040300
   -- facility: Custom (Defined by the interface)
 
   at 2
   at 1
   at void __cdecl `anonymous-namespace'::GetDistributionSites(const class ATL::CComPtr<struct Sophos_Management_Sddma::ISubscriptionPolicy> &,struct Sophos_Management::IUnitOfWork *,class LocationList &)
   at void __thiscall SauConfigData::GetDistributionSitesForCurrentSubscription(class LocationList &)
   at void __thiscall SauConfigPrimarySourcePage::RefreshAvailableDistributions(void)
   at int __thiscall SauConfigPrimarySourcePage::OnSetActive(void)
   at 1
   at void __thiscall PolicyDialogViewer::ShowPolicy(struct ISMT_Policy *,class ATL::CWindow,const class bl::UIPermissions &,unsigned long,const class ProductReleaseData &,const class TranslationService &)
   at __w64 long __thiscall CPolicyTreeCtrl::OnEditPolicy(unsigned int,__w64 unsigned int,__w64 long,int &)
   at int __cdecl Run(int,class bl::CommandLine,enum bl::ConsoleType::Type)
   at int __stdcall wWinMain(struct HINSTANCE__ *,struct HINSTANCE__ *,wchar_t *,int)
 
:23989


This thread was automatically locked due to age.
Parents
  • 0

    Hi,

    The configure updating policy error is due to a mismatched SQL collation.  The collation of the database needs to be the same on both servers.  I suspect, that the collation is different maybe because the locale has changed from server to server.  

    You will need to uninstall the SQL instance on the new server and ensure that the SQL instance is created with the same collation.

    I would suggest it is probably easier to start again on the new server and check the collation on the original server first.  This command will do:

    sqlcmd -E -S .\sophos -Q "SELECT DATABASEPROPERTYEX('SOPHOS50', 'Collation') SQLCollation;" > 1.txt

    or install SQL server Management Studio on a machine and connect to the instance to check it.

    Then on the new server, manually run the installer of SQL Express, you may as well install SQL 2008 R2 Express, you can then choose the same collation during install.  You can get it from here:
    http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=3743
    Maybe create the same named SQL instance (the default is SOPHOS). 

    As for the account problem, I assume the account specified in the logon tab of the services can logon to the machine?  Maybe come back to this after retrying the migration.

    Regards,

    Jak

    :23991
Reply
  • 0

    Hi,

    The configure updating policy error is due to a mismatched SQL collation.  The collation of the database needs to be the same on both servers.  I suspect, that the collation is different maybe because the locale has changed from server to server.  

    You will need to uninstall the SQL instance on the new server and ensure that the SQL instance is created with the same collation.

    I would suggest it is probably easier to start again on the new server and check the collation on the original server first.  This command will do:

    sqlcmd -E -S .\sophos -Q "SELECT DATABASEPROPERTYEX('SOPHOS50', 'Collation') SQLCollation;" > 1.txt

    or install SQL server Management Studio on a machine and connect to the instance to check it.

    Then on the new server, manually run the installer of SQL Express, you may as well install SQL 2008 R2 Express, you can then choose the same collation during install.  You can get it from here:
    http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=3743
    Maybe create the same named SQL instance (the default is SOPHOS). 

    As for the account problem, I assume the account specified in the logon tab of the services can logon to the machine?  Maybe come back to this after retrying the migration.

    Regards,

    Jak

    :23991
Children
No Data