[cisco-voip] Unity 5 and Exchange 2007, can not contact message store

Fri Feb 8 16:01:54 EST 2008

The VM ports do not need to have a CSS that has access  to the directory
number to turn on and off MWI.

On Feb 8, 2008 9:52 AM, Jonathan Charles <jonvoip at gmail.com> wrote:

> Make sure the CSS of the voicemail ports has the partition where the
> phones are...
>
>
>
> Jonathan
>
> On Feb 8, 2008 7:52 AM, Ian du Preez <iandupreez at gmail.com> wrote:
> > Unity server running Win 2003 Server SP1
> > Exchange running Win 2003 Server SP2
> >
> > I saw Exchange had no Service pack installed.
> > I downloaded SP 1 and installed it. Took very long.
> >
> > Now I have Unified messaging working in Outlook.
> > I can leave messages on the phone and they are droped in the users
> mailbow.
> > I can listen to them and they move out of the inbox, all ok.
> >
> > But the MWI on the phones are not working.
> > I can phone the MWI extensions from the phones and they go on and off.
> > But Unity can not turn them on or off.
> >
> > I get event id 121 from the CiscoUnity_TSP Source
> > and event id 1031 from the CiscoUnity_Notifier Source.
> >
> > Ian
> >
> >
> >
> >
> > On 2/7/08, Jonathan Charles <jonvoip at gmail.com> wrote:
> > > I presume you have downloaded the latest permissions wizard, and
> > > applied all of the service packs to Exchange, Windows, etc...
> > >
> > >
> > > J
> > >
> > > On Feb 7, 2008 5:12 AM, Ian du Preez <iandupreez at gmail.com> wrote:
> > > > Thanks
> > > > I looked at these.
> > > > Did'nt know I can make these changes from the 2003 Management side.
> > > >
> > > > I gave all these permissions and restarted Exchange and Uity.
> > > > But still get these 3 event errors and on the phone it plays that
> > > > unavailible messages greeting.
> > > >
> > > > The AD and Exchange Servers are running on VMware and Unity on a
> MCS.
> > > > Don't think this might be the problem. I've heard of guys getting it
> to
> > work
> > > > in this setup.
> > > >
> > > > Any ideas where to next?
> > > >
> > > > Thanks
> > > > Ian
> > > >
> > > >
> > > >
> > > >
> > > > On 2/6/08, Jonathan Charles <jonvoip at gmail.com> wrote:
> > > > > Go to Exchange system manager, delegate control, make sure the
> install
> > > > > acct is set an Exchange full admin; dirsvc is a full admin; and
> > > > > msgstore is a full admin...
> > > > >
> > > > > Go to the msgstore acct in ad users and computers, view advanced,
> > > > > click the security tab, make sure send-as and receive-as are
> checked.
> > > > >
> > > > > Make sure the dirsvc acct is a member of the domain admins
> group...
> > > > >
> > > > > make sure you have Exchange 2003 system tools on the unity box...
> > > > >
> > > > >
> > > > > J
> > > > >
> > > > > On Feb 6, 2008 1:09 AM, Ian du Preez <iandupreez at gmail.com> wrote:
> > > > > > How can I check all these now in 2003 and change to have the 3
> > accounts
> > > > have
> > > > > > the right permissions?
> > > > > > And in Exchange 2007, how do I make sure the right permissions
> are
> > set?
> > > > > >
> > > > > > Thanks
> > > > > > Ian
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On 2/6/08, Jonathan Charles <jonvoip at gmail.com> wrote:
> > > > > > > It still does with Windows 2003, though there is a reghack to
> make
> > it
> > > > > > > work again...
> > > > > > >
> > > > > > >
> > > > > > > J
> > > > > > >
> > > > > > > On Feb 5, 2008 8:06 AM, Ryan Ratliff <rratliff at cisco.com>
> wrote:
> > > > > > > > Is the msgstoresvc acount also a domain admin?  Back in the
> day
> > when
> > > > I
> > > > > > > > actually worked Unity cases the domain admin account had an
> > explicit
> > > > > > deny on
> > > > > > > > send as/receive as.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > -Ryan
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On Feb 5, 2008, at 4:00 AM, Ian du Preez wrote:
> > > > > > > > Exchange is up, and the normal test mailboxes I created can
> send
> > and
> > > > > > recieve
> > > > > > > > mail.
> > > > > > > > The server is not out of disk space.
> > > > > > > > All 3 the Unity accounts are Exchange Organization
> > Administrators.
> > > > > > > >
> > > > > > > > In Exchange 2007, how do I check that the system attendent,
> MTA
> > and
> > > > so
> > > > > > on
> > > > > > > > are up?
> > > > > > > > And how do I check the accounts have send-as and receive-as
> > rights?
> > > > > > > >
> > > > > > > > Thanks
> > > > > > > > Ian
> > > > > > > >
> > > > > > > >
> > > > > > > > On 2/4/08, Jonathan Charles <jonvoip at gmail.com> wrote:
> > > > > > > > > OK, dumb question mode...
> > > > > > > > >
> > > > > > > > > Is Exchange up, I mean is system attendant, MTA, etc up?
> > > > > > > > >
> > > > > > > > > Is the Exchange server out of hard drive space?
> > > > > > > > >
> > > > > > > > > Does the unitymsgstoresvc account have Exchange access
> > (delegate
> > > > > > > > > control, etc...) does it have send-as and receive-as
> rights?
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Jonathan
> > > > > > > > >
> > > > > > > > > On Feb 4, 2008 3:34 AM, Ian du Preez <iandupreez at gmail.com
> >
> > wrote:
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > I have done so, but still with no success.
> > > > > > > > > >
> > > > > > > > > > In Unity 4, when these types of errors happened, Unity
> would
> > > > just
> > > > > > not
> > > > > > > > star
> > > > > > > > > > up.
> > > > > > > > > >
> > > > > > > > > > But now it does start and everything looks ok.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Should I try rebuilding Exchange or Unity.
> > > > > > > > > >
> > > > > > > > > > Have no idea what next.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Thanks
> > > > > > > > > >
> > > > > > > > > > Ian
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On 2/1/08, Scott Voll <svoll.voip at gmail.com> wrote:
> > > > > > > > > > >
> > > > > > > > > > > have you rebooted the exchange server ..... then the
> unity
> > > > server?
> > > > > > > > I'm
> > > > > > > > > > just guessing.  Maybe the Unity server can't log into
> the
> > > > account.
> > > > > > > > > > >
> > > > > > > > > > > Scott
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > On Jan 31, 2008 11:55 PM, Ian du Preez
> > <iandupreez at gmail.com>
> > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Hi all
> > > > > > > > > > > >
> > > > > > > > > > > > I finished building a lab with CM6, Unity 5 and
> Exchange
> > > > 2007
> > > > > > SP1.
> > > > > > > > > > > > I did all the steps as the manual shows and all went
> > > > through.
> > > > > > > > > > > > This is a complete new install of everything.
> > > > > > > > > > > > The installation went through with no problems.
> > > > > > > > > > > > Unity is up and running, and Syscheck shows no
> problems
> > with
> > > > > > > > Exchange
> > > > > > > > > > permissions or access.
> > > > > > > > > > > > I imported test users from exchange and they enroll
> ok.
> > > > > > > > > > > >
> > > > > > > > > > > > But trying to access the messages on the phone I get
>  "
> > Your
> > > > > > > > messages
> > > > > > > > > > are not availible now "
> > > > > > > > > > > >
> > > > > > > > > > > > According to the syscheck tool, all the system
> accounts
> > have
> > > > > > enough
> > > > > > > > > > rights.
> > > > > > > > > > > > All the Unity services, including the AvCsMgr
> service
> > has no
> > > > > > problem
> > > > > > > > > > starting up.
> > > > > > > > > > > >
> > > > > > > > > > > > Below are the errors I get in the event log.
> > > > > > > > > > > >
> > > > > > > > > > > > Does any one know what I can do to fix this?
> > > > > > > > > > > > On Unity4 I saw this a couple of times, but its
> usually
> > > > > > permissions
> > > > > > > > in
> > > > > > > > > > Exchange.
> > > > > > > > > > > >
> > > > > > > > > > > > Any help will be great
> > > > > > > > > > > > Thanks
> > > > > > > > > > > >
> > > > > > > > > > > > First error is :
> > > > > > > > > > > >
> > > > > > > > > > > > ivent ID : 1004
> > > > > > > > > > > > Source : CuscoUnity_ExchangeMo
> > > > > > > > > > > > Description :
> > > > > > > > > > > > The following information store is currently off
> line.
> > > > > > > > > > > > CN=...........
> > > > > > > > > > > >
> > > > > > > > > > > > The I get these ones every 5 minutes :
> > > > > > > > > > > >
> > > > > > > > > > > > ID: 30003
> > > > > > > > > > > > Source: CiscoUnity_MALEx
> > > > > > > > > > > > Message: An attempt to access the Primary Exchange
> > Mailbox
> > > > Store
> > > > > > by
> > > > > > > > %1
> > > > > > > > > > via MAPI has failed. The MAPI subsystem return the
> following
> > > > error:
> > > > > > %2.
> > > > > > > > > > > > An attempt to access the Primary Exchange Mailbox
> Store
> > by
> > > > %1
> > > > > > via
> > > > > > > > MAPI
> > > > > > > > > > has failed. The MAPI subsystem return the following
> error:
> > %2.
> > > > > > > > > > > >
> > > > > > > > > > > > ID: 30012
> > > > > > > > > > > > Source: CiscoUnity_MALEx
> > > > > > > > > > > > Message: An occurred which prevents successful
> Exchange
> > > > access
> > > > > > by %1
> > > > > > > > via
> > > > > > > > > > MAPI.%n%nThis is typically an indication of
> configuration
> > issues
> > > > > > with
> > > > > > > > Unity,
> > > > > > > > > > Exchange, or the MAPI subsystem.%n%nVerify that the
> Unity
> > > > services
> > > > > > > > accounts
> > > > > > > > > > are granted the correct permissions and that there are
> no
> > issues
> > > > > > with
> > > > > > > > > > installation. The SysCheck utility may assist in
> diagnosing
> > the
> > > > > > problem.
> > > > > > > > > > > >
> > > > > > > > > > > > ID: 32013
> > > > > > > > > > > > Source: CiscoUnity_Doh
> > > > > > > > > > > > Message: Doh logon failed due to messaging component
> > logon
> > > > > > error: %1
> > > > > > > > > > > > Doh logon failed due to messaging component logon
> error:
> > %1
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > _______________________________________________
> > > > > > > > > > > > cisco-voip mailing list
> > > > > > > > > > > > cisco-voip at puck.nether.net
> > > > > > > > > > > > https://puck.nether.net/mailman/listinfo/cisco-voip
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > _______________________________________________
> > > > > > > > > > cisco-voip mailing list
> > > > > > > > > > cisco-voip at puck.nether.net
> > > > > > > > > > https://puck.nether.net/mailman/listinfo/cisco-voip
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > > _______________________________________________
> > > > > > > > cisco-voip mailing list
> > > > > > > > cisco-voip at puck.nether.net
> > > > > > > > https://puck.nether.net/mailman/listinfo/cisco-voip
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> >
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20080208/bf62edb8/attachment-0001.html 