Unity 4.2(1) Upgrade to 7.0(2) Setup failed to Configure default settings

[brown.george]

Unity 4.2(1) UM with Exchange 2003 / 2007

Upgrade Unity 4.2(1)tp 7.0(2). Phase 1 of Unity Install seems to be running OK, end of installation I get the following errors;

Setup was unable to configure default settings on your system. To resolve, do the following.

1. Gather the following file from the server, where <account> is the account name of the user logged on to the server running the installation:

-\Document and Setting\<account>\Local Settings\Temp\tempu*.*

-\Document and Setting\<account>\Local Settings\Temp\SysCheck*.*

-\Document and Setting\<account>\Local Settings\Temp\AV*.*

-\Document and Setting\<account>\Local Settings\Temp\tempu*.*

-\Document and Setting\<account>\Local Settings\Temp\CommServer_*_*.*, including all subdirectories

-\CommServer\Logs\OsqlDump_*_*.txt

-\CommServer\Logs\Diag_Install_*_*.txt

-\CommServer\Logs\CfgCUApp_*_*.txt

2. Contact the Cisco Technical Assistance Center (TAC).

3. Wait for instructions from TAC before proceeding.

I have reloaded the server from scratch, and restored DiRT. I have attempted the u/g twice - same error.

I am using lastet version of DiRT, and DBWalker (runs clean).

SQL Server and Agent services use the system account.

Nothing appears bad in the tempu.log or the OSQLDump logs..

Suggestions please

[Michael Owuor]

Hi George,

Check out defect CSCsf97662 which was documented for a similar error encountered while upgrading to a different version. The defect has pointers on what errors to look for in the OSQLDump logs, specifically relating to ReportDb.

If you see the same output in your logs, the same workaround may apply.

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsf97662

Hope this helps.

Regards,

Michael.

[brown.george]

Thanks Michael,

I've had a look through the logs, but they appear to be clean;

This is the last OSQLDump log...

Running UnityDefaultSQLObjects.sql

Amis RestrictionTable is Null in the Configuration table; Reading

value from the registry.

RegQueryValueEx() returned error 2, 'The system cannot find the file

specified.'

Amis RestrictionTable is Null in the registry; Nothing more to do.

Insert ConvHotel, Opt1 and Standard conversations.

(1 row affected)

Insert alternate custom 2.

(1 row affected)

Insert alternate custom 3.

(1 row affected)

Setup the clean delete objects if not set

RegQueryValueEx() returned error 2, 'The system cannot find the file

specified.'

CallHandlerecipName is Null in the registry.

Found defined alias for the example admin call handler.

(0 rows affected)

(0 rows affected)

(0 rows affected)

RegQueryValueEx() returned error 2, 'The system cannot find the file

specified.'

CallHandOwnerName is Null in the registry.

Found defined alias for the example admin call handler.

(0 rows affected)

(0 rows affected)

(0 rows affected)

RegQueryValueEx() returned error 2, 'The system cannot find the file

specified.'

CallHandAFtMsgName is Null in the registry.

Found defined alias for the goodbye call handler.

(0 rows affected)

(0 rows affected)

RegQueryValueEx() returned error 2, 'The system cannot find the file

specified.'

CallHandExitName is Null in the registry.

Found defined alias for the goodbye call handler.

(0 rows affected)

Device ReportDbDump already exists

Processed 96 pages for database 'ReportDb', file 'ReportDb' on file 2.

Processed 1 pages for database 'ReportDb', file 'ReportDb_log' on file

2.

BACKUP DATABASE successfully processed 97 pages in 0.219 seconds

(3.595 MB/sec).

(0 rows affected)

[Michael Owuor]

HI George,

Did you get this issue resolved? Did you get TAC involved?

Regards,

Michael.

[brown.george]

Michael,

Still trying to get it resolved. TAC have been involved for 3 weeks, but no resolution yet..

Regards,

gmb

[Michael Owuor]

George,

Would you please enumerate a summary of the precise step by step process you are taking, and which step the upgrade fails?

Thanks,

Michael.

[brown.george]

Michael,

Unity 4.2(1) on Windows Enterprise Server 2003SP2 SQL2000SP4, UM with Exchange 2003SP2 / 2007

Trying to Upgrade to 7.0(2).

Run CUSPA - all OK

Run Unity 7.0(2) setup, permission wizard runs clean, 7.0(2)license files install ok.

Latest version and installation media version of dbwalker run clean

DiRT skipped (already run with latest version)

Unity setup now runs, seems to go 98% of the way through, running SQL upgrade scipts etc, then fails with the above error.

Since the first failure, I've re-installed Windows and Unity on a clean DL380G4 server, then restored the DiRT backup using the latest versions of DIRT backup and restore.

No ES's installed for Unity, upgrade attempted again..

Still fails at the same point.

Regards,

gmb

[brown.george]

One other point.

We originally used only 3 unity accounts;

1.Installer account

2.Message and Service account (same)

3.Administration account

The 7 upgrade forces us to use 4, so at that point of the upgrade, we use the 4 acounts

gmb

[shabali52]

bug CSCsf97662 pointed by Michael does appear to be the case, however I ran into this earlier and what I found out was that somehow there was an instance of UnityDB and ReportDB which I had to detach from SQL Ent Manager and move the .mdf file to some other locations and rerun set which ended up resolving the issue.

[ranpierce]

Still having this issue? I had the exact same thing. Let me know and I will tell you what I did to resolve it.

rlp

[ranpierce]

sorry late on this I did the same thing

rlp

[steve.sarrick]

I deleted Reportdb and reportdb_log, recreated through osql command and restarted the install. Worked perfect.

[Jason Nash]

Hi George,

Did you ever resolve this one, I have the exact same problem as you report. My Osqldump log looks identical to the one you posted. Interested to know if and how you resolved?

[brown.george]

Yup Jason, I got it resolved after some weeks...

I could see under SQL Enterprise Manager, the properties of my database - the collation type was "Latin1_general_Cl_As"

It should have been "SQL_Latin1_general_Cl_As"

Turned out that when I'd installed all my UK Unity servers, I'd selected EnglishBritish as the regional locale exclusively (removing US). When you do that, then install SQL, the wrong collation type gets installed by default.

All I had to do to fix, was re-install windows2003, and when I installed SQL2000, choose a custom install, and choose "Dictionary Order, case insensitive, 1252 Character set".

I then restored my DiRT backup, and completed the u/g from 4 to 7

Hope this helps you,

Regards,

gmb

[brown.george]

Yup Jason, I got it resolved after some weeks...

I could see under SQL Enterprise Manager, the properties of my database - the collation type was "Latin1_general_Cl_As"

It should have been "SQL_Latin1_general_Cl_As"

Turned out that when I'd installed all my UK Unity servers, I'd selected EnglishBritish as the regional locale exclusively (removing US). When you do that, then install SQL, the wrong collation type gets installed by default.

All I had to do to fix, was re-install windows2003, and when I installed SQL2000, choose a custom install, and choose "Dictionary Order, case insensitive, 1252 Character set".

I then restored my DiRT backup, and completed the u/g from 4 to 7

Hope this helps you,

Regards,

gmb