"Item no longer exists" in OMA. With error 1000 in Event log

Lack of authentication prompt usually means one of the authentication settings is wrong.
Ensure that anonymous authentication isn't enabled on any of the Exchange virtual directories in IIS manager, except /exchweb.

Test it from Internet Explorer on your desktop with Show Friendly HTTP error messages disabled. That will show you a more useful error message than Pocket IE does.

Simon.

i've checked it from https://localhost/oma/ and get the same error both ways. I only seem to get access to OMA when logged on as administrator which is weird as all my users have mobile access turned on.

think i was testing from 'administrator' on my XDA which is why it's not asking me for another user.

IIS setting checked and its not enabled.

i have SSL ticked on my OMA. but i think it was there before. i certainly haven't changed it today (when it stopped bloody working)

turned on Integrated Auth for the Oma folder.  Now i get the following in the event log:



=======================================
Event Type:      Error
Event Source:      MSExchangeOMA
Event Category:      (1000)
Event ID:      1503
Date:            31/10/2006
Time:            11:43:48
User:            N/A
Computer:      BDS-SERVER
Description:
An unknown error occurred while processing the current request:
Message: No ServicesObject found!
Source: Microsoft.Exchange.OMA.UserInterface
Stack trace:
   at Microsoft.Exchange.OMA.UserInterface.Page.InitSessionVars()
   at Microsoft.Exchange.OMA.UserInterface.Page.Page_Load(Object sender, EventArgs e)
   at System.Web.UI.Control.OnLoad(EventArgs e)
   at System.Web.UI.MobileControls.MobilePage.OnLoad(EventArgs e)
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Page.ProcessRequestMain()

Message: Exception of type System.Web.HttpUnhandledException was thrown.
Source: System.Web
Stack trace:
   at System.Web.UI.Page.HandleError(Exception e)
   at System.Web.UI.Page.ProcessRequestMain()
   at System.Web.UI.Page.ProcessRequest()
   at System.Web.UI.Page.ProcessRequest(HttpContext context)
   at System.Web.HttpServerUtility.ExecuteInternal(String path, TextWriter writer, Boolean preserveForm)

Message: Error executing child request for oma.aspx.
Source: System.Web
Stack trace:
   at System.Web.HttpServerUtility.ExecuteInternal(String path, TextWriter writer, Boolean preserveForm)
   at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
   at Microsoft.Exchange.OMA.UserInterface.UserError.OkClick(Object sender, EventArgs e)
   at System.Web.UI.MobileControls.Command.OnClick(EventArgs e)
   at System.Web.UI.MobileControls.Command.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String argument)
   at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
   at System.Web.UI.MobileControls.MobilePage.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
   at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
   at System.Web.UI.Page.ProcessRequestMain()
   at System.Web.UI.Page.ProcessRequest()
   at System.Web.UI.Page.ProcessRequest(HttpContext context)
   at System.Web.CallHandlerExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute()
   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

sod. yeah that's because it doesn't like Windows Integrated Auth security!
turned it off again *chuckle*

!!!!!!!!!!!!! GGGGGGGGGGGRRRRRRRRRRRRRRRRRRRRRRr.

can now browse OMA from server https://localhost/oma but not from my device.

Can hit OMA on my home exchange box from my device.

maybe a certificate issue???

A lot of the problems with this feature are down to certificate.
Make sure that you don't have require SSL enabled on the /exchange virtual directory as that can break things.

Simon.

... or maybe an access issue?  Balls.

re-installed the cert. same problem - just not authenticating.

Si what's your VD path for 'exchange-oma' set to on a box near you? Maybe that's the problem??

no i Do have SSL enabled on /exchange, as everything's running HTTPS.

but this was set before.. so not sure this is the problem? Unless you just want it off for testing porpoises?

ok SSL off on both /exchange and /oma

same issue when connecting from the web.

yeah it was the VD.

changed the path before, then did an iisreset which... err.. reset it.

changed the path, did a 'default web site': stop. then a 'start'. THEN an IISreset, which kept the new path.

works ok. or seems to. no more eventlog errors.


cheers Si

Don't confuse the setting for require SSL with your ability to use SSL. You can use SSL without the require SSL option being on.

When you hit the web site, do you get an SSL certificate prompt?

Simon.

Si yeah i get the prompt when i browse to it. and when i'm in OMA on a PC i also get the certificate pop=up stuff.

not sure i understand using vs. requiring though..... *frowns*

I have 'require SSL' ticked on, on all my exchange related folders in default website?!

Require SSL means that the web server will reject the connection UNLESS it is coming over SSL.
If you turn that option off, you can still use SSL, it just will not reject the connection if it comes over http.
The problem is that OMA and Exchange ActiveSync make internal calls to the /exchange virtual directory on port 80. That cannot be changed. If you have require SSL enabled, everything breaks.

For the deployments that I do, this isn't a problem as I simply do not allow anonymous port 80 traffic in to the network. I only open two ports on the firewall - 25 (SMTP) and 443 (https). Nothing else is required. What happens behind the firewall doesn't really matter.

Simon.

yeah i do the same thing with my routers. so i can turn off the 'require SSL' on all the web folders in exchange??

ok thanks man. i will ensure it's not ticked.

500 more points to add to yer Trillion?! :)