RE: OMA only works for some users

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hi

Thank you for replying.

The server operating system is Server 2003 with an Exchange 2003 standard
edition.

The domain admin can log on without any problem and ONE user can also access
OMA. But most users cant.

The Local path of Exchange-OMA virtual directory IS different from Exchange
virtual directory. I have tried to change the OMAs to the same as Exchange
but then the ONE user that can access OMA fails. And noone else can access
OMA either. The diffrence is that I get another error. So I have gone back to
the way it was and have different directories on the two.

Log files are sent to your email.

Thank you
Best regards
Perra


I have verified that the OWA and OMA virtual directory is the same SMTP
domain as the users trying to access OMA.




--
________________________
Per-Olof Olsson
IT - Manager


"chace zhang" wrote:

Hi,

Thank you for posting here.

From you post, I understand domain admin can access oma, however other
users get "Item no longer exists. The item you are attempting to access may
have been deleted or moved" error. If I have misunderstood your concern,
please do not hesitate to let me know.

Does this is a SBS Server? Since Small Business Server is integrated with
Exchange Server, since some Exchange issue maybe specific to SBS
environment. In order to provide more efficient support on this issue,
please double confirm it to me first.

Per my research, the issue may happen when the SMTP address of problematic
user account doesn't include the SMTP domain hosted by Exchange virtual
directory.

To determine the SMTP Domain hosted in Exchange virtual directory:

1. Start Exchange System Manager.
2. Expand Servers, expand ServerName, expand Protocols, expand HTTP, expand
Exchange Virtual Server, and then expand Exchange.
3. Right-click the Exchange virtual directory, and then click Properties to
view the properties of the Exchange virtual directory. This is the default
OWA virtual directory created during Exchange Server Setup.
4. On the General tab, note the value from the field labeled Exchange Path.
An example of this value is example.com (default).

- To determine the SMTP address of user account who cannot login OMA:

1. Start the Active Directory Users and Computers snap-in (ADUC).
2. Locate the specific user account in the console tree, right-click the
user account, and then click Properties.
3. Click the E-mail Addresses tab, you will see all SMTP address here.

Please verify whether the SMTP addresses of this user who encountered this
issue include the SMTP domain hosted by Exchange virtual directory.

If they are different, just for troubleshooting purpose, accessing E-mail
Addresses tab of this user account in Active Directory Users and Computers
(ADUC) snap-in, uncheck "Automatically update e-mail addresses based on
recipient policy" and then click New to add a SMTP address including the
SMTP domain hosted by Exchange virtual directory. Then restart Exchange
System Attendant service and then verify the issue.

Also this issue may happen when Local path of Exchange-OMA virtual
directory is different from Exchange virtual directory.

To troubleshoot the issue, please follow steps below to make Local path of
Exchange-OMA virtual directory the same as Exchange virtual directory.

1. Go to Start/Administrative Tools/Internet Information Services (IIS)
Manager
2. Expand out the list by clicking the plus sign next to the server's name
3. Expand out the Web Sites
4. Expand out Default Web Site
5. Right click the Exchange virtual directory, click Properties. Copy the
value for Local Path to a word file.
5. Right click the exchange-OMA virtual directory and select Properties
6. Compare the value in the Local Path box from the Exchange-OMA virtual
directory with the Exchange virtual directory.
7. If they are different, make Local path of Exchange-OMA virtual directory
the same as Exchange virtual directory.
8. Restart IIS Admin service and Exchange System Attendant service to take
change effect.


If the issue persists after steps above, please help me gather following
info for further analysis.

Collect the IIS metabase on Exchange Server and send to me:
v-chacez@xxxxxxxxxxxxx

1). On Exchange Server, install .NET Framework Version 1.1:
http://www.microsoft.com/downloads/details.aspx?FamilyID=262d25e3-f589-4842-
8157-034d1e7cf3a3&DisplayLang=en.
2). Install MBExplorer by installing IIS 6 Resource Kit Tools:
http://www.microsoft.com/downloads/details.aspx?FamilyId=56FC92EE-A71A-4C73-
B628-ADE629C89499&displaylang=en.
3). Once it is installed, access it from Start, Programs, IIS Resources,
Metabase Explorer.
4). In the left pane, right click ''LM'' (under your server computer name)
to choose ''Export to file'', and then save it as IIS.mbk.
5). Compress this mbk file and send it to me for analysis. Please let me
know the password if you set on this iis mbk file.

