Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 807
  • Last Modified:

Exchange 2010 - ActiveSync drop outs (Error 1309) and other odd issues (OWA)

Hello,
I have a new exchange server and am currently in the process of slowly moving mailboxes from an older 2003 exchange server to the new one. Everything seemed to be goign just fine, but every so often I get issues with ActiveSync and sometimes OWA.  I also will randomly get errors when opening user mailbox properties but only when I select specific tabs (such as the calendar settings)

With all the items above (and it probably shows up in other places), I get an error, on screen (EMC), on a web page (OWA)  in the event log (ActiveSync):

"Operation not valid due to the current state of the object"

For active sync, error code is 1309


0
JamesonJendreas
Asked:
JamesonJendreas
  • 5
  • 4
1 Solution
 
ThorinOCommented:
Is this the EMC on the server or remote? Have you applied SP1 and rollup 4?
0
 
JamesonJendreasAuthor Commented:
Yeah, I'm connecting locally to the EMC, and have installed SP1 and rollup 4.  

One note, and I am not 100% sure about this, but it seems all these issue happen after we move a box from the old server to the new one.  It may just be coincidence, but there does seem to be some correlation.  I'm currently only moving 2-3 mailboxes a day as we work out issues.  I have some 450 total mailboxes.   A reboot does seem to fix the problem, and sometimes re-creating the virtual directories via the EMC then doing an iisreset.

I've also attempted to just restart the exchange services instead of a restart, but it tends to hang, and a reboot is required.  Obviously, daily reboots are not a solution!

Cheers
JJ
0
 
ThorinOCommented:
Can you try running the Exchange best practice analyzer and see if it comes back with anything.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
JamesonJendreasAuthor Commented:
Ok - I've ran the healh check, and am going to continue on to the others.  Not a whole lot there.

For my new server the only thing that showed was a "Database Backup Critical"

For my 2003 box:
'SystemPages' Set too high
ActiveDirectory cannot be contacted (?!)
HeapDeCOmmitFreeBlock Threshold not set
Open relay test failed
Physical Memory Configuration (Has more than 4GB, To avoid sever kernal memory depletion, limit or remove physical memory"
Missing FQDN in service principle name

So there are some items with the old server, but not on the new...
0
 
JamesonJendreasAuthor Commented:
Baseline scan gives me a BUNCH of items, but they are all something along the lines of:

Default IP Gateway
The value of configuration setting 'Default Gateway' on server SERVER is '192.168.0.6', which differs from specified value of ''.

ANd there's a bunch where the specified value is blank, and the configured value is pretty much correct (for the items I've checked so far)
0
 
JamesonJendreasAuthor Commented:
Connectivity test does give me:

Active Directory Server: WMI cannot be accessed
Cannot connect to the Windows Management Instrument (WMI) repository on server 2003DC.Domain.com.  This could be a permissions problem.  Error: Access is denied. (Exception from HRESULT: 0x8007005 (E_ACCESSDENIED))

Oddly, the AD server it is attempting to contact is my older 2003 AD server, which is a server I am looking to remove soon (I have 2 2008 DC's).  I have moved all the FSMO roles to a 2008 DC, as well as both 2008 DC"s being GC's (single domain forest)_
0
 
ThorinOCommented:
Sorry for not getting back with you on this, is it still an issue?
0
 
JamesonJendreasAuthor Commented:
Actually, I left the organization I was working for when this issue arose.  Now that I'm back to work (months later) I'm cleaning everything up.  

Although, I do believe I eventually found a solution.  We had a ton of AD issues resulting from a very poorly thought out topology, incorrectly demoted DC and AD sites that had subnet conflicts (all thi.  Running the best practices did in fact point us to the overall problems

Interestingly enough, after resolving these issues, I got laid off :)
0
 
ThorinOCommented:
Sorry about the layoff but glad it got fixed and that you have a new job.
0

Featured Post

[Webinar On Demand] Database Backup and Recovery

Does your company store data on premises, off site, in the cloud, or a combination of these? If you answered “yes”, you need a data backup recovery plan that fits each and every platform. Watch now as as Percona teaches us how to build agile data backup recovery plan.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now