Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

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

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

21 REPLIES
Cisco Employee

Re: Unity 4.2(1) Upgrade to 7.0(2) Setup failed to Configure def

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.

New Member

Re: Unity 4.2(1) Upgrade to 7.0(2) Setup failed to Configure def

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)

Cisco Employee

Re: Unity 4.2(1) Upgrade to 7.0(2) Setup failed to Configure def

HI George,

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

Regards,

Michael.

New Member

Re: Unity 4.2(1) Upgrade to 7.0(2) Setup failed to Configure def

Michael,

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

Regards,

gmb

Cisco Employee

Re: Unity 4.2(1) Upgrade to 7.0(2) Setup failed to Configure def

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.

New Member

Re: Unity 4.2(1) Upgrade to 7.0(2) Setup failed to Configure def

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

New Member

Re: Unity 4.2(1) Upgrade to 7.0(2) Setup failed to Configure def

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

New Member

Re: Unity 4.2(1) Upgrade to 7.0(2) Setup failed to Configure def

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.

Silver

Re: Unity 4.2(1) Upgrade to 7.0(2) Setup failed to Configure def

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

Silver

Re: Unity 4.2(1) Upgrade to 7.0(2) Setup failed to Configure def

sorry late on this I did the same thing

rlp

New Member

Re: Unity 4.2(1) Upgrade to 7.0(2) Setup failed to Configure def

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

New Member

Re: Unity 4.2(1) Upgrade to 7.0(2) Setup failed to Configure def

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?

New Member

Re: Unity 4.2(1) Upgrade to 7.0(2) Setup failed to Configure def

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

New Member

Re: Unity 4.2(1) Upgrade to 7.0(2) Setup failed to Configure def

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

New Member

Re: Unity 4.2(1) Upgrade to 7.0(2) Setup failed to Configure def

Perfect! My problem was the same cause! I can actually see the error in the OSQL logs regarding the collation issue now. I don't recall anything in the notes on this (unless I missed it), it would have been good if the original install had checked on this as it can be easily avoided.

As this is a small install it is using MSDE which does not give any options when installing, it just selected the collation based on the locale of the OS.

As I did not want to completely rebuild I found a workaround. I changed the locale of the OS to English (US) and then uninstalled and reinstalled MSDE, this then picked up the correct collation (SQL_Latin1_General_CP1_CI_AS). I then just restored the UnityDB (as the collation was Ok on this as it came from a DIRT backup of an old server), recreated the ReportDB and imported all of the users, jobs etc back in. Ran the install and all is working perfectly now.

Thanks for your assistance on this one.

New Member

Re: Unity 4.2(1) Upgrade to 7.0(2) Setup failed to Configure def

I have this same problem. Upgrading from 4.2 to 7.0 failed and the osql dumps show the collation problem. However my box has been built with english and english US. All dbases except the unitydb have the correct collation. Any ideas how I can overcome this? I can't see how rebuilding the box and then restoring the same Dirt backup will fix this, as the dirt restore will surely set the unitydb back to the "wrong" collation, causing the subsequant upgrade to fail again. Any ideas, much appreciated.

New Member

Re: Unity 4.2(1) Upgrade to 7.0(2) Setup failed to Configure def

Allan, it does!

A rebuild selecting the correct collation, then restore will fix the issue,

gmb

New Member

Re: Unity 4.2(1) Upgrade to 7.0(2) Setup failed to Configure def

Thanks George - can i confirm these steps.

uninstall unity and sql, then reinstall sql selecting a custom build using the parameters you have specified. Then restore my 4.2 dirt restore, then run the upgrade. If i already have the os built correctly, there seems no point in doing that again? Thanks again very much for the reply!

New Member

Re: Unity 4.2(1) Upgrade to 7.0(2) Setup failed to Configure def

Perfect

New Member

Re: Unity 4.2(1) Upgrade to 7.0(2) Setup failed to Configure def

HI George, this isn't going to work for me. My box is built correctly and up to the point of restoring the db via dirt, the collation is correct. After running the dirt restore, the collation changes. I'm possibly going to have to recreate the unitydb with the correct collation - but im not a sql person. Thanks for the replies, will let you know how it goes with support - case is open now.

New Member

Re: Unity 4.2(1) Upgrade to 7.0(2) Setup failed to Configure def

Just for completeness, I'd like to clarify some issues surrounding this problem. There seem to be several conditions that cause the same error message. My particular problem it seemed was a mismatch between the unitydb collation and the sql server default collation. NB you do not have to have sql_latin1_general for the upgrade to work. Think about it - unity is used in many countries and they would build sql server to their own requirements not US standard! Rather it seems you need to have matching collations, which makes sense. Seems obvious in hindsight. My original 4.0 server built in 2005 had been built with latin1_general_ci_as as the server / sql default and likewise the unitydb was the same when created. My 4.0 server was upgrade to 4.2 with no drama. Last year during a hardware refresh I built a server from scratch but left the US local on the server. When you then install sql on a box with the us local enabled (but not necessarily the default), sql server defaults to the sql_latin1_general_XX_XX_XX already mentioned in this conversation. Restoring the unitydb using DiRT threw up no problems and I've had a good working 4.2 unity server since last year. After trying to add some languages to our server at the end of last year I had the same error message as shown at the start of this thread caused by the schema version being in the sql server tables. HP support very kindly advised me to change the major and minor version to 3 and 17 respectively which then allowed the upgrade (installation of language packs) to succeed (thanks HP). I don't know how this problem came about, but their fix worked. Now if you see in your osql dumps, a message about schema versions being null or missing you can manually edit the server table and insert the correct major and minor version, then be confident your upgrade attempt will complete. If you see a message about collation mismatch / problems check your unitydb and sql server default are the same. If you need to change something, it really has to be the sql server default to match the unitydb as it is not so easy to change a db collation properly. Hope this helps others with similar probs - thanks George for putting me on the right track with your fix.

408
Views
5
Helpful
21
Replies
CreatePlease login to create content