Re: upgrade from 30(3) - 31(3)

ajones · ‎05-02-2002

I have done all the needed service packs and hotfixes required.. I run the cd1 setup and it brings me through the licensing and then it says it is updating my configuration but shows no progress and Ive left it there for 30 minutes. I have stopped it and re ran it twice to no eval..any thoughts..? Amy Jones Senior Systems Analyst AAC Associates 703-918-6394

Anil Verma · ‎05-03-2002

Do you have any anit virus package running on the Unity server? We have seen this happen a lot when you have virus detection systems on the server. It can take upto 6 hours for Unity setup to complete as all the files we are putting on the drive are being verified by the anti virus software.
You can either wait for this to complete, or stop the anti virus services before you start the install/urgrade.

Anil Verma
Cisco Systems
anilve@cisco.com

ajones · ‎05-03-2002

I have no anti virus software on it at all.....any other thoughts...

Amy Jones
Senior Systems Analyst
AAC Associates
703-918-6394

Anil Verma · ‎05-03-2002

Check the tempu.log. See what was the last entry in there before you cancelled the setup.

Anil Verma
Cisco Systems
anilve@cisco.com

Report Inappropriate Content · ‎05-03-2002

These are the last few lines...It seems to me like it was working...but nothing was happening for me to see...should I just let it go...

Mode:Install, Step:KeypadMapStep [IDD_KEYPADMAP_SELECT] (e:\views\Unity3.1.2.41 un_Setup\UnitySetup\InstallExe\Src\MYSETUP.CPP 180)
2002-05-02T22:05:27 - Mode:Install, Step:SelectSwitchStep [IDD_SELECTSWITCH] (e:\views\Unity3.1.2.41\un_Setup\UnitySetup\InstallExe\Src\MYSETUP.CPP 185)
2002-05-02T22:05:27 - Commsvr is already installed. This step will not be displayed. (e:\views\Unity3.1.2.41\un_Setup\UnitySetup\InstallExe\Src\SelectSwitch.cpp 86)
2002-05-02T22:05:27 - Mode:Install, Step:ConfirmContinueStep [IDD_CONFIRM_CONTINUE] (e:\views\Unity3.1.2.41\un_Setup\UnitySetup\InstallExe\Src\MYSETUP.CPP 190)
2002-05-02T22:05:27 - Step 'CSetupStep' (106) modeless: 0 milliseconds (e:\views\Unity3.1.2.41\un_Setup\SetupEngine2\IWLib\src\step.cpp 910)
2002-05-02T22:05:28 - Mode:Install, Step:VersionMigration [IDD_VERSION_MIGRATION] (e:\views\Unity3.1.2.41\un_Setup\UnitySetup\InstallExe\Src\MYSETUP.CPP 195)
2002-05-02T22:05:29 - Launching version migration with command line: "E:\Migration\AvUpgradeData.exe" /Quiet /LogFile "C:\DOCUME~1\unity30\LOCALS~1\Temp\CommServer_05022002_220439\VersionMigration\Migration.log" /MigTable "E:\Migration\Migration.tbl" /SystemParms "C:\DOCUME~1\unity30\LOCALS~1\Temp\CommServer_05022002_220439\VersionMigration\Migration.prm" (e:\views\Unity3.1.2.41\un_Setup\UnitySetup\Common\Src\ConfigVerMig.cpp 125)

Anil Verma · ‎05-06-2002

Looks like the setup was trying to upgrade your SQL database. I am not sure what happenes now that you stopped it in the middle of the upgrade. It might be nice to involve TAC as they might need to look at the tables etc.

In the meantime, check the file
C:\DOCUME~1\unity30\LOCALS~1\Temp\CommServer_05022002_220439\VersionMigration\Migration.log

Looks like this was the file that the version migration was writing its log to. I saw the name of the file in the tempu.log statements you posted.

Anil Verma
Cisco Systems
anilve@cisco.com

Report Inappropriate Content · ‎05-08-2002

There were no Migration.log files and that is what tac wanted...I am going to try the migration again...

ajones · ‎05-15-2002

here is the Migration log.

InitializingObject:AvMigrateFailover.AvMigrateFailover.1
Failed to find element in registry:AvCsNodeMgrClientSupport.AvCsNodeMgrClientSupport\CurVer
InitializingObject:AvMigrateRuler.AvMigrateRuler.1
InitializingObject:AvMigrateScheduler.AvMigrateScheduler.1
InitializingObject:AvMigrateDsadSvr.AvMigrateDsad.1
*** Verifying ***
Verifying Object:AvMigrateFailover.AvMigrateFailover.1
Enter: Old version[0,0,0,0] New version[3,1,2,33] LogFile[C:\DOCUME~1\unity30\LOCALS~1\Temp\AVU467.tmp] SysParms[0x00BB5068]
Exit: hr[0x00000000]
Verifying Object:AvMigrateRuler.AvMigrateRuler.1
Enter: Old version[2,5,0,72] New version[3,1,2,76] LogFile[C:\DOCUME~1\unity30\LOCALS~1\Temp\AVU468.tmp] SysParms[0x00BB5068]
Executing Verify3_1_74()...
Exit: hr[0x00000000]
Verifying Object:AvMigrateScheduler.AvMigrateScheduler.1
Enter: Old version[2,5,0,21] New version[3,1,2,24] LogFile[C:\DOCUME~1\unity30\LOCALS~1\Temp\AVU469.tmp] SysParms[0x00BB5068]
Executing Verify3_1_22()...
Exit: hr[0x00000000]
Verifying Object:AvMigrateDsadSvr.AvMigrateDsad.1
Unable to locate ProgID key: AvMigrateDsad.AvMigrateDsad\CurVer
Enter: Old version[3,0,2,33] New version[0,0,0,0] LogFile[C:\DOCUME~1\unity30\LOCALS~1\Temp\AVU46A.tmp] SysParms[0x0015AF74]
Executing Upgrade2_5_29()...
Validating Registry
Validating registry for aac.com
Validating Registry Done
Validating Monitor Object Table
Validating Monitor Object Table Done
Executing DN to GUID migration...
ADsGetObject(LDAP://CN=Mailbox Store (VATCVM01),CN=First Storage Group,CN=InformationStore,CN=VATCVM01,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=Unity,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=aac,DC=com) in ConvertDnToGuid failed: 80072030
Verify for DN to GUID migration failed: 80072030
Exit: hr[0x80072030]
*** Failed Verification ***

Amy Jones
Senior Systems Analyst
AAC Associates
703-918-6394