Unity Issue

[jamied]

When trying to run the message store configuration wizard I am getting the following error. Failure encountered while synchronizing the SQL database with the mail store. hr=0x80070433.

The partner Exchange server is running Exchange 5.5.

Unity has just been upgraded from 3.1.4 to 4.0.4.

Any ideas?

[kechambe]

What do you see in the application log?

You can gather further data doing this:

-Turn on the DSEx55 traces in the Unity Diagnostic Tool under micro traces.

-Click 'Start New Log Files'

-From command line run:

c:\commserver\configurationsetup\setup.exe /sync. Reply c with whatever drive you installed Unity on. This will run the synker again.

Once it is done "Gather Log Files' -> 'Select Logs' -> 'AvDS55'. Get the last log file and try to post it out here. Or if it is critical and you open a case give it to the engineer.

Thanks,

Keith

[jamied]

Info from Log file is:

20:59:09:355,-1,-1,-1,-1,LogMgr,-1,diag Diag file opened 2004-10-05 20:59:09

20:59:09:355 (AvDiagnostics_MC,1152,-1,-1) [Thread 1980] LOGMGR OPENNEXTDIAGFILE d:\CommServer\logs\diag_AvDSEx55_20041005_205909.txt

20:59:09:356 (CiscoUnity_LogMgr,1004,-1,-1) [Thread 1980] AvDSEx55 opened new diagnostic file d:\CommServer\logs\diag_AvDSEx55_20041005_205909.txt. (null)

20:59:09:370 (AvDiagnostics_MC,1141,-1,-1) [Thread 1980] LOGMGR INITIALIZE

20:59:09:371 (AvDiagnostics_MC,1142,-1,-1) [Thread 1980] LOGMGR RUN

20:59:10:198,-1,-1,-1,-1,LogMgr,-1,diag Diag file closed 2004-10-05 20:59:10

[Hin Lee]

This log looks a bit "thin". Are you sure you have micro traces turned on for AvDsEx55?

H. M.

[jamied]

Running SYS Check returns the following errors:

Failure Doh Trying to find the Doh. Unexpected Error Occured in e:\views\cs_ue4.0.3.159\un_Doh2\SysCheck\DohTests\GetTheDoh.cpp, line: 45, hr = : HRESULT 0x80004005 Contact Technical Support.

Failure Doh Check call routing rules Property Not Found or Corrupted in e:\views\cs_ue4.0.3.159\un_Doh2\SysCheck\DohTests\CheckRoutingRules.cpp, line: 136, hr = : HRESULT 0x80043200 Check client code if property is being set.

[jamied]

Worked through this with TAC. Problems were related to an incorrect registry entry that refered to the Directory server and the Unity services being configured incorrectly. Re-runing the Services Wizard and changing the registry entry got Unity up and running.

Thanks