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 2.4.6 to 3.1.2 - issues on import

Hey Jeff,<br><br>A couple weeks ago I asked you about a client who had dink'd w/ their ADC and wiped out their Unity server (changing the DOH to contacts). We are trying to move them to Exchange 2k. Everything installs perfectly but when attempting to import the users it errors on the call handler objects. All the users and call handlers import but the ch_%user% ones show errors.<br><br>Here's a copy of our log.<br><br>Any thoughts on why? We wiped the box and used killsubscriber???.exe on the Exch2k/AD stuff but to no avail.<br><br>Thoughts?<br><br><br>Log:<br> Alias=ch_NancyR<br> Display Name=ch_NancyR<br> DTMFID=1021<br> Owner Object ID=.401:{FE7E2006-2D21-49EA-877C-6AA91732E761} <br> Recipient Object ID=.401:{FE7E2006-2D21-49EA-877C-6AA91732E761} <br> Destination Object ID=.403:{DBB46979-44D9-46A0-B41D-DC216B60BFE4} <br> Rule:Alternate<br> Rule:Busy<br> Rule:Error<br> Destination Object ID=.403:{F2F22020-1E91-4B30-804E-CC932E83C988} <br> Rule:Internal<br> Rule:OffHours<br> Rule:Standard<br> Messaging Rules Complete<br> Menu Entry #11<br> Menu Entry #10<br> Menu Entry #0<br> Destination Object ID=.403:{6ED1AE4D-D532-4BDF-989D-648210F92680} <br> Menu Entry #1<br> Menu Entry #2<br> Menu Entry #3<br> Menu Entry #4<br> Menu Entry #5<br> Menu Entry #6<br> Menu Entry #7<br> Menu Entry #8<br> Menu Entry #9<br> Menu Entry Rules Complete<br><br>(error) in import call handlers 2nd pass. Number=-2147463168, Description=Method '~' of object '~' failed, Source=DatabaseImport<br> <br>Thanks,<br>Rob<br>rob@team-sos.com<br><br>

1 REPLY
Anonymous
N/A

Re: Unity 2.4.6 to 3.1.2 - issues on import

I suspect the data in the system you backed up had some missing chunks in it (possible given the ADC action that went on). That error in that spot is basically the DOH barking when I go to commit the changes made on the call handler during the import's second pass (this is where I link everything up). It could be any one of dozens of properties that it doesn't like, unfortunately it doesn't say which one.

The easiest way for me to troubleshoot this is to get hold of the MDB file created by the export and to import it in a debug environement here. Ping my at my corporate email and we'll see about setting that up.


Jeff Lindborg
Unity Technical Lead/Answer Monkey
Cisco Systems
lindborg@cisco.com
http://www.AnswerMonkey.net (new page for Unity support tools and scripts)

76
Views
0
Helpful
1
Replies
CreatePlease login to create content