3. Please collect the IIS log on Exchange Server so that I can perform
further research:

1). On Exchange Serves, open IIS MMC, right click Default Web Site and then
click Properties.
2). Click Website tab and then check Enable logging.
3). Stop the Default Website and RENAME the existing IIS log files under
C:\WINDOWS\system32\LogFiles\W3SVC1.
4). Restart the Default Website and reproduce the OMA problem, which will
generate new IIS log file with the exact error.
5). Wait for a while so that IIS Log can be synced. And then go to the
following folder on Exchange Server: C:\WINDOWS\system32\LogFiles\W3SVC1.
6). Send me the log files to my working email address
v-chacez@xxxxxxxxxxxxx
And please let me know the alias of the user who encountered the issue.

Hope this helps, if you need more assistance on this issue, please do not
hesitate to let me know.

Have a nice day!

Best Regards,

Chace Zhang (MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on Exchange technical issues. If you have
issues regarding other Microsoft products, you'd better post in the
corresponding newsgroups so that they can be resolved in an efficient and
timely manner. You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.

=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| Thread-Topic: OMA only works for some users
| thread-index: AcbrplL1VDprCfu9QkqoDW6bSUDBKA==
| X-WBNR-Posting-Host: 213.115.2.228
| From: =?Utf-8?B?ZmM5YTlmODItMjEyOTY5Mjg1MEBuZXdzLnBvc3RhbGlhcw==?=
<fc9a9f82-2129692850@xxxxxxxxxxxxxx>
| Subject: OMA only works for some users
| Date: Mon, 9 Oct 2006 06:25:01 -0700
| Lines: 24
| Message-ID: <71F00E97-0111-4E93-BCF7-296972DDFC42@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
| Newsgroups: microsoft.public.exchange.setup
| Path: TK2MSFTNGXA01.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.exchange.setup:144712
| NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
| X-Tomcat-NG: microsoft.public.exchange.setup
|
| Hi
|
| I have had OMA working for a while and It has only been used now and then
by
| some users so I havent discovered that its not working until recently for
me.
| Now when I try to access oma i get :
|
| Item no longer exists. The item you are attempting to access may have
been
| deleted or moved.
| Home
|
| I have as I have found out now only one user and the domain admin that
| doesnt get that message and actually can access OMA properly. I have
looked
| at settings for other users in ADUC and OMA is enabeled under exchange
| features and so on. I cant find what is worong, it feels like its a
| access/security problem as i actually have one user(+admin) that works
and
| others dont, but the message doesnt state that it is... so any
suggestions is
| appreciated. I have been struggeling for a long time with this now...
|
| thank you
| Perra
| --
| ________________________
| Per-Olof Olsson
| IT - Manager
|


.

Relevant Pages

  • RE: OMA not accessible
    ... If this is not the case, your Exchange ... Microsoft Outlook or Microsoft Outlook Web Access to create your user ... This problem may occur if the Exchange Server 2003 computer is heavily ... the OMA virtual directory may corrupted on SBS. ...
    (microsoft.public.windows.server.sbs)
  • Re: can access oma via browser, but mobile device wont work
    ... We have clients with larger networks and Exchange ... two addresses were the only addresses allowed to connect to the oma ... oma virtual directory is there and it has been set up by the wizard. ... that I am supposed to rebuild the server to fix this... ...
    (microsoft.public.windows.server.sbs)
  • RE: OMA
    ... To access the contents of a user's mailbox in Exchange Server 2003, ... It appeared meaningful for my problem, in fact the error was raised by OMA ... > invokeAttr, Binder binder, Objectparameters, CultureInfo culture, Boolean ...
    (microsoft.public.exchange.setup)
  • Re: Since sp2 installation, users are no longer able to access OMA on exchange 2003
    ... we are running an exchange 2003 cluster on windows 2003 servers front ... All are up to date with sp2 installed, starting with the front end server, ... Yes we are using blackberries to access OMA, although even when I am trying ... > And you aren't using BES or Blackberry desktop redirector BECAUSE... ...
    (microsoft.public.exchange2000.general)
  • Re: OWA logon issue
    ... We have one exchange 2003 server. ... > backslash before their username to logon to OWA. ... page) for the Exchange Virtual Directory in Internet Services Manager on ...
    (microsoft.public.exchange.setup